User login processing method and device, computer equipment, readable storage medium and program product

Abstract

The invention relates to a user login processing method and device, computer equipment, a computer readable storage medium and a computer program product. The method comprises the following steps: acquiring a login user name input by a user on a preset login interface; querying a necessary information historical confirmation state corresponding to the login user name from a local storage to obtain a query result; when the query result is that the query is successful, displaying a first target state in a preset login interface; the first target state is a state for identifying that the user has checked and confirms necessary information; when the query result is that the query fails, displaying a second target state in the preset login interface; the second target state is a state for identifying that the user does not check and confirm necessary information; and when the user clicks a login key in the preset login interface, executing user login processing corresponding to the first target state or the second target state displayed in the preset login interface. By adopting the method, the user login efficiency can be improved.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a user login processing method, apparatus, computer equipment, computer-readable storage medium, and computer program product. Background Art

[0002] In modern Internet applications, user login verification is an important part of ensuring system security and legal use. Usually, users need to manually confirm the license agreement and privacy policy before logging in.

[0003] However, the existing login process has certain limitations, especially when the user logs in multiple times. It is currently impossible to automatically determine whether the user has confirmed the necessary information, resulting in the user needing to repeat the confirmation operation, which makes the user login efficiency poor. Summary of the invention

[0004] Based on this, it is necessary to provide a user login processing method, device, computer equipment, computer-readable storage medium and computer program product that can improve user login efficiency in response to the above technical problems.

[0005] In a first aspect, the present application provides a user login processing method, comprising:

[0006] Get the login username entered by the user on the preset login interface;

[0007] Query the necessary information history confirmation status corresponding to the login user name from the local storage to obtain the query result;

[0008] When the query result is successful, a first target state is displayed in the preset login interface; the first target state is a state indicating that the user has viewed and confirmed the necessary information;

[0009] In the case where the query result is a query failure, a second target state is displayed in the preset login interface; the second target state is a state indicating that the user has not viewed and confirmed the necessary information;

[0010] When the user clicks a login button in the preset login interface, a user login process corresponding to the first target state or the second target state displayed in the preset login interface is executed.

[0011] In one embodiment, when the user clicks a login button in the preset login interface, executing a user login process corresponding to the first target state or the second target state displayed in the preset login interface includes:

[0012] Initiate a user login verification operation when the display status in the preset login interface is the first target status;

[0013] When the display state in the preset login interface is the second target state, a viewing confirmation prompt message is displayed to prompt the user to view and confirm necessary information.

[0014] In one of the embodiments, after displaying the second target state in the preset login interface, the method further includes:

[0015] In response to the user's viewing and confirming operation on the necessary information, the second target state displayed in the preset login interface is switched to the first target state.

[0016] In one embodiment, after the initiating user login verification operation, the method further includes:

[0017] When the user's login verification is passed, the necessary information history confirmation status corresponding to the login user name is recorded in the local storage.

[0018] In one embodiment, obtaining a login user name input by a user in a preset login interface includes:

[0019] When the user inputs information in the login user name input box of the preset login interface and clicks an area other than the login user name input box, acquiring the information input in the login user name input box;

[0020] The information input in the login user name input box is determined as the login user name.

[0021] In one embodiment, after obtaining the login username input by the user in the preset login interface, the method further includes:

[0022] Detecting the number of times the preset login interface is displayed and obtaining a detection result;

[0023] In the case where the detection result is displayed for the first time, a preset necessary information viewing page is displayed, and the query result is determined to be a query failure;

[0024] The querying of the necessary information history confirmation status corresponding to the login user name from the local storage to obtain the query result includes:

[0025] When the detection result is not displayed for the first time, the necessary information history confirmation status corresponding to the login user name is queried from the local storage to obtain the query result.

[0026] In a second aspect, the present application also provides a user login processing device, comprising:

[0027] The information acquisition module is used to obtain the login username entered by the user in the preset login interface;

[0028] A status query module, used to query the necessary information history confirmation status corresponding to the login user name from the local storage to obtain the query result;

[0029] A first display module, used to display a first target state in the preset login interface when the query result is a successful query; the first target state is a state indicating that the user has viewed and confirmed the necessary information;

[0030] A second display module is used to display a second target state in the preset login interface when the query result is a query failure; the second target state is a state indicating that the user has not viewed and confirmed the necessary information;

[0031] A login processing module is used to execute user login processing corresponding to the first target state or the second target state displayed in the preset login interface when the user clicks the login button in the preset login interface.

[0032] In a third aspect, the present application further provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the following steps are implemented:

[0033] Get the login username entered by the user on the preset login interface;

[0034] Query the necessary information history confirmation status corresponding to the login user name from the local storage to obtain the query result;

[0035] When the query result is successful, a first target state is displayed in the preset login interface; the first target state is a state indicating that the user has viewed and confirmed the necessary information;

[0036] In the case where the query result is a query failure, a second target state is displayed in the preset login interface; the second target state is a state indicating that the user has not viewed and confirmed the necessary information;

[0037] When the user clicks a login button in the preset login interface, a user login process corresponding to the first target state or the second target state displayed in the preset login interface is executed.

[0038] In a fourth aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, wherein when the computer program is executed by a processor, the following steps are implemented:

[0039] Get the login username entered by the user on the preset login interface;

[0040] Query the necessary information history confirmation status corresponding to the login user name from the local storage to obtain the query result;

[0041] When the query result is successful, a first target state is displayed in the preset login interface; the first target state is a state indicating that the user has viewed and confirmed the necessary information;

[0042] In the case where the query result is a query failure, a second target state is displayed in the preset login interface; the second target state is a state indicating that the user has not viewed and confirmed the necessary information;

[0043] When the user clicks a login button in the preset login interface, a user login process corresponding to the first target state or the second target state displayed in the preset login interface is executed.

[0044] In a fifth aspect, the present application further provides a computer program product, including a computer program, which implements the following steps when executed by a processor:

[0045] Get the login username entered by the user on the preset login interface;

[0046] Query the necessary information history confirmation status corresponding to the login user name from the local storage to obtain the query result;

[0047] When the query result is successful, a first target state is displayed in the preset login interface; the first target state is a state indicating that the user has viewed and confirmed the necessary information;

[0048] In the case where the query result is a query failure, a second target state is displayed in the preset login interface; the second target state is a state indicating that the user has not viewed and confirmed the necessary information;

[0049] When the user clicks a login button in the preset login interface, a user login process corresponding to the first target state or the second target state displayed in the preset login interface is executed.

[0050] The above-mentioned user login processing method, device, computer equipment, computer-readable storage medium and computer program product first obtain the login user name entered by the user in the preset login interface, and by instantly capturing the user input, can quickly identify the specific user who has logged in, ensure that subsequent login processing is performed for the individual user, improve the efficiency of user data processing, and avoid unnecessary interactive processes; then, query the historical confirmation status of the necessary information corresponding to the login user name from the local storage to obtain the query result, and through the browser local storage technology, there is no need to frequently rely on server requests, and the user's license agreement confirmation status can be efficiently queried, thereby improving the processing capability in disconnected or low-latency scenarios, avoiding resource consumption and system load problems caused by frequent network requests, and ensuring the immediacy of operations; then, when the query result is a successful query, the first target state is displayed in the preset login interface; The first target state is a state that indicates that the user has viewed and confirmed the necessary information, and the state that the user has confirmed the necessary information is automatically displayed, so that the user avoids repeated confirmation operations, thereby improving the user's login efficiency; when the query result is a query failure, the second target state is displayed in the preset login interface; the second target state is a state that indicates that the user has not viewed and confirmed the necessary information. When the query fails, the information that the user has not confirmed the license agreement is fed back in real time to ensure that the user completes the necessary operations before logging in, thereby improving the security and compliance of the login process; finally, when the user clicks the login button in the preset login interface, the user login process corresponding to the first target state or the second target state displayed in the preset login interface is executed, and the login process is automatically performed according to the user's current confirmation state. Regardless of the user's confirmation state, the user can be smoothly guided to perform the corresponding operation, thereby improving the flexibility and efficiency of the login process. In the above method, the user experience problems caused by repeated operations are avoided through the localized confirmation mechanism, the user's login efficiency is improved, and timely feedback is given when the user has not confirmed the information, thereby effectively ensuring the compliance of the user's behavior. In addition, the use of local storage technology allows the user's historical confirmation state to be quickly identified without server support, thereby reducing the system's dependence on external resources and improving login efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0051] In order to more clearly illustrate the technical solutions in the embodiments of the present application or related technologies, the drawings required for use in the embodiments of the present application or related technical descriptions will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

[0052] FIG1 is a schematic diagram of a flow chart of a method for processing user login in one embodiment;

[0053] FIG2 is a schematic diagram of a flow chart of executing the login processing steps in one embodiment;

[0054] FIG3 is a schematic diagram of a flow chart of a method for processing user login in one embodiment;

[0055] FIG4 is a schematic diagram of a flow chart of a user login processing method in another embodiment;

[0056] FIG5 is a structural block diagram of a user login processing device in one embodiment;

[0057] FIG. 6 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0058] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0059] In one embodiment, as shown in FIG1 , a user login processing method is provided. This embodiment uses the method applied to a terminal as an example for illustration. It is understandable that the method can also be applied to a system including a terminal and a server, and is implemented through the interaction between the terminal and the server. The terminal can be, but is not limited to, various personal computers, laptops, smart phones, and tablet computers. The server can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides cloud computing services. In this embodiment, the method includes the following steps:

[0060] Step S101, obtaining the login user name input by the user in the preset login interface.

[0061] The login username is a unique character or string used by a user to identify himself or herself, usually composed of letters, numbers, and special symbols, and is used to distinguish different users.

[0062] Exemplarily, the terminal obtains the login username by monitoring the user's input behavior on the login interface. When the user types in the username input box on the login interface, the terminal detects the change event of the input box and obtains the user input data through the event monitoring mechanism. When the user completes the input or leaves the input box, the terminal saves the captured input information (i.e., the username) in a local variable as the basic data for the subsequent login verification process. In addition, the terminal can also be combined with other verification mechanisms, such as preliminary verification through the user's input behavior characteristics or preset username format standards (such as length, character type) to ensure that the username format meets the requirements. If the username input does not meet the format requirements, the terminal can prompt the user to modify it in real time to improve the login success rate and user experience.

[0063] Step S102, query the necessary information history confirmation status corresponding to the login user name from the local storage to obtain the query result.

[0064] Among them, local storage refers to the local storage provided by the login system (for example, if the login system is a web page, it can be localStorage), which is used to save user data on the client side and allows the data to be saved after the user closes the browser or session. The necessary information history confirmation status refers to the status record of whether the user has confirmed the license agreement or privacy policy required for login.

[0065] Exemplarily, the terminal uses the login user name as a key to query the historical data stored in the local storage. If the necessary information confirmation status corresponding to the user name is found, the status is returned as the query result. If there is no corresponding record, the query failure or default status is returned, indicating that the user has not confirmed the relevant necessary information. When the terminal performs this operation, it does not need to send a request to the server, so it can quickly complete the status check locally and improve the response speed of the system. In addition, the terminal can not only query a single data item in the local storage, but also query multiple related data (such as the last login time, login device, etc.) as needed, so as to set the query expiration time or clearing mechanism to ensure that the stored data is always up to date and meets the current privacy and security standards.

[0066] Step S103, when the query result is successful, the first target state is displayed in the preset login interface.

[0067] The first target state is a state indicating that the user has viewed and confirmed the necessary information. Specifically, when the user has confirmed the necessary information (such as a license agreement or privacy policy), the status indicator displayed on the login interface usually uses visual prompts (such as automatic checkboxes, green signs, prompt text, etc.) to indicate that the user has viewed and confirmed the relevant information.

[0068] For example, when the terminal confirms that the query result is successful, it will automatically update the corresponding elements in the login interface, such as setting the checkbox of "Agree to the License Agreement" or "Agree to the Privacy Policy" to a checked state, or displaying a prompt message in the interface, such as "You have confirmed the necessary information." Displaying the first target state can not only improve the user experience, but also reduce unnecessary repeated operations of users.

[0069] Step S104: when the query result is a query failure, the second target state is displayed in the preset login interface.

[0070] The second target state is a state indicating that the user has not reviewed and confirmed the necessary information. Specifically, when the user has not reviewed or confirmed the necessary information (such as the license agreement or privacy policy), the status indicator displayed in the login interface usually indicates that the user has not completed the necessary confirmation operation in the form of a visual reminder (such as an unchecked checkbox, a red warning prompt, a pop-up window, etc.).

[0071] For example, when the query result is a failure, the terminal automatically adjusts the UI elements of the login interface, such as ensuring that the checkboxes for "Agree to the License Agreement" or "Agree to the Privacy Policy" are not checked, or displaying a striking prompt message below the login button, such as "Please confirm and agree to the necessary information before continuing to log in." Ensure that the user clearly knows that a confirmation operation is required to meet the prerequisites for login.

[0072] Step S105, when the user clicks the login button in the preset login interface, the user login process corresponding to the first target state or the second target state displayed in the preset login interface is executed.

[0073] Exemplarily, after the user clicks the login button, the terminal will first determine whether the target state displayed in the current interface is the first target state (the user has confirmed the necessary information) or the second target state (the user has not confirmed the necessary information). If the interface displays the first target state, the terminal will execute the standard user login process, which usually includes sending the user name and password to the server for verification, using Ajax requests or API calls to interact with the background system to verify the validity of the user credentials. If the interface displays the second target state, the terminal will not directly initiate a login request, but will display a reminder message to the user, requiring him to confirm the necessary information first, such as agreeing to the license agreement or privacy policy. At this time, the terminal can prevent the login process from continuing until the user completes the necessary confirmation operations.

[0074] In the above user login processing method, first, the login username entered by the user in the preset login interface is obtained. By instantly capturing the user input, the specific user who logs in can be quickly identified, ensuring that subsequent login processing is performed for the individual user, improving the efficiency of user data processing, and avoiding unnecessary interactive processes; then, the necessary information history confirmation status corresponding to the login username is queried from the local storage to obtain the query result. Through the browser local storage technology, there is no need to frequently rely on server requests, and the user's license agreement confirmation status can be efficiently queried, which improves the processing capability in disconnected or low-latency scenarios, avoids resource consumption and system load problems caused by frequent network requests, and ensures the immediacy of operations; then, when the query result is a successful query, the first target status is displayed in the preset login interface; the first target status is to indicate that the user has viewed And confirm the status of the necessary information, automatically display the status of the user confirming the necessary information, so that the user avoids repeated confirmation operations, and improves the user's login efficiency; when the query result is a query failure, the second target state is displayed in the preset login interface; the second target state is a state that indicates that the user has not viewed and confirmed the necessary information. When the query fails, the information that the user has not confirmed the license agreement is fed back in real time to ensure that the user completes the necessary operations before logging in, which improves the security and compliance of the login process; finally, when the user clicks the login button in the preset login interface, the user login process corresponding to the first target state or the second target state displayed in the preset login interface is executed, and the login process is automatically performed according to the user's current confirmation state. Regardless of the user's confirmation state, the user can be smoothly guided to perform the corresponding operation, which improves the flexibility and efficiency of the login process. In the above method, the user experience problems caused by repeated operations are avoided through the localized confirmation mechanism, the user's login efficiency is improved, and timely feedback is given when the user does not confirm the information, which effectively guarantees the compliance of the user's behavior. In addition, the use of local storage technology allows the user's historical confirmation state to be quickly identified without server support, reducing the system's dependence on external resources and improving login efficiency.

[0075] In an exemplary embodiment, as shown in FIG. 2 , the above step S105 performs a user login process corresponding to the first target state or the second target state displayed in the preset login interface when the user clicks the login button in the preset login interface, and can also be implemented by the following steps:

[0076] Step S201, when the display status in the preset login interface is the first target status, initiating a user login verification operation;

[0077] Step S202: When the display state in the preset login interface is the second target state, display a check confirmation prompt message to prompt the user to check and confirm necessary information.

[0078] Among them, the user login verification operation refers to the standard login process triggered after the user has confirmed the necessary information.

[0079] Exemplarily, the terminal collects the user's input information (such as username and password) and initiates a verification request to the server, usually using the HTTPS protocol to communicate with the server in an encrypted manner to ensure the security of the user's credentials and information transmission. The terminal can send the user's credentials to the back-end system through Ajax, API calls, etc. The back-end system confirms the user's login validity through database comparison and security verification, and returns the login result. When the terminal detects that the user has not confirmed the relevant information, a prompt box will pop up or a red warning message will be displayed in the interface, informing the user that the relevant agreement needs to be checked before continuing. The terminal can dynamically generate prompt content. For example, in a web login system, JavaScript can be used to update UI elements, such as pop-up boxes or warning text, to prompt users to click the corresponding checkbox or link to view and confirm detailed information. Ensure that users do not skip the required confirmation steps and effectively improve system compliance.

[0080] In this embodiment, flexible login process management is achieved through processing logic for different target states. When the user has confirmed the necessary information, the standard login verification process is quickly initiated to improve operational efficiency; and when the user has not confirmed, the user can be reminded to complete the confirmation operation in time to avoid possible legal risks or compliance issues. This ensures the smoothness of the user experience and effectively guarantees the safety and legality of the operation.

[0081] In an exemplary embodiment, after the second target state is displayed in the preset login interface in the above step S104, it also includes: in response to the user's viewing and confirmation operation for necessary information, the second target state displayed in the preset login interface is switched to the first target state.

[0082] The review and confirmation operation refers to the user actively reviewing necessary information such as the license agreement and privacy policy, and expressing his or her consent by checking a checkbox or clicking an agree button.

[0083] Exemplarily, the terminal determines whether the user has completed the review and confirmation operation by monitoring the user's interactive actions in the license agreement confirmation area (such as clicking to check a checkbox or a confirmation button). At this time, the terminal can monitor the user's click events, for example, by capturing the user's operations through the addEventListener function. When the terminal confirms that the user has completed the review and confirmation of the necessary information, the terminal automatically switches the second target state (indicating that the user has not confirmed the information) to the first target state (indicating that the user has confirmed the information). It is usually manifested as a change in interface elements, such as automatically marking a checkbox as checked, or removing a red warning prompt. Update the prompt information that may exist in the interface to inform the user that the necessary operation has been successfully completed. Ensure that after the user completes the review and confirmation operation, the status of the login interface can promptly reflect this change, thereby providing a basis for subsequent login operations.

[0084] In this embodiment, the dynamic adjustment of the login process is achieved by automatically switching the target state after the user confirms the necessary information. The user does not need to reload the page or perform additional operations, and the change of the confirmation state can be reflected in real time. This not only simplifies user operations and improves the user experience, but also ensures accurate tracking and management of user behavior, effectively avoiding repeated confirmation or incomplete confirmation.

[0085] In an exemplary embodiment, after the user login verification operation is initiated in the above step S201, the method further includes: if the user login verification is passed, recording the historical confirmation status of the necessary information corresponding to the login user name in the local storage.

[0086] Exemplarily, after receiving the verification result returned by the server, the terminal starts the subsequent operation process, including recording the necessary information confirmation status of the user to local storage. The purpose of recording the historical confirmation status of necessary information is to ensure that when the user logs in again in the future, it can quickly obtain whether the user has confirmed the relevant information to avoid repeated confirmation steps. In addition, the terminal can also record more user information, such as confirmation date, protocol version, etc., to ensure that the user's confirmation version and time can be accurately distinguished when the protocol is updated in the future, so as to prompt the user to reconfirm according to different situations.

[0087] In this embodiment, after the user login verification is successful, the necessary information confirmation status is recorded in the local storage, thereby optimizing and automating the user login process. This can reduce unnecessary repeated confirmations, improve user experience, and simplify the management process of user confirmation records, ensuring smooth and efficient login.

[0088] In an exemplary embodiment, the above-mentioned step S101 obtains the login username entered by the user in the preset login interface, and also includes: when the user enters information in the login username input box of the preset login interface and clicks an area other than the login username input box, obtaining the information entered in the login username input box; and determining the information entered in the login username input box as the login username.

[0089] Exemplarily, the terminal monitors whether the user has completed the input in the input box and clicked other areas through an event monitoring mechanism. When the user clicks an area outside the input box, it means that he has completed the input of the user name, and the terminal will automatically capture the input information and use it as the user name. In this process, the terminal can also add input verification logic to check whether the format of the user name meets the predetermined requirements (such as character length, alphanumeric combination, etc.). If the input is valid, the information is determined as the official login user name.

[0090] In this embodiment, by automatically obtaining and determining the login username input by the user, it is ensured that the username input by the user is automatically captured after the input is completed, and there is no need for the user to actively submit the information. This can efficiently and accurately capture the key information input by the user, reduce the complexity of user operations, and improve the response speed and user experience, ensuring the real-time and accuracy of the user input.

[0091] In an exemplary embodiment, after obtaining the login username entered by the user on the preset login interface in the above step S101, the method further includes: detecting the number of times the preset login interface is displayed to obtain a detection result; if the detection result is the first display, displaying the preset necessary information viewing page, and determining that the query result is a query failure;

[0092] The above step S102 queries the historical confirmation status of the necessary information corresponding to the login user name from the local storage to obtain the query result, and also includes: when the detection result is not displayed for the first time, querying the historical confirmation status of the necessary information corresponding to the login user name from the local storage to obtain the query result.

[0093] The number of impressions refers to the number of times a user visits the login interface. The number of impressions is used to determine whether the user is visiting for the first time.

[0094] Exemplarily, the terminal can record whether the user has visited the login page before through local storage or browser session storage. For example, on the login system of the web page, the terminal can check whether there is a record through the localStorage.getItem('loginPageShown') method each time the login username is obtained. If it is detected that the login page is displayed for the first time, the terminal displays the necessary information page that the user needs to view (such as a license agreement or privacy policy), and sets the query result to a query failure, indicating that the user has not yet confirmed this information. If the detection result shows that the login interface is not displayed for the first time, the terminal directly skips the necessary information viewing page and performs a query operation to confirm whether the current user has viewed and confirmed the necessary information.

[0095] In this embodiment, by combining the detection of the number of displays and the query of the login status, it is possible to dynamically determine whether the necessary information page needs to be displayed, thereby avoiding the situation where the user is repeatedly prompted to confirm the information. The user experience is optimized, so that the user can be forced to confirm the necessary information during the first display, and the historical records can be quickly queried during subsequent displays, providing a more flexible and efficient login experience.

[0096] In an exemplary embodiment, in an exemplary embodiment, before the above step S101 obtains the login username entered by the user in the preset login interface, it also includes: when it is found that necessary information needs to be updated, the necessary information is updated, and the necessary information historical confirmation status corresponding to all login usernames in the local storage is cleared.

[0097] Exemplarily, each time the terminal loads the login interface, the terminal checks whether the currently stored version of the necessary information is consistent with the version on the server through an API or server request. If it is found that the necessary information has been updated, the terminal will record the new necessary information and notify the user. When it is found that the necessary information needs to be updated, the terminal will also automatically replace the old version information in the local storage with the latest version, and a page or prompt may pop up, asking the user to review and confirm the updated information. Since the necessary information has been updated, the previous confirmation status may no longer apply. The terminal clears all records related to the user's confirmation status in the local storage to ensure that the user must reconfirm the new necessary information when logging in again.

[0098] In this embodiment, by automatically clearing the historical confirmation status when necessary information is updated, it can effectively ensure that the content confirmed by the user is always up to date and valid, which not only ensures the timely updating of information and the user's right to know, but also reduces possible compliance risks and provides a safer and more transparent user experience.

[0099] In an exemplary embodiment, as shown in FIG3 , the present application provides a user login processing method, the method comprising:

[0100] Step S301, when it is found that necessary information needs to be updated, the necessary information is updated, and the necessary information history confirmation status corresponding to all login user names in the local storage is cleared.

[0101] Step S302: when the user inputs information in the login user name input box of the preset login interface and clicks an area other than the login user name input box, the information input in the login user name input box is obtained.

[0102] Step S303: determine the information input in the login user name input box as the login user name.

[0103] Step S304, detecting the number of times the preset login interface is displayed, and obtaining a detection result.

[0104] Step S305: When the detection result is displayed for the first time, a preset necessary information viewing page is displayed, and the query result is determined to be a query failure.

[0105] Step S306, when the detection result is not displayed for the first time, query the historical confirmation status of the necessary information corresponding to the login user name from the local storage to obtain the query result.

[0106] Step S307: When the query result is a query failure, the second target status is displayed in the preset login interface.

[0107] The second target state is a state indicating that the user has not viewed and confirmed the necessary information.

[0108] Step S308, in response to the user's viewing and confirming operation on necessary information, the second target state displayed in the preset login interface is switched to the first target state.

[0109] The first target state is a state indicating that the user has viewed and confirmed the necessary information.

[0110] Step S309: When the query result is successful, the first target state is displayed in the preset login interface.

[0111] Step S310, when the display state in the preset login interface is the second target state, display the view confirmation prompt information to prompt the user to view and confirm the necessary information.

[0112] Step S311, when the display status in the preset login interface is the first target status, a user login verification operation is initiated.

[0113] Step S312: When the user's login verification is passed, the necessary information history confirmation status corresponding to the login user name is recorded in the local storage.

[0114] In this embodiment, the user experience and system security are effectively improved through the systematic user login processing flow. First, by detecting the update of necessary information, it is ensured that users always view and confirm the latest license agreement or privacy policy to avoid legal or usage risks caused by outdated information. Secondly, by recording the number of times the user login interface is displayed, the first login and subsequent logins are automatically distinguished, which simplifies repeated confirmation operations and reduces the redundancy of user operations. In addition, the user's necessary information confirmation status can be dynamically detected and updated to ensure that before each login, it can accurately assess whether the user has confirmed the necessary information, thereby ensuring the compliance and legality of the process. Finally, the access to user information is optimized through local storage technology, which improves the response speed and operation efficiency of subsequent logins.

[0115] In another exemplary embodiment, as shown in FIG4 , the present application provides a user login processing method, the method comprising:

[0116] Step S401: The user inputs a user name.

[0117] Step S402, check whether the user name is recorded as a checked user; if so, execute step S403; if not, execute step S404.

[0118] Step S403, the login system automatically checks the necessary information.

[0119] Step S404: The user needs to manually select necessary information.

[0120] Step S405, check whether the necessary information has been checked; if so, execute step S406; if not, execute step S407.

[0121] Step S406, initiating a login request, and storing the association between the user name and the check status after successful login.

[0122] Step S407, prompting the user to check necessary information, and preventing the user from initiating login.

[0123] Exemplarily, when a user logs in to the system for the first time, there is no corresponding information of the user agreement being checked in the browser localstorage, so when the user clicks the login button, he will be prompted that the user agreement must be checked or he will not be able to log in; after the user checks the user agreement, a login request is sent to the back-end server to verify the login; if the login is successful, the web client uses the window.localStorage.setItem method of the localstorage technology to store the user information of the logged-in user in an object data structure, such as {name:user1, agree:true}, and stores the object information of the successfully logged-in user in the browser local storage; the user logs out of the system; the user enters a user name when it is not the first time to log in to the system; after entering the user name, when the user clicks anywhere else and loses focus on the user name input box, a blur event (out-of-focus event) is triggered to start checking the logic using the window.localStorage.getItem method to obtain the stored user information and compare it with the currently entered user name to determine whether the user automatically checks the user agreement; if it is consistent with the object information {name, agree} attributes stored in localstorage, the user agreement is automatically checked, indicating that the user agreement has been checked and agreed, and the prompt information is directly skipped to send the login request information through verification to enter the system.

[0124] In this embodiment, the user license agreement and privacy policy are guaranteed to accurately locate individual prompts for users who have not read or agreed to them, making the role of the user agreement and privacy policy adaptive and legal. The problem of being unable to verify whether the user agreement license agreement for a certain user has been confirmed before logging in is solved. The automatic selection of the user agreement based on the object record simplifies the steps of repeated manual selection and verification when logging in, making it convenient for confirmed users to directly enter the system. The implementation scheme achieves the effect of both convenience and legal security.

[0125] It should be understood that, although the various steps in the flowcharts involved in the above-mentioned embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps does not have a strict order restriction, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above-mentioned embodiments can include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.

[0126] Based on the same inventive concept, the embodiment of the present application also provides a user login processing device for implementing the user login processing method involved above. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme recorded in the above method, so the specific limitations in the one or more user login processing device embodiments provided below can refer to the limitations on the user login processing method above, and will not be repeated here.

[0127] In an exemplary embodiment, as shown in FIG5 , a user login processing device is provided, comprising: an information acquisition module 501, a state query module 502, a first display module 503, a second display module 504 and a login processing module 505, wherein:

[0128] The information acquisition module 501 is used to obtain the login username entered by the user in the preset login interface;

[0129] The status query module 502 is used to query the necessary information history confirmation status corresponding to the login user name from the local storage to obtain the query result;

[0130] The first display module 503 is used to display the first target state in the preset login interface when the query result is successful; the first target state is a state indicating that the user has viewed and confirmed the necessary information;

[0131] The second display module 504 is used to display the second target state in the preset login interface when the query result is a query failure; the second target state is a state indicating that the user has not viewed and confirmed the necessary information;

[0132] The login processing module 505 is used to execute the user login processing corresponding to the first target state or the second target state displayed in the preset login interface when the user clicks the login button in the preset login interface.

[0133] In one of the embodiments, the above-mentioned login processing module 505 is also used to initiate a user login verification operation when the display status in the preset login interface is a first target state; when the display status in the preset login interface is a second target state, display a view confirmation prompt message to prompt the user to view and confirm the necessary information.

[0134] In one of the embodiments, the user login processing device further includes a state updating module for switching the second target state displayed in the preset login interface to the first target state in response to the user's viewing and confirming operation on necessary information.

[0135] In one of the embodiments, the login processing module 505 is further configured to record the historical confirmation status of the necessary information corresponding to the login user name in the local storage when the user's login verification is passed.

[0136] In one of the embodiments, the above-mentioned information acquisition module 501 is also used to obtain the information entered in the login username input box when the user enters information in the login username input box of the preset login interface and clicks on an area other than the login username input box; and determine the information entered in the login username input box as the login username.

[0137] In one of the embodiments, the user login processing device is also used to detect the number of times a preset login interface is displayed to obtain a detection result; when the detection result is the first display, the preset necessary information viewing page is displayed, and the query result is determined to be a query failure.

[0138] In one of the embodiments, the above-mentioned status query module 502 is also used to query the historical confirmation status of the necessary information corresponding to the login user name from the local storage to obtain the query result when the detection result is not displayed for the first time.

[0139] Each module in the above user login processing device can be implemented in whole or in part by software, hardware, or a combination thereof. Each module can be embedded in or independent of a processor in a computer device in the form of hardware, or can be stored in a memory in a computer device in the form of software, so that the processor can call and execute operations corresponding to each module.

[0140] In an exemplary embodiment, a computer device is provided, which may be a terminal, and its internal structure diagram may be shown in FIG6. The computer device includes a processor, a memory, an input / output interface, a communication interface, a display unit, and an input device. The processor, the memory, and the input / output interface are connected via a system bus, and the communication interface, the display unit, and the input device are connected to the system bus via the input / output interface. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The input / output interface of the computer device is used to exchange information between the processor and an external device. The communication interface of the computer device is used to communicate with an external terminal in a wired or wireless manner, and the wireless manner may be implemented through WIFI, a mobile cellular network, near field communication (NFC) or other technologies. When the computer program is executed by the processor, a user login processing method is implemented. The display unit of the computer device is used to form a visually visible picture, which may be a display screen, a projection device, or a virtual reality imaging device. The display screen can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer device can be a touch layer covering the display screen, or a button, trackball or touchpad set on the computer device shell, or an external keyboard, touchpad or mouse.

[0141] Those skilled in the art will understand that the structure shown in FIG. 6 is merely a block diagram of a partial structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than shown in the figure, or combine certain components, or have a different arrangement of components.

[0142] In one embodiment, a computer device is further provided, including a memory and a processor, wherein a computer program is stored in the memory, and the processor implements the steps in the above method embodiments when executing the computer program.

[0143] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps in the above-mentioned method embodiments are implemented.

[0144] In one embodiment, a computer program product is provided, including a computer program, which implements the steps in the above method embodiments when executed by a processor.

[0145] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant regulations.

[0146] A person of ordinary skill in the art can understand that all or part of the processes in the above-mentioned embodiment method can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in the present application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, an artificial intelligence (AI) processor, etc., but are not limited to this.

[0147] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0148] The above-described embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.

Claims

1. A user login processing method, characterized in that: The method comprises: Get the login username entered by the user on the preset login interface; Query the necessary information history confirmation status corresponding to the login user name from the local storage to obtain the query result; When the query result is successful, a first target state is displayed in the preset login interface; the first target state is a state indicating that the user has viewed and confirmed the necessary information; In the case where the query result is a query failure, a second target state is displayed in the preset login interface; the second target state is a state indicating that the user has not viewed and confirmed the necessary information; When the user clicks a login button in the preset login interface, a user login process corresponding to the first target state or the second target state displayed in the preset login interface is executed.

2. The method according to claim 1, characterized in that When the user clicks the login button in the preset login interface, executing the user login process corresponding to the first target state or the second target state displayed in the preset login interface includes: Initiate a user login verification operation when the display status in the preset login interface is the first target status; When the display state in the preset login interface is the second target state, a viewing confirmation prompt message is displayed to prompt the user to view and confirm necessary information.

3. The method according to claim 1, characterized in that After the second target state is displayed in the preset login interface, the method further includes: In response to the user's viewing and confirming operation on the necessary information, the second target state displayed in the preset login interface is switched to the first target state.

4. The method according to claim 2, characterized in that: After the initiating user login verification operation, the method further includes: When the user's login verification is passed, the necessary information history confirmation status corresponding to the login user name is recorded in the local storage.

5. The method according to claim 1, characterized in that The step of obtaining a login user name input by a user in a preset login interface includes: When the user inputs information in the login user name input box of the preset login interface and clicks an area other than the login user name input box, acquiring the information input in the login user name input box; The information input in the login user name input box is determined as the login user name.

6. The method according to any one of claims 1 to 5, characterized in that: After obtaining the login username entered by the user on the preset login interface, it also includes: Detecting the number of times the preset login interface is displayed and obtaining a detection result; In the case where the detection result is displayed for the first time, a preset necessary information viewing page is displayed, and the query result is determined to be a query failure; The querying of the necessary information history confirmation status corresponding to the login user name from the local storage to obtain the query result includes: When the detection result is not displayed for the first time, the necessary information history confirmation status corresponding to the login user name is queried from the local storage to obtain the query result.

7. A user login processing device, characterized in that: The device comprises: The information acquisition module is used to obtain the login username entered by the user in the preset login interface; A status query module, used to query the necessary information history confirmation status corresponding to the login user name from the local storage to obtain the query result; A first display module, used to display a first target state in the preset login interface when the query result is a successful query; the first target state is a state indicating that the user has viewed and confirmed the necessary information; A second display module is used to display a second target state in the preset login interface when the query result is a query failure; the second target state is a state indicating that the user has not viewed and confirmed the necessary information; A login processing module is used to execute user login processing corresponding to the first target state or the second target state displayed in the preset login interface when the user clicks the login button in the preset login interface.

8. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 6 are implemented.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

10. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

Images