Account login method and related device

Abstract

A kind of account login method and related equipment, for realizing the password-free login of account, and can simplify the user operation step required in password-free login process, improve convenience.For example, the first device displays the code scanning interface in response to the approach of the second device, the second device is not logged in the first account;The first device scans the first graphic displayed by the second device through the code scanning interface, establishes the near field communication connection between the first device and the second device;The first device sends first data to the second device through the near field communication connection, so that the second device logs in the first account based on the first data, the first data includes first login credential, the first login credential is the identity credential issued by the server corresponding to the first account for the first device, and the first login credential includes token.

Description

[0001] This application is a divisional application, the original application number is 202410799669.5, the original application date is June 20, 2024, and the entire contents of the original application are incorporated herein by reference. TECHNICAL FIELD

[0002] The present application relates to the technical field of terminals, and in particular to an account login method and related equipment. BACKGROUND

[0003] In order to protect privacy, the operating system, application, file, etc. of an electronic device can be set with an account and a login password corresponding to the account. After a user logs in to the account using the password, the user can view relevant information in the account. However, in this way, the user needs to remember the account and the password, which is a high requirement for the user, and in the case of a large number of accounts, it is difficult to remember, which affects the use experience of the electronic device. SUMMARY

[0004] Embodiments of the present application provide an account login method and related equipment, which are used to implement password-free login and can simplify the user operation steps required in the password-free login process, thereby improving convenience.

[0005] In a first aspect, an account login method is provided, which can be applied to a communication system. The communication system includes a first device and a second device, and the operating system of the first device is currently logged in to a first account. For example, the second device displays a first interface, and the first interface is an interface for logging in to an account. The first device displays a code scanning interface in response to detecting that the second device is close. The second device displays a first pattern in response to detecting that the first device is close, and the first pattern is used to establish near field communication. The first device scans the first pattern through the code scanning interface to establish a near field communication connection with the second device. The first device sends first data to the second device through the near field communication connection, and the first data includes a first login credential of the first device. The second device logs in to the first account based on the first login credential.

[0006] In the embodiments of the present application, when the second device displays the first interface, the two devices can automatically pull up the corresponding interface when the second device is close to the first device. For example, the first device pulls up the code scanning interface, and the second device pulls up the first graphic. In this process, the user does not need to perform complicated operations on the first device and the second device respectively to open the code scanning interface and the first graphic, thereby simplifying the user operation steps and improving the convenience. Moreover, when the second device displays the first interface, the two devices can automatically pull up the corresponding interface when they are close, which can avoid false triggering to a certain extent. For example, when the second device displays an interface other than the first interface, the two devices will not pull up the interface when they are close. In addition, after the first device and the second device establish the near field communication connection, the first device can send the first login credential of the first device to the second device through the near field communication connection, so that the second device logs in the first account by using the first login credential. In this process, the first device does not transmit the account information and the password information of the first account to the second device, which will not cause password leakage. Moreover, the first login credential has a time limit, so that the first login credential cannot be used after the time limit is exceeded, which can avoid the persistence of data leakage to a certain extent.

[0007] In a possible design, the first interface includes any of the following: the first interface is an interface for logging in an account in a settings application of the second device, the first interface is an interface in an OOBE process of the second device, or the first interface is an interface for migrating data from another device.

[0008] In the embodiments of the present application, when the second device displays the first interface, the two devices can automatically pull up the corresponding interface when they are close, which can avoid false triggering to a certain extent. Moreover, the first interface can be an interface in various scenarios, for example, the first interface is an interface for logging in an account in a settings application of the second device, or the first interface is an interface in an OOBE process of the second device, or the first interface is an interface for migrating data from another device. Therefore, in the account login scenario, the OOBE scenario, or the data migration scenario, the two devices can automatically pull up the corresponding interface when they are close. In addition, after the two devices pull up the interface, the near field communication connection is established by scanning the code, and then the account login, the OOBE, and the data migration requirements are implemented based on the near field communication connection, thereby realizing convenient account login, OOBE, and data migration and improving the user experience.

[0009] In a possible design, the first device is currently in a networkless state.

[0010] In the embodiments of the present application, the first device in the networkless state can assist the second device in logging in the first account, thereby breaking the limitation in the prior art that the old machine (i.e., the first device) must be connected to a network to assist the new machine (i.e., the second device) in logging in an account.

[0011] In a possible design, before the first device displays the code scanning interface in response to detecting that the second device is close, the method further includes: the first device displaying a lock screen interface, a black screen, a desktop, a minus one screen, or an application interface.

[0012] In the embodiments of the present application, when the second device displays the first interface, the two devices being close can automatically pull up the corresponding interface, and the interface of the first device is not limited in this process, and the user does not need to open a specific interface on the first device, thereby saving user operation.

[0013] In a possible design, the detecting that the second device is close includes: detecting that a distance between the first device and the second device is less than a first distance, and / or receiving a request signal broadcast by the second device, the request signal being a short-distance communication signal; and the detecting that the first device is close includes: detecting that a distance between the first device and the second device is less than a second distance, and / or receiving a consent signal returned by the first device.

[0014] In the embodiments of the present application, the two devices being close to pull up the interface can be that the interface is pulled up when the two devices are detected to be close, or the interface is pulled up when a short-distance communication signal of the other party is received. In summary, in this way, the user does not need to perform complicated operations on the first device and the second device respectively to open the code scanning interface and the first graphic, thereby simplifying the user operation steps and improving convenience.

[0015] In a possible design, the first device displays the code scanning interface in response to detecting that the second device is close, including: the first device displays prompt information in response to detecting that the second device is close, the prompt information being used to prompt whether to consent to the second device logging in the first account; and the first device displays the code scanning interface when a consent operation is received.

[0016] In the embodiments of the present application, when the first device detects that the second device is close, the first device can first output prompt information, and then pull up the code scanning interface after obtaining user consent, thereby avoiding interrupting the current business of the user due to directly pulling up the code scanning interface.

[0017] In a possible design, the method further includes: the first device sending a consent instruction to the second device, the consent instruction being used to indicate consent to the second device logging in the first account; and the second device displaying the first graphic in response to detecting that the first device is close, including: the second device displaying the first graphic when the consent instruction is received.

[0018] In the embodiments of the present application, after the user of the first device agrees, the first device sends an agreement instruction to the second device, and the second device pulls up the first graph. Without the user's agreement of the first device, the second device directly pulls up the first graph, which affects the user experience.

[0019] In a possible design, the first login credential is a token.

[0020] In the embodiments of the present application, the first device can send the first login credential (token) of the first device to the second device through a near field communication connection, so that the second device logs in the first account using the first login credential. The token has a time limit, so even if the token is stolen, it cannot be used after the expiration date, which can to some extent avoid the persistence of data leakage.

[0021] In a possible design, the first data does not include the login password of the first account, and / or the first data is encrypted using a first key, and the first key is a key agreed by the server corresponding to the first account and the first device.

[0022] In the embodiments of the present application, the first device can send the first login credential (token) of the first device to the second device through a near field communication connection, so that the second device logs in the first account using the first login credential. In this process, the first device does not pass the account information and password information of the first account to the second device, which does not cause password leakage. Moreover, the first data is encrypted, which further ensures the security of the first login credential.

[0023] In a possible design, the first device displays a code scanning interface in response to detecting that the second device is close, including: the first device displays N accounts of the first device in response to detecting that the second device is close, N being a positive integer; and the first device displays the code scanning interface when receiving an operation for selecting the first account.

[0024] In the embodiments of the present application, the first device can display multiple accounts, and the user of the first device can select an account, so that the second device logs in the account, which is better in user experience.

[0025] In a possible design, the second device logs in the first account based on the first login credential, including: the second device sends a login request to a server corresponding to the first account, the login request being used to request to log in the first account, and the first login credential being included in the login request; and the second device receives a second login credential sent by the server.

[0026] In the embodiments of the present application, the second device logs in the first account using the first login credential of the first device. For the server of the first account, the second device is regarded as proxying the first device to log in the first account. In this process, the first device does not transmit the account information and password information of the first account to the second device, so as to avoid password leakage.

[0027] In a possible design, before the second device receives the second login credential sent by the server, the method further includes: the second device receives prompt information sent by the server, where the prompt information is used to prompt that the first device needs to be network authenticated; the second device sends the prompt information to the first device through the near field communication connection; the first device outputs the prompt information; and after the first device is connected to the network, the first device sends authentication information to the server, where the authentication information is used to indicate that the second device is allowed to log in the first account.

[0028] In the embodiments of the present application, the second device logs in the first account using the first login credential of the first device. For the server of the first account, the first login credential originally issued to the first device is at the second device, and the server considers that the second device steals the first login credential of the first device. Therefore, the server can require the first device to perform network authentication. Since the first device is in a networkless state, the server can send prompt information to the second device, so as to send the prompt information to the first device through the second device, to remind the first device to perform network authentication, and to ensure the security of account login.

[0029] In a possible design, when the first interface is an interface used to migrate data from other devices, the method further includes: the first device sends second data to the second device through the near field communication connection, where the second data includes user data stored in the first device; and the second device stores the second data.

[0030] In the embodiments of the present application, after the first device and the second device are close to pull up the interface, the near field communication connection is established by scanning, and then data migration is performed through the near field communication connection, so as to improve the efficiency of data transmission.

[0031] In a second aspect, a method for logging into an account is provided. The method is applied to a first device, and an operating system of the first device is currently logged into a first account. The method comprises: in response to detecting that a second device is close to the first device, displaying, by the first device, a code scanning interface; scanning, by the first device, a first graphic on the second device through the code scanning interface, and establishing a near field communication connection between the first device and the second device; and sending, by the first device, first data to the second device through the near field communication connection, wherein the first data comprises a first login credential of the first device, and the first login credential is used for the second device to log into the first account.

[0032] In a possible design, the first device is currently in a networkless state.

[0033] In a possible design, before the first device displays the code scanning interface in response to detecting that the second device is close to the first device, the method further comprises: displaying, by the first device, a lock screen interface, a black screen, a desktop, a minus one screen, or an application interface.

[0034] In a possible design, the detecting that the second device is close to the first device comprises: detecting that a distance between the first device and the second device is less than a first distance, and / or receiving a request signal broadcast by the second device, wherein the request signal is a short-distance communication signal.

[0035] In a possible design, the first device displays the code scanning interface in response to detecting that the second device is close to the first device, comprising: in response to detecting that the second device is close to the first device, displaying, by the first device, prompt information, wherein the prompt information is used to prompt whether to agree that the second device logs into the first account; and when the first device receives an operation of agreement, displaying the code scanning interface.

[0036] In a possible design, the first login credential is a token.

[0037] In a possible design, the first data does not comprise a login password of the first account, and / or the first data is encrypted by using a first key, wherein the first key is a key agreed by the first device and a server corresponding to the first account.

[0038] In a possible design, the first device displays the code scanning interface in response to detecting that the second device is close to the first device, comprising: in response to detecting that the second device is close to the first device, displaying, by the first device, N accounts of the first device, wherein N is a positive integer; and when the first device receives an operation of selecting the first account, displaying the code scanning interface.

[0039] In a possible design, the method further includes: receiving, by the first device, prompt information sent by the second device through the near field communication connection, where the prompt information is used to prompt that the first device needs to be authenticated for network connection; outputting, by the first device, the prompt information; and sending, by the first device, authentication information to a server corresponding to the first account after the first device is connected to the network, where the authentication information is used to indicate consent to the second device logging in to the first account.

[0040] In a possible design, when the first interface is an interface for migrating data from other devices, the method further includes: sending, by the first device, second data to the second device through the near field communication connection, where the second data includes user data stored in the first device.

[0041] The third aspect also provides an account login method, applied to a second device, and the method includes: displaying, by the second device, a first interface, where the first interface is an interface for logging in to an account; displaying, by the second device, a first graphic in response to detecting that a first device is close, where the first graphic is used to establish a near field communication; establishing, by the second device, a near field communication connection with the first device in response to scanning, by the first device, the first graphic; receiving, by the second device, first data sent by the first device through the near field communication connection, where the first data includes first login credentials of the first device; and logging in, by the second device, to a first account based on the first login credentials.

[0042] In a possible design, the first interface includes any of the following: the first interface is an interface for logging in to an account in a settings application of the second device, the first interface is one interface in an OOBE process of the second device, or the first interface is an interface for migrating data from other devices.

[0043] In a possible design, the first device is currently in a networkless state.

[0044] In a possible design, before the first device displays a code scanning interface in response to detecting that the second device is close, the method further includes: displaying, by the first device, a lock screen interface, a black screen, a desktop, a negative one screen, or an application interface.

[0045] In a possible design, the detecting that the first device is close includes: detecting that a distance between the first device and the second device is less than a second distance, and / or receiving a consent signal returned by the first device.

[0046] In a possible design, before the second device displays the first graphic in response to detecting that the first device is close, the method further includes: the second device displaying the first graphic when the second device receives an agreement instruction sent by the first device, the agreement instruction being used to indicate that the first device agrees to the second device logging in the first account.

[0047] In a possible design, the first login credential is a token.

[0048] In a possible design, the first data does not include a login password of the first account, and / or the first data is encrypted by using a first key, the first key being a key agreed by the first device and a server corresponding to the first account.

[0049] In a possible design, the second device logging in the first account based on the first login credential includes: the second device sending a login request to the server corresponding to the first account, the login request being used to request to log in the first account, and the first login credential being included in the login request; and the second device receiving a second login credential sent by the server.

[0050] In a possible design, before the second device receives the second login credential sent by the server, the method further includes: the second device receiving prompt information sent by the server, the prompt information being used to prompt that the first device needs to be connected to a network for authentication; and the second device sending the prompt information to the first device through the near field communication connection.

[0051] In a possible design, when the first interface is an interface used to migrate data from other devices, the method further includes: the second device receiving second data sent by the first device through the near field communication connection, the second data including user data stored in the first device; and the second device storing the second data.

[0052] The fourth aspect further provides an account login method, applied to a server, and the method includes: receiving a login request of a second device, the login request being used to request to log in a first account, and the login request including a first login credential of a first device; and sending a second login credential to the second device.

[0053] In the embodiments of the present application, the server can implement proxy login of different devices of the same account. For example, the second device logs in the first account by using the first login credential of the first device, and for the server of the first account, the second device proxies the first device to log in the first account, so that the second device does not necessarily need to obtain a password of the first account to log in the first account, and the efficiency and convenience of password-free login are achieved.

[0054] In a possible design, the login request includes a first code value; and before sending the second login credential to the second device, the method further includes: determining that the first code value is a code value that has been sent by the server to the second device and that the first code value is within a valid period.

[0055] In an embodiment of the present application, the server can verify the second device (for example, verify the first code value), and only issue the second login credential to the second device after verification, so as to ensure the security of the account.

[0056] In a possible design, before sending the second login credential to the second device, the method further includes: sending prompt information to the second device, where the prompt information is used to prompt that the first device needs to be authenticated in networking; and receiving authentication information sent by the first device, where the authentication information is used to indicate that the second device is authorized to log in to the first account.

[0057] In an embodiment of the present application, the second device logs in to the first account by using the first login credential of the first device. For the server of the first account, the first login credential originally issued to the first device is at the second device, and the server considers that the second device has stolen the first login credential of the first device. Therefore, the server can require the first device to be authenticated in networking. For example, the server can send prompt information to the second device to remind that the first device needs to be authenticated in networking, so as to ensure the security of the account.

[0058] A fifth aspect further provides an electronic device, including a memory, a processor, and a computer program stored in the memory and capable of running on the processor, and the processor implements the method in the second aspect or the third aspect when running the computer program.

[0059] A sixth aspect further provides an electronic device, including modules / units for implementing the method corresponding to any design in the second aspect or the third aspect. These modules / units can be implemented by hardware, or by hardware executing corresponding software.

[0060] A seventh aspect further provides a server, including a memory, a processor, and a computer program stored in the memory and capable of running on the processor, and the processor implements the method in the fourth aspect when running the computer program.

[0061] An eighth aspect further provides a server, including modules / units for implementing the method corresponding to any design in the fourth aspect. These modules / units can be implemented by hardware, or by hardware executing corresponding software.

[0062] In a ninth aspect, a chip is provided, comprising a processor and an interface; the processor is configured to read instructions through the interface to execute the method according to any one of the first aspect, the second aspect, the third aspect or the fourth aspect.

[0063] In a tenth aspect, a chip system is provided, comprising a processing circuit, a storage medium, wherein the storage medium stores instructions; when the instructions are executed by the processing circuit, the method according to any one of the first aspect, the second aspect, the third aspect or the fourth aspect is implemented.

[0064] In an eleventh aspect, a communication system is provided, comprising: a first device configured to execute the method according to the second aspect; and a second device configured to execute the method according to the third aspect.

[0065] In a twelfth aspect, a communication system is provided, comprising: a first device configured to execute the method according to the second aspect; a second device configured to execute the method according to the third aspect; and a server configured to execute the method according to the fourth aspect.

[0066] In a thirteenth aspect, a computer readable storage medium is provided, which stores a computer program, when the computer program is executed by a processor, the method according to any one of the first aspect, the second aspect, the third aspect or the fourth aspect is implemented.

[0067] In a fourteenth aspect, a computer program product is provided, which comprises a computer program, when the computer program is executed on a computer, the computer is caused to execute the method according to any one of the first aspect, the second aspect, the third aspect or the fourth aspect.

[0068] The beneficial effects of the designs in any one of the second aspect to the fourteenth aspect can refer to the beneficial effects of the corresponding designs in the first aspect, which will not be repeated here. BRIEF DESCRIPTION OF DRAWINGS

[0069] Figure 1 A schematic diagram of a communication system provided by an embodiment of the present application;

[0070] Figure 2 A schematic diagram of a code scanning login provided by an embodiment of the present application;

[0071] Figures 3A to 3B Two example diagrams of a code scanning login provided by an embodiment of the present application;

[0072] Figure 4 Another schematic diagram of a code scanning login provided by an embodiment of the present application;

[0073] Figures 5A to 5F A schematic diagram of two devices approaching a pull-up interface according to an embodiment of the present application;

[0074] Figures 6A to 6B Another schematic diagram of two devices approaching a pull-up interface according to an embodiment of the present application;

[0075] Figures 7A to 7B Another schematic diagram of two devices approaching a pull-up interface according to an embodiment of the present application;

[0076] Figure 8 A first flowchart of an account login method according to an embodiment of the present application;

[0077] Figure 9 A second flowchart of an account login method according to an embodiment of the present application;

[0078] Figure 10 A third flowchart of an account login method according to an embodiment of the present application;

[0079] Figures 11A to 11B A fourth flowchart of an account login method according to an embodiment of the present application;

[0080] Figure 12A A fifth flowchart of an account login method according to an embodiment of the present application;

[0081] Figure 12B A sixth flowchart of an account login method according to an embodiment of the present application;

[0082] Figure 13 A schematic diagram of an electronic device according to an embodiment of the present application;

[0083] Figure 14 Another schematic diagram of a communication system according to an embodiment of the present application;

[0084] Figure 15 Another schematic diagram of an electronic device according to an embodiment of the present application. DETAILED DESCRIPTION

[0085] Hereinafter, some terms in the embodiments of the present application are explained to facilitate the understanding of the skilled in the art.

[0086] At least one of the embodiments of the present application includes one or more; wherein the plurality refers to greater than or equal to two. In addition, it needs to be understood that in the description of the specification, the words "first", "second", etc. are used only for the purpose of distinguishing the description, and cannot be understood as indicating or implying relative importance. For example, the first device and the second device do not represent the importance of the two or the order of the two, but only for the purpose of distinguishing the description. In the embodiments of the present application, "and / or" is only to describe the relationship between the two, which means that there are three kinds of relationships, for example, A and / or B, which means that there are three kinds of situations, such as A alone, A and B together, and B alone. In addition, the character " / " in this paper generally represents that the front and rear associated objects are a kind of "or" relationship.

[0087] The orientation terms mentioned in the embodiments of the present application, such as "up", "down", "left", "right", "in", "out" and the like, are only the direction of the drawings, therefore, the orientation terms used are for better and clearer illustration and understanding of the embodiments of the present application, and are not indicative or implied that the devices or elements referred to must have a specific orientation, be constructed and operated in a specific orientation, therefore, cannot be understood as a limitation on the embodiments of the present application.

[0088] In the description of the specification, the reference "one embodiment", "in some examples" or "some embodiments" and the like means that the specific features, structures or characteristics described in connection with the embodiment are included in one or more embodiments of the specification. Therefore, the statements "in some examples", "in one embodiment", "in some embodiments", "in other some embodiments", "in another some embodiments" and the like appearing in different places in the specification are not necessarily all referring to the same embodiment, but mean "one or more but not all embodiments", unless otherwise specifically emphasized. The terms "include", "contain", "have" and their variants mean "include but are not limited to", unless otherwise specifically emphasized.

[0089] As described above, the way of logging in the account by inputting the password requires the user to remember the account and the password, which is high for the user. In order to solve this problem, in the embodiments of the present application, the account can be logged in by the password-free login mode. In this way, the user does not need to remember the password, which reduces the difficulty of memory and helps to improve the use experience of the electronic device. In the embodiments of the present application, the password-free login can include: scanning code login. The scanning code login involves two devices, one is the device logged in the account, for example, device A, and the other is the device not logged in the account, for example, device B. Device B can display a pattern to be scanned, for example, a two-dimensional code, a bar code, etc. Device A can display a scanning code interface. Device A scans the pattern displayed by device B through the scanning code interface, so that device B logs in the account of device A.

[0090] The code scanning login process provided by the embodiments of the present application will be described in detail below with reference to the drawings.

[0091] The technical solutions provided by the embodiments of the present application can be applied to a communication system. For example, please refer to Figure 1 , a schematic diagram of a communication system provided by an embodiment of the present application. As shown in Figure 1 , the communication system includes a first device, a second device and a cloud side.

[0092] Figure 1 In the embodiment, the first device logs in a first account. Therefore, the first device can be referred to as a logged-in device. Optionally, the first device logging in the first account can include that a first operating system of the first device logs in the first account (i.e., the first account is a system account), or a first application in the first device logs in the first account. The first operating system can be any operating system such as an Android system, a HongMeng system, system, system, system, system, system, system, etc. The first application can be any application in the first device, which can be a system application or a third-party application. Optionally, the first account can be any form of account such as a mobile phone number, an email address, a bank card number, etc., which is not limited in the embodiments of the present application. Figure 1 In the embodiment, the first device is taken as an example of a mobile phone. It should be understood that the first device can also be other types of devices. For example, the first device can be a mobile phone, a tablet computer, a notebook computer, a personal computer (PC), an ultra-mobile personal computer (UMPC), a netbook, a personal digital assistant (PDA), etc. portable devices; or, it can also be a watch, a bracelet, etc. wearable devices; or, it can also be a virtual reality (VR) device, an augmented reality (AR) device, a mixed reality (MR) device, etc. In general, the specific type of the first device is not limited in the embodiments of the present application.

[0093] In the embodiments of the present application, the first device can have distance sensing capability, and can sense the distance between the other device and the first device. For example, the first device comprises a ranging unit. Optionally, the ranging unit can be a laser ranging unit, a sound wave ranging unit, an ultrasonic ranging unit, a radar, etc., and the embodiments of the present application do not make any limitation. After the first device senses the distance between the other device and the first device, if the distance is less than the first distance, it is determined that the other device is close to the first device, and the corresponding interface can be automatically pulled up. The process will be described hereinafter.

[0094] Figure 1 In the embodiments of the present application, the second device does not log in the first account. Therefore, the second device can be referred to as a non-logged-in device. Optionally, the second device not logging in the first account can include that the second operating system of the second device does not log in the first account, or the second application in the second device does not log in the first account. The second operating system can be any operating system, such as system, system, system, system, system, system, system, system, etc. Optionally, the second operating system and the first operating system can be the same operating system or different operating systems, for example, the second operating system and the first operating system are both systems. The second application can be any application in the second device, and can be a system application or a third-party application. Optionally, the second application and the first application in the foregoing can be the same application or different applications. Figure 1 In the embodiments of the present application, the second device is taken as a mobile phone for example, and it should be understood that the second device can also be other types of devices. For example, the second device can be a mobile phone, a tablet computer, a notebook computer, a PC, a UMPC, a netbook, a PDA, etc. portable device; or can also be a television, a game console, etc. entertainment device; or can also be a watch, a bracelet, etc. wearable device; or can also be a vehicle-mounted device, for example, a device mounted in a vehicle, for example, a display device; of course, the vehicle can also be replaced by a train, an aircraft, a mobile platform, etc. other carrier or transportation tool; or can also be a VR device, an AR device, an MR device, etc. In short, the embodiments of the present application do not make any limitation on the specific type of the second device. Optionally, the second device and the first device can be the same type of device or different types of devices, for example, the first device is a mobile phone, and the second device is a PC or a tablet computer. In the present application, the first device and the second device are both taken as mobile phones for example.

[0095] In the embodiments of the present application, the second device can have distance sensing capability, and can sense the distance between the other device and the second device. For example, the second device comprises a ranging unit. Please refer to the foregoing description for the ranging unit. After the second device senses the distance between the other device and the second device, if the distance is less than the first distance, it is determined that the other device is close to the second device, and the corresponding interface can be automatically pulled up. The process will be described hereinafter.

[0096] Figure 1 In the embodiments, the cloud side can comprise a server corresponding to the first account, i.e., a login server of the first account, for example, a first server. The first device logs in to the first account, which can be simply understood as that the first device can access data resources in the first server. The second device does not log in to the first account, which can be simply understood as that the second device cannot access data resources in the first server. Optionally, the first server can be various types of servers, for example, an application server (Application Server), an account server (Account Server), an identity management (Identity Management, IDM) server, etc. Figure 1 In the embodiments, the cloud side can further comprise other servers, for example, a second server. The second server can be understood as an auxiliary server of the first server. For example, for a device (for example, the second device) that needs to perform code scanning login, the second server can provide verification information to the device. The verification information can be a login code value (code), hereinafter referred to as code value. Optionally, the code value can be in the form of any one or combination of text, numerical value, symbol, letter, pattern, sound, video, etc. The code value can be used to generate a to-be-scanned pattern, for example, a two-dimensional code, a bar code or any other form of pattern. That is, the second server can be used to generate a code value and provide the code value to a device (for example, the second device) that needs to perform code scanning login, so that the device displays a to-be-scanned pattern, and when the pattern is scanned by a device (for example, the first device) that has logged in an account, password-free login can be achieved. For example, the second server can be a quick response code (Quick Response code, QR code) server, and the generated code value can be a QR code, which is used to generate a two-dimensional code, a bar code or various forms of patterns. It should be noted that, Figure 1 In the embodiments, the second server and the first server are taken as an example of two independent servers. It can be understood that the second server and the first server can also be one server, for example, the second server is integrated in the first server, in other words, the first server has the function of generating a code value.

[0097] The following continues to take the communication system shown in Figure 1 as an example for description.

[0098] Figure 1 In some embodiments, the first device has logged in the first account, and the second device has not logged in the first account. For ease of understanding, it is assumed that the first operating system of the first device has logged in the first account, and the second operating system of the second device has not logged in the first account. If the first operating system and the second operating system are both Huawei systems, the first account can be a Huawei account. In the embodiments of the present application, the second operating system of the second device can be logged in the first account by means of scanning and logging in.

[0099] For example, please refer to Figure 2 , which is a schematic diagram of scanning and logging in provided by an embodiment of the present application. Figure 2 In some embodiments, the first operating system of the first device has logged in the first account. The second operating system of the second device has not logged in the first account. For example, Figure 2 (a), the second device displays an interface 100, and the interface 100 includes a first pattern. For example, Figure 2 (b), the first device displays an interface 200. The interface 200 can also be referred to as a scanning interface. The interface 200 includes an image captured by the camera of the first device. The user can align the camera of the first device to the first pattern on the second device for scanning, so that the second operating system of the second device logs in the first account. The specific login process will be described later. Figure 2 In some embodiments, the first pattern can be a two-dimensional code, a bar code or any other form of pattern. Optionally, the shape of the first pattern can be a square, a rectangle, a circle, a ring or any other shape, which is not limited in the embodiments of the present application.

[0100] In the embodiments of the present application, the generation of the first pattern can include the following two methods.

[0101] The first method is that the first pattern is generated based on a first code value. The first code value is a code value obtained by the second device from the cloud side (for example, obtained by the second server from the cloud side) for implementing password-free login. For example, as Figure 1 , the second device displays the first pattern, which is a two-dimensional code generated based on the first code value. The first device scans the two-dimensional code to obtain the first code value, and then requests the cloud side to authorize the second device to log in the first account based on the first code value. Figure 3A

[0102] The second method is that the first pattern is generated based on a second code value. The second code value is different from the first code value described above, and the difference can include different sources and / or different functions. The different sources include, for example, that the first code value is obtained by the second device from the cloud side (for example, Figure 1 ​The first code value is obtained by the second device from the second server, and the second code value can be locally generated by the second device or obtained from a third server, which can be the same server as the second server or a different server from the second server. The functions of the first code value and the second code value are different, for example, the first code value is used for the cloud side to authenticate the second device to determine whether to authorize the second device to log in to the first account, and the second code value is used to establish a near field communication connection. For example, as shown in Figure 3B , the second device displays a first pattern, which is a ring code generated based on the second code value. If the operating system of the second device is a Harmony system, the ring code can be referred to as a Harmony ring, and of course, the name is not limited in the embodiments of the present application. When the first device scans the ring code, a near field communication connection between the first device and the second device can be established. The first device can assist the second device to log in to the first account through the near field communication connection, and the specific implementation process will be described below.

[0103] In the embodiments of the present application, the second device can generate the first pattern based on any one of the above two methods. For example, if the second device only includes program code of the first method, the first pattern is generated by the first method. Alternatively, if the second device only includes program code of the second method, the first pattern is generated by the second method. Alternatively, the second device includes program code of the first method and program code of the second method, in which case, the second device can randomly select one method, or select one method according to actual conditions, for example, the second device determines that the near field communication function (for example, Bluetooth) is not turned on, the first method can be used, otherwise, the second method can be used; or the user can also set which method the second device uses.

[0104] It should be noted that the generation method of the first pattern (for example, the first or second method described above) is different, and the corresponding login process is different, which will be described below. For ease of understanding, the following will be described mainly by taking the second method for generating the first pattern (i.e. Figure 3B ) as an example, that is, the first pattern is used to establish a near field communication connection. For example, Figure 3B , to achieve code scanning login, the second device needs to open an interface 100, and the first device needs to open an interface 200. The process of opening the interface 100 by the second device and opening the interface 200 by the first device will be described below. It should be emphasized that the principles of opening the interface 100 by the second device and opening the interface 200 by the first device in the following are also applicable to Figure 3A .

[0105] For example, as shown in Figure 4(a), the second device displays a desktop. After the second device receives one or more user operations (e.g., click operations), an interface for logging in an account is displayed, for example, an interface for logging in a system account (e.g., a Huawei account), which may be, for example, an interface as shown in Figure 4 (b). The interface includes a "near-field login" button. When the second device receives an operation on the "near-field login" button, an interface 100 as shown in Figure 4 (c) is displayed. The interface 100 includes a first graphic for establishing a near-field communication connection. As shown in Figure 4 (d), the first device displays a desktop. After the first device receives one or more user operations (e.g., click operations), an interface as shown in Figure 4 (e) is displayed. The interface may be an interface of an account center of an account of the first device. The interface includes a scan-to-scan button. When the first device receives an operation on the scan-to-scan button, a camera is started, and an interface 200 as shown in Figure 4 (f) is displayed. Therefore, through the process of Figure 4 , the second device opens the interface 100, and the first device opens the interface 200. However, in the process, the user needs to perform cumbersome operations on the first device and the second device respectively, which is not convenient and the experience is not good.

[0106] In order to simplify the user operation steps, so that the second device quickly opens the interface 100, and / or the first device quickly opens the interface 200. A possible solution is that the two devices automatically pull up the corresponding interface under the triggering of a triggering condition. Optionally, the triggering condition may include that the two devices are close. That is, the two devices are close to automatically pull up the corresponding interface.

[0107] For example, as shown in Figure 5A (b), when the first device detects that the second device is close, there are two processing methods. Method A, the first device pops up a prompt box as shown in Figure 5A (e). The prompt box includes account information (e.g., a mobile phone number) of the first device, and also includes prompt information for prompting that the account of the first device will be logged in on the second device. The prompt box also includes a "log in with this account" button. When the first device receives an operation on the "log in with this account" button, the interface 200 as shown in Figure 5A (d), that is, a code scanning interface, is pulled up. Method B, the first device directly pulls up the interface 200 as shown in Figure 5A (d). As shown in Figure 5A (a), when the second device detects that the first device is close, the interface 100 as shown in Figure 5A (c) may be directly pulled up, which includes a first graphic for establishing a near-field communication connection; or, the second device pulls up the interface 100 as shown in Figure 5A The interface 100 of (c) is displayed on the first device and the interface 200 of (c) is displayed on the second device. Figure 5A In (f), after receiving the operation on the "log in with this account" button, the first device sends a pull-up instruction to the second device, and after receiving the pull-up instruction, the second device pulls up the interface 100 as shown in Figure 5A The interface 100 of (c) is displayed on the first device and the interface 200 of (c) is displayed on the second device.

[0108] It should be noted that, Figure 5A When the first device displays the desktop and the second device displays the desktop, the two devices are automatically pulled up to the corresponding interface when they are close. Alternatively, before the second device pulls up the interface 100, it can also display other interfaces other than the desktop, such as a lock screen, a black screen, or other interfaces. The remaining interfaces can be a negative screen or any interface entered by the user in the unlocked state. Alternatively, before the first device pulls up the interface 200, it can also display other interfaces other than the desktop, such as a lock screen, a black screen, or other interfaces. The remaining interfaces can be a negative screen or any interface entered by the user in the unlocked state.

[0109] In comparison with the foregoing Figure 5A In the foregoing Figure 4 In the foregoing Figure 4 In the foregoing Figure 5A In the foregoing, the user only needs to bring the two devices close, and the two devices can automatically pull up the corresponding interface. This automatic pulling up of the interface when close greatly simplifies the user operation steps and improves the convenience and user experience.

[0110] Figure 5A In the foregoing, the two devices are automatically pulled up to the corresponding interface when they are close, which can include various implementation manners.

[0111] In mode A, when the second device detects that the first device is close, it automatically displays the interface 100 and triggers the first device to display the interface 200, for example, sends an instruction to open the interface 200 to the first device, so that the first device opens the interface 200 based on the instruction. In this mode, the second device performs distance detection, and when it is determined that the first device is close (for example, the distance is less than the first distance) based on the distance, it displays the interface 100 and triggers the first device to display the interface 200. In this mode, the workload of the first device is relatively small.

[0112] In mode B, when the first device detects that the second device is close, it automatically displays the interface 200 and triggers the second device to display the interface 100, for example, sends an instruction to open the interface 100 to the second device, so that the second device opens the interface 100 based on the instruction. In this mode, the first device performs distance detection, and when it is determined that the second device is close (for example, the distance is less than the second distance) based on the distance, it displays the interface 200 and triggers the second device to display the interface 100. In this mode, the workload of the second device is relatively small.

[0113] Mode C, the second device automatically displays the interface 100 when detecting that the first device is close; the first device automatically displays the interface 200 when detecting that the second device is close. In this mode, the computational load of the first device and the second device is balanced.

[0114] Optionally, the system can use the above-mentioned mode A by default, that is, the distance detection and the interface pulling up are performed by the device (that is, the second device) that has not logged in the account by default. In a possible case, when the second operating system of the second device has not logged in any account, the distance sensing unit (see the foregoing description) in the second device can be always in an open state, that is, always senses whether another device is close, to be ready for pulling up the interface and completing the code scanning and logging in as soon as possible. The first operating system of the first device has logged in the first account, and the distance sensing unit in the first device does not need to be always open, and the first device only needs to pull up the interface 200 after receiving the interface pulling up instruction of the second device. Of course, the system can also use mode B or mode C by default, and the embodiments of the present application are not limited in this regard.

[0115] Figure 5A In this mode, the corresponding interfaces are automatically pulled up when the two devices are close. The embodiments of the present application also consider that the automatic pulling up of the interface when the two devices are close may not be what the user expects to happen. For example, the user does not have the intention to log in the first account by using the second operating system of the second device, and simply places the second device and the first device in a relatively close position, and if the two devices automatically pull up the interface, the user experience may be affected.

[0116] Therefore, in order to avoid mis-triggering, the embodiments of the present application provide the following solutions.

[0117] The first solution is that when the second device displays the first interface (which can also be referred to as the first specific interface), the corresponding interfaces are automatically pulled up when the two devices are close, and when the second device does not display the first interface, the two devices will not pull up the interface when they are close, to avoid mis-triggering.

[0118] The first interface of the second device can be different in different scenarios. Three scenarios are taken as examples in the following.

[0119] The first scenario is a scenario in which the second device logs in an account. Optionally, the scenario in which the account is logged in can be a scenario in which a system account (for example, a Huawei account) is logged in.

[0120] For example, as shown in Figure 5B (a), the second device displays a desktop. After receiving one or more user operations, the second device displays an interface for logging in an account. Taking logging in a system account (for example, a Huawei account) as an example, the interface for logging in the system account can be, for example, Figure 5B(b) the interface 301 shown. As an example, the second device opens the interface 301 in the following way: desktop -> settings -> account. As shown in Figure 5B (b), the interface 301 includes a "near field login" button. When the second device receives an operation on the "near field login" button, it displays the interface 302 shown in Figure 5B (c), or directly displays the interface 100 shown in Figure 5B (d). It should be noted that, as shown in the interface 301 in Figure 5B (b), the account can be a mobile phone number, an email address, or an account name, which is used to log in to the operating system on the second device.

[0121] Alternatively, the first interface can be any one of the following interfaces or other interfaces: the interface 301 shown in Figure 5B (b), the interface 302 shown in Figure 5B (c), the interface 100 shown in Figure 5B (d), or the home page of a settings application or any interface entered from the home page.

[0122] Taking the interface 302 shown in Figure 5B (c) as an example, when the second device displays the interface 302, if the two devices are close to each other, the corresponding interface can be pulled up. For example, as shown in Figure 5B (e), the first device displays a desktop, and when the first device detects that the second device is close (the second device is displaying the interface 302), there are two processing methods. Method A: the first device automatically pops up a prompt box shown in Figure 5B (f). The prompt box includes prompt information, which is used to prompt that the account of the first device will be logged in on the second device. The prompt box also includes a "use this account to log in" button. When the first device receives an operation on the "use this account to log in" button, it pulls up the interface 200 shown in Figure 5B (g). Method B: the first device directly pulls up the interface 200 shown in Figure 5B (g) without going through the process of Figure 5B (f), saving operations and simplifying the process. When the second device displays the interface 302, if it detects that the first device is close, it can automatically pull up the interface 100 shown in Figure 5B (d), or, when it receives a pull-up instruction sent by the first device, it pulls up the interface 100 shown in Figure 5B (d). For example, Figure 5B (f), after receiving an operation on the "use this account to log in" button, the first device sends a pull-up instruction to the second device, and after receiving the pull-up instruction, the second device pulls up the interface 200 shown in Figure 5BThe interface 100 of (d) is displayed on the second device. It should be noted that in this example, the interface 100 is automatically pulled up when the two devices are close to each other while the first device displays the desktop and the second device displays the interface 100. Alternatively, the first device can display other interfaces other than the desktop, such as a lock screen, a black screen, or other interfaces. The other interfaces can be any interface entered by the user when the first device is unlocked, such as a negative one screen or an interface of a certain application.

[0123] The first interface is the interface 100 of (d). Figure 5B The interface 100 of (d) is displayed on the second device. It should be noted that in this example, the interface 100 is automatically pulled up when the two devices are close to each other while the first device displays the desktop and the second device displays the interface 100. Alternatively, the first device can display other interfaces other than the desktop, such as a lock screen, a black screen, or other interfaces. The other interfaces can be any interface entered by the user when the first device is unlocked, such as a negative one screen or an interface of a certain application. Figure 5B (e), the first device displays the desktop, and the first device detects that the second device is close (the second device is displaying the interface 100). There are two processing methods, as in the previous method A and method B. When the second device detects that the first device is close, the second device continues to remain in the interface 100. It should be noted that in this example, the interface 100 is automatically pulled up when the two devices are close to each other while the first device displays the desktop and the second device displays the interface 100. Alternatively, the first device can display other interfaces other than the desktop, such as a lock screen, a black screen, or other interfaces. The other interfaces can be any interface entered by the user when the first device is unlocked, such as a negative one screen or an interface of a certain application.

[0124] The first interface is the interface 100 of (d). Figure 5B The interface 301 of (b) is displayed on the second device. It should be noted that in this example, the interface 301 is automatically pulled up when the two devices are close to each other while the first device displays the desktop and the second device displays the interface 301. Alternatively, the first device can display other interfaces other than the desktop, such as a lock screen, a black screen, or other interfaces. The other interfaces can be any interface entered by the user when the first device is unlocked, such as a negative one screen or an interface of a certain application. Figure 5B (e), the first device displays the desktop, and the first device detects that the second device is close (the second device is displaying the interface 301). There are two processing methods, as in the previous method A and method B. When the second device displays the interface 301, if it is detected that the first device is close, the interface 100 of (d) can be directly pulled up; or, when the pull-up instruction sent by the first device is received, the interface 100 of (d) is pulled up. For example, Figure 5B (e), the first device displays the desktop, and the first device detects that the second device is close (the second device is displaying the interface 301). There are two processing methods, as in the previous method A and method B. When the second device displays the interface 301, if it is detected that the first device is close, the interface 100 of (d) can be directly pulled up; or, when the pull-up instruction sent by the first device is received, the interface 100 of (d) is pulled up. For example, Figure 5B (e), the first device displays the desktop, and the first device detects that the second device is close (the second device is displaying the interface 301). There are two processing methods, as in the previous method A and method B. When the second device displays the interface 301, if it is detected that the first device is close, the interface 100 of (d) can be directly pulled up; or, when the pull-up instruction sent by the first device is received, the interface 100 of (d) is pulled up. For example, Figure 5B (f), the first device sends a pull-up instruction to the second device after receiving an operation on the "log in with this account" button, and the second device pulls up the interface 100 of (d) after receiving the pull-up instruction. It should be noted that in this example, the interface 301 is automatically pulled up when the two devices are close to each other while the first device displays the desktop and the second device displays the interface 301. Alternatively, the first device can display other interfaces other than the desktop, such as a lock screen, a black screen, or other interfaces. The other interfaces can be any interface entered by the user when the first device is unlocked, such as a negative one screen or an interface of a certain application. Figure 5B (f), the first device sends a pull-up instruction to the second device after receiving an operation on the "log in with this account" button, and the second device pulls up the interface 100 of (d) after receiving the pull-up instruction. It should be noted that in this example, the interface 301 is automatically pulled up when the two devices are close to each other while the first device displays the desktop and the second device displays the interface 301. Alternatively, the first device can display other interfaces other than the desktop, such as a lock screen, a black screen, or other interfaces. The other interfaces can be any interface entered by the user when the first device is unlocked, such as a negative one screen or an interface of a certain application.

[0125] The second scenario is the out-of-box experience (OOBE) of the second device.

[0126] For example, such as Figure 5C (a) The second device is in the off state. After receiving the power-on operation, the second device can display as follows: Figure 5C (b) shows the boot screen. Optionally, the second device can perform processes such as SIM card network search and registration to enable the SIM card to function properly. Optionally, it can also perform a wireless connection process, such as accessing a WLAN. These processes are not detailed in this embodiment. After completing the above processes, the second device can display the boot screen shown in Figure (b). Figure 5C Interface 303 is shown in (c). The user can select a language, such as Simplified Chinese, within interface 303. When the second device receives an operation on the "Start" button, it displays as shown... Figure 5C As shown in interface 304 (d), the user can select a region, such as China. When the second device receives an operation on the "Continue" button, it can display an interface for logging into an account, such as an interface for logging into a system account (e.g., a Huawei account). The interface could be, for example, as shown in... Figure 5C Interface 305 as shown in (e), or, as... Figure 5C Interface 100 is shown in (f). Interface 305 includes the prompt message: Please bring another device close to this device to easily complete the setup.

[0127] Optionally, the first interface can be any interface in the OOBE process, for example, Figure 5C (c) Interface 303, Figure 5C (d) Interface 304 Figure 5C (e) Interface 305, or Figure 5C (f) Interface 100.

[0128] The first interface is Figure 5C (e) shows interface 305 as an example. When the second device displays interface 305, the corresponding interface can be pulled up if the two devices are close together. For example, as shown in the image... Figure 5C (g) When the first device displays the lock screen and detects the second device approaching (the second device is currently displaying screen 305), there are two processing methods. Method A: The first device automatically pops up the lock screen as shown in the image. Figure 5C (g) A prompt box appears, containing device information for the second device and a prompt message. The prompt message guides users to configure the second device using the account provided by the first device. The prompt box also includes a "Settings" button. When the first device receives an operation on the "Settings" button, it can directly pull up... Figure 5C(h) the interface 200 shown. Alternatively, since the first device is in the lock screen state, the first device receives an operation on the "Settings" button, and the user is prompted to perform identity authentication (the process is not shown in the figure) to ensure that the owner of the first device is operating. For example, the first device can prompt the user to enter an unlocking fingerprint or an unlocking password, and if the verification is passed, the first device directly pulls up the interface 200 shown in Figure 5C (h). Mode B, the first device directly pulls up the interface 200 shown in Figure 5C (h) without the pop-up Figure 5C (h) shown in the figure, and the first device receives an operation on the "Settings" button, and the first device sends a pull-up instruction to the second device, and the second device receives the pull-up instruction and pulls up the interface 100 shown in Figure 5C (f) without the pop-up Figure 5C (f) shown in the figure. For example, Figure 5C (f) in the figure, the first device receives an operation on the "Settings" button, and the first device sends a pull-up instruction to the second device, and the second device receives the pull-up instruction and pulls up the interface 100 shown in Figure 5C (f). It should be noted that in this example, when the second device displays the interface 305 and the first device displays the lock screen interface, the two devices are close to automatically pull up the interface. Alternatively, the first device can also display other interfaces other than the lock screen interface, for example, a black screen, or any interface entered by the user in the unlocked state, for example, a desktop, a negative one screen, or an interface of a certain application. Figure 5C

[0129] (f) shown in the figure. For example, Figure 5C (f) in the figure. When the second device displays the interface 100, if the two devices are close, the corresponding interface can be pulled up. For example, as shown in Figure 5C (g), the first device displays the lock screen interface, and the first device detects that the second device is close (the second device is displaying the interface 100), and there are two processing modes, as described in the previous mode A and mode B. It should be understood that since the second device has displayed the interface 100, when the first device is detected to be close, the second device continues to remain in the interface 100. It should be noted that in this example, when the second device displays the interface 100 and the first device displays the lock screen interface, the two devices are close to automatically pull up the interface. Alternatively, the first device can also display other interfaces other than the lock screen interface, for example, a black screen, or any interface entered by the user in the unlocked state, for example, a desktop, a negative one screen, or an interface of a certain application.

[0130] (f) shown in the figure. For example, Figure 5C (d) in the figure. When the second device displays the interface 304, if the two devices are close, the corresponding interface can be pulled up. For example, as shown in Figure 5C ​(g) When the first device displays the lock screen and detects the second device approaching (the second device is currently displaying screen 304), there are two processing methods, such as method A and method B mentioned above. When the second device displays screen 304, if it detects the first device approaching, it can directly pull up the lock screen. Figure 5C (f) Interface 100; or, upon receiving a pull-up command from the first device, pull up as follows: Figure 5C (f) Interface 100. For example, Figure 5C In (g), after receiving an operation on the "Settings" button, the first device sends a pull-up command to the second device. Upon receiving the pull-up command, the second device pulls up as follows: Figure 5C (f) Interface 100. It should be noted that in this example, taking the second device displaying interface 304 and the first device displaying the lock screen interface as an example, when the two devices are close together, the interface automatically pulls up. Optionally, the first device can also display other interfaces besides the lock screen interface. Other interfaces include a black screen or any interface that the user enters when unlocked, such as the desktop, the negative one screen, or the interface of a certain application.

[0131] The third scenario is the data cloning scenario.

[0132] For example, such as Figure 5D (a) The second device displays an interface with two options: "This is the old device" and "This is the new device". Optionally, the second device opens... Figure 5D The process shown in (a) may include: Desktop -> Settings -> System & Updates -> Data Cloning; or, after the second device installs an application for data cloning (e.g., "Huawei Phone Cloning") from the app store, opening the application as shown in (a) Figure 5D The interface shown in (a) is as follows. When the second device receives an operation for the "This is a new device" option, it can display something like this. Figure 5D (b) The interface 306 shown, or, directly displaying as shown in the image, is... Figure 5D Interface 100 is shown in (c).

[0133] Optionally, the first interface can be Figure 5D (b) Interface 306 Figure 5D (c) Interface 100 or other interfaces, which may be other interfaces that the second device may display after receiving an operation for the "This is a new device" option.

[0134] The first interface is Figure 5D (b) Taking interface 306 as an example. When the second device displays interface 306, the corresponding interface can be pulled up if the two devices are close together. For example, Figure 5D(f), the first device displays a lock screen interface, and when the first device detects that the second device is close (the second device is displaying interface 306), there are two processing methods. Method A, the first device automatically pops up a prompt box as shown in Figure 5D (f), which includes device information of the second device and prompt information for prompting to clone data to the second device. The prompt box also includes a "Confirm" button. When the first device receives an operation on the "Confirm" button, it can pull up interface 200 as shown in Figure 5D (g); or, when the first device receives an operation on the "Confirm" button, it can prompt the user to perform identity authentication (this process Figure 5D is not shown), to ensure that the owner of the first device is operating. For example, the first device can prompt the user to input an unlocking fingerprint or an unlocking password, and if the verification is passed, it pulls up interface 200 as shown in Figure 5D (g). Method B, the first device directly pulls up interface 200 as shown in Figure 5D (g), without popping up the prompt box in Figure 5D (f), saving operation and simplifying the process. When the second device displays interface 306, if it detects that the first device is close, it can directly pull up interface 100 as shown in Figure 5D (c); or, when it receives a pull-up instruction sent by the first device, it pulls up interface 100 as shown in Figure 5D (c). For example, Figure 5D (f), after the first device receives an operation on the "Confirm" button, it sends a pull-up instruction to the second device, and after the second device receives the pull-up instruction, it pulls up interface 100 as shown in Figure 5D (c). It should be noted that in this example, when the second device displays interface 306 and the first device displays a lock screen interface, the two devices are close and automatically pull up the interface. Alternatively, the first device can also display other interfaces other than the lock screen interface, such as a black screen, or any interface entered by the user in the unlocked state, such as a desktop, a negative one screen, or an interface of a certain application.

[0135] Taking interface 100 as shown in Figure 5D (c) as an example. When the second device displays interface 100, if the two devices are close, the corresponding interface can be pulled up. For example, as shown in Figure 5D(f), the first device displays a lock screen interface, and when the first device detects that the second device is close (the second device is displaying the interface 100), there are two processing manners, which are the manner A and the manner B as described above. It should be understood that since the second device has displayed the interface 100, when the first device is detected to be close, the second device continues to remain in the interface 100. It should be noted that in this example, when the second device displays the interface 100 and the first device displays the lock screen interface, the two devices are close to automatically pull up the interface. Alternatively, the first device can also display other interfaces other than the lock screen interface, for example, a black screen, or an arbitrary interface entered by a user in an unlocked state, for example, a desktop, a negative one screen or an interface of a certain application.

[0136] As Figure 5D , after the first device scans the first graphics in the interface 100 of the second device through the scanning interface 200, the near field communication connection between the first device and the second device is established. For example, the first device can display an interface as shown in Figure 5D (h), which displays a prompt information: connecting. After the connection is successful, the first device displays an interface as shown in Figure 5D (i), which includes a prompt information: please operate on the new device (i.e., the second device). The second device can display an interface for logging in an account, for example, an interface for logging in a system account (for example, a Huawei account), which can be an interface as shown in Figure 5D (k), which includes the account information (for example, a mobile phone number) of the first device, further includes a prompt information for prompting the second device to log in the account of the first device, and further includes two buttons: "synchronize to log in this account" and "set up later".

[0137] Figure 5D In (k), when the second device receives an operation on the "synchronize to log in this account" button, the account of the first device is logged in through the near field communication connection (the implementation principle is described below), for example, the second device can display an interface as shown in Figure 5Dthe interface in (1) displays prompt information of "logging in". After the second device logs in the account of the first device through the near field communication connection, the second device can acquire the data of the account in multiple ways. Way A, since the second device has logged in the account of the first device, the second device can acquire the data of the account from the cloud side. Way B, the second device does not need to acquire the data from the cloud side, but receives the data of the account from the first device through the near field communication connection. Way C, considering that the first device can upload part of the data to the cloud side and another part of the data is not uploaded to the cloud side, the second device can acquire the uploaded data from the cloud side, and for the data not uploaded to the cloud side, the second device can acquire the data from the first device through the near field communication connection. Taking way B as an example, the second device can acquire all the data or part of the data of the account from the first device through the near field communication connection, and the part of the data can be data selected by the user. For example, Figure 5D In (1), after the second device successfully logs in the account of the first device, the second device can display Figure 5D the data selection interface in (d), in which the user can select data, and the second device sends a start migration instruction to the first device when the second device receives an operation on the "start migration" button. After the first device receives the start migration instruction, the first device migrates the data (selected by the user) to the second device through the near field communication connection. For example, the first device can display, as shown in Figure 5D the prompt information in (j): data migration in progress. The second device displays, as shown in Figure 5D the migration progress in (e).

[0138] Figure 5D In (k), when the second device receives an operation on the "set up later" button, since the second device does not need to log in the account of the first device, the second device can directly display Figure 5D the data selection interface in (d), in which the user can select data, and the second device sends a start migration instruction to the first device when the second device receives an operation on the "start migration" button. After the first device receives the start migration instruction, the first device migrates the data (selected by the user) to the second device through the near field communication connection. For example, the first device can display, as shown in Figure 5D the prompt information in (j): data migration in progress. The second device displays, as shown in Figure 5D the migration progress in (e).

[0139] The above are several examples of the first interface, and it should be understood that the first interface can also be other interfaces, which are not enumerated one by one in the embodiments of the present application. It should be noted that in the first solution, when the second device displays the first interface, the display interface of the first device can not be required, and no matter what interface (for example, a lock screen, a black screen, a desktop, a negative one screen or other arbitrary interface) the first device displays, the automatic raising of the interface by approaching can be realized.

[0140] The second solution is that when the first device displays the second interface (also referred to as the second specific interface), the two devices are close to each other, and the corresponding interface is automatically pulled up. When the first device does not display the second interface, the two devices are close to each other, and the interface is not pulled up, so as to avoid false triggering.

[0141] Taking the first scenario in the foregoing (the scenario in which the second device logs in the account) as an example, the first device has logged in the account, and the second interface can be any interface of the account center of the first device. For example, as shown in Figure 5E (a), the first device displays a desktop. After receiving one or more user operations, the first device displays an interface 401 of the account center as shown in Figure 5E (b). Details about the process in which the first device opens the interface 401 are not described. The interface 401 includes a scan-to-scan button in the upper right corner. When the first device receives an operation on the scan-to-scan button, the first device displays an interface 200 as shown in Figure 5E (c).

[0142] Optionally, the second interface can be the interface 401 as shown in Figure 5E (b), the interface 200 as shown in Figure 5E (c), or another interface of the account center of the first device.

[0143] Taking the second interface as the interface 200 as shown in Figure 5E (c) as an example. When the first device displays the interface 200, if the two devices are close to each other, the corresponding interface can be pulled up. For example, as shown in Figure 5E (d), the second device displays a desktop, and the second device detects that the first device is close (the first device is displaying the interface 200). There are two processing manners. In manner A, the second device pops up a prompt box as shown in Figure 5E (f), and the prompt box includes prompt information: whether to log in the account of the first device, and further includes a “log in with this account” button. When the second device receives an operation on the button, the second device pulls up an interface 100 as shown in Figure 5E (e). In manner B, the second device directly pulls up the interface 100 as shown in Figure 5E (e), and does not need to pop up the prompt box as shown in Figure 5E (f), thereby saving the operation process. It should be understood that, because the first device has displayed the interface 200, when the two devices are close to each other, the first device continues to remain in the interface 200.

[0144] Taking the second interface as the interface 401 as shown in Figure 5E (b) as an example. When the first device displays the interface 401, if the two devices are close to each other, the corresponding interface can be automatically pulled up. For example, the first device automatically pulls up the interface 200 as shown in Figure 5E (c). As shown in Figure 5E(d) The second device displays the desktop. When the second device detects the first device approaching (the first device is currently displaying interface 401), it automatically pulls up the desktop. Figure 5E (e) Interface 100.

[0145] It should be noted that, in Figure 5E In the example, the second device displays the desktop. Optionally, the second device can also display a lock screen, a black screen, or other interfaces. Other interfaces can be any interface that the user enters after unlocking, such as the desktop, the negative one screen, or the application interface.

[0146] Taking the third scenario mentioned earlier (data cloning scenario) as an example, such as Figure 5F (a) The first device displays an interface that includes two options: "This is the old device" and "This is the new device". Optionally, the first device opens... Figure 5F The process shown in (a) may include: Desktop -> Settings -> System & Updates -> Data Cloning; or, after the first device installs an application for data cloning (e.g., "Huawei Phone Cloning") from the app store, opening the application as shown in (a) Figure 5F The interface shown in (a) is displayed when the first device receives an operation for the "This is an old device" option. Figure 5F (b) The interface 402 shown, or, directly displaying as shown in the image, is also acceptable. Figure 5F Interface 200 is shown in (c).

[0147] Optionally, the second interface can be Figure 5F (b) Interface 402, Figure 5F (c) Interface 200 or other interfaces, which may be other interfaces that the first device may display in response to an operation that says "This is an old device".

[0148] The second interface is Figure 5F (b) Taking interface 402 as an example. When the first device displays interface 402, the corresponding interface can be automatically pulled up if the two devices are close together. For example, Figure 5F (g) When the second device displays the lock screen and detects the first device approaching (the first device is currently displaying screen 402), there are two processing methods. Method A: The second device automatically pops up a lock screen. Figure 5F (g) A prompt box appears, containing device information for the first device and a prompt message indicating that data from the first device will be cloned to the second device. The prompt box also includes an "OK" button. When the second device receives an operation on the "OK" button, it can pull up... Figure 5F (h) shows interface 100; or, when the second device receives an operation on the "Confirm" button, it can prompt the user to perform identity authentication (this process) Figure 5F(Not shown in the image) to ensure that the user is operating the second device. For example, the second device can prompt the user to enter a fingerprint or password to unlock; if the verification is successful, it can pull up an icon. Figure 5F (h) Interface 100. Method B, the second device directly pulls up as follows: Figure 5F (h) interface 100, no pop-up required Figure 5F (g) The prompt box saves operations and simplifies the process. When the first device displays interface 402, if the second device is detected approaching, the prompt box can be pulled up directly. Figure 5F (c) Interface 200; or, upon receiving a pull-up command from the second device, pull up as follows: Figure 5F (c) Interface 200. For example, Figure 5F In (g), after receiving an operation on the "Confirm" button, the second device sends a pull-up command to the first device. Upon receiving the pull-up command, the first device pulls up as follows: Figure 5F (c) Interface 200. It should be noted that in this example, when the first device displays interface 402 and the second device displays the lock screen interface, the interface automatically pulls up when the two devices are close together. Optionally, the second device can also display other interfaces besides the lock screen interface. Other interfaces include a black screen or any interface that the user enters when the device is unlocked, such as the desktop, the negative one screen, or the interface of a certain application.

[0149] The second interface is Figure 5F (c) Taking interface 200 as an example. When the first device displays interface 200, the corresponding interface can be automatically pulled up if the two devices are close together. For example, Figure 5F (g) When the second device displays the lock screen and detects the first device approaching (the first device is currently displaying interface 200), there are two processing methods, as described in Method A and Method B above. Since the first device is already displaying interface 200, it remains on interface 200 when the two devices approach each other. It should be noted that in this example, which uses the scenario of the first device displaying interface 200 and the second device displaying the lock screen, and the interface automatically pulling up when the two devices approach each other as an example, the second device can optionally display other interfaces besides the lock screen. These other interfaces could be a black screen or any interface the user enters when the device is unlocked, such as the desktop, the negative one screen, or the interface of a specific application.

[0150] like Figure 5F After the first device scans the first graphic on the interface 100 of the second device via the scanning interface 200, a near-field communication connection can be established. For example, the first device can display something like... Figure 5F (d) This interface displays the message: Connecting. After a successful connection, the first device displays the following: Figure 5Fthe interface of (e) includes prompt information: please operate on the new device (i.e., the second device). The second device can display an interface for logging in an account, for example, an interface for logging in a system account (e.g., a Huawei account), which can be as shown in Figure 5F the interface of (k) shown in FIG. 13K, which includes account information (e.g., a mobile phone number) of the first device, further includes prompt information for prompting the second device to log in the account of the first device, and further includes two buttons of "synchronize to log in this account" and "set up later". When the second device receives an operation on the button of "synchronize to log in this account", the second device logs in the account of the first device through the near field communication connection (the implementation principle is described below), for example, the second device can display an interface as shown in Figure 5F the interface of (l), which displays prompt information of "logging in". After the second device logs in the account of the first device through the near field communication connection, the second device can acquire data of the account, for example, the data can be acquired in any one of the manners A to C described above. Taking the manner B as an example, after the second device successfully logs in the account of the first device, the second device can display an interface as shown in Figure 5F the data selection interface of (i), in which the user can select data. When the second device receives an operation on the button of "start migration", the second device sends a start migration instruction to the first device. After the first device receives the start migration instruction, the first device migrates data (selected by the user) to the second device through the near field communication connection. For example, the first device can display an interface as shown in Figure 5F the prompt information of (f): data migration. The second device displays an interface as shown in Figure 5F the migration progress of (j). In Figure 5F (k), when the second device receives an operation on the button of "set up later", since there is no need to log in the account of the first device, the second device can directly display Figure 5F the data selection interface of (i), and then perform data migration, the principle of which is as described above and will not be repeated.

[0151] The above are several examples of the second interface, and it should be understood that the second interface can also be other interfaces, which will not be enumerated one by one in the embodiments of the present application. It should be noted that in the second solution, when the first device displays the second interface, the display interface of the second device can not be required, and no matter what interface (e.g., a lock screen interface, a black screen, a desktop, a negative one screen or any other interface) the second device displays, the second device can automatically pull up the interface by approaching.

[0152] The third solution is that when the two devices are close, it is determined whether the condition is met, and if the condition is met, the corresponding interface is pulled up, otherwise, the interface is not pulled up. In this solution, the condition determination can be performed by either of the two devices; alternatively, the two devices can each perform condition determination. As described above, the automatic pulling up of the interface when the two devices are close can include three ways of way A to way C. If way A is adopted, the second device performs condition determination, if way B is adopted, the first device performs condition determination, and if way C is adopted, the two devices each perform condition determination. When the two devices each perform condition determination, the corresponding determination conditions of each device can be the same or different. The following takes way A as an example, that is, when the second device detects that the first device is close, it is determined whether the condition is met, and if the condition is met, the interface 100 is automatically displayed, and the first device is triggered to display the interface 200. Optionally, the condition can include at least one of the following:

[0153] Condition a, the second operating system of the second device is the same as the first operating system of the first device, for example, both are the Harmony operating system.

[0154] Condition b, the second operating system of the second device is not logged in any account.

[0155] Condition c, the first operating system of the first device is currently logged in an account. In this way, the second device needs to determine whether the first operating system of the first device is logged in an account. One possible way is that the second device sends (for example, through Bluetooth) a query request to the first device, requesting to query whether the first operating system of the first device is logged in an account. After the second device receives the query response returned by the first device, it determines whether the first operating system of the first device is logged in an account based on the query response. Optionally, the query response can include account information of the account currently logged in by the first operating system of the first device, such as account name, avatar, etc., and the account name can be a mobile phone number, email, or of course a nickname set by the user, etc.

[0156] Condition d, the second operating system of the second device is not logged in the first account, which is the account currently logged in by the first operating system of the first device. In this way, the second device needs to determine the currently logged-in account (i.e., the first account) of the first operating system of the first device, and then determine whether the second operating system of the second device is logged in the account. The second device determines the currently logged-in account of the first operating system of the first device in the manner described in condition c, which is not repeated here.

[0157] The condition e is that the second device outputs prompt information for prompting whether to log in the first account of the first device, and the second device receives a confirmation instruction for confirming the device account of the first device. Optionally, the first device can also output prompt information for prompting whether to agree to authorize the second device to log in the first account in response to the proximity of the second device; and the first device pulls up a code scanning interface if the first device receives an instruction for agreeing. In this way, the interface is pulled up only when the user agrees after the two devices are close, avoiding the interface being pulled up directly when the two devices are close, and affecting the user experience.

[0158] The three solutions above can be used alone or in combination. For example, in the case of using the first solution and the second solution in combination, the second device displays the first interface, and the first device displays the second interface, and the two devices are close to automatically pull up the corresponding interface. The above lists three solutions, which can all avoid mis-triggering. It should be understood that there can be other solutions for preventing mis-triggering, and the embodiments of the present application do not list them one by one.

[0159] In the above, the two devices can be close to automatically pull up the interface, simplifying the user operation steps. However, in actual use, the user can not be clear about the function of the two devices being close to automatically pull up the interface, and thus can not use the function well. In order to guide the user, a possible solution is that the first device and / or the second device can output guidance information for guiding the user how to operate, improving the user experience.

[0160] For example, the second device outputs guidance information (which can be referred to as first guidance information), such as Figure 6A (a), the second device displays an interface 600, and the interface 600 includes guidance information: please bring the other device close to log in the account of the other device. The user brings the first device close to the second device according to the guidance information. As Figure 6A (b), the first device displays a desktop or other interface (for example, the other interface can include a lock screen, a black screen, a negative screen, or any interface entered after unlocking) when the first device is close to the second device. When the first device detects that the second device is close, there are two processing methods. Method A, the first device pops up a prompt box as shown in Figure 6A (f), the prompt box includes the account information (for example, a mobile phone number) of the first device, and also includes prompt information for prompting that the account of the first device will be logged in on the second device. The prompt box also includes a "log in with this account" button. The first device receives an operation for the "log in with this account" button, and pulls up the interface 200 as shown in Figure 6A (d). Method B, the first device directly pulls up the interface 200 as shown in Figure 6A (d). When the second device detects that the first device is close, the second device can directly pull up the interface 200 as shown in Figure 6A(c) the interface 100, or, upon receiving the pull-up instruction sent by the first device, pull up the interface 100 as shown in Figure 6A (c) the interface 100. For example, Figure 6A (f), the first device sends a pull-up instruction to the second device after receiving the operation on the "log in with this account" button, and the second device pulls up the interface 100 as shown in Figure 6A (c) the interface 100. It should be noted that, Figure 6A (a), the second device opens the interface 600 in any manner, and the embodiments of the present application do not limit the manner. For example, the interface 300 in Figure 5B (b) contains a button (for example, a near-field login button), which is triggered to open the interface 600.

[0161] For example, the first device outputs guidance information (which can be referred to as second guidance information), and the first device displays the interface 700 as shown in Figure 6B (a), which includes the guidance information: please approach the other device to authorize it to log in to the account. The user approaches the second device to the first device according to the guidance information. For example, Figure 6B (b), the second device displays the desktop or other interfaces (for example, the other interfaces can include a lock screen, a black screen, a negative screen, or any interface entered after unlocking) when the second device approaches the first device. The first device detects the approach of the second device, and there are two processing manners. In manner A, the first device pops up a prompt box as shown in Figure 6B (f), which includes the account information (for example, a mobile phone number) of the first device, and also includes prompt information for prompting that the account of the first device will be logged in on the second device. The prompt box also includes a "log in with this account" button. The first device receives the operation on the "log in with this account" button, and pulls up the interface 200 as shown in Figure 6B (d). In manner B, the first device directly pulls up the interface 200 as shown in Figure 6B (d). When the second device detects the approach of the first device, it can directly pull up the interface 100 as shown in Figure 6B (c) the interface 100, or, upon receiving the pull-up instruction sent by the first device, pull up the interface 100 as shown in Figure 6B (c) the interface 100. For example, Figure 6B (f), the first device sends a pull-up instruction to the second device after receiving the operation on the "log in with this account" button, and the second device pulls up the interface 100 as shown in Figure 6B (c) the interface 100. It should be noted that, Figure 6B (a), the first device opens the interface 700 in any manner, and the embodiments of the present application do not limit the manner.

[0162] In the above scheme, when the first operating system of the first device has logged in the first account, the first device and the second device are automatically caused to pull up the corresponding interface when they are close to each other, and then the second operating system of the second device is caused to log in the first account by means of scanning and logging in. There is a possible case that the first operating system of the first device corresponds to multiple accounts. For example, the multiple accounts are accounts that the first operating system has logged in before, and the first account is an account that is currently logged in among the multiple accounts. Alternatively, the multiple accounts have a correlation relationship, for example, the multiple accounts belong to family-related accounts, for example, the first account is an adult account, and the other accounts are child accounts corresponding to the adult account.

[0163] When the first operating system of the first device corresponds to multiple accounts, the user can select one of the accounts, so that the second operating system of the second device logs in the account selected by the user. Optionally, when the user selects the account, the selection can be made on the first device or on the second device.

[0164] Taking the selection on the first device as an example, for example, as shown in Figure 7A (a), the second device displays the interface 600, or can also display other interfaces or a black screen. As shown in Figure 7A (b), the first device displays a desktop or other interfaces other than the desktop or a black screen. When the first device and the second device are close to each other, the second device automatically pulls up the interface 100 as shown in Figure 7A (c). The first device automatically pulls up the interface as shown in Figure 7A (d), which includes the identifiers (for example, mobile phone numbers, avatars, etc.) of the multiple accounts. The user can select an account, for example, by selecting the account through left and right sliding operations. When the first device receives an operation on the “log in with this account” button, the interface 200 as shown in Figure 7A (e) is displayed. At this time, the first device can authorize the second device to log in the account selected by the user by scanning the first pattern in the interface 100 of the second device through the interface 200.

[0165] Taking the selection on the second device as an example, for example, as shown in Figure 7B (a), the second device displays the interface 600, or can also display other interfaces, which can be a lock screen, a black screen, a desktop, a negative one screen or any interface entered after unlocking. As shown in Figure 7B (b), the first device displays a desktop or other interfaces other than the desktop, which can be a lock screen, a black screen, a negative one screen or any interface entered after unlocking. When the first device and the second device are close to each other, the second device automatically pulls up the interface as shown in Figure 7Binterface of (c), which includes the identification of the multiple accounts of the first device, and the user can select a certain account. In this way, the second device needs to determine which accounts of the first device correspond to, for example, the first device can be queried through the Bluetooth broadcast query information to determine which accounts of the first device correspond to. When the second device receives the operation of the "use this account to log in" button, the interface 100 of (d) is displayed. The second device can inform the first device of the account selected by the user, and after the first device determines the account selected by the user, there are two ways. Way A, the first device pops up a prompt box as shown in (f), which includes the account information (for example, the mobile phone number) selected by the user, and also includes a prompt information for prompting that the account will be logged in on the second device. The prompt box also includes a "use this account to log in" button. When the first device receives the operation of the "use this account to log in" button, the interface 200 of (e) is displayed. Way B, the first device directly displays the interface 200 of (e). At this time, the first device can authorize the second device to log in to the account selected by the user by scanning the first graphic in the interface 100 of the second device through the interface 200. Figure 7B Figure 7B Figure 7B Figure 7B

[0166] The above embodiments illustrate the process of opening the interface 100 of the second device and opening the interface 200 of the first device. It should be understood that after the second device opens the interface 100 and the first device opens the interface 200, the code scanning login can be performed.

[0167] The implementation principle of the code scanning login will be described below in conjunction with the accompanying drawings.

[0168] As described above, there are two ways to generate the first graphic, and the corresponding login process is different when the first graphic is generated in different ways. For example, if the first graphic is generated in the second way (i.e., the first graphic is used to establish a near field communication connection), the login process shown in Figure 8 、 Figure 9 or Figure 10 can be used. If the first graphic is generated in the first way, the login process shown in Figure 11A can be used. The following will be described respectively.

[0169] Taking the second device generating the first graphic in the second way as an example, i.e., the first graphic is used to establish a near field communication connection, then the second device can realize the password-free login of the account based on the near field communication connection. Among them, the second device can realize the password-free login of the account based on the near field communication connection, which can at least include the following three schemes.

[0170] First scheme

[0171] Please refer to Figure 8 ​​​​Another flowchart of the account login method provided by an embodiment of the present application is shown. The flowchart can be applicable to the scenario shown in Figure 1 , Figure 2 , Figure 3B , Figures 5A to 5F . As shown in Figure 8 , the flowchart can include the following steps:

[0172] S800, the first device logs in the first account.

[0173] Taking the first device in the system shown in Figure 1 as an example, the first device logs in the first account, that is, the first device logs in the cloud side, for example, logs in the first server in the cloud side. Taking the user inputting the account information and password information of the first account on the first device for login as an example, S800 can include four sub-steps, which are S800a, S800b, S800c and S800d. S800a, the first device receives an input operation, the input operation being used to input the account information and password information of the first account. The account information can be, for example, an account name. The account name can be a registered account mobile phone number, an email address, of course, it can also be a user-set nickname, etc. The password information can be a user-set login password, for example, a combination of one or more of numbers, letters and symbols. S800b, the first device sends a login request to the cloud side, for requesting to log in the first account. The login request can include the account information and password information of the first account. S800c, the cloud side verifies the first account according to the login request. Verifying the first account can include verifying the correctness of the account information and password information of the first account. For example, the cloud side compares the account information and password information carried in the login request with the stored account information and password information, if they are consistent, the verification is passed, otherwise, the verification is not passed. After the verification is passed, S800d is executed, the cloud side sends the first login credential to the first device, and correspondingly, the first device receives the first login credential sent by the cloud side. The first login credential can be understood as an identity credential issued by the cloud side for the first device, representing that the first device logs in successfully, and then the first device can use the first login credential to access the data of the cloud side. For example, when the first device needs to access data, it can send a data access request to the cloud side, and the first login credential is carried in the data access request. After the cloud side receives the data access request, the identity of the first device is verified based on the first login credential carried in the data access request, and after the verification is passed, the data is returned to the first device. Wherein, verifying the identity of the first device based on the first login credential carried in the data access request by the cloud side can include comparing the first login credential carried in the data access request with the login credential stored locally by the cloud side, if they are consistent, the verification is passed, otherwise, the verification is not passed.

[0174] For example, the first login credential can be a token.

[0175] Optionally, the first login credential can remain unchanged. Of course, in order to ensure data security, the first login credential can also be dynamically changed. For example, the server can update the first login credential at a certain period and send the updated first login credential to the first device, so that the first device uses the latest first login credential to access data. The period can be 1 week, 15 days, one month, of course, it can also be 1 day, 2 days, etc., and the embodiments of the present application are not limited. In other words, the first login credential has a time limit, and the first login credential is valid within a specified time period and invalid outside the specified time period. Therefore, after the first login credential is stolen, it cannot be used as long as it exceeds the validity period, which can to some extent avoid the persistence of data leakage.

[0176] It should be noted that from the four sub-steps of S800, the first login credential is different from the password of the first account. The first login credential is an identity credential issued by the cloud side to the first device after the account information and password information of the first account are verified, and then the first device can access data based on the first login credential. When accessing data, the account information and password information do not need to be carried again, avoiding password leakage. In addition, generally speaking, the password of the first account is unchanged unless the user modifies the password, but the first login credential can be dynamically changed and has a time limit. The principle is described above.

[0177] S801, the second device displays a first interface. The first interface can be the first interface in the first scenario (i.e., the scenario of logging in an account) described above, that is, Figure 5B the interface 301 of (b), Figure 5B the interface 302 of (c), Figure 5B the interface 100 of (d); or, it can also be the first interface in the second scenario (OOBE scenario) described above, for example, Figure 5C the interface 303 of (c), Figure 5C the interface 304 of (d), Figure 5C the interface 305 of (e), Figure 5C the interface 100 of (f); or, it can also be the first interface in the third scenario (data cloning scenario) described above, for example, Figure 5D the interface 306 of (b), Figure 5D the interface 100 of (c), etc. Optionally, S801a can be executed or not executed, so the dashed line is used in the figure.

[0178] S802, the second device and the first device are close to automatically pull up the interface, wherein the second device is not logged in the first account.

[0179] Optionally, S802 can include S802a-S802e.

[0180] S802a, the second device broadcasts a request signal, the request signal is a short-distance communication signal, for example, a Bluetooth signal; when the first device is close to the second device (for example, within 30 cm), the request signal is received. For the three different application scenarios described above, the content requested by the request signal can be different. For example, in the first scenario (i.e., the scenario of logging in an account), the second device displays the first interface (interface 301 of (b), interface 302 of (c), interface 100 of (d), or interface 306 of (b)), and broadcasts the request signal, which is used to request assistance in logging in the account. For example, in the second scenario (OOBE scenario), the second device displays the first interface (interface 303 of (c), interface 304 of (d), interface 305 of (e), or interface 100 of (f)), and broadcasts the request signal, which is used to request assistance in logging in the account. For example, in the third scenario (data cloning scenario), the second device displays the first interface (interface 100 of (c)), and broadcasts the request signal, which is used to request data migration. Figure 5B (b)’s interface 301, Figure 5B (c)’s interface 302, or Figure 5B (d)’s interface 100) displays the first interface (interface 100 of (d), or interface 305 of (e)), and broadcasts the request signal, which is used to request assistance in logging in the account. For example, in the second scenario (OOBE scenario), the second device displays the first interface (interface 304 of (d), or interface 100 of (f)), and broadcasts the request signal, which is used to request assistance in logging in the account. For example, in the third scenario (data cloning scenario), the second device displays the first interface (interface 100 of (c)), and broadcasts the request signal, which is used to request data migration. Figure 5C (c)’s interface 303, Figure 5C (d)’s interface 304, Figure 5C (e)’s interface 305, or Figure 5C (f)’s interface 100) displays the first interface (interface 100 of (d), or interface 305 of (e)), and broadcasts the request signal, which is used to request assistance in logging in the account. For example, in the second scenario (OOBE scenario), the second device displays the first interface (interface 304 of (d), or interface 100 of (f)), and broadcasts the request signal, which is used to request assistance in logging in the account. For example, in the third scenario (data cloning scenario), the second device displays the first interface (interface 100 of (c)), and broadcasts the request signal, which is used to request data migration. Figure 5D (b)’s interface 306, Figure 5D (c)’s interface 100) displays the first interface (interface 100 of (d), or interface 305 of (e)), and broadcasts the request signal, which is used to request assistance in logging in the account. For example, in the second scenario (OOBE scenario), the second device displays the first interface (interface 304 of (d), or interface 100 of (f)), and broadcasts the request signal, which is used to request assistance in logging in the account. For example, in the third scenario (data cloning scenario), the second device displays the first interface (interface 100 of (c)), and broadcasts the request signal, which is used to request data migration.

[0181] S802b, the first device outputs prompt information, which is used to prompt whether to agree to the content requested by the request signal. For example, in the first scenario, after the first device receives the request signal, the first device displays a prompt box as shown in Figure 5B (f), which includes a “use this account to log in” button. For example, in the second scenario, after the first device receives the request signal, the first device displays a prompt box as shown in Figure 5C (g), which includes a setting button. For example, in the third scenario, after the first device receives the request signal, the first device displays a prompt box as shown in Figure 5D (f), which includes a confirmation button.

[0182] S802c, when the first device receives an operation of agreeing, the first device sends an agreement signal to the second device. For example, in the first scenario, after the first device displays the prompt box as shown in Figure 5B (f), the first device receives an operation of the “use this account to log in” button, and sends the agreement signal to the second device. For example, in the second scenario, after the first device displays the prompt box as shown in Figure 5C (g), the first device receives an operation of the setting button, and sends the agreement signal to the second device. For example, in the third scenario, after the first device displays the prompt box as shown in Figure 5D(f) after the prompt box is shown, when an operation for the confirmation button is received, a consent signal is sent to the second device.

[0183] Optionally, S802b to S802c can or can not be executed, so the dashed lines are used in the figure. If not executed, S801d and S801e are executed directly after S801a.

[0184] S802d, the second device displays a first graphic. The first graphic is generated based on the second code value and is used to establish the near field communication connection. For the second code value, please refer to the foregoing description. Exemplarily, the first graphic can be the interface 100 of (d) or Figure 5B (d) or Figure 5C (f) or Figure 5D the HUAWEI RING in the interface 100 of (c).

[0185] S802e, the first device displays a code scanning interface. Exemplarily, the code scanning interface can be the interface 200 of (g) or Figure 5B (g) or Figure 5C (h) or Figure 5D (g).

[0186] S803, the first device scans the first graphic to establish the near field communication connection.

[0187] Since the first graphic is generated based on the second code value, the first device can obtain the second code value by scanning the first graphic, and can establish the near field communication connection based on the second code value. In one possible implementation, the first device sends a near field communication connection request to the second device, and the request includes the second code value. After receiving the request, the second device can verify the first device, and if the verification is passed, the second device sends an indication of consent to the connection to the first device, and the near field communication connection is completed. In one way of verifying the first device by the second device, the second device compares the second code value carried in the request with the second code value stored locally, and if they are consistent, the verification is passed, otherwise, the verification is not passed. Optionally, the near field communication connection request can further include a service ID of the second device. The service ID can be created by the second device. For example, the second device broadcasts a signal, and the signal includes the service ID. After the signal is received by the first device, the first device obtains the service ID in the signal, and then sends the second code value and the service ID to the second device in the near field communication connection. After receiving the near field communication connection request, the second device verifies the first device, for example, the second device compares the second code value carried in the near field communication connection request with the second code value stored locally, and compares the service ID carried in the near field communication connection request with the service ID stored locally, and if they are consistent, the verification is passed, otherwise, the verification is not passed.

[0188] Optionally, in order to ensure data security, the data transmitted through the near field communication connection can be encrypted using a session key. For example, the second device generates a session key and synchronizes the session key to the first device. In this way, when the first device and the second device transmit data through the near field communication connection, the session key can be used for encryption to prevent data leakage.

[0189] S804, the second device obtains the first code value from the cloud side.

[0190] It should be noted that the execution order between S804 and S802-S803 is not limited.

[0191] S805, the second device sends a first request to the first device through the near field communication connection, and the first request is used to request to log in the account of the first device. For example, the first request can include the first code value.

[0192] S806, the first device sends an authorization login request to the cloud side, which is used to request to authorize the second device to request to log in the first account.

[0193] Optionally, the authorization login request can include at least one of the following information:

[0194] (1), the first login credential. For the first login credential, please refer to the description above.

[0195] (2), the first code value. For the first code value, please refer to the description above.

[0196] (3), the related information of the first account. The related information of the first account can include the account information of the first account, and optionally, can also include the password information of the first account. For the account information and the password information of the first account, please refer to the description above.

[0197] (4), the device information of the first device. The device information of the first device can include the device type and the device model of the first device.

[0198] (5), the device information of the second device. The device information of the second device can include the device type and the device model of the second device.

[0199] S807, the cloud side performs verification according to the authorization login request.

[0200] Optionally, S807 can include: the cloud side verifying at least one of the first account, the first device and the second device. The cloud side verifying the first account can include verifying the correctness of the account information and the password information of the first account, which has been described in S800. The cloud side verifying the first device can include verifying the identity of the first device. For example, the first login credential is included in the authorization login request, and the cloud side compares the first login credential carried in the authorization login request with the stored login credential of the first device. If they are consistent, the verification is passed, otherwise, the verification is failed. For another example, the device information of the first device is included in the authorization login request, and the cloud side matches the device information of the first device carried in the authorization login request with the device information corresponding to the first account stored by the cloud side. If they are consistent, the verification is passed, otherwise, the verification is failed. The cloud side verifying the second device can include verifying the identity of the second device. For example, the first code value is included in the authorization login request, which is the verification information for the code scanning login applied by the second device to the cloud side. The cloud side can judge whether the first code value carried in the authorization login request is the code value sent by the cloud side to the second device and / or whether it is within the valid period. If yes, the verification is passed, otherwise, the verification is failed. The valid period can be the valid period of the code value specified by the cloud side, for example, 30 seconds, 50 seconds, etc. For another example, the device information of the second device is included in the authorization login request, and the cloud side matches the device information of the second device carried in the authorization login request with the device information corresponding to the first account stored by the cloud side. If they are consistent, the verification is passed, otherwise, the verification is failed.

[0201] S808, the cloud side sends the second login credential to the second device.

[0202] In the first scheme (i.e. the scheme shown in Figure 8 In the first scheme (i.e. the scheme shown in

[0203] The second scheme

[0204] In the first scheme (i.e. the scheme shown in Figure 8 In the first scheme (i.e. the scheme shown in

[0205] For example, see Figure 9 This is a schematic diagram of another account login method provided in an embodiment of this application. This process can be applied to... Figure 1 , Figure 2 , Figure 3B , Figures 5A to 5F The scene shown. (As shown) Figure 9 The process may include:

[0206] S900, the first device logs in to the first account.

[0207] It should be noted that the implementation principle of S900 is the same as described above. Figure 8 The implementation principle of S800 is the same; for example, S900 can also include four sub-steps. Figure 9 (Not shown in the text), which has been explained in detail above and will not be repeated here.

[0208] S901, the second device displays the first interface. Please refer to the previous description for information about the first interface.

[0209] S902, the interface automatically pops up when the second device approaches the first device. The second device is not logged into the first account.

[0210] As mentioned earlier, when the two devices are close together, the second device displays the first graphic, which is generated based on the second code value and used to establish a near-field communication connection. The second device then displays the QR code scanning interface. It should be noted that the implementation principle of the S902 is the same as described above. Figure 8 The implementation principle of S802 is the same; for example, S902 can also include five sub-steps. Figure 9 (not shown in the image), because Figure 8 This has already been explained in detail, so I will not repeat it here.

[0211] S903, the first device scans the first pattern and establishes a near-field communication connection.

[0212] It should be noted that the process of establishing a near-field communication connection between the first device and the second device is described above. Figure 8 The S803 in the text will not be repeated here.

[0213] S904, the first device sends the account information and password information of the first account to the second device through a near-field communication connection.

[0214] S905, the second device sends a login request to the cloud side, which includes the account information and password information of the first account.

[0215] S906, the cloud side performs verification based on the login request.

[0216] Optionally, S906 can include: verifying, by the cloud side, the correctness of the account information and the password information of the first account. For example, the cloud side compares the account information and the password information carried in the login request with the stored account information and password information. If they are consistent, the verification is passed, otherwise, the verification is failed.

[0217] S907, the cloud side sends the second login credential to the second device.

[0218] In the second scheme (i.e. Figure 9 the scheme shown), the first device sends the account information and the password information of the first account to the second device through the near field communication connection, and the second device logs in the first account after obtaining the account information and the password information. In this scheme, the first device does not need to send the authorization login request to the cloud side, so the first device can be in a networkless state. Therefore, this scheme breaks the limitation that the old machine (i.e. the first device) must be networked to assist the new machine (i.e. the second device) to log in the account.

[0219] The third scheme

[0220] In the second scheme (i.e. Figure 9 the scheme shown), the first device needs to send the account information and the password information of the first account to the second device, which is easy to cause password leakage. Once the password is leaked, the first account will be occupied by others and it is difficult to retrieve. Different from the second scheme, in the third scheme, the first device does not need to send the password to the second device, and can also assist the second device to log in the first account, reducing the possibility of password leakage. Moreover, the third scheme can also be used when the first device is in a networkless state.

[0221] For example, please refer to Figure 10 another flowchart of an account login method provided by an embodiment of the present application. The flowchart can be applied to the scenario shown in Figure 1 , Figure 2 , Figure 3B , Figures 5A to 5F . As Figure 10 shown, the flowchart can include:

[0222] S1000, the first device logs in the first account.

[0223] It should be noted that the implementation principle of S1000 is the same as that of S800 in the foregoing Figure 8 . For example, S1000 can also include four sub-steps (not shown in Figure 10 ), which have been described in detail in the foregoing and will not be repeated here.

[0224] S1001, the first device agrees with the cloud side on the first key.

[0225] Optionally, the first device can agree with the cloud side on the first key when in the networked state.

[0226] S1002, the second device displays the first interface. For the first interface, refer to the foregoing description.

[0227] S1003, the second device automatically pulls up the interface when close to the first device. The second device is not logged in the first account.

[0228] As described above, when the two devices are close, the second device pulls up the first pattern, the first pattern is generated based on the second code value, and is used to establish a near field communication connection. The second device pulls up the code scanning interface. It should be noted that the implementation principle of S1003 is the same as that of S802 in the foregoing description. For example, S1003 can also include five sub-steps (not shown in the foregoing description), and since the details have been described in the foregoing description, they will not be described here. Figure 8 Figure 10 Figure 8

[0229] S1004, the first device scans the first pattern to establish a near field communication connection.

[0230] It should be noted that the process of establishing a near field communication connection between the first device and the second device is described in S803 in the foregoing description, and thus will not be described here. Figure 8

[0231] S1005, the second device obtains the first code value from the cloud side.

[0232] S1006, the second device sends a first request to the first device through the near field communication connection, and the first request is used to request to log in the account of the first device. For example, the first request includes the first code value. For the first code value, refer to the foregoing description.

[0233] Optionally, S1005 and S1006 can be executed or not executed, and thus the dashed line is used in the foregoing description. Figure 10

[0234] Optionally, the implementation principle of S1002 to S1006 is the same as that of S801 to S805 in the foregoing description, and thus will not be described here. Figure 8

[0235] S1007, the first device encrypts the first data using the first key.

[0236] In some embodiments, the first data includes the first login credential of the first device. For the first login credential, refer to the foregoing description. Optionally, the first data can also include other information, for example, device information of the first device, account information of the first account, the first code value, etc. In order to prevent password leakage, the first data does not include the login password of the first account.​​​​​​

[0237] S1008, the first device sends the encrypted first data to the second device through the near field communication connection.

[0238] S1009, the second device sends a login request to the cloud side, for requesting to log in the first account, and the login request includes the encrypted first data.

[0239] S1010, the cloud side decrypts the encrypted first data using the first key.

[0240] S1011, the cloud side performs verification according to the login request. For S1011, please refer to S906 in Figure 9 , which will not be repeated here.

[0241] It should be noted that, Figure 10 S1001, S1007 and S1010 can not be executed, so Figure 10 the three steps in are represented by dashed lines. In addition, in S1001, the first device and the cloud side agree on the first key and a key ID, which is used to indicate the first key. In this way, in S1007, the first device can send the key ID together with the encrypted first data to the second device after encrypting the first data using the first key. The second device carries the key ID and the encrypted first data in the login request sent to the cloud side. The cloud side can first determine the first key according to the key ID, and then decrypt the encrypted first data using the first key. In this way, the cloud side can efficiently find the first key according to the key ID.

[0242] S1012, the second device receives prompt information sent by the cloud side, for prompting that the first device needs to be connected for authentication.

[0243] It should be understood that in the foregoing, the login request sent by the second device to the cloud side includes the first login credential of the first device, and the cloud side may suspect that the second device has stolen the first login credential of the first device. For safety, the cloud side can perform secondary verification (i.e., S1012-S1014), that is, verify whether the first device agrees to authorize the second device to log in the first account. Optionally, S1012-S1014 can be executed or not executed, so Figure 10 are represented by dashed lines.

[0244] Optionally, before S1012, the cloud side can further determine whether the first device is in a networked state, if it is determined that the first device is in a non-networked state, S1012 is performed, if it is determined that the first device is in a networked state, the first device is sent a prompt message to prompt whether the first device agrees to authorize the second device to log in to the first account. Optionally, after the first device receives the prompt message, the first device can output the prompt message, and optionally, a corresponding display component can be displayed, which can include a button (such as an agree button and a reject button) or the like. When the first device receives an operation on the agree button, the first device sends an instruction to authorize to the cloud side. After the cloud side receives the instruction, the second device is sent a second login credential.

[0245] S1013, the second device sends a prompt message to the first device through a near field communication connection.

[0246] In the embodiments of the present application, after the second device receives the prompt message from the cloud side, the second device can send the prompt message to the first device through a near field communication connection. The first device can output the prompt message, and optionally, a corresponding display component can be displayed, which can include a button (such as an agree button and a reject button) or the like.

[0247] S1014, the first device performs network authentication.

[0248] After the first device outputs the prompt message, the user can network the first device after seeing the prompt message. In one possible way, after the first device detects that it is networked, the first device actively sends authentication information to the cloud side to indicate that it agrees to authorize the second device to log in to the first account. After the cloud side receives the authentication information, the second device is sent a second login credential. In another possible way, the cloud side can continuously (for example, every 5 seconds) send a prompt message to the first device. After the first device is networked, the first device can receive the prompt message sent by the cloud side, and then the first device can output the prompt message and display a corresponding display component. After the first device receives an operation on the agree button, the first device sends an instruction to authorize to the cloud side. After the cloud side receives the instruction, the second device is sent a second login credential.

[0249] S1015, the cloud side sends a second login credential to the second device.

[0250] Comparison Figure 9 and Figure 10 . Figure 9 In the comparison, the first device sends account information and password information of the first account to the second device through a near field communication connection, so that the second device can use the account information and the password information to request the cloud side to log in to the first account. In this way, for the cloud side, the second device is logged in based on the account information and the password information, which belongs to independent login. Figure 10In the first scenario, the first device sends the first data to the second device through the near field communication connection, and the first data includes the first login credential of the first device. The login request sent by the second device to the cloud side includes the first data. For the cloud side, the first login credential originally issued to the first device appears in the login request of the second device, and the cloud side considers that the second device logs in to the first account on behalf of the first device, which is proxy login. Therefore, Figure 10 and Figure 9 are two different login processes. It should be noted that Figure 10 In the first scenario, the first device sends the first login credential to the second device through the near field communication connection, which has a certain risk of leakage. However, since the first login credential has a time limit, if the first login credential is stolen, it cannot be used after the expiration date. This method does not leak the password, so the first account will not be occupied by others, and compared with the case of password leakage, it can avoid the persistence of data leakage to a certain extent.

[0251] In the above embodiments, three schemes for realizing password-free login of the second device based on the near field communication connection are listed. The system (for example, the communication system shown in Figure 1 ) can use any one of the three schemes, or it can also select one of the schemes according to the actual situation. Optionally, the selection methods include the following.

[0252] Method A: The first device can determine whether it is currently connected to the network. If it is connected to the network, the first scheme can be used, and if it is not connected to the network, the second scheme or the third scheme can be used.

[0253] Method B: As described above, the first login credential has a time limit. Therefore, the first device can determine whether the first login credential is invalid. If it is invalid, the first scheme or the second scheme can be used, and if the first login credential is not invalid, the third scheme can be used. One possible scenario is that the first device has not been connected to the network for a long time, although the cloud side has updated the first login credential, the cloud side cannot synchronize the latest first login credential to the first device because the first device has not been connected to the network for a long time, resulting in the invalidation of the first login credential. In this case, the first device can use the first scheme or the second scheme.

[0254] The above methods A and B can be used alone or in combination. Taking the combined use as an example, the first device uses method A to determine to use the second scheme or the third scheme (i.e., the first device is not connected to the network), and further, the first device uses method B to determine to use the third scheme (the first login credential is not invalid).

[0255] As described above, in the case of multiple accounts of the first operation of the first device, the user can select one of the accounts, so that the second operation system of the second device logs in to the account selected by the user. In this case, the above Figures 8 to 10 In the login request (or authorized login request), the account information contained is the account information of the account selected by the user.

[0256] The previous text Figures 8 to 10 Taking the second device generating the first pattern using the second method (i.e., the first pattern is used to establish a near-field communication connection) as an example. If the second device generates the first pattern using the first method (i.e., generates the first pattern based on the first code value), it can use... Figure 11A The login process is shown below. Figure 11A This is a schematic diagram illustrating another flow of an account login method provided in an embodiment of this application. This flow can be applied to... Figure 1 , Figure 2 , Figure 3A The scene shown. (As shown) Figure 11A The process may include:

[0257] S1100, the first device logs in to the first account.

[0258] Optionally, the implementation principle of S1100 is the same as... Figure 8 The implementation principle of S800 is the same, so it will not be repeated.

[0259] S1101, the second device displays the first interface. For example... Figure 11B (a) The second device displays the desktop. After receiving one or more user operations, the second device displays, as shown below. Figure 11B (b) Interface 1101. Interface 1101 includes a "Scan to Log In" button. When the second device receives an operation on the "Scan to Log In" button, it displays as shown below. Figure 11B (c) Interface 1102, or, directly display as shown in Figure 11B (d) Interface 100. Interface 100 includes a first graphic, which is generated based on a first code value, which is obtained by the second device from the cloud. The first interface can be... Figure 11B (c) Interface 1102, or, Figure 11B (d) Interface 100.

[0260] S1102, the interface automatically pops up when the first device and the second device approach each other. The second device is not logged into the first device's account.

[0261] Optionally, S1102 may include S1102a to S1102e.

[0262] S1102a, the second device broadcasts a request signal. This request signal is a short-range communication signal, such as a Bluetooth signal. The first device will receive the request signal if it is close to the second device (e.g., within 30cm). The request signal is used to request login to the first device's account. For example, as... Figure 11B(e), the first device displays the desktop, and the request signal of the second device is received. Optionally, the first device can also display other interfaces other than the desktop, such as a lock screen interface, a black screen, a negative one screen, an interface of an application, or any interface entered after the first device is unlocked.

[0263] S1102b, the first device outputs prompt information for prompting whether to agree to the second device logging in the account of the first device. For example, as shown in Figure 11B (e), the first device displays the desktop, and the request signal of the second device is received. Optionally, the first device can also display other interfaces other than the desktop, such as a lock screen interface, a black screen, a negative one screen, an interface of an application, or any interface entered after the first device is unlocked. Figure 11B (f) shown, the prompt box includes prompt information, whether to agree to the second device logging in the account. The prompt box can also include a “log in with this account” button.

[0264] S1102c, the first device receives an agreement operation, and sends an agreement signal to the second device. For example, as shown in Figure 11B (f), the first device receives an operation on the “log in with this account” button, and sends an agreement signal to the second device.

[0265] Optionally, S1102b to S1102c can be executed or not executed, so the dashed line is used in the figure, if not executed, S1102a is directly executed S1102d and S1102e.

[0266] S1102d, the second device displays a first graph. The first graph is generated based on a first code value, and the first code value is obtained from the cloud side. For the first code value, see the foregoing description. For example, the first graph is, for example Figure 11B the interface 100 in (d).

[0267] S1102e, the first device displays a code scanning interface. For example, the code scanning interface can be FIG. 11B the interface 200 in (g).

[0268] S1103, the first device scans the first graph to obtain the first code value.

[0269] A possible way is that the first device obtains an image of the first graph by scanning, and then analyzes the first code value from the image of the first graph. Another possible way is that the first device obtains an image of the first graph by scanning, and then sends the image to the cloud side (for example, the second server), and analyzes the first code value by using the cloud side, and then returns the first code value to the first device.

[0270] S1104, the first device sends an authorized login request to the cloud side, and the authorized login request is used to indicate that the second device requests to log in the first account.

[0271] S1105, the cloud side performs verification according to the authorized login request.

[0272] S1106, the cloud side sends the second login credential to the second device.

[0273] Optionally, the principles of S1104 to S1106 are the same as those of S806 to S808 in FIG. 8 , and are not repeated here.

[0274] FIG. 12A Another flowchart of the account login method provided by an embodiment of the present application. The flowchart can be applied to the first scenario (i.e. FIG. 5B ) or the second scenario (i.e. FIG. 5C ) described above. As FIG. 12A , the flowchart includes:

[0275] S1200, the first device logs in the first account. The implementation principle of S1200 is the same as that of S800 in FIG. 8 , and is not repeated here.

[0276] S1201, the second device displays the first interface. Optionally, the first interface is an interface of the second device for logging in an account. Taking the account login scenario of the first scenario (i.e. FIG. 5B ) described above as an example, the first interface can be the interface 301 of FIG. 5B (b), FIG. 5B (c) the interface 302, FIG. 5B (d) the interface 100. Taking the OOBE scenario of the second scenario (i.e. FIG. 5C ) described above as an example, the first interface can be the interface 303 of FIG. 5C (c), FIG. 5C (d) the interface 304, FIG. 5C (e) the interface 305, FIG. 5C (f) the interface 100. Taking the data cloning scenario of the third scenario (i.e. FIG. 5D ) described above as an example, the first interface can be the interface 306 of FIG. 5D (b), FIG. 5D (c) the interface 100.

[0277] S1202, the first device and the second device are automatically pulled up to the interface when they are close to each other.

[0278] For example, the first device displays a code scanning interface in response to detecting that the second device is close. Optionally, the first device can display any interface, such as a lock screen, a black screen, a desktop, a negative one screen, or an application interface, before pulling up the code scanning interface.

[0279] Optionally, in response to detecting the approach of the second device, the first device displays a prompt message. The prompt message asks whether the user agrees to allow the second device to log in to the first account. In the first scenario (i.e....) FIG. 5B Taking the scenario of logging into an account as an example, the prompt message could be... FIG. 5B The prompt box shown in (f) includes a "Log in with this account" button. This is in the second scenario (i.e.) FIG. 5C Taking an OOBE scenario as an example, the prompt message could be... FIG. 5C The prompt box shown in (g) includes a settings button. This is in the third scenario (i.e.) FIG. 5D Taking a data cloning scenario as an example, the prompt message could be something like: FIG. 5D The prompt box shown in (f) includes a confirmation button. After the first device displays the prompt message, if it receives an agreement, it displays the QR code scanning interface. Taking the first scenario as an example, the first device displays as shown in (f). FIG. 5B Following the prompt shown in (f), if an action is received to press the "Log in with this account" button, the following will be displayed: FIG. 5B (g) The QR code scanning interface 200. Taking the second scenario as an example, the first device displays as follows: FIG. 5C Following the prompt shown in (g), if an operation on the settings button is received, the following will be displayed: FIG. 5C (h) The QR code scanning interface 200. In the third scenario (i.e. FIG. 5D Taking a data cloning scenario as an example, the first device displays as follows: FIG. 5D Following the prompt shown in (f), if an action is received for pressing the confirm button, the following will be displayed: FIG. 5D (g) The QR code scanning interface 200.

[0280] Optionally, the first device detecting the proximity of the second device may include: the first device detecting that the distance between the first device and the second device is less than a first distance (e.g., 30cm), and / or, the first device receiving a request signal broadcast by the second device, said request signal being a short-range communication signal, such as a Bluetooth signal; see [link to relevant documentation]. FIG. 8 S801 in the middle.

[0281] For example, in response to detecting the proximity of the first device, the second device displays a first graphic, wherein the first graphic is used to establish near-field communication. Optionally, the second device may directly display the first graphic in response to detecting the proximity of the first device, or it may display the first graphic upon receiving a consent command from the first device. FIG. 5B For example, when the second device displays interface 302, if the first device is detected to be approaching, it can automatically pull up as shown. FIG. 5B (d) Interface 100, which includes a first graphic; or, when the second device receives a pull-up command sent by the first device, it pulls up as shown in the image. FIG. 5BThe interface 100 of (d). For example, FIG. 5B In (f), after receiving the operation on the "Log in with this account" button, the first device sends a pull-up instruction to the second device. After receiving the pull-up instruction, the second device pulls up the interface as shown in FIG. 5B The interface 100 of (d).

[0282] Optionally, the second device detecting the first device close can include: the second device detecting that the distance between the first device and the second device is less than a second distance (for example, 30 cm), and / or the second device receiving a consent signal returned by the first device, please refer to S801 in FIG. 8 In the first scenario, after the first device displays the prompt box as shown in FIG. 5B (f), the first device receives the operation on the "Log in with this account" button and sends a consent signal to the second device. In the second scenario, after the first device displays the prompt box as shown in FIG. 5C (g), the first device receives the operation on the setting button and sends a consent signal to the second device. In the third scenario, after the first device displays the prompt box as shown in FIG. 5D (f), the first device receives the operation on the confirmation button and sends a consent signal to the second device.

[0283] S1203, the first device scans the first pattern through the scanning code interface, and establishes a near field communication connection with the second device.

[0284] Optionally, the first device can obtain a second code value by scanning the first pattern. The principle of establishing a near field communication connection based on the second code value is described in 803 of FIG. 8

[0285] S1204, the first device sends first data to the second device through the near field communication connection, wherein the first data includes the first login credential.

[0286] Optionally, the first login credential can be a token. In some embodiments, the first data can not include the login password of the first account, so as to avoid password leakage. In other embodiments, the first data is encrypted using a first key, and the first key is a key agreed by the server corresponding to the first device and the first account, please refer to S1007 in FIG. 10

[0287] S1205, the second device logs in the first account based on the first login credential

[0288] Optionally, the implementation principle of S1206 is described in S1009 to S1012 of FIG. 10

[0289] ​​​It should be noted that if the first interface displayed by the second device in S1201 is the third scenario mentioned above (i.e. FIG. 5D The first interface in a data cloning scenario, for example FIG. 5D (b) Interface 306 FIG. 5D (c) Interface 100, then after S1205, may further include: the first device sending second data to the second device via a near-field communication connection, the second data being user data stored in the first device. After receiving the second data, the second device stores the second data. For example, FIG. 5D In (l), after the second device successfully logs into the account of the first device, it can display... FIG. 5D (d) A data selection interface where the user can select data. When the second device receives an operation on the "Start Migration" button, it sends a start migration command to the first device. After receiving the start migration command, the first device sends second data (e.g., the data selected by the user) to the second device via a near-field communication connection. For example, the first device may display... FIG. 5D (j) The message reads: Data migration in progress. The second device displays the following: FIG. 5D (e) Migration progress.

[0290] FIG. 12B This is another flowchart illustrating an embodiment of the account login method provided in this application. This process can be applied to the third scenario described above (i.e....). FIG. 5D )).like FIG. 12B The process includes:

[0291] S1300, the first device logs into the first account. The implementation principle of S1200 is... FIG. 8 The implementation principle of S800 is the same, so it will not be repeated.

[0292] S1301, the second device displays the first interface. The first interface is used to migrate data from other devices. This relates to the third scenario mentioned earlier (i.e....). FIG. 5D Taking a data cloning scenario as an example, the first interface can be... FIG. 5D (b) Interface 306 FIG. 5D (c) Interface 100.

[0293] S1302, the interface automatically pops up when the first and second devices approach each other.

[0294] For example, the first device displays a QR code scanning interface in response to detecting the second device approaching. Optionally, before displaying the QR code scanning interface, the first device can display any interface, such as a lock screen, a black screen, a desktop, a negative one screen, or an application interface.

[0295] Optionally, in response to detecting the proximity of the second device, the first device displays a prompt message. The prompt message asks whether the user agrees to migrate data to the second device. In the third scenario (i.e....) FIG. 5D Taking a data cloning scenario as an example, the prompt message could be something like: FIG. 5D The prompt box shown in (f) includes a confirmation button. After the first device displays the prompt message, if it receives an agreement, it displays the QR code scanning interface. Taking the third scenario as an example, the first device displays as shown in (f). FIG. 5D After the prompt box shown in (f) is displayed, when an operation is received for the confirmation button, the following will be shown: FIG. 5D (g) The QR code scanning interface 200.

[0296] Optionally, the first device detecting the proximity of the second device may include: the first device detecting that the distance between the first device and the second device is less than a first distance (e.g., 30cm), and / or, the first device receiving a request signal broadcast by the second device, said request signal being a short-range communication signal, such as a Bluetooth signal; see [link to relevant documentation]. FIG. 8 S801 in the middle.

[0297] For example, in response to detecting the proximity of the first device, the second device displays a first graphic, wherein the first graphic is used to establish near-field communication. Optionally, the second device may directly display the first graphic in response to detecting the proximity of the first device, or it may display the first graphic upon receiving a consent command from the first device. FIG. 5D For example, when the second device displays interface 306, if the first device is detected approaching, it can automatically pull up as shown. FIG. 5D (c) Interface 100, which includes a first graphic; or, when the second device receives a pull-up command sent by the first device, it pulls up as shown in the image. FIG. 5D (c) Interface 100. For example, FIG. 5D In (f), after receiving an operation on the "Confirm" button, the first device sends a pull-up command to the second device. Upon receiving the pull-up command, the second device pulls up as shown. FIG. 8 (c) Interface 100.

[0298] Optionally, the second device detecting the proximity of the first device may include: the second device detecting that the distance between the first and second devices is less than a second distance (e.g., 30cm), and / or, the second device receiving a consent signal returned by the first device. (See also: [link to relevant documentation]). FIG. 5D The S801 in the example. Taking the third scenario as an example, the first device displays as follows: FIG. 8 After the prompt box shown in (f) is received, when an operation is performed on the confirmation button, an agreement signal is sent to the second device.

[0299] S1304, the first device scans the first pattern through the scanning code interface, and establishes a near field communication connection with the second device.

[0300] Optionally, the first device can obtain the second code value by scanning the first pattern, and the principle of establishing the near field communication connection based on the second code value can be referred to 803 in FIG. 13

[0301] S1305, the first device sends first data to the second device through the near field communication connection. The first data includes user data stored in the first device. The user data can be data in each application (system application or third-party application) in the first device, such as data in a photo album application, a memo, a contact list, a calendar, and the like.

[0302] S1306, the second device stores the first data.

[0303] Hereinafter, an electronic device provided by an embodiment of the present application is introduced. The electronic device can be the first device, the second device or the cloud side in the foregoing.

[0304] For example, refer to FIG. 13 a structural schematic diagram of the electronic device provided by an embodiment of the present application. As shown in FIG. 13 the electronic device can include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (universal serial bus, USB) interface 130, a charge management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a loudspeaker 170A, a receiver 170B, a microphone 170C, a headset interface 170D, a sensor module 180, a key 190, a motor 191, an indicator 192, a camera 193, a display screen 194, and a subscriber identification module (subscriber identification module, SIM) card interface 195, and the like. The sensor module 180 can include a pressure sensor 180A, a gyroscope sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity light sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, and the like.

[0305] ​The processor 110 can include one or more processing units, for example: the processor 110 can include an application processor (AP), a modem processor, a graphics processing unit (GPU), an image signal processor (ISP), a controller, a memory, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural-network processing unit (NPU), etc. Different processing units can be independent devices or integrated in one or more processors. The controller can be the nervous system and command center of the electronic device. The controller can generate operation control signals according to instruction operation codes and timing signals, and complete the control of fetching and executing instructions. A memory can also be provided in the processor 110, used to store instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. The memory can save instructions or data that the processor 110 has just used or repeatedly uses. If the processor 110 needs to use the instructions or data again, it can directly call from the memory. This avoids repeated access and reduces the waiting time of the processor 110, thereby improving the efficiency of the system.

[0306] In some embodiments, the processor 110 can perform the account login method provided in the embodiments of the present application.

[0307] In some embodiments, the processor 110 can include one or more interfaces. The interface can include an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (I2S) interface, a pulse code modulation (PCM) interface, a universal asynchronous receiver / transmitter (UART) interface, a mobile industry processor interface (MIPI), a general-purpose input / output (GPIO) interface, a subscriber identity module (SIM) interface, and / or a universal serial bus (USB) interface, etc.

[0308] The I2C interface is a bidirectional synchronous serial bus, including a serial data line (SDA) and a serial clock line (SCL). In some embodiments, the processor 110 can contain multiple sets of I2C bus. The processor 110 can be coupled to the touch sensor 180K, the charger, the flash, the camera 193, etc. through different I2C bus interfaces respectively. For example, the processor 110 can be coupled to the touch sensor 180K through an I2C interface, so that the processor 110 and the touch sensor 180K communicate through the I2C bus interface, and the touch function of the electronic device 100 is realized.

[0309] The I2S interface can be used for audio communication. In some embodiments, the processor 110 can contain multiple sets of I2S bus. The processor 110 can be coupled to the audio module 170 through the I2S bus, and communication between the processor 110 and the audio module 170 is realized. In some embodiments, the audio module 170 can deliver audio signals to the wireless communication module 160 through the I2S interface, and the function of answering a phone through a Bluetooth headset is realized.

[0310] The PCM interface can also be used for audio communication, sampling, quantizing and encoding analog signals. In some embodiments, the audio module 170 and the wireless communication module 160 can be coupled through the PCM bus interface. In some embodiments, the audio module 170 can also deliver audio signals to the wireless communication module 160 through the PCM interface, and the function of answering a phone through a Bluetooth headset is realized. Both the I2S interface and the PCM interface can be used for audio communication.

[0311] The UART interface is a universal serial data bus, which is used for asynchronous communication. The bus can be a bidirectional communication bus. It converts the data to be transmitted between serial communication and parallel communication. In some embodiments, the UART interface is usually used to connect the processor 110 and the wireless communication module 160. For example, the processor 110 communicates with the Bluetooth module in the wireless communication module 160 through the UART interface, and the Bluetooth function is realized. In some embodiments, the audio module 170 can deliver audio signals to the wireless communication module 160 through the UART interface, and the function of playing music through a Bluetooth headset is realized.

[0312] The MIPI interface can be used to connect the processor 110 and the display screen 194, the camera 193 and other peripheral devices. The MIPI interface includes a camera serial interface (CSI), a display serial interface (DSI), and the like. In some embodiments, the processor 110 and the camera 193 communicate through the CSI interface to implement the photographing function of the electronic device 100. The processor 110 and the display screen 194 communicate through the DSI interface to implement the display function of the electronic device 100.

[0313] The GPIO interface can be configured by software. The GPIO interface can be configured as a control signal or as a data signal. In some embodiments, the GPIO interface can be used to connect the processor 110 and the camera 193, the display screen 194, the wireless communication module 160, the audio module 170, the sensor module 180, and the like. The GPIO interface can also be configured as an I2C interface, an I2S interface, a UART interface, a MIPI interface, and the like.

[0314] The USB interface 130 is an interface that conforms to the USB standard specification, and can be a Mini USB interface, a Micro USB interface, a USB Type C interface, or the like. The USB interface 130 can be used to connect a charger to charge the electronic device 100, or to transmit data between the electronic device 100 and a peripheral device. It can also be used to connect a headset to play audio through the headset. The interface can also be used to connect other electronic devices, such as AR devices and the like.

[0315] It can be understood that the interface connection relationship between the modules shown in the embodiments of the present application is only illustrative and does not constitute a structural limitation of the electronic device 100. In other embodiments of the present application, the electronic device 100 can also use different interface connection methods or combinations of multiple interface connection methods as described in the above embodiments.

[0316] The wireless communication function of the electronic device 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, and the like. The antenna 1 and the antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in the electronic device can be used to cover a single or multiple communication frequency bands. Different antennas can also be multiplexed to improve the utilization rate of the antennas. For example, the antenna 1 can be multiplexed as a diversity antenna for a wireless local area network. In some other embodiments, the antenna can be used in combination with a tuning switch.

[0317] The mobile communication module 150 can provide a solution for wireless communication including 2G / 3G / 4G / 5G, etc. applied to the electronic device. The mobile communication module 150 can include at least one filter, a switch, a power amplifier, a low noise amplifier (LNA), etc. The mobile communication module 150 can receive electromagnetic waves by the antenna 1, and perform filtering, amplification, etc. on the received electromagnetic waves, and transfer the processed signals to the modem processor for demodulation. The mobile communication module 150 can also amplify the signals modulated by the modem processor, and radiate the signals as electromagnetic waves through the antenna 1. In some embodiments, at least part of the functional modules of the mobile communication module 150 can be disposed in the processor 110. In some embodiments, at least part of the functional modules of the mobile communication module 150 can be disposed in the same device as at least part of the modules of the processor 110.

[0318] The wireless communication module 160 can provide a solution for wireless communication including wireless local area networks (WLAN) (e.g., wireless fidelity (Wi-Fi) network), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared (IR) technology, etc. applied to the electronic device. The wireless communication module 160 can be one or more devices integrated with at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2, performs frequency modulation and filtering on the electromagnetic wave signals, and transmits the processed signals to the processor 110. The wireless communication module 160 can also receive signals to be transmitted from the processor 110, perform frequency modulation and amplification on the signals, and radiate the signals as electromagnetic waves through the antenna 2.

[0319] In some embodiments, the antenna 1 and the mobile communication module 150 of the electronic device are coupled, and the antenna 2 and the wireless communication module 160 are coupled, so that the electronic device can communicate with a network and other devices through wireless communication technology.

[0320] The display screen 194 is used to display the display interface of an application, etc. The display screen 194 includes a display panel. In some embodiments, the electronic device can include one or N display screens 194, N being a positive integer greater than 1.

[0321] The electronic device 100 can implement a photographing function through an ISP, a camera 193, a video codec, a GPU, a display 194, and an application processor, etc. Among them, the ISP is used to process data fed back by the camera 193.

[0322] The internal memory 121 can be used to store computer executable program codes, which include instructions. The processor 110 executes various function applications and data processing of the electronic device by running the instructions stored in the internal memory 121. The internal memory 121 can include a program storage area and a data storage area. Among them, the program storage area can store an operating system, software codes of at least one application program, etc. The data storage area can store data (such as images, videos, etc.) generated during use of the electronic device, etc. In addition, the internal memory 121 can include a high-speed random access memory, and can also include a non-volatile memory, such as at least one magnetic disk storage device, a flash memory device, a universal flash storage, etc.

[0323] 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 electronic device. The external memory card communicates with the processor 110 through the external memory interface 120 to implement a data storage function. For example, files such as pictures and videos are saved in the external memory card.

[0324] The electronic device can implement an audio function through an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, and an application processor, etc. For example, music playing, recording, etc.

[0325] The audio module 170 is used to convert digital audio information into an analog audio signal output, and is also used to convert an analog audio input into a digital audio signal. The audio module 170 can also be used to encode and decode audio signals. In some embodiments, the audio module 170 can be disposed in the processor 110, or part of the function modules of the audio module 170 can be disposed in the processor 110.

[0326] The speaker 170A, also known as a “loudspeaker”, is used to convert an audio electrical signal into an acoustic signal. The electronic device 100 can listen to music or listen to an external speaker scene such as a hands-free call through one or more speakers 170A.

[0327] The receiver 170B, also known as a “earpiece”, can be one or more, and is used to convert an audio electrical signal into an acoustic signal. When the electronic device 100 answers a call or a voice message, the receiver 170B can be held close to the ear to listen to the voice.

[0328] The microphone 170C, also known as a “microphone”, “sound transducer”, is used to convert an acoustic signal into an electrical signal.

[0329] The earphone interface 170D is used to connect a wired earphone.

[0330] The pressure sensor 180A is used to sense a pressure signal and can convert the pressure signal into an electrical signal. In some embodiments, the pressure sensor 180A can be disposed on the display screen 194.

[0331] The gyro sensor 180B can be used to determine the motion posture of the electronic device. In some embodiments, the angular velocity of the electronic device around three axes (i.e., x, y, and z axes) can be determined by the gyro sensor 180B. The gyro sensor 180B can be used for anti-shake shooting.

[0332] The barometric sensor 180C is used to measure air pressure. In some embodiments, the electronic device calculates altitude, assists positioning and navigation by using the air pressure value measured by the barometric sensor 180C.

[0333] The magnetic sensor 180D includes a Hall sensor. The electronic device can detect the opening and closing of a flip cover by using the magnetic sensor 180D.

[0334] The acceleration sensor 180E can detect the magnitude of acceleration of the electronic device in various directions (generally three axes). When the electronic device is stationary, the magnitude and direction of gravity can be detected.

[0335] The distance sensor 180F is used to measure distance. The electronic device can measure distance by infrared or laser.

[0336] The proximity light sensor 180G can include, for example, a light emitting diode (LED) and a light detector, such as a photodiode. The light emitting diode can be an infrared light emitting diode. The electronic device emits infrared light outwardly by the light emitting diode. The electronic device detects infrared reflected light from nearby objects using the photodiode. When sufficient reflected light is detected, it can be determined that there is an object near the electronic device. When insufficient reflected light is detected, the electronic device can determine that there is no object near the electronic device.

[0337] The ambient light sensor 180L is used to sense ambient light brightness. The electronic device can adaptively adjust the display screen 194 brightness according to the sensed ambient light brightness.

[0338] The fingerprint sensor 180H is used to collect a fingerprint.

[0339] The temperature sensor 180J is used to detect temperature.

[0340] The touch sensor 180K, also referred to as a "touch panel". The touch sensor 180K can be disposed on the display screen 194, and the touch sensor 180K and the display screen 194 form a touch screen, also referred to as a "touch screen". The touch sensor 180K is used to detect touch operations acting on or near it. The touch sensor can pass the detected touch operation to the application processor to determine the touch event type.

[0341] The bone conduction sensor 180M can obtain a vibration signal. In some embodiments, the bone conduction sensor 180M can obtain a vibration signal of a human body sound part vibration bone block.

[0342] The keys 190 include a power-on key, a volume key, and the like. The keys 190 can be mechanical keys. They can also be touch keys. The electronic device can receive key inputs, generate key signal inputs related to user settings and function control of the electronic device. The motor 191 can generate a vibration prompt. The motor 191 can be used for incoming call vibration prompts, and can also be used for touch vibration feedback. The indicator 192 can be an indicator light, which can be used to indicate the charging state, the power change, and can also be used to indicate messages, missed calls, notifications, and the like. The SIM card interface 195 is used to connect the SIM card. The SIM card can be inserted into or removed from the SIM card interface 195 to achieve contact and separation with the electronic device.

[0343] It can be understood that, FIG. 13 The components shown do not constitute a specific limitation on the electronic device. The electronic device in the embodiments of the present application can include more or fewer components. In addition, FIG. 13 the combination / connection relationship between the components in FIG. 14 may also be adjusted and modified.

[0344] FIG. 14 Another schematic diagram of a communication system provided by the embodiments of the present application is shown. As FIG. 14 , the communication system includes a first device and a second device. Optionally, although FIG. 14 not shown, the communication system can also include a cloud side. FIG. 14 The left half of the figure is the structure of the second device, and the right half is the structure of the first device. The second device includes various applications and a second operating system. The second operating system can include a code value acquisition unit and an account login unit. The second device can also include a distributed architecture. The distributed architecture includes a device discovery module and a device connection module. It should be noted that, FIG. 14In an embodiment, the distributed architecture is independent of the second operating system. Alternatively, the distributed architecture can be built-in in the second operating system. FIG. 14 In an embodiment, the distributed architecture is independent of the first operating system. Alternatively, the distributed architecture can be built-in in the first operating system.

[0345] In an embodiment, the distributed architecture is independent of the first operating system. Alternatively, the distributed architecture can be built-in in the first operating system. FIG. 15 In an embodiment, the distributed architecture is independent of the first operating system. Alternatively, the distributed architecture can be built-in in the first operating system.

[0346] The device discovery module in the distributed architecture of the second device can discover the surrounding devices. Therefore, when the first device is close to the second device, the device discovery module in the second device can discover the first device. Similarly, the device discovery module in the distributed architecture of the first device can also discover the surrounding devices. Therefore, when the second device is close to the first device, the device discovery module in the first device can also discover the second device. In other words, the first device and the second device can discover each other.

[0347] Then, the code value acquisition unit in the second device acquires a second code value. The second operating system generates a first graphic based on the second code value, and displays the first graphic. The second device can trigger the first device to pull up a code scanning interface. For example, the second device broadcasts a signal through the distributed architecture, and the signal is used to instruct the receiving end to pull up the code scanning interface. After receiving the signal, the first device pulls up the code scanning interface.

[0348] Then, the first device scans the first graphic displayed by the second device through the code scanning interface, and establishes a near field communication connection through the connection module in the distributed architecture. The account login unit in the first device can assist the second device to log in the first account based on the near field communication connection. The account login unit in the first device can assist the second device to log in the first account through three schemes. The three schemes are the first scheme, the second scheme and the third scheme mentioned above. For the three schemes, please refer to the foregoing description, which will not be repeated here.

[0349] FIG. 15 Another structural diagram of the electronic device is provided in an embodiment of the present application. The electronic device 1500 can be the first device, the second device or the cloud side mentioned above. As shown in FIG. 15, the electronic device 1500 includes a processor 1501, a memory 1502 and a communication interface 1503. FIGS. 1-14As shown, the electronic device 1500 can include one or more processors 1501, one or more memories 1502, a communication interface 1503, and one or more computer programs 1504, which can be connected through one or more communication buses 1505. The one or more computer programs 1504 are stored in the memory 1502 and configured to be executed by the one or more processors 1501, and the one or more computer programs 1504 include instructions. For example, when the electronic device 1500 is the first device in the foregoing, the instructions can be used to perform the related steps of the first device in any of the embodiments of the foregoing FIGS. 1-14 . For example, when the electronic device 1500 is the second device in the foregoing, the instructions can be used to perform the related steps of the second device in any of the embodiments of the foregoing FIGS. 1-14 . For example, when the electronic device 1500 is the cloud side in the foregoing, the instructions can be used to perform the related steps of the cloud side in any of the embodiments of the foregoing FIG. 1 . The communication interface 1503 is configured to realize the communication between the electronic device 1500 and other devices, and the communication interface can be a transceiver, for example.

[0350] In the embodiments of the present application, the method provided by the embodiments of the present application is introduced from the perspective of the electronic device (for example, a mobile phone or a cloud side) as an execution subject. In order to implement the functions in the method provided by the embodiments of the present application, the terminal device can include a hardware structure and / or a software module, and the above functions are implemented in the form of hardware structure, software module, or hardware structure plus software module. Whether a certain function in the above functions is implemented in the form of hardware structure, software module, or hardware structure plus software module depends on the specific application and design constraints of the technical solution.

[0351] In the embodiments described above, all or some of the embodiments can be implemented by software, hardware, firmware or any combination thereof. When implemented by software, all or some of the embodiments can be implemented in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded into and executed by a computer, all or some of the procedures or functions described in the embodiments of the present application are performed. The computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions can be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be transmitted from a website, a computer, a server or a data center to another website, computer, server or data center through a wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) manner. The computer readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that includes one or more available media sets. The available media can be a magnetic medium (for example, floppy disk, hard disk, magnetic tape), an optical medium (for example, DVD), or a semiconductor medium (for example, solid state disk (SSD)) and the like. The solutions of the above embodiments can be combined without conflict.

[0352] Based on the above embodiments, the present application also provides a computer program product including instructions, which, when executed on a computer, cause the computer to perform the methods described in the embodiments of the present application.

[0353] Based on the above embodiments, the present application also provides a computer readable storage medium, which stores a computer program. When the computer program is executed on a computer, the computer program causes the computer to perform the methods described in the embodiments of the present application.

[0354] Based on the above embodiments, the present application also provides a chip for reading a computer program stored in a memory, implementing the methods described in the embodiments of the present application.

[0355] Based on the above embodiments, the present application provides a chip system, which includes a processor for supporting a computer device to implement the methods described in the embodiments of the present application. In a possible design, the chip system further includes a memory for storing the necessary programs and data of the computer device. The chip system can be composed of a chip, or can include a chip and other discrete devices.

[0356] Based on the above embodiments, the present application provides a communication system, which comprises a first device and a second device, and optionally, a server (i.e. cloud side). For the method steps performed by the first device, the second device and the server, please refer to the foregoing description.

[0357] Those skilled in the art will understand that the embodiments of the present application can be provided as methods, systems or computer program products. Therefore, the present application can take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Moreover, the present application can take the form of a computer program product implemented on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage etc.) containing computer-usable program code.

[0358] The present application is described with reference to the flowcharts and / or block diagrams of the methods, apparatus (systems) and computer program products according to this application. It should be understood that each flow and / or block in the flowcharts and / or block diagrams, and the combination of flows and / or blocks in the flowcharts and / or block diagrams can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor or other programmable data processing apparatus to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing apparatus produce the functions specified in the flowcharts and / or block diagrams. FIG. 1 one or more flows and / or blocks FIG. 1 means for performing the function specified by one or more blocks.

[0359] These computer program instructions can also be stored in a computer-readable memory that can direct the computer or other programmable data processing apparatus to work in a specific manner, so that the instructions stored in the computer-readable memory produce a product including instruction means, which implements the functions specified in the flowcharts and / or block diagrams. FIG. 1 one or more flows and / or blocks FIG. 1 means for performing the function specified by one or more blocks.

[0360] These computer program instructions can also be loaded onto a computer or other programmable data processing apparatus, so that a series of operation steps are performed on the computer or other programmable data processing apparatus to produce a computer-implemented process, so that the instructions executed on the computer or other programmable data processing apparatus provide functions for implementing the functions specified in the flowcharts and / or block diagrams. FIG. 1 one or more flows and / or blocks ​ means for performing the function specified by one or more blocks.

[0361] Obviously, many modifications and variations of the present application are possible in light of the above teachings. It is, therefore, to be understood that within the scope of the appended claims and their equivalents, the application can be practiced otherwise than as specifically described.

Claims

1. An account login method, characterized in that, Applied to a communication system, the communication system including a first device and a second device, the method includes: The second device displays a first interface, which is used to log in to an account; If the first device is currently logged into the first account on the operating system of the first device, the first device will display the QR code scanning interface if it determines that the second device is close to the first device based on the distance between the second device and the first device. The second device determines that the first device is close to the second device based on the distance between the first device and the second device, and then displays a first graphic, which is used to establish near-field communication; The first device scans the first graphic through the scanning interface to establish a near-field communication connection with the second device; The first device sends first data to the second device through the near-field communication connection, the first data including the first login credentials of the first device; The second device logs into the first account based on the first login credential.

2. The method according to claim 1, characterized in that, The first interface includes any one of the following: The first interface is the login interface for the account in the settings application of the second device, or The first interface is an interface of the second device during the OOBE process, or The first interface is used to migrate data from other devices.

3. The method according to claim 1, characterized in that, The first device is currently in a no-network state.

4. The method according to claim 1, characterized in that, Before the first device displays the QR code scanning interface, the method further includes: the first device displaying a lock screen, a black screen, a desktop, a negative one screen, or an application interface.

5. The method according to claim 1, characterized in that, The first device determines that the second device is close to the first device based on the distance between the second device and the first device, including: the first device detects that the distance between the first device and the second device is less than a first distance, and determines that the second device is close to the first device; The second device determines that the first device is close to the second device based on the distance between the first device and the second device, including: the second device detects that the distance between the first device and the second device is less than a second distance, and determines that the first device is close to the second device.

6. The method according to any one of claims 1-5, characterized in that, The first device determines that the second device is close to the first device based on the distance between the second device and the first device, and displays a QR code scanning interface, including: The first device determines that the second device is close to the first device based on the distance between the second device and the first device, and displays a prompt message. The prompt message is used to ask whether the user agrees to allow the second device to log in to the first account. When the first device receives the consent request, it displays the QR code scanning interface.

7. The method according to claim 6, characterized in that, The method further includes: the first device sending an agreement instruction to the second device, the agreement instruction being used to indicate that the second device is authorized to log in to the first account; the second device displaying a first graphic, including: when the second device receives the agreement instruction, it displays the first graphic.

8. The method according to any one of claims 1-5, characterized in that, The first login credential is a token.

9. The method according to any one of claims 1-5, characterized in that, The first data does not contain the login password of the first account, and / or the first data is encrypted using a first key, which is a key agreed upon by the first device and the server corresponding to the first account.

10. The method according to any one of claims 1-5, characterized in that, The first device determines that the second device is close to the first device based on the distance between the second device and the first device, and displays a QR code scanning interface, including: The first device determines that the second device is closer to the first device based on the distance between the second device and the first device, and displays N accounts of the first device, where N is a positive integer; When the first device receives an operation to select the first account, it displays the QR code scanning interface.

11. The method according to claim 1, characterized in that, The second device logs into the first account based on the first login credential, including: The second device sends a login request to the server corresponding to the first account. The login request is used to request login to the first account, and the login request includes the first login credential. The second device receives the second login credential sent by the server.

12. The method according to claim 11, characterized in that, Before the second device receives the second login credential sent by the server, the method further includes: The second device receives a prompt message sent by the server, the prompt message being used to indicate that the first device needs to connect to the network for authentication; The second device sends the prompt message to the first device via the near-field communication connection; The first device outputs the prompt information; After the first device connects to the network, it sends authentication information to the server, which indicates that the second device is authorized to log in to the first account.

13. The method according to any one of claims 2-5, characterized in that, When the first interface is an interface used for migrating data from other devices, the method further includes: The first device sends second data to the second device through the near-field communication connection, the second data including user data stored in the first device; The second device stores the second data.

14. An account login method, characterized in that, Applied to a first device, the method includes: If the first device is currently logged into the first account on the operating system of the first device, the first device will display the QR code scanning interface if it determines that the second device is close to the first device based on the distance between the second device and the first device. The first device scans the first graphic on the second device through the scanning interface to establish a near-field communication connection with the second device; The first device sends first data to the second device through the near-field communication connection. The first data includes a first login credential of the first device, which is used by the second device to log in to the first account.

15. The method according to claim 14, characterized in that, The first device is currently in a no-network state.

16. The method according to claim 14, characterized in that, Before the first device displays the QR code scanning interface, the method further includes: the first device displaying a lock screen, a black screen, a desktop, a negative one screen, or an application interface.

17. The method according to any one of claims 14-16, characterized in that, The first device determines that the second device is close to the first device based on the distance between the second device and the first device, and then displays a scanning interface, including: The first device determines that the second device is close to the first device based on the distance between the second device and the first device, and displays a prompt message. The prompt message is used to ask whether the user agrees to allow the second device to log in to the first account. When the first device receives the consent request, it displays the QR code scanning interface.

18. The method according to any one of claims 14-16, characterized in that, The first login credential is a token.

19. The method according to any one of claims 14-16, characterized in that, The first data does not contain the login password of the first account, and / or the first data is encrypted using a first key, which is a key agreed upon by the first device and the server corresponding to the first account.

20. The method according to any one of claims 14-16, characterized in that, The first device determines that the second device is close to the first device based on the distance between the second device and the first device, and displays a scanning interface, including: The first device determines that the second device is closer to the first device based on the distance between the second device and the first device, and displays N accounts of the first device, where N is a positive integer; When the first device receives an operation to select the first account, it displays the QR code scanning interface.

21. The method according to any one of claims 14-16, characterized in that, The method further includes: The first device receives a prompt message sent by the second device through the near-field communication connection. The prompt message is used to indicate that the first device needs to be connected to the network for authentication. The first device outputs the prompt information; After the first device connects to the network, it sends authentication information to the server corresponding to the first account. The authentication information is used to indicate that the second device is allowed to log in to the first account.

22. The method according to any one of claims 15-16, characterized in that, The second device displays a first interface. When the first interface is an interface used for migrating data from other devices, the method further includes: The first device sends second data to the second device through the near-field communication connection, the second data including user data stored in the first device.

23. An account login method, characterized in that, Applied to a second device, the method includes: The second device displays a first interface, which is used to log in to an account; The second device determines that the first device is close to the second device based on the distance between the first device and the second device, and displays a first graphic. The first graphic is used to establish near-field communication. The first graphic is used to enable the first device to display a scanning interface when it determines that the second device is close to the first device based on the distance between the second device and the first device. The second device, in response to the first device scanning the first pattern, establishes a near-field communication connection with the first device; The second device receives first data sent by the first device through the near-field communication connection, the first data including the first login credentials of the first device; The second device logs into the first account based on the first login credential.

24. The method according to claim 23, characterized in that, The first interface includes any one of the following: The first interface is the login interface for the account in the settings application of the second device, or The first interface is an interface of the second device during the OOBE process, or The first interface is used to migrate data from other devices.

25. The method according to claim 23, characterized in that, Before the second device displays the first graphic, the method further includes: The second device receives a consent instruction sent by the first device, the consent instruction being used to indicate consent for the second device to log in to the first account.

26. The method according to any one of claims 23-25, characterized in that, The first login credential is a token.

27. The method according to any one of claims 23-25, characterized in that, The first data does not contain the login password of the first account, and / or the first data is encrypted using a first key, which is a key agreed upon by the first device and the server corresponding to the first account.

28. The method according to any one of claims 23-25, characterized in that, The second device logs into the first account based on the first login credential, including: The second device sends a login request to the server corresponding to the first account. The login request is used to request login to the first account, and the login request includes the first login credential. The second device receives the second login credential sent by the server.

29. The method according to claim 28, characterized in that, Before the second device receives the second login credential sent by the server, the method further includes: The second device receives a prompt message sent by the server, the prompt message being used to indicate that the first device needs to connect to the network for authentication; The second device sends the prompt message to the first device via the near-field communication connection.

30. The method according to claim 25, characterized in that, When the first interface is an interface used for migrating data from other devices, the method further includes: The second device receives second data sent by the first device through the near-field communication connection, the second data including user data stored in the first device; The second device stores the second data.

31. A communication system, characterized in that, include: A first device is configured to perform the method as described in any one of claims 14-22; A second device is used to perform the method as described in any one of claims 23-30.

32. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the method as described in any one of claims 14 to 22, or the method as described in any one of claims 23 to 30.

33. A chip system, characterized in that, The chip system includes a processing circuit and a storage medium, wherein the storage medium stores instructions; when the instructions are executed by the processing circuit, they implement the method as described in any one of claims 1 to 30.

34. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by a processor, it implements the method as described in any one of claims 1 to 30.

35. A computer program product, characterized in that, The computer program product includes a computer program that, when run on a computer, causes the computer to perform the method as described in any one of claims 1 to 30.

Images