A lock screen login method, device, electronic device, and storage medium

Abstract

The present application discloses a lock screen login method, device, electronic device, and storage medium, which specifically include: obtaining verification information collected by a user terminal; sending the verification information to a server for verification, and if the verification is passed, obtaining a login token from the server according to the verification information; sending a system login verification request to the server according to the login token to obtain user system login information; comparing the user system login information with the user information saved locally, and performing system login after successful comparison; after performing system login, saving the login token to update the login token stored locally; performing single sign-on according to the updated login token. It improves the separation between system login and single sign-on in the prior art to obtaining the single sign-on permission while performing system login, realizes the synchronization of system login and single sign-on, further improves the single sign-on efficiency of the user terminal, and improves the operation convenience of the user, enhancing the user experience.

Description

Technical Field

[0001] This application relates to the technical field of data processing, and in particular, to a screen lock login method, device, electronic device, and storage medium. Background Art

[0002] With the rapid development of the Internet industry, more and more users use online methods to handle work. As a result, various functional websites, software, etc. emerge in an endless stream, and users can select corresponding websites or software to log in and use according to their own needs. In order to improve the user's usage convenience, single sign-on technology has emerged.

[0003] Currently, when a user faces different software or systems on the same terminal, the process of repeated verification in different software or systems can be omitted through single sign-on. However, each software or system still needs to repeatedly access the server to verify whether the user is allowed to log in, so it will consume more access resources and reduce the login efficiency. Summary of the Invention

[0004] This application provides a screen lock login method, device, electronic device, and storage medium to improve the user's single sign-on efficiency.

[0005] According to one aspect of this application, a screen lock login method is provided, which is executed by a system login control module configured in a user terminal. The method includes:

[0006] Obtain verification information collected by the user terminal;

[0007] Send the verification information to the server for verification, and if the verification is passed, obtain a login token from the server according to the verification information;

[0008] Send a system login verification request to the server according to the login token to obtain user system login information;

[0009] Compare the user system login information with the user information saved locally, and perform system login after successful comparison;

[0010] After performing system login, save the login token to update the login token stored locally;

[0011] Perform single sign-on according to the updated login token.

[0012] According to another aspect of this application, a screen lock login method is provided, which is applied to the server. The method includes:

[0013] Obtain the verification information sent by the system login control module and perform verification;

[0014] If the verification is passed, a login token is generated according to the verification information, and the login token is sent to the system login control module, so that the system login control module sends a system login verification request to the server according to the login token;

[0015] According to the system login verification request, user system login information is generated and sent to the system login control module, so that the system login control module performs the following operations: compare the user system login information with the user information saved locally, and perform system login after successful comparison; after performing system login, save the login token to update the login token stored locally; perform single sign-on according to the updated login token.

[0016] According to another aspect of the present application, a lock screen login device is provided, which is applied to the system login control module of the user terminal. The device includes:

[0017] A verification information acquisition module, configured to acquire verification information collected by the user terminal;

[0018] A login token acquisition module, configured to send the verification information to the server for verification, and if the verification is passed, acquire the login token from the server according to the verification information;

[0019] A login request sending module, configured to send a system login verification request to the server according to the login token to acquire user system login information;

[0020] A system login module, configured to compare the user system login information with the user information saved locally, and perform system login after successful comparison;

[0021] A login token update module, configured to save the login token after performing system login to update the login token stored locally;

[0022] A single sign-on module, configured to perform single sign-on according to the updated login token.

[0023] According to another aspect of the present application, a lock screen login device is provided, which is applied to the server. The device includes:

[0024] An information verification module, configured to acquire the verification information sent by the system login control module and perform verification;

[0025] A login token generation module, configured to generate a login token according to the verification information if the verification is passed, and send the login token to the system login control module, so that the system login control module sends a system login verification request to the server according to the login token;

[0026] A login information generation module, which is used to generate user system login information according to a system login verification request, and send the user system login information to a system login control module, so that the system login control module performs the following operations: compare the user system login information with the user information saved locally, and perform system login after successful comparison; after performing system login, save a login token to update the login token stored locally; perform single sign-on according to the updated login token.

[0027] According to another aspect of the present application, there is provided an electronic device, which includes:

[0028] At least one processor; and

[0029] A memory communicatively connected to the at least one processor; wherein,

[0030] The memory stores a computer program executable by the at least one processor, and the computer program is executed by the at least one processor, so that the at least one processor can execute the lock screen login method described in any embodiment of the present application.

[0031] According to another aspect of the present application, there is provided a computer-readable storage medium, which stores computer instructions for implementing the lock screen login method described in any embodiment of the present application when executed by a processor.

[0032] The technical solution of the embodiment of the present application obtains a login token for single sign-on while performing system login of the user terminal, improves the separation between system login and single sign-on in the prior art to obtaining the permission of single sign-on while performing system login, realizes the synchronization of system login and single sign-on, further improves the single sign-on efficiency of the user terminal, and improves the operation convenience of the user, thus enhancing the user experience.

[0033] It should be understood that the content described in this part is not intended to identify the key or important features of the embodiments of the present application, nor is it used to limit the scope of the present application. Other features of the present application will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0034] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following will briefly introduce the drawings required for the description of the embodiments. Obviously, the following drawings are only some embodiments of the present application. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts.

[0035] Figure 1 is a flowchart of a lock screen login method provided in Embodiment 1 of the present application;

[0036] Figure 2 is a flowchart of a lock screen login method provided in Embodiment 2 of the present application;

[0037] Figure 3 is a flowchart of a lock screen login method provided in Embodiment 3 of the present application;

[0038] Figure 4 is a schematic diagram of single sign - on provided in Embodiment 4 of the present application;

[0039] Figure 5 is a structural diagram of a lock screen login device provided in Embodiment 5 of the present application;

[0040] Figure 6 is a structural diagram of a lock screen login device provided in Embodiment 6 of the present application;

[0041] Figure 7 is a schematic structural diagram of an electronic device for implementing the lock screen login method of the embodiments of the present application. Detailed implementation manners

[0042] In order to enable those skilled in the art to better understand the solutions of the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present application.

[0043] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application 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 such used data can be interchanged under appropriate circumstances so that the embodiments of the present application described here can be implemented in an order different from those illustrated or described here. In addition, the terms "include" and "have" and any variations thereof are intended to cover non - exclusive inclusion. For example, a process, method, system, product or device including a series of steps or units does not necessarily have to be limited to those clearly listed steps or units, but may include other steps or units not clearly listed or inherent to these processes, methods, products or devices.

[0044] Embodiment 1

[0045] Figure 1The present invention provides a flowchart of a lock screen login method according to Embodiment 1 of the present application. This embodiment is applicable to the case where single sign-on conditions are activated during system login. The method can be executed by the system login control module of the user terminal and can be set in a lock screen login device, which can be implemented in the form of hardware and / or software and can be configured in an electronic device.

[0046] In a practical implementation, the technical solution of the embodiment of the present application can be executed by the system login control module configured in the user terminal. The user terminal may include, but is not limited to, devices such as the user's computer and mobile phone. The system login control module can be a functional software for controlling system login and / or single sign-on, and can be an application program for unlocking the lock screen and obtaining single sign-on conditions, which is an application program independent of the default unlocking function in the user terminal. For example, the system login control module mentioned in the embodiments of the present application can replace the original login model in the user terminal through CP (Credential Provider) or a user-defined GINA (Graphical Identification and Authentication) model, and cooperate with the server (such as an authentication server) to achieve secure login of the user terminal. In particular, the system control module can be installed as a software (application program) in the operating system of the user terminal or in other hardware devices that can be securely connected to the user terminal, such as external hard disks and servers.

[0047] As Figure 1 shown, the method includes:

[0048] S110. Obtain the verification information collected by the user terminal.

[0049] Among them, the verification information can be data information for verifying the login of the user terminal, such as, but not limited to, passwords, digital certificates, dynamic passwords, facial recognition information, gesture information, fingerprint information, and two-dimensional code information, etc. The verification information can be collected through the inherent program of the user terminal, or the collection function of the verification information can be integrated into the system login control module in the user terminal. The embodiments of the present application do not limit this.

[0050] S120. Send the verification information to the server for verification, and if the verification is passed, obtain a login token from the server according to the verification information.

[0051] Among them, the server side corresponds to the user terminal and is a server side that interacts with the user terminal. For example, it can be in the form of a remote server, an authentication server, etc. The system login control module in the user terminal sends the obtained verification information to the server side so that the server side verifies the verification information. Of course, any verification method in the prior art can be used for verification, and the embodiments of the present application do not limit this. For example, the verification information can be compared with the user information of the user terminal pre-stored in the server side to verify whether the person with the permission to use the user terminal unlocks the user terminal. If the verification passes, the system login control module can apply to the server side for a login token used for system login, and the login token can be a user authentication token provided by the background authentication server.

[0052] S130. Send a system login verification request to the server side according to the login token to obtain user system login information.

[0053] Among them, the user system login information can be data information used by the user for unlocking and logging in. For example, it can include but is not limited to the user's personal information, etc. After the system login control module obtains the login token, it triggers the sending of the login verification request and applies to the server side to obtain the user system login information.

[0054] S140. Compare the user system login information with the user information saved locally, and perform system login after successful comparison.

[0055] Among them, the user information can be data information saved in the system login control module of the user terminal locally for login unlocking verification. Of course, it can also include but is not limited to the user's personal information, etc. Compare the user system login information obtained from the server side with the user information saved in the local system login control module to confirm whether the information is unified. After the comparison is determined to be unified, the user is allowed to unlock the current user terminal for login. It should be added that for the local storage of data such as user information in the present application, it can be stored in the system login control module or in the local memory of the user terminal. The storage in the system login control module in the embodiments of the present application should not be understood as a limitation on local storage.

[0056] S150. After performing system login, save the login token to update the login token stored locally.

[0057] After the user unlocks and logs in to the system, save the login token obtained from the server side in the previous steps to the local system login control module, and update the old login token stored in the local system login control module.

[0058] S160. Perform single sign-on according to the updated login token.

[0059] Perform single sign-on operation within the system of the user terminal using the updated login token.

[0060] It should be noted that in the prior art, for single sign-on, the user terminal needs to be unlocked and the system needs to be logged in first. When the system is running, the application programs that support single sign-on obtain the login tokens required for single sign-on from the server, so as to achieve the effect of logging in to multiple application programs without repeated verification using only one login token. In this embodiment, when the user unlocks and logs in to the user terminal, the login token is obtained simultaneously. The login token not only serves as the basis for single sign-on, but also as the basis for system unlocking and login. Just obtaining this login token can complete the unlocking of the user terminal and system login, and this login token can also be used for single sign-on of multiple application programs within the system, realizing the dual use of system login and single sign-on.

[0061] The technical solution of the embodiment of the present application obtains the login token for single sign-on while performing system login of the user terminal, improving the separation between system login and single sign-on in the prior art to obtaining the permission for single sign-on while performing system login, realizing the synchronization of system login and single sign-on, further improving the single sign-on efficiency of the user terminal, enhancing the operation convenience of the user, and improving the user experience.

[0062] In another optional implementation manner, the system login control module can also be used to pre-store user information, configure the registration information between the user account and the server, and establish the binding relationship between the system login control module and the user information.

[0063] Among them, the registration information between the user account and the server can be the information of the user's account registration on the server when the user uses the user terminal. This registration information can be writing the user's personal information and user terminal information (such as IP address, etc.) into the server to enable the user to obtain the qualification (or permission) of the login account. At the same time, the binding relationship between the system login control module and the user information can also be established. According to this binding relationship, the user's login behavior can be verified to verify whether the user is the one allowed to log in by the system (the system of the user terminal). On the one hand, the user can lock the screen after using the terminal, and the next system unlocking will also verify whether it is the user allowed to log in in the previous or historical records, further improving the security of the user terminal and ensuring the privacy of single sign-on.

[0064] Embodiment Two

[0065] Figure 2 It is a flowchart of a lock screen login method provided by the second embodiment of the present application. This embodiment further refines the single sign-on operation on the basis of the foregoing embodiments. As Figure 2As shown, the method includes:

[0066] S210. Obtain verification information collected by the user terminal.

[0067] S220. Send the verification information to the server for verification. If the verification is passed, obtain a login token from the server according to the verification information.

[0068] S230. Send a system login verification request to the server according to the login token to obtain user system login information.

[0069] S240. Compare the user system login information with the user information saved locally. After successful comparison, perform system login.

[0070] S250. After performing system login, save the login token to update the login token stored locally.

[0071] Optionally, the method may further include: storing the updated login token in the browser at a preset period.

[0072] After saving the login token obtained from the server during system login to the local to update the old login token in the local system login control module, the new login token saved locally can be additionally stored in the browser at a preset period for easy invocation by the browser.

[0073] Or, the method may further include: while updating the login token stored locally, storing the updated login token in the browser.

[0074] While saving the login token obtained from the server during system login to the local, the updated login token can also be directly and concurrently saved to the browser of the system for easy invocation by the browser.

[0075] S260. Obtain the historical login data of the browser in the user terminal.

[0076] Among them, the historical login data is used to record the historical information of the user logging in to the browser in the past. The historical login data may include, but is not limited to, user system login information. The historical login data may be the cookie of the browser.

[0077] S270. Perform single sign-on according to the historical login data and the updated login token.

[0078] It can be understood that since the relevant information during single sign-on can be correspondingly stored in the historical login data of the browser, the historical information of using the login token for single sign-on to the browser is also recorded. By verifying the login token in the historical login data, single sign-on to the browser is performed.

[0079] In an alternative embodiment, the single sign-on based on historical login data and the updated login token may include: controlling the acquisition of the updated login token stored locally for single sign-on according to the existence of the updated login token in the historical login data.

[0080] It can be understood that if the updated login token already exists in the historical login data, then the login token can be directly called for single sign-on; further, the controlling the acquisition of the updated login token stored locally for single sign-on according to the existence of the updated login token in the historical login data may include: if the updated login token is not included in the historical login data, then controlling the acquisition of the updated login token from the login control module for single sign-on. The advantage of this is that when logging in to the browser, there is no need to repeatedly obtain the login token from the server, and it can be directly called from the local, saving the process of repeated authentication, improving the usage efficiency of the browser, and enhancing the user experience.

[0081] The technical solution of the embodiment of the present application, for single sign-on based on historical login data and the updated login token, can verify the login token in the historical login data when logging in to the browser to check whether there is an available new login token. It can be understood that if the user switches to use a different browser, since the local system login control module can obtain the latest login token every time the system successfully logs in, even if the browser is changed, it is still possible to perform single sign-on by calling the login token stored in the local system login control module, saving the process of re-authentication.

[0082] Embodiment III

[0083] Figure 3 FIG. 3 is a flowchart of a lock screen login method provided for Embodiment III of the present application. This embodiment is applicable to the situation where single sign-on conditions are activated during system login. The method can be executed by a server, can be implemented by a lock screen login device, and the lock screen login device can be implemented in the form of hardware and / or software, and the lock screen login device can be configured in an electronic device. As Figure 3 shown, the method includes:

[0084] S310. Obtain the verification information sent by the system login control module and perform verification.

[0085] It can be understood that the server verifies the verification information sent by the system login control module of the user terminal.

[0086] S320. If the verification is passed, generate a login token according to the verification information and send the login token to the system login control module, so that the system login control module sends a system login verification request to the server according to the login token.

[0087] If the verification is passed, a login token for system login and single sign-on is generated by the system login control module, and the login token is sent to the system login control module of the user terminal.

[0088] S330: Generate user system login information according to the system login verification request, and send the user system login information to the system login control module, so that the system login control module performs the following operations: Compare the user system login information with the user information saved locally, and perform system login after successful comparison; After performing system login, save the login token to update the login token stored locally; Perform single sign-on according to the updated login token.

[0089] After obtaining the system login verification request, the server generates the corresponding user system login information and feeds it back to the system login control module to help the system login control module perform system login and single sign-on.

[0090] The technical solution of the embodiment of the present application obtains the login token for single sign-on while performing the system login of the user terminal, improves the separation of system login and single sign-on in the prior art to obtaining the single sign-on permission while performing system login, realizes the synchronization of system login and single sign-on, further improves the single sign-on efficiency of the user terminal, and improves the operation convenience of the user, thus enhancing the user experience.

[0091] Embodiment Four

[0092] Embodiment Four of the present application provides a preferred embodiment on the basis of the foregoing embodiments. This preferred embodiment can be applied to the situation of obtaining single sign-on permission while unlocking the screen of the user terminal. The specific preferred implementation includes:

[0093] Users can use various login methods (such as account password, QR code, fingerprint, etc.) to enable the login program (i.e., the system login control module) configured on the user terminal to obtain the account password (or other verification information) for the user's system login; the login program sends the obtained user system login information to the background authentication server (i.e., the server) for authentication; after receiving the verification information input by the user of the terminal, the background authentication server authenticates the information, and after successful authentication, it sends an authentication token to the login program of the user terminal; after the login program obtains the authentication token sent by the background authentication server, it submits the token information and the request for system login verification. The information is submitted to the authentication server to request the user system login information corresponding to the token; the authentication server receives the token and the request to obtain the user system login information, and returns the user system login information through the interface. The login program obtains the user login information returned by the authentication server and compares it with the user information saved locally. After successful comparison, the user of the user terminal is regarded as a legitimate user (i.e., having the right to unlock the system and perform single sign-on), and the successful login of the system lock screen desktop is achieved. After the system login is successful, the login program stores the token information in its storage module.

[0094] After the user realizes the lock screen login of the system, the user can perform single sign-on of the application according to the token obtained through the above process. Compared with the existing single sign-on solutions, since the token information is obtained from the server each time the desktop login program realizes system login, it is convenient to obtain the token locally in a timely manner after the policy changes or the token is lost, saving the process of re-obtaining the token from the authentication server as mentioned above. And through the above method, system login and single sign-on can be realized synchronously, improving the system security and the convenience of user operation.

[0095] Of course, when performing the first single sign-on of the application program, relevant authentication interfaces can be called to find cookies in the browser to confirm whether there is a token. If there is a token that can be used for single sign-on, it is considered that the login authentication is passed. The token information is compared and verified with the user information, and the relevant status of the browser is checked. If the status is normal, single sign-on can be performed in a timely manner. If there is no token for single sign-on in the browser's cookies, the login program is called to call the latest stored token from the local storage for browser login, which can save the process of repeatedly obtaining the token through the authentication server. Similarly, if the browser is replaced, the token can also be obtained in the above way to save the process of re-authenticating through the server.

[0096] In addition, it is inevitable that the token information stored in the cookie is not the latest token when verifying the cookie of the browser. During single sign-on, if the token information fails the comparison and verification with the user information (that is, there is no corresponding latest token for the user information), the latest token stored locally when the system logs in successfully is called, and then the comparison and verification can pass and the single sign-on of the browser can be performed.

[0097] In a specific embodiment, as Figure 4 shown, the personal computer (user terminal) requests a QR code from the authentication server, and scans the QR code through the personal mobile phone (equivalent to the verification process of the unlocking verification information). While the desktop is unlocked, the login token is written (locally stored to) the single-point control (equivalent to the system login control module), and the login token stored in the single-point control is obtained through the browser for single sign-on and access to the browser and application programs.

[0098] It should be added that the single-point control (i.e., the system login control module) can be configured in the user terminal as an independent application program. This application program can replace the built-in lock screen function of the user terminal to implement system login authentication, and realize multi-factor login authentication (such as digital certificate, dynamic password, face recognition, and QR code, etc.) through linkage with the authentication server. This application program can also obtain the latest user authentication token from the authentication server and save it locally every time the user unlocks the system, and use this latest authentication token to realize cross-browser application single sign-on.

[0099] Embodiment 5

[0100] Figure 5 This is a schematic structural diagram of a lock screen login device provided by Embodiment 5 of the present application. This device is configured at one end of the system login control module of the user terminal. As Figure 5 shown, this device 500 includes:

[0101] A verification information acquisition module 510, configured to acquire verification information collected by the user terminal;

[0102] A login token acquisition module 520, configured to send the verification information to the server for verification, and if the verification passes, acquire the login token from the server according to the verification information;

[0103] A login request sending module 530, configured to send a system login verification request to the server according to the login token to obtain user system login information;

[0104] A system login module 540, configured to compare the user system login information with the user information saved locally, and perform system login after successful comparison;

[0105] A login token update module 550, which is used to save the login token after system login to update the locally stored login token.

[0106] A single sign-on module 560, which is used to perform single sign-on according to the updated login token.

[0107] The technical solution of the embodiment of the present application obtains the login token used for single sign-on while performing the system login of the user terminal, improves the separation between system login and single sign-on in the prior art to obtain the single sign-on permission while performing the system login, realizes the synchronization of system login and single sign-on, further improves the single sign-on efficiency of the user terminal, and improves the operation convenience of the user, enhancing the user experience.

[0108] In an optional implementation manner, the system login control module is further used to prestorage user information, configure the registration information between the user account and the server, and construct the binding relationship between the system login control module and the user information.

[0109] In an optional implementation manner, the single sign-on module 560 may include:

[0110] A historical data acquisition unit, which is used to acquire the historical login data of the browser in the user terminal;

[0111] A single sign-on unit, which is used to perform single sign-on according to the historical login data and the updated login token.

[0112] In an optional implementation manner, the single sign-on unit may include:

[0113] A login subunit, which is used to control the acquisition of the updated login token stored locally for single sign-on according to the existence of the updated login token in the historical login data.

[0114] In an optional implementation manner, the login subunit may specifically be used to: if the updated login token is not included in the historical login data, control to obtain the updated login token from the login control module for single sign-on.

[0115] In an optional implementation manner, the device 500 may further include:

[0116] A periodic storage module, which is used to store the updated login token to the browser at a preset period.

[0117] In an optional implementation manner, the device 500 may further include:

[0118] A synchronous storage module, which is used to update the login token stored locally and store the updated login token in the browser at the same time.

[0119] The lock screen login device provided by the embodiments of the present application can execute the lock screen login method provided by any embodiment of the present application, and has the corresponding functional modules and beneficial effects for executing each lock screen login method.

[0120] Embodiment Six

[0121] Figure 6 It is a structural schematic diagram of a lock screen login device provided by Embodiment Six of the present application. This device is configured on the server side. As Figure 6 described, this device 600 includes:

[0122] An information verification module 610, which is used to obtain the verification information sent by the system login control module and verify it;

[0123] A login token generation module 620, which is used to generate a login token according to the verification information if the verification is passed, and send the login token to the system login control module, so that the system login control module sends a system login verification request to the server side according to the login token;

[0124] A login information generation module 630, which is used to generate user system login information according to the system login verification request, and send the user system login information to the system login control module, so that the system login control module performs the following operations: compare the user system login information with the user information saved locally, and perform system login after successful comparison; after performing system login, save the login token to update the login token stored locally; perform single sign-on according to the updated login token.

[0125] The technical solution of the embodiment of the present application obtains the login token used for single sign-on while performing the system login of the user terminal, improves the separation between system login and single sign-on in the prior art to obtaining the single sign-on permission while performing system login, realizes the synchronization of system login and single sign-on, further improves the single sign-on efficiency of the user terminal, and improves the operation convenience of the user, enhancing the user experience.

[0126] The lock screen login device provided by the embodiments of the present application can execute the lock screen login method provided by any embodiment of the present application, and has the corresponding functional modules and beneficial effects for executing each lock screen login method.

[0127] Embodiment Seven

[0128] Figure 7The structural schematic diagram of an electronic device 10 that can be used to implement the embodiments of the present application is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processors, cellular phones, smart phones, wearable devices (such as helmets, glasses, watches, etc.) and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the present application described and / or claimed herein.

[0129] As Figure 7 shown, the electronic device 10 includes at least one processor 11 and a memory communicatively connected to the at least one processor 11, such as a read-only memory (ROM) 12, a random access memory (RAM) 13, etc. The memory stores a computer program executable by the at least one processor. The processor 11 can perform various appropriate actions and processes according to the computer program stored in the read-only memory (ROM) 12 or the computer program loaded from the storage unit 18 into the random access memory (RAM) 13. Various programs and data required for the operation of the electronic device 10 can also be stored in the RAM 13. The processor 11, the ROM 12, and the RAM 13 are connected to each other via a bus 14. An input / output (I / O) interface 15 is also connected to the bus 14.

[0130] A plurality of components in the electronic device 10 are connected to the I / O interface 15, including: an input unit 16, such as a keyboard, a mouse, etc.; an output unit 17, such as various types of displays, speakers, etc.; a storage unit 18, such as a magnetic disk, an optical disk, etc.; and a communication unit 19, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 19 allows the electronic device 10 to exchange information / data with other devices via a computer network such as the Internet and / or various telecommunication networks.

[0131] The processor 11 can be various general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of the processor 11 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various dedicated artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any appropriate processor, controller, microcontroller, etc. The processor 11 executes the various methods and processes described above, such as the foregoing lock screen login methods.

[0132] In some embodiments, each of the foregoing lock screen login methods may be implemented as a computer program tangibly embodied in a computer-readable storage medium, such as storage unit 18. In some embodiments, part or all of the computer program may be loaded and / or installed onto the electronic device 10 via the ROM 12 and / or the communication unit 19. When the computer program is loaded into the RAM 13 and executed by the processor 11, one or more steps of the lock screen login methods described above may be performed. Alternatively, in other embodiments, the processor 11 may be configured to perform the lock screen login methods described above in any other suitable manner (e.g., by means of firmware).

[0133] The various embodiments of the systems and techniques described above in this document may be implemented in digital electronic circuitry, integrated circuit systems, field programmable gate arrays (FPGA), application specific integrated circuits (ASIC), application specific standard products (ASSP), systems on a chip (SOC), complex programmable logic devices (CPLD), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include: being implemented in one or more computer programs that may be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a special-purpose or general-purpose programmable processor that receives data and instructions from a storage system, at least one input device, and at least one output device, and transmits the data and instructions to the storage system, the at least one input device, and the at least one output device.

[0134] The computer programs for implementing the methods of the present application may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, such that when the computer programs are executed by the processor, the functions / operations specified in the flowchart and / or block diagram are implemented. The computer programs may be executed entirely on the machine, partially on the machine, as a stand-alone software package partially on the machine and partially on a remote machine, or entirely on a remote machine or server.

[0135] In the context of this application, a computer-readable storage medium can be a tangible medium that can contain or store a computer program for use by or in connection with an instruction execution system, apparatus, or device. The computer-readable storage medium can include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. Alternatively, the computer-readable storage medium can be a machine-readable signal medium. More specific examples of the machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0136] To provide for interaction with a user, the systems and techniques described herein can be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and a pointing device (e.g., a mouse or a trackball) by which the user can provide input to the electronic device. Other kinds of devices can also be used to provide for interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including acoustic input, speech input, or tactile input).

[0137] The systems and techniques described herein can be implemented in a computing system that includes backend components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes frontend components (e.g., a user computer having a graphical user interface or a web browser through which the user can interact with an implementation of the systems and techniques described herein), or a computing system that includes any combination of such backend components, middleware components, or frontend components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: a local area network (LAN), a wide area network (WAN), a blockchain network, and the Internet.

[0138] A computing system may include a client and a server. The client and the server are generally far from each other and usually interact via a communication network. The client-server relationship is created by computer programs running on respective computers and having a client-server relationship with each other. The server can be a cloud server, also known as a cloud computing server or a cloud host, which is a host product in the cloud computing service system, solving the defects of difficult management and weak business scalability existing in traditional physical hosts and VPS services.

[0139] It should be understood that various forms of the processes shown above can be used, steps can be reordered, added or deleted. For example, the steps recited in this application can be executed in parallel, sequentially or in a different order, as long as the desired results of the technical solution of this application can be achieved, and no limitation is imposed herein.

[0140] The above specific embodiments do not constitute a limitation on the protection scope of this application. Those skilled in the art should understand that various modifications, combinations, sub-combinations and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principle of this application shall be included within the protection scope of this application.

Claims

1. A lock screen login method, characterized in that, Executed by a system login control module configured in a user terminal, the method includes: Obtain the verification information collected by the user terminal; Send the verification information to the server for verification, and if the verification is passed, obtain a login token from the server according to the verification information; Send a system login verification request to the server according to the login token to obtain user system login information; Compare the user system login information with the user information saved locally, and perform system login after successful comparison; After performing the system login, save the login token to update the login token stored locally; Perform single sign-on according to the updated login token; The performing single sign-on according to the updated login token includes: Obtain the historical login data of the browser in the user terminal; wherein, relevant information for single sign-on is stored correspondingly in the historical login data; Perform single sign-on according to the historical login data and the updated login token; The system login control module is further used to pre-store the user information, configure the registration information between the user account and the server, and construct the binding relationship between the system login control module and the user information; wherein, the login behavior of the user is verified according to the binding relationship to verify whether the user is a user candidate allowed to log in by the system. When the user locks the screen after using the terminal, the next system unlocking will also verify whether the user is the one allowed to log in in the previous or historical records.

2. The method according to claim 1, characterized in that The performing single sign-on according to the historical login data and the updated login token includes: Control to obtain the updated login token stored locally for single sign-on according to the existence of the updated login token in the historical login data.

3. The method according to claim 2, wherein The controlling to obtain the updated login token stored locally for single sign-on according to the existence of the updated login token in the historical login data includes: If the updated login token is not included in the historical login data, control to obtain the updated login token from the login control module for single sign-on.

4. The method according to any one of claims 1 to 3, characterized in that, The method further includes: Store the updated login token in the browser at a preset period.

5. The method according to any one of claims 1 to 3, characterized in that, The method further includes: While updating the login token stored locally, store the updated login token in the browser.

6. A lock screen login method, characterized in that, Applied to the server, the method includes: Obtain the verification information sent by the system login control module and perform verification; If the verification is passed, generate a login token according to the verification information and send the login token to the system login control module, so that the system login control module sends a system login verification request to the server according to the login token; Generate user system login information according to the system login verification request, and send the user system login information to the system login control module so that the system login control module performs the following operations: compare the user system login information with the user information saved locally, and perform system login after successful comparison; after performing system login, save the login token to update the login token stored locally; perform single sign-on according to the updated login token. The performing single sign-on according to the updated login token includes: Obtain the historical login data of the browser in the user terminal; wherein, relevant information during single sign-on is stored correspondingly in the historical login data. Perform single sign-on according to the historical login data and the updated login token. The system login control module is further configured to pre-store user information, configure registration information between the user account and the server, and establish a binding relationship between the system login control module and the user information; wherein, the login behavior of the user is verified according to the binding relationship to verify whether the user is a candidate allowed to log in by the system. When the user locks the screen after using the terminal, the next system unlocking will also verify whether the user is the one allowed to log in in the previous or historical records.

7. An electronic device, characterized in that, The electronic device includes: At least one processor; and A memory communicatively connected to the at least one processor; wherein, The memory stores a computer program executable by the at least one processor. The computer program is executed by the at least one processor so that the at least one processor can execute the lock screen login method according to any one of claims 1-5, and / or execute the lock screen login method according to claim 6.

8. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions for causing a processor to implement the lock screen login method according to any one of claims 1-5 when executed, and / or execute the lock screen login method according to claim 6.

Images