Method and apparatus for managing user login, and device and medium

Abstract

Provided are a method and apparatus for managing user login, and a device and a medium. One method comprises: in response to determining that an interaction action of a user in an application is about to initiate a login event for logging in the application, storing interaction data associated with the interaction action; acquiring state data associated with the login event; in response to determining that the state data meets a predetermined login condition, providing a login channel for initiating the login event; and in response to determining that the application has been successfully logged in via the login channel, applying the stored interaction data in the application, so as to execute the interaction action. By using the exemplary implementation of the present disclosure, a login page can be provided to a user when it is determined that an application environment is suitable for logging in an application. Particularly, when login cannot be immediately performed due to some reasons, the problem of a user waiting for the response of a login page for a long time is avoided, and the problem of interrupting the normal browsing of the user is also avoided.

Description

Methods, apparatus, devices, and media for managing user logins Technical Field

[0001] Exemplary implementations of this disclosure generally relate to user management, and more particularly to methods, apparatus, devices, and computer-readable storage media for managing user logins. Background Technology

[0002] Applications have been developed to perform various functions, allowing users to log in and access these functions. In some applications, specific functions associated with a user's account can only be accessed after the user logs in. However, due to factors such as network conditions, users may not be able to log in immediately, and the login process may be unresponsive. Therefore, there is a need for a more efficient way to manage user logins and avoid long waiting times for users.

[0003] Summary of the Invention

[0004] In a first aspect of this disclosure, a method for managing user login is provided. In this method, in response to determining that a user's interaction in an application will initiate a login event, interaction data associated with the interaction is stored. State data associated with the login event is acquired. In response to determining that the state data meets predetermined login conditions, a login channel for initiating the login event is provided. In response to determining that successful login to the application via the login channel is achieved, the stored interaction data is applied in the application to perform the interaction action.

[0005] In a second aspect of this disclosure, an apparatus for managing user login is provided. The apparatus includes: a storage module configured to store interaction data associated with the interaction in response to determining that a user's interaction in an application will initiate a login event; an acquisition module configured to acquire state data associated with the login event; a provision module configured to provide a login channel for initiating the login event in response to determining that the state data meets predetermined login conditions; and an application module configured to apply the stored interaction data in the application to perform the interaction action in response to determining that the user has successfully logged into the application via the login channel.

[0006] In a third aspect of this disclosure, an electronic device is provided. The electronic device includes: at least one processing unit; and at least one memory coupled to the at least one processing unit and storing instructions for execution by the at least one processing unit, the instructions causing the electronic device to perform the method according to a first aspect of this disclosure when executed by the at least one processing unit.

[0007] In a fourth aspect of this disclosure, a computer-readable storage medium is provided having a computer program stored thereon, which, when executed by a processor, causes the processor to implement the method according to a first aspect of this disclosure.

[0008] In a fifth aspect of this disclosure, a computer program product is provided, comprising a computer program that, when executed by a processor, implements the method according to a first aspect of this disclosure.

[0009] It should be understood that the content described in this content section is not intended to limit the key or essential features of the implementation of this disclosure, nor is it intended to restrict the scope of this disclosure. Other features of this disclosure will become readily apparent from the following description. Attached Figure Description

[0010] In the following detailed description, the above and other features, advantages, and aspects of the various implementations of this disclosure will become more apparent, taken in conjunction with the accompanying drawings. In the accompanying drawings, the same or similar reference numerals denote the same or similar elements, wherein:

[0011] Figure 1 shows a block diagram of an application environment according to an exemplary implementation of the present disclosure;

[0012] Figure 2 shows a block diagram for managing user login according to some implementations of this disclosure;

[0013] Figure 3 shows a block diagram of interactive actions according to some implementations of this disclosure;

[0014] Figure 4 shows a block diagram of determining login success metrics according to some implementations of this disclosure;

[0015] Figure 5 shows a block diagram illustrating the detailed process of managing user login according to some implementations of this disclosure;

[0016] Figure 6 shows a flowchart of a method for managing user login according to some implementations of this disclosure;

[0017] Figure 7 shows a block diagram of an apparatus for managing user login according to some implementations of this disclosure; and

[0018] Figure 8 shows a block diagram of a device capable of implementing various implementations of the present disclosure. Detailed Implementation

[0019] Implementations of this disclosure will now be described in more detail with reference to the accompanying drawings. While some implementations of this disclosure are shown in the drawings, it should be understood that this disclosure can be implemented in various forms and should not be construed as limited to the implementations set forth herein. Rather, these implementations are provided to provide a more thorough and complete understanding of this disclosure. It should be understood that the accompanying drawings and implementations of this disclosure are for illustrative purposes only and are not intended to limit the scope of protection of this disclosure.

[0020] In the description of the implementation methods disclosed herein, the term "comprising" and similar terms should be understood as open inclusion, i.e., "including but not limited to". The term "based on" should be understood as "at least partially based on". The term "one implementation" or "the implementation" should be understood as "at least one implementation". The term "some implementations" should be understood as "at least some implementations". Other explicit and implicit definitions may also be included below. As used herein, the term "model" can represent the relationships between various data. For example, the aforementioned relationships can be obtained based on various currently known and / or future-developed technical solutions.

[0021] It is understood that the data involved in this technical solution (including but not limited to the data itself, the acquisition or use of the data) shall comply with the requirements of relevant laws, regulations and related provisions.

[0022] It is understood that before using the technical solutions disclosed in the various embodiments of this disclosure, users should be informed of the types, scope of use, and usage scenarios of the personal information involved in this disclosure through appropriate means in accordance with relevant laws and regulations, and user authorization should be obtained.

[0023] For example, upon receiving a user's active request, a prompt message is sent to the user to explicitly inform them that the requested operation will require the acquisition and use of the user's personal information. This allows the user to independently choose whether to provide personal information to the software or hardware, such as the electronic device, application, server, or storage medium performing the operations of this disclosed technical solution, based on the prompt message.

[0024] As an optional but non-restrictive implementation, in response to a user's active request, a prompt message can be sent to the user, for example, via a pop-up window, where the prompt message can be presented in text format. Furthermore, the pop-up window can also include a selection control allowing the user to choose whether to "agree" or "disagree" to provide personal information to the electronic device.

[0025] It is understood that the above notification and user authorization process are merely illustrative and do not constitute a limitation on the implementation of this disclosure. Other methods that comply with relevant laws and regulations may also be applied to the implementation of this disclosure.

[0026] The term "in response to" as used herein refers to a state in which a corresponding event occurs or a condition is satisfied. It will be understood that the timing of subsequent actions performed in response to such event or condition is not necessarily strongly correlated with the time when the event occurs or the condition is met. For example, in some cases, subsequent actions may be performed immediately upon the occurrence of the event or the fulfillment of the condition; while in others, they may be performed some time after the occurrence of the event or the fulfillment of the condition.

[0027] Example Environment

[0028] In some applications, certain functions associated with a user's account can only be accessed after the user logs in. However, due to network conditions or other reasons, the user may not be able to log in immediately, and the login process may be unresponsive. Refer to Figure 1, which illustrates a block diagram 100 of an application environment according to an exemplary implementation of this disclosure. For ease of description, a media sharing application will be used as an example to describe the process of managing user login. Alternatively and / or additionally, the application may include, but is not limited to, video applications, audio applications, news applications, social networking applications, online store applications, and so on.

[0029] As shown in Figure 1, users can browse page 110 of the application, which may include media items 112 published by various users within the application. Users can use the application without being logged in; for example, they can browse various media items, view information about various users within the application, and so on. However, users need to log in first to use certain functions within the application. For example, a user can click the "like" control 120. Since the "like" action is associated with the user's account, the user needs to log in to the application first. Upon receiving an interaction between the user and control 120, page 120 can be displayed, and the user can log in to the application via any of several login channels 130, 132, and 134. Upon successful login, the user's "like" action will be executed.

[0030] However, due to poor network conditions, application latency, or other reasons, the login process may experience response delays or even become unresponsive. In such cases, users can only wait for the application to respond and cannot continue using the application. Therefore, it is desirable to manage user logins in a more efficient way and avoid prolonged user wait times.

[0031] Login Management Overview

[0032] To at least partially address the shortcomings of the prior art, a method for managing user login is proposed according to an exemplary implementation of this disclosure. Referring to Figure 2, which describes an overview of an exemplary implementation of this disclosure, Figure 2 shows a block diagram 200 for managing user login according to some implementations of this disclosure. As shown in Figure 2, a method for managing user login is provided. Specifically, at box 210, it can be determined whether an interactive action will trigger a login event. If the determination result is "yes," then at box 220, login can be paused, i.e., the login page is not displayed. At box 222, interactive data associated with the interactive action can be stored. Continuing the example above, interactive data related to a "like" action can be stored, such as the control operated by the action being "like," the identifier of the object corresponding to the interactive action (e.g., the media item being liked), the corresponding execution time, and the execution status "incomplete," etc.

[0033] Furthermore, at box 230, status data associated with the login event can be obtained asynchronously. This status data may include, for example, the network status and workload of the electronic device running the application. At box 240, in response to determining that the status data meets predetermined login conditions, a login channel for initiating the login event is provided. Specifically, the success probability of logging into the application using different login channels can be determined separately, and login channels with higher success probabilities can be presented preferentially. For example, the login channels can be sorted in descending order of success probability, or one or more login channels with higher success probabilities can be provided, and so on.

[0034] At box 260, it can be determined whether the application has been successfully logged in via the provided login channel. In response to confirming successful login, at box 260, the stored interaction data is applied within the application to execute an interaction action. At this point, a "like" action can be automatically performed on the media item 112 previously viewed by the user. It should be understood that after the user performs the "like" action, a login page does not immediately pop up, nor does it require the user to log in to the application immediately. Instead, the user can continue browsing within the application as needed.

[0035] Using the exemplary implementation of this disclosure, state data can be retrieved asynchronously in the application's background, and a login page can be provided to the user when the application environment is deemed suitable for logging in. In this way, the user does not need to log in to the application immediately. In particular, it avoids the problem of users waiting for a long time for the login page to respond, and also avoids interrupting the user's normal browsing, in cases where login fails for some reason.

[0036] Detailed process of login management

[0037] Having outlined some implementations according to this disclosure, further details regarding login management will be described below. According to some implementations of this disclosure, users can use the application without being logged in. In certain circumstances, user interactions within the application may trigger a login event, in which case interaction data associated with the interaction can be stored.

[0038] Referring to Figure 3 for further details regarding the interactive action, Figure 3 shows a block diagram 300 of an interactive action according to some implementations of this disclosure. As shown in Figure 3, the interactive action 310 may include at least one of the following: a "like" action 311 for a media item in the application, a "favorite" action 312 for a media item in the application, a "rating" action 313 for a media item in the application, a "share" action 314 for a media item in the application, a "follow" action 315 for a user account in the application, or a "take a picture" action 316 in the application.

[0039] Specifically, the "like" action corresponds to the user's account within the app, therefore, the user needs to log in before liking. The "favorite" action adds a media item to the user's favorites list, also requiring login. The "rating" action displays the ratingr's account information, requiring login. The "share" action displays the sharer's account information, requiring login. The "follow" action displays the follower's account information, requiring login. Furthermore, photographed media items will be published within the app, displaying the publisher's account information, thus requiring login before photographing.

[0040] Using some implementation methods disclosed herein, subsequent state collection and login channel recommendation processes can be performed when an interactive action is about to trigger a login event. This reduces interference with user operations and ensures that users can perform subsequent actions (e.g., freely browsing various media items within the application) without needing to log in immediately. Furthermore, it ensures that when login is required, information on the channel most likely to result in successful login is provided.

[0041] According to some implementations of this disclosure, multiple login channels may include at least one of the following: an application account; an account of another application besides those supported by the application; an electronic device identifier; or an email address supported by the application. See Figure 4 for more information, which illustrates a block diagram 400 of determining login success metrics according to some implementations of this disclosure. As shown in Figure 4, multiple login channels 420 may be provided. User account 421 may represent an account registered in the application; for example, if application account 421 exists, the password for application account 421 may be stored by default to improve login speed.

[0042] According to some implementations of this disclosure, other accounts 422 can represent accounts in other applications supported by the application. For example, suppose the current application is a media item sharing application, and the current application supports logging in using an account from a video application. In this case, it can be determined whether the video application is installed on the user's electronic device. If it is determined that the video application is installed, a login channel using the video application can be recommended. If the video application is not installed on the electronic device, the corresponding login channel may not be provided.

[0043] For example, it can be determined whether a user identification card (e.g., a SIM card) is installed in the electronic device. If a SIM card is installed, an option to log in using a mobile phone number (423) can be provided; otherwise, the option to log in using a mobile phone number (423) can be omitted. Alternatively and / or additionally, the application can support login using an email address (424). In this case, the network status between the electronic device and the email server can be determined; if the email server can be accessed normally, an option to log in using an email address (424) can be provided.

[0044] According to some implementations of this disclosure, status data can be collected to determine the channel most likely to successfully log in from multiple login channels 420. As shown in the figure, status data 410 associated with login events can be collected. This status data 410 may include, for example, at least one of the following: network status 411 of the electronic device running the application; workload 412 of the electronic device running the application; server status 413 of the server device communicating with the application; login history 414 of logging into the application via multiple login channels; or resource status 415 associated with multiple login channels.

[0045] Specifically, network state 411 can represent the data transmission efficiency between the electronic device and the application's server. When network state 411 is poor, various login channels will result in significant time delays. In this case, the login page can be temporarily suspended, allowing the user to perform other operations that do not require login (e.g., browsing, etc.). Workload 412 can represent the workload of the electronic device, and thus the computing resources available to the application. When the application has limited resources, the login page can be temporarily suspended to avoid prolonged login delays. Server state 413 represents the performance metrics of the server providing the application. When the server is busy processing other tasks, the login page can be temporarily suspended to avoid prolonged login delays.

[0046] Furthermore, login history 414 can represent the login success rate of multiple users using multiple login channels, allowing for the priority recommendation of login channels with higher success rates to increase the login probability. Similarly, resource status 415 can represent the status of resources associated with each login channel. Specifically, assuming the application supports login using accounts from other applications, it can determine whether those other supported applications are installed on the electronic device. Or, assuming the application supports login using a mobile phone number, it can detect whether a SIM card is installed on the electronic device, and so on.

[0047] Using some implementation methods of this disclosure, multi-faceted state data can be collected, and weighting operations can be performed on different aspects of the state data to recommend login channels that are more conducive to successful login. According to some implementation methods of this disclosure, in the process of providing login channels for initiating login events, multiple success indicators for logging into the application via multiple login channels can be determined based on state data. Based on multiple success indicators, a login channel can be selected from multiple login channels, where each login channel includes at least one of the multiple login channels.

[0048] As shown in Figure 4, a corresponding success metric 430 can be determined for each login channel. Specifically, a machine learning model can be used to determine the success metric. For example, for each login channel, sample data related to historical logins can be collected, which may include historical status data and corresponding login results (e.g., success or failure). A large amount of sample data can be used to train the machine learning model so that the model can describe the correlation between status data and login results using each login channel. The login results of multiple channels can be sorted in descending order, and one or more higher-ranked login channels can be recommended preferentially.

[0049] According to some implementations of this disclosure, in response to determining that the status data meets predetermined login conditions, a login channel for initiating a login event is provided. In other words, if the status data indicates a high probability of successful login, a login channel for initiating a login event can be provided. Predetermined login conditions can be customized, for example, the probability of successful login is higher than a predetermined value (e.g., 50%, 60%, or other values), etc. Specifically, the login page may include one or more recommended login channels. For example, multiple login channels can be arranged in descending order of success rate. Alternatively and / or additionally, the highest-ranking login channel can be highlighted; for example, the highest-ranking login channel can be displayed first, displayed in a larger font and / or bold, displayed using other colors and / or formats, etc. In this way, user attention can be attracted to prioritize the recommended login channel.

[0050] Furthermore, users can log in to the application via a recommended login channel. Upon confirming successful login via a login channel, stored interaction data can be applied within the application to perform interactive actions. Specifically, upon confirming successful login via a login channel, the user enters the account corresponding to the login channel; and stored interaction data can be applied within the account to perform interactive actions. For example, if relevant interaction data for a "like" action is stored, a "like" action can be performed on the media item that was liked. In this case, the user does not need to return to the previous media item or press the "like" control again; instead, the "like" action is automatically performed after successful login.

[0051] It should be understood that since the status detection and recommended login channel processes are executed in the application background, they do not interfere with the user's normal browsing process. Furthermore, because the login page and its recommended login channels are only displayed when the probability of successful login is considered high, login is usually successful immediately. This reduces login latency and user waiting time.

[0052] According to some implementations of this disclosure, in response to the determination that the status data does not meet the predetermined login conditions, information to postpone login is provided. In other words, if it is determined that the success rate of each login channel is low, the login page can be postponed, for example, by providing a message such as "The current network condition is poor, and the login time will be long." The user can then be further asked whether to "log in now" or "log in later." If the user selects "log in now," multiple login channels are presented in descending order of success rate; if the user selects "log in later," the user can continue to use the allowed functions in the application without being logged in.

[0053] Alternatively and / or additionally, in the absence of login, relevant status data can be collected periodically, and a login page can be provided in response to the determination that the status data meets the predetermined login conditions. In this way, the appropriate time for login can be determined in the background, and the user can be prompted to log in, thereby avoiding the problem of users repeatedly trying to log in and waiting when the network conditions are poor.

[0054] According to some implementations of this disclosure, subsequent user interactions following an initial interaction can be received; in response to determining that the subsequent interaction is not related to the login event, the subsequent interaction is executed within the application. In other words, assuming the subsequent interaction does not need to be executed after login, the user can be allowed to operate freely. For example, the user can continue browsing "liked" media items, refresh the page, browse other media items, etc., within the application. Using some implementations of this disclosure, users can continue to use some functions of the application without interrupting their free operation.

[0055] According to some implementations of this disclosure, in response to determining that a subsequent interaction is associated with a login event, subsequent interaction data associated with the subsequent interaction is stored; and in response to determining that the user has successfully logged into the application via a login channel, the stored subsequent interaction data is applied in the application to execute the subsequent interaction. In other words, if a subsequent interaction requires login to execute, the subsequent interaction can be recorded. For example, if a user presses the "Comment" control on the page, a text box for entering comment content can pop up even if the user is not logged in. The user can then enter comment content in this text box.

[0056] At this point, the comment can be recorded and marked as "not executed". If the status data indicates that login is allowed, a login page can be provided for the user to log in. After the user successfully logs in, the recorded comment can be published using that user's account.

[0057] According to some implementations of this disclosure, in response to determining that login to the application via a login channel has failed, a notification indicating login failure is provided. It should be understood that login failures may occur due to changes in the surrounding environment of the electronic device; in such cases, the user can be notified: "Login failed, please try again later." Alternatively and / or additionally, changes in the environmental state can be automatically detected, and once the environmental state improves, a pop-up message can appear recommending one or more login channels determined based on the new state detection, allowing the user to log in.

[0058] According to some implementation methods of this disclosure, the execution time of the interactive action can be determined by utilizing the actual time point of the interactive action performed after successful login. Alternatively and / or additionally, the time point at which the user enters comment content can be recorded, and the comment's publication time can be determined based on this time point. Assume the user performs an interactive action at time point T1, successfully logs in at time point T2, and the comment content is actually published at time point T3. In this case, time point T3 can be used as the publication time point. In this way, the publication time point is consistent with the execution of the actual action and can accurately reflect the real changes in various data within the application. Alternatively and / or additionally, time point T1 can be used as the publication time point. In this way, the user will not experience time delays caused by network anomalies, etc.

[0059] While the above describes the process of triggering user login through user interaction, alternatively and / or additionally, user login can also be triggered based on predetermined rules. For example, various state information can be collected, and if it is determined that the current state is suitable for login, a ranked login channel can be displayed. Alternatively and / or additionally, a ranked login channel can be displayed when it is determined that subsequent user interaction may require login. Specifically, a pre-trained machine learning model can be used to predict possible future actions based on the user's historical actions. Furthermore, when it is predicted that the user will perform an action that triggers a login event, a ranked login channel can be displayed.

[0060] The various steps of some implementations according to this disclosure have been described separately. The detailed process of managing user login is described below with reference to Figure 5. Figure 5 shows a block diagram 500 of the detailed process of managing user login according to some implementations of this disclosure. As shown in Figure 5, user login management can be triggered based on rules 510, at which point user login management 530 can be actively triggered 512. Then, status detection 534 can be performed, actively acquiring status data associated with the login event. Further, login channels can be sorted 536, and the sorted login channels can be displayed. If login is successful, subsequent actions can be performed.

[0061] Alternatively and / or additionally, user login management 530 can be triggered based on user trigger 520. In this case, user login management 530 can be initiated in response to receiving an interaction action 310 indicating that a login event is about to be started. Specifically, interaction data associated with the login event can be stored 532. In status detection 534, status data associated with the login event can be obtained. Then, login channels can be sorted 536, and at box 540, if login is successful, the stored interaction action can be executed at box 550. If login fails, at box 552, after waiting for the login status to improve, the sorted login channels can be displayed again for the user to log in.

[0062] It should be understood that although the process of managing user logins was described above using a media sharing application as an example, alternatively and / or additionally, this process can be performed in other applications, such as video applications, audio applications, news applications, social networking applications, online store applications, etc. For example, in an online store application, a user can browse information about various items offered in the application without being logged in, and upon detecting an action of adding to the shopping cart and / or making a purchase, a status check is performed, which then pops up a sorted login channel.

[0063] Using the exemplary implementation of this disclosure, state data can be retrieved asynchronously in the application's background, and a login page can be provided to the user when the application environment is deemed suitable for logging in. In this way, the user does not have to log in to the application immediately. In particular, it avoids the problem of users waiting for a long time for a login page response, and also avoids interrupting the user's normal browsing, in cases where immediate login is not possible for some reason.

[0064] Example process

[0065] Figure 6 shows a flowchart of a method 600 for managing user login according to some implementations of this disclosure. At block 610, in response to determining that a user's interaction in the application will initiate a login event, interaction data associated with the interaction is stored. At block 620, state data associated with the login event is obtained. At block 630, in response to determining that the state data meets predetermined login conditions, a login channel for initiating the login event is provided. At block 640, in response to determining that successful login to the application via the login channel has been achieved, the stored interaction data is applied in the application to perform the interaction action.

[0066] According to some implementations of this disclosure, applying stored interaction data in an application to perform an interaction action includes: in response to determining that a user has successfully logged into the application via a login channel, accessing the account corresponding to the login channel; and applying stored interaction data in the account to perform an interaction action.

[0067] According to some implementations of this disclosure, the method 600 further includes: receiving a subsequent interaction action from the user after the initial interaction action; and, in response to determining that the subsequent interaction action is not associated with the login event, executing the subsequent interaction action in the application.

[0068] According to some implementations of this disclosure, the method 600 further includes: in response to determining that a subsequent interaction action is associated with a login event, storing subsequent interaction data associated with the subsequent interaction action; and in response to determining that the user has successfully logged into the application via a login channel, applying the stored subsequent interaction data in the application to perform the subsequent interaction action.

[0069] According to some implementations of this disclosure, the interactive action includes at least one of the following: liking a media item in the application; adding a media item to favorites in the application; rating a media item in the application; sharing a media item in the application; following a user account in the application; or taking a photo in the application.

[0070] According to some implementations of this disclosure, providing a login channel for initiating a login event includes: determining multiple success metrics for logging into the application via multiple login channels based on state data; and selecting a login channel from multiple login channels based on the multiple success metrics, wherein the login channel includes at least one of the multiple login channels.

[0071] According to some implementations of this disclosure, the status data includes at least one of the following: the network status of the electronic device running the application; the workload of the electronic device running the application; the server status of the server device communicating with the application; the login history of logging into the application via multiple login channels; or the resource status associated with multiple login channels.

[0072] According to some implementations of this disclosure, multiple login channels include at least one of the following: an application account; an account of an application other than the application supported by the application; an electronic device identifier; or an email address supported by the application.

[0073] According to some implementations of this disclosure, the method 600 further includes: in response to determining that logging into the application via a login channel has failed, providing a notification indicating login failure.

[0074] According to some implementations of this disclosure, the method 600 further includes: in response to determining that the status data does not meet the predetermined login conditions, providing information to postpone login.

[0075] Example devices and equipment

[0076] Figure 7 shows a block diagram of an apparatus 700 for managing user login according to some implementations of the present disclosure. The apparatus 700 includes: a storage module 710 configured to store interaction data associated with an interaction action in response to determining that a user's interaction action in an application will initiate a login event; an acquisition module 720 configured to acquire status data associated with the login event; a providing module 730 configured to provide a login channel for initiating the login event in response to determining that the status data meets predetermined login conditions; and an application module 740 configured to apply the stored interaction data in the application to perform an interaction action in response to determining that the user has successfully logged into the application via the login channel.

[0077] According to some implementations of this disclosure, applying stored interaction data in an application to perform an interaction action includes: in response to determining that a user has successfully logged into the application via a login channel, accessing the account corresponding to the login channel; and applying stored interaction data in the account to perform an interaction action.

[0078] According to some implementations of this disclosure, the device further includes: receiving a subsequent interaction action from the user after the initial interaction action; and executing the subsequent interaction action in the application in response to determining that the subsequent interaction action is not associated with the login event.

[0079] According to some implementations of this disclosure, the apparatus further includes: in response to determining that a subsequent interactive action is associated with a login event, storing subsequent interactive data associated with the subsequent interactive action; and in response to determining that a user has successfully logged into the application via a login channel, applying the stored subsequent interactive data in the application to perform the subsequent interactive action.

[0080] According to some implementations of this disclosure, the interactive action includes at least one of the following: liking a media item in the application; adding a media item to favorites in the application; rating a media item in the application; sharing a media item in the application; following a user account in the application; or taking a photo in the application.

[0081] According to some implementations of this disclosure, providing a login channel for initiating a login event includes: determining multiple success metrics for logging into the application via multiple login channels based on state data; and selecting a login channel from multiple login channels based on the multiple success metrics, wherein the login channel includes at least one of the multiple login channels.

[0082] According to some implementations of this disclosure, the status data includes at least one of the following: the network status of the electronic device running the application; the workload of the electronic device running the application; the server status of the server device communicating with the application; the login history of logging into the application via multiple login channels; or the resource status associated with multiple login channels.

[0083] According to some implementations of this disclosure, multiple login channels include at least one of the following: an application account; an account of an application other than the application supported by the application; an electronic device identifier; or an email address supported by the application.

[0084] According to some implementations of this disclosure, it further includes: in response to determining that logging into the application via a login channel has failed, providing a notification indicating login failure.

[0085] According to some implementations of this disclosure, it further includes: in response to determining that the status data does not meet the predetermined login conditions, providing information to postpone login.

[0086] Figure 8 shows a block diagram of a device 800 capable of implementing various implementations of the present disclosure. It should be understood that the computing device 800 shown in Figure 8 is merely exemplary and should not constitute any limitation on the functionality and scope of the implementations described herein. The computing device 800 shown in Figure 8 can be used to implement the methods described above.

[0087] As shown in Figure 8, the computing device 800 is in the form of a general-purpose computing device. Components of the computing device 800 may include, but are not limited to, one or more processors or processing units 810, memory 820, storage devices 830, one or more communication units 840, one or more input devices 850, and one or more output devices 860. The processing unit 810 may be a physical or virtual processor and is capable of performing various processes according to programs stored in memory 820. In a multiprocessor system, multiple processing units execute computer-executable instructions in parallel to improve the parallel processing capability of the computing device 800.

[0088] Computing device 800 typically includes multiple computer storage media. Such media can be any available media accessible to computing device 800, including but not limited to volatile and non-volatile media, removable and non-removable media. Memory 820 can be volatile memory (e.g., registers, cache, random access memory (RAM)), non-volatile memory (e.g., read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory), or some combination thereof. Storage device 830 can be removable or non-removable media and can include machine-readable media, such as flash drives, disks, or any other media that can be used to store information and / or data (e.g., training data for training) and can be accessed within computing device 800.

[0089] The computing device 800 may further include additional removable / non-removable, volatile / non-volatile storage media. Although not shown in FIG8, disk drives for reading from or writing to removable, non-volatile disks (e.g., "floppy disks") and optical disk drives for reading from or writing to removable, non-volatile optical disks may be provided. In these cases, each drive may be connected to a bus (not shown) via one or more data media interfaces. The memory 820 may include a computer program product 825 having one or more program modules configured to perform various methods or actions of various implementations of the present disclosure.

[0090] The communication unit 840 enables communication with other computing devices via a communication medium. Additionally, the components of the computing device 800 can function as a single computing cluster or multiple computing machines capable of communicating via communication connections. Therefore, the computing device 800 can operate in a networked environment using logical connections to one or more other servers, networked personal computers (PCs), or another network node.

[0091] Input device 850 can be one or more input devices, such as a mouse, keyboard, trackball, etc. Output device 860 can be one or more output devices, such as a monitor, speaker, printer, etc. Computing device 800 can also communicate as needed with one or more external devices (not shown) via communication unit 840. These external devices, such as storage devices, display devices, etc., can communicate with one or more devices that enable user interaction with computing device 800, or with any device (e.g., network card, modem, etc.) that enables computing device 800 to communicate with one or more other computing devices. Such communication can be performed via input / output (I / O) interfaces (not shown).

[0092] According to exemplary implementations of this disclosure, a computer-readable storage medium is provided that stores computer-executable instructions thereon, wherein the computer-executable instructions are executed by a processor to implement the methods described above. According to exemplary implementations of this disclosure, a computer program product is also provided, which is tangibly stored on a non-transitory computer-readable medium and includes computer-executable instructions, which are executed by a processor to implement the methods described above. According to exemplary implementations of this disclosure, a computer program product is provided that stores a computer program thereon, which, when executed by a processor, implements the methods described above.

[0093] Various aspects of this disclosure are described herein with reference to flowchart illustrations and / or block diagrams of methods, apparatuses, devices, and computer program products implemented according to this disclosure. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer-readable program instructions.

[0094] These computer-readable program instructions can be provided to a processing unit of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine such that, when executed by the processing unit of the computer or other programmable data processing apparatus, they create means for implementing the functions / actions specified in one or more blocks of the flowchart and / or block diagram. These computer-readable program instructions can also be stored in a computer-readable storage medium that causes a computer, programmable data processing apparatus, and / or other device to operate in a particular manner. Thus, the computer-readable medium storing the instructions comprises an article of manufacture that includes instructions for implementing aspects of the functions / actions specified in one or more blocks of the flowchart and / or block diagram.

[0095] Computer-readable program instructions can be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable data processing apparatus, or other device to produce a computer-implemented process, thereby causing the instructions that execute on the computer, other programmable data processing apparatus, or other device to perform the functions / actions specified in one or more boxes of a flowchart and / or block diagram.

[0096] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of an instruction, which contains one or more executable instructions for implementing the specified logical function. In some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutive blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, may be implemented using a dedicated hardware-based system that performs the specified function or action, or using a combination of dedicated hardware and computer instructions.

[0097] Various implementations of this disclosure have been described above. These descriptions are exemplary and not exhaustive, nor are they limited to the disclosed implementations. Many modifications and variations will be apparent to those skilled in the art without departing from the scope and spirit of the described implementations. The terminology used herein is chosen to best explain the principles, practical applications, or improvements to technology in the market, or to enable others skilled in the art to understand the various implementations disclosed herein.

Claims

1. A method for managing user login, comprising: In response to determining that the user's interaction action in the application will initiate a login event to log in to the application, the interaction data associated with the interaction action is stored; Obtain the status data associated with the login event; In response to determining that the status data meets predetermined login conditions, a login channel for initiating the login event is provided; as well as In response to determining that the application has been successfully logged in via the login channel, the stored interaction data is applied in the application to perform the interaction action.

2. The method of claim 1, wherein applying the stored interaction data in the application to perform the interaction action comprises: In response to determining that the user has successfully logged into the application via the login channel, access the account corresponding to the login channel; as well as The stored interaction data is applied to the account in order to perform the interaction action.

3. The method according to claim 1, further comprising: Receive subsequent interactive actions from the user after the first interactive action; In response to determining that the subsequent interaction is not associated with the login event, the subsequent interaction is performed in the application.

4. The method of claim 3, further comprising: In response to determining that the subsequent interaction action is associated with the login event, subsequent interaction data associated with the subsequent interaction action is stored; as well as In response to determining that the user has successfully logged into the application via the login channel, the stored subsequent interaction data is applied in the application to execute the subsequent interaction action.

5. The method of claim 1, wherein the interactive action includes at least one of the following: The "like" action for media items in the application; The action of adding a media item to favorites in the application; Evaluation actions for media items in the application; Forwarding actions for media items in the application; Actions related to following user accounts within the application; or The shooting action in the application.

6. The method of claim 1, wherein providing the login channel for initiating the login event comprises: Based on the status data, multiple success indicators for logging into the application via multiple login channels are determined respectively; as well as Based on the multiple success metrics, the login channel is selected from the multiple login channels, and the login channel includes at least one of the multiple login channels.

7. The method of claim 1, wherein the status data includes at least one of the following: The network status of the electronic device running the application; The workload of the electronic device running the application; Server status of the server device communicating with the application; Login history of the application is accessed via the multiple login channels respectively; or The resource status associated with each of the multiple login channels.

8. The method of claim 1, wherein the plurality of login channels includes at least one of the following: The application's account; Accounts for applications other than the application mentioned above that are supported by the application; Electronic device identification; or The application supports the following email addresses.

9. The method of claim 1, further comprising: In response to determining that logging into the application via the login channel failed, a notification indicating login failure is provided.

10. The method of claim 1, further comprising: In response to determining that the status data does not meet the predetermined login conditions, information to postpone login is provided.

11. An apparatus for managing user login, comprising: A storage module is configured to store interaction data associated with an interaction action in response to a login event that determines the user's interaction action in the application will initiate the login process. The acquisition module is configured to acquire status data associated with the login event; A module is configured to provide a login channel for initiating the login event in response to determining that the status data meets predetermined login conditions; as well as An application module is configured to, in response to determining that the application has been successfully logged in via the login channel, apply the stored interaction data in the application to perform the interaction action.

12. An electronic device, comprising: At least one processing unit; as well as At least one memory, coupled to the at least one processing unit and storing instructions for execution by the at least one processing unit, the instructions causing the electronic device to perform the method according to any one of claims 1 to 10 when executed by the at least one processing unit.

13. A computer-readable storage medium having a computer program stored thereon, the computer program causing the processor to implement the method according to any one of claims 1 to 10 when executed by a processor.

14. A computer program product comprising a computer program, wherein the computer program, when executed by a processor, implements the method according to any one of claims 1 to 10.

Images