WO2024022124A1

WO2024022124A1 - Application login method, electronic device and system

Info

Publication number: WO2024022124A1
Application number: PCT/CN2023/107324
Authority: WO
Inventors: 何峰
Original assignee: 华为技术有限公司
Priority date: 2022-07-28
Filing date: 2023-07-13
Publication date: 2024-02-01
Also published as: CN117527275A

Abstract

The present application relates to the technical field of terminals. Provided are an application login method, an electronic device and a system. In the present application, during the process of logging in to a first application, a first electronic device can automatically acquire login information of a second application in a second electronic device, so that when the second application is not installed in the first electronic device or the second application is not in a logged-in state, login to the first application can also be automatically performed by means of the second application in the second electronic device, improving the use experience of a user. The method comprises: in response to an operation of a user logging in to a first application, a first electronic device can determine a second application used for performing login authentication on the first application, and determine a second electronic device used for performing login authentication on the first application, the second application being installed in the second electronic device; and then, the first electronic device can perform login to the first application on the basis of acquired login information of the second application in the second electronic device.

Description

Application login methods, electronic devices and systems

This application claims priority to the Chinese patent application submitted to the State Intellectual Property Office on July 28, 2022, with the application number 202210899410.9 and the invention name "Application login method, electronic device and system", the entire content of which is incorporated herein by reference. Applying.

Technical field

The embodiments of the present application relate to the field of terminal technology, and in particular, to an application login method, electronic device, and system.

Background technique

During the login process of the third-party application, the electronic device can authenticate the login of the third-party application through the account application that has created a trusted account. In this way, after the user registers a trusted account of the account application, he can log in to other third-party applications through the trusted account, so that the user does not need to register multiple accounts, simplifying user operations and reducing user memory difficulty.

However, during the third-party application login process, the account application needs to be installed on the electronic device and the account application is in the logged-in state, so that the user can be provided with a one-click login experience to the third-party application. If the account application is not logged in, the user needs to re-enter the trusted account and password. After logging in to the account application, the login of the third-party application can be completed. The steps are relatively cumbersome. Moreover, if the account application is not installed in the electronic device, the login of the third-party application cannot be authenticated through the account application, causing the third-party application login to fail.

Contents of the invention

In order to solve the above technical problems, this application provides an application login method, electronic device and system. According to the technical solution provided by this application, during the process of logging in to the first application, the first electronic device can automatically obtain the login information of the second application in the second electronic device. Therefore, even if the second application is not installed in the first electronic device or the second application is not logged in, the first application can be logged in automatically through the second application in the second electronic device, thereby improving the user experience.

In order to achieve the above technical objectives, the embodiments of this application provide the following technical solutions:

The first aspect is to provide an application login method. The method includes: after detecting a first operation of a user logging in to a first application, the first electronic device determines a second application used for login authentication of the first application. The first electronic device determines a second electronic device used for login authentication of the first application, and the second electronic device is installed with the second application. The first electronic device obtains the login information of the second application in the second electronic device and logs in the first application.

In this way, when the second application is not installed in the first electronic device, or the second application in the first electronic device is not logged in, the first electronic device can also obtain the login information of the second application in the second electronic device. , realizing the login authentication of the first application in the first electronic device by the second application. This effectively simplifies user operations and improves user experience.

According to the first aspect, the first electronic device obtains the login information of the second application in the second electronic device and logs in the first application, including: the first electronic device sends the first information of the second electronic device to the server; The information includes one or more of the device identification of the second electronic device, the information of the first application, and the information of the second application. The first electronic device receives the login information of the second application determined by the server based on the first information, and logs in the first application.

The information about the first application includes, for example, the package name of the first application, and the information about the second application includes, for example, the package name of the second application.

Optionally, after determining the second electronic device, the first electronic device may send information to the server of the second application for querying the login information of the second application in the second electronic device. The server can determine the corresponding first application based on the information of the first application, and can determine the corresponding second application based on the information of the second application. Furthermore, based on the identification of the second electronic device, the server can determine whether the second electronic device logs into the second application and whether the second application authorizes the first application, and then determines the corresponding login information. Therefore, after receiving the login information, the first electronic device can determine whether it can directly synchronize the login status of the second application in the second electronic device and complete the login of the first application, or whether it needs to instruct the second electronic device to log in the second application. Authorization.

According to the first aspect, or any implementation of the above first aspect, the first electronic device obtains the login information of the second application in the second electronic device, and performs the login of the first application, including: The two electronic devices send second information, and the second information includes one or more of the device identification of the first electronic device, the information of the first application, and the information of the second application. The first electronic device receives the login information of the second application determined by the second electronic device based on the second information, and logs in the first application.

Optionally, the login authentication process of the second application does not require the participation of the server, for example, the trusted account of the second application is a stand-alone account, etc. Then, the first electronic device can directly send a request to the second electronic device for confirming the login status of the second application. second The application may respond to the request, locally complete the confirmation of the login status of the second application, and feed back the confirmation result of the login status of the second application to the first electronic device, such as feedback of login information.

In this way, the first electronic device can also determine the login information through interaction with the second electronic device. Then, based on the login information, it is determined whether the login status of the second application in the second electronic device can be directly synchronized to complete the login of the first application, or whether it is necessary to instruct the second electronic device to perform login authorization of the second application.

According to the first aspect, or any implementation of the above first aspect, when the second application has logged in and authorized the first application, the login information includes the account information of the second application; the first electronic device performs the first The login of the application includes: the first electronic device logs in to the first application according to the account information of the second application.

In this way, when the second application is not installed in the first electronic device, or the second application in the first electronic device is not logged in, the first electronic device can also synchronize the login status of the second application in the second electronic device, Complete the login authentication of the first application in the first electronic device by the second application. Effectively simplify user operations and improve user experience.

According to the first aspect, or any implementation of the above first aspect, when the second application is not logged in, the login information includes login authentication information; the first electronic device logs in the first application, including: the first electronic device The device instructs the second electronic device to complete the login authorization of the first application by the second application based on the login authentication information.

In this way, when the second application is not installed in the first electronic device, or the second application in the first electronic device is not logged in, and the second electronic device selected by the user for login authentication is not logged in to the second application, the second electronic device is not logged in. An electronic device can also complete the login of the first application by triggering the second electronic device to start the login authorization process of the second application. Effectively simplify user operations and improve user experience.

According to the first aspect, or any implementation of the above first aspect, the first electronic device instructs the second electronic device to complete the login authorization of the first application by the second application according to the login authentication information, including: the first electronic device according to Log in authentication information and send a login authentication request to the second electronic device. The first electronic device acquires the display data sent by the second electronic device in response to the login authentication request. The first electronic device displays the first login interface of the second application according to the display data. The first electronic device receives the first login data of the second application input by the user through the first login interface, and performs login authorization for the first application by the second application.

Optionally, the login of the second application of the second electronic device is directly completed on the first electronic device side through screen projection, thereby completing the login authentication of the first application in the first electronic device by the second application.

In this way, through screen projection, when a user operates one electronic device, he or she can complete the login authentication of the second application of the second electronic device on the first electronic device, effectively simplifying user operations.

According to the first aspect, or any implementation of the above first aspect, the first electronic device instructs the second electronic device to complete the login authorization of the first application by the second application according to the login authentication information, including: the first electronic device according to Log in authentication information and send a login authentication request to the second electronic device. The first electronic device receives the login result of the second application sent by the server to complete the login authorization of the second application to the first application; the login result is the login result determined by the server based on the obtained second login data sent by the second electronic device. , the second login data is user input data collected by the second electronic device in response to the login authentication request by displaying the second login interface of the second application.

In some scenarios, the user may be accustomed to completing the login of the second application through the second electronic device. Then, in the case that the second application is not installed in the first electronic device, or the second application in the first electronic device is not logged in, and the second electronic device selected by the user for login authentication has not logged in the second application, the second One electronic device can also trigger the second electronic device to start the login process of the second application. After completing the login of the second application on the second electronic device, the first electronic device automatically synchronizes the login status of the second application to complete the login authentication of the first application in the first electronic device by the second application. Effectively simplify user operations and improve user experience.

According to the first aspect, or any implementation of the above first aspect, the first electronic device determines a second electronic device used to perform login authentication for the first application, including: the first electronic device searches for a device with the second application installed. Trusted device. When the number of trusted devices is one, the first electronic device determines that the trusted device is the second electronic device. Or, when the number of trusted devices is multiple, the first electronic device displays a device selection interface, and the device selection interface is used to display multiple trusted devices. The first electronic device receives the user's second operation on the device selection interface and determines that the trusted device selected by the user is the second electronic device.

Optionally, the second application in different trusted devices may correspond to different trusted accounts, and the user may need to log in to the first application through one of the trusted devices. Therefore, the first electronic device can determine the second electronic device used to log in and authenticate the first application this time in response to the user operation.

In this way, the first electronic device can determine the second electronic device installed with the second application for login authentication according to the user's needs, thereby meeting the user's usage needs.

According to the first aspect, or any implementation of the above first aspect, the trusted device includes a first electronic device, and the first electronic device displays a device selection interface, including: the first electronic device displays a plurality of The first identification of the trusted device. The first identification includes one or more of the following: the login status of the second application, the device identification, the device name, the device nickname edited by the user, the system account, and the system account nickname.

In this way, the user can select a required trusted device among multiple trusted devices according to the display of the first electronic device to log in to the first application.

According to the first aspect, or any implementation manner of the first aspect above, the first electronic device displays a device selection interface, including: the first electronic device displays multiple trusted devices in order of priority on the device selection interface, The criteria for determining the priority order include one or more of the following: whether it is the first electronic device, whether the second application has been logged in, and whether the second application has been logged in recently.

In this way, when there are multiple trusted devices, the first electronic device displays multiple trusted devices in order of priority, which facilitates the user to find and select the required trusted device, and reduces user operation difficulty.

According to the first aspect, or any implementation of the above first aspect, before the first electronic device detects the first operation of the user logging in to the first application, the method further includes: the first electronic device and the second electronic device pass a preset Preset ways to form a trusted network include: the first electronic device and the second electronic device log in to the same first account, or a first communication connection is established between the first electronic device and the second electronic device. Communication connections include HyperTerminal connections.

In this way, by creating a trusted network, the security of data transmission between the first electronic device and the second electronic device is ensured, thereby ensuring the security of the first application and the second application, and avoiding leakage of user information.

The second aspect is to provide an application login method. The method includes: the second electronic device receives second information sent by the first electronic device, and the second information includes one or more of a device identification of the first electronic device, information of the first application, and information of the second application, The first application is an application used by the first electronic device to log in in response to a user instruction determined by the user's first operation, and the second application is an application used in the second electronic device for performing login authentication on the first application. The second electronic device determines the login information of the second application according to the second information. The second electronic device sends the login information of the second application to the first electronic device, and the login information of the second application is used by the first electronic device to log in the first application.

According to the second aspect, when the second application has been logged in and the first application has been authorized, the login information includes account information of the second application, and the account information is used by the first electronic device to log in to the first application.

According to the second aspect, or any implementation of the first aspect above, when the second application is not logged in, the login information includes login authentication information; the method further includes: the second electronic device receives the login response from the first electronic device Authentication information sent in the login authentication request. The second electronic device obtains the login data of the second application according to the login authentication request. The second electronic device sends login data to the server, and the login data is used by the first electronic device to complete the login authorization of the second application to the first application.

According to the second aspect, or any implementation of the above first aspect, the second electronic device obtains the login data of the second application according to the login authentication request, including: in response to the login authentication request, the second electronic device determines that the second application display data. The second electronic device sends display data to the first electronic device. The display data is used by the first electronic device to display the first login interface, receive the first login data of the second application input by the user, and perform login authorization for the first application by the second application. .

According to the second aspect, or any implementation of the above first aspect, the second electronic device obtains the login data of the second application according to the login authentication request, including: in response to the login authentication request, the second electronic device displays the second application The second login interface. The second electronic device receives login data input by the user on the second login interface.

According to the second aspect, or any implementation of the above first aspect, before the second electronic device receives the second information sent by the first electronic device, the method further includes: the second electronic device and the first electronic device pass a preset The way to form a trusted network, the preset way includes: the second electronic device and the first electronic device log in to the same first account, or the second electronic device and the first electronic device establish a first communication connection, the first communication Connections include HyperTerminal connections.

For the technical effects corresponding to the second aspect and any one of the implementation methods of the second aspect, please refer to the technical effects corresponding to the above-mentioned first aspect and any one of the implementation methods of the first aspect, which will not be described again here.

In a third aspect, an electronic device is provided. The electronic device includes: a processor and a memory. The memory is coupled to the processor. The memory is used to store computer program code. The computer program code includes computer instructions. When the processor reads the program from the memory, The computer instruction causes the electronic device to execute: after detecting the first operation of the user logging in to the first application, the first electronic device determines a second application used for login authentication of the first application. The first electronic device determines a second electronic device used for login authentication of the first application, and the second electronic device is installed with the second application. The first electronic device obtains the login information of the second application in the second electronic device and logs in the first application.

According to the third aspect, the first electronic device obtains the login information of the second application in the second electronic device and logs in the first application, including: the first electronic device sends the first information of the second electronic device to the server; The information includes one or more of the device identification of the second electronic device, the information of the first application, and the information of the second application. The first electronic device receives the login information of the second application determined by the server based on the first information, and logs in the first application.

According to the third aspect, or any implementation manner of the above third aspect, the first electronic device obtains the login information of the second application in the second electronic device and performs the login of the first application, including: The two electronic devices send second information, and the second information includes one or more of the device identification of the first electronic device, the information of the first application, and the information of the second application. The first electronic device receives the login information of the second application determined by the second electronic device based on the second information, and logs in the first application.

According to the third aspect, or any implementation of the above third aspect, when the second application has logged in and authorized the first application, the login information includes the account information of the second application; the first electronic device performs the first The login of the application includes: the first electronic device logs in to the first application according to the account information of the second application.

According to the third aspect, or any implementation of the above third aspect, when the second application is not logged in, the login information includes login authentication information; the first electronic device logs in the first application, including: the first electronic device The device instructs the second electronic device to complete the login authorization of the first application by the second application based on the login authentication information.

According to the third aspect, or any implementation of the above third aspect, the first electronic device instructs the second electronic device to complete the login authorization of the first application by the second application according to the login authentication information, including: the first electronic device according to the login authentication information. Log in authentication information and send a login authentication request to the second electronic device. The first electronic device acquires the display data sent by the second electronic device in response to the login authentication request. The first electronic device displays the first login interface of the second application according to the display data. The first electronic device receives the first login data of the second application input by the user through the first login interface, and performs login authorization for the first application by the second application.

According to the third aspect, or any implementation of the above third aspect, the first electronic device instructs the second electronic device to complete the login authorization of the first application by the second application according to the login authentication information, including: the first electronic device according to the login authentication information. Log in authentication information and send a login authentication request to the second electronic device. The first electronic device receives the login result of the second application sent by the server to complete the login authorization of the second application to the first application; the login result is the login result determined by the server based on the obtained second login data sent by the second electronic device. , the second login data is user input data collected by the second electronic device in response to the login authentication request by displaying the second login interface of the second application.

According to the third aspect, or any implementation of the above third aspect, the first electronic device determines the second electronic device used to perform login authentication for the first application, including: the first electronic device searches for the second electronic device installed with the second application. Trusted device. When the number of trusted devices is one, the first electronic device determines that the trusted device is the second electronic device. Or, when the number of trusted devices is multiple, the first electronic device displays a device selection interface, and the device selection interface is used to display multiple trusted devices. The first electronic device receives the user's second operation on the device selection interface and determines that the trusted device selected by the user is the second electronic device.

According to the third aspect, or any implementation manner of the above third aspect, the trusted device includes a first electronic device, and the first electronic device displays a device selection interface, including: the first electronic device displays a plurality of devices on the device selection interface. The first identification of the trusted device. The first identification includes one or more of the following: the login status of the second application, the device identification, the device name, the device nickname edited by the user, the system account, and the system account nickname.

According to the third aspect, or any implementation manner of the above third aspect, the first electronic device displays a device selection interface, including: the first electronic device displays multiple trusted devices in order of priority on the device selection interface, The criteria for determining the priority order include one or more of the following: whether it is the first electronic device, whether the second application has been logged in, and whether the second application has been logged in recently.

According to the third aspect, or any implementation of the above third aspect, when the processor reads the computer readable instructions from the memory, it also causes the electronic device to perform the following operations: the first electronic device and the second electronic device pass the preset Methods to form a trusted network, the preset methods include: the first electronic device and the second electronic device log in to the same first account, or the first electronic device and the second electronic device establish a first communication connection, the first communication Connections include HyperTerminal connections.

For technical effects corresponding to any implementation method in the third aspect and the second aspect, please refer to the above-mentioned third aspect and the third aspect. The technical effects corresponding to any of the implementation methods will not be described again here.

A fourth aspect provides an electronic device. The electronic device includes: a processor and a memory. The memory is coupled to the processor. The memory is used to store computer program codes. The computer program codes include computer instructions. When the processor reads the computer instructions from the memory, the electronic device executes: the second electronic device The device receives second information sent by the first electronic device. The second information includes one or more of the device identification of the first electronic device, information about the first application, and information about the second application. The first application is the first electronic device. The device determines an application to log in according to the user's instruction in response to the user's first operation, and the second application is an application in the second electronic device used to perform login authentication on the first application. The second electronic device determines the login information of the second application according to the second information. The second electronic device sends the login information of the second application to the first electronic device, and the login information of the second application is used by the first electronic device to log in the first application.

According to the fourth aspect, when the second application has been logged in and the first application has been authorized, the login information includes account information of the second application, and the account information is used by the first electronic device to log in to the first application.

According to the fourth aspect, or any implementation of the above first aspect, when the second application is not logged in, the login information includes login authentication information. When the processor reads the computer-readable instructions from the memory, it also causes the electronic device to perform the following operations: the second electronic device receives a login authentication request sent by the first electronic device in response to the login authentication information. The second electronic device obtains the login data of the second application according to the login authentication request. The second electronic device sends login data to the server, and the login data is used by the first electronic device to complete the login authorization of the second application to the first application.

According to the fourth aspect, or any implementation of the above first aspect, the second electronic device obtains the login data of the second application according to the login authentication request, including: in response to the login authentication request, the second electronic device determines that the second application display data. The second electronic device sends display data to the first electronic device. The display data is used by the first electronic device to display the first login interface, receive the first login data of the second application input by the user, and perform login authorization for the first application by the second application. .

According to the fourth aspect, or any implementation of the first aspect above, the second electronic device obtains the login data of the second application according to the login authentication request, including: in response to the login authentication request, the second electronic device displays the second application The second login interface. The second electronic device receives login data input by the user on the second login interface.

According to the fourth aspect, or any implementation of the above first aspect, when the processor reads the computer readable instructions from the memory, it also causes the electronic device to perform the following operations: the second electronic device and the first electronic device pass the preset The way to form a trusted network, the preset way includes: the second electronic device and the first electronic device log in to the same first account, or the second electronic device and the first electronic device establish a first communication connection, the first communication Connections include HyperTerminal connections.

For the technical effects corresponding to the fourth aspect and any one of the implementation methods of the fourth aspect, please refer to the technical effects corresponding to the above-mentioned first aspect and any one of the implementation methods of the first aspect, and will not be described again here.

In a fifth aspect, embodiments of the present application provide an application login system, which includes a first electronic device and a second electronic device. Wherein, the first electronic device is used to perform the method of the above-mentioned first aspect or any one of the first aspects, and the second electronic device is used to perform the method of the above-mentioned second aspect or any one of the second aspects.

For the technical effects corresponding to the fifth aspect and any one of the implementation methods of the fifth aspect, please refer to the technical effects corresponding to the above-mentioned first aspect and any one of the implementation methods of the first aspect, which will not be described again here.

In a sixth aspect, embodiments of the present application provide an electronic device that has the function of implementing the application login method as described in the above first aspect and any possible implementation manner; or, the electronic device has the function of implementing The function of applying the login method as described in the above second aspect and any possible implementation manner thereof. This function can be implemented by hardware, or can be implemented by hardware and corresponding software. The hardware or software includes one or more modules corresponding to the above functions.

For the technical effects corresponding to the sixth aspect and any one of the implementation methods of the sixth aspect, please refer to the technical effects corresponding to the above-mentioned first aspect and any one of the implementation methods of the first aspect, which will not be described again here.

In a seventh aspect, a computer-readable storage medium is provided. The computer-readable storage medium stores a computer program (which may also be referred to as instructions or codes). When the computer program is executed by an electronic device, it causes the electronic device to perform the method of the first aspect or any one of the embodiments of the first aspect; or , causing the electronic device to perform the second aspect or the method of any one of the implementation modes of the second aspect.

For the technical effects corresponding to the seventh aspect and any one of the implementation methods of the seventh aspect, please refer to the technical effects corresponding to the above-mentioned first aspect and any one of the implementation methods of the first aspect, and will not be described again here.

In an eighth aspect, embodiments of the present application provide a computer program product. When the computer program product is run on an electronic device, causing the electronic device to perform the first aspect or the method of any one of the first aspect implementations; or, causing the electronic device to perform the second aspect or the method of any one of the second aspect implementations.

For the technical effects corresponding to the eighth aspect and any one of the implementation methods of the eighth aspect, please refer to the technical effects corresponding to the above-mentioned first aspect and any one of the implementation methods of the first aspect, and will not be described again here.

In a ninth aspect, embodiments of the present application provide a circuit system. The circuit system includes a processing circuit. The processing circuit is configured to execute the method of the first aspect or any one of the implementation modes of the first aspect; or, the processing circuit is configured to execute The method of the second aspect or any one of the second aspects.

For the technical effects corresponding to the ninth aspect and any one of the implementation methods of the ninth aspect, please refer to the technical effects corresponding to the above-mentioned first aspect and any one of the implementation methods of the first aspect, and will not be described again here.

In a tenth aspect, embodiments of the present application provide a chip system, including at least one processor and at least one interface circuit. The at least one interface circuit is used to perform transceiver functions and send instructions to at least one processor. When at least one processor When executing instructions, at least one processor performs the first aspect or the method of any one implementation of the first aspect; or, at least one processor performs the second aspect or the method of any one implementation of the second aspect.

For the technical effects corresponding to the tenth aspect and any one of the implementation methods of the tenth aspect, please refer to the technical effects corresponding to the above-mentioned first aspect and any one of the implementation methods of the first aspect, which will not be described again here.

Description of drawings

Figure 1A is a schematic diagram 1 of the interface provided by the embodiment of the present application;

Figure 1B is the second schematic diagram of the interface provided by the embodiment of the present application;

Figure 1C is a schematic diagram three of the interface provided by the embodiment of the present application;

Figure 2 is a schematic diagram of a communication system applied by an application login method provided by an embodiment of the present application;

Figure 3A is a schematic diagram of the hardware structure of a first electronic device or a second electronic device provided by an embodiment of the present application;

Figure 3B is a schematic block diagram of the software structure of the first electronic device and the second electronic device provided by the embodiment of the present application;

Figure 4 is a schematic flowchart 1 of the application login method provided by the embodiment of the present application;

Figure 5 is a schematic diagram 1 of module interaction provided by the embodiment of this application;

Figure 6 is a schematic diagram 4 of the interface provided by the embodiment of the present application;

Figure 7A is a schematic flowchart 2 of the application login method provided by the embodiment of the present application;

Figure 7B is a schematic flowchart three of the application login method provided by the embodiment of the present application;

Figure 8A is a schematic diagram 5 of the interface provided by the embodiment of the present application;

Figure 8B is a schematic diagram 6 of the interface provided by the embodiment of the present application;

Figure 8C is a schematic seventh interface diagram provided by an embodiment of the present application;

Figure 8D is a schematic diagram 8 of the interface provided by the embodiment of the present application;

Figure 9 is a schematic diagram 9 of the interface provided by the embodiment of the present application;

Figure 10 is a schematic flowchart 4 of the application login method provided by the embodiment of the present application;

Figure 11 is a schematic diagram 2 of module interaction provided by the embodiment of this application;

Figure 12 is a schematic diagram 10 of the interface provided by the embodiment of the present application;

Figure 13 is a schematic diagram 11 of the interface provided by the embodiment of this application;

Figure 14 is a schematic flow chart 5 of the application login method provided by the embodiment of the present application;

Figure 15 is a schematic diagram of the interface provided by the embodiment of the present application;

Figure 16 is a schematic structural diagram of a first electronic device provided by an embodiment of the present application;

Figure 17 is a schematic structural diagram of a second electronic device provided by an embodiment of the present application.

Detailed ways

The technical solutions in the embodiments of the present application will be described below with reference to the accompanying drawings in the embodiments of the present application. In the description of the embodiments of the present application, the terms used in the following embodiments are only for the purpose of describing specific embodiments and are not intended to limit the present application. As used in the specification and appended claims of this application, the singular expressions "a,""an,""the,""above,""the" and "the" are intended to include For example, the expression "one or more" unless the context clearly indicates otherwise. It should also be understood that in the following embodiments of this application, "at least one" and "one or more" refer to one or more than two (including two).

Reference in this specification to "one embodiment" or "some embodiments" or the like means that a particular feature, structure or characteristic described in connection with the embodiment is included in one or more embodiments of the application. Therefore, the phrases "in one embodiment", "in some embodiments", "in other embodiments", "in other embodiments", etc. appearing in different places in this specification are not necessarily References are made to the same embodiment, but rather to "one or more but not all embodiments" unless specifically stated otherwise. The terms “including,” “includes,” “having,” and variations thereof all mean “including but not limited to,” unless otherwise specifically emphasized. The term "connected" includes both direct and indirect connections unless otherwise stated. “First” and “second” are used for descriptive purposes only and cannot be understood as indicating or implying relative importance or implicitly indicating the quantity of indicated technical features.

In the embodiments of this application, words such as "exemplarily" or "for example" are used to represent examples, illustrations or explanations. Any embodiment or design described as "exemplary" or "such as" in the embodiments of the present application is not to be construed as being preferred or advantageous over other embodiments or designs. Rather, the use of the words "exemplarily" or "for example" is intended to present the relevant concepts in a concrete manner.

In some scenarios, multiple applications are installed in the electronic device to provide users with different functional experiences. Generally, the application provides a login service. After the user logs in, the application can obtain the user data, thereby providing the user with a better user experience. However, if each application requires the user to register an account, the user will need to remember a large number of registered accounts and passwords, which will affect the user experience. Therefore, some third-party applications provide services that can complete login authentication through applications that have created trusted accounts during the login process. In this way, trusted accounts with limited user memory can complete the login of other third-party applications, reducing user operation difficulty and improving user experience.

Optionally, applications that have created trusted accounts include Huawei applications, etc. The corresponding trusted account is, for example, Huawei account, Among them, users can register multiple trusted accounts corresponding to the same application. For example, a user registers multiple accounts with different mobile phone numbers

It should be noted that, for the convenience of description, the following takes the third-party application as the first application, the application that has created a trusted account as the second application, and the second application can be used to perform login authentication for the first application. For the first application The login process is introduced in detail.

Exemplarily, as shown in (a) of FIG. 1A , the electronic device displays a login authentication interface 101 in response to a user's request to log in to a first application (such as A video application). After detecting the user's click on the login control 11, the electronic device determines that the user has instructed the second application corresponding to the login control 11 (such as ) Complete login authentication. The electronic device determines that the second application is installed in the electronic device and the second application is in a logged-in state, and may display interface 102 as shown in (b) of Figure 1A . On the interface 102, after the electronic device detects that the user clicks on the allow control 12, the electronic device can directly log in to the first application through the second application. In this way, users can log in to third-party applications with one click through simple operations, reducing user operation difficulty and improving user experience.

However, if the second application installed in the electronic device is not in the logged-in state, the user still needs to enter the trusted account number and password of the second application during the login process of the first application, and the operation is still relatively cumbersome.

Exemplarily, as shown in interface 103 in (a) of Figure 1B , during the process of logging in to the first application (such as video application A), the electronic device detects the user's click on the login control 13 and determines that the electronic device is installed with The second application corresponding to the login control 13 (such as ), but the second application is in a non-login state, the second application login authorization interface 104 shown in (b) in Figure 1B may be displayed. The electronic device receives the account name and password entered by the user on the interface 104, and after detecting the user's click on the login control 14, sends the received account name and password to the server corresponding to the second application for authentication. After the electronic device determines that the account name and password are correct according to the received feedback signal sent by the server, the electronic device can display the interface 105 as shown in (c) in Figure 1B. On the interface 105, after the electronic device detects the user's click on the allow control 15, it can determine that the login authentication of the first application by the second application is completed.

In the scenarios illustrated in FIGS. 1A and 1B above, the second application needs to be installed in the electronic device to complete the login authentication of the first application, which places higher requirements on the electronic device.

In some examples, the second application may not be installed in the electronic device. Instead, after the other electronic device logs in to the second application, the second application of the other electronic device scans the authorization QR code displayed by the first application in the electronic device. Complete the login authentication of the first application.

For example, in the interface 106 shown in (a) in Figure 1C, during the process of logging in to the first application (such as video application A), the electronic device detects the user's click on the login control 16 and determines that the electronic device is not installed. The second application corresponding to the login control 16 can display the interface 107 as shown in (b) in Figure 1C. A QR code and prompt information 17 are displayed on the interface 107 to prompt the user to scan the displayed QR code through a second application in other electronic devices to complete authorized login. As shown in Figure 1C, use After the user logs in to the second application in other electronic devices, he can scan the QR code through the second application in other electronic devices to complete the login authentication of the first application on other electronic devices.

It can be seen that during the above QR code verification login process, the user needs to operate multiple electronic devices, and the electronic device used for scanning is required to be equipped with a camera, and the second application installed in the electronic device used for scanning is in the logged-in state . The user operations are cumbersome and require high electronic equipment for scanning, which affects the user experience.

Therefore, embodiments of the present application provide an application login method. During the process of logging in to the first application, the first electronic device can automatically synchronize the login status of the second application in the second electronic device. Therefore, even if the second application is not installed in the first electronic device or the second application is not logged in, the login authentication of the first application through the second application can be automatically completed, thereby improving the user experience.

FIG. 2 is a schematic diagram of a communication system in which the application login method provided by the embodiment of the present application is applied. As shown in FIG. 2 , the communication system includes a first electronic device 100 , a second electronic device 200 , and a server 300 .

Optionally, the first electronic device 100 or the second electronic device 200 may be, for example, a mobile phone, a tablet computer, a notebook computer, an ultra-mobile personal computer (UMPC), a large-screen device, a netbook, or a personal digital assistant ( terminal devices such as personal digital assistant (PDA), wearable devices, artificial intelligence (AI) devices, etc., the operating systems installed on the first electronic device 100 or the second electronic device 200 include but are not limited to or other operating systems. This application does not limit the specific type of the first electronic device 100 or the second electronic device 200 or the operating system installed.

Optionally, the server 300 may be a device or network device with computing functions such as a cloud server or a network server. The server 300 may be one server, a server cluster composed of multiple servers, or a cloud computing service center. Optionally, the server 300 is a server corresponding to the second application, and is used to perform login authentication for the second application of the electronic device.

In some examples, the first electronic device 100 is installed with a third-party application (ie, the first application) for login authentication, and the second electronic device 200 is installed with the second application for login authentication of the third-party application. Optionally, the number of the second electronic device 200 is one or more. As shown in FIG. 2 , the second electronic device 200 includes the second electronic device 1 , the second electronic device 2 , and the second electronic device 3 .

In some examples, the first electronic device 100 and the second electronic device 200 form a trusted network. Electronic devices in a trusted network can determine other electronic devices as trusted devices, and use other electronic devices to complete login authentication for third-party applications installed in themselves. Optionally, electronic devices in a trusted network log in to the same account (such as a Huawei account); or, electronic devices in a trusted network can search for other electronic devices through the HyperTerminal application.

Optionally, the first electronic device 100 can also establish a trusted network through Pengpeng, Bluetooth, device-to-device (D2D), and other methods.

For example, FIG. 3A shows a schematic structural diagram of the first electronic device 100 or the second electronic device 200 .

The first electronic device 100 or the second electronic device 200 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, and a power management module 141. Battery 142, antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, audio module 170, sensor module 180, button 190, motor 191, indicator 192, camera 193, display screen 194, and user identification module (subscriber identification module, SIM card interface 195, etc.

It can be understood that the structure illustrated in the embodiment of the present application does not constitute a specific limitation on the first electronic device 100 or the second electronic device 200 . In other embodiments of the present application, the first electronic device 100 or the second electronic device 200 may include more or less components than shown in the figures, or combine some components, or separate some components, or different components. layout. The components illustrated may be implemented in hardware, software, or a combination of software and hardware.

For example, when the first electronic device 100 is a PC, the first electronic device 100 may not include the mobile communication module 150 and the SIM card interface 195 .

The processor 110 may include one or more processing units. For example, the processor 110 may include an application processor (application processor, AP), a modem processor, a graphics processing unit (GPU), and an image signal processor. (image signal processor, ISP), controller, video codec, digital signal processor (digital signal processor, DSP), baseband processor, and/or neural network processor (neural-network processing unit, NPU), etc. Among them, different processing units can be independent devices or integrated in one or more processors.

The processor 110 may also be provided with a memory for storing instructions and data. In some embodiments, processor 110 The memory is cache memory. This memory may hold instructions or data that have been recently used or recycled by processor 110 . If the processor 110 needs to use the instructions or data again, it can be called directly from the memory. Repeated access is avoided and the waiting time of the processor 110 is reduced, thus improving the efficiency of the system.

The USB interface 130 is an interface that complies with the USB standard specification, and may be a Mini USB interface, a Micro USB interface, a USB Type C interface, etc. The USB interface 130 can be used to connect a charger to charge the first electronic device 100 or the second electronic device 200, and can also be used to transmit data between the first electronic device 100 or the second electronic device 200 and peripheral devices. It can also be used to connect headphones to play audio through them. This interface can also be used to connect other electronic devices, such as AR devices, etc.

The charging management module 140 is used to receive charging input from the charger. Among them, the charger can be a wireless charger or a wired charger. While the charging management module 140 charges the battery 142, it can also provide power to the electronic device through the power management module 141.

The power management module 141 is used to connect the battery 142, the charging management module 140 and the processor 110. The power management module 141 receives input from the battery 142 and/or the charging management module 140 and supplies power to the processor 110, the internal memory 121, the display screen 194, the camera 193, the wireless communication module 160, and the like. In some other embodiments, the power management module 141 may also be provided in the processor 110 . In other embodiments, the power management module 141 and the charging management module 140 may also be provided in the same device.

The wireless communication function of the first electronic device 100 or the second electronic device 200 can be implemented through the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, the modem processor and the baseband processor.

Antenna 1 and Antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in the first electronic device 100 or the second electronic device 200 may be used to cover a single or multiple communication frequency bands. Different antennas can also be reused to improve antenna utilization. For example: Antenna 1 can be reused as a diversity antenna for a wireless LAN. In other embodiments, antennas may be used in conjunction with tuning switches.

The mobile communication module 150 may provide applications on the first electronic device 100 or the second electronic device 200 including

2G/3G/4G/5G and other wireless communication solutions. The mobile communication module 150 may include at least one filter, switch, power amplifier, low noise amplifier (LNA), etc. The mobile communication module 150 can receive electromagnetic waves through the antenna 1, perform filtering, amplification and other processing on the received electromagnetic waves, and transmit them to the modem processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modem processor and convert it into electromagnetic waves through the antenna 1 for radiation. In some embodiments, at least part of the functional modules of the mobile communication module 150 may be disposed in the processor 110 . In some embodiments, at least part of the functional modules of the mobile communication module 150 and at least part of the modules of the processor 110 may be provided in the same device.

The wireless communication module 160 may provide a wireless local area network (WLAN) (such as a wireless fidelity (Wi-Fi) network), Bluetooth ( bluetooth, BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared technology (infrared, IR) and other wireless communications solution. The wireless communication module 160 may be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2 , frequency modulates and filters the electromagnetic wave signals, and sends the processed signals to the processor 110 . The wireless communication module 160 can also receive the signal to be sent from the processor 110, frequency modulate it, amplify it, and convert it into electromagnetic waves through the antenna 2 for radiation.

In some embodiments, the antenna 1 of the first electronic device 100 or the second electronic device 200 is coupled to the mobile communication module 150, and the antenna 2 is coupled to the wireless communication module 160, so that the first electronic device 100 or the second electronic device 200 can pass Wireless communications technology communicates with networks and other devices. The wireless communication technology may include global system for mobile communications (GSM), general packet radio service (GPRS), code division multiple access (CDMA), broadband Code division multiple access (wideband code division multiple access, WCDMA), time division code division multiple access (time-division code division multiple access, TD-SCDMA), long term evolution (long term evolution, LTE), BT, GNSS, WLAN, NFC , FM, and/or IR technology, etc. The GNSS may include global positioning system (GPS), global navigation satellite system (GLONASS), Beidou navigation satellite system (BDS), quasi-zenith satellite system (quasi) -zenith satellite system (QZSS) and/or satellite based augmentation systems (SBAS).

The first electronic device 100 or the second electronic device 200 implements display through a GPU, a display screen 194, an application processor, etc. Function. The GPU is an image processing microprocessor and is connected to the display screen 194 and the application processor. GPUs are used to perform mathematical and geometric calculations for graphics rendering. Processor 110 may include one or more GPUs that execute program instructions to generate or alter display information.

The display screen 194 is used to display images, videos, etc. Display 194 includes a display panel. The display panel can use a liquid crystal display (LCD), such as an organic light-emitting diode (OLED), an active matrix organic light emitting diode or an active matrix organic light emitting diode (active-matrix). Production and manufacturing of organic light emitting diodes (AMOLED), flexible light-emitting diodes (FLED), Mini-led, Micro-led, Micro-oled, quantum dot light emitting diodes (QLED), etc. . In some embodiments, the first electronic device 100 or the second electronic device 200 may include 1 or N display screens 194, where N is a positive integer greater than 1.

In some examples, the first electronic device 100 displays the login authentication interface of the third-party application through the display screen 194 in response to the user operation, and determines the second application used to perform login authentication for the third-party application. The first electronic device 100 determines the second electronic device 200 in the trusted network that can be used to complete third-party application login authentication. Afterwards, the first electronic device 100 may determine the authentication result of the second application of the second electronic device 200 through interaction with the server 300 .

If the second electronic device 200 has logged into the second application, the first electronic device 100 can directly synchronize the login status of the second application and automatically complete the login authentication of the third-party application.

If the second electronic device 200 has not logged into the second application, the first electronic device 100 may send a login authentication request to the second electronic device 200 to obtain the authentication interface display data sent by the second electronic device 200, so as to obtain the authentication interface display data according to the authentication interface display data. The login authentication interface of the second application is displayed on the display screen 194 to complete the login authentication of the third-party application.

The indicator 192 may be an indicator light, which may be used to indicate charging status, power changes, or may be used to indicate messages, missed calls, notifications, etc.

Camera 193 is used to capture still images or video. The object passes through the lens to produce an optical image that is projected onto the photosensitive element. The photosensitive element can be a charge coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The photosensitive element converts the optical signal into an electrical signal, and then passes the electrical signal to the ISP to convert it into a digital image signal. ISP outputs digital image signals to DSP for processing. DSP converts digital image signals into standard RGB, YUV and other format image signals. In some embodiments, the first electronic device 100 or the second electronic device 200 may include 1 or N cameras 193, where N is a positive integer greater than 1.

The external memory interface 120 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the first electronic device 100 or the second electronic device 200 . The external memory card communicates with the processor 110 through the external memory interface 120 to implement the data storage function. Such as saving music, videos, etc. files in external memory card.

Internal memory 121 may be used to store computer executable program code, which includes instructions. The internal memory 121 may include a program storage area and a data storage area. Among them, the stored program area can store an operating system, at least one application program required for a function (such as a sound playback function, an image playback function, etc.). The storage data area may store data created during use of the first electronic device 100 or the second electronic device 200 (such as audio data, phone book, etc.). In addition, the internal memory 121 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, universal flash storage (UFS), etc. The processor 110 executes various functional applications and data processing of the first electronic device 100 or the second electronic device 200 by executing instructions stored in the internal memory 121 and/or instructions stored in a memory provided in the processor.

The audio module 170 is used to convert digital audio information into analog audio signal output, and is also used to convert analog audio input into digital audio signals. Audio module 170 may also be used to encode and decode audio signals. The audio module 170 may include a speaker, a receiver, a microphone, a headphone interface, and an application processor to implement audio functions.

The sensor module 180 may include a pressure sensor, a gyroscope sensor, an air pressure sensor, a magnetic sensor, an acceleration sensor, a distance sensor, a proximity light sensor, a fingerprint sensor, a temperature sensor, a touch sensor, an ambient light sensor, a bone conduction sensor, and the like.

Touch sensor, also known as "touch device". The touch sensor can be disposed on the display screen 194, and the touch sensor and the display screen 194 form a touch screen, which is also called a "touch screen". Touch sensors are used to detect touches on or near them. The touch sensor can pass the detected touch operation to the application processor to determine the touch event type. Visual output related to the touch operation may be provided through display screen 194 . In other embodiments, the touch sensor may also be disposed on the surface of the first electronic device 100 or the second electronic device 200 at a location different from that of the display screen 194 .

The buttons 190 include a power button, a volume button, etc. Key 190 may be a mechanical key. It can also be a touch button.

The motor 191 can generate vibration prompts. The motor 191 can be used for vibration prompts for incoming calls and can also be used for touch vibration feedback.

The SIM card interface 195 is used to connect a SIM card. The first electronic device 100 or the second electronic device 200 may support 1 or N SIM card interfaces, where N is a positive integer greater than 1.

The software system of the first electronic device 100 or the second electronic device 200 may adopt a layered architecture, an event-driven architecture, a microkernel architecture, a microservice architecture, or a cloud architecture. This embodiment of the present application takes the Android system with a layered architecture as an example to illustrate the software structures of the first electronic device 100 and the second electronic device 200 .

FIG. 3B is a software structure block diagram of the first electronic device 100 and the second electronic device 200 according to the embodiment of the present application.

The layered architecture divides the software into several layers, and each layer has clear roles and division of labor. The layers communicate through software interfaces. In some embodiments, the Android system is divided into four layers, from top to bottom: application layer, application framework layer, Android runtime and system libraries, and kernel layer.

The application layer can include a series of application packages.

As shown in Figure 3B, the application package can include applications such as application market, camera, calendar, music, gallery, map, call, and video.

Optionally, as shown in FIG. 3B , the first application is installed in the first electronic device 100 , and the second application is installed in the second electronic device 200 .

The application framework layer provides an application programming interface (API) and programming framework for applications in the application layer. The application framework layer includes some predefined functions.

As shown in Figure 3B, the application framework layer can include content providers, resource managers, view systems, etc.

Content providers are used to store and retrieve data and make this data accessible to applications. Said data can include videos, images, audio, calls made and received, browsing history and bookmarks, phone books, etc.

The resource manager provides various resources to applications, such as localized strings, icons, pictures, layout files, video files, etc.

The view system includes visual controls, such as controls that display text, controls that display pictures, etc. A view system can be used to build applications. The display interface can be composed of one or more views. For example, a display interface including a text message notification icon may include a view for displaying text and a view for displaying pictures.

Optionally, as shown in FIG. 3B , the application framework layer of the first electronic device 100 may also include, for example, a distributed device management system (distributed device management system, DMS) and an application management service (application management service, AMS).

In some examples, the first electronic device 100 can obtain information about electronic devices in the trusted network through DMS. Optionally, after determining that the first application needs to be logged in and authenticated through the second application, the first electronic device 100 can query the trusted device (such as the second electronic device 200) that has the second application installed in the trusted network through DMS. ).

In some examples, after determining that the trusted device used for login authentication for the first application is the second electronic device 200, the first electronic device 100 starts the login authentication interface of the second application through the AMS. In the subsequent process of login authentication for the first application in the first electronic device 100 through the second application in the second electronic device 200, the first electronic device 100 can manage the life cycle of the second application through the AMS.

Optionally, as shown in FIG. 3B , the application framework layer of the second electronic device 200 may also include, for example, a package management service (package manager service, PMS) and an AMS.

In some examples, after determining the second electronic device 200 for login authentication of the first application, the first electronic device 100 sends a login authentication request to the second electronic device 200 . Correspondingly, after receiving the login authentication request, the second electronic device 200 queries the second application in the second electronic device 200 through the PMS. Afterwards, the second electronic device 200 starts the second application through the AMS background to obtain the second application login authentication interface display data to facilitate subsequent login authentication of the first application.

Android Runtime includes core libraries and virtual machines. Android Runtime is responsible for the scheduling and management of the Android system.

The core library contains two parts: one is the functional functions that need to be called by the Java language, and the other is the core library of Android.

The application layer and application framework layer run in virtual machines. The virtual machine executes the java files of the application layer and application framework layer into binary files. The virtual machine is used to perform object life cycle management, stack management, thread management, security and exception management, and garbage collection and other functions.

System libraries can include multiple functional modules. For example: surface manager (surface manager), media libraries (Media Libraries), three-dimensional graphics processing libraries (for example: OpenGL ES), two-dimensional graphics engines (for example: SGL), etc.

The surface manager is used to manage the display subsystem and provides the fusion of 2D and 3D layers for multiple applications.

The media library supports playback and recording of a variety of commonly used audio and video formats, as well as static image files, etc. The media library can support a variety of audio and video encoding formats, such as: MPEG4, H.264, MP3, AAC, AMR, JPG, PNG, etc.

The 3D graphics processing library is used to implement 3D graphics drawing, image rendering, composition, and layer processing.

2D Graphics Engine is a drawing engine for 2D drawing.

The kernel layer is the layer between hardware and software. The kernel layer contains at least display driver, camera driver, audio driver, and sensor driver.

The following takes the first electronic device 100 as a first electronic device, the second electronic device 200 as a second electronic device, and the server 300 as a server for a second application that performs login authentication on the first application (ie, a third-party application). , describing the application login method provided by the embodiment of this application.

For example, FIG. 4 is a schematic flowchart of an application login method provided by an embodiment of the present application. As shown in Figure 4, the method includes the following steps.

S401. After detecting the user's operation of logging in to the first application, the first electronic device determines a second application used for login authentication of the first application.

In some examples, the first application is a third-party application, and the first electronic device can complete login authentication for the first application through the second application during the login process of the third-party application. The second application is an application for which the user has completed trusted account registration, and the number of trusted accounts corresponding to the second application is one or more.

Optionally, after detecting the user's operation of logging in to the first application, the first electronic device determines that multiple applications can authenticate the login of the first application, displays a second application selection interface, and determines multiple applications based on the user's selection. The second application in the application is used to perform login authentication for the first application. Alternatively, the first application is pre-configured with a second application used for login authentication. After detecting the user's operation of logging in to the first application, the first electronic device can automatically determine the second application used for login authentication of the first application.

For example, as shown in (a) of FIG. 6 , the first electronic device displays the login authentication interface 601 in response to the user's request to log in to the video application A (ie, the first application). After detecting the user's click on the login control 61 , the first electronic device can determine that the second application instructed by the user to perform login authentication for the A video application is the application corresponding to the login control 61 .

S402. The first electronic device queries the trusted device in the trusted network where the second application is installed.

In some examples, after determining the second application, the first electronic device may query the trusted device in the trusted network where the second application is installed. Wherein, the second application in the trusted device is in a logged-in state or a non-login state.

Optionally, the first electronic device may query the trusted device in the trusted network where the second application is installed based on the package name, component name, etc. of the second application. For example, the first electronic device queries the trusted device on which the second application is installed in the trusted network through various methods such as interacting with electronic devices in the trusted network, sending broadcast information in the trusted network, etc. .

For example, as shown in FIG. 5 , after detecting the user's operation of logging in to the first application 511 , the first electronic device 51 determines the second application used to perform login authentication on the first application 511 . Afterwards, the first electronic device 51 obtains the information of the electronic devices in the trusted network through the distributed device management system (DMS) 512, thereby querying the trusted device on which the second application is installed.

S403. The first electronic device determines the second electronic device used for login authentication.

In some examples, the number of trusted devices with the second application installed in the trusted network is one or more, and the first electronic device needs to determine the second electronic device that is ultimately used to perform login authentication for the first application.

Optionally, as shown in FIG. 7A , step S403 after step S402 may include steps S4031 to S4034.

S4031. The first electronic device determines that multiple electronic devices in the trusted network have the second application installed. If not, execute step S4032; if yes, execute step S4033.

In some examples, if the first electronic device determines through DMS that there is only one trusted device in the trusted network with the second application installed, it can automatically complete the login authentication of the first application through the trusted device (ie, perform step S4032 ). If the first electronic device determines through the DMS that the trusted network includes multiple trusted devices with the second application installed, the second electronic device that performs login authentication for the first application can be determined according to the user's selection (ie, step S4033 is performed) .

S4032. The first electronic device determines the only second electronic device used for login authentication.

In some examples, the first electronic device obtains information about electronic devices in the trusted network through DMS and determines that there is only one The second application is installed in the trusted device. Then, the first electronic device may determine that the trusted device is the only second electronic device used for login authentication.

S4033. The first electronic device displays multiple electronic devices that can be used for login authentication.

In some examples, the first electronic device obtains information about electronic devices in the trusted network through the DMS, and determines that there are multiple trusted devices in the trusted network with the second application installed. Then, the first electronic device may display the searched multiple trusted devices for receiving the user's operation of selecting the trusted device.

Optionally, the trusted devices with the second application installed that are searched by the first electronic device include the first electronic device.

Optionally, the first electronic device may display one or more of the device identification (identity, ID), device name, user-edited device nickname, system account, system account nickname, etc. of the searched trusted device to facilitate Users differentiate between different trusted devices. For example, in the interface 602 shown in (b) of Figure 6 , the device 1, device 2, and device 3 displayed by the first electronic device are the devices of trusted devices searched by the first electronic device in the trusted network. name.

Optionally, the first electronic device may display multiple trusted devices for login authentication in order of priority to facilitate user selection. The criteria for determining the priority order include, for example: whether it is the first electronic device, whether the second application has been logged in, whether the second application has been logged in recently, etc.

Exemplarily, as shown in FIG. 8A , the first electronic device displays multiple searched trusted devices with the second application installed on the interface 801 . Optionally, on the interface 801, the first electronic device can separately display the local selection controls and the selection controls of other trusted devices to facilitate user operations.

As another example, in the interface 802 shown in FIG. 8B , the first electronic device searches for multiple trusted devices with the second application installed, and can obtain the login status of the second application in the trusted devices. For example, if the second application is a Huawei application, the first electronic device can obtain the login status of the Huawei account of the Huawei application of the trusted device. Then, the first electronic device may display the login status of the second application of each trusted device. As shown in FIG. 8B , the first electronic device preferentially displays the device 1 that has logged in to the second application. In this way, the user can select a trusted device that has logged in to the second application to complete the login authentication of the first application without having to enter the account number and password, thus simplifying the user operation.

As another example, in interface 803 shown in FIG. 8C , the first electronic device searches for multiple trusted devices with the second application installed, and can determine whether the trusted device has recently logged in to the second application. Then, the first electronic device can mark the trusted device among the trusted devices that has recently logged in to the second application to facilitate the user's selection. As shown in FIG. 8B , the first electronic device preferentially displays the device 1 that has recently logged into the second application.

As another example, in the above-mentioned step S401, after the first electronic device detects the operation of the user to log in to the first application, it does not need to determine the second application first, but directly searches for the information installed in the trusted network for the first application. Trusted device for applications that perform login authentication. As shown in interface 804 in Figure 8D, the first electronic device displays the searched trusted devices and the second applications in each trusted device that can be used to log in to the first application. For example, device 1 is installed with For login authentication Afterwards, the first electronic device can directly determine the second electronic device and the second application used for login authentication of the first application according to the user's selection operation. In this way, the user does not need to select the second application first and then the second electronic device, thereby reducing user operations.

It should be noted that in the scenarios shown in FIGS. 8B to 8D , the trusted devices displayed by the first electronic device may also include the first electronic device.

S4034. The first electronic device receives the user's operation of selecting the electronic device and determines the second electronic device used for login authentication.

In some examples, after detecting the user's operation of selecting an electronic device among multiple trusted devices, the first electronic device determines, based on the user's operation, the second electronic device indicated by the user for login authentication.

Exemplarily, as shown in (a) of FIG. 6 , in response to the user clicking the login control 61 , the first electronic device searches for multiple available second applications installed with the second application corresponding to the login control 61 in the trusted network. letter equipment. As shown in (b) of FIG. 6 , the first electronic device displays the identifications of multiple searched trusted devices (such as device 1, device 2, and device 3). Afterwards, after detecting the user's operation of clicking the control 62, the first electronic device can determine that the trusted device selected by the user for login authentication for the A video application is device 1.

In this way, through the above steps, the first electronic device can determine the second electronic device used for login authentication.

S404. The first electronic device sends the second electronic device information to the server of the second application.

In some examples, the first electronic device may obtain the second electronic device information during the process of querying the trusted device in the trusted network where the second application is installed in step S402. Optionally, the second electronic device information includes, for example, a device unique identifier (unique device identifier, UDID). Optionally, the device information of the second electronic device may also include, for example, information about the second application (such as the package name of the second application), information about the first application (such as the package name of the first application), etc., for The server confirms the authentication result of the second application in the second electronic device.

In some examples, after determining the second electronic device, the first electronic device may send the second electronic device information to the server of the second application through various methods such as Wi-Fi network and cellular network.

Optionally, the login authentication process of the second application does not require the participation of the server, for example, the trusted account of the second application is a stand-alone account, etc. Then, the first electronic device can directly send a request to the second electronic device for confirming the login status of the second application. The second application may respond to the request, locally complete the confirmation of the login status of the second application, and feed back the confirmation result of the login status of the second application to the first electronic device.

For example, the first electronic device displays prompt information, prompting the user to obtain the login status of the second application in the second electronic device by touching or other methods.

S405. The server of the second application determines the authentication result of the second application in the second electronic device.

In some examples, the server of the second application determines the second electronic device based on the second electronic device information. Afterwards, the server of the second application determines the authentication result of the second application in the second electronic device. For example, the authentication result includes that the second electronic device has logged into the second application, the login authentication of the second application of the second electronic device has expired, the second electronic device has not logged into the second application, etc.

S406. The server of the second application sends the authentication result of the second application in the second electronic device to the first electronic device.

In some examples, after determining the authentication result, the server of the second application sends the authentication result of the second application in the second electronic device to the first electronic device. Correspondingly, the first electronic device obtains the authentication result.

For example, as shown in FIG. 5 , the first electronic device 51 sends the information of the second electronic device 53 to the server 52 of the second application, such as the UDID of the second electronic device 53 (ie, step S404). The server 52 of the second application determines the corresponding second electronic device 53 according to the UDID. Afterwards, the server 52 of the second application determines the authentication result of the second application 531 in the second electronic device 53 and sends the authentication result to the first electronic device 51 (ie, step S406).

S407. The first electronic device determines, based on the authentication result, that the second application has logged in and has authorized the first application. If yes, execute step S408; if not, execute step S409.

In some examples, after determining that the second application has logged in and authorized the first application, the first electronic device may complete the authorized login of the second application to the first application. Therefore, the first electronic device determines whether the second electronic device has logged into the second application and the second application has authorized the first application according to the received authentication result. If the second application has been logged in and the second application has authorized the first application, the first electronic device can synchronize the login status of the second application and log in the first application. If the second application is not logged in, the first electronic device needs to request the second electronic device to log in to the second application to perform login authentication on the first application.

Optionally, as shown in Figure 7B, step S407 may include steps S4071 to S4074.

S4071. The first electronic device determines that the second application has been logged in to the second electronic device. If yes, execute step S4073; if not, execute step S4072.

In some examples, the first electronic device determines that the second application has logged in to the second application based on the authentication result. Then, the first electronic device may further determine whether the second application has authorized the first application (ie, perform the following step S4073). Alternatively, the first electronic device determines that the second electronic device has not logged in to the second application based on the authentication result. Then, it is necessary to instruct the second electronic device to log in to the second application (ie, perform the following step S4072).

S4072. The first electronic device determines that it needs to log in to the second application.

In some examples, the first electronic device determines that the second application is not logged in and may determine that the second application needs to be logged in. Optionally, the first electronic device may send a login authentication request of the second application to the second electronic device to instruct the second electronic device to log in to the second application and determine the authorization of the second application to the first application.

Optionally, for the content of step S409, please refer to the detailed description of step S409 below, which will not be described again here.

S4073. The first electronic device determines that the second application has been logged in to the second electronic device and the second application has authorized the first application. If yes, execute step S408; if not, execute step S4074.

In some examples, after determining that the second electronic device has logged in to the second application, the first electronic device needs to confirm the authorization of the first application by the second application. If the second application has authorized the first application, the first electronic device can directly synchronize the login status of the second application and log in the first application (ie, perform the following step S408). If the second application does not authorize the first application, the first electronic device may execute the second electronic device to complete the authorization of the first application by the second application (ie, perform the following step S409).

For example, the second electronic device has logged into the second application through a trusted account, but the second electronic device has not logged into the first application using the trusted account of the second application. Then, it can be determined that the second application has not authorized the first application, and it is necessary to log in to the first application through the trusted account of the second application to complete the login authorization of the first application by the second application.

Optionally, for the content of step S408 and step S409, please refer to the detailed description of step S408 and step S409 below, which will not be described again here.

S4074. The first electronic device determines that the second application needs to authorize the first application.

In some examples, the first electronic device determines that the second application does not authorize the first application and may determine that the second application is required to authorize the first application. Optionally, the first electronic device may send a login authentication request of the second application to the second electronic device to instruct the second application in the second electronic device to authorize the first application.

In this way, after the first electronic device determines the login status of the second application based on the authentication result in step S407, it can log in the first application based on the login status of the second application through the following steps.

It should be noted that, for convenience of description, in the following, the second application has logged in is used to indicate that the second application has logged in and has completed the authorization of the first application.

S408. The first electronic device logs in the first application based on the login status of the second application of the second electronic device.

In some examples, the first electronic device determines that the second application in the second electronic device has been logged in based on the received authentication result, can synchronize the login status of the second application, and automatically complete the login authentication of the first application. Optionally, when the second application has been logged in, the authentication result received by the first electronic device may include the login information of the second application in the second electronic device, such as the account information of the second application, the first electronic device The first application can be automatically logged in according to the login information of the second application. The account information of the second application includes, for example, user nickname, avatar, user registration ID, user information, region information, user introduction and other information.

Exemplarily, as shown in the scenario shown in Figure 6 above, the first electronic device responds to the user operation and determines that the electronic device used to perform login authentication for the A video application (i.e., the first application) is device 1 (i.e., the second electronic device) , and through the above steps, the login status of the second application in device 1 can be synchronized to log in to the A video application. Then, as shown in interface 603 in (c) of Figure 6 , the first electronic device can display prompt information 63 to prompt user A to successfully log in to the video application. That is, the first electronic device automatically completes the login of the A video application through the login authorization of the A video application by the second application in the device 1.

S409. The first electronic device sends a second application login authentication request to the second electronic device.

In some examples, the first electronic device determines, based on the received authentication result, that the second application in the second electronic device is not logged in, or is logged in but has not authorized the first application, and login authorization is required. Then, the first electronic device may send a login authentication request to the second electronic device. Optionally, the login authentication request may carry the identifier of the second application, and the second electronic device determines that the login authentication request is used to request login authentication of the second application based on the identifier of the second application. Optionally, the login authentication request may also carry information such as the identity of the first application and the identity of the first electronic device. The identification of the first application is used by the second electronic device to confirm login authorization for the first application through the second application.

Optionally, data can be transmitted between the first electronic device and the second electronic device through a trusted network connection. This improves transmission efficiency and ensures data security. This will not be explained below.

Optionally, the above steps S404 to S408 are optional steps. In some scenarios, after determining the second electronic device for login authentication (ie, step S403), the first electronic device may directly send a login authentication request to the second electronic device to request authorization of the second application in the second electronic device. Log in to the first application in the first electronic device.

For example, the second electronic device determines that the second application has logged in and has authorized the first application according to the login authentication request. Then, the second electronic device can send the login information of the second application to the first electronic device, and the first electronic device can log in the first application based on the login information of the second application. That is, the first electronic device can automatically synchronize the login status of the second application in the second electronic device to complete the login of the first application.

For another example, if the second electronic device determines that the second application is not logged in according to the login authentication request, or that the second application is logged in but not authorized, then the second electronic device can complete the login authorization of the second application through the following steps to perform the second application. An application login.

S410. The second electronic device sends the second application login authentication interface display data to the first electronic device.

In some examples, the second electronic device responds to the login authentication request and sends the second application login authentication interface display data to the first electronic device, where the display data is used to display the login authentication interface of the second application.

For example, as shown in FIG. 5 , the first electronic device 51 starts the login authentication interface of the second application through the application management service (AMS) 513 to manage the life cycle of the second application. Afterwards, after querying the second application information (such as the identification of the second application) of the second electronic device 53 through the DMS 512, the first electronic device 51 sends a login authentication request to the second electronic device 53 (ie, step S409). Correspondingly, after receiving the login authentication request, the second electronic device 53 queries the second application 531 in the second electronic device 53 through the package management service (PMS) 532 . After that, the second electronic device 53 starts the second application 531 through the AMS 533 background to obtain the login authentication interface display data of the second application 531. Afterwards, the second electronic device 53 sends the determined login authentication interface display data of the second application 531 to the first electronic device 51 through screen projection (ie, step S410).

It should be noted that the login authentication interface is used to complete the login of the second application and the authorization of the first application. It can be understood that, in order to simplify user operations, the second electronic device completes the login of the second application and the authorization of the first application by the second application through a login authentication interface. However, in some scenarios, the second electronic device may also generate display data for displaying an interface for logging in to the second application, and generate display data for displaying an interface for authorizing the first application by the second application. That is, the login process of the second application and the authorization process of the second application to the first application are separated. The embodiments of this application do not limit this.

S411. The first electronic device displays data according to the second application login authentication interface, displays the second application login authentication interface on the screen, and receives login data input by the user.

In some examples, after receiving the display data of the second application login authentication interface, the first electronic device can display the second application login authentication interface to receive the login data input by the user and complete the login authentication of the second application.

For example, as shown in Figure 5, after receiving the second application login authentication interface display data, the first electronic device 51 displays the interface 901 shown in Figure 9 through the display module 514. On the interface 901, the first electronic device receives the account name and password of the second application input by the user. After detecting the user's operation of clicking the login control 91, the first electronic device can determine that the user has completed inputting the login data.

S412. The first electronic device sends login data to the second electronic device.

S413. The second electronic device sends login data to the server of the second application.

In some examples, in steps S412 and S413, after receiving the login data input by the user, the first electronic device may forward the login data to the second electronic device. After receiving the login data, the second electronic device can forward the login data to the server of the second application, thereby completing the login authentication of the second application through the second electronic device.

Exemplarily, as shown in FIG. 5 , the first electronic device 51 sends the received login data input by the user to the second electronic device 53 . Afterwards, the second electronic device 53 forwards the login data sent by the first electronic device 51 to the server 52 of the second application.

S414. The server of the second application determines the login authentication result.

In some examples, after receiving the login data, the server of the second application determines whether to allow the second electronic device to log in to the second application. For example, confirm whether the account name has been registered, whether the account password is correct, etc. If the server of the second application allows the second device to log in to the second application, it can be determined that the login authentication result is login authorization successful; if the server of the second application does not allow the second electronic device to log in to the second application, it can be determined that the login authentication result is login authorization. fail.

Optionally, the login authentication result includes the login result of the second application and the authorization result of the second application to the first application.

S415. The server of the second application sends the login authentication result to the first electronic device.

In some examples, after determining the login authentication result, the server of the second application sends the login authentication result to the first electronic device. Correspondingly, the first electronic device receives the login authentication result sent by the server of the second application.

For example, as shown in FIG. 5 , the server 52 of the second application sends the login authentication result of the second application to the first electronic device 51 .

S416. The first electronic device determines the login result of the first application based on the login authentication result of the second application.

In some examples, after obtaining the login authentication result of the second application, the first electronic device may determine the login result of the first application based on the login authentication result.

For example, the first electronic device determines that the login authentication of the first application is successful based on the login authentication result of successful login authorization, thereby completing the login of the first application.

For another example, the first electronic device determines that the first application has failed login authentication based on the login authentication result of failed login authorization, displays a login authentication failure interface, and prompts the user to confirm whether to log in again.

Exemplarily, as shown in the scenario shown in Figure 6 above, the first electronic device responds to the user operation and determines that the electronic device used to perform login authentication for the A video application (i.e., the first application) is device 1 (i.e., the second electronic device) , and instructs the second application in device 1 to perform login authorization through the above steps, thereby obtaining the login information of the second application to log in to the A video application. Then, as shown in interface 603 in (c) of Figure 6 , the first electronic device can display prompt information 63 to prompt user A to successfully log in to the video application. That is, the first electronic device automatically completes the login of the A video application through the login authorization of the A video application by the second application in the device 1.

In this way, when the second application is not installed in the first electronic device, or the second application in the first electronic device is not logged in, and the second electronic device selected by the user for login authentication is not logged in to the second application, the second electronic device is not logged in. An electronic device can also trigger the second electronic device to start the login process of the second application, and directly complete the login of the second application of the second electronic device on the side of the first electronic device through screen projection, thereby completing the second application's login process for the second application. Login authentication for the first application in an electronic device. Effectively simplify user operations and improve user experience.

In addition, through screen projection, when a user operates one electronic device, he or she can complete the login authentication of the second application of the second electronic device on the first electronic device, effectively simplifying user operations.

In the above example, through screencasting, the user can complete the login of the second application in the second electronic device by operating the first electronic device, thereby completing the login authentication of the first application in the first electronic device. In some scenarios, the user may be accustomed to completing the login of the second application through the second electronic device.

Exemplarily, FIG. 10 is a schematic flowchart of yet another application login method provided by an embodiment of the present application. As shown in Figure 10, after the above step S409, steps S1001 to S1005 may be included. Therefore, the user completes the login authentication of the first application in the first electronic device by operating the first electronic device and the second electronic device.

S1001. The second electronic device displays the second application login authentication interface and receives login data input by the user.

In some examples, after receiving the login authentication request, the second electronic device determines the second application requesting login based on the login authentication request. Afterwards, the second electronic device displays a second application login authentication interface to receive login data input by the user.

S1002. The second electronic device sends login data to the server of the second application.

In some examples, after receiving the login data input by the user, the second electronic device may forward the login data to the server of the second application to complete the login authentication of the second application.

Exemplarily, as shown in Figure 11, after the second electronic device 53 determines the second application 531 through the PMS 532 and starts the second application 531 through the AMS 533, the login authentication interface of the second application 531 can be displayed through the display module 534. And receive the login data input by the user through the login authentication interface (ie step S1001). Afterwards, the second electronic device 53 sends the login data received on the login authentication interface to the server 52 of the second application (ie, step S1002).

Exemplarily, as shown in Figure 12, in response to the received login authentication request, the second electronic device displays the interface 1201. On the interface 1201, the second electronic device receives the account name and password of the second application input by the user. Afterwards, after detecting the user's click on the login control 121, the second electronic device can determine that the user has completed inputting the login data, and can send the obtained login data to the server of the second application.

S1003. The server of the second application determines the login authentication result.

S1004. The server of the second application sends the login authentication result to the first electronic device.

S1005. The first electronic device determines the login result of the first application based on the login authentication result of the second application.

Optionally, for the content of step S1003-step S1005, reference may be made to the relevant content of the above-mentioned step S414-step S416, which will not be described again here.

In this way, when the second application is not installed in the first electronic device, or the second application in the first electronic device is not logged in, and the second electronic device selected by the user for login authentication is not logged in to the second application, the second electronic device is not logged in. One electronic device can also trigger the second electronic device to start the login process of the second application. After completing the login of the second application on the second electronic device, the first electronic device automatically synchronizes the login status of the second application to complete the login authentication of the first application in the first electronic device by the second application. Effectively simplify user operations and improve user experience.

Optionally, the login authentication process of the second application does not require the participation of the server, for example, the trusted account of the second application is a stand-alone account, etc. Then, after receiving the login authentication request sent by the first electronic device in step S409, the second electronic device can directly interact with the first electronic device to complete the login authorization of the second application to log in to the first application. .

For example, after receiving the login data sent by the first electronic device in step S412, the second electronic device may locally determine whether the login data can complete the login of the second application. If it is determined that the second application login authorization is successful, the second electronic device can directly The first electronic device sends the login result, so that the first electronic device can log in the first application according to the login result sent by the second electronic device.

For another example, in the above step S1001, after receiving the login data input by the user by displaying the login authentication interface, the second electronic device can directly determine the login result of the second application based on the login data. Afterwards, the second electronic device can directly send the login result to the first electronic device, so that the first electronic device can log in to the first application based on the login result sent by the second electronic device.

In some scenarios, the first electronic device may be pre-configured to complete the login authentication of the second application of the second electronic device through screen projection, or complete the login authentication of the second application on the second device side. Optionally, the first electronic device may also provide a setting interface to receive the login authentication method of the second application set by the user.

Exemplarily, as shown in (a) of Figure 13, the first electronic device displays the setting interface 1301. After detecting that the user clicks on the application login status synchronization setting control 131, the first electronic device displays the interface 1302 as shown in (b) of Figure 13. . On the interface 1302, the user can choose to complete the authentication login locally (that is, as described in steps S410 to S414 above, the account name and password input by the user are received on the first electronic device through screen projection to complete the first electronic device. Login of the second application), or complete the authentication login at the opposite end (that is, as described in the above steps S1001 to S1003, receive the account name and password input by the user on the second electronic device to complete the login of the second application).

For example, after detecting that the user clicks on the switch control 132, the first electronic device determines that the user has instructed to complete authentication login at the opposite end. Then, when the first electronic device determines that the user indicates that the second application in the second electronic device needs to log in again during the login authentication process of the first application, the method shown in FIG. 10 can be used to log in again in the second electronic device. Complete the login of the second application on the device side.

In this way, users can customize the login authentication method, making the login authentication process more in line with users' usage habits and improving user experience.

In some scenarios, when the first electronic device determines that a second application for login authentication of the first application is installed in the first electronic device and the second application is in a logged-in state, the user may be prompted whether to directly based on The login status of the second application completes the login authentication of the first application. This reduces the operations of the first electronic device searching for a trusted device in the trusted network and selecting the second electronic device among the trusted devices, and reduces the power consumption of the first electronic device.

Illustratively, FIG. 14 is a schematic flowchart of yet another application login method provided by an embodiment of the present application. As shown in Figure 14, the method includes the following steps.

S1401. After detecting the user's operation of logging in to the first application, the first electronic device determines a second application used for login authentication of the first application.

Optionally, for the content of step S1401, reference may be made to the relevant content of the above step S401, which will not be described again here.

S1402. The first electronic device determines that the second application is installed on the local terminal, and the second application has been logged in and authorized. If yes, execute step S1403; if not, execute step S1405.

In some examples, after determining the second application used for login authentication of the first application, the first electronic device may first determine whether the second application is installed on the local terminal. If the second application is installed on the local side, the first electronic device can further determine whether the second application on the local side is in a logged-in state. Thus, it is determined whether the login authentication of the first application can be completed directly on the first electronic device.

S1403. The first electronic device detects the user's operation of searching for other devices. If not, execute step S1404; if yes, execute step S1405.

In some examples, the user can create multiple trusted accounts for the second application. Then, the trusted account of the second application logged in by the first electronic device may not be the trusted account of the second application required by the user. Therefore, the first application can receive the trusted account used by the user to determine whether to use the current second application of the first electronic device to log in, and complete the login operation of the first application.

S1404. The first electronic device logs in to the first application through the second application on the local side.

In some examples, the first electronic device responds to the user operation and determines that the user instructed to complete the login of the first application using a trusted account currently logged in with the second application of the first electronic device. Then, the first electronic device can directly complete the login authentication of the first application based on the login status of the second application on the local side.

In this way, when the second application in the first electronic device is in the login state, the first electronic device can automatically complete the login authentication of the first application directly based on the login state of the second application. This simplifies user operations and improves user experience.

S1405. The first electronic device determines the second electronic device used for login authentication.

In some examples, in response to the user operation, the first electronic device determines that the user instructed to use the second application in other trusted devices to complete the login authentication of the first application. Then, the first electronic device needs to continue to search for other trusted devices in the trusted network that can be used to perform login authentication for the first application.

Optionally, for the remaining content of step S1405, reference may be made to the relevant content of the above-mentioned step S402 and step S403, which will not be described again here.

For example, as shown in (a) of FIG. 15 , the first electronic device displays the login authentication interface 1501 in response to the user's request to log in to the video application A (ie, the first application). After detecting the user's click on the login control 151, the first electronic device can determine that the application that the user instructed to perform login authentication for the A video application is the second application corresponding to the login control 151 (such as ). The first electronic device determines that the second application is installed in the first electronic device and is in a logged-in state. Then, the first electronic device displays the interface 1502 shown in (b) of Figure 15, which is used to prompt the user whether to use the current login account of the second application to log in to the A video application.

For example, if the first electronic device detects the user's click on the allow control 152, it may determine that the user instructed to log in to the A video application using the current login account of the second application. Then, the first electronic device can automatically complete the login of the A video application.

For another example, if the first electronic device detects the user's operation of clicking the search for other devices control 153, it may determine that the user instructed to search for other trusted devices with the second application installed in the trusted network. Then, the first electronic device may determine the second electronic device used for login authentication of the first application in response to the user operation.

Optionally, for details on completing the login authentication of the first application of the first electronic device through the second application of the second electronic device, refer to the relevant contents of steps S404 to S416 shown in the above-mentioned Figure 4, or refer to the above-mentioned The relevant contents of steps S404 to S1005 shown in Figure 10 will not be described again here.

The application login method provided by the embodiment of the present application is described in detail above with reference to Figures 4-15. The electronic device provided by the embodiment of the present application will be described in detail below with reference to FIG. 16 and FIG. 17 .

In one possible design, FIG. 16 is a schematic structural diagram of a first electronic device provided by an embodiment of the present application. As shown in Figure 16, the first electronic device 1600 may include: a transceiver unit 1601 and a processing unit 1602. The first electronic device 1600 may be used to implement the functions of the first electronic device involved in the above method embodiments.

Optionally, the transceiver unit 1601 is used to support the first electronic device 1600 to perform S404, S406, S409, S410, S412 and S415 in Figure 4; and/or to support the first electronic device 1600 to perform S404, S406, S409, S410, S412 and S415 in Figure 10; S1004.

Optionally, the processing unit 1602 is used to support the first electronic device 1600 to perform S401, S402, S403, S407 and S416 in Figure 4; and/or to support the first electronic device 1600 to perform S4031, S4031 in Figure 7A. S4032, S4033, and S4034; and/or, for supporting the first electronic device 1600 to perform S4071, S4072, S4073, and S4074 in Figure 7B; and/or, for supporting the first electronic device 1600 to perform S1005 in Figure 10; And/or, used to support the first electronic device 1600 to perform S1401, S1402, S1403, S1404 and S1405 in Figure 14.

The transceiver unit may include a receiving unit and a transmitting unit, may be implemented by a transceiver or a transceiver-related circuit component, and may be a transceiver or a transceiver module. The operation and/or function of each unit in the first electronic device 1600 is to implement the corresponding process of the application login method described in the above method embodiment. All relevant content of each step involved in the above method embodiment can be quoted from the corresponding For the sake of brevity, the function description of the functional unit will not be repeated here.

Optionally, the first electronic device 1600 may further include a display unit (not shown in FIG. 16 ), which is used to support the first electronic device 1600 in performing S411 in FIG. 4 .

Optionally, the first electronic device 1600 shown in FIG. 16 may also include a storage unit (not shown in FIG. 16), in which programs or instructions are stored. When the transceiver unit 1601 and the processing unit 1602 execute the program or instruction, the first electronic device 1600 shown in FIG. 16 can execute the application login method described in the above method embodiment.

For the technical effects of the first electronic device 1600 shown in FIG. 16 , reference can be made to the technical effects of the application login method described in the above method embodiment, which will not be described again here.

In addition to being in the form of the first electronic device 1600, the technical solution provided by this application can also be a functional unit or chip in the first electronic device, or a device used in conjunction with the first electronic device.

In a possible design, FIG. 17 is a schematic structural diagram of a second electronic device provided by an embodiment of the present application. As shown in Figure 17, the second electronic device 1700 may include: a transceiver unit 1701 and a processing unit 1702. The second electronic device 1700 may be used to implement the functions of the second electronic device involved in the above method embodiments.

Optionally, the transceiver unit 1701 is used to support the second electronic device 1700 to perform S409, S410, S412 and S413 in Figure 4; and/or to support the second electronic device 1700 to perform S1002 in Figure 10.

Optionally, the processing unit 1702 is configured to support the second electronic device 1700 in executing S410 in FIG. 4 .

The transceiver unit may include a receiving unit and a transmitting unit, may be implemented by a transceiver or a transceiver-related circuit component, and may be a transceiver or a transceiver module. The operation and/or function of each unit in the second electronic device 1700 is to implement the corresponding process of the application login method described in the above method embodiment. All relevant content of each step involved in the above method embodiment can be quoted from the corresponding For the sake of brevity, the function description of the functional unit will not be repeated here.

Optionally, the first electronic device 1600 may further include a display unit (not shown in FIG. 16 ), which is used to support the first electronic device 1600 in performing S1001 in FIG. 10 .

Optionally, the second electronic device 1700 shown in FIG. 17 may also include a storage unit (not shown in FIG. 17), in which programs or instructions are stored. When the transceiver unit 1701 and the processing unit 1702 execute the program or instruction, the second electronic device 1700 shown in FIG. 17 can execute the application login method described in the above method embodiment.

For the technical effects of the second electronic device 1700 shown in FIG. 17 , reference can be made to the technical effects of the application login method described in the above method embodiment, which will not be described again here.

In addition to being in the form of the second electronic device 1700, the technical solution provided by this application can also be a functional unit or chip in the second electronic device, or a device used in conjunction with the second electronic device.

An embodiment of the present application also provides a chip system, including: a processor, the processor is coupled to a memory, and the memory is used to store programs or instructions. When the program or instructions are executed by the processor, the The chip system implements the method in any of the above method embodiments.

Optionally, there may be one or more processors in the chip system. The processor can be implemented in hardware or software. When implemented in hardware, the processor may be a logic circuit, an integrated circuit, or the like. When implemented in software, the processor may be a general-purpose processor implemented by reading software code stored in memory.

Optionally, there may be one or more memories in the chip system. The memory may be integrated with the processor or may be provided separately from the processor, which is not limited by the embodiments of the present application. For example, the memory may be a non-transient processor, such as a read-only memory ROM, which may be integrated with the processor on the same chip, or may be separately provided on different chips. The embodiments of this application vary on the type of memory, and The arrangement of the memory and processor is not specifically limited.

For example, the chip system can be a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), or a system on chip (SoC). ), it can also be a central processor (central processor unit, CPU), a network processor (network processor, NP), a digital signal processing circuit (digital signal processor, DSP), or a microcontroller (micro controller unit, MCU), it can also be a programmable logic device (PLD) or other integrated chip.

It should be understood that each step in the above method embodiment can be completed by an integrated logic circuit of hardware in the processor or instructions in the form of software. The method steps disclosed in conjunction with the embodiments of this application can be directly implemented by a hardware processor, or executed by a combination of hardware and software modules in the processor.

Embodiments of the present application also provide a computer-readable storage medium. A computer program is stored in the computer-readable storage medium. When the computer program is run on a computer, it causes the computer to perform the above related steps to implement the above embodiments. application login method.

An embodiment of the present application also provides a computer program product. When the computer program product is run on a computer, it causes the computer to perform the above related steps to implement the application login method in the above embodiment.

In addition, the embodiment of the present application also provides a device. The device may specifically be a component or module, and the device may include one or more connected processors and memories. Among them, memory is used to store computer programs. When the computer program is executed by one or more processors, the device is caused to execute the application login method in each of the above method embodiments.

Among them, the devices, computer-readable storage media, computer program products or chips provided by the embodiments of the present application are all used to execute the corresponding methods provided above. Therefore, the beneficial effects it can achieve can be referred to the beneficial effects in the corresponding methods provided above, and will not be described again here.

The steps of the methods or algorithms described in connection with the disclosure of the embodiments of this application can be implemented in hardware, or they can be It is implemented by the processor executing software instructions. Software instructions can be composed of corresponding software modules. The software modules can be stored in random access memory (random access memory, RAM), flash memory, read only memory (read only memory, ROM), erasable programmable read only memory ( erasable programmable ROM (EPROM), electrically erasable programmable read-only memory (electrically EPROM, EEPROM), register, hard disk, removable hard disk, compact disc (CD-ROM) or any other form of storage media well known in the art. An exemplary storage medium is coupled to the processor such that the processor can read information from the storage medium and write information to the storage medium. Of course, the storage medium can also be an integral part of the processor. The processor and storage medium may be located in an application specific integrated circuit (AP device application specific integrated circuit, ASIC).

Through the above description of the embodiments, those skilled in the art can clearly understand that, for the convenience and simplicity of description, only the division of the above functional modules is used as an example. In practical applications, the above function allocation can be completed by different functional modules according to needs; that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above. For the specific working processes of the systems, devices and units described above, reference can be made to the corresponding processes in the foregoing method embodiments, which will not be described again here.

In the several embodiments provided in this application, it should be understood that the disclosed method can be implemented in other ways. The device embodiments described above are merely illustrative. For example, the division of modules or units is only a logical function division, and there may be other division methods in actual implementation; for example, multiple units or components may be combined or integrated into another system, or some features may be ignored. or not executed. In addition, the coupling or direct coupling or communication connection between each other shown or discussed may be through some interfaces, and the indirect coupling or communication connection of the modules or units may be in electrical, mechanical or other forms.

In addition, each functional unit in each embodiment of the present application can be integrated into one processing unit, each unit can exist physically alone, or two or more units can be integrated into one unit. The above integrated units can be implemented in the form of hardware or software functional units.

Computer-readable storage media includes but is not limited to any of the following: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk or optical disk, etc. Various media that can store program code.

The above are only specific embodiments of the present application, but the protection scope of the present application is not limited thereto. Any changes or substitutions within the technical scope disclosed in the present application shall be covered by the protection scope of the present application. . Therefore, the protection scope of this application should be subject to the protection scope of the claims.

Claims

An application login method, characterized in that the method includes:

After detecting the first operation of the user to log in to the first application, the first electronic device determines the second application used to perform login authentication for the first application;

The first electronic device determines a second electronic device used for login authentication of the first application, and the second electronic device is installed with the second application;

The first electronic device obtains the login information of the second application in the second electronic device and logs in the first application.
The method of claim 1, wherein the first electronic device obtains the login information of the second application in the second electronic device and logs in the first application, including:

The first electronic device sends the first information of the second electronic device to the server. The first information includes the device identification of the second electronic device, the information of the first application, and the information of the second application. one or more items of information;

The first electronic device receives the login information of the second application determined by the server based on the first information, and logs in the first application.
The method of claim 1, wherein the first electronic device obtains the login information of the second application in the second electronic device and logs in the first application, including:

The first electronic device sends second information to the second electronic device. The second information includes the device identification of the first electronic device, the information of the first application, and the information of the second application. one or more items;

The first electronic device receives the login information of the second application determined by the second electronic device based on the second information, and logs in the first application.
The method according to claim 2 or 3, characterized in that, when the second application has logged in and authorized the first application, the login information includes the account information of the second application; The first electronic device performs login of the first application, including:

The first electronic device logs in to the first application according to the account information of the second application.
The method according to claim 2 or 3, characterized in that, when the second application is not logged in, the login information includes login authentication information; the first electronic device logs in the first application. ,include:

The first electronic device instructs the second electronic device to complete the login authorization of the first application by the second application based on the login authentication information.
The method of claim 5, wherein the first electronic device instructs the second electronic device to complete the login authorization of the second application to the first application based on the login authentication information, including :

The first electronic device sends a login authentication request to the second electronic device based on the login authentication information;

The first electronic device obtains the display data sent by the second electronic device in response to the login authentication request;

The first electronic device displays the first login interface of the second application according to the display data;

The first electronic device receives the first login data of the second application input by the user through the first login interface, and performs login authorization for the first application by the second application.
The method of claim 5, wherein the first electronic device instructs the second electronic device to complete the login authorization of the second application to the first application based on the login authentication information, including :

The first electronic device sends a login authentication request to the second electronic device based on the login authentication information;

The first electronic device receives the login result of the second application sent by the server to complete the login authorization of the second application to the first application; the login result is the login result obtained by the server according to the The login result determined by the second login data sent by the second electronic device. The second login data is collected by the second electronic device in response to the login authentication request by displaying the second login interface of the second application. user input data.
The method according to any one of claims 1 to 7, characterized in that the first electronic device determines the second electronic device used to perform login authentication for the first application, including:

The first electronic device searches for a trusted device on which the second application is installed;

When the number of the trusted devices is one, the first electronic device determines that the trusted device is the second electronic device;

or,

When the number of the trusted devices is multiple, the first electronic device displays a device selection interface, and the device selection interface is used to display the multiple trusted devices;

The first electronic device receives the user's second operation on the device selection interface and determines that the trusted device selected by the user is the second electronic device.
The method of claim 8, wherein the trusted device includes the first electronic device, and the first electronic device displays a device selection interface, including:

The first electronic device displays first identifiers of the multiple trusted devices on the device selection interface. The first identifiers include one or more of the following: login status of the second application, device Identity, device name, user-edited device nickname, system account, and system account nickname.
The method according to claim 8 or 9, characterized in that the first electronic device displays a device selection interface, including:

The first electronic device displays the plurality of trusted devices in order of priority on the device selection interface. The determination criteria of the priority order include one or more of the following: whether it is the first electronic device. Electronic device, whether the second application has been logged in, and whether the second application has been logged in recently.
The method according to any one of claims 1 to 10, characterized in that, before the first electronic device detects the first operation of the user logging in to the first application, the method further includes:

The first electronic device and the second electronic device form a trusted network through a preset method. The preset method includes: the first electronic device and the second electronic device log in to the same first account, Alternatively, a first communication connection is established between the first electronic device and the second electronic device, and the first communication connection includes a hyperterminal connection.
An application login method, characterized in that the method includes:

The second electronic device receives the second information sent by the first electronic device, where the second information includes one or more of the device identification of the first electronic device, the information of the first application, and the information of the second application, The first application is an application used by the first electronic device to log in in response to a user instruction determined by the user's first operation, and the second application is used in the second electronic device to log in to the first application. certified applications;

The second electronic device determines the login information of the second application based on the second information;

The second electronic device sends the login information of the second application to the first electronic device, and the login information of the second application is used by the first electronic device to log in the first application.
The method of claim 12, wherein when the second application has logged in and authorized the first application, the login information includes account information of the second application, and the account number The information is used by the first electronic device to log in to the first application.
The method according to claim 12, characterized in that, when the second application is not logged in, the login information includes login authentication information; the method further includes:

The second electronic device receives a login authentication request sent by the first electronic device in response to the login authentication information;

The second electronic device obtains the login data of the second application according to the login authentication request;

The second electronic device sends the login data to the server, and the login data is used by the first electronic device to complete the login authorization of the second application to the first application.
The method of claim 14, wherein the second electronic device obtains the login data of the second application according to the login authentication request, including:

In response to the login authentication request, the second electronic device determines display data of the second application;

The second electronic device sends the display data to the first electronic device, and the display data is used for the first electronic device to display a first login interface and receive the first login data of the second application input by the user. , perform login authorization by the second application to the first application.
The method of claim 14, wherein the second electronic device obtains the login data of the second application according to the login authentication request, including:

In response to the login authentication request, the second electronic device displays a second login interface of the second application;

The second electronic device receives the login data input by the user on the second login interface.
The method according to any one of claims 12 to 16, characterized in that, before the second electronic device receives the second information sent by the first electronic device, the method further includes:

The second electronic device and the first electronic device form a trusted network through a preset method. The preset method includes: the second electronic device and the first electronic device log in to the same first account, Alternatively, a first communication connection is established between the second electronic device and the first electronic device, and the first communication connection includes a hyperterminal connection.
An application login system, characterized in that the system includes a first electronic device and a second electronic device; wherein the first electronic device is used to perform the method according to any one of claims 1-11, The second electronic device is used to perform the method according to any one of claims 12-17.
An electronic device, characterized in that it includes: a processor and a memory, the memory is coupled to the processor, the memory is used to store computer program code, the computer program code includes computer instructions, when the processor The computer instructions are read from the memory, causing the electronic device to execute the method as claimed in any one of claims 1-11; or, causing the electronic device to execute the method as claimed in any one of claims 12-17. method described in the item.
A computer-readable storage medium, characterized in that the computer-readable storage medium includes a computer program. When the computer program is run on an electronic device, the electronic device causes the electronic device to execute any one of claims 1-11. The method described in claim 12; or, causing the electronic device to perform the method described in any one of claims 12-17.
A computer program product, characterized in that, when the computer program product is run on a computer, it causes the computer to execute the method as described in any one of claims 1-11; or, causes the computer to execute as The method of any one of claims 12-17.