Equipment positioning method and electronic equipment

Abstract

The invention provides a device positioning method and an electronic device, and relates to the technical field of terminals, a cloud device can verify whether a first electronic device is bound by using an obtained device identifier and a first user account of the first electronic device, and then the first electronic device can be accurately positioned under the condition that the first electronic device is repeatedly bound. And sending the first notification information to the second electronic equipment which is logged in by the second user account which is bound with the first electronic equipment in advance, so as to prompt the current position of the first electronic equipment to a user to which the second user account belongs through the first notification information, thus, even under the condition that the first electronic equipment is refurbished, the current position of the first electronic equipment can be prompted to the user to which the second user account belongs. In the embodiment of the invention, the first electronic equipment can still be positioned, the loss finding probability of the electronic equipment can be improved, the probability of loss or leakage of information stored by a user in the electronic equipment is reduced, and the user experience is further improved.

Description

Technical Field

[0001] This application relates to the field of terminal technology, and in particular to a device positioning method and an electronic device. Background Technology

[0002] As people become increasingly reliant on electronic devices such as mobile phones and tablets, they are increasingly inclined to store more data, information, and images on these devices. Consequently, the security of electronic devices and assets is receiving more and more attention, and the demand for recovering lost electronic devices is growing stronger. Currently, the device location function built into electronic devices only relies on the user's logged-in account to locate the location of various electronic devices associated with that account, thus enabling the search for lost devices.

[0003] However, the above search method can only be used to locate lost electronic devices if the user account is logged in. If the lost electronic device is "restored" or the user account is forcibly logged out, it will be impossible to locate the lost electronic device, thus making it impossible to find the lost electronic device. This may result in the loss or leakage of user information stored on the electronic device, affecting the user experience. Summary of the Invention

[0004] This application provides a device positioning method and an electronic device, which can improve the probability of recovering lost electronic devices, help reduce the probability of loss or leakage of user-stored information in electronic devices, and thus improve the user experience.

[0005] To achieve the above objectives, the embodiments of this application adopt the following technical solutions:

[0006] Firstly, a device positioning method is provided for cloud devices. In this method, when the cloud device receives a device identifier and a first user account from a first electronic device, it first verifies whether the first electronic device has been repeatedly bound based on the first user account and device identifier. Secondly, if the first electronic device has been repeatedly bound, a first notification message is sent to a second electronic device logged into with a second user account to inform the user holding the second electronic device of the current location of the first electronic device. Thus, even if the first electronic device is lost by another user or has been reprogrammed, it can still be located, and the original user of the first electronic device can be notified. This increases the probability of recovering a lost electronic device and helps reduce the probability of loss or leakage of user-stored information on the electronic device, thereby improving the user experience.

[0007] The first user account is the user account that requests to bind to the first electronic device.

[0008] The first notification information is used to inform the user holding the second electronic device of the current location of the first electronic device; the second user account is the account that has been bound to the first electronic device.

[0009] In one possible implementation of the first aspect, when the cloud device determines that the first electronic device has been repeatedly bound based on the first user account and the device identifier, the cloud device obtains the second user account that has been bound to the first electronic device based on the device identifier of the first electronic device; if the cloud device obtains the second user account and the second user account is inconsistent with the first user account, it indicates that the first electronic device has previously established a binding relationship with the second user account, and the first electronic device has been repeatedly bound, that is, the first electronic device has been repeatedly bound.

[0010] Here, when the cloud device verifies the binding relationship of the first electronic device, it does not blindly determine that the first electronic device has been bound to another user account (i.e., the second user account) as soon as it obtains the first electronic device's previous binding. Instead, it accurately determines the binding status of the first electronic device (e.g., duplicate binding, normal binding, not bound, etc.) after a detailed comparison of the first user account and the second user account. This improves the accuracy of obtaining the binding status and avoids sending incorrect notification messages to the user due to incorrect acquisition of the binding status, which would cause unnecessary interference to the user's normal use process.

[0011] In one possible implementation of the first aspect, when the cloud device compares the first user account with the second user account, if the first user account and the second user account are the same, it means that the first user account is the user account previously bound to the first electronic device, and there is no duplicate binding. At this time, it can be considered that the first electronic device and the first user account are normally bound; that is, it is determined that the first electronic device is normally bound. When the first electronic device is normally bound, the cloud device can respond to the received account unbinding instruction for the first electronic device, unbind the binding relationship between the first electronic device and the first user account, and delete the saved binding information of the first electronic device. It can be seen that the cloud device can only perform the unbinding operation on the first electronic device when the first electronic device is normally bound. In this way, the first electronic device can be "forced" to unbind, and the security of the electronic device can be improved, reducing the probability of loss or leakage of user information stored in the electronic device, thereby improving the user experience.

[0012] The binding information is used to indicate that the first electronic device has been bound to the first user account.

[0013] In one possible implementation of the first aspect, if the cloud device does not obtain the second user account bound to the first electronic device, it means that the first electronic device is not currently bound to any user account. In this case, the cloud device can back up the binding information of the first electronic device so as to use the binding information of the first electronic device to ensure the security of the first electronic device in the subsequent use of the first electronic device.

[0014] The binding information is used to indicate that the first electronic device has been bound to the first user account.

[0015] In one possible implementation of the first aspect, the device identifier includes at least one of the device serial number, device identification code, and device chip number of the first electronic device; the device identifier is used to uniquely identify the first electronic device. Therefore, when binding a user account to an electronic device, different device identifiers can be selected to achieve the binding of the electronic device, as long as the device identifier can uniquely identify the first electronic device. This enriches the binding methods of electronic devices, meets different binding needs, and improves the user experience.

[0016] In one possible implementation of the first aspect, if the cloud device determines that the first electronic device has been repeatedly bound, the cloud device may send a second notification message to the first electronic device to indicate that the first user account and the first electronic device cannot be bound together, so as to make the user aware of the binding status of the first electronic device.

[0017] Secondly, a device positioning method is provided, applied to a first electronic device. In this device positioning method, firstly, when the first electronic device determines that it is not bound to a user account, it sends the device identifier of the first electronic device and the first user account to a cloud device to request the backup of the binding information between the first electronic device and the first user account in the cloud device; secondly, it receives and displays the second notification information fed back by the cloud device.

[0018] The second notification message is used to indicate that the first user account failed to be bound to the first electronic device.

[0019] Thirdly, a device positioning method is provided, applied to a first electronic device. In this method, firstly, the first electronic device responds to an account input operation by obtaining a first user account entered by the user and a device identifier used to uniquely identify the first electronic device. Secondly, after obtaining the first user account and device identifier, the first electronic device verifies whether it has been repeatedly bound to another device based on the first user account and device identifier. Thirdly, if the first electronic device has been repeatedly bound to another device, the first electronic device sends a device positioning request to a cloud device. This request requests the cloud device to send a first notification message to a second electronic device logged in with a second user account. The first notification message then informs the user holding the second electronic device of the current location of the first electronic device. Thus, even if the first electronic device is lost by another user or has been re-flashed, it can still be located, and the original user of the first electronic device can be notified. This increases the probability of recovering a lost electronic device and helps reduce the probability of loss or leakage of user-stored information on the electronic device, thereby improving the user experience.

[0020] The first user account is the user account that needs to be logged into the first electronic device.

[0021] The device location request is used to request the cloud device to send a first notification message to the second electronic device. The first notification message includes the current location of the first electronic device and a second user account logged in on the second electronic device. The second user account is the account that the first electronic device has been bound to.

[0022] In one possible implementation of the third aspect, when it is determined that the first electronic device is normally bound, that is, when the first user account is normally logged into the first electronic device, the first electronic device can respond to the user's account unbinding operation and unbind the binding relationship between the first electronic device and the first user account. First, it obtains the identity verification information entered by the user through the identity verification interface, and uses the obtained identity verification information to complete the user's identity verification. Second, if the obtained identity verification information of the user is verified, it removes the binding relationship between the first electronic device and the first user account and deletes the saved binding information of the first electronic device. It is evident that the first electronic device can only... Under normal binding conditions, an unbinding operation is performed on the first electronic device. This avoids the first electronic device being "forced" to unbind, improves the security of the electronic device, reduces the probability of loss or leakage of user information stored on the electronic device, and thus improves the user experience. Finally, the first electronic device sends an account unbinding command to the cloud device to synchronize the unbinding information of the first electronic device on the cloud device and request the cloud device to delete the previously saved binding information of the first electronic device. This completes the "dual" unbinding of the first electronic device on both the "local" side and the "cloud" side, thereby avoiding the retention of the binding information of the first electronic device on the cloud device and causing unnecessary interference to the user's normal use process.

[0023] Here, in order to avoid the first electronic device being "forced" to unbind, the identity of the user requesting unbinding is verified before unbinding. Therefore, in order to facilitate the user to complete the identity verification process, after the user performs the account unbinding operation, the identity verification interface can be provided to the user without the user performing any operation. In this way, the operation required by the user to complete the identity verification is reduced, and the response frequency and data processing volume of the first electronic device are reduced.

[0024] The binding information is used to indicate that the first electronic device has been bound to the first user account.

[0025] In one possible implementation of the third aspect, when it is determined that the first electronic device is normally bound, that is, when the first user account is normally logged into the first electronic device, the first electronic device can respond to the user's account logout operation and log out of the first user account on the first electronic device. First, in response to the account logout operation, the first electronic device displays an unbinding prompt interface so that the user can use the unbinding prompt interface to clarify whether to perform the account unbinding operation. Second, in response to the user's account unbinding operation performed in the unbinding prompt interface, the first electronic device displays an identity verification interface. Then, it obtains the identity verification information entered by the user in the identity verification interface. Finally, if the identity verification information is verified, the first electronic device and the first user account are unbound, the binding information of the first electronic device is deleted, and an account unbinding instruction is sent to the cloud device, as well as the first user account that has logged into the first electronic device is logged out.

[0026] The account unbinding instruction is used to request the deletion of the binding information of the first electronic device that has been saved in the cloud device; the binding information is used to indicate that the first electronic device has been bound to the first user account.

[0027] Here, to prevent the binding relationship between the first electronic device and the first user account from affecting other user accounts when the first electronic device logs out after the first user account logs out, the system asks whether the user wants to unbind the first electronic device from the first user account before the first user account logs out. Therefore, to facilitate the user's unbinding process, an unbinding prompt interface is provided to the user after the user logs out without requiring any user action. This reduces the number of actions the user needs to perform to complete the unbinding process, thereby lowering the response frequency and data processing volume of the first electronic device.

[0028] In one possible implementation of the third aspect, the first electronic device may, in response to the binding maintenance operation performed in the unbinding prompt interface, only log out of the first user account that has been logged into the first electronic device without breaking the binding relationship between the first electronic device and the first user account.

[0029] In the above methods, the identity verification information includes at least one of fingerprint, facial image, voice, and password. Users can choose the appropriate verification method according to their actual situation and use the identity verification information corresponding to the verification method to complete the identity verification. This enriches the verification methods that users can choose and makes it easier for users to verify their identity.

[0030] Fourthly, a device positioning method is provided, which is applied to cloud devices. In this device positioning method, the cloud device receives a device positioning request from a first electronic device and sends a first notification message to a second electronic device logged in with a second user account.

[0031] The first notification information includes the current location of the first electronic device, and the second user account is the account that the first electronic device is bound to.

[0032] Fifthly, a device positioning method is provided, applied to a device positioning system, which includes a cloud device, a first electronic device, and a second electronic device. First, in response to an account input operation, the first electronic device obtains a first user account and a device identifier of the first electronic device, and sends the first user account and device identifier to the cloud device. Second, based on the first user account and device identifier, if it is determined that the first electronic device has been repeatedly bound, the cloud device sends a first notification message to a second device logged in with a second user account. Finally, after receiving the first notification message sent by the cloud device, the second electronic device displays the current location of the first electronic device included in the first notification message.

[0033] The first user account is the user account that needs to be logged into the first electronic device.

[0034] The first notification information is used to inform the user holding the second device of the current location of the first electronic device; the second user account is the account that has been bound to the first electronic device.

[0035] In this way, even if the first electronic device is lost by another user and has been reprogrammed, it is still possible to locate the first electronic device and notify the original user of the first electronic device. This can increase the probability of recovering the lost electronic device, help reduce the probability of loss or leakage of information stored in the electronic device, and thus improve the user experience.

[0036] Sixthly, a device positioning method is provided, applied to a device positioning system, which includes a cloud device, a first electronic device, and a second electronic device. First, in response to an account input operation, the first electronic device obtains a first user account and a device identifier of the first electronic device. Based on the first user account and the device identifier, if it is determined that the first electronic device has been repeatedly bound, it sends a device positioning request to the cloud device. Second, upon receiving the device positioning request, the cloud device sends a first notification message to the second electronic device. Finally, after receiving the first notification message from the cloud device, the second electronic device displays the current location of the first electronic device included in the first notification message.

[0037] The first user account is the user account that needs to be logged into the first electronic device.

[0038] The first notification information includes the current location of the first electronic device and the second user account logged in on the second electronic device. The second user account is the account that has been bound to the first electronic device.

[0039] In this way, even if the first electronic device is lost by another user and has been reprogrammed, it is still possible to locate the first electronic device and notify the original user of the first electronic device. This can increase the probability of recovering the lost electronic device, help reduce the probability of loss or leakage of information stored in the electronic device, and thus improve the user experience.

[0040] A seventh aspect provides an electronic device, the electronic device including a memory and one or more processors; the memory is coupled to the processors; wherein the memory stores computer program code, the computer program code including computer instructions, which, when executed by the processor, cause the electronic device to perform a device positioning method as described in the first aspect and any implementation thereof, or perform a device positioning method as described in the second aspect and any implementation thereof, or perform a device positioning method as described in the third aspect and any implementation thereof, or perform a device positioning method as described in the fourth aspect and any implementation thereof.

[0041] Eighthly, a computer-readable storage medium is provided, including computer instructions that, when executed on an electronic device, cause the electronic device to perform a device positioning method as described in the first aspect and any implementation thereof, or to perform a device positioning method as described in the second aspect and any implementation thereof, or to perform a device positioning method as described in the third aspect and any implementation thereof, or to perform a device positioning method as described in the fourth aspect and any implementation thereof.

[0042] Ninthly, a computer program product is provided, which, when running on an electronic device, causes the electronic device to execute the device positioning method as described in the first aspect and any implementation thereof, or execute the device positioning method as described in the second aspect and any implementation thereof, or execute the device positioning method as described in the third aspect and any implementation thereof, or execute the device positioning method as described in the fourth aspect and any implementation thereof.

[0043] The beneficial effects that the electronic equipment provided in the seventh aspect, the computer-readable storage medium provided in the eighth aspect, and the computer program product provided in the ninth aspect can achieve can be referred to the beneficial effects that can be achieved in the first aspect, the second aspect, the third aspect, the fourth aspect, and any of their implementations, and will not be repeated here. Attached Figure Description

[0044] Figure 1 This illustration shows a schematic diagram of a device positioning scenario provided by an embodiment of this application;

[0045] Figure 2A schematic diagram of a device positioning system provided in an embodiment of this application is shown;

[0046] Figure 3 A schematic diagram of the hardware structure of an electronic device provided in an embodiment of this application is shown;

[0047] Figure 4 A schematic diagram of the software structure of an electronic device provided in an embodiment of this application is shown;

[0048] Figure 5 This illustration shows one of the flowcharts of a device positioning method provided in an embodiment of this application;

[0049] Figure 6 This illustration shows one of the interface diagrams provided in an embodiment of this application;

[0050] Figure 7 This illustration shows a schematic diagram of an authentication interface provided in an embodiment of this application;

[0051] Figure 8 This illustration shows a schematic diagram of an unbinding prompt interface provided in an embodiment of this application;

[0052] Figure 9 This illustration shows a second schematic diagram of an interface provided in an embodiment of this application;

[0053] Figure 10 This illustration shows a second flowchart of a device positioning method provided in an embodiment of this application;

[0054] Figure 11 This illustration shows a schematic diagram of a device processing procedure provided in an embodiment of this application;

[0055] Figure 12 This illustration shows another device processing procedure provided in an embodiment of this application;

[0056] Figure 13 This illustration shows another device processing procedure provided in an embodiment of this application;

[0057] Figure 14 A schematic diagram of the hardware structure of another electronic device provided in an embodiment of this application is shown. Detailed Implementation

[0058] The technical solutions of the embodiments of this application will be described below with reference to the accompanying drawings. In the description of this application, unless otherwise stated, " / " indicates that the objects before and after are in an "or" relationship. For example, A / B can represent A or B. "And / or" in this application is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, and B alone, where A and B can be singular or plural. Furthermore, in the description of this application, unless otherwise stated, "multiple" refers to two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple. Furthermore, to facilitate a clear description of the technical solutions in the embodiments of this application, the terms "first" and "second" are used in the embodiments of this application to distinguish identical or similar items with substantially the same function and effect. Those skilled in the art will understand that the terms "first" and "second" do not limit the quantity or execution order, and that "first" and "second" are not necessarily different. Meanwhile, in the embodiments of this application, the terms "exemplary" or "for example" are used to indicate that something is being used as an example, illustration, or description. Any embodiment or design scheme described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design schemes. Specifically, the use of terms such as "exemplary" or "for example" is intended to present related concepts in a concrete manner for ease of understanding.

[0059] Furthermore, the business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided by the embodiments of this application. As those skilled in the art will know, with the emergence of new business scenarios, the technical solutions provided by the embodiments of this application are also applicable to similar technical problems.

[0060] Currently, mobile phones, tablets, and other electronic devices have penetrated into all aspects of people's lives. As people become more dependent on these devices, they tend to store more information, data, and pictures on them, considering the portability of information. Because people store a large amount of data on electronic devices, the security of electronic devices and assets is receiving increasing attention, and people's demands for recovering lost electronic devices are becoming stronger.

[0061] Given the growing concern for electronic device security, some electronic devices now include a device location function. Users can log in to their accounts to view the current location and historical movement patterns of all electronic devices associated with that account. When a user needs to locate an electronic device, they can use the "Find Device" function to log in to the user account used on the lost device and view the location information of at least one electronic device associated with that account. However, the "Find Device" function only works by relying on the user's logged-in account to locate the lost device; in other words, this method only works if the user account is logged into the lost electronic device.

[0062] For example, when a user uses the "Find My Device" function on another electronic device to locate a lost electronic device, if the lost electronic device is powered on and connected to the internet (e.g., the SIM card can access the internet normally or connect to a valid WLAN), the latest location information of the lost electronic device will be displayed on the interface of the other electronic device used by the user. Figure 1 As shown in (a).

[0063] If the lost electronic device is offline, or if it has been forcibly logged out of the user's account due to being "restored" (removed from the network), other electronic devices used by the user will display the message "Device not connected to the network or powered off, unable to obtain the latest location." Figure 1 As shown in (b), it is evident that the location of the lost electronic device cannot be established at this time, resulting in the loss or leakage of user-stored information on the electronic device, thus affecting the user experience.

[0064] Based on the above, this application provides a device positioning method. When a cloud device receives a device identifier and a first user account sent by a first electronic device, it first verifies whether the first electronic device has been repeatedly bound based on the first user account and the device identifier. Secondly, if the first electronic device has been repeatedly bound, it sends a first notification message to a second electronic device logged into with a second user account to inform the user holding the second electronic device of the current location of the first electronic device. Thus, even if the first electronic device is lost by another user or has been reprogrammed, it can still be located, and the user who previously owned the first electronic device can be notified. This increases the probability of recovering a lost electronic device, helps reduce the probability of loss or leakage of user-stored information in the electronic device, and ultimately improves the user experience.

[0065] Furthermore, when verifying the binding relationship of the first electronic device, the cloud device does not blindly assume that the first electronic device is duplicated simply because it has been previously bound to another user account (i.e., the second user account). Instead, it accurately determines the binding status of the first electronic device (e.g., duplicate binding, normal binding, not bound, etc.) after a detailed comparison of the first and second user accounts. This improves the accuracy of obtaining the binding status and avoids sending incorrect notification messages to the user due to incorrect binding status, thus preventing unnecessary interference with the user's normal usage. The cloud device can also back up the binding information of the first electronic device to ensure its security during subsequent use.

[0066] The device positioning method provided in this application can be applied to a device positioning system. For example, as shown in the embodiments... Figure 2 As shown, the device positioning system includes electronic devices and cloud devices 200. The electronic devices include a first electronic device 100a and a second electronic device 100b. The first electronic device 100a can be a mobile or portable device such as a mobile phone, tablet computer, headphones (e.g., wired headphones, Bluetooth headphones, etc.), head-mounted display devices (e.g., virtual reality devices, augmented reality devices, mixed display devices), or laptop computer; wherein, the mobile phone can be a foldable screen phone or a non-foldable screen phone.

[0067] The second electronic device 100b can be a mobile or portable device such as a mobile phone, tablet computer, headphones (e.g., wired headphones, Bluetooth headphones, etc.), head-mounted display device (e.g., virtual reality device, augmented reality device, mixed display device), or laptop computer; it can also be a terminal device such as a smart home device (e.g., a television set) or an in-vehicle system (e.g., an in-vehicle terminal).

[0068] When a user enters the first user account they are using into the first electronic device 100a, both the first electronic device 100a in the device positioning system and the cloud device 200 can verify whether the first electronic device 100a has been repeatedly bound.

[0069] In some examples, considering the large amount of data that the cloud device needs to process, frequent requests to the cloud device to verify the binding status of the first electronic device will put pressure on the data processing of the cloud device.

[0070] Therefore, if the binding information is stored in the local information of the first electronic device 100a, the first electronic device 100a can be used to perform repeated binding verification first.

[0071] In other examples, if no binding information is recorded in the first electronic device 100a, or if the first electronic device 100a is determined to be unbound to a user account, the first electronic device 100a sends the device identifier and the first user account to the cloud device 200 to perform repeated binding verification through the cloud device 200.

[0072] In some implementations, when repeated binding authentication of the first electronic device 100a is required through the cloud device 200, the first electronic device 100a sends its unique device identifier and the first user account entered by the user through the account input operation to the cloud device 200 to request the backup of the binding information between the first electronic device 100a and the first user account in the cloud device 200.

[0073] After receiving the device identifier and the first user account sent by the first electronic device 100a, the cloud device 200 first uses the received first user account and device identifier to verify whether the first electronic device 100a has been bound to a second user account in the past usage process; that is, by determining whether the first electronic device has a previously bound second user account, it determines whether the first electronic device 100a has been bound repeatedly.

[0074] Secondly, if it is verified that the first electronic device 100a has been repeatedly bound, a first notification message is sent to the second electronic device 100b, which is logged in with a second user account, so as to indicate the current location of the first electronic device 100a held by the second electronic device 100b.

[0075] After receiving the first notification information sent by the cloud device 200, the second electronic device 100b displays the first notification information to inform the user holding the second electronic device 100b of the current location of the first electronic device 100a.

[0076] If the cloud device 200 verifies that the first electronic device 100a has been repeatedly bound, it can also send a second notification message to the first electronic device 100a to notify the user holding the first electronic device 100a that the first electronic device 100a cannot be bound to the first user account.

[0077] After receiving the second notification information from the cloud device 200, the first electronic device 100a displays the received second notification information.

[0078] In other embodiments, when the first electronic device 100a can perform repeated binding authentication based on the stored local information, the first electronic device 100a first responds to the account input operation performed by the user and obtains the unique device identifier of the first electronic device and the first user account entered by the user through the account input operation.

[0079] Secondly, based on the received first user account and device identifier, it is verified whether the first electronic device 100a has been bound to the second user account during its historical use; that is, by determining whether the first electronic device 100a has been previously bound to the second user account, it is determined whether the first electronic device 100a has been repeatedly bound.

[0080] Finally, after verifying that the first electronic device 100a has been repeatedly bound, a device location request is sent to the cloud device 200.

[0081] After receiving a device location request from the first electronic device 100a, the cloud device 200 sends a first notification message to the second electronic device 100b, which is logged into a second user account, to inform the second electronic device 100b of the current location of the first electronic device 100a held by the user.

[0082] After receiving the first notification information sent by the cloud device 200, the second electronic device 100b displays the first notification information to inform the user holding the second electronic device 100b of the current location of the first electronic device 100a.

[0083] The device positioning method provided in this application, involving the electronic device 100 (e.g., a first electronic device or a second electronic device), can be found in [reference needed]. Figure 3 As shown. The electronic device 100 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, antenna 1, antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a sensor module 180, buttons 190, a motor 191, a camera 192, a display screen 193, and a subscriber identification module (SIM) card interface 194, etc. The sensor module 180 may include a pressure sensor 180A, a fingerprint sensor 180B, a touch sensor 180C, etc.

[0084] It is understood that the structures illustrated in the embodiments of this application do not constitute a specific limitation on the electronic device 100. In other embodiments of this application, the electronic device 100 may include more or fewer components than illustrated, or combine some components, or split some components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0085] Processor 110 may include one or more processing units, such as: application processor (AP), modem processor, graphics processing unit (GPU), image signal processor (ISP), controller, memory, video codec, digital signal processor (DSP), baseband processor, and / or neural network processing unit (NPU), etc. Different processing units may be independent devices or integrated into one or more processors.

[0086] In some embodiments, the electronic device 100 may implement the above-described device positioning method through the processor 110.

[0087] The processor 110 may also include a memory for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. This memory can store instructions or data that the processor 110 has just used or that are used repeatedly. If the processor 110 needs to use the instruction or data again, it can retrieve it directly from the memory. This avoids repeated accesses, reduces the waiting time of the processor 110, and thus improves the efficiency of the system.

[0088] Electronic device 100 implements display functions through a GPU, display screen 193, and application processor. The GPU is a microprocessor for image processing, connected to the display screen 193 and the application processor. The GPU performs mathematical and geometric calculations for graphics rendering. Processor 110 may include one or more GPUs, which execute program instructions to generate or modify display information. Display screen 193 is used to display images, videos, etc. Display screen 193 includes a display panel.

[0089] In some embodiments, processor 110 may include one or more interfaces ( Figure 3(Not shown in the image). For example, USB interface 130 is an interface conforming to the USB standard specification, specifically a Mini USB interface, Micro USB interface, USB Type-C interface, etc. USB interface 130 can be used to connect a charger to charge electronic device 100, and can also be used for data transfer between electronic device 100 and peripheral devices. It can also be used to connect headphones for audio playback. This interface can also be used to connect other electronic devices, such as AR devices.

[0090] The charging management module 140 is used to receive charging input from the charger. The charger can be a wireless charger or a wired charger.

[0091] 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 power the processor 110, internal memory 121, external memory, display 193, camera 192, and wireless communication module 160, etc.

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

[0093] Antennas 1 and 2 are used to transmit and receive electromagnetic wave signals. The mobile communication module 150 can provide wireless communication solutions, including 2G / 3G / 4G / 5G, for use on the electronic device 100. The mobile communication module 150 can receive electromagnetic waves via antenna 1, and perform filtering, amplification, and other processing on the received electromagnetic waves before transmitting them to a modem processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modem processor and convert it into electromagnetic waves for radiation via antenna 1.

[0094] The wireless communication module 160 can provide solutions for wireless communication applications on the electronic device 100, including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), and infrared (IR) technologies. The wireless communication module 160 receives electromagnetic waves via antenna 2, modulates and filters the electromagnetic wave signals, and sends the processed signal to processor 110. The wireless communication module 160 can also receive signals to be transmitted from processor 110, modulate and amplify them, and then convert them into electromagnetic waves for radiation via antenna 2.

[0095] In some embodiments, antenna 1 of electronic device 100 is coupled to mobile communication module 150, and antenna 2 is coupled to wireless communication module 160, so that electronic device 100 can communicate with networks and other devices through wireless communication technology.

[0096] In some possible implementations, the electronic device 100 can display a first notification message and a second notification message on the display screen 193. The first notification message indicates the current location of the first electronic device to the user holding the second electronic device; the second user account is the account already bound to the first electronic device. The electronic device 100 can also display an unbinding prompt interface, an identity verification interface, etc., on the display screen 193, allowing the user to complete the binding relationship between the first electronic device and the first user account through the unbinding prompt interface, and to complete user identity verification through the identity verification interface.

[0097] It is understood that the display screen 193 mentioned herein can serve as the screen in the following embodiments.

[0098] Electronic device 100 can perform shooting functions through ISP, camera 192, video codec, GPU, display 193 and application processor.

[0099] The audio module 170 (e.g., a microphone), sensor module 180 (e.g., a pressure sensor 180A, a fingerprint sensor 180B, a touch sensor 180C), button 190, and camera 192 are used to acquire authentication information entered by the user.

[0100] A digital signal processor (DSP) is used to process digital signals, including digital image signals and other digital signals. A video codec is used to compress or decompress digital video. An NPU (Neural Processing Unit) is a neural network (NN) computing processor that, by borrowing the structure of biological neural networks, such as the transmission patterns between neurons in the human brain, rapidly processes input information and can continuously learn. NPUs enable intelligent cognitive applications in electronic devices, such as image recognition, speech recognition, and text understanding.

[0101] 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 perform data storage functions.

[0102] Internal memory 121 can be used to store computer executable program code, which includes instructions. Processor 110 executes various functional applications and data processing of electronic device 100 by running the instructions stored in internal memory 121. Internal memory 121 may include a program storage area and a data storage area. The program storage area may store the operating system, at least one application program required for a function (such as sound playback, image playback, etc.), etc. The data storage area may store data created during the use of electronic device 100 (such as audio data, phonebook, etc.). Furthermore, internal memory 121 may include high-speed random access memory and may also include non-volatile memory, such as at least one disk storage device, flash memory device, universal flash storage (UFS), etc.

[0103] In some possible implementations, the electronic device 100 may also store the binding information between the electronic device and the user account through the internal memory 121.

[0104] Electronic device 100 can implement audio functions through audio module 170 and application processor, such as music playback and recording. Audio module 170 is used to convert digital audio information into analog audio signals for output, and also to convert analog audio input into digital audio signals. Audio module 170 can also be used for encoding and decoding audio signals.

[0105] Buttons 190 include a power button, volume buttons, etc. Buttons 190 can be mechanical buttons or touch-sensitive buttons. Motor 191 can generate vibration alerts. Motor 191 can be used for information vibration alerts or for touch vibration feedback.

[0106] In some embodiments, such as Figure 4As shown, the electronic device 100 (e.g., the first electronic device or the second electronic device) can also adopt a layered architecture, event-driven architecture, microkernel architecture, microservice architecture, or cloud architecture. This application embodiment uses a layered architecture mobile operating system as an example to exemplify the software structure of the electronic device 100.

[0107] like Figure 4 As shown, 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 mobile operating system is divided into four layers, from top to bottom: the application layer, the application framework layer, the system service layer, and the kernel layer.

[0108] The application layer can include a series of application packages.

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

[0110] The application framework layer provides application programming interfaces (APIs) and a programming framework for applications in the application layer. The application framework layer includes some predefined functions.

[0111] like Figure 4 As shown, the application framework layer may include a window manager, content provider, view system, phone manager, resource manager, notification manager, etc.

[0112] The view system includes visual controls, such as controls for displaying text and controls for displaying images. The view system can be used to build applications. The display interface can consist of one or more views.

[0113] The system service layer can include multiple functional modules. For example: surface manager, media libraries, 3D graphics processing libraries (e.g., OpenGL ES), 2D graphics engines (e.g., SGL), etc.

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

[0115] In some embodiments, the cloud device 200 involved in the device positioning method provided in this application may have the same structure and / or hierarchical architecture as the electronic device 100. Compared with the electronic device 100, the cloud device 200 may not need to be configured with audio module 170, sensor module 180, button 190, motor 191, camera 192, display screen 193, etc., but in the actual process of data processing, it can achieve the same effect as the electronic device 100.

[0116] The following describes the device positioning method provided in the embodiments of this application, taking mobile phone 1 as the first electronic device, mobile phone 2 as the second electronic device, and server as the cloud device. In some embodiments, such as Figure 5 As shown, the method may include the following steps S501-S504.

[0117] S501, Mobile Phone 1 sends the device identifier and the first user account to the server.

[0118] When a user enters a first user account on mobile phone 1, mobile phone 1 will use the stored "local information" to verify whether it has a previously bound user account; then, if mobile phone 1 has not bound a user account, the binding between mobile phone 1 and the first user account will be triggered.

[0119] Meanwhile, in order to synchronize the binding information on the server side, mobile phone 1 will send the first user account and the device identifier that uniquely identifies mobile phone 1 to the server, so as to record the binding information between mobile phone 1 and the first user account on the server side.

[0120] The first user account can be the user's mobile phone number, the user's ID card number, the user's email address, or the user's registered account ID, etc.

[0121] In some embodiments, the device identifier is used to uniquely identify mobile phone 1; that is, any unique code in mobile phone 1 can be used as the device identifier of mobile phone 1. For example, the device identifier includes at least one of the following: the device serial number (SN) of mobile phone 1, the device identification code (IMEI) of mobile phone 1, and the chip number of the built-in chip in mobile phone 1.

[0122] The above-mentioned user entering the first user account on mobile phone 1 can refer to the user entering the first user account on the account login interface provided on the interface of mobile phone 1; it can also refer to the user entering the first user account in the application software (or built-in application software) downloaded on mobile phone 1, etc.

[0123] One user account can be bound to the device identifiers of multiple electronic devices, while the device identifier of an electronic device can only be bound to one user account at a time.

[0124] For example, when a user logs into a mobile phone using the first account ID, mobile phone 1 retrieves the second account ID previously bound to the phone by querying the stored "local information". If the second account ID of the phone is not found in the "local information", it is determined that the phone is not bound to a user account. At this time, the binding operation between the phone and the first account ID is automatically triggered, and the phone's SN number and the first account ID are synchronized to the cloud device. The binding information of the phone has been "recorded" in the cloud device. Therefore, the phone will send its own device identifier and the first user account to the cloud device to realize the synchronization of the binding information of the first electronic device.

[0125] S502. The server receives the device identifier and the first user account sent by mobile phone 1 and triggers the execution of the mobile phone 1 binding status authentication operation; that is, when the server receives the device identifier and the first user account of mobile phone 1, it will verify whether the first electronic device has been bound repeatedly.

[0126] The first user account is the user account that requests to bind with mobile phone 1. Here, when the user enters the first user account into mobile phone 1, if the binding information of mobile phone 1 cannot be obtained in the "local information" of mobile phone 1, then the first user account is considered to be the user account that requests to bind with mobile phone 1.

[0127] S503. Based on the received first user account and device identifier of mobile phone 1, the server determines whether mobile phone 1 has been duplicated by checking if a second user account has been previously bound to it. If mobile phone 1 has been duplicated, a first notification message is sent to mobile phone 2, which is logged in with the second user account, to indicate the current location of mobile phone 1 held by mobile phone 2 by displaying the first notification message on mobile phone 2.

[0128] The first notification information is used to inform the user holding the second electronic device of the current location of the first electronic device; the second user account is the account that has been bound to the first electronic device.

[0129] This application's embodiments consider a scenario where a user previously logged out of their first user account on phone 1. Entering that first user account again on phone 1 constitutes a second login. In other words, the second user account bound to phone 1 is actually the same account as the first user account used for this login. If, based solely on obtaining the second user account, one blindly concludes that phone 1 has been repeatedly bound, it will lead to an incorrect assessment of phone 1's binding status. Consequently, incorrect notifications will be sent to the user, unnecessarily interfering with their normal usage.

[0130] In some implementations, when the server determines that mobile phone 1 has been repeatedly bound based on the first user account and the device identifier, the server obtains the second user account that mobile phone 1 was previously bound to based on the device identifier; if the first user account sent by mobile phone 1 is inconsistent with the second user account obtained by the server, it is determined that mobile phone 1 has been repeatedly bound.

[0131] Here, the server retrieves a second user account that is bound to the device identifier of mobile phone 1 from the binding information already stored on the server (or the binding information already stored on other storage devices); that is, it retrieves the second user account that mobile phone 1 was previously bound to.

[0132] If the server obtains the second user account that was previously bound to mobile phone 1, and this second user account is different from the first user account currently entered by the user, it means that mobile phone 1 has already established a binding relationship with the second user account. At this time, binding it with the first user account will cause mobile phone 1 to be bound repeatedly. Therefore, it can be determined that mobile phone 1 has been bound repeatedly.

[0133] For example, the server uses the SN number of mobile phone 1 to query the stored binding information. If the server obtains a second account ID that has been bound to the SN number of mobile phone 1, and the first account ID is inconsistent with the second account ID, it means that the binding of mobile phone to the first account ID is a duplicate binding of mobile phone 1. At this time, it can be determined that mobile phone 1 has been bound repeatedly.

[0134] As can be seen, in this embodiment of the application, when the server verifies the binding relationship of the first mobile phone 1, it does not simply use whether it obtains other user accounts (i.e., the second user account) that the mobile phone 1 was previously bound to as the basis for judgment and blindly determine that the first electronic device has a duplicate binding situation. Instead, after comparing the first user account and the second user account in detail, it accurately determines the binding status of the mobile phone 1 (e.g., duplicate binding, normal binding, not bound, etc.), thereby improving the accuracy of obtaining the binding status and avoiding incorrect notification messages fed back to the user due to incorrect acquisition of the binding status, which would cause unnecessary interference to the user's normal use process.

[0135] S504, The second electronic device receives and displays the first notification information.

[0136] For example, after receiving the first notification information sent by the cloud device, the second electronic device can parse the first notification information and display its current location as shown in the image. Figure 6 On the page shown.

[0137] In the device positioning method shown in S501-S504 above, the server can use the obtained device identifier of mobile phone 1 and the first user account to verify whether mobile phone 1 has been bound. Then, if mobile phone 1 is bound repeatedly, a first notification message is sent to mobile phone 2 logged in by the second user account that mobile phone 1 was previously bound to, so as to notify the user of the second user account of the current location of mobile phone 1 through the first notification message. In this way, even if mobile phone 1 is "flashed", it can still be located, which can improve the probability of finding lost mobile phone 1 and help reduce the probability of loss or leakage of information stored by the user on mobile phone 1, thereby improving the user experience.

[0138] In some implementations, if the server determines that the first user account and the second user account are the same when comparing the first user account with the second user account, then the server determines that mobile phone 1 is normally bound; that is, the first user account is the user account that was previously bound to mobile phone 1, and this time, the user enters the first user account on mobile phone 1, which is only a second login of the first user account on mobile phone 1.

[0139] Then, once the server determines that mobile phone 1 is properly bound, in response to receiving the account unbinding instruction sent by mobile phone 1, the server deletes the binding information about mobile phone 1 stored therein, so as to simultaneously unbind mobile phone 1 from the first user account on both mobile phone 1 and the server.

[0140] The binding information is used to indicate that mobile phone 1 has been bound to the first user account. The binding information includes at least the device identifier of mobile phone 1 and the first user account.

[0141] For example, the binding information of mobile phone 1 can be expressed as: "SN number of mobile phone 1 + first account ID (or second account ID)"; or it can be expressed as "the SN number and first account ID of mobile phone 1 were bound on XXX year XX month X day".

[0142] The account unbinding instruction may include the device identifier of the mobile phone 1 to be unbound, so that the electronic device to be unbound is identified as mobile phone 1 in the account unbinding instruction.

[0143] For example, a user triggers an account unbinding command to the server via mobile phone 1. Mobile phone 1 sends the account unbinding command to the server. The server obtains the saved binding information of mobile phone 1 (including the SN number of mobile phone 1 and the first user ID bound to it) by recognizing the device identifier carried in the account unbinding command, and deletes the binding information of mobile phone 1. In this way, the unbinding of mobile phone 1 is completed on the server side.

[0144] During the use of mobile phone 1, the user can send an account unbinding command to the server at any time to unbind the binding relationship between mobile phone 1 and the first user account. In some implementations, the user can use at least two methods to trigger account unbinding and generate the account unbinding command: First, the user can actively trigger account unbinding to actively unbind the binding relationship between mobile phone 1 and the first user account; Second, the user can trigger the unbinding relationship between mobile phone 1 and the first user account when logging out of the first user account.

[0145] In some implementations, if a user chooses to actively trigger the unbinding of mobile phone 1 from the first user account, and mobile phone 1 is already normally bound, mobile phone 1 will first respond to the user's account unbinding operation by displaying the following... Figure 7 The authentication interface shown is used to authenticate the user requesting unbinding, thereby preventing mobile phone 1 from being forcibly unbound by other users.

[0146] Secondly, mobile phone 1 obtains the authentication information entered by the user on the authentication interface.

[0147] Finally, if the user's authentication information successfully passes verification, the binding relationship between mobile phone 1 and the first user account is unbound, the binding information about mobile phone 1 stored in mobile phone 1's "local information" is deleted, and an account unbinding command is generated and sent to the server. This command requests the server to synchronously delete the binding information of mobile phone 1 stored on the server. In this way, synchronous unbinding between the server and mobile phone 1 is achieved.

[0148] The account unbinding instruction is used to request the deletion of the binding information of mobile phone 1 that has been saved on the server; the binding information is used to indicate that mobile phone 1 has been bound to the first user account.

[0149] In other embodiments, if the unbinding of mobile phone 1 from the first user account is triggered when the user logs out, and mobile phone 1 is normally bound, firstly, the first electronic device responds to the user's account logout operation by displaying the following on the interface: Figure 8 The unbinding prompt interface shown asks the user whether they want to unbind the first electronic device from the first user account.

[0150] Secondly, if the user chooses to unbind the mobile phone number 1 from the first user account, the system will respond to the account unbinding operation performed by the user on the unbinding prompt screen, displaying the following: Figure 7 The authentication interface shown is used to authenticate the user requesting to unbind, thereby preventing the user from being forcibly unbound by other users.

[0151] Then, mobile phone 1 obtains the authentication information (e.g., password and / or biometrics) entered by the user on the authentication interface.

[0152] Finally, if the user's entered authentication information successfully passes authentication, the binding relationship between mobile phone 1 and the first user account is unbound, the binding information saved in mobile phone 1's "local information" is deleted, and an account unbinding command is generated and sent to the server. This command requests the server to synchronously delete the binding information of mobile phone 1 stored on the server. At the same time, mobile phone 1 logs out of the first user account it has logged into.

[0153] This avoids the binding relationship between the mobile phone and the first user account affecting other user accounts when the first user account logs out and the mobile phone 1 logs in to use the phone. Furthermore, the unbinding prompt interface is automatically triggered during the login process, so that the binding relationship is unbound without the user having to perform any operation. This reduces the operations that the user needs to perform to complete the unbinding, thereby reducing the response frequency and data processing volume of the first electronic device.

[0154] In other embodiments, if a user triggers a factory reset, and phone 1 is normally bound, the first electronic device first responds to the factory reset operation performed by the user by displaying, as shown below. Figure 8 The unbinding prompt interface shown asks the user whether they want to unbind the first electronic device from the first user account.

[0155] Secondly, if the user chooses to unbind the mobile phone number 1 from the first user account, the system will respond to the account unbinding operation performed by the user on the unbinding prompt screen, displaying the following: Figure 7 The authentication interface shown is used to authenticate the user requesting to unbind, thereby preventing the user from being forcibly unbound by other users.

[0156] Then, mobile phone 1 obtains the authentication information (e.g., password and / or biometrics) entered by the user on the authentication interface.

[0157] Finally, if the user's authentication information is successfully verified, the binding relationship between mobile phone 1 and the first user account is unbound, the binding information saved in the "local information" of mobile phone 1 is deleted, and an account unbinding command is generated and sent to the server. The account unbinding command is sent to the server to request the server to synchronously delete the binding information of mobile phone 1 saved on the server. At the same time, mobile phone 1 is restored to factory settings.

[0158] This avoids the binding relationship between the phone and the first user account affecting other user accounts when the phone is logged into other user accounts after a factory reset. Furthermore, the unbinding prompt interface is automatically triggered during the factory reset, without requiring any user action to trigger the unbinding process. This reduces the number of operations required for the user to complete the unbinding, thereby lowering the response frequency and data processing volume of the first electronic device.

[0159] The authentication information entered by the user on the authentication interface includes at least one of biometrics or a password; biometrics may include fingerprints, facial images, voice, etc.

[0160] For example, a user can register their fingerprint using a fingerprint sensor to complete identity verification according to the instructions on the identity verification interface; or, a user can register their facial image using a camera to complete identity verification according to the instructions on the identity verification interface; or, a user can register their voice using a microphone to complete identity verification according to the instructions on the identity verification interface; or, a user can enter their password using a virtual keyboard (or physical keyboard) displayed on the identity verification interface to complete identity verification.

[0161] In some implementations, after the unbinding prompt interface is displayed, the first electronic device responds to the binding maintenance operation performed by the user in the unbinding prompt interface, and continues to save the binding information of the first electronic device in "local information" while maintaining the binding relationship between the first electronic device and the first user account, and only logs out of the logged-in first user account in the first electronic device.

[0162] In some embodiments, if the server does not obtain the second user account bound to mobile phone 1, it is determined that mobile phone 1 is not bound; further, if the server determines that mobile phone 1 is not bound, the server performs the binding operation of the device identifier associated with mobile phone 1 and the first user account, generates and saves the binding information of mobile phone 1, so that in the subsequent use of mobile phone 1, the binding information can indicate that mobile phone 1 has been bound.

[0163] For example, mobile phone 1 used by a user authenticated by the server is not currently bound to any user account. In other words, mobile phone 1 is in an unbound state. When the user logs in to mobile phone 1 using the first account ID, it will by default request to bind the first account ID to the SN number of mobile phone 1. At this time, the server combines the first account ID and the SN number of the mobile phone to generate and store the binding information of mobile phone 1 (for example, the binding information of mobile phone 1 is: SN number of mobile phone 1 + first account ID) so as to realize the synchronization of the binding information of mobile phone 1 on the server side.

[0164] In this way, when mobile phone 1 is used for the first time, since mobile phone 1 is not bound to any user account, if the first user account requests to bind with mobile phone 1 (for example, the first user account tries to log in to mobile phone 1), the server can back up the binding information between the first electronic device and the first user account when it receives the device identifier of mobile phone 1 and the first user account, so as to use the binding information of mobile phone 1 to ensure the security of mobile phone 1 in subsequent use.

[0165] In some embodiments, if the server-authenticated mobile phone 1 is repeatedly bound, the server sends a second notification message to the first electronic device to inform the user that the mobile phone 1 used by the user cannot be bound to the first user account entered by the user; if the user enters the first user account in the form of login in the mobile phone 1, the second notification message is also used to indicate that the first user account cannot log in to the mobile phone 1.

[0166] For example, when the server verifies that the SN number of mobile phone 1 used by the user is already bound to a second account ID, the server sends a second notification message to mobile phone 1, indicating that the SN number of the mobile phone is already bound to the second account ID (another account ID) and cannot be bound to the first account ID, thus the login with the first account ID fails. At this time, the interface of mobile phone 1 will display "This device has been bound. Please unbind it before logging into a new account" (e.g., ...). Figure 9 (As shown).

[0167] The second notification message is used to indicate that the first user account failed to be bound to mobile phone 1.

[0168] The following description uses an example where the first electronic device is mobile phone 1, the second electronic device is mobile phone 2, and the cloud device is a server to illustrate another device positioning method provided in this application embodiment. Figure 10 As shown, the method may include the following steps S1001-S1004.

[0169] S1001, Mobile phone 1 responds to the account input operation performed by the user and obtains the first user account and device identifier of mobile phone 1 entered by the user through the account input operation.

[0170] The first user account is the user account to be logged into mobile phone 1. In some implementations, the first user account entered into mobile phone 1 can be regarded as the user account to be logged into mobile phone 1 in at least two cases: first, the user enters the first user account in the account login interface provided on the interface of mobile phone 1; second, the user enters the first user account in the application software (or built-in application software) downloaded on mobile phone 1, etc.; that is to say, as long as the user enters the first user account on mobile phone 1 without logging into any user account, the first user account entered by the user can be regarded as the user account to be logged into mobile phone 1.

[0171] S1002, Mobile Phone 1, using the obtained first user account and device identifier, queries the "local information" stored in the device to determine whether it has a bound second user account, thus verifying whether it has been duplicated. If Mobile Phone 1 verifies that it has been duplicated, it sends a device location request to the server. This request requests the server to send a first notification message to Mobile Phone 2, which is logged into with the second user account. In this way, the first notification message informs Mobile Phone 2 of the current location of Mobile Phone 1, the user's mobile phone.

[0172] The device location request is used to request the server to send a first notification message to the receiving mobile phone 2. The first notification message includes the current location of mobile phone 1 and that a second user account is logged in on mobile phone 2. The second user account is the user account that mobile phone 1 was previously bound to.

[0173] S1003. The server receives the device location request from mobile phone 1 and sends the first notification information to mobile phone 2, which is logged in with a second user account.

[0174] S1004, The second electronic device receives and displays the first notification information.

[0175] The device positioning method shown in S1001-S1004 above involves mobile phone 1 using the obtained device identifier and first user account to verify whether it has been bound. If mobile phone 1 is bound repeatedly, it sends a device positioning request to the server, which then sends a first notification message to mobile phone 2, which is logged in by the second user account previously bound to mobile phone 1. The first notification message then informs the user of the second user account of the current location of mobile phone 1. This increases the probability of recovering lost electronic devices and helps reduce the probability of loss or leakage of user-stored information in electronic devices, thereby improving the user experience.

[0176] In some implementations, the process of verifying whether mobile phone 1 has been repeatedly bound by querying the second user account stored in the "local information" of mobile phone 1, and the process of mobile phone 1 triggering account unbinding, are the same as the repeated binding verification process and account unbinding process mentioned in the above implementations, and will not be described again here.

[0177] The following combination Figure 11 The process of logging out / unbinding an account should be explained. For example... Figure 11 As shown, when a user enters a first user account on mobile phone 1, the binding of the first user account and mobile phone 1 is triggered. Mobile phone 1 stores the binding information locally and on the server. If the user wants to log out / unbind the first user account while it is already logged in on mobile phone 1, an unbinding prompt interface is provided on the interface of mobile phone 1 before logging out / unbinding, asking the user whether to unbind mobile phone 1 and the first user account. If so, the user's identity is verified using a password and / or biometrics (e.g., fingerprint). If the user passes the identity verification, the binding relationship between mobile phone 1 and the first user account is released and / or the login of the first user account is exited. The binding information stored locally and on the server is deleted.

[0178] The following combination Figure 12 The process of repeatedly binding and authenticating mobile phone 1 based on the saved local information is explained. For example... Figure 12As shown, when a user enters a first user account on mobile phone 1, mobile phone 1 determines, based on local information, whether the first user account is the same user account bound to mobile phone 1. If yes, the user logs in to the first user account on mobile phone 1. If no, a message is displayed indicating that mobile phone 1 is already bound. At this point, an unbinding prompt interface can be provided to the user on the interface of mobile phone 1 to ask if the user wants to unbind mobile phone 1 and the first user account. If yes, the user's identity is verified using a password and / or biometrics (e.g., fingerprint). If the user passes the identity verification, the binding relationship between mobile phone 1 and the first user account is removed and / or the user is logged out of the first user account. The binding information stored locally and on the server is deleted. After unbinding, the user can log in to a new account (i.e., the first user account that was previously not successfully logged in).

[0179] The following combination Figure 13 The process of the server performing repeated binding authentication based on the saved binding information is explained below. For example... Figure 13 As shown, the user enters the first user account on mobile phone 1, triggering the binding of the first user account with mobile phone 1; the device identifier of mobile phone 1 and the first user account entered by the user are sent to the server; the server uses the device identifier and the first user account to verify the historical binding of mobile phone 1. When the server determines that mobile phone 1 has been bound repeatedly (that is, the first user account is inconsistent with the second user account previously bound to mobile phone 1), the server reports the current location of mobile phone 1 to mobile phone 2 to indicate that the user holding the mobile phone, mobile phone 1, is requesting to bind another user account.

[0180] The technical solutions disclosed in this application involve the collection, storage, use, processing, transmission, provision, and disclosure of user personal information, all of which comply with relevant laws and regulations and do not violate public order and good morals. User personal information includes, but is not limited to, fingerprints, facial images, voice, or passwords.

[0181] It is understood that, in order to achieve the above functions, the aforementioned electronic device includes hardware and / or software modules corresponding to perform each function. Based on the algorithmic steps of the various examples described in conjunction with the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application in conjunction with the embodiments, but such implementation should not be considered beyond the scope of this application.

[0182] This application embodiment can divide the electronic device into functional modules according to the above method example. For example, each function can be divided into its own functional module, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware. It should be noted that the module division in this embodiment is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods.

[0183] This application also provides an electronic device, such as... Figure 14 As shown, the electronic device may include one or more processors 1401, memory 1402 and communication interface 1403.

[0184] The memory 1402, communication interface 1403, and processor 1401 are coupled together. For example, the memory 1402, communication interface 1403, and processor 1401 can be coupled together via bus 1404.

[0185] The communication interface 1403 is used for data transmission with other devices. The memory 1402 stores computer program code. The computer program code includes computer instructions, which, when executed by the processor 1401, cause the electronic device to perform the login method described in this embodiment.

[0186] The processor 1401 may be a processor or controller, such as a central processing unit (CPU), a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute the various exemplary logic blocks, modules, and circuits described in connection with this disclosure. The processor may also be a combination that implements computational functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, etc.

[0187] The bus 1404 can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. The bus 1404 can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 14 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0188] This application also provides a computer-readable storage medium storing computer program code. When the processor executes the computer program code, the electronic device executes the relevant method steps in the above method embodiments.

[0189] The electronic devices and computer storage media provided in this application are used to execute the corresponding methods provided above. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects of the corresponding methods provided above, and will not be repeated here.

[0190] Through the above description of the embodiments, those skilled in the art can clearly understand that, for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

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

[0192] The units described as separate components may or may not be physically separate. A component shown as a unit can be one or more physical units; that is, it can be located in one place or distributed in multiple different locations. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0193] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0194] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solution of the embodiments of this application, in essence, or the part that contributes, or all or part of the technical solution, can be embodied in the form of a software product. This software product is stored in a storage medium and includes several instructions to cause a device (which may be a microcontroller, chip, etc.) or processor to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0195] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for positioning equipment, characterized in that, Applied to cloud devices, the method includes: The device identifier and the first user account sent by the first electronic device are received; wherein, the first user account is the user account that requests to bind with the first electronic device. If, based on the first user account and the device identifier, it is determined that the first electronic device has been repeatedly bound, a first notification message is sent to the second electronic device logged in with the second user account; wherein, the first notification message is used to indicate the current location of the user holding the second electronic device to the first electronic device; the second user account is the account that the first electronic device has been bound to.

2. The method according to claim 1, characterized in that, The step of determining that the first electronic device has been repeatedly bound based on the first user account and the device identifier includes: Based on the device identifier, obtain the second user account that is already bound to the first electronic device; If the first user account and the second user account are different, it is determined that the first electronic device has been bound repeatedly.

3. The method according to claim 2, characterized in that, The method further includes: If the first user account is the same as the second user account, it is determined that the first electronic device has been successfully bound. If it is determined that the first electronic device is properly bound, an account unbinding instruction for the first electronic device is received, and the binding information of the first electronic device is deleted; wherein, the binding information is used to indicate that the first electronic device has been bound to the first user account.

4. The method according to claim 2, characterized in that, The method further includes: If a second user account bound to the first electronic device is not obtained, it is determined that the first electronic device is not bound. If it is determined that the first electronic device is not bound, the device identifier is associated with the first user account to generate binding information for the first electronic device, and the binding information for the first electronic device is saved; wherein, the binding information is used to indicate that the first electronic device has been bound to the first user account.

5. The method according to any one of claims 1-4, characterized in that, The device identifier includes at least one of the device serial number, device identification code, and device chip number of the first electronic device; the device identifier is used to uniquely identify the first electronic device.

6. The method according to any one of claims 1-5, characterized in that, If it is determined that the first electronic device has been repeatedly bound, the method further includes: Send a second notification message to the first electronic device; wherein the second notification message is used to indicate that the first user account failed to bind to the first electronic device.

7. A method for positioning equipment, characterized in that, Applied to a first electronic device, the method includes: In response to an account input operation, the system obtains a first user account and a device identifier of the first electronic device; wherein, the first user account is the user account to be logged into the first electronic device. Based on the first user account and the device identifier, if it is determined that the first electronic device is repeatedly bound, a device location request is sent to the cloud device; wherein, the device location request is used to request the cloud device to send a first notification information to the second electronic device, the first notification information including the current location of the first electronic device, and a second user account logged in on the second electronic device, the second user account being the account already bound to the first electronic device.

8. The method according to claim 7, characterized in that, If it is determined that the first electronic device is properly bound, the method further includes: In response to the account unbinding operation, the identity verification interface is displayed; Obtain the authentication information entered by the user on the authentication interface; If the identity verification information is verified, the first electronic device is unbound from the first user account, the binding information of the first electronic device is deleted, and an account unbinding instruction is sent to the cloud device; wherein, the account unbinding instruction is used to request the deletion of the binding information of the first electronic device already saved in the cloud device; the binding information is used to indicate that the first electronic device has been bound to the first user account.

9. The method according to claim 7, characterized in that, If it is determined that the first electronic device is properly bound, the method further includes: In response to an account logout, an unbinding prompt interface will be displayed; In response to the user's account unbinding operation performed on the unbinding prompt interface, the identity verification interface is displayed; Obtain the authentication information entered by the user on the authentication interface; If the identity verification information is verified, the binding between the first electronic device and the first user account is unbound, the binding information of the first electronic device is deleted, and an account unbinding instruction is sent to the cloud device, as well as the first user account that has logged into the first electronic device is logged out; wherein, the account unbinding instruction is used to request the deletion of the binding information of the first electronic device that has been saved in the cloud device; the binding information is used to indicate that the first electronic device has been bound to the first user account.

10. The method according to claim 9, characterized in that, After displaying the unbinding prompt interface, the method further includes: In response to the binding maintenance operation performed by the user on the unbinding prompt interface, the first user account that has been logged into the first electronic device is logged out.

11. The method according to any one of claims 8-10, characterized in that, The authentication information includes at least one of fingerprints, facial images, voice, and passwords.

12. A method for positioning equipment, characterized in that, Applied to a device positioning system, the device positioning system including a cloud device, a first electronic device, and a second electronic device, the method includes: In response to an account input operation, the first electronic device obtains a first user account and a device identifier of the first electronic device, and sends the first user account and the device identifier to the cloud device; wherein, the first user account is the user account to be logged into the first electronic device; Based on the first user account and the device identifier, if the cloud device determines that the first electronic device has been repeatedly bound, it sends a first notification message to a second device logged in with a second user account; wherein, the first notification message is used to indicate the current location of the user holding the first electronic device; the second user account is the account already bound to the first electronic device; The second electronic device displays the first notification information.

13. A method for positioning equipment, characterized in that, Applied to a device positioning system, the device positioning system including a cloud device, a first electronic device, and a second electronic device, the method includes: In response to an account input operation, the first electronic device obtains a first user account and a device identifier of the first electronic device. If it is determined that the first electronic device has been repeatedly bound based on the first user account and the device identifier, it sends a device location request to the cloud device. The first user account is the user account to be logged into the first electronic device. The cloud device receives the device location request and sends a first notification message to the second electronic device. The first notification message includes the current location of the first electronic device and a second user account logged in on the second electronic device. The second user account is the account that the first electronic device has been bound to. The second electronic device displays the first notification information.

14. An electronic device, characterized in that, The device includes a memory and one or more processors; the memory is coupled to the processors; the memory stores computer program code, the computer program code including computer instructions, which, when executed by the processor, cause the electronic device to perform the device positioning method as described in any one of claims 1-6, or to perform the device positioning method as described in any one of claims 7-11.

15. A computer-readable storage medium, characterized in that, The method includes computer instructions that, when executed on an electronic device, cause the electronic device to perform the device positioning method as described in any one of claims 1-6, or to perform the device positioning method as described in any one of claims 7-11.

16. A computer program product, characterized in that, When the computer program product is run on an electronic device, it causes the electronic device to perform the device positioning method as described in any one of claims 1-6, or to perform the device positioning method as described in any one of claims 7-11.

Images