Mailbox login method and device, electronic equipment, storage medium and program product

Abstract

This application discloses an email login method, apparatus, electronic device, storage medium, and program product; it displays an email login page corresponding to an instant messaging application, the email login page including a login information editing area; in response to an input operation in the login information editing area, it obtains email login information corresponding to the input operation; in response to a failure to log in to the email based on the email login information, it displays updated email login information corresponding to the original email login information on the email login page, the updated email login information being determined based on the member information of the current member recorded by the instant messaging application, the current member being the member in the business entity corresponding to the input operation in the instant messaging application; in response to a confirmation operation of the updated email login information, it logs in to the email based on the updated email login information. This application can improve the success rate of email login.

Description

Technical Field

[0001] This application relates to the field of computer technology, specifically to an email login method, apparatus, electronic device, storage medium, and program product. Background Technology

[0002] With the continuous development of the internet, email, as a widely used communication method, has become an indispensable information delivery tool. Email enables efficient and convenient communication between different locations and devices, greatly improving work efficiency and quality of life. Many existing instant messaging applications also support email login functionality.

[0003] Currently, logging into an email account usually requires manually entering the email address and other login information. However, if the login information is entered incorrectly, the email login will fail. Summary of the Invention

[0004] This application provides an email login method, apparatus, electronic device, storage medium, and program product, which can improve the success rate of email login.

[0005] This application provides an email login method, comprising: displaying an email login page corresponding to an instant messaging application, the email login page including a login information editing area; in response to an input operation in the login information editing area, obtaining email login information corresponding to the input operation; in response to a failure to log in to the email based on the email login information, displaying updated email login information corresponding to the email login information on the email login page, the updated email login information being determined based on the member information of the current member recorded by the instant messaging application, the current member being the member in the business entity corresponding to the input operation in the instant messaging application; and in response to a confirmation operation of the updated email login information, logging in to the email based on the updated email login information.

[0006] This application embodiment also provides an email login device, including: a login unit, configured to display an email login page corresponding to an instant messaging application, the email login page including a login information editing area; the login unit is further configured to, in response to an input operation in the login information editing area, obtain email login information corresponding to the input operation; the login unit is further configured to, in response to a failure to log in to the email based on the email login information, display updated email login information corresponding to the email login information on the email login page, the updated email login information being determined based on the member information of the current member recorded by the instant messaging application, the current member being the member in the business entity corresponding to the instant messaging application that corresponds to the input operation; the login unit is further configured to, in response to a confirmation operation of the updated email login information, log in to the email based on the updated email login information.

[0007] In some implementations, the email login information includes an email address, and the login unit is specifically configured to: in response to a failure to log in to the email address based on the email login information, search for a candidate field in the member information of the current member recorded in the instant messaging application, wherein the candidate field is a field related to the email naming rules of the business entity; determine the updated email address corresponding to the input email address based on the found candidate field; and display the updated email address on the email login page.

[0008] In some implementations, the email naming rule includes field feature information corresponding to the email address, and the email login device further includes a field determination unit. The field determination unit is used to: obtain the email address of the historical login email address of the instant messaging application, the historical login email address including email addresses of members of the business entity who have successfully logged in through the instant messaging application in the past; determine the target field that matches the email address of the historical login email address from the member information of the member corresponding to the email address of the historical login email address; and determine the field feature information based on the field feature of the target field.

[0009] In some implementations, the member information includes custom information of the business entity and native information of the instant messaging application. The step of determining the target field matching the email name of the historical login email from the member information of the member corresponding to the email name of the historical login email includes: searching for the target field matching the email name of the historical login email in the custom information; and when the target field is not found in the custom information, searching for the target field matching the email name of the historical login email in the native information.

[0010] In some implementations, there are multiple target fields, and the field determining unit is further configured to: determine at least one combination method based on the position of the target field in the email names of the historical login email addresses, wherein the combination method is a way in which the target field constitutes the email name of the historical login email address; determine the email name weight of the combination method, wherein the email name weight includes the matching weight between the combination method and the email name of the historical login email address, wherein the matching weight is determined based on the frequency of occurrence of the target field in the email names of the historical login email addresses; and determine the updated email login information corresponding to the email login information based on the found candidate fields, including: obtaining at least one updated email name based on the found candidate fields and the at least one combination method, wherein the updated email name corresponds to the combination method, and the at least one updated email name is arranged and displayed on the email login page based on the corresponding matching weight.

[0011] In some implementations, the email login information also includes an email domain name, and the login unit is further configured to: obtain the email domain name of the historical login email of the instant messaging application, the historical login email including emails of members of the business entity who have successfully logged in through the instant messaging application in the past; determine the updated email domain name corresponding to the input email domain name based on the email domain name of the historical login email; and display the updated email domain name on the email login page.

[0012] This application also provides an electronic device, including a processor and a memory, wherein the memory stores multiple instructions; the processor loads instructions from the memory to execute the steps in any of the email login methods provided in this application.

[0013] This application also provides a computer-readable storage medium storing a plurality of instructions adapted for loading by a processor to execute steps in any of the email login methods provided in this application.

[0014] This application also provides a computer program product, including a computer program or instructions, which, when executed by a processor, implement the steps in any of the email login methods provided in this application.

[0015] This application embodiment can display an email login page corresponding to an instant messaging application. The email login page includes a login information editing area. In response to an input operation in the login information editing area, the email login information corresponding to the input operation is obtained. In response to a failure to log in to the email based on the email login information, the updated email login information corresponding to the original email login information is displayed on the email login page. The updated email login information is determined based on the member information of the current member recorded by the instant messaging application. The current member is the member in the business entity corresponding to the instant messaging application who corresponds to the input operation. In response to a confirmation operation of the updated email login information, the email is logged in based on the updated email login information.

[0016] In this application, when logging into an email account via an instant messaging application, if the entered email login information fails, the system can reconstruct and display new email login information based on the member information of the business entity member currently logged into the instant messaging application. This new member information corrects the entered email login information, and the system then attempts to log in to the current member's email account again based on the new information, thereby improving the success rate of email login. Furthermore, this method automatically corrects email login information based on member information, eliminating the need for manual re-entry of email login information, thus simplifying the login input process and improving login efficiency. Attached Figure Description

[0017] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0018] Figure 1a This is a schematic diagram of a scenario for the email login method provided in an embodiment of this application;

[0019] Figure 1b This is a flowchart illustrating the email login method provided in an embodiment of this application;

[0020] Figure 1c This is a schematic diagram of the email login page provided in an embodiment of this application;

[0021] Figure 1d This is a schematic diagram of another email login page provided in an embodiment of this application;

[0022] Figure 1e This is a schematic diagram of another email login page provided in an embodiment of this application;

[0023] Figure 1fThis is a timing diagram of the email login process provided in an embodiment of this application;

[0024] Figure 1g This is a timing diagram of another email login process provided in the embodiments of this application;

[0025] Figure 2a This is a flowchart illustrating an email login method provided in another embodiment of this application;

[0026] Figure 2b This is a flowchart illustrating the process of determining field feature information provided in an embodiment of this application;

[0027] Figure 2c This is a schematic diagram of the server-side email login process provided in an embodiment of this application;

[0028] Figure 3 This is a schematic diagram of the email login device provided in the embodiments of this application;

[0029] Figure 4 This is a schematic diagram of the structure of the electronic device provided in the embodiments of this application. Detailed Implementation

[0030] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0031] This application provides an email login method, apparatus, electronic device, storage medium, and program product.

[0032] Specifically, the email login device can be integrated into an electronic device, such as a terminal or server. The terminal can be a mobile phone, tablet, smart Bluetooth device, laptop, or personal computer (PC); the server can be a single server or a server cluster consisting of multiple servers.

[0033] In some embodiments, the email login device can also be integrated into multiple electronic devices. For example, the email login device can be integrated into multiple servers, and the email login method of this application can be implemented by multiple servers.

[0034] In some embodiments, the terminal can also be used as a server to implement some or all of the functions of a server.

[0035] For example, refer to Figure 1aThis email login method can be applied to electronic devices, which may include terminals. These terminals can display an email login page corresponding to an instant messaging application. The email login page includes a login information editing area. In response to an input operation in the login information editing area, the method retrieves the email login information corresponding to the input operation and sends it to a server. In response to a failure to log in using the email login information, the method displays updated email login information on the email login page. The updated email login information is determined by the server based on the member information of the current member recorded by the instant messaging application. The current member is the member in the business entity corresponding to the input operation within the instant messaging application. Finally, in response to a confirmation operation of the updated email login information, the method logs in using the updated email login information.

[0036] In this application embodiment, the terms "module" or "unit" refer to a computer program or part of a computer program that has a predetermined function and works with other related parts to achieve a predetermined goal, and can be implemented wholly or partially using software, hardware (such as processing circuitry or memory), or a combination thereof. Similarly, a processor (or multiple processors or memory) can be used to implement one or more modules or units. Furthermore, each module or unit can be part of an overall module or unit that includes the functionality of that module or unit.

[0037] The following sections provide detailed descriptions. It should be noted that the order of the following embodiments is not intended to limit the preferred order of the embodiments. It is understood that the specific embodiments of this application involve user-related data such as input operations, email login information, email accounts, email passwords, email names, member information, and address books. When the embodiments of this application are applied to specific products or technologies, user permission or consent is required, and the collection, use, and processing of related data must comply with the relevant laws, regulations, and standards of the relevant countries and regions.

[0038] In this embodiment, an email login method is provided, such as... Figure 1b As shown, the specific process for this email login method can be as follows:

[0039] 110. Display the email login page corresponding to the instant messaging application. The email login page includes a login information editing area.

[0040] Instant messaging applications (IMAs) are applications that transmit messages in real time over a network. IMAs support one-to-one or one-to-many instant interactions and can send and receive information via text, voice, images, video, files, and other methods. In practical applications, an IMA can support one or more business entities, providing them with corresponding services, including email functionality. In other words, an IMA corresponds to at least one business entity.

[0041] In this context, a business entity refers to an entity or system that initiates or executes one or more business activities. A business entity can be a school, enterprise, organization, etc. In practice, a business entity can have one or more members, which can be configured according to actual needs or application scenarios. Members of a business entity can provide support or services for the business entity's operations, such as employees of the business entity and / or other personnel involved in the business entity's operations.

[0042] The email login page refers to the page used to log in to an email account. For example, an email login page may include at least one of an email account input component and an email verification information input component to allow users to enter their email account, email verification information, etc. The login information editing area refers to the area used to edit email login information. Email login information refers to the information used to log in to an email account, such as the email account and email verification information (e.g., password, verification code, etc.), etc.

[0043] For example, embodiments of this application can be applied to a terminal. The email login page can be opened through an instant messaging application (such as an enterprise IM, where IM is an instant messaging application) running on the terminal, allowing users (such as members of a business entity) to access the email login page through this application. The login information editing area on the email login page may include input components for the email account and input components for email verification information.

[0044] 120. In response to input operations in the login information editing area, obtain the email login information corresponding to the input operation.

[0045] The input operation refers to the operation of entering email login information in the login information editing area.

[0046] For example, users (such as members of a business entity) can enter their email address and password in the email account input component and email verification information input component in the login information editing area of ​​the email login page, respectively. This allows the terminal to obtain the user's email login information through the input components, with the user's separate permission or consent.

[0047] The email login method in this application can be used to log in to an email address already bound to an instant messaging application, or it can be used to newly bind and log in to an email address for an instant messaging application. For example, in the scenario of logging in to an email address already bound to an instant messaging application, the email address to be logged in can be an email address bound to or not bound to a member account of a member logging into the instant messaging application's business entity. Alternatively, in the scenario of newly binding and logging in to an email address for an instant messaging application, the email address to be logged in can also be an email address that will be bound to a member account of a member logging into the instant messaging application's business entity.

[0048] For example, in some implementations, the email login page displays a login prompt or a binding prompt. A login prompt is a message indicating that the user should enter their email login information to log in to their email account, while a binding prompt is a message indicating that the user should enter their email login information to bind and log in to their email account. For example, such as... Figure 1c The email login page shown, in a scenario where the email is linked to an instant messaging application, displays an input field for the email account (i.e., the email account input component) and an input field for the email password (i.e., the email verification information input component) in the login information editing area, as well as a "Login" button (i.e., a login prompt). Alternatively, as... Figure 1d The email login page shown, in the scenario of logging into an instant messaging application and binding a new email address, displays an input box for the email account (i.e., the input component for the email account) and an input box for the email password (i.e., the input component for email verification information), as well as an "Add" button (i.e., a binding prompt).

[0049] 130. In response to failure to log in to an email account based on the email login information, the updated email login information corresponding to the email login information is displayed on the email login page. The updated email login information is determined based on the member information of the current member recorded by the instant messaging application. The current member is the member in the business entity corresponding to the instant messaging application who is the same as the one who entered the operation.

[0050] The updated email login information refers to the updated email login information displayed on the email login page.

[0051] In this context, member information refers to the relevant information of members within a business entity. In this embodiment, members of a business entity can log in to the instant messaging application using their member accounts. A member account refers to the user account of a member of a business entity within the instant messaging application. It is understood that in this embodiment, the current member is the member who performed the input operation in the login information editing area; that is, the current member is the member who performed the corresponding input operation. Therefore, the current member is the member currently logged into the instant messaging application within the business entity, and the member information of the current member can be obtained from the instant messaging application based on the member account of the currently logged-in instant messaging application.

[0052] For example, the terminal can send the email login information entered by the user (i.e., the current member) to the backend (server) for verification. If the verification is successful (i.e., successful email login), the terminal logs into the email account based on the user's entered email login information. If the verification fails (i.e., email login fails), with the user's separate permission or consent, the terminal retrieves the updated email login information from the server based on the current member's member information and displays it on the email login page. Thus, when logging into an email account via an instant messaging application, if the entered email login information fails, the terminal can reconstruct and display the new email login information based on the member information of the business entity member currently logging into the instant messaging application. This new member information corrects the entered email login information, and the terminal attempts to log into the current member's email account again based on the new email login information, thereby improving the success rate of email login. This method automatically corrects email login information based on member information, eliminating the need for manual re-entry of email login information, thus simplifying the login input process and improving login efficiency.

[0053] In some implementations, member information includes the member's identity information within the business entity. For example, a member's identity information may include, but is not limited to, the member's identification information within the business entity recorded by the instant messaging application. This identification information may include, but is not limited to, one or more of the following: identifiers (such as employee ID), member name, role information (such as department / position), account name, alias, etc.

[0054] In this application embodiment, in addition to displaying the user-inputted email login information, updated email login information is also displayed, or the updated email login information can replace the user-inputted email login information for display. For example, in some implementations, the updated email login information can replace the user-inputted email login information for display, such as... Figure 1e The email login page shown allows you to display only the updated email login information, such as the email account "memberA@company.com", in the login information editing area, instead of showing the email login information entered by the user.

[0055] In some implementations, after a login failure based on email login information, fields related to the email naming rules of the business entity can be searched based on the member information of the currently logged-in member. This improves the accuracy of the determined updated email login information, avoids login failures due to incorrect email names, and increases the success rate of email login. Specifically, the email login information includes the email name. In response to a login failure based on email login information, the updated email login information corresponding to the email login information is displayed on the email login page, including:

[0056] When login to an email account fails based on the email login information, the system searches for candidate fields in the member information of the current member recorded in the instant messaging application. The candidate fields are fields related to the email naming rules of the business entity.

[0057] Based on the found candidate fields, determine the updated email address corresponding to the entered email address;

[0058] The updated email address will be displayed on the email login page.

[0059] Email naming rules refer to how a business entity names the email addresses of its members. Understandably, different business entities may use different email naming rules in practice, but the naming rules for email addresses within the same business entity are often consistent. Furthermore, to facilitate naming their email addresses, business entities will select one or more sub-information from their members' member information, such as member name, employee ID, or role information like department / position, and use them for the member's email address. Therefore, the member information of a business entity typically records fields related to the member's email address (i.e., candidate fields).

[0060] For example, if a business entity selects a member name as the email address for each member, after a failed login attempt based on the entered email login information, the member name can be read from the member information of the current member recorded in the instant messaging application. The local part of the entered email account (i.e., the part before the @ symbol, i.e., the email address) can be replaced with the member name, and the replaced email account can be displayed on the email login page. The email address in the replaced email account is the updated email address.

[0061] In practical applications, since an instant messaging application can provide services to one or more business entities, it often only records necessary information about these entities and may not be aware of their email naming rules. This can lead to an inability to accurately identify fields in member information related to each entity's email naming rules. To address this, in this embodiment, for any business entity, the application can determine the candidate fields corresponding to the known email addresses of its members by matching and identifying the field characteristics (such as field structure, field position, field identifier, etc.) of these candidate fields. This allows the application to determine the email naming rules specific to that business entity based on the known email addresses of its members—that is, the field characteristics of the fields used for member email addresses. This facilitates the search for candidate fields corresponding to the email addresses of members within the instant messaging application based on these field characteristics, thereby improving the accuracy of the updated email login information and increasing the success rate of email login.

[0062] For example, in some implementations, the email naming rule includes field feature information corresponding to the email name. In response to a failure to log in to the email account based on the email login information, before displaying the updated email login information corresponding to the email login information on the email login page, the rule further includes:

[0063] Retrieve the email names of historical login emails for the instant messaging application. Historical login emails include emails of members of the business entity who have successfully logged in through the instant messaging application in the past.

[0064] From the member information of the members corresponding to the email addresses of the historical login email addresses, determine the target field that matches the email address of the historical login email address;

[0065] Field feature information is determined based on the field features of the target field.

[0066] The target field refers to the field that matches the email address of the historical login email address. For example, the target field may typically include one or more sub-information from the member's member information, such as member name, employee ID, or role information such as department or position.

[0067] Field feature information refers to information used to represent the characteristics of a field. For example, field feature information may include, but is not limited to, field identifiers (such as names), field locations (such as indexes), and data types.

[0068] For example, for any given business entity, we can retrieve the email addresses of its members who have successfully logged in via instant messaging applications throughout their history. We then match these email addresses with fields in their member information, selecting the most matching field as the target field. Finally, we extract the characteristic information (such as type and name) from the target field's attribute information as its feature information.

[0069] It should be noted that in some implementations, the historical login email addresses can be all email addresses that members of the business entity have successfully logged in to through the instant messaging application in the past. These members who have logged in to historical login email addresses can be any member of the business entity, such as including the current member and any other members, or only other members. It is understood that, with the permission or consent of the business entity members, the instant messaging application backend can record the email accounts of the email addresses that the business entity members have previously logged in to. However, if a member of the business entity does not allow binding their logged-in email account (i.e., the email address of the historical login email address) to their member account in the instant messaging application, the instant messaging application backend can record the email account, but will not associate the email account with their member account. Therefore, when the current member does not allow binding their historically logged-in email account to the instant messaging application, and at the current moment, the current member fails to log in to their email address by entering their password, the instant messaging application cannot directly obtain the associated historical login email address. In this case, it can obtain the email accounts of all historically logged-in email addresses of the business entity members (which may include the email addresses of the current member and other members) to determine the email naming rules of the business entity, thereby determining the possible email account of the current member (i.e., the updated email login information).

[0070] Alternatively, in some implementations, the historical login email address can be an email address bound to a member account of a business entity member. For example, with the permission or consent of a business entity member, only email addresses that the member has allowed to bind and that have successfully logged in via the instant messaging application in the past can be retrieved as historical login email addresses. In this case, the members who logged in to these historical login email addresses can be any other member of the business entity besides the current member.

[0071] It's understandable that for any given business entity, the sub-information of similar members will share similar field characteristics. For example, the names of any two members are typically stored using the same data type, such as VARCHAR or CHAR. Similarly, the employee IDs of any two members often share the same named field, such as the employee ID field being named employee_id. Therefore, by analyzing the field characteristics of the member information of any employee within a business entity, it's possible to find candidate fields with the same characteristics in the member information of another employee.

[0072] In some implementations, after determining the field feature information based on the field features of the target field, the method further includes: associating and storing the field feature information with the entity identifier of the business entity. This way, before searching for the field corresponding to the field feature information, the field feature information corresponding to the business entity can be obtained based on the entity identifier of the owner entity corresponding to the user's logged-in member account. Therefore, the field feature information corresponding to the business entity only needs to be stored once, which can meet the requirement of all members of the business entity retrieving the corresponding field feature information when logging into their email accounts.

[0073] In some implementations, member information refers to the member's information in the contact list of the business entity recorded in the instant messaging application, field feature information refers to contact list fields, and candidate fields are the values ​​of the contact list fields corresponding to the field feature information. Here, contact list fields refer to different categories or items in the instant messaging application's contact list used to describe the specific information of each member (or contact), and this specific information is the value of the contact list field.

[0074] Therefore, in this embodiment of the application, the email names of the historical login emails of the instant messaging application can be obtained in advance, the target field matching the email name of the historical login email can be determined, and the field feature information can be determined based on the field features of the target field. In this way, when the user fails to log in to the email, the field feature information of the pre-determined business entity can be obtained, the target field matching the email name of the historical login email can be determined, and the field feature information can be determined based on the field features of the target field.

[0075] For example, in some implementations, candidate fields related to the email naming rules of the business entity can be searched based on field features to find the candidate fields more quickly and accurately. Specifically, the email naming rules include field feature information corresponding to the email name. In response to a failure to log in to the email account based on the email login information, candidate fields are searched in the member information of the current member recorded by the instant messaging application, including:

[0076] When login to an email account fails based on the email login information, the system searches for the field corresponding to the field feature information in the member information of the current member recorded in the instant messaging application.

[0077] The fields corresponding to the found field feature information are used as candidate fields.

[0078] For example, after a failed login attempt based on the entered email address, the field pointed to by the field name can be read from the member information of the current member recorded in the instant messaging application. If the read field is the member's name, it can be used as a candidate field, that is, a candidate field has been found.

[0079] For example, such as Figure 1fThe sequence diagram shown illustrates the email login process. Users (e.g., members of a business entity) can enter their email address and password in the login information editing area on the email login page. This information is then obtained by the client (the instant messaging application running on the terminal). The client sends the entered login information to the backend (server) email login module for verification. If verification fails, the login fails. Upon login failure, the email login module determines the field feature information corresponding to the business entity (e.g., the address book field corresponding to the current member's company) and requests the backend field extraction module to find the corresponding candidate fields (e.g., the values ​​of the address book field). The field extraction module reads the current member's member information (e.g., address book) from the backend field matching module and matches it with the read member information and field feature information to determine the corresponding candidate fields. These candidate fields are then sent to the client to update the displayed email address. After the user confirms the updated email address, the client can log in again using the updated email address (i.e., log in again using the candidate fields). The email login module verifies the updated email account and password. If the verification is successful (i.e., the email login is successful), the module logs into the email account to be logged in based on the user's input email login information and directly returns the login result to the client.

[0080] In some implementations, the field feature information corresponding to the business entity can be stored in the email login module of the server, so that when the email login module fails to verify the user's entered email login information, the corresponding candidate field can be determined in real time based on the stored field feature information.

[0081] In some implementations, for existing business entities of instant messaging applications, the field feature information corresponding to the existing business entity can be determined in advance through offline tasks based on the email names of the historical login emails of the instant messaging application corresponding to the existing business entity. In this way, the data processing work of existing business entities of instant messaging applications can be completed in batches and in advance. Especially since instant messaging applications usually have multiple existing business entities, this method can reduce the burden of real-time processing of instant messaging applications and avoid response delays.

[0082] For example, obtaining the email address of the historical login email address of an instant messaging application includes: obtaining the email address of the historical login email address of the instant messaging application corresponding to the existing business entity through the offline task corresponding to the existing business entity.

[0083] Among them, existing business entities refer to business entities that already exist in instant messaging applications and have a certain level of activity. For example, the registration time and / or number of members of such business entities meet specified conditions, such as the registration time exceeding a preset duration and / or the number of members exceeding a preset number. Therefore, in this embodiment of the application, existing business entities often have a sufficient amount of data to meet the requirements for determining the corresponding field feature information. Offline tasks refer to tasks that do not rely on real-time processing but are executed in the background (server) or during off-peak periods.

[0084] For example, the backend of an instant messaging application can pre-create offline tasks corresponding to existing business entities (such as existing enterprises). These offline tasks can be used to batch retrieve the email addresses of historical login email addresses for the instant messaging application corresponding to the existing business entities; that is, the email addresses of members of the existing business entities who have successfully logged in through the instant messaging application in the past. Furthermore, the offline task can perform offline processing based on the retrieved email addresses to offline determine target fields that match the historical login email addresses, and determine the field feature information corresponding to the existing business entities based on the field features of the target fields.

[0085] In some implementations, for new business entities in instant messaging applications or existing business entities whose field feature information could not be determined through offline tasks, the email address of any member of the business entity can be obtained in real time as the email address of the historical login email address when any member of the business entity successfully logs in to the email address through the instant messaging application. The field feature information corresponding to the business entity can then be determined in real time based on the latest email address recorded by the instant messaging application. This provides a comprehensive basis for email login for different business entities and improves the overall success rate of logging in to the email address using the instant messaging application.

[0086] For example, obtaining the email address of the historical login email address of the instant messaging application includes: when a member of the target business entity successfully logs in to the email address through the instant messaging application, the email address of the email address logged in by the member of the target business entity is used as the email address of the historical login email address. The target business entity is a newly added business entity or an existing business entity whose field feature information could not be determined through offline tasks.

[0087] Among them, the newly added business entity refers to the business entity added in the instant messaging application. For example, the registration time and / or members of the business entity meet the specified conditions, such as the registration time not exceeding the preset duration and / or the number of members not exceeding the preset number. Therefore, in this embodiment of the application, the newly added business entity often has a small amount of data required to determine the corresponding field feature information.

[0088] For example, when a member of a target business entity successfully logs into their email account via an instant messaging application, the instant messaging application's backend can obtain the email address of the member who logged in as a historical login email address in real time. Based on the obtained email address, it can determine the target field that matches the historical login email address, and based on the field characteristics of the target field, it can determine the corresponding field characteristic information of the target business entity, providing a basis for subsequent logins by other members of the same target business entity.

[0089] For example, such as Figure 1g The sequence diagram of the email login process illustrates that new users (e.g., members of a business entity) can enter their email address and password in the login information editing area on the email login page. This information is then obtained by the client (the instant messaging application running on the terminal). The client sends the entered login information to the backend (server) email login module for verification. If verification is successful, the user logs in. Upon successful login, the email login module requests the backend field extraction module to determine the field feature information matching the email address of a previously logged-in email address (e.g., checking if the successfully logged-in username matches the address book field). The field extraction module reads the current member's information (e.g., address book) from the backend field matching module to determine the target field matching the email address of a previously logged-in email address. Based on the target field's field features, the module determines the field feature information. The field extraction module sends the field feature information to the email login module for storage (e.g., returning the matched address book field to the email login module and saving it). Additionally, the login result can be returned to the client.

[0090] In some implementations, when matching target fields for existing business entities using offline tasks, since offline tasks are executed in the background or during off-peak periods, they can match all fields of member information with the email names of historical login emails. This may result in multiple fields matching the email names. In this case, the field with the highest matching degree can be selected as the target field to improve matching accuracy. When matching target fields for target business entities, since this matching process is based on the email names of real-time login emails, to improve matching efficiency and facilitate subsequent search for candidate fields, fields in member information can be matched with email names of historical login emails according to priority. For example, first match fields of business entity custom information in member information (student ID > employee ID > UID > domain account > employee ID > workcode, etc.), then match fields of native information (account > alias), and use the first matched field as the target field.

[0091] Since the email addresses of business entities are often closely related to the membership identities of their members, and the custom information of business entities can more accurately represent membership identities, in some implementations, the custom information of business entities can be preferentially used to match the email addresses of historical login email addresses to improve the accuracy and efficiency of the matching. Specifically, member information includes the custom information of the business entity and the native information of the instant messaging application. From the member information of the members corresponding to the email addresses of historical login email addresses, the target fields that match the email addresses of historical login email addresses are determined, including:

[0092] In the custom information, find the target field that matches the email address of the historical login email address;

[0093] If the target field is not found in the custom information, the target field that matches the email name of the historical login email address will be searched in the native information.

[0094] Custom information refers to information defined by the business entity within the instant messaging application. For example, custom information may include, but is not limited to, one or more sub-information such as student ID, employee ID, UID, domain account, employee number, and workcode. Native information refers to information directly generated by the instant messaging application without any processing, modification, or manipulation. For example, native information may include, but is not limited to, one or more sub-information such as application account (e.g., user ID, account name) and alias (e.g., nickname, username, or display name).

[0095] For example, when matching a recorded member's email address with fields in their member information, the system can prioritize matching the email address with custom information (defined by the business entity) from the member information. If any field in the custom information matches the local portion of a previously logged-in email address, that field is used as the target field. If no match is found, meaning all fields in the custom information do not match the email address, the system can match the email address with native information from the instant messaging application (i.e., native information). If any field in the native information matches the local portion of a previously logged-in email address, that field is used as the target field.

[0096] When a user launches an instant messaging application, the application may preload certain functions, such as the contact list of the business entity corresponding to the user's logged-in member account, for the user's convenience. Based on this, matching can be performed locally. For example, in some implementations, the instant messaging application can cache the current members locally upon startup, allowing the application to read member information from its local cache, thereby improving matching efficiency. Especially when the field characteristics of the business entity are predetermined, matching can be performed locally only by retrieving the predetermined field characteristics from the server, reducing the need for frequent communication with the server and improving the stability of the matching process.

[0097] In practical applications, due to data loss or reasons specific to the business entity, it may be impossible to find the candidate field in the current member's information. For example, when the business entity is a newly added entity or an existing entity whose field feature information could not be determined through offline tasks, the candidate field cannot be found because the field feature information is empty or the corresponding field in the member information is empty. In this case, the user's entered email login information can still be displayed on the email login page. Alternatively, in some implementations, if no candidate field is found, an error or failure message can be displayed.

[0098] Alternatively, in some implementations, if no candidate field is found, a preset specified field from the custom information defined by the business entity in the current member's member information can be used as a candidate field to attempt email login, thereby improving the success rate of email login. Specifically, in response to a failure to log in to the email based on the email login information, displaying the updated email login information corresponding to the email login information on the email login page further includes:

[0099] When no candidate field is found, the specified field is selected as the candidate field from the current member's member information according to the email name selection rules preset by the instant messaging application.

[0100] Based on the candidate fields, determine the updated email address corresponding to the entered email address.

[0101] The email name selection rule refers to the general email name selection rule preset by the instant messaging application for its associated business entities. This preset rule includes selecting specified fields from the current member's member information as candidate email name fields; for example, selecting the account number from the member information as a candidate field. In other words, in this embodiment, the email naming rule for each business entity is its unique email naming method determined based on the characteristics of each business entity's email name, while the preset email name selection rule refers to the possible email naming methods preset by the instant messaging application for each business entity.

[0102] For example, if no candidate field is found, the corresponding specified field can be retrieved from the member information recorded by the instant messaging application based on the application's preset, general email name selection rules. For instance, some predefined built-in fields in the enterprise address book (such as account) can be used as the specified field, selecting only the first non-empty value. This allows the input email name to be replaced with the correct account name, and the replaced email address will be displayed on the email login page.

[0103] Because the default email name selection rules of instant messaging applications are general rules and may not match the specific naming needs of a business entity, selecting only one specified field as a candidate field may not result in an accurate updated email name. For example, in some implementations, there can be multiple specified fields, and the default email name selection rules can include the selection order of these fields. For instance, based on the field characteristics recorded in the default email name selection rules and the selection order of the multiple specified fields, one of the multiple specified fields (such as account, alias, etc.) in the current member's information can be selected sequentially as a candidate field to obtain an updated email name. The updated email name is then used to attempt login. For example, according to the selection order, the account is selected first as a candidate field, the email name in the input email account is replaced with the account name, and login is attempted using the replaced email name. If login is successful, the process ends. If login fails, the alias is selected as a candidate field according to the selection order, the email name in the input email account is replaced with the alias, and login is attempted using the replaced email name.

[0104] In practical applications, business entities can determine complex or multiple email naming rules based on their own needs. Therefore, the target field used for naming by the business entity may contain all or part of multiple sub-information fields, or the business entity may use one sub-information field as the target field for some member emails and another sub-information field as the target field for other member emails. In other words, the email naming rules of a business entity may include multiple different naming methods. In this case, there may be multiple fields that match the email name portion of one or more historical login emails corresponding to the business entity. To ensure users can successfully log in, at least one updated email name can be displayed on the email login page based on the association information between fields and email names.

[0105] For example, in some implementations, the updated email address can be determined and displayed based on the position and frequency of the matching target field in the email addresses of historical login email addresses, thereby achieving more refined email address identification and matching, and making the displayed updated email address more comprehensive and accurate. Specifically, there are multiple target fields. After determining the target fields matching the email addresses of historical login email addresses from the member information of the members corresponding to the email addresses of historical login email addresses, the following is also included:

[0106] Based on the position of the target field in the email names of the historical login emails, determine at least one combination method, wherein the combination method is the way in which the target field constitutes the email name of the historical login email;

[0107] Determine the email name weight for the combination method. The email name weight includes the matching weight between the combination method and the email names of the historical login emails. The matching weight is determined based on the frequency of the target field in the email names of the historical login emails.

[0108] Based on the found candidate fields, determine the updated email login information corresponding to the email login information, including:

[0109] Based on the found candidate fields and at least one combination method, at least one updated email address is obtained. The updated email address corresponds to the combination method, and the at least one updated email address is displayed on the email login page in a sorted manner based on the corresponding matching weight.

[0110] In this context, matching weight refers to determining the importance of a target field relative to the historical login email address when identifying the target field to match the email address. For example, in the member email addresses of a business entity, the frequency of using the member name as a field in the email address might be higher than the frequency of using the employee ID as a field. Therefore, the member name matching the historical login email address can be considered more important (i.e., matching weight) than the employee ID.

[0111] For example, in email name matching, target fields might include member name, employee ID, department, etc., and these fields can appear in different positions in the email names of historical login emails. Therefore, the email names of historical login emails may contain different combinations of these fields. Thus, based on the position of the target field in the historical login emails, the combination method of the target field in the historical login emails can be determined, such as member name, member name + employee ID, member name + department, etc. Furthermore, the probability of the target field appearing in the recorded email names of the business entity can be directly calculated (e.g., the number of occurrences divided by the total number of characters in the email name). The sum of the probability of the target field appearing in each combination method yields the matching weight of each combination method. Based on this, the candidate fields corresponding to the target field can be combined according to the combination method of the target field to obtain at least one updated email name. Then, according to the matching weight of each email name from highest to lowest, the updated email names are arranged and displayed on the email login page.

[0112] In some implementations, the similarity between the user-input email address and the updated email address determined by various combinations can be calculated. This allows the most similar one or more of the updated email addresses to be displayed on the email login page, making the displayed updated email addresses more relevant to the user's needs. Specifically, the email address weight includes the similarity between the input email address and the updated email address.

[0113] Because email information such as email names is often consistent among members of the same organizational unit (such as the same region or department) within the business entity's organizational structure, the association weight of email names belonging to members of the same organizational unit as the current member can be determined. This increases the weight of email names within the same organizational unit, increasing their probability of being selected and improving the success rate of users logging in with the updated email domain. Specifically, email name weight includes the association weight of email names with the historical login email addresses corresponding to the associated member. The email name association weight refers to the importance of the combination of email names with the historical login email addresses corresponding to the associated member. For example, a specific weight (i.e., email name weight) can be assigned to the target field corresponding to the email names of members in the same organizational unit as the current member to increase the matching weight of these email names.

[0114] It should be noted that in practical applications, email address weight can be a combination of one or more of email address similarity, matching weight, and email address association weight.

[0115] In some implementations, after a login failure based on email login information, an updated email domain name can be determined based on the email domain name corresponding to the business entity. This improves the accuracy of the updated email login information, avoids login failures due to incorrect email domain name input, and increases the success rate of email login. Specifically, the email login information also includes the email domain name. In response to a login failure based on email login information, the updated email login information corresponding to the original email login information is displayed on the email login page, and further includes:

[0116] Obtain the email domains of historical login emails for instant messaging applications. Historical login emails include emails of members of the business entity who have successfully logged in through instant messaging applications in the past.

[0117] Based on the email domain of the historical login email, determine the updated email domain corresponding to the entered email domain;

[0118] The updated email domain name is displayed on the email login page.

[0119] For example, for any given business entity, it's possible to retrieve the email domains of its members who have successfully logged in via instant messaging applications in the past. These email domains are then displayed as the updated email domain on the email login page.

[0120] In practical applications, business entities can use one or more email domains according to their own needs, such as using different domains for different regions or parts. Therefore, to ensure users can successfully log in to their email, the email domains of the business entity can be further processed to more accurately display the updated email domain.

[0121] For example, in some implementations, the updated email domain can be determined and displayed based on the domain weight of the email domains of historically logged-in email addresses, thereby achieving more refined email identification and matching and making the displayed updated email domain more accurate. Specifically, since there are multiple email domains, the email login method also includes:

[0122] Determine the domain weight of the email domain used for historical logins, and display the updated email domain on the email login page based on its corresponding domain weight.

[0123] Domain weight refers to the importance of an email domain among historical login email addresses. For example, the email domain with the highest domain weight can be used as the updated email domain, or multiple or all of the historical login email domains can be arranged and displayed as the updated email domain on the email login page, arranged from highest to lowest domain weight.

[0124] In some implementations, the similarity between the user-input email domain and historical login email domains can be determined. This allows the system to display one or more of the most similar domains on the email login page, making the updated domains more aligned with the user's needs. Specifically, the domain weighting includes the similarity between the input email domain and historical login email domains.

[0125] In some implementations, the probability of an email domain appearing in the business entity's recorded email addresses can be directly calculated (e.g., the number of occurrences divided by the total number of domains). This probability can be used as the domain weight of the email domain to achieve more refined and quantitative email identification and matching, making the displayed updated email domain more accurate. Specifically, the domain weight includes the frequency of the email domain appearing in historical login emails.

[0126] Because email domains of members within the same organizational unit (such as the same region or department) often share similar domain names, it's possible to determine the domain association weight of email domains belonging to members within the same organizational unit as the current member. This increases the domain weight of email domains within the same organizational unit, raising their probability of being selected and improving the success rate of user login based on the updated email domain. Specifically, domain weight includes the domain association weight of the historical login email domains corresponding to the associated member. Domain association weight refers to the importance of the historical login email domains corresponding to the associated member. For example, a specific weight (i.e., domain association weight) can be assigned to email domains of members within the same organizational unit as the current member to increase their overall domain weight.

[0127] It should be noted that in practical applications, domain name weight can be one or more of the following combinations, including but not limited to domain name similarity, domain name frequency of occurrence, and domain name association weight.

[0128] In this embodiment, the updated email address and updated email domain can be displayed separately or combined on the email login page. For example, in some implementations, the updated email address and updated email domain can be combined in pairs, such as combining any updated email address and any updated email domain into a complete email account, which is then displayed on the email login page. When there are multiple updated email addresses and multiple updated email domains, the address matching weight of the combined email account can be determined based on the matching weight of the email address and the domain name, so that the multiple combined email accounts are arranged and displayed on the email login page according to their corresponding address matching weights.

[0129] 140. In response to the confirmation operation of the updated email login information, log in to the email account based on the updated email login information.

[0130] The confirmation operation refers to the process of confirming the updated email login information. Confirmation operations can include, but are not limited to, one or more combinations of methods such as clicking, keyboard shortcuts, gestures, voice commands, and shaking.

[0131] For example, a user can click on the updated email login information displayed on the terminal's email login page to confirm the updated login information. In response to this click, the terminal can send the updated login information to the server for verification. If verification is successful, the user can log in to their email account using the verified login information. If verification fails, a login failure message will be displayed.

[0132] In some implementations, when multiple updated email login entries are displayed on the email login page, the confirmation operation can be a confirmation operation for any one of the updated email login entries. Alternatively, in some implementations, to simplify the user's operation process and increase the probability of a user successfully logging in on the first attempt using updated email login entries, the confirmation operation can be a confirmation operation for multiple updated email login entries. For example, a user can select all displayed updated email login entries, or select multiple entries, to send the selected entries to the server for verification. If any one of the email login entries is verified successfully, the user can log in using that entry, thus requiring only one confirmation operation to attempt multiple logins.

[0133] In some implementations, in scenarios where an instant messaging application is bound to and a new email address is logged in, the updated email login information can be bound to the current member. This ensures that the current member can subsequently use the instant messaging application directly without needing to log in again, automatically logging into the email address and improving the user experience for convenience and efficiency. Specifically, the email login method further includes: in response to a confirmation operation on the updated email login information, binding the email address logged in based on the updated email login information to the current member's account in the instant messaging application.

[0134] The email login scheme provided in this application can be applied to various email login scenarios. It displays an email login page corresponding to an instant messaging application, including a login information editing area; in response to an input operation in the login information editing area, it obtains the email login information corresponding to the input operation; in response to a failure to log in to the email based on the original email login information, it displays updated email login information on the email login page, the updated email login information being determined based on the member information of the current member recorded by the instant messaging application, where the current member is the member in the business entity corresponding to the input operation; in response to a confirmation operation of the updated email login information, it logs in to the email based on the updated email login information.

[0135] As can be seen from the above, in this embodiment of the application, when logging into an email account via an instant messaging application, if the entered email login information fails, the system can reconstruct and display new email login information based on the member information of the business entity member currently logged into the instant messaging application. This new member information corrects the entered email login information, and the system attempts to log into the current member's email account again based on the new email login information, thereby improving the success rate of email login. This method automatically corrects email login information based on member information, eliminating the need for manual input of email login information again, thus simplifying the login input process and improving login efficiency.

[0136] The method described in the above embodiments will be further described in detail below.

[0137] In this embodiment, the method of this application embodiment will be described in detail using an instant messaging application for an enterprise as an example.

[0138] This application embodiment uses the address book as an example of member information and an enterprise as an example of business entity. The email login method provided in this application embodiment can be applied to email login information, which may include a terminal and a server. The server includes an email login module, a field extraction module, and a field matching module. The email login module provides an email login access server to realize the functions of email login and sending address book fields to assist users in logging in within instant messaging applications. The field extraction module provides the function of reading user address book fields. The field matching module provides enterprise email with the ability to read address book fields and report successfully logged-in user email accounts for address book field matching tasks.

[0139] like Figure 2a As shown, the specific process of one email login method is as follows:

[0140] 210. Determine the field feature information corresponding to the business entity.

[0141] For example, in this embodiment, considering that many companies use employee ID, student ID, or student-employee ID as general internal accounts, which are displayed in the address book field and can also be used to log in to personal email accounts, the system identifies and records the address book field (i.e., field feature information) that best matches the current company's email account for subsequent email login processes of business members. This involves offline identification for existing companies and real-time identification for new companies or companies where no matching address book field was found offline. Specifically, for existing companies, the system scans offline to find the address book field that best matches the current company's email account; for new companies or companies where no matching address book field was found, when a member of that company successfully logs in to their email account, the system checks whether that successfully logged-in account has a matching address book field.

[0142] For example, such as Figure 2b The process for determining field feature information, as shown, involves the server's field matching module using an offline tool (i.e., creating an offline task) to scan each enterprise. In the address book of each user (i.e., member) within the enterprise, it searches for address book fields (i.e., field feature information) that match the user's email address. If a matching field is found, the field with the most frequent matches is selected and recorded as the enterprise's corresponding field feature information. This information is then used as potential fields to consider when new users log in to the enterprise's email account.

[0143] For newly added enterprises or existing enterprises (i.e., target business entities) whose contact list fields could not be determined through offline tasks, if a new user successfully logs in, the server's field matching module will match the currently logged-in user's email address with that user's contact list. If a matching field is found, the contact list field can be selected according to priority and recorded as the enterprise's corresponding field feature information. This allows subsequent users logging in with the email address to use the value of that user's corresponding contact list field as a potential candidate field for new users logging in to the enterprise's email address.

[0144] During the matching process, the email username is used to first match enterprise-defined fields (in the order: student ID > employee ID > UID > domain account > employee ID > workcode, etc.), and then matches native address book fields (in the order: account > alias). The matching method is full match, meaning a match is considered successful only if the email username and address book field values ​​are exactly the same. If the email username matches multiple address book fields, the custom fields are selected first, followed by the address book fields.

[0145] 220. Display the email login page corresponding to the instant messaging application. The email login page includes a login information editing area.

[0146] 230. In response to an input operation in the login information editing area, obtain the email login information corresponding to the input operation.

[0147] For example, the email login page can be opened through an instant messaging application (such as enterprise IM, where IM is an instant messaging application) running on the terminal, allowing users (such as members of the business entity) to access the email login page through this application. The login information editing area on this page can include input components for the email account and email verification information. Users can enter their email address and password in the input components for both the email account and verification information on the login information editing area, allowing the terminal to obtain the user's entered email login information.

[0148] 240. In response to failure to log in to an email address based on the email login information, obtain the field feature information corresponding to the business entity.

[0149] 250. In the member information of the current member recorded in the instant messaging application, find the candidate fields. The candidate fields are fields related to the email naming rules of the business entity. The email naming rules include the field feature information corresponding to the email name.

[0150] 260. Based on the found candidate fields, determine the updated email address corresponding to the entered email address.

[0151] 270. Display the updated email address on the email login page.

[0152] 280. In response to the confirmation operation of the updated email login information, log in to the email account based on the updated email login information.

[0153] For example, on the terminal side, a user enters their email address and password on the email login page. The server then attempts to log in using the entered email address. If login fails using the entered email address and password, the server sends a correction message based on contact information. Simultaneously, the terminal can display a corrected email username based on the contact information (i.e., the updated email name). The user can then click "Add" to try logging in with the corrected email username. The password will remain the same as the one entered in the previous step. If login is successful, the user is taken to the email application's inbox page. If login also fails using the updated email name, the user is notified of a login failure.

[0154] Correspondingly, on the server side, such as Figure 2cThe server-side email login process shown is as follows: When a user logs in, the email login module first attempts to log in using the email address and password entered by the user. If the email address / password verification is successful, the login is successful. If the verification fails, the login fails, and the system checks if the server has recorded a matching address book field. If the server has recorded a matching address book field, it further checks if the user's corresponding address book field is empty. If it is not empty, after the user confirms the value of the address book field (i.e., the candidate field), the user logs in using the value of the corresponding address book field as the email address. If the server has not recorded a matching address book field, or if the user's corresponding address book field is empty, the system selects a specified field from the current member's information as the email address based on the instant messaging application's preset email address selection rules, such as using a predefined built-in field from the enterprise address book as the email username. If the email address / password verification is successful, the login is successful. If the verification fails, the login fails, and the terminal can display a login failure message to the user. If a field value contains Chinese characters, symbols, or other characters that are not valid for a legitimate email account, the user will be directly prompted that the login has failed.

[0155] As shown above, when logging into an email account using an instant messaging application, if the entered email login information fails, the system can reconstruct and display new email login information based on the member information of the business entity member currently logged into the instant messaging application. This new member information can be used to correct the entered email login information, and the system can then attempt to log into the current member's email account again based on the new email login information, thereby improving the success rate of email login.

[0156] To better implement the above methods, this application also provides an email login device, which can be integrated into an electronic device, such as a terminal or server. The terminal can be a mobile phone, tablet computer, smart Bluetooth device, laptop computer, or personal computer; the server can be a single server or a server cluster composed of multiple servers.

[0157] For example, in this embodiment, the method of this application embodiment will be described in detail by taking the email login device specifically integrated into an electronic device as an example.

[0158] For example, such as Figure 3 As shown, the email login device may include a login unit 310, as follows:

[0159] The login unit displays the email login page corresponding to the instant messaging application. The email login page includes a login information editing area. The login unit also retrieves the corresponding email login information in response to an input operation in the login information editing area. Furthermore, in response to a failure to log in using the original email login information, the login unit displays updated email login information on the email login page. The updated email login information is determined based on the member information of the current member recorded by the instant messaging application. The current member is the member in the business entity corresponding to the input operation within the instant messaging application. The login unit also confirms the updated email login information and logs in to the email account based on the updated email login information.

[0160] In some implementations, the email login information includes an email address. The login unit is specifically used to: in response to a failure to log in to the email address based on the email login information, search for candidate fields in the member information of the current member recorded in the instant messaging application. The candidate fields are fields related to the email naming rules of the business entity; determine the updated email address corresponding to the entered email address based on the found candidate fields; and display the updated email address on the email login page.

[0161] In some implementations, the email naming rules include field feature information corresponding to the email address, and the email login device further includes a field determination unit. The field determination unit is used to: obtain the email address of the historical login email address of the instant messaging application, the historical login email address including the email address of the member of the business entity who has successfully logged in through the instant messaging application in the past; determine the target field that matches the email address of the historical login email address from the member information of the member corresponding to the email address of the historical login email address; and determine the field feature information based on the field feature of the target field.

[0162] In some implementations, member information includes custom information of the business entity and native information of the instant messaging application. The target field that matches the email name of the historical login email is determined from the member information of the member corresponding to the email name of the historical login email. This includes: searching for the target field that matches the email name of the historical login email in the custom information; and when the target field is not found in the custom information, searching for the target field that matches the email name of the historical login email in the native information.

[0163] In some implementations, there are multiple target fields, and the field determination unit is further configured to: determine at least one combination method based on the position of the target field in the email names of historical login emails, wherein the combination method is a way in which the target fields constitute the email names of historical login emails; determine the email name weight of the combination method, wherein the email name weight includes the matching weight between the combination method and the email names of historical login emails, and the matching weight is determined based on the frequency of occurrence of the target field in the email names of historical login emails; and determine the updated email login information corresponding to the email login information based on the found candidate fields, including: obtaining at least one updated email name based on the found candidate fields and at least one combination method, wherein the updated email name corresponds to the combination method, and at least one updated email name is displayed on the email login page in an order based on the corresponding matching weight.

[0164] In some implementations, the email login information also includes an email domain name, and the login unit is further configured to: obtain the email domain name of the historical login email of the instant messaging application, the historical login email includes emails of members of the business entity who have successfully logged in through the instant messaging application in the past; determine the updated email domain name corresponding to the input email domain name based on the email domain name of the historical login email; and display the updated email domain name on the email login page.

[0165] In practice, each of the above units can be implemented as an independent entity or can be arbitrarily combined to be implemented as the same or several entities. For the specific implementation of each of the above units, please refer to the previous method embodiments, which will not be repeated here.

[0166] As can be seen from the above, the email login device of this embodiment includes a login unit, which is used to display the email login page corresponding to the instant messaging application. The email login page includes a login information editing area. The login unit is also used to obtain the email login information corresponding to the input operation in response to the input operation in the login information editing area. The login unit is also used to display the updated email login information corresponding to the email login information on the email login page when the email login fails based on the email login information. The updated email login information is determined based on the member information of the current member recorded by the instant messaging application. The current member is the member in the business entity corresponding to the input operation in the instant messaging application. The login unit is also used to log in to the email based on the updated email login information in response to the confirmation operation of the updated email login information.

[0167] Therefore, in this embodiment of the application, if the entered email login information fails when logging into an email account based on an instant messaging application, the new email login information can be reconstructed and displayed based on the member information of the business entity member currently logged into the instant messaging application. This member information can be used to correct the entered email login information, and the new email login information can be used to attempt to log into the current member's email account again, thereby improving the success rate of email login.

[0168] This application also provides an electronic device, which can be a terminal, a server, or other similar device. The terminal can be a mobile phone, tablet computer, smart Bluetooth device, laptop computer, personal computer, etc.; the server can be a single server or a server cluster composed of multiple servers, etc.

[0169] In some embodiments, the email login device can also be integrated into multiple electronic devices. For example, the email login device can be integrated into multiple servers, and the email login method of this application can be implemented by multiple servers.

[0170] In this embodiment, the electronic device of this embodiment will be described in detail, for example, as... Figure 4 As shown, it illustrates a structural schematic diagram of the electronic device involved in the embodiments of this application, specifically:

[0171] The electronic device may include components such as a processor 410 with one or more processing cores, a memory 420 with one or more computer-readable storage media, a power supply 430, an input module 440, and a communication module 450. Those skilled in the art will understand that... Figure 4 The electronic device structure shown does not constitute a limitation on the electronic device and may include more or fewer components than shown, or combine certain components, or have different component arrangements. Wherein:

[0172] The processor 410 is the control center of the electronic device, connecting various parts of the device via various interfaces and lines. It executes various functions and processes data by running or executing software programs and / or modules stored in the memory 420, and by calling data stored in the memory 420. In some embodiments, the processor 410 may include one or more processing cores; in some embodiments, the processor 410 may integrate an application processor and a modem processor, wherein the application processor mainly handles the operating system, user interface, and applications, and the modem processor mainly handles wireless communication. It is understood that the modem processor may also not be integrated into the processor 410.

[0173] The memory 420 can be used to store software programs and modules. The processor 410 executes various functional applications and data processing by running the software programs and modules stored in the memory 420. The memory 420 may mainly include a program storage area and a data storage area. The program storage area may store the operating system, application programs required for at least one function (such as sound playback function, image playback function, etc.), etc.; the data storage area may store data created according to the use of the electronic device, etc. In addition, the memory 420 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other volatile solid-state storage device. Accordingly, the memory 420 may also include a memory controller to provide the processor 410 with access to the memory 420.

[0174] The electronic device also includes a power supply 430 that supplies power to the various components. In some embodiments, the power supply 430 can be logically connected to the processor 410 through a power management system, thereby enabling functions such as charging, discharging, and power consumption management through the power management system. The power supply 430 may also include one or more DC or AC power supplies, recharging systems, power fault detection circuits, power converters or inverters, power status indicators, and other arbitrary components.

[0175] The electronic device may also include an input module 440, which can be used to receive input digital or character information and generate keyboard, mouse, joystick, optical or trackball signal inputs related to user settings and function control.

[0176] The electronic device may also include a communication module 450. In some embodiments, the communication module 450 may include a wireless module, through which the electronic device can perform short-range wireless transmission, thereby providing users with wireless broadband internet access. For example, the communication module 450 can be used to help users send and receive emails, browse web pages, and access streaming media.

[0177] Although not shown, the electronic device may also include a login unit, etc., which will not be described in detail here. Specifically, in this embodiment, the processor 410 in the electronic device loads the executable files corresponding to the processes of one or more applications into the memory 420 according to the following instructions, and the processor 410 runs the applications stored in the memory 420 to realize various functions, as follows:

[0178] Displays the email login page corresponding to the instant messaging application, which includes a login information editing area; responds to input operations in the login information editing area and retrieves the corresponding email login information; responds to failure to log in to the email based on the original email login information and displays the updated email login information on the email login page, the updated email login information being determined based on the member information of the current member recorded by the instant messaging application, the current member being the member in the business entity corresponding to the input operation; responds to the confirmation operation of the updated email login information and logs in to the email based on the updated email login information.

[0179] For details on the implementation of each of the above operations, please refer to the previous examples, which will not be repeated here.

[0180] As can be seen from the above, in the embodiments of this application, if the entered email login information fails to log in when logging in to an email account based on an instant messaging application, the new email login information can be reconstructed and displayed based on the member information of the business entity member currently logging in to the instant messaging application. This member information can be used to correct the entered email login information, and the new email login information can be used to attempt to log in to the current member's email account again, thereby improving the success rate of email login.

[0181] Those skilled in the art will understand that all or part of the steps in the various methods of the above embodiments can be performed by instructions, or by instructions controlling related hardware. These instructions can be stored in a computer-readable storage medium and loaded and executed by a processor.

[0182] Therefore, embodiments of this application provide a computer-readable storage medium storing a plurality of instructions that can be loaded by a processor to execute steps in any of the email login methods provided in embodiments of this application. For example, the instructions can execute the following steps:

[0183] Displays the email login page corresponding to the instant messaging application, which includes a login information editing area; responds to input operations in the login information editing area and retrieves the corresponding email login information; responds to failure to log in to the email based on the original email login information and displays the updated email login information on the email login page, the updated email login information being determined based on the member information of the current member recorded by the instant messaging application, the current member being the member in the business entity corresponding to the input operation; responds to the confirmation operation of the updated email login information and logs in to the email based on the updated email login information.

[0184] The storage medium may include: read-only memory (ROM), random access memory (RAM), disk or optical disk, etc.

[0185] According to one aspect of this application, a computer program product or computer program is provided, comprising a computer program or instructions that, when executed by a processor, implement the steps of the methods provided in the various optional implementations of the above embodiments. The computer program / instructions are stored in a computer-readable storage medium. A processor of an electronic device reads the computer program / instructions from the computer-readable storage medium and executes the computer program / instructions, causing the electronic device to perform the methods provided in the various optional implementations of the above embodiments.

[0186] Since the instructions stored in the storage medium can execute the steps of any of the email login methods provided in the embodiments of this application, the beneficial effects that any of the email login methods provided in the embodiments of this application can achieve can be realized. For details, please refer to the previous embodiments, which will not be repeated here.

[0187] The foregoing has provided a detailed description of an email login method, apparatus, electronic device, storage medium, and program product provided in the embodiments of this application. Specific examples have been used to illustrate the principles and implementation methods of this application. The descriptions of the above embodiments are only for the purpose of helping to understand the method and core ideas of this application. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of this application. Therefore, the content of this specification should not be construed as a limitation of this application.

Claims

1. An email login method, characterized in that, include: Displays the email login page corresponding to the instant messaging application, the email login page including a login information editing area; In response to an input operation in the login information editing area, obtain the email login information corresponding to the input operation; In response to a failure to log in to the email based on the email login information, the updated email login information corresponding to the email login information is displayed on the email login page. The updated email login information is determined based on the member information of the current member recorded by the instant messaging application. The current member is the member in the business entity corresponding to the instant messaging application that corresponds to the input operation. In response to the confirmation operation of the updated email login information, log in to the email account based on the updated email login information.

2. The email login method as described in claim 1, characterized in that, The email login information includes an email address. When logging into the email account based on the email login information fails, displaying the updated email login information corresponding to the email login information on the email login page includes: When logging into an email account based on the email login information fails, the system searches for candidate fields in the member information of the current member recorded in the instant messaging application. The candidate fields are fields related to the email naming rules of the business entity. Based on the found candidate fields, determine the updated email address corresponding to the input email address; The updated email address is displayed on the email login page.

3. The email login method as described in claim 2, characterized in that, The email naming rule includes field feature information corresponding to the email name. Before displaying the updated email login information on the email login page in response to a failed login attempt based on the email login information, the method further includes: Obtain the email names of the historical login emails of the instant messaging application, including emails of members of the business entity who have successfully logged in through the instant messaging application in the past; From the member information of the members corresponding to the email names of the historical login emails, determine the target field that matches the email names of the historical login emails; The field feature information is determined based on the field features of the target field.

4. The email login method as described in claim 3, characterized in that, The member information includes the custom information of the business entity and the native information of the instant messaging application. The step of determining the target field matching the email address of the member corresponding to the email address of the historical login email address from the member information includes: In the custom information, find the target field that matches the email name of the historical login email address; If the target field is not found in the custom information, the target field that matches the email name of the historical login email is searched in the native information.

5. The email login method as described in claim 3, characterized in that, There are multiple target fields. After determining the target field that matches the email name of the historical login email from the member information of the member corresponding to the email name of the historical login email, the method further includes: Based on the position of the target field in the email address of the historical login email, at least one combination method is determined, wherein the combination method is the way in which the target field constitutes the email address of the historical login email; The email name weight of the combination method is determined, and the email name weight includes the matching weight between the combination method and the email name of the historical login email. The matching weight is determined based on the frequency of occurrence of the target field in the email name of the historical login email. The step of determining the updated email login information corresponding to the found candidate fields includes: Based on the found candidate fields and the at least one combination method, at least one updated email address is obtained. The updated email address corresponds to the combination method, and the at least one updated email address is displayed on the email login page in an order based on the corresponding matching weight.

6. The email login method as described in any one of claims 1 to 5, characterized in that, The email login information also includes an email domain name. The step of displaying updated email login information on the email login page when login fails based on the email login information also includes: Obtain the email domain of the historical login email of the instant messaging application, including the email addresses of members of the business entity who have successfully logged in through the instant messaging application in the past; Based on the email domain of the historical login email, determine the updated email domain corresponding to the input email domain; The updated email domain name is displayed on the email login page.

7. An email login device, characterized in that, include: The login unit is used to display the email login page corresponding to the instant messaging application, the email login page including a login information editing area; The login unit is also configured to respond to an input operation in the login information editing area and obtain the email login information corresponding to the input operation; The login unit is further configured to, in response to a failure to log in to the email based on the email login information, display the updated email login information corresponding to the email login information on the email login page. The updated email login information is determined based on the member information of the current member recorded by the instant messaging application. The current member is the member in the business entity corresponding to the instant messaging application that corresponds to the input operation. The login unit is also used to log in to the email account based on the updated email login information in response to the confirmation operation of the updated email login information.

8. An electronic device, characterized in that, The method includes a processor and a memory, the memory storing multiple instructions; the processor loads instructions from the memory to perform the steps in the email login method as described in any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a plurality of instructions adapted for loading by a processor to perform the steps of the email login method according to any one of claims 1 to 6.

10. A computer program product, comprising a computer program or instructions, characterized in that, When the computer program or instructions are executed by the processor, they implement the steps of the email login method according to any one of claims 1 to 6.

Images