A method, electronic device and system for authorizing with other devices

Abstract

The application provides a method, an electronic device and a system for authorizing other devices, the method comprising: device A sending first request information to device B in response to detecting that a user performs an account login or account registration operation on a first application through a second application, the first request information being used to request the second application on device B to authorize the first application; device B sending first information to the first electronic device according to the first request information, the first information being used to request information of a first account by device A, the first account being an account logged in by the second application on device B; device A requesting information of the first account from the server according to the first information; and device A receiving the information of the first account sent by the server and performing account login or account registration of the first application according to the information of the first account. The embodiments of the application help to improve the convenience of the user when performing account login or account registration.

Description

TECHNICAL FIELD

[0001] The present application relates to the terminal field, and more particularly, to a method, an electronic device and a system for authorizing by other devices. BACKGROUND

[0002] Currently, users have more and more devices, and the same application is often installed on different devices. Users need to repeatedly log in to the same application on different devices, and the cumbersome input and password memory will make the user inconvenient when using the application. SUMMARY

[0003] The present application provides a method, an electronic device and a system for authorizing by other devices, which helps to reduce the repeated operation and complex memory of the user when logging in or registering on multiple devices, and helps to improve the convenience of the user when logging in or registering an account.

[0004] In a first aspect, a system is provided, which includes a first electronic device and a second electronic device. The first electronic device is configured to display a first interface, which is an account login or registration interface of a first application. The first electronic device is further configured to, in response to detecting that a user performs an operation of logging in or registering an account of the first application through a second application, send first request information to the second electronic device, the first request information being used to request the second application on the second electronic device to authorize the first application. The second electronic device is configured to, according to the first request information, send second request information to a server corresponding to the second application, the second request information being used to request first information, the first information being used to request information of a first account by the first electronic device, the first account being an account logged in by the second application on the second electronic device. The second electronic device is further configured to receive the first information sent by the server and send the first information to the first electronic device. The first electronic device is further configured to, according to the first information, request information of the first account from the server. The first electronic device is further configured to receive the information of the first account sent by the server and perform account login or registration of the first application according to the information of the first account.

[0005] In the embodiments of the present application, when logging in or registering an account of the first application through the second application, the first electronic device can use the second electronic device on which the second application has been installed, so that the user can conveniently and quickly log in or register an account, which helps to reduce the repeated operation and complex memory of the user when logging in or registering on multiple devices, thereby helping to improve the user experience.

[0006] In some possible implementation manners, the first electronic device can save information of the second electronic device (for example, information of an application installed in the second electronic device), and when detecting that the user performs an operation of logging in or registering an account of the first application through the second application, the first electronic device can send the first request information to the second electronic device.

[0007] In some possible implementation manners, the first information is an access token.

[0008] With reference to the first aspect, in some implementation manners of the first aspect, the first electronic device further includes: before sending the first request information to the second electronic device, sending a query request, the query request being used to request an electronic device receiving the query request to determine whether the second application is installed; and receiving a first response sent by the second electronic device, the first response being used to indicate that the second electronic device installs the second application.

[0009] In the embodiments of the present application, when detecting that the user performs an operation of logging in or registering an account of the first application through the second application, the first electronic device can further query whether the second application is installed on other electronic devices. The first electronic device can send the first request information to the second electronic device that installs the second application, so that the user can conveniently and quickly log in or register an account, which helps to reduce repeated operations and complex memories of the user when logging in or registering on multiple devices, thereby helping to improve the user experience.

[0010] In some possible implementation manners, the first electronic device further includes: before sending the first request information to the second electronic device, sending a query request, the query request being used to request an electronic device receiving the query request to determine whether the second application is installed and logged in; receiving a first response sent by the second electronic device, the first response being used to indicate that the second electronic device installs and logs in the second application; and in response to receiving the response, the first electronic device sends the first request information to the second electronic device.

[0011] With reference to the first aspect, in some implementation manners of the first aspect, the first electronic device further includes: receiving a second response sent by a third electronic device, the second response being used to indicate that the third electronic device installs the second application; prompting the user to select to authorize the first application through the second application on the second electronic device or the third electronic device; and in response to an operation of the user selecting the second electronic device, sending the first request information to the second electronic device.

[0012] In the embodiments of the present application, when the first electronic device receives responses of multiple electronic devices, the first electronic device can prompt the user to select one of the devices, and the user can select a suitable device, which brings convenience to the user for account login or account registration of the first application, and helps to improve the user experience.

[0013] In some possible implementation manners, when the first electronic device receives responses of multiple electronic devices (for example, including the second electronic device and the third electronic device), the first electronic device can send the first request information to the second electronic device closest to the first electronic device.

[0014] With reference to the first aspect, in some implementation manners of the first aspect, the second electronic device is further configured to: before sending the second request information to the server, prompt the user whether to agree that the first application uses the information of the first account; and in response to an operation of the user agreeing that the first application uses the information of the first account, send the second request information to the server.

[0015] In the embodiments of the present application, the second electronic device can prompt the user whether to agree that the first application uses the information of the first account, and request the first information from the server after the user agrees, which helps to improve the security in the account login or account registration process.

[0016] With reference to the first aspect, in some implementation manners of the first aspect, the second electronic device is specifically configured to: in response to receiving the first request information, send the first request information to the server; in response to receiving the third response sent by the server for the first request information, prompt the user whether to agree that the first application uses the information of the first account; and in response to an operation of the user agreeing that the first application uses the information of the first account, send the second request information to the server.

[0017] In some possible implementation manners, the third response can be an authorization code.

[0018] With reference to the first aspect, in some implementation manners of the first aspect, the first request information includes identification information of the first application.

[0019] In the embodiments of the present application, by carrying the identification information of the first application in the first request information, the server can verify the identification information of the first application, which helps to improve the security in the account login or account registration process.

[0020] With reference to the first aspect, in some implementation manners of the first aspect, the first electronic device is a device that does not install the second application.

[0021] In a second aspect, a method for authorization by another device is provided. The method is applied in a first electronic device, and includes: displaying, by the first electronic device, a first interface, the first interface being an account login or account registration interface of a first application; in response to detecting that a user performs an operation of account login or account registration of the first application by a second application, sending, by the first electronic device, first request information to a second electronic device, the first request information being used to request the second application on the second electronic device to authorize the first application; receiving, by the first electronic device, first information of the second electronic device, the first information being used to request information of a first account by the first electronic device, the first account being an account logged in by the second application on the second electronic device, wherein the first information is obtained by the second electronic device from a server; requesting, by the first electronic device, information of the first account from the server according to the first information; and performing, by the first electronic device, account login or account registration of the first application according to the information of the first account, after receiving the information of the first account sent by the server.

[0022] In the embodiments of the present application, when the first electronic device performs account login or account registration of the first application by the second application, the second electronic device which has installed the second application can be used, so that the user can conveniently and quickly perform account login or account registration, which helps to reduce repeated operations and complex memory of the user when logging in or registering on multiple devices, thereby helping to improve the user experience.

[0023] In some possible implementation manners, the first electronic device can save information of the second electronic device (for example, information of an application installed in the second electronic device), and when detecting that the user performs an operation of account login or account registration of the first application by the second application, the first electronic device can send the first request information to the second electronic device.

[0024] In some possible implementation manners, the first information is an access token.

[0025] In combination with the second aspect, in some implementation manners of the second aspect, before the first request information is sent to the second electronic device, the method includes: sending a query request, the query request being used to request an electronic device receiving the query request to determine whether the second application is installed; and receiving a first response sent by the second electronic device, the first response being used to indicate that the second electronic device installs the second application.

[0026] In the embodiments of the present application, when the first electronic device detects that the user performs an account login or account registration operation on the first application program through the second application program, the first electronic device can further query whether the second application program is installed on other electronic devices. The first electronic device can send the first request information to the second electronic device that has installed the second application program, so that the user can conveniently and quickly perform account login or account registration, which helps to reduce the repeated operation and complex memory of the user when logging in or registering on multiple devices, thereby helping to improve the user experience.

[0027] With reference to the second aspect, in some implementations of the second aspect, before the first electronic device sends the first request information to the second electronic device, the method further includes: receiving a second response sent by a third electronic device, the second response being used to indicate that the third electronic device has installed the second application program; prompting the user to select to authorize the first application program through the second application program on the second electronic device or the third electronic device; and wherein the first electronic device sends the first request information to the second electronic device includes: in response to the operation of the user selecting the second electronic device, the first electronic device sends the first request information to the second electronic device.

[0028] In some possible implementations, the method further includes: before the first electronic device sends the first request information to the second electronic device, the first electronic device sends a query request, the query request being used to request an electronic device receiving the query request to determine whether the second application program is installed and logged in; the first electronic device receives a first response sent by the second electronic device, the first response being used to indicate that the second electronic device has installed and logged in the second application program; and in response to receiving the response, the first electronic device sends the first request information to the second electronic device.

[0029] With reference to the second aspect, in some implementations of the second aspect, the first request information includes identification information of the first application program.

[0030] In the embodiments of the present application, by carrying the identification information of the first application program in the first request information, the server can verify the identification information of the first application program, which helps to improve the security in the account login or account registration process.

[0031] With reference to the second aspect, in some implementations of the second aspect, the first electronic device is a device that does not install the second application program.

[0032] In a third aspect, a method for authorization by another device is provided. The method is applied in a second electronic device, and includes: receiving, by the second electronic device, first request information sent by a first electronic device, the first request information being used to request authorization of the first application by the second application on the second electronic device; sending, by the second electronic device, second request information to a server corresponding to the second application according to the first request information, the second request information being used to request first information, the first information being used to request information of a first account by the first electronic device, the first account being an account logged in by the second application on the second electronic device; receiving, by the second electronic device, the first information sent by the server; and sending, by the second electronic device, the first information to the first electronic device.

[0033] In the embodiments of the present application, when the first electronic device logs in or registers an account by the second application for the first application, the second electronic device on which the second application is installed can be used, so that the user can conveniently and quickly log in or register an account, and the repeated operation and complex memory of the user when logging in or registering on multiple devices can be reduced, thereby improving the user experience.

[0034] In combination with the third aspect, in some implementations of the third aspect, before the second electronic device receives the first request information sent by the first electronic device, the method further includes: receiving, by the second electronic device, a query request sent by the first electronic device, the query request being used to request the electronic device receiving the query request to determine whether the second application is installed.

[0035] The second electronic device sends a first response to the first electronic device, the first response being used to indicate that the second electronic device installs the second application.

[0036] In the embodiments of the present application, when the first electronic device detects the operation of the user logging in or registering an account by the second application for the first application, the second electronic device on which the second application is installed can be queried. The first electronic device can send the first request information to the second electronic device on which the second application is installed, so that the user can conveniently and quickly log in or register an account, and the repeated operation and complex memory of the user when logging in or registering on multiple devices can be reduced, thereby improving the user experience.

[0037] In combination with the third aspect, in some implementations of the third aspect, the method further includes: prompting the user whether to agree to use the information of the first account by the first application before the second request information is sent to the server corresponding to the second application; and in response to the operation of the user agreeing to use the information of the first account by the first application, sending the second request information to the server.

[0038] In the embodiments of the present application, the second electronic device can prompt the user whether to agree that the first application uses the information of the first account, and request the first information from the server after the user agrees, which helps to improve the security in the account login or account registration process.

[0039] With reference to the third aspect, in some implementations of the third aspect, the second electronic device sends, according to the first request information, the second request information to the server corresponding to the second application, comprising: in response to receiving the first request information, the second electronic device sends the first request information to the server; in response to receiving the third response sent by the server to the first request information, the second electronic device prompts the user whether to agree that the first application uses the information of the first account; and in response to the operation of the user agreeing that the first application uses the information of the first account, the second electronic device sends the second request information to the server.

[0040] In some possible implementations, the third response can be an authorization code.

[0041] With reference to the third aspect, in some implementations of the third aspect, the first request information includes the identification information of the first application.

[0042] In the embodiments of the present application, by carrying the identification information of the first application in the first request information, the server can verify the identification information of the first application, which helps to improve the security in the account login or account registration process.

[0043] With reference to the third aspect, in some implementations of the third aspect, the first electronic device is a device without the second application installed.

[0044] In a fourth aspect, an apparatus is provided, which includes: a display unit configured to display a first interface, the first interface being an account login or account registration interface of a first application; a detection unit configured to detect an operation of a user logging into or registering an account of the first application through a second application; a sending unit configured to, in response to the operation, send first request information to a second electronic device, the first request information being used to request the second application on the second electronic device to authorize the first application; a receiving unit configured to receive first information of the second electronic device, the first information being used for the apparatus to request information of a first account, the first account being an account logged into by the second application on the second electronic device, wherein the first information is obtained by the second electronic device from a server; the sending unit is further configured to request the information of the first account from the server according to the first information; and the receiving unit is configured to receive the information of the first account sent by the server and perform account login or account registration of the first application according to the information of the first account.

[0045] In a fifth aspect, an apparatus is provided, which includes: a receiving unit configured to receive first request information sent by a first electronic device, the first request information being used to request a second application on the apparatus to authorize a first application; a sending unit configured to, according to the first request information, send second request information to a server corresponding to the second application, the second request information being used to request first information, the first information being used for the first electronic device to request information of a first account, the first account being an account logged into by the second application on the apparatus; the receiving unit is further configured to receive the first information sent by the server; and the sending unit is further configured to send the first information to the first electronic device.

[0046] In a sixth aspect, an electronic device is provided, which includes: one or more processors; a memory; and one or more computer programs. The one or more computer programs are stored in the memory, and include instructions. When the instructions are executed by the electronic device, the electronic device performs the method in any possible implementation of the second aspect.

[0047] In a seventh aspect, an electronic device is provided, which includes: one or more processors; a memory; and one or more computer programs. The one or more computer programs are stored in the memory, and include instructions. When the instructions are executed by the electronic device, the electronic device performs the method in any possible implementation of the third aspect.

[0048] In an eighth aspect, a computer program product including instructions, which, when executed on a first electronic device, cause the electronic device to perform the method of the second aspect described above; or, when executed on a second electronic device, cause the electronic device to perform the method of the third aspect described above.

[0049] In a ninth aspect, a computer-readable storage medium includes instructions, which, when executed on a first electronic device, cause the electronic device to perform the method of the second aspect described above; or, when executed on a second electronic device, cause the electronic device to perform the method of the third aspect described above.

[0050] In a tenth aspect, a chip is provided for executing instructions, when the chip is executed, the chip performs the method of the second aspect described above; or, the chip performs the method of the third aspect described above. BRIEF DESCRIPTION OF DRAWINGS

[0051] Figure 1 is a hardware structure schematic diagram of an electronic device provided by an embodiment of the present application.

[0052] Figure 2 is a software structure block diagram provided by an embodiment of the present application.

[0053] Figure 3 is a set of graphical user interfaces provided by an embodiment of the present application.

[0054] Figure 4 is another set of graphical user interfaces provided by an embodiment of the present application.

[0055] Figure 5 is another set of graphical user interfaces provided by an embodiment of the present application.

[0056] Figure 6 is another set of graphical user interfaces provided by an embodiment of the present application.

[0057] Figure 7 is a schematic diagram of a system architecture provided by an embodiment of the present application.

[0058] Figure 8 is a schematic flow chart of a method for device A to obtain user data provided by an embodiment of the present application.

[0059] Figure 9 is a schematic flow chart of a method for authorization by other devices provided by an embodiment of the present application.

[0060] Figure 10 is another schematic flow chart of a method for authorization by other devices provided by an embodiment of the present application.

[0061] Figure 11 is another schematic flowchart of a method for authorizing by other devices provided by an embodiment of the present application.

[0062] Figure 12 is a schematic structural diagram of an apparatus provided by an embodiment of the present application.

[0063] Figure 13 is another schematic structural diagram of an apparatus provided by an embodiment of the present application.

[0064] Figure 14 is another structural schematic diagram of an electronic device provided by an embodiment of the present application. DETAILED DESCRIPTION

[0065] The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application. In the description of the embodiments of the present application, unless otherwise specified, “ / ” represents the meaning of or, for example, A / B can represent A or B; in this document, “and / or” only describes the association relationship of the associated objects, which means that there can be three relationships, for example, A and / or B, which means that there are three cases of A alone, A and B together, and B alone. In addition, in the description of the embodiments of the present application, “plural” or “multiple” means two or more than two.

[0066] Hereinafter, the terms “first” and “second” are only used for descriptive purposes, and cannot be understood as indicating or implying relative importance or implicitly indicating the number of indicated technical features. Therefore, the features defined with “first” and “second” can explicitly or implicitly include one or more features. In the description of the embodiments, unless otherwise specified, the meaning of “multiple” is two or more than two.

[0067] The method provided by the embodiments of the present application can be applied to electronic devices such as mobile phones, tablet computers, wearable devices, vehicle-mounted devices, augmented reality (AR) / virtual reality (VR) devices, notebook computers, ultra-mobile personal computers (UMPCs), netbooks, personal digital assistants (PDAs), etc. The embodiments of the present application do not make any limitation on the specific type of electronic device.

[0068] Exemplary, Figure 1A structural diagram of the electronic device 100 is shown. The electronic device 100 can include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, 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 speaker 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 (SIM) card interface 195, etc. The sensor module 180 can include a pressure sensor 180A, a gyroscope sensor 180B, a barometric 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, etc.

[0069] It can be understood that the structure shown in the embodiments of the present application does not constitute a specific limitation on the electronic device 100. In other embodiments of the present application, the electronic device 100 can include more or fewer components than shown, or combine certain components, or split certain components, or different component arrangements. The components shown can be implemented in hardware, software, or a combination of software and hardware.

[0070] 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 can be integrated in one or more processors.

[0071] The controller can be the nerve center and command center of the electronic device 100. The controller can generate operation control signals according to instruction operation codes and timing signals, and complete the control of fetching instructions and executing instructions.

[0072] The processor 110 can also have a memory that stores instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. The memory can hold instructions or data that the processor 110 has just used or is using repeatedly. If the processor 110 needs to use the instructions or data again, it can call them directly from the memory. This avoids repeated access and reduces the latency of the processor 110, thus improving the efficiency of the system.

[0073] In some embodiments, the processor 110 can include one or more interfaces. The interfaces 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.

[0074] The I2C interface is a bidirectional synchronous serial bus that includes a serial data line (SDA) and a serial clock line (SCL). In some embodiments, the processor 110 can include multiple sets of I2C buses. The processor 110 can be coupled to the touch sensor 180K, the charger, the flash, the camera 193, etc. through different I2C bus interfaces. 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 to realize the touch function of the electronic device 100.

[0075] The I2S interface can be used for audio communication. In some embodiments, the processor 110 can include multiple sets of I2S buses. The processor 110 can be coupled with the audio module 170 through the I2S buses to enable communication between the processor 110 and the audio module 170. In some embodiments, the audio module 170 can deliver audio signals to the wireless communication module 160 through the I2S interface to enable the function of answering a phone call through a Bluetooth earphone.

[0076] The PCM interface can also be used for audio communication to sample, quantize, and encode analog signals. In some embodiments, the audio module 170 can be coupled with the wireless communication module 160 through a 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 to enable the function of playing music through a Bluetooth earphone. Both the I2S interface and the PCM interface can be used for audio communication.

[0077] The UART interface is a universal serial data bus used for asynchronous communication. The bus can be a bidirectional communication bus. It converts 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 to enable Bluetooth functionality. In some embodiments, the audio module 170 can deliver audio signals to the wireless communication module 160 through the UART interface to enable the function of playing music through a Bluetooth earphone.

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

[0079] The GPIO interface can be configured through 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.

[0080] The USB interface 130 is an interface conforming to the USB standard specification, and can be a Mini USB interface, a Micro USB interface, a USB Type C interface, etc. The USB interface 130 can be used to connect a charger to charge the electronic device 100, and can also be used 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, etc.

[0081] 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 on the electronic device 100. In some other embodiments of the present application, the electronic device 100 can also use different interface connection modes or combinations of multiple interface connection modes in the above embodiments.

[0082] The charging management module 140 is used to receive charging input from a charger. The charger can be a wireless charger or a wired charger. In some wired charging embodiments, the charging management module 140 can receive charging input from a wired charger through the USB interface 130. In some wireless charging embodiments, the charging management module 140 can receive wireless charging input through the wireless charging coil of the electronic device 100. The charging management module 140 can charge the battery 142 while also supplying power to the electronic device through the power management module 141.

[0083] The power management module 141 is used to connect the battery 142, the charging management module 140, and the processor 110. The power management module 141 receives input from the battery 142 and / or the charging management module 140 to supply power to the processor 110, the internal memory 121, the external memory, the display screen 194, the camera 193, and the wireless communication module 160, etc. The power management module 141 can also be used to monitor parameters such as battery capacity, battery cycle count, battery health status (leakage, impedance), etc. In some other embodiments, the power management module 141 can also be disposed in the processor 110. In some other embodiments, the power management module 141 and the charging management module 140 can also be disposed in the same device.

[0084] The wireless communication function of the electronic device 100 can be realized through the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, the modem processor, and the baseband processor, etc.

[0085] The antenna 1 and the antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in the electronic device 100 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 antennas can be used in combination with a tuning switch.

[0086] The mobile communication module 150 can provide a solution including 2G / 3G / 4G / 5G wireless communication applied to the electronic device 100. 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 same to the modem processor to be demodulated. The mobile communication module 150 can also amplify the signal modulated by the modem processor, and radiate the same as electromagnetic waves through the antenna 1. In some embodiments, at least part of the function modules of the mobile communication module 150 can be disposed in the processor 110. In some embodiments, at least part of the function 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.

[0087] The modem processor can include a modulator and a demodulator. The modulator is used to modulate a low-frequency baseband signal to be transmitted into a medium-high frequency signal. The demodulator is used to demodulate the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then transmits the demodulated low-frequency baseband signal to the baseband processor for processing. The low-frequency baseband signal processed by the baseband processor is transmitted to the application processor. The application processor outputs the sound signal through the audio device (not limited to the speaker 170A, the microphone 170B, etc.), or displays the image or video through the display screen 194. In some embodiments, the modem processor can be an independent device. In other embodiments, the modem processor can be independent of the processor 110, and disposed in the same device as the mobile communication module 150 or other function modules.

[0088] 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 100. The wireless communication module 160 can be one or more devices that integrate at least one communication processing module. The wireless communication module 160 receives an electromagnetic wave via the antenna 2, frequency-modulates and filters the electromagnetic wave signal, and transmits the processed signal to the processor 110. The wireless communication module 160 can also receive a signal to be transmitted from the processor 110, frequency-modulate it, amplify it, and radiate it as an electromagnetic wave via the antenna 2.

[0089] In some embodiments, the antenna 1 and the mobile communication module 150 of the electronic device 100 are coupled, and the antenna 2 and the wireless communication module 160 are coupled, so that the electronic device 100 can communicate with a network and other devices through wireless communication technology. The wireless communication technology can include global system for mobile communications (GSM), general packet radio service (GPRS), code division multiple access (CDMA), wideband code division multiple access (WCDMA), time-division code division multiple access (TD-SCDMA), long term evolution (LTE), BT, GNSS, WLAN, NFC, FM, and / or IR technology, etc. The GNSS can include a global positioning system (GPS), a global navigation satellite system (GLONASS), a beidu navigation satellite system (BDS), a quasi-zenith satellite system (QZSS), and / or a satellite based augmentation systems (SBAS).

[0090] The electronic device 100 implements a display function through a GPU, a display screen 194, and an application processor, etc. The GPU is a microprocessor for image processing, which is connected to the display screen 194 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. The processor 110 can include one or more GPUs, which execute program instructions to generate or change display information.

[0091] The display screen 194 is configured to display images, videos, and the like. The display screen 194 includes a display panel. The display panel can be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED), a flex light-emitting diode (FLED), a Miniled, a MicroLed, a Micro-oLed, a quantum dot light emitting diodes (QLED), or the like. In some embodiments, the electronic device 100 can include one or N display screens 194, where N is a positive integer greater than 1.

[0092] The electronic device 100 can implement the photographing function through the ISP, the camera 193, the video codec, the GPU, the display screen 194, and the application processor.

[0093] The ISP is configured to process the data fed back by the camera 193. For example, when taking a photo, the shutter is opened, the light is transmitted to the camera photosensitive element through the lens, the light signal is converted into an electrical signal, and the camera photosensitive element transmits the electrical signal to the ISP for processing to convert it into an image visible to the naked eye. The ISP can also optimize the noise, brightness, and skin color of the image. The ISP can also optimize the exposure, color temperature, and other parameters of the shooting scene. In some embodiments, the ISP can be disposed in the camera 193.

[0094] The camera 193 is configured to capture still images or videos. An object generates an optical image through a lens and projects it onto a photosensitive element. The photosensitive element can be a charge coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The photosensitive element converts the light signal into an electrical signal, which is then transmitted to the ISP to convert it into a digital image signal. The ISP outputs the digital image signal to the DSP for processing. The DSP converts the digital image signal into an image signal in a standard RGB, YUV, or the like format. In some embodiments, the electronic device 100 can include one or N cameras 193, where N is a positive integer greater than 1.

[0095] The digital signal processor is used to process digital signals, in addition to being able to process digital image signals, it can also process other digital signals. For example, when the electronic device 100 selects a frequency point, the digital signal processor is used to perform Fourier transform on the frequency point energy, etc.

[0096] The video codec is used to compress or decompress digital video. The electronic device 100 can support one or more video codecs. In this way, the electronic device 100 can play or record videos in multiple encoding formats, such as: moving picture experts group (MPEG) 1, MPEG 2, MPEG 3, MPEG 4, etc.

[0097] The NPU is a neural-network (NN) calculation processor, which can quickly process input information by drawing on the structure of a biological neural network, such as drawing on the transmission mode between human brain neurons, and can also constantly self-learn. Through the NPU, the electronic device 100 can realize intelligent cognition applications such as image recognition, face recognition, voice recognition, text understanding, etc.

[0098] 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 100. The external memory card communicates with the processor 110 through the external memory interface 120 to realize data storage functions. For example, music, video, etc. Files are saved in the external memory card.

[0099] 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 100 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. The program storage area can store an operating system, at least one application program required by a function (such as a sound playing function, an image playing function, etc.), etc. The data storage area can store data created during the use of the electronic device 100 (such as audio data, a phone book, etc.), 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 (UFS), etc.

[0100] The electronic device 100 can realize audio functions through the audio module 170, the speaker 170A, the receiver 170B, the microphone 170C, the earphone interface 170D, and the application processor, etc. For example, music playing, recording, etc.

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

[0102] The speaker 170A, also referred to as a "loudspeaker", is configured to convert an audio electrical signal into a sound signal. The electronic device 100 can listen to music or listen to a hands-free call through the speaker 170A.

[0103] The receiver 170B, also referred to as a "earpiece", is configured to convert an audio electrical signal into a sound signal. When the electronic device 100 receives a call or a voice message, the user can listen to the voice by holding the receiver 170B close to the ear.

[0104] The microphone 170C, also referred to as a "microphone", "transducer", is configured to convert a sound signal into an electrical signal. When making a call or sending a voice message, the user can speak into the microphone 170C by holding the mouth close to the microphone 170C, and input the sound signal into the microphone 170C. The electronic device 100 can be provided with at least one microphone 170C. In other embodiments, the electronic device 100 can be provided with two microphones 170C, in addition to collecting sound signals, the noise reduction function can also be realized. In other embodiments, the electronic device 100 can also be provided with three, four or more microphones 170C, in addition to collecting sound signals, noise reduction, it can also identify the source of the sound, realize the function of directional recording, etc.

[0105] The earphone interface 170D is configured to connect a wired earphone. The earphone interface 170D can be a USB interface 130, or a 3.5mm open mobile terminal platform (OMTP) standard interface, a cellular telecommunications industry association of the USA (CTIA) standard interface.

[0106] The pressure sensor 180A is configured to sense a pressure signal and convert the pressure signal into an electrical signal. In some embodiments, the pressure sensor 180A can be disposed on the display screen 194. The pressure sensor 180A can be of various types, such as a resistive pressure sensor, an inductive pressure sensor, a capacitive pressure sensor, etc. The capacitive pressure sensor can include at least two parallel plates of conductive material. When a force is applied to the pressure sensor 180A, the capacitance between the electrodes changes. The electronic device 100 determines the intensity of the pressure according to the change in capacitance. When a touch operation is applied to the display screen 194, the electronic device 100 detects the intensity of the touch operation according to the pressure sensor 180A. The electronic device 100 can also calculate the position of the touch according to the detection signal of the pressure sensor 180A. In some embodiments, touch operations applied to the same touch position but with different touch operation intensities can correspond to different operation instructions. For example, when a touch operation with a touch operation intensity less than a first pressure threshold is applied to a short message application icon, an instruction to view short messages is executed. When a touch operation with a touch operation intensity greater than or equal to the first pressure threshold is applied to the short message application icon, an instruction to create a new short message is executed.

[0107] The gyroscope sensor 180B can be configured to determine the motion attitude of the electronic device 100. In some embodiments, the angular velocity of the electronic device 100 around three axes (i.e., x, y, and z axes) can be determined by the gyroscope sensor 180B. The gyroscope sensor 180B can be used for anti-shake photography. For example, when the shutter is pressed, the gyroscope sensor 180B detects the angle of shaking of the electronic device 100, calculates the distance that the lens module needs to compensate according to the angle, and lets the lens offset the shaking of the electronic device 100 by reverse movement to achieve anti-shake. The gyroscope sensor 180B can also be used for navigation and motion sensing game scenarios.

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

[0109] The magnetic sensor 180D includes a Hall sensor. The electronic device 100 can detect the opening and closing of a flip cover by using the magnetic sensor 180D. In some embodiments, when the electronic device 100 is a flip phone, the electronic device 100 can detect the opening and closing of the flip cover according to the magnetic sensor 180D. Further, according to the detected opening and closing state of the cover or the flip cover, the electronic device 100 can set a feature such as automatic unlocking of the flip cover.

[0110] The acceleration sensor 180E can detect the magnitude of acceleration of the electronic device 100 in various directions (generally three axes). When the electronic device 100 is stationary, the acceleration sensor 180E can detect the magnitude and direction of gravity. The acceleration sensor 180E can also be used to identify the attitude of the electronic device, and can be applied to landscape / portrait screen switching and pedometer applications.

[0111] Distance sensor 180F is configured to measure distance. Electronic device 100 can measure distance by infrared or laser. In some embodiments, electronic device 100 can utilize distance sensor 180F to measure distance for fast focusing when taking a picture.

[0112] 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. Electronic device 100 emits infrared light outwardly through the light emitting diode. Electronic device 100 detects infrared reflected light from nearby objects using the photodiode. When sufficient reflected light is detected, electronic device 100 can determine that there is an object near electronic device 100. When insufficient reflected light is detected, electronic device 100 can determine that there is no object near electronic device 100. Electronic device 100 can utilize proximity light sensor 180G to detect that a user is holding electronic device 100 close to the ear for a phone call, so as to automatically turn off the screen to save power. Proximity light sensor 180G can also be used for automatic unlocking and locking of the screen in a holster mode or a pocket mode.

[0113] Ambient light sensor 180L is configured to sense ambient light brightness. Electronic device 100 can adaptively adjust the brightness of display screen 194 according to the sensed ambient light brightness. Ambient light sensor 180L can also be used to automatically adjust white balance when taking a picture. Ambient light sensor 180L can also cooperate with proximity light sensor 180G to detect whether electronic device 100 is in a pocket to prevent accidental touch.

[0114] Fingerprint sensor 180H is configured to collect a fingerprint. Electronic device 100 can utilize the collected fingerprint characteristics to implement fingerprint unlocking, access application lock, fingerprint picture taking, fingerprint call answering, and the like.

[0115] Temperature sensor 180J is configured to detect temperature. In some embodiments, electronic device 100 utilizes the temperature detected by temperature sensor 180J to implement temperature handling strategies. For example, when the temperature reported by temperature sensor 180J exceeds a threshold, electronic device 100 implements performance reduction of a processor located near temperature sensor 180J to reduce power consumption and implement thermal protection. In other embodiments, when the temperature is lower than another threshold, electronic device 100 heats battery 142 to avoid abnormal shutdown of electronic device 100 caused by low temperature. In other embodiments, when the temperature is lower than yet another threshold, electronic device 100 implements voltage boosting of the output voltage of battery 142 to avoid abnormal shutdown caused by low temperature.

[0116] Touch sensor 180K, also referred to as "touch panel". Touch sensor 180K can be disposed on display screen 194, and touch sensor 180K and display screen 194 together form a touch screen, also referred to as "touch panel". Touch sensor 180K is configured to detect touch operations applied to or near the touch sensor 180K. The touch sensor 180K can transmit the detected touch operation to the application processor to determine the touch event type. Visual output related to the touch operation can be provided through display screen 194. In other embodiments, touch sensor 180K can also be disposed on the surface of electronic device 100, which is different from the position of display screen 194.

[0117] Bone conduction sensor 180M can obtain vibration signals. In some embodiments, bone conduction sensor 180M can obtain vibration signals of the human body's vocal vibration bone block. Bone conduction sensor 180M can also contact the human body pulse to receive blood pressure pulsation signals. In some embodiments, bone conduction sensor 180M can also be disposed in a headset to form a bone conduction headset. Audio module 170 can analyze voice signals based on the vibration signals of the vocal vibration bone block obtained by the bone conduction sensor 180M to realize voice functions. The application processor can analyze heart rate information based on the blood pressure pulsation signals obtained by the bone conduction sensor 180M to realize heart rate detection functions.

[0118] Keys 190 include power on / off keys, volume keys, and the like. Keys 190 can be mechanical keys. They can also be touch keys. Electronic device 100 can receive key input and generate key signal input related to user settings and function control of electronic device 100.

[0119] Motor 191 can generate vibration prompts. Motor 191 can be used for incoming call vibration prompts and also for touch vibration feedback. For example, touch operations applied to different applications (such as taking pictures, playing audio, etc.) can correspond to different vibration feedback effects. Touch operations applied to different regions of display screen 194 can also correspond to different vibration feedback effects. Different application scenarios (such as time reminders, received messages, alarms, games, etc.) can also correspond to different vibration feedback effects. Touch vibration feedback effects can also be customizable.

[0120] Indicator 192 can be an indicator light, which can be used to indicate charging status, power changes, and also to indicate messages, missed calls, notifications, and the like.

[0121] The SIM card interface 195 is used to connect a SIM card. The SIM card can be inserted into or removed from the SIM card interface 195 to make contact with and separate from the electronic device 100. The electronic device 100 can support one or N SIM card interfaces, where N is a positive integer greater than 1. The SIM card interface 195 can support Nano SIM cards, Micro SIM cards, SIM cards, etc. Multiple cards can be inserted into the same SIM card interface 195 simultaneously. The multiple cards can be of the same or different types. The SIM card interface 195 is also compatible with different types of SIM cards. The SIM card interface 195 is also compatible with external memory cards. The electronic device 100 interacts with the network through the SIM card to realize functions such as calls and data communication. In some embodiments, the electronic device 100 uses an embedded SIM (eSIM) card. The eSIM card can be embedded in the electronic device 100 and cannot be separated from the electronic device 100.

[0122] It should be understood that the phone cards in the embodiments of this application include, but are not limited to, SIM cards, eSIM cards, universal subscriber identity modules (USIM), universal integrated circuit cards (UICC), etc.

[0123] The software system of electronic device 100 can adopt a layered architecture, event-driven architecture, microkernel architecture, microservice architecture, or cloud architecture. This application embodiment uses the layered architecture Android system as an example to exemplify the software structure of electronic device 100.

[0124] Figure 2 This is a software structure block diagram of an electronic device 100 according to an embodiment of this application. The layered architecture divides the software into several layers, each with a clear role and function. Layers communicate with each other through software interfaces. In some embodiments, the Android system is divided into four layers, from top to bottom: the application layer, the application framework layer, the Android runtime and system libraries, and the kernel layer. The application layer may include a series of application packages.

[0125] like Figure 2 As shown, the application package may include applications such as camera, gallery, calendar, call, map, navigation, WLAN, Bluetooth, music, video, and SMS.

[0126] The application framework layer provides an application programming interface (API) and programming framework for applications of the application layer. The application framework layer includes some pre-defined functions.

[0127] As shown in Figure 2 the application framework layer can include a window manager, a content provider, a view system, a phone manager, a resource manager, a notification manager, etc.

[0128] The window manager is used to manage window programs. The window manager can acquire the size of the display screen, determine whether there is a status bar, lock the screen, and intercept the screen, etc.

[0129] The content provider is used to store and acquire data, and make the data accessible to the application program. The data can include video, image, audio, dialed and received phone, browsing history and bookmark, phone book, etc.

[0130] The view system includes visual controls, such as a control for displaying text, a control for displaying pictures, etc. The view system can be used to build an application program. A display interface can be composed of one or more views. For example, a display interface including a short message notification icon can include a view for displaying text and a view for displaying pictures.

[0131] The phone manager is used to provide the communication function of the electronic device 100. For example, the management of the call state (including connection, hang-up, etc.).

[0132] The resource manager provides various resources for the application program, such as localized strings, icons, pictures, layout files, video files, etc.

[0133] The notification manager enables the application program to display notification information in the status bar, which can be used to convey a type of message that can automatically disappear after a short stay without user interaction. For example, the notification manager is used to inform the completion of downloading, message reminders, etc. The notification manager can also be a notification in the form of a chart or a scroll bar text appearing in the top status bar of the system, such as a notification of an application program running in the background, and can also be a notification in the form of a dialogue window appearing on the screen. For example, prompting text information in the status bar, issuing a prompt sound, the electronic device vibrating, the indicator light flashing, etc.

[0134] The Android runtime includes a core library and a virtual machine. The Android runtime is responsible for the scheduling and management of the Android system.

[0135] The core library includes two parts: one part is the function function required to be called by the java language, and the other part is the core library of Android.

[0136] The application program layer and the application framework layer run in a virtual machine. The virtual machine executes the java files of the application program layer and the application framework layer into binary files. The virtual machine is used to perform functions such as management of object life cycle, stack management, thread management, management of security and exceptions, and garbage collection.

[0137] The system library can include a plurality of functional modules. For example, a surface manager, media libraries, a three-dimensional graphics processing library (for example, OpenGL ES), a 2D graphics engine (for example, SGL), and the like.

[0138] The surface manager is used to manage a display subsystem and provides fusion of 2D and 3D layers for a plurality of application programs.

[0139] The media libraries support playback and recording of a plurality of commonly used audio, video formats, and static image files. The media libraries can support a plurality of audio and video encoding formats, for example, MPEG4, H.264, MP3, AAC, AMR, JPG, PNG, and the like.

[0140] The three-dimensional graphics processing library is used to implement three-dimensional graphics drawing, image rendering, synthesis, and layer processing, and the like.

[0141] The 2D graphics engine is a drawing engine for 2D drawing.

[0142] The kernel layer is a layer between hardware and software. The kernel layer at least includes a display driver, a camera driver, an audio driver, and a sensor driver.

[0143] It should be understood that the technical solutions in the embodiments of the present application can be used in Android, IOS, Harmony, and the like.

[0144] Figure 3 is a set of graphical user interfaces (GUIs) provided by the embodiments of the present application.

[0145] Referring to (a) in Figure 3 The notebook computer displays a display interface of an App1 website, where the display interface is a webpage login interface of the App1. The mobile phone displays a desktop of the mobile phone, where the desktop of the mobile phone includes an icon of an App2.

[0146] Referring to (b) in Figure 3As shown in (b) of FIG. 3, the notebook computer detects an operation of the user logging in through the third-party account (the account of App2). In response to detecting the operation of the user logging in through the account of App2, the notebook computer can send a query request to the surrounding devices, the query request being used to query the devices surrounding the notebook computer that have App2 installed. If the mobile phone receives the query request and the mobile phone has App2 installed, the mobile phone can send a response (ACK) to the notebook computer. In response to receiving the response sent by the mobile phone, the notebook computer can send an authorization request to the mobile phone, the authorization request being used to request App2 on the mobile phone to authorize App1 to log in. In response to receiving the authorization request, the mobile phone can display a prompt box 302, wherein the prompt box 302 includes prompt information “Notebook computer requests App2 authorization”.

[0147] In an embodiment, in response to detecting the operation of the user logging in through the account of App2, the notebook computer can send the query request to the devices under the same account (for example, the devices under the same account include the mobile phone) or the mobile phone under the same family group (for example, the family group includes account 1 and account 2, the devices under account 1 include the notebook computer, and the devices under account 2 include the mobile phone).

[0148] It should be understood that in the embodiments of the present application, the user can invite the account (for example, Huawei ID2) of the other family member through the account (for example, Huawei ID1) logged in on a certain device, so that the account of the user and the account of the other family member form a family group. After forming the family group, the account of the user and the account of the other family member can share information, for example, the account of the user can obtain the device name, device type, address, and the like of the account of the other family member; for another example, if the user purchases a membership of an application, the other family member can obtain the membership of the user; for another example, the members under the same family group can share the storage space of the cloud server.

[0149] In an embodiment, after receiving the authorization request, the mobile phone can determine whether the notebook computer is a trusted device. For example, if the mobile phone determines that the mobile phone and the notebook computer are devices under the same account, the mobile phone can determine that the notebook computer is a trusted device; or, if the mobile phone determines that the mobile phone and the notebook computer are devices under the same family group, the mobile phone can determine that the notebook computer is a trusted device; or, if the mobile phone determines that the user sets the notebook computer as a trusted device on the mobile phone, the mobile phone can determine that the notebook computer is a trusted device. After the mobile phone determines that the notebook computer is a trusted device, the mobile phone can display the prompt box 302. If the mobile phone determines that the notebook computer is a non-trusted device, the mobile phone can prompt the user that the notebook computer is a non-trusted device in the display prompt box 302.

[0150] See Figure 3 As shown in (c), when the phone detects that the user clicks on control 303, the phone can launch App2 and display the authorization login information of App1 on the display interface of App2. Figure 3 In (c), the display interface of App2 includes the message "App1 requests to use your account information". The mobile phone detects the user's click on control 304 and can request information for authorization login (e.g., an access token) from App2's server. In response to receiving the authorization login information from App2's server, the mobile phone can send the authorization login information to the laptop.

[0151] In one embodiment, the mobile phone may also prompt the user on the App2 display interface to authorize the use of the account information requested by App1. For example, the user can choose to allow App1 to use the nickname and profile picture information of the App2 account, while choosing not to allow App1 to use the region and gender information of the App2 account.

[0152] See Figure 3 As shown in (d), in response to receiving the authorization login information from the mobile phone, the laptop can use this information to request App2's account information from App2's server. Upon receiving the corresponding account information from App2's server, the laptop can use this account information to log in to the App1 website. After logging in, the laptop can display the App1 interface, where the App1 login account information is displayed in the upper right corner. The avatar of the App1 login account is the same as the App2 account avatar. The mobile phone can display the App2 chat history, where the most recent chat message is a login notification: "Your App2 account has logged into the website."

[0153] In this embodiment, the laptop computer can conveniently and quickly log in to the application using a mobile phone with the third-party application App2 installed. This simplifies the application login authorization process, avoids tedious input or manual memorization by the user, improves the efficiency of user application login, and also ensures the security of application login.

[0154] Figure 4 This is another set of GUIs provided in the embodiments of this application.

[0155] See Figure 4As shown in (a), the mobile phone displays the lock screen. The laptop displays the website of App1, which is the login page for App1. The laptop detects that the user has logged in using a third-party account (App2's account). In response to detecting the user's login using App2's account, the laptop can send a query request to nearby devices to find those with App2 installed. If the mobile phone and tablet receive the query request and both have App2 installed, they can send an ACK response to the laptop.

[0156] See Figure 4 As shown in (b), in response to receiving responses from the mobile phone and tablet, the laptop can display a prompt box 402, which includes the message "Multiple devices with App2 installed have been detected nearby. Please select one." In response to detecting that the user selects the mobile phone and clicks control 403, the laptop sends an authorization request to the mobile phone, which requests App2 on the mobile phone to authorize login to App1. In response to receiving the authorization request, the mobile phone can display a prompt box 405, which includes the message "The laptop requests authorization from App2."

[0157] In one embodiment, in response to detecting a user's login operation using the App2 account, the laptop can send the query request to devices under the same account (e.g., mobile phones and tablets). If both the mobile phone and tablet have App2 installed, they can send a response (ACK) to the laptop.

[0158] Alternatively, the laptop can send the query request to other devices within the same home group (e.g., the home group includes Account 1 and Account 2, where Account 1 includes laptops and mobile phones, and Account 2 includes tablets). If both the mobile phone and tablet have App 2 installed, they can send an ACK response to the laptop.

[0159] See Figure 4 As shown in (c), when the phone detects that the user clicks on control 407, the phone can launch App2 and display the authorization login information of App1 on the display interface of App2. Figure 4(c) of FIG. 6B, the display interface of App2 includes a prompt information "App1 applies to use your account information". In response to detecting the operation of the user clicking the control 407, the phone can request information (e.g., an access token) for authorizing login from the server of App2. In response to receiving the information for authorizing login from the server of App2, the phone can send the information for authorizing login to the notebook computer.

[0160] Referring to Figure 4 (d) of FIG. 6B, in response to receiving the information for authorizing login from the phone, the notebook computer can use the information for authorizing login to request the account information of App2 from the server of App2. In response to requesting the corresponding user information from the server of App2, the notebook computer can use the account information to implement login of the website of App1. After implementing login, the notebook computer can display the display interface of App1, wherein the account information of the login of App1 can be displayed in the upper right corner of the display interface, and the avatar of the account of the login of App1 is the same as the avatar of the account of App2. The phone can display the chat record display interface of App2, wherein the last chat record is the login operation notification "your App2 account has performed website login operation".

[0161] In the embodiments of the present application, the notebook computer can use the device around which the third-party application App2 is installed to conveniently and quickly log in to the application. When there are multiple devices that can be used around, the notebook computer can prompt the user to select a suitable device for login. The embodiments of the present application simplify the interactive steps of application login authorization, avoid the cumbersome input or active memory process of the user, improve the efficiency of the user logging in to the application, and also ensure the security when logging in to the application.

[0162] Figure 5 is another set of GUIs provided by the embodiments of the present application.

[0163] Referring to Figure 5 (a) of FIG. 6A, the phone displays a lock screen interface. The notebook computer displays the display interface of the website of App1, wherein the display interface is the webpage login interface 501 of App1. The notebook computer detects the operation of the user clicking the control 502 for logging in using other devices.

[0164] Referring to Figure 5 (b) of FIG. 6A, in response to detecting the operation of the user clicking the control 502, the notebook computer can send a query request to the surrounding devices, and the query request is used to query the devices around which App1 is installed. If the phone receives the query request and the phone installs App1, the phone can send a response (ACK) to the notebook computer.

[0165] Referring toFigure 5 As shown in (b), in response to receiving a response from the mobile phone, the laptop can send an authorization request to the mobile phone. This authorization request is used to request App1 on the mobile phone to authorize login to App1 on the laptop. In response to receiving the authorization request, the mobile phone can display a prompt box 503, which includes the message "Laptop requests authorization from App1".

[0166] In one embodiment, in response to receiving a response from the mobile phone, the laptop may also prompt the user with "App1 is detected installed on the mobile phone. Do you want to authorize it using the mobile phone?" When the laptop detects that the user has confirmed the authorization operation using the mobile phone, the laptop may send an authorization request to the mobile phone.

[0167] In one embodiment, the laptop receives responses from the mobile phone and tablet, and can prompt the user, "App1 has been detected installed on the mobile phone and tablet. Please confirm which device to use for authorization." When the laptop detects that the user has confirmed using the mobile phone for authorization, the laptop can send an authorization request to the mobile phone.

[0168] In one embodiment, after receiving the authorization request, the mobile phone can determine whether the laptop is a trusted device. For example, if the mobile phone determines that the mobile phone and the laptop are devices under the same account, then the mobile phone can determine that the laptop is a trusted device; or, if the mobile phone determines that the mobile phone and the laptop are devices under the same family group, then the mobile phone can determine that the laptop is a trusted device; or, if the mobile phone determines that the user has set the laptop as a trusted device on the mobile phone, then the mobile phone can determine that the laptop is a trusted device. After the mobile phone determines that the laptop is a trusted device, the mobile phone can display a prompt box 503. If the mobile phone determines that the laptop is an untrusted device, then the mobile phone can notify the user that the laptop is an untrusted device in the prompt box 503.

[0169] See Figure 5 As shown in (c), in response to the phone detecting a user click on control 504, the phone can display an authorization login interface for App1, which includes information prompting the user to confirm login. Upon detecting a user click on control 505, the phone can request authorization login information (e.g., an access token) from App1's server. In response to receiving the authorization login information from App1's server, the phone can send the authorization login information to the laptop. See also... Figure 5As shown in (d), in response to receiving the authorization login information from the mobile phone, the laptop can use this information to request the account information for logging into App1 on the mobile phone from App1's server. Upon receiving the account information from App1's server, the laptop can use this account information to log into the App1 website. After logging in, the laptop can display the App1 interface, where the avatar information of the App1 account logged in on the mobile phone can be displayed in the upper right corner. This allows the same account to be logged in on both the mobile phone and the laptop.

[0170] In this embodiment, the laptop computer can conveniently and quickly log in to the application using a mobile phone with the third-party application App1 installed. This simplifies the application login authorization process, avoids tedious input or manual memorization by the user, improves the efficiency of user login, and also ensures the security of application login.

[0171] Figure 6 This is another set of GUIs provided in the embodiments of this application.

[0172] See Figure 6 As shown in (a), the laptop displays the interface of the App1 website, which is the App1 web registration interface 601. The mobile phone displays the phone's desktop, which includes an icon for App2.

[0173] See Figure 6 As shown in (b), the laptop detects a user's registration and login operation using a third-party account (App2's account). In response to detecting this operation, the laptop can send a query request to nearby devices that have App2 installed. If the mobile phone receives this query request and App2 is installed on the phone, it can send an ACK response to the laptop. Upon receiving the ACK from the mobile phone, the laptop can send an authorization request to the mobile phone, requesting App2 on the phone to authorize login to App1. Upon receiving this authorization request, the mobile phone can display a prompt box 602, which includes the message "Laptop requests authorization from App2".

[0174] See Figure 6 As shown in (c), when the phone detects that the user clicks on control 603, the phone can launch App2 and display the authorization login information of App1 on the display interface of App2. Figure 6In (c), the display interface of App2 includes the message "App1 requests to use your account information". The mobile phone detects the user's click on control 604 and can request information for authorization login (e.g., an access token) from App2's server. In response to receiving the authorization login information from App2's server, the mobile phone can send the authorization login information to the laptop.

[0175] See Figure 6 As shown in (d), in response to receiving the authorization login information from the mobile phone, the laptop can use this information to request App2's account information from App2's server. Upon receiving the account information from App2's server, the laptop can use this information to log in to the App1 website. After logging in, the laptop can display the App1 interface, where the App1 login account information is displayed in the upper right corner. The avatar of the App1 login account is the same as the App2 account avatar. The mobile phone can display the App2 chat history, where the most recent chat message is a login notification: "Your App2 account has logged into the website."

[0176] In this embodiment, a laptop computer can conveniently and quickly register an account for App1 using a mobile phone with a third-party application App2 installed. This simplifies the interactive steps during application registration, avoids tedious input processes for users, and improves the efficiency of account registration.

[0177] The above combination Figures 3 to 6 Several GUIs in the embodiments of this application have been introduced. The internal implementation process of the embodiments of this application will be described below with reference to the accompanying drawings.

[0178] Figure 7 A schematic diagram of a system architecture provided in an embodiment of this application is shown. This system architecture includes device A (e.g., a laptop computer) and device B (e.g., a mobile phone). Device A includes an App1 to be logged into or registered, an application launcher 710, and a data synchronization module 720. The application launcher 710 handles application launch requests and provides application information responsive to specific services (e.g., ...). Figure 3 As shown in (a) of the diagram (App2, App3, and App4), the data synchronization module 720 is used to handle request forwarding and data synchronization between device A and other devices. Device B includes App2, notification module 730, and data synchronization module 740. App2 is an application that supports authorized login to other applications (e.g., OAuth authorization login), and notification module 730 is used to notify or prompt the user with specific information or operations.

[0179] When the device A detects that the user logs in or registers the account of the App1 on the device A, the device A selects the App2 with the third-party authorization login to log in or register. The application launcher 710 of the device A queries whether the App2 is installed on the device A. Meanwhile, the application launcher 710 can send a query request to the data synchronization module 720, where the query request is used to query whether the App2 is installed on the surrounding devices. The data synchronization module 720 can send a first message, where the first message can include the query request.

[0180] For example, the first message can be a broadcast message, which can be a Bluetooth low energy (BLE) data packet, where the BLE data packet can carry the query request. The BLE data packet includes a protocol data unit (PDU), where the query request can be carried in a service data field in the PDU, or can be carried in a manufacturer specific data field in the PDU. For example, the payload of the service data field can include a plurality of bit positions, where the plurality of bit positions include extensible bit positions. The device A and the surrounding devices (including the device B) can agree on the content of a certain extensible bit position. When the certain extensible bit position is 1, the device B can obtain that the device A queries whether the device B installs the App2.

[0181] The broadcast message can also carry the media access control (MAC) address of the device A. For example, if the broadcast message is a BLE data packet, the MAC address of the device A can be carried in an access address field in the BLE data packet.

[0182] For example, the first message can be a broadcast message, which can be a user datagram protocol (UDP) data packet, where the UDP data packet can carry the query request. The UDP data packet includes a data part of an IP datagram. The data part of the IP datagram can include extensible bit positions. The device A and the surrounding devices (including the device B) can agree on the content of a certain extensible bit position. When the certain extensible bit position is 1, the device B can obtain that the device A queries whether the device B installs the App2.

[0183] The UDP data packet can carry the IP address and port number of device A (including the source port number and the destination port number, wherein the source port number refers to the port number used by device A when sending data, and the destination port number refers to the port used by device A when receiving data), and the IP address and port number of device A can be carried in the UDP header of the data part of the IP datagram.

[0184] In one embodiment, the data synchronization module 720 can send the query request to devices under the same account (including device B), or the data synchronization module 720 can send the query request to devices under the same family group (including device B). For example, the data synchronization module 720 can send the query request to the data synchronization module 740 of device B in a BLE data packet or a UDP data packet. The process of sending through the BLE data packet or the UDP data packet can refer to the description of the above embodiments, and for the sake of brevity, it will not be repeated here.

[0185] For example, device A and device B are devices under the same account, and device A can save the device type, device name, MAC address and other information of device B. When device A detects that the user performs authorized login or registration of App1 through App2, device A can send a BLE data packet to device B according to the MAC address of device B. The BLE data packet can include a PDU, and the query request can be carried in the service data field in the PDU, or can also be carried in the vendor-specific data field in the PDU. For example, the load of the service data field can include a plurality of bit positions, wherein the plurality of bit positions include extensible bit positions. Device A and device B can agree on the content of a certain extensible bit position. When a certain extensible bit position is 1, device B can obtain whether device A queries whether device B installs App2.

[0186] In one embodiment, if device A and device B are devices under the same account, device A can also save the information of the applications installed in device B. For example, device B can send a BLE packet to device A, and the BLE packet can carry the package name information of all the applications installed in device B. The package name information of all the applications installed in device B can be carried in the service data field in the PDU, or can also be carried in the vendor specific data field in the PDU. For example, the load of the service data field can include a plurality of bits, and the plurality of bits include extensible bits. Device B can encode the package name information of all the applications by using GBK, ISO8859-1 or Unicode (for example, UTF-8, UTF-16) and carry the encoded information on one or more extensible bits. After receiving the BLE packet sent by device B, device A can decode the information on the corresponding bits to obtain the information of the applications installed in device B.

[0187] In one embodiment, after receiving the first message sent by the data synchronization module 720 of device A, the data synchronization module 740 of device B can first establish a connection with device A. For example, if the BLE packet sent by device A to device B carries the MAC address of device A, device B can establish a Bluetooth connection with device A after obtaining the MAC address of device A. For example, if the UDP packet carries the IP address of device A and the destination port number, device B can establish a transmission control protocol (TCP) connection with device A through the IP address and the destination port number.

[0188] The data synchronization module 740 of device B sends a response to the query request to the data synchronization module 720 of device A.

[0189] For example, the response can be carried in a BLE packet, and the BLE packet includes a protocol data unit. The response can be carried in the service data field in the PDU, or can also be carried in the vendor specific data field in the PDU. For example, the load of the service data field can include a plurality of bits, and the plurality of bits include extensible bits. Device A and device B can agree on the content of a certain extensible bit. When a certain extensible bit is 1, device A can know that device B has installed App2.

[0190] For example, device B can send the response to device A through the TCP connection between device A and device B.

[0191] The data synchronization module 720 of the device A can forward the response to the application launcher 710 after receiving the response sent by the data synchronization module 740 of the device B. The application launcher 710 can determine the installation information of the App2 on the device A and the installation information of the App2 on the surrounding devices (or the devices under the same account, the devices under the same family group).

[0192] In one embodiment, if the App2 is not installed on the device A, and the device A only receives the response sent by the device B, the device A can not prompt the user with the installation information of the App2 on the device A and the installation information of the App2 on the surrounding devices (or the devices under the same account, the devices under the same family group), but directly send an authorization request to the device B.

[0193] In one embodiment, if the App2 is not installed on the device A, and the device A receives the responses sent by at least two devices (for example, the device B and the device C), the device A can prompt the user that the App2 is installed on the device B and the device C and prompt the user to select one of the devices for authorization login. For example, as shown in (b) of FIG. 7, the notebook computer can prompt the user that the App2 is installed on the mobile phone and the tablet computer. Figure 4

[0194] In one embodiment, if the App2 is installed on the device A, and the device A receives the response sent by at least one device, the device A can prompt the user that the App2 is installed on the device A and the device B and prompt the user to select one of the devices for authorization login.

[0195] In one embodiment, if the App2 is installed on the device A, and the device A does not receive the response sent by other devices, the device A can open the App2 for authorization login.

[0196] When the device A detects the operation of the user selecting the App2 on the device B for authorization login, the application launcher 710 of the device A can send an authorization request to the data synchronization module 720, and the authorization request is used to request the App2 on the device B for authorization login of the App1.

[0197] It should be understood that the process of the device A sending the authorization request to the device B can refer to the process of the device A sending the query request to the device B, which is not described herein for brevity.

[0198] The data synchronization module 740 of the device B can send the authorization request to the notification module 730 after receiving the authorization request. The notification module 730 can prompt the user to authorize in the App2 according to the authorization request. For example, as shown in (b) of FIG. 7, the notebook computer can prompt the user to authorize in the App2. Figure 3 ​As shown in (b) of FIG. 3, after receiving the authorization request sent by the notebook computer, the mobile phone can display a prompt box 302, which includes prompt information "Notebook computer requests App2 authorization". When detecting the authorization operation of the user, the device B can start App2 and prompt the user that App1 applies to use the account information of App2. When detecting the operation of the user agreeing to use the account information of App2 by App1, the device B can request the server of App2 for information (for example, access token) for authorization login. The server of App2 can send the information for authorization login to the device B.

[0199] In one embodiment, when detecting the operation of the user agreeing to use the account information of App2 by App1, the device B can send a hyper text transfer protocol (HTTP) request to the server of App2 according to the uniform resource locator (URL) address of App2, and the HTTP request can carry request information for requesting the information for authorization login. In response to receiving the HTTP request, the server of App2 sends an HTTP response to the device B, and the HTTP response can carry the information for authorization login.

[0200] It should be understood that when the user installs App2 on the device B, the device B can obtain the URL address of App2 from the server of App2. When the device B detects the operation of the user agreeing to use the account information of App2 by App1, the device B can send the HTTP request to the server of App2.

[0201] The device B can send the information for authorization login to the device A, so that the device A uses the information for authorization login to request the account information of App2 from the server of App2, thereby realizing the login or registration of App1 on the device A.

[0202] In one embodiment, the information for authorization login can be an access token, and the access token can be composed of a string.

[0203] For example, the device B can send a BLE data packet to the device A, and the access token can be included in the BLE data packet. The access token can be carried in a service data field or a vendor specific data field in a PDU. For example, the service data field can include a plurality of bits, and the plurality of bits can include extensible bits. The device B can encode the access token by using GBK, ISO8859-1, Unicode (e.g., UTF-8, UTF-16), or the like, and carry the encoded information in one or more extensible bits. The device A can decode the information in the corresponding bits after receiving the BLE data packet sent by the device B, and thus obtain the access token.

[0204] For example, the device B can also send the access token to the device A through a TCP connection.

[0205] It should be understood that in the embodiments of the present application, the signaling between the device B and the App2 server can be transmitted through a network transmission channel, and the signaling between the device A and the App2 server can also be transmitted through a network transmission channel.

[0206] It should also be understood that when the user installs the App1 on the device A (or opens the login or registration interface of the App1 through a webpage), the device A can obtain the URL address of the App2 server from the server of the App1. Thus, when the device A receives the access token, the device A can send an HTTP request to the App2 server according to the URL address of the App2 server, and the HTTP request can carry the access token. In response to receiving the HTTP request from the device A, the App2 server can determine that the access token is sent by the App2 server to the device B, and thus the App2 server can send an HTTP response to the device A, and the HTTP response can include the account information of the App2 logged in on the device B.

[0207] It should also be understood that if the App1 supports authorization login or registration through a third-party (e.g., App2) account, the developer of the App1 can write the URL address of the App2 server into the installation package of the App1 and upload it to the server of the App1. Thus, when the user installs the App1 on the device A, the device A can obtain the installation package of the App1 from the server of the App1, and thus obtain the URL address of the App2 server.

[0208] The following will be described in detail with reference to the accompanying drawings. Figure 8 A method 800 for obtaining user data by the device A is introduced. Referring to FIG. 8, the method 800 includes the following steps. Figure 8

[0209] ​S801, App1 of device A sends an authorization request to the data synchronization module 720 of device A.

[0210] For example, device A can carry the authorization request in a BLE data packet; or device A can carry the authorization request in a UDP data packet.

[0211] S802, the data synchronization module 720 of device A forwards the authorization request to the data synchronization module 740 of device B.

[0212] It should be understood that the process of forwarding the authorization request from the data synchronization module 720 of device A to the data synchronization module 740 of device B can refer to the process of sending the query request from the data synchronization module 720 of device A to the data synchronization module 740 of device B, which will not be described here for brevity.

[0213] In one embodiment, the authorization request includes the identification information of App1.

[0214] For example, the identification information of App1 can be the unique ID (e.g., client_id) of App1.

[0215] In the embodiments of the present application, if App1 supports authorization login through a third-party application (e.g., App2), when the user installs App1 on device A, device A can obtain the identification information of App1 from the server of App1.

[0216] It should be understood that if App1 supports authorization login through a third-party application (e.g., App2), the developer of App1 can obtain the identification information of App1 from the developer of App2 and upload the identification information of App1 into the installation package of App1 to the server of App1. When the user installs App1 on device A, device A can obtain the identification information of App1 from the server of App1. The developer of App2 can upload the identification information of App1 to the server of App2. When the server of App2 obtains the authorization request, it can verify the identification information in the authorization request through the identification information uploaded by the developer of App2.

[0217] In an embodiment, the identification information of the App1 can be obtained by the device A from a server of the App1 when the device A installs the App1, or can be obtained in real time. For example, the device A can request the identification information of the App1 from the server of the App1 in response to the user detecting a user operation of clicking to log in or register an account of the App1 through the App2 on a login or registration interface of the App1. By carrying the identification information of the App1 in the authorization request, the App2 server can verify the authorization request, so that the device B can send information (for example, an access token) for authorizing the login to the device A.

[0218] S803, the data synchronization module 740 of the device B sends the authorization request to the App2 of the device B.

[0219] S804, the App2 of the device B sends the authorization request to the authorization server of the App2.

[0220] It should be understood that after receiving the authorization request sent by the data synchronization module 740, the App2 of the device B can send the HTTP request to the authorization server of the App2 according to the URL address of the authorization server of the App2, and the HTTP request can carry the authorization request.

[0221] It should also be understood that when the user installs the App2 on the device B, the device B can obtain the URL address of the authorization server of the App2 from the authorization server of the App2. When the device B receives the authorization request from the device A, the device B can determine that the device A wants to authorize the login of the App1 through the App2, so that the device B can send the HTTP request to the authorization server of the App2 according to the URL address of the authorization server of the App2, and the HTTP request can carry the authorization request.

[0222] S805, in response to receiving the authorization request sent by the device B, the authorization server of the App2 sends a response to the authorization request to the App2 of the device B.

[0223] In an embodiment, the response can be an authorization code.

[0224] In an embodiment, the authorization server of the App2 can verify the identification information of the App1 in the authorization request. If the verification is passed, the authorization server of the App2 can send a response to the device B.

[0225] It should be understood that when the authorization server of the App2 receives the HTTP request sent by the device B, the authorization server of the App2 can send an HTTP response to the device B, and the HTTP response can include the response to the authorization request.

[0226] S806, in response to receiving the response from the authorization server of App2, device B prompts the user to determine whether to agree to the authorized login of App1.

[0227] S807, in response to device B detecting the operation of the user agreeing to the authorized login of App1, App2 of device B sends request information to the authorization server of App2, the request information being used to request an access token.

[0228] S808, in response to receiving the request information from device B, the authorization server of App2 sends the access token to App2 of device B.

[0229] It should be understood that the information between device B and the authorization server of App2 in S804-S808 can be transmitted through a network channel between device B and the authorization server of App2.

[0230] It should be understood that the process of device B sending the request information to the authorization server of App2 and the process of the authorization server of App2 sending the access token to device B can refer to the description in the above embodiments, and will not be repeated here for brevity.

[0231] S809, App2 of device B sends the access token to the data synchronization module of device B.

[0232] S810, the data synchronization module of device B sends the access token to the data synchronization module of device A.

[0233] It should be understood that the process of device B sending the access token to device A can refer to the description in the above embodiments, and will not be repeated here for brevity.

[0234] S811, the data synchronization module of device A sends the access token to App1 of device A.

[0235] S812, App1 of device A sends the access token to the resource server of App2.

[0236] After receiving the access token sent by device B, device A sends an HTTP request to the URL address of the resource server of App2 according to the operation of the user clicking App2 detected on the login (or registration) interface of App1, and the HTTP request can carry the access token.

[0237] It should be understood that when the user installs App1 on device A, device A can obtain the URL address of the resource server of App2 from the resource server of App2.

[0238] It should also be understood that the authorization server of App2 and the resource server of App2 can be two independent servers; or the authorization server of App2 and the resource server of App2 can also be located in the same server, and the embodiments of the present application do not limit this.

[0239] In one embodiment, App1 of device A can also send the identification information of the App1 to the resource server of App2.

[0240] S813, in response to receiving the access token, the resource server of App2 sends a protection resource to App1 of device A, wherein the protection resource includes the account information of App2.

[0241] After receiving the HTTP request sent by device A, the resource server of App2 can obtain the access token therefrom, and since the access token is sent by the authorization server of App2 to device B, the resource server of App2 can determine that device A hopes to request the account information of App2 logged in device B, so that the resource server of App2 can send an HTTP response to device A, and the HTTP response can carry the protection resource.

[0242] After waiting for the protection resource, App1 of device A can log in according to the user data therein. For example, App1 obtains the account information of App2 in the protection resource, and App1 can generate an App1 account using the account information of App2, or query the App1 account associated with the account information of App2, thereby realizing login.

[0243] Figure 9 A schematic flowchart of a method 900 for authorizing by other devices is shown. The method 900 includes:

[0244] S901, device A detects, in the login or registration interface of App1, an operation of a user logging in or registering by using a third-party application App2.

[0245] For example, as shown in (a) of FIG. 10, the mobile phone detects an operation of the user logging in by using a third-party account (App2). Figure 3

[0246] S902, in response to the operation, device A sends a first message, and the first message is used to query whether the device receiving the first message is installed with App2.

[0247] In one embodiment, the first message is used to query whether the device receiving the first message is installed with and logged in App2.

[0248] ​It should be understood that the process of device A sending the first message can refer to the description in the above embodiments, which will not be repeated here for brevity.

[0249] S903, upon receiving the first message, device B can detect whether App2 is installed in device B.

[0250] For example, device A can send a BLE data packet to device B, which can include the package name information of App2. The BLE data packet includes a protocol data unit, and the package name information of App2 can be carried in a service data field in the PDU, or can also be carried in a vendor specific data field in the PDU. For example, the load of the service data field can include a plurality of bit positions, wherein the plurality of bit positions include extensible bit positions. Device A can encode the package name information of App2 by using GBK, ISO8859-1, or Unicode (for example, UTF-8, UTF-16), and carry the encoded information on one or more extensible bit positions. After receiving the BLE data packet sent by device A, device B can decode the information on the corresponding bit positions to obtain the package name information of App2, thereby obtaining whether device A wants to query whether App2 is installed in device B.

[0251] Device B can query the package name information of all applications installed in the application layer, and if the package name information of an application in device B is the same as the package name information carried in the BLE data packet, device B can determine that App2 is installed.

[0252] In one embodiment, the first message is used to query whether the device receiving the first message has installed and logged in App2.

[0253] For example, the device A can send a BLE data packet to the device B, and the BLE data packet can include the package name information of the App2 and indication information indicating whether the device B has logged in the application corresponding to the package name information. The BLE data packet includes a protocol data unit, and the package name information of the App2 and the indication information can be carried in a service data field in the PDU or a vendor specific data field in the PDU. For example, the load of the service data field can include a plurality of bits, and the plurality of bits include extensible bits. The device A can encode the package name information of the App2 by using a coding mode such as GBK, ISO8859-1 or Unicode (for example, UTF-8, UTF-16), and carry the encoded information on one or more extensible bits. The device A can also set a certain extensible bit to 1 (1 indicates that the device B queries whether the device B has installed and logged in the application corresponding to the package name information). After receiving the BLE data packet sent by the device A, the device B can decode the information on the corresponding bit to obtain the package name information of the App2, and determine that the device A wants to query whether the device B has installed and logged in the application corresponding to the package name information through the bit 1.

[0254] The device B can query the package name information of all applications installed in the application layer, and if the package name information of a certain application in the device B is the same as the package name information carried in the BLE data packet, the device B can determine that the App2 is installed. After determining that the App2 is installed, the data synchronization module of the device B can call a query login interface (for example, a content provider interface) to send a request to the App2 in the application layer, and the request is used to request the App2 to determine whether an account is logged in. If the App2 logs in the account, the App2 can send a response to the data synchronization module, and the response is used to indicate that the App2 logs in the account. Thus, the device B can determine that the device B has installed and logged in the App2.

[0255] S904, when the device B determines that the App2 is installed, the device B can send a response to the device A, and the response is used to indicate that the device B has installed the App2.

[0256] In one embodiment, if the first message is used to query whether the device receiving the first message has installed and logged in the App2, when the device B determines that the App2 is installed and logged in, the device B can send a response to the device A, and the response is used to indicate that the device B has installed and logged in the App2.

[0257] It should be understood that the process of the device B sending a response to the device A can refer to the description in the above embodiments, and will not be described here in detail.

[0258] In one embodiment, the method 900 further includes: device A requesting, from a server of App1, identification information of App1 on device A.

[0259] In one embodiment, the identification information of App1 is a unique identifier of App1.

[0260] It should be understood that the process of device A obtaining the identification information of App1 can refer to the description in the above embodiments, which will not be repeated here for brevity.

[0261] S905, device A sends a authorization request to device B, the authorization request is used to request App2 on device B to authorize login of App1, and the authorization request includes the identification information. S906, in response to receiving the authorization request, device B sends the authorization request to a server of App2.

[0262] In one embodiment, device B sends the authorization request to an authorization server of App2.

[0263] In the embodiments of the present application, the authorization request sent by device B to the server of App2 can be transmitted through a network transmission channel between device B and the server of App2.

[0264] In one embodiment, when device B receives the authorization request, if device B has installed App2 but there is no login account on App2, device B can prompt the user to log in the account of App2. After device B detects that the user has logged in App2, device B can send the authorization request to the server of App2.

[0265] S907, the server of App2 responds to receiving the authorization request and checks the identification information of App1.

[0266] Since the server of App1 has previously requested the identification information of App1 from the server of App2, the identification information of App1 sent to the server of App1 can be saved in App2. When the server of App2 obtains the authorization request sent by device A, the server of App2 can check the identification information of App1 sent by device B according to the identification information of App1 saved by the server of App2.

[0267] S908, in response to successful checking of the identification information of App1, the server of App2 sends a response.

[0268] In one embodiment, the response can be used to indicate device B to confirm with the user whether to agree to the authorized login of App1.

[0269] In one embodiment, the response can be an authorization code.

[0270] S909, in response to receiving the response from the server of App2, device B can display an authorization login interface.

[0271] For example, as shown in (c) of FIG. 9, in response to receiving the authorization code from the server of App2, the mobile phone can display the authorization login information of App1 on the display interface of App2. As shown in (c) of FIG. 9, the display interface of App2 includes a prompt information “App1 applies to use your account information”. Figure 3 Figure 3

[0272] In one embodiment, the authorization login interface can further include multiple options of the account information of App2, for example, the avatar information, gender, nickname, etc. of the account of App2. The user can select some or all of the options.

[0273] S910, in response to the operation of the user agreeing to the authorization login of App1, device B sends a request information to the server of App2, the request information being used to request an access token.

[0274] In one embodiment, device B sends the request information to the authorization server of App2.

[0275] S911, in response to obtaining the request information from device B, the server of App2 sends an access token to device B.

[0276] It should be understood that the signaling in S912 and S913 can be transmitted through the network transmission channel between device B and the server of App2.

[0277] For example, in response to the operation of the user agreeing to the authorization login of App1, device B can send an HTTP request to the server of App2 according to the URL address of the server of App2, the HTTP request carrying the request information; in response to receiving the HTTP request sent by device B, the server of App2 can send an HTTP response to device B, the HTTP response including the access token.

[0278] S912, in response to receiving the access token from the server of App2, device B sends the access token to device A.

[0279] It should be understood that the process of device B sending the access token to device A can refer to the description of the above embodiments, and will not be described here for brevity.

[0280] ​​S913, in response to receiving the access token from the device B, the device A sends the access token to the server of the App2.

[0281] In one embodiment, the device A sends the access token to the resource server of the App2.

[0282] In one embodiment, the device A can send the access token and the identification information of the App1 to the resource server of the App2. After receiving the access token and the identification information of the App1, the resource server of the App2 can first verify the identification information of the App1. If the resource server of the App2 verifies the identification information of the App1 successfully, the resource server of the App2 can send the account information of the App2 to the device A.

[0283] For example, after receiving the access token sent by the device B, the device A sends an HTTP request to the URL address of the resource server of the App2 according to the operation of the user clicking the App2 detected on the login (or registration) interface of the App1, and the HTTP request can carry the access token.

[0284] S914, in response to receiving the access token from the device A, the server of the App2 can send the account information of the App2 to the device A.

[0285] For example, in response to receiving the HTTP request sent by the device A, the resource server of the App2 can obtain the access token in the HTTP request. Since the access token is the access token sent by the authorization server of the App2 to the device B, the resource server of the App2 can know that the device A wants to use the access token to request the account information of the App2 logged in the device B, so the resource server of the App2 sends an HTTP response to the device A, and the HTTP response can carry the account information of the App2 logged in the device B.

[0286] In one embodiment, if the user selects part of the account information (for example, the user selects the avatar information and the nickname of the App2 account) in S911, the server of the App2 can determine the part of the account information authorized by the user. After receiving the access token sent by the device A, the server of the App2 can send the part of the account information to the device A.

[0287] S915, in response to receiving the account information of the App2 from the server of the App2, the device A implements the login or registration of the App1.

[0288] After receiving the account information, the App1 of the device A can log in according to the user data in the account information. For example, the App1 can generate an account of the App1 using the account information of the App2, or query an account of the App1 that is associated with the account of the App2, so as to log in.

[0289] It should be understood that the S915 can refer to the implementation process in the prior art, and details are not described herein for brevity.

[0290] Figure 10 A schematic flowchart of a method 1000 for authorizing by other devices is shown. The method 1000 includes the following steps.

[0291] In the S1001, the device A detects, in a login or registration interface of the App1, an operation of logging in or registering by using other devices.

[0292] For example, as shown in (a) of FIG. 5, the mobile phone detects the operation of the control 502 for logging in by using other devices. Figure 5

[0293] In the S1002, in response to the operation, the device A sends a second message for querying whether the surrounding device is installed with the App1.

[0294] It should be understood that the process of sending the second message by the device A can refer to the process of sending the first message by the device A in the method 900 described above, and details are not described herein for brevity.

[0295] In the S1003, the device B can detect whether the device B is installed with the App1 after receiving the second message.

[0296] It should be understood that the process of detecting whether the device B is installed with the App1 can refer to the process of detecting whether the device B is installed with the App2 described above, and details are not described herein for brevity.

[0297] In the S1004, the device B can send a response to the device A after determining that the device B is installed with the App1, and the response is used to indicate that the device B is installed with the App1.

[0298] It should be understood that the process of sending the response by the device B to the device A can refer to the description in the embodiments described above, and details are not described herein for brevity.

[0299] In the S1005, the device A sends an authorization request to the device B, and the authorization request is used to request the App1 on the device B to authorize the App1 on the device A to log in.

[0300] In one embodiment, the authorization request can include identification information of the App1.​

[0301] It should be understood that the process of device A obtaining the identification information of App1 can refer to the description in the above embodiments, which will not be repeated here for brevity.

[0302] S1006, in response to receiving the authorization request, device B sends the authorization request to the server of App1.

[0303] In one embodiment, device B sends the authorization request to the authorization server of App1.

[0304] In the embodiments of the present application, the authorization request sent by device B to the server of App1 can be transmitted through the network transmission channel between device B and the server of App1.

[0305] For example, after receiving the authorization request sent by device A, device B can send an HTTP request to the server of App1 according to the URL address of the server of App1, and the HTTP request can include the authorization request.

[0306] It should be understood that when the user installs App1 on device B, device B can obtain the URL address of the server of App1 from the server of App1.

[0307] S1007, the server of App1 responds to the authorization request and checks the identification information of App1. When the server of App1 obtains the authorization request sent by device A, it can check the identification information of App1 sent by device B according to the identification information of App1 saved by the server of App1.

[0308] S1008, in response to the successful check of the identification information of App1, the server of App1 sends a response to device B.

[0309] In one embodiment, the response can be used to indicate device B to confirm with the user whether to agree to the authorized login of App1.

[0310] In one embodiment, the response can be an authorization code.

[0311] For example, in response to receiving the HTTP request, if the server of App1 checks the identification information of App1 successfully, the server of App1 can send an HTTP response to device B, and the HTTP response can carry the response to the authorization request.

[0312] S1009, in response to receiving the response from the server of App1, device B can display an authorized login interface.

[0313] For example, in response to receiving the HTTP request, if the server of App1 checks the identification information of App1 successfully, the server of App1 can send an HTTP response to device B, and the HTTP response can carry the response to the authorization request. Figure 5As shown in (c) in FIG. 10, in response to receiving the response from the server of App1, the phone can display "authorize notebook computer to log in" on the display interface of App1.

[0314] S1010, in response to the operation of the user agreeing to authorize App1 to log in, the device B sends request information to the server of App1, the request information being used to request an access token.

[0315] In one embodiment, the device B sends the request information to the authorization server of App1. S1011, in response to obtaining the request information from the device B, the server of App1 sends an access token to the device B.

[0316] It should be understood that the signaling in S1010 and S1011 can be transmitted through a network transmission channel between the device B and the server of App1.

[0317] It should be understood that the process of the device B sending the request information to the server of App1 can refer to the process of the device B sending the request information to the server of App2 described above, and the process of the server of App1 sending the access token to the device B can refer to the process of the server of App2 sending the access token to the device B described above.

[0318] S1012, in response to receiving the access token from the server of App1, the device B sends the access token to the device A.

[0319] It should be understood that the process of the device B sending the access token to the device A can refer to the description of the above embodiment.

[0320] S1013, in response to receiving the access token from the device B, the device A sends the access token to the server of App1.

[0321] In one embodiment, the device A sends the access token to the resource server of App2.

[0322] In one embodiment, the device A sends the access token and the identification information of App1 to the resource server of App2.

[0323] S1014, in response to receiving the access token from the device A, the server of App1 can send the account information of App1 to the device A.

[0324] It should be understood that the process of device A sending an access token to the server of App1 can be referred to as the process of device A sending an access token to the server of App2 described above, and the process of the server of App1 sending the account information of App1 to device A can be referred to as the process of the server of App2 sending the account information of App2 to device A described above. For the sake of brevity, it will not be described again here.

[0325] S1015, in response to receiving the account information of App1 from the server of App1, device A enables App1 to log in or register.

[0326] For example, such as Figure 5 As shown in (d), after receiving the account information sent by the server of App1, the laptop can log in to App1. The account used to log in to App1 on the laptop is the same as the account used to log in to App1 on the mobile phone.

[0327] Figure 11 A schematic flowchart of a method 1100 for utilizing other devices, as provided in an embodiment of this application, is shown. This method is applicable to systems including device A (e.g., a laptop computer in the above embodiment) and device B (e.g., a mobile phone in the above embodiment). The method 1100 includes:

[0328] S1101, Device A displays a first interface, which is the account login or account registration interface of the first application.

[0329] For example, such as Figure 3 As shown in (a), the laptop can display the account login interface of App1, which includes information about logging in through third-party accounts (e.g., App2, App3, and App4).

[0330] S1102, in response to detecting that a user logs in or registers an account with the first application through the second application, device A sends a first request message to device B, the first request message being used to request the second application on device B to authorize the first application.

[0331] For example, such as Figure 3 As shown in (b), when the laptop detects that the user clicks to log in to the account of App1 through App2, the laptop can send the first request information to the mobile phone.

[0332] In one embodiment, the method further includes: before device A sends the first request information to device B, sending a query request, the query request being used to request the electronic device receiving the query request to determine whether the second application is installed; device A receiving a first response sent by device B, the first response being used to indicate that device B has installed the second application.

[0333] It should be understood that the process of device A sending the query request to device B and device B determining whether to install the second application can be referred to the description in the above embodiments, and will not be repeated here for the sake of brevity.

[0334] In one embodiment, the method further includes: before device A sends the first request information to device B, sending a query request, the query request being used to request the electronic device receiving the query request to determine whether the second application is installed and logged in; device A receiving a first response sent by device B, the first response being used to indicate that device B has installed and logged in to the second application.

[0335] It should be understood that the process by which device B determines whether to install and log in to the second application can be referred to the description in the above embodiments, and will not be repeated here for the sake of brevity.

[0336] In one embodiment, the method 1100 further includes: device A receiving a second response sent by device C, the second response indicating that device C has installed the second application; device A prompting a user to authorize the first application through the second application on device B or device C; and in response to the user's operation of selecting the second electronic device, device A sending the first request information to device B.

[0337] For example, such as Figure 4 As shown in (b), after receiving responses from the mobile phone and tablet, the laptop can display a prompt box 402, which includes the message "Multiple devices with App2 installed have been detected nearby. Please select one." In response to detecting that the user selects the mobile phone and clicks the control 403, the laptop sends an authorization request to the mobile phone. This authorization request is used to request App2 on the mobile phone to authorize the login of App1.

[0338] S1103, Device B sends a second request to the server corresponding to the second application based on the first request information. The second request is used to request the first information. The first information is used by Device A to request the information of the first account. The first account is the account logged in to the second application on Device B.

[0339] In one embodiment, the first information is an access token.

[0340] In one embodiment, device B sends a second request message to the server corresponding to the second application based on the first request message, including: in response to receiving the first request message, device B sends the first request message to the server; in response to receiving a third response from the server regarding the first request message, device B prompts the user whether they agree to the first application using the information of the first account; in response to the user's agreement to the first application using the information of the first account, device B sends the second request message to the server.

[0341] For example, such as Figure 3 As shown in (c), after the mobile phone receives the third response from the server, the mobile phone can prompt the user "App1 requests to use your account information". When the mobile phone detects that the user clicks on control 304, the mobile phone can send a second request message to the laptop computer, which is used to request an access token.

[0342] In one embodiment, the third response may be an authorization code.

[0343] S1104, Device B receives the first information sent by the server.

[0344] It should be understood that the process in S1104 can be referenced. Figure 7 For the sake of brevity, the descriptions in the illustrated embodiments will not be repeated here.

[0345] S1105, Device B sends the first information to Device A.

[0346] It should be understood that the process in S1105 can be referenced. Figure 7 For the sake of brevity, the descriptions in the illustrated embodiments will not be repeated here.

[0347] S1106, Device A requests the information of the first account from the server based on the first information.

[0348] It should be understood that the process of S1106 can be referred to the process of S812 above, and for the sake of brevity, it will not be repeated here.

[0349] S1107, Device A receives the information of the first account sent by the server.

[0350] S1108, Device A performs account login or account registration for the first application based on the information of the first account.

[0351] It should be understood that the process of device A receiving the information of the first account sent by the server and logging in or registering an account based on the information of the first account can be referred to the description in S813 above.

[0352] Figure 12A schematic block diagram of a device 1200 provided in an embodiment of this application is shown. This device 1200 can be disposed in the above-described... Figure 11 In device A, device 1200 includes: a display unit 1210 for displaying a first interface, which is an account login or account registration interface for a first application; a detection unit 1220 for detecting a user's operation of logging into or registering an account with the first application through a second application; a sending unit 1230 for sending a first request message to a second electronic device in response to the operation, the first request message being used to request the second application on the second electronic device to authorize the first application; a receiving unit 1240 for receiving first information from the second electronic device, the first information being used by the device to request information about a first account, the first account being the login account of the second application on the second electronic device, wherein the first information is obtained by the second electronic device from a server; the sending unit 1230 is also used to request the information about the first account from the server based on the first information; and the receiving unit 1240 is used to receive the information about the first account sent by the server and perform account login or account registration for the first application based on the information about the first account.

[0353] Figure 13 A schematic block diagram of a device 1300 provided in an embodiment of this application is shown. This device 1300 can be disposed in the above-described... Figure 11 In device B, the device 1300 includes: a receiving unit 1310, configured to receive a first request message sent by a first electronic device, the first request message being used to request the second application on the device to authorize the first application; a sending unit 1320, configured to send a second request message to a server corresponding to the second application based on the first request message, the second request message being used to request first information, the first information being used by the first electronic device to request information about a first account, the first account being the account logged into by the second application on the device; the receiving unit 1310 is also configured to receive the first message sent by the server; the sending unit 1320 is also configured to send the first message to the first electronic device.

[0354] Figure 14 A schematic structural diagram of an electronic device 1400 provided in an embodiment of this application is shown. Figure 14 As shown, the electronic device includes: one or more processors 1410, and one or more memories 1420. The one or more memories 1420 store one or more computer programs, which include instructions. When the instructions are executed by the one or more processors 1410, they cause the first electronic device or the second electronic device to perform the technical solutions described in the above embodiments.

[0355] The embodiment of the present application provides a system, comprising a first electronic device and a second electronic device, and the system is used for executing the technical solutions in the above-mentioned embodiments. The implementation principle and technical effects are similar to those of the above-mentioned method-related embodiments, and details are not described herein again.

[0356] The embodiment of the present application provides a computer program product, when the computer program product is run on the first electronic device (or the notebook computer in the above-mentioned embodiment), the first electronic device executes the technical solutions in the above-mentioned embodiments. The implementation principle and technical effects are similar to those of the above-mentioned method-related embodiments, and details are not described herein again.

[0357] The embodiment of the present application provides a computer program product, when the computer program product is run on the second electronic device (or the mobile phone in the above-mentioned embodiment), the second electronic device executes the technical solutions in the above-mentioned embodiments. The implementation principle and technical effects are similar to those of the above-mentioned method-related embodiments, and details are not described herein again.

[0358] The embodiment of the present application provides a readable storage medium, the readable storage medium contains instructions, when the instructions are run on the first electronic device (or the notebook computer in the above-mentioned embodiment), the first electronic device executes the technical solutions in the above-mentioned embodiments. The implementation principle and technical effects are similar, and details are not described herein again.

[0359] The embodiment of the present application provides a readable storage medium, the readable storage medium contains instructions, when the instructions are run on the second electronic device (or the mobile phone in the above-mentioned embodiment), the second electronic device executes the technical solutions in the above-mentioned embodiments. The implementation principle and technical effects are similar, and details are not described herein again.

[0360] The embodiment of the present application provides a chip, the chip is used for executing instructions, when the chip is run, the technical solutions in the above-mentioned embodiments are executed. The implementation principle and technical effects are similar, and details are not described herein again.

[0361] Those skilled in the art can realize that the units and algorithm steps of the examples described in combination with the embodiments disclosed herein can be realized by electronic hardware or a combination of computer software and electronic hardware. Whether the functions are realized in hardware or software mode depends on the specific application and design constraints of the technical solutions. The skilled person can use different methods to realize the described functions for each specific application, but such implementation should not be considered beyond the scope of the present application.

[0362] Those skilled in the art can clearly understand that, for the convenience and brevity of the description, the specific working processes of the above-mentioned system, device and unit can refer to the corresponding processes in the foregoing method embodiments, and details are not described herein again.

[0363] In several embodiments provided in the present application, it should be understood that the disclosed system, device and method can be implemented in other manners. For example, the described device embodiments are merely schematic. For example, the division of the units is only a logical function division. There can be another division manner for the actual implementation, for example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the displayed or discussed mutual couplings or direct couplings or communication connections between the units can be indirect couplings or communication connections through some interfaces, devices or units, and can be in electrical, mechanical or other forms.

[0364] The units described as separate components can or can not be physically separate, and the components displayed as units can or can not be physical units, i.e., can be located in one place, or can be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purposes of the embodiments.

[0365] In addition, each functional unit in the embodiments of the present application can be integrated into a processing unit, or each unit can exist physically, or two or more units can be integrated into one unit.

[0366] If the functions are implemented in the form of software function units and sold or used as independent products, they can be stored in a computer readable storage medium. Based on this understanding, the technical solutions of the present application essentially or the parts that make contributions to the prior art or parts of the technical solutions can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the embodiments of the present application. The aforementioned storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and various media that can store program codes.

[0367] The above description is merely specific embodiments of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art can easily think of changes or replacements within the technical scope disclosed in the present application, which should be covered within the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A system comprising a first electronic device and a second electronic device, characterized in that, The first electronic device is used to display a first interface, which is the account login or account registration interface of the first application; The first electronic device is further configured to send a first request message to the second electronic device in response to detecting that a user performs an account login or account registration operation on the first application through the second application. The first request message is used to request the second application on the second electronic device to authorize the first application. The second electronic device is used to send a second request message to the server corresponding to the second application according to the first request message. The second request message is used to request first information. The first information is used by the first electronic device to request information of a first account. The first information is an access token, and the first account is the account logged in by the second application on the second electronic device. The second electronic device is further configured to receive the first information sent by the server and send the first information to the first electronic device; The first electronic device is further configured to send the first information to the server to request information about the first account; The first electronic device is also configured to receive information of the first account sent by the server and, based on the information of the first account, perform account login or account registration for the first application. Specifically, the second electronic device is used to send the first request information to the server and receive response information from the server in response to the first request information. The response information is used to instruct the second electronic device to confirm with the user whether they agree to authorize login to the first application. In response to the user's authorization of the first application on the second electronic device, the second request information is sent to the server.

2. The system according to claim 1, characterized in that, The first electronic device is also used for: Before sending the first request information to the second electronic device, a query request is sent, the query request being used to request the electronic device receiving the query request to determine whether the second application is installed; Receive a first response from the second electronic device, the first response indicating that the second electronic device has installed the second application.

3. The system according to claim 2, characterized in that, The first electronic device is also used for: Receive a second response from a third electronic device, the second response indicating that the third electronic device has installed the second application; The user is prompted to authorize the first application via the second application on the second electronic device or the third electronic device; In response to the user's selection of the second electronic device, the first request information is sent to the second electronic device.

4. The system according to any one of claims 1 to 3, characterized in that, The first request information includes the identification information of the first application.

5. The system according to any one of claims 1 to 3, characterized in that, The first electronic device is a device that does not have the second application installed.

6. A method for licensing using other devices, characterized in that, The method is applied to a first electronic device, and the method includes: The first electronic device displays a first interface, which is the account login or account registration interface of the first application; In response to detecting that a user logs in or registers an account with the first application through the second application, the first electronic device sends a first request message to the second electronic device, and the first request message is sent by the second electronic device to the server corresponding to the second application. The first request message is used to request the second application on the second electronic device to authorize the first application. The first electronic device receives first information sent by the second electronic device. The first information is used by the first electronic device to request information about a first account. The first information is an access token, and the first account is the account logged in by the second application on the second electronic device. The first information is obtained by the second electronic device from the server. The first electronic device sends the first information to the server to request information about the first account; The first electronic device receives the information of the first account sent by the server and performs account login or account registration for the first application based on the information of the first account.

7. The method according to claim 6, characterized in that, Before sending the first request information to the second electronic device, the method includes: Send a query request, the query request being used to request the electronic device receiving the query request to determine whether the second application is installed; Receive a first response from the second electronic device, the first response indicating that the second electronic device has installed the second application.

8. The method according to claim 6 or 7, characterized in that, Before sending the first request information to the second electronic device, the method includes: Receive a second response from a third electronic device, the second response indicating that the third electronic device has installed the second application; The user is prompted to authorize the first application via the second application on the second electronic device or the third electronic device; The step of sending the first request information to the second electronic device includes: In response to the user's selection of the second electronic device, the first request information is sent to the second electronic device.

9. The method according to claim 6 or 7, characterized in that, The first request information includes the identification information of the first application.

10. The method according to claim 6 or 7, characterized in that, The first electronic device is a device that does not have the second application installed.

11. A method for licensing using other devices, characterized in that, The method is applied to a second electronic device, and the method includes: The second electronic device receives a first request message sent by the first electronic device, the first request message being used to request a second application on the second electronic device to authorize the first application; The second electronic device sends a second request to the server corresponding to the second application based on the first request information. The second request information is used to request the first information, which is used by the first electronic device to request the information of the first account. The first information is an access token, and the first account is the account logged in by the second application on the second electronic device. The second electronic device receives the first information sent by the server; The second electronic device sends the first information to the first electronic device, so that the first electronic device sends the first information to the server to request information about the first account; The second electronic device sends a second request to the server corresponding to the second application based on the first request information, including: The second electronic device sends the first request information to the server and receives response information from the server in response to the first request information. The response information is used to instruct the second electronic device to confirm with the user whether they agree to authorize login to the first application. In response to the user's authorization of the first application on the second electronic device, the second electronic device sends the second request information to the server.

12. The method according to claim 11, characterized in that, Before the second electronic device receives the first request information sent by the first electronic device, the method further includes: The second electronic device receives a query request sent by the first electronic device, the query request being used to request the electronic device receiving the query request to determine whether the second application is installed; The second electronic device sends a first response to the first electronic device, the first response indicating that the second electronic device has installed the second application.

13. The method according to claim 11 or 12, characterized in that, The first request information includes the identification information of the first application.

14. The method according to claim 11 or 12, characterized in that, The first electronic device is a device that does not have the second application installed.

15. An electronic device, characterized in that, include: One or more processors; One or more memory units; The one or more memories store one or more computer programs, the one or more computer programs including instructions that, when executed by the one or more processors, cause the electronic device to perform the method as described in any one of claims 6 to 10.

16. An electronic device, characterized in that, include: One or more processors; One or more memory units; The one or more memories store one or more computer programs, the one or more computer programs including instructions that, when executed by the one or more processors, cause the electronic device to perform the method as described in any one of claims 11 to 14.

17. A computer-readable storage medium, characterized in that, Includes computer instructions that, when executed on an electronic device, cause the electronic device to perform the method as described in any one of claims 6 to 10; or, When the computer instructions are executed on an electronic device, the electronic device causes the electronic device to perform the method as described in any one of claims 11 to 14.

Images