CN110099164B

CN110099164B - Method for finding lost terminal and terminal

Info

Publication number: CN110099164B
Application number: CN201910242177.5A
Authority: CN
Inventors: 张跃; 陶强
Original assignee: Huawei Device Co Ltd
Current assignee: Huawei Device Co Ltd
Priority date: 2019-03-28
Filing date: 2019-03-28
Publication date: 2022-04-05
Anticipated expiration: 2039-03-28
Also published as: CN110099164A

Abstract

The application provides a method for finding lost terminal and a terminal. The method can comprise the following steps: determining that the terminal is in a possible loss state, wherein the possible loss state is a state judged that the terminal is possible to be lost currently; determining the position information of the terminal, wherein the position information is the information of the geographical position of the terminal; and notifying the cloud account of the terminal of loss information and the position information, wherein the loss information is used for indicating that the terminal is possibly in a lost state currently. According to the method, when the terminal judges that the terminal is possibly in a lost state, the geographical position of the terminal is located, the lost information and the position information are actively reported to the cloud account, active reminding can be triggered under the condition that the terminal judges that the terminal is possibly in the lost state, the success rate of finding the lost terminal is improved, and therefore user loss is reduced.

Description

Method for finding lost terminal and terminal

Technical Field

The present application relates to the field of intelligent terminals, and more particularly, to a method for retrieving a lost terminal and a lost terminal.

Background

At present, after a smart terminal (e.g., a smart phone) is lost, a user usually needs to check a specific geographic location of the lost mobile phone when logging in the cloud account last or last time by logging in an official website of a mobile phone manufacturer or actively logging in the cloud account of the user through other mobile phones produced by the mobile phone manufacturer or other terminal devices, so as to retrieve the mobile phone. If the mobile phone is online networked when the user logs in the cloud account, the current geographic position of the mobile phone can be located in real time; if the mobile phone is not networked online when the user logs in the account, the current geographic position of the mobile phone cannot be located in real time, and only the specific geographic position of the mobile phone when the mobile phone logs in the cloud account for the last time can be determined. The scheme depends on that the user logs in the cloud account of the user recently or logs in after losing the mobile phone, the retrieving requirement is high, and an active reminding mechanism related to loss does not exist.

Disclosure of Invention

The application provides a method and a terminal for finding a lost terminal, which can trigger active reminding under the condition that the terminal judges that the terminal is possibly in a lost state, improve the success rate of finding the lost terminal, and reduce the loss of a user.

In a first aspect, a method for recovering a lost terminal is provided, where the method includes: determining that the terminal is in a possible loss state, wherein the possible loss state is a state judged that the terminal is possible to be lost currently; determining the position information of the terminal, wherein the position information is the information of the geographical position of the terminal; and notifying the cloud account of the terminal of loss information and the position information, wherein the loss information is used for indicating that the terminal is possibly in a lost state currently.

According to the method for finding the lost terminal, when the terminal judges that the terminal is possibly in a lost state, the geographical position of the terminal is located, the lost information and the position information are actively reported to the cloud account, active reminding can be triggered under the condition that the terminal judges that the terminal is possibly in the lost state, the success rate of finding the lost terminal is improved, and therefore user loss is reduced.

In a possible implementation manner, the possible current state of the terminal that may be lost may include: the terminal is swiped, the terminal is switched to other cloud account numbers, and the terminal is continuously and repeatedly wrongly input at least one of the screen locking passwords and the SIM card replaced. In other words, determining that the terminal is in a potentially lost state may include: determining that the terminal is swiped, determining that the terminal is switched to other cloud account numbers, determining that the terminal is mistakenly input screen locking passwords for multiple times continuously, and determining that the terminal is replaced by at least one of SIM cards. This possible implementation can be applied to multiple scene, and when judging that the terminal takes place arbitrary one or more in the above-mentioned condition, there is certain possibility that the terminal is lost and is obtained by other people or the terminal is stolen, carries out geographical position location to the terminal, reports positional information and loses the information to the account number in the high in the clouds.

In one possible implementation, the lost information is further used to indicate that the terminal is booted, the terminal is switched to other cloud account numbers, and the terminal is mistakenly input a screen locking password or the terminal is replaced with a SIM card. The possible implementation mode enables the user to know the reason for receiving the loss reminding so as to make more accurate judgment.

In one possible implementation, the loss information may be stored in NV items of the terminal. Therefore, the lost information can be ensured not to be deleted under the condition that the terminal is refreshed.

In one possible implementation, the method may further include: when the terminal is determined to be in the possible loss state, the terminal is identified to be in the possible loss state currently through the value of the identification bit; after the cloud account of the terminal is notified of the loss information and the position information, the value of the identification bit is reset. The possible implementation mode records the current possible lost state of the terminal through the identification position, and resets the identification position after the prompt is sent, so that the normal use of the user is not influenced.

In a second aspect, the present application provides a terminal configured to perform the method of the first aspect or any possible implementation manner thereof. In particular, the terminal may comprise means for performing the method of the first aspect or any possible implementation thereof.

In a third aspect, the present application provides a terminal comprising a processor and a memory, the memory being configured to store instructions, and the processor being configured to execute the instructions stored by the memory, so that the terminal performs the method of the first aspect or any possible implementation manner thereof.

In a fourth aspect, the present application provides a computer-readable storage medium having stored thereon instructions which, when executed on a computer, cause the computer to perform the method of the first aspect and any possible implementation thereof.

In a fifth aspect, the present application provides a computer program product comprising instructions which, when executed by a computer, cause the computer to perform the method of the first aspect and any possible implementation thereof.

In a sixth aspect, the present application provides a computer chip for causing a computer to perform the method of the first aspect and any possible implementation manner thereof.

The effects obtainable by the second to sixth aspects and any possible implementation manner thereof are consistent with the corresponding effects of the first aspect, and are not described again.

Drawings

Fig. 1 is a schematic diagram of a method for recovering a lost terminal according to an embodiment of the present application.

Fig. 2 is a schematic diagram of a flashing process provided in an embodiment of the present application.

Fig. 3 is a schematic diagram of a notification flow provided by an embodiment of the present application.

FIG. 4 is a diagram illustrating the operation of the software and hardware framework of the method of one embodiment of the present application.

Fig. 5 is a schematic diagram of a notification flow provided in another embodiment of the present application.

FIG. 6 is a schematic diagram of the software and hardware framework in operation of the method of another embodiment of the present application.

Fig. 7 is a schematic diagram of a notification flow provided by another embodiment of the present application.

FIG. 8 is a schematic diagram of the software and hardware framework in operation of the method of another embodiment of the present application.

Fig. 9 is a schematic diagram of a notification flow provided in another embodiment of the present application.

FIG. 10 is a schematic representation of the method of another embodiment of the present application as it operates on a software and hardware framework.

Fig. 11 shows a schematic block diagram of a terminal provided in an embodiment of the present application.

Fig. 12 shows a schematic block diagram of a terminal provided in another embodiment of the present application.

Detailed Description

The technical solution in the present application will be described below with reference to the accompanying drawings.

The embodiment of the application provides a method and a terminal for recovering a lost terminal, and the method and the terminal can be used for recovering the lost terminal in various scenes. For example: (1) the terminal of the user is refreshed after being lost, and the account information logged in before is lost, so that the terminal cannot be retrieved; (2) after the terminal of the user is lost, the account number logged in before is cracked, and a new account number is logged in, so that the terminal cannot be retrieved; (3) after the terminal of the user is lost, other people continuously try to input the screen locking password, and the terminal cannot be retrieved no matter whether the password is tried successfully or not; (4) after the terminal of the user is lost, a Subscriber Identity Module (SIM) card is replaced by others, and the user is informed without an active alarm mechanism, so that the terminal cannot be found back. It should be understood that the method and the terminal provided by the embodiment of the present application are not limited to be applied to the foregoing scenarios, and may also be applied to other broader scenarios, which are not limited in the embodiment of the present application.

Fig. 1 is a schematic diagram of a method 100 for recovering a lost terminal according to an embodiment of the present disclosure. As shown in fig. 1, the method 100 may include the following steps.

S110, determining that the terminal is in a possible loss state, where the possible loss state is a state judged that the terminal is currently possible to be lost.

And S120, determining the position information of the terminal, wherein the position information is the information of the geographical position of the terminal.

S130, notify the cloud account of the terminal of loss information and the location information, where the loss information is used to indicate that the terminal may be in a lost state currently.

And then, the cloud end can inform the user of lost information and position information through the network.

In some embodiments of the present application, the terminal may be currently in a lost state, which may include: the terminal is swiped, the terminal is switched to other cloud account numbers, and the terminal is continuously and repeatedly wrongly input at least one of the screen locking passwords and the SIM card replaced. In other words, determining that the terminal is in a potentially lost state may include: determining that the terminal is swiped, determining that the terminal is switched to other cloud account numbers, determining that the terminal is mistakenly input screen locking passwords for multiple times continuously, and determining that the terminal is replaced by at least one of SIM cards.

It will be appreciated that there is a certain likelihood that the terminal will be lost and either obtained by others or stolen when it is determined that any one or more of the above conditions are occurring at the terminal. When the situation or the situations occur, the geographic position of the terminal is located, and the position information and the loss information are reported to the cloud account. Wherein the loss information alerts the user that the terminal may be currently in a lost state. Correspondingly, for any one of the above situations, the lost information may further be used to indicate that the terminal is booted, the terminal is switched to another cloud account, and the terminal is continuously mistakenly input a screen locking password for multiple times or the terminal is replaced with an SIM card. Specific processing modes for the above cases and combinations of the above cases will be described in detail below.

In some embodiments of the present application, for example in case of a terminal being flushed, it is necessary to ensure that the missing information is not deleted in case of a terminal being flushed. In a specific example, the loss information may be stored in a non-volatile random access memory (NVRAM, NV for short) entry of the terminal.

The NV item is generally used for recording some information inherent to the terminal, a basic configuration, and a dedicated file system of the radio frequency parameter, for example, when the terminal is a mobile phone, the NV item may record a Mobile Equipment Identifier (MEID) and the like. Generally, the NV item is closely related to the communication function, for example, networks that the mobile phone is allowed to register, networks that the mobile phone is currently registered, and the like may be marked in the NV item. In a specific example, if the NV item in the handset marks that the network allowed to be registered is a connected network, when the mobile SIM card is inserted, the problem occurs that the new number of the network cannot be found. Typically, the currently registered network marked in the NV item is rewritten with the insertion of the SIM card of the handset. Usually, once data is written into the NV item, the data cannot be lost even if the terminal is powered down, and the original setting can still be kept when the terminal is restarted next time. I.e. when the terminal is powered off, the data stored in the NV item is not lost. Almost all high-pass platforms use NV items to store important parameters of the handset. The NV item causes various problems in the terminal after it is broken, and thus the NV item is generally set not to be deleted even if it is flushed. According to the method and the device for saving the lost information, the lost information is saved in the NV item by utilizing the characteristic of the NV item, so that the lost information cannot be deleted under the condition that the terminal is refreshed, and a user can still be reminded that the terminal is possibly lost at present.

The user himself may switch other cloud account numbers, replace the SIM card, or continuously input a wrong screen locking password for many times due to a wrong operation, which is the autonomous operation of the user rather than the terminal being lost and being obtained by others or the terminal being stolen. For such a situation, a certain mechanism needs to be designed, so that after a reminder that the terminal may be in a lost state at present is sent, the terminal is restored to a normal state, and the user can continue to use the terminal normally.

In some embodiments of the present application, the method 100 may further comprise: when the terminal is determined to be in the possible loss state, the terminal is identified to be in the possible loss state currently through the value of the identification bit; after the cloud account of the terminal is notified of the loss information and the position information, the value of the identification bit is reset. Namely, the current state that the terminal is possibly lost is recorded through the identification position, and the identification position is reset after the prompt is sent, so that the normal use of the user is not influenced.

In one specific example, the identification bit may be 1 bit (bit). When the value of the flag bit is 0, it indicates that the terminal is not currently in a state that may be lost, and when the value of the flag bit is 1, it indicates that the terminal is currently in a state that may be lost.

In another specific example, the identification bit may be 3 bits (bit). When the value of the identification bit is 000, the terminal is not in a possibly lost state currently; when the value of the identification bit is 001, the terminal is refreshed, and the terminal is possibly in a lost state currently; when the value of the identification bit is 010, the terminal is switched to other cloud account numbers, and the terminal is possibly in a lost state at present; when the value of the identification bit is 011, the terminal is indicated to be continuously mistakenly input screen locking passwords for multiple times, and the terminal is possibly in a lost state at present; when the value of the identification bit is 100, the terminal is replaced by the subscriber identity module SIM card, and the terminal may be in a lost state currently.

It should be understood that the value of the identification bit in the embodiments of the present application may be assigned to other types of values, and the above examples are only illustrative and not restrictive.

The method for retrieving the lost terminal is described in detail below with reference to specific scenarios, and the implementation of the method of the present application in each scenario may be accomplished with reference to corresponding software and/or hardware.

The following embodiment describes a method for recovering a lost terminal in a scenario where the terminal is flashed.

In this scenario, a pre-preparation step is required to perform corresponding processing. In the pre-preparation step, after a user logs in the cloud account for the first time, information (for example, a user name and a password may be included) of the cloud account is written into the NV item for storage. Next, a flashing process is performed, and the flashing process of this embodiment, as shown in the process 200 shown in fig. 2, may include the following steps.

And S210, starting a flashing process.

S220, when the terminal is booted, the terminal system starts a bootstrap program, namely, enters a bootloader (bootloader) program, and carries out data transportation and other operations. The bootloader program operates to determine that the terminal is in a state of possible loss.

S230, this embodiment may assign a value to the identification bit, where the value of the identification bit indicates that the terminal is powered down and may be in a lost state. The flag is stored as an NV item and recorded in an oeminfo file (which may be a block file) that is not deleted after the flush. In one example, the value of the identification bit may be assigned to flush.

And S240, finishing the flashing process.

This is followed by a notification flow, such as flow 300 shown in fig. 3, which may include the following steps.

S310, the notification flow starts.

And S320, after the terminal is started, registering and monitoring the networking broadcast.

And S330, judging whether the terminal is in a networking state. When the terminal is in the networking state, executing S340; otherwise, executing S390 to notify the end of the process.

S340, starting a state determination service (or called a scene determination service) in a system service (system _ server) program, and reading an identification bit of the NV item.

S350, judging whether the value of the identification bit is brushed or not. When the value of the flag bit is busy, S360 is executed; otherwise, executing S390 to notify the end of the process.

And S360, acquiring the current position information of the terminal, wherein the position information can be longitude and latitude information. The positioning process may be implemented by a Global Positioning System (GPS).

And S370, reading the information of the cloud account of the terminal in the NV item.

And S380, informing the cloud account of the terminal of the refreshed state (lost information) and the current longitude and latitude information (position information) of the terminal.

S390, notify the end of the process.

After S390, the cloud may remind the user terminal that the terminal may be stolen and the machine is refreshed through the cloud account, and inform the user of the longitude and latitude of the terminal when the terminal is networked after the machine is refreshed. After S390, the information of the identification bits in the NV item and/or the cloud account of the terminal may be set to NULL (NULL).

FIG. 4 is a schematic diagram of the method of the present embodiment when the software and hardware framework is in operation.

In this embodiment, the terminal is determined to be a refreshed scene, and when the user terminal is lost and is obtained by others or the terminal is refreshed after being stolen, the user can be actively notified of the lost information in a cloud-end matching manner, so that the user can be more efficiently helped to retrieve the terminal.

The following embodiment describes a method for finding a lost terminal in a scenario where the terminal is switched to another cloud account (quit an old cloud account, and log in a new cloud account).

In this scenario, a pre-preparation step is required to perform corresponding processing. In the pre-preparation step, after a user logs in the cloud account for the first time, information (for example, a user name and a password may be included) of the cloud account is written into the NV item for storage. The NV item may be stored in an oeminfo file. Next, a notification flow follows, and the notification flow of the present embodiment, as shown in the flow 500 of fig. 5, may include the following steps.

S510, the notification flow starts.

S520, the terminal detects that the cloud account is logged in.

S530, the terminal reads the information of the cloud account in the NV item and judges whether the cloud account is switched to other cloud accounts. The specific judging step may be: judging whether the information of the cloud account stored in the NV item is null or not, if so, namely the old cloud account is not switched to other cloud accounts, considering that the cloud account logs in for the first time, executing S580, and notifying that the process is finished; if not, that is, the old cloud account is switched to another cloud account, then S540 is executed. It should be understood that S520 and S530 may be specifically executed by the cloud account management unit.

S540 sets the value of the identification bit in the NV item to change (switch account).

The terminal can be networked certainly when the cloud account is online, so that the terminal can directly lose the terminal and can be obtained by others or the terminal is stolen, and the information of the new cloud account is switched and sent to the cloud account which logs in before, so that the mobile phone account of the user is prompted to be switched and the current position of the user terminal is informed.

S550, acquiring current location information of the terminal, where the location information may be, for example, latitude and longitude information. The positioning process may be implemented by GPS.

And S560, reading the information of the old cloud account in the NV item.

S570, notify the old cloud account (the cloud account before switching) in the NV item of the switched account (loss information) and the current longitude and latitude information (location information) of the terminal.

S580, the notification flow ends.

After S580, the cloud may remind the user terminal of the account being switched through the cloud account, where the account may be lost or obtained by others or may be stolen, and inform the user of the current longitude and latitude of the terminal. After S580, the flag in the NV item for saving may be set to NULL (NULL), and the information of the new cloud account is saved into the NV item again.

FIG. 6 is a schematic diagram of the method of the present embodiment when the software and hardware framework is in operation.

In this embodiment, the terminal is determined to be a scene switched with other cloud account numbers, and when the user terminal is lost and is obtained by others or the terminal is switched with other cloud account numbers after being stolen, the user can be actively notified of the lost information in a cloud cooperation mode, so that the user can be more efficiently helped to find back the terminal.

The following embodiment describes a method for retrieving a lost terminal in a scene where a screen locking password is set in the terminal and the screen locking password is continuously and repeatedly input.

In this scenario, when the terminal is lost and is obtained by another person or is stolen, the thief tries to input the screen locking password for multiple times, so that the identification logic for monitoring the number of times of wrong input of the screen locking password (for example, whether the number of times reaches 5) is added to the screen locking application.

Pre-preparation steps are required to deal with this. In the pre-preparation step, after a user logs in the cloud account for the first time, information (for example, a user name and a password may be included) of the cloud account is written into the NV item for storage. The NV item may be stored in an oeminfo file. Next, a notification flow follows, and the notification flow of the present embodiment, as shown in the flow 700 of fig. 7, may include the following steps.

S710, the notification flow starts.

S720, the current user of the terminal inputs the screen locking password and records the times of continuously mistakenly inputting the screen locking password.

S730, judging whether the frequency of continuously mistaken screen locking passwords input by the user reaches 5 times. Executing S740 when the number of times of continuously mistaken screen locking passwords reaches 5 times; otherwise, executing S790, and notifying the end of the process. It should be understood that the number of consecutive screen-locking password-losing times of 5 times is only exemplary, and is not a limitation of the present application, and other embodiments of the present application may set more or less consecutive screen-locking password-losing times according to specific requirements.

S740, setting the value of the identification bit in the NV item as password (continuously and repeatedly inputting wrong screen locking passwords).

And S750, judging whether the terminal is in the networking state. When the terminal is in the networking state, executing S760; otherwise, executing S790, and notifying the end of the process.

S760, acquiring current location information of the terminal, where the location information may be, for example, latitude and longitude information. The positioning process may be implemented by GPS.

And S770, reading the information of the cloud account of the terminal in the NV item.

S780, notify the cloud account of the terminal that the terminal has been continuously and repeatedly wrongly input the screen locking password (lost information) and the current longitude and latitude information (location information).

S790, notify the flow end. .

After S790, the cloud may remind the user terminal through the cloud account to miss the screen locking password for a plurality of consecutive times, where the screen locking password may be lost and obtained by others or may be stolen, and inform the user of the current longitude and latitude of the terminal. After S790, the flag bit in the NV item for saving may be set to NULL.

FIG. 8 is a schematic diagram of the method of the present embodiment when the software and hardware framework is running.

In this embodiment, the terminal is determined to be a scene in which the screen locking password is continuously and repeatedly input, and when the user terminal is lost and is obtained by others or the terminal is stolen and then the screen locking password is continuously and repeatedly input, the user can be actively notified of the lost information through a cloud-end matching mode, so that the user can be more efficiently helped to find back the terminal.

The following embodiment describes a method for recovering a lost terminal in a scenario where the SIM card of the terminal is replaced.

In this scenario, when the terminal is lost and is obtained by another person or stolen, the thief replaces the SIM card, so the receiving broadcast logic identified by the new SIM card is added to the terminal in this embodiment.

Pre-preparation steps are required to deal with this. In the pre-preparation step, after a user logs in the cloud account for the first time, information (for example, a user name and a password may be included) of the cloud account is written into the NV item for storage. The NV item may be stored in an oeminfo file. Each time a new SIM card is inserted into the terminal, the Integrated Circuit Card Identification (ICCID) of the SIM card is stored in a database (may be the NV item).

Next, a notification flow follows, and the notification flow of the present embodiment, like the flow 900 shown in fig. 9, may include the following steps.

S910, the notification flow starts.

S920, the terminal process monitors the SIM card inserting event.

S930, inserting a new SIM card.

And S940, judging whether the ICCID of the new SIM card is the same as the ICCID stored in the database. When different, S950 is performed; otherwise, S995 is executed, and the notification process ends.

S950, the value of the identification bit in the NV item is set to simchange (replacing the SIM card).

S960, judging whether the terminal is in the networking state. When the terminal is in the networking state, executing S970; otherwise, S995 is executed, and the notification process ends.

S970, acquiring current location information of the terminal, where the location information may be, for example, latitude and longitude information. The positioning process may be implemented by GPS.

And S980, reading the information of the cloud account of the terminal in the NV item.

S990, notify the cloud account of the terminal of the replaced SIM card (lost information) and the current longitude and latitude information (location information).

S995, notifying the end of the process.

After S995, the cloud may remind the user terminal through the cloud account that the SIM card is replaced, that it may be lost and obtained by others or may be stolen, and inform the user of the current longitude and latitude of the terminal. After S995, the flag bit in the NV item for saving may be set to NULL (NULL).

FIG. 10 is a schematic diagram of the method of the present embodiment when the software and hardware framework is in operation.

In this embodiment, the terminal is determined to be a scenario of a replaced SIM card, and when the user terminal is lost and is obtained by others or the SIM card is replaced after the terminal is stolen, the user can be actively notified of the lost information in a cloud-end matching manner, so that the user can be more efficiently helped to retrieve the terminal.

The method for recovering the lost terminal according to the embodiment of the present application is described above with reference to fig. 1 to 10, and the configuration of the terminal and the cloud terminal is described in detail with reference to fig. 11 and 12. It should be understood that the description of the terminal and cloud embodiments corresponds to the description of the method embodiment, and therefore, for the sake of brevity, details which are not described in detail may be referred to the foregoing method embodiment.

Fig. 11 shows a schematic block diagram of a terminal 1100 provided in an embodiment of the present application. The terminal 1100 is adapted to perform the method embodiments described above. The terminal 1100 includes the following modules.

A state determining module 1110, configured to determine that the terminal 1100 is in a possible loss state, where the possible loss state is a state judged that the terminal 1100 is likely to be lost currently; a positioning module 1120, configured to determine location information of the terminal 1100, where the location information is information of a geographic location where the terminal 1100 is located; the cloud communication module 1130 is configured to notify the cloud account of the terminal 1100 of loss information and the location information, where the loss information is used to indicate that the terminal 1100 may be in a lost state currently.

The terminal provided by the embodiment of the application locates the geographical position of the terminal when the terminal judges that the terminal is possibly in a loss state, actively reports loss information and position information to the cloud account, can trigger active reminding under the condition that the terminal judges that the terminal is possibly in the loss state, improves the success rate of finding the lost terminal, and reduces user loss.

It should be understood that, in various embodiments, the determination that the terminal may be in the lost state by the state determination module 1110 may be implemented based on the foregoing software and/or hardware, for example, including but not limited to the foregoing bootloader program, system _ server program, state determination service, cloud account management unit, identification logic for monitoring the number of screen locking password input errors, and broadcast receiving logic for adding new SIM card identification. The position information obtained by the positioning module 1120 may be, for example, latitude and longitude information, and the positioning module 1120 may be implemented based on a GPS or a beidou satellite navigation system, which is not limited in this application.

In some embodiments of the present application, the terminal may be currently in a lost state, which may include: the terminal is swiped, other cloud account numbers are switched to the terminal, and the terminal is continuously mistakenly input screen locking passwords for multiple times and replaced by at least one of the SIM cards.

In some embodiments of the present application, the loss information may be further used to indicate that the terminal is flashed, the terminal is switched to other cloud account numbers, and the terminal is mistakenly input a screen locking password or the terminal is replaced with an SIM card.

In some embodiments of the present application, the missing information is not deleted in case the terminal is flushed.

In some embodiments of the application, the loss information is stored in a non-volatile random access storage, NV, item of the terminal.

In some embodiments of the present application, the terminal may further include: an identification bit storage module 1140, configured to identify, when the terminal is determined to be in a possibly lost state, that the terminal is currently possibly in a lost state by a value of an identification bit; and after the lost information and the position information are notified to the cloud account of the terminal, resetting the value of the identification bit.

It should be understood that the terminal in each embodiment of the present application may further include a storage module for storing information of the cloud account, which is not limited in this application.

Accordingly, as shown in fig. 11, the cloud may include a corresponding module for notifying the user, such as a message notification module.

Fig. 12 is a schematic block diagram of a terminal 1200 provided in an embodiment of the present application. The terminal 1200 shown in fig. 12 may include a processor 1210 and a memory 1220, the memory 1220 having stored therein computer instructions, which when executed by the processor 1210, cause the terminal 1200 to perform the steps of: determining that the terminal is in a possible loss state, wherein the possible loss state is a state judged that the terminal is possible to be lost currently; determining the position information of the terminal, wherein the position information is the information of the geographical position of the terminal; and notifying the cloud account of the terminal of loss information and the position information, wherein the loss information is used for indicating that the terminal is possibly in a lost state currently.

In some embodiments of the present application, the processor 1210 may be further configured to execute the computer instructions, so that the terminal 1200 performs the following steps: when the terminal is determined to be in the possible loss state, the terminal is identified to be in the possible loss state currently through the value of the identification bit; and after the lost information and the position information are notified to the cloud account of the terminal, resetting the value of the identification bit.

It should be understood that the apparatus of the embodiments of the present application may be implemented based on a memory and a processor, wherein the memory is used for storing instructions for executing the method of the embodiments of the present application, and the processor executes the instructions to make the apparatus execute the method of the embodiments of the present application.

It should be understood that the processor mentioned in the embodiment of the present application may include a Central Processing Unit (CPU), a Network Processor (NP), or a combination of the CPU and the NP. The processor may further include a hardware chip. The hardware chip may be an application-specific integrated circuit (ASIC), a Programmable Logic Device (PLD), or a combination thereof. The PLD may be a Complex Programmable Logic Device (CPLD), a field-programmable gate array (FPGA), a General Array Logic (GAL), or any combination thereof.

It should also be understood that the memory referred to in the embodiments of the present application may be a volatile memory (volatile memory) or a non-volatile memory (non-volatile memory), or may include both volatile and non-volatile memory. The nonvolatile memory may be a read-only memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an electrically Erasable EPROM (EEPROM), a flash memory (flash memory), a hard disk (HDD), or a solid-state drive (SSD). Volatile memory can be Random Access Memory (RAM), which acts as external cache memory. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic Random Access Memory (SDRAM), double data rate SDRAM, enhanced SDRAM, SLDRAM, Synchronous Link DRAM (SLDRAM), and direct rambus RAM (DR RAM).

It should be noted that when the processor is a general-purpose processor, a DSP, an ASIC, an FPGA or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, the memory (memory module) is integrated in the processor.

It should be noted that the memory described herein is intended to comprise, without being limited to, these and any other suitable types of memory.

Embodiments of the present application also provide a computer-readable storage medium, on which instructions are stored, and when the instructions are executed on a computer, the computer is caused to execute the steps of the above method embodiments.

An embodiment of the present application further provides a computing device, which includes the computer-readable storage medium.

The embodiment of the present application further provides a computer program product including instructions, wherein when the instructions of the computer program product are executed by a computer, the computer performs the steps of the above method embodiment.

The embodiment of the present application further provides a computer chip, where the computer chip enables a computer to execute the steps of the above method embodiments.

It should be understood that the division of circuits, sub-units of the various embodiments of the present application is illustrative only. Those of ordinary skill in the art will appreciate that the various illustrative circuits, sub-circuits, and sub-units described in connection with the embodiments disclosed herein can be split or combined.

The apparatus provided by the embodiments of the present application may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the application to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored on a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website, computer, server, or data center to another website, computer, server, or data center via wire (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that incorporates one or more of the available media. The usable medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a Digital Video Disk (DVD)), or a semiconductor medium (e.g., an SSD), among others.

It should be understood that the reference herein to first, second, and various numerical designations is merely a convenient division to describe and is not intended to limit the scope of the present application.

It should be understood that the term "and/or" herein is merely one type of association relationship that describes an associated object, meaning that three relationships may exist, e.g., a and/or B may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" herein generally indicates that the former and latter related objects are in an "or" relationship.

It should be understood that, in the embodiment of the present application, the sequence numbers of the above-mentioned processes do not mean the execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiment of the present application.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.

The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method for recovering lost terminal, comprising:

determining that a terminal is in a possible loss state, wherein the possible loss state is a state judged that the terminal is possible to be lost currently;

determining the position information of the terminal, wherein the position information is the information of the geographical position of the terminal;

notifying a cloud account of the terminal of loss information and the location information, where the loss information is used to indicate that the terminal may be currently in a lost state, and the loss information is further used to indicate one or more of: the terminal is switched to other cloud account numbers, the SIM card of the terminal is replaced, the lost information cannot be deleted under the condition that the terminal is refreshed, and the cloud account numbers cannot be deleted under the condition that the terminal is refreshed.

2. The method of claim 1, wherein the terminal may be currently in a lost state, comprising:

the terminal is swiped, other cloud account numbers are switched to the terminal, and the terminal is continuously mistakenly input screen locking passwords for multiple times and replaced by at least one of the SIM cards.

3. A method according to claim 1 or 2, characterized in that the loss information is kept in a non-volatile random access storage, NV, item of the terminal.

4. The method according to claim 1 or 2, characterized in that the method further comprises:

when the terminal is determined to be in the possible loss state, the terminal is identified to be in the possible loss state currently through the value of the identification bit;

and after the lost information and the position information are notified to the cloud account of the terminal, resetting the value of the identification bit.

5. A terminal, comprising:

a state determining module, configured to determine that a terminal is in a possible loss state, where the possible loss state is a state judged that the terminal may be currently lost;

the positioning module is used for determining the position information of the terminal, and the position information is the information of the geographical position of the terminal;

a cloud communication module, configured to notify a cloud account of the terminal of loss information and the location information, where the loss information is used to indicate that the terminal may be currently in a lost state, and the loss information is further used to indicate one or more of the following: the terminal is refreshed, other cloud account numbers are switched to the terminal, the SIM card of the terminal is replaced, the lost information cannot be deleted under the condition that the terminal is refreshed, and the cloud account numbers cannot be deleted under the condition that the terminal is refreshed.

6. The terminal of claim 5, wherein the terminal may be currently in a lost state, comprising:

7. A terminal as claimed in claim 5 or 6, characterised in that the loss information is held in a non-volatile random access memory (NV) entry in the terminal.

8. The terminal according to claim 5 or 6, characterized in that the terminal further comprises:

an identification bit storage module, configured to identify, when it is determined that the terminal is in a state that may be lost, a current state that the terminal may be lost through a value of an identification bit; and after the lost information and the position information are notified to the cloud account of the terminal, resetting the value of the identification bit.

9. A terminal, comprising a processor and a memory, the memory having stored therein computer instructions that, when executed by the processor, cause the terminal to perform the steps of:

determining that the terminal is in a possible loss state, wherein the possible loss state is a state judged that the terminal is possible to be lost currently;

notifying a cloud account of the terminal of loss information and the location information, where the loss information is used to indicate that the terminal may be currently in a lost state, and the loss information is further used to indicate one or more of: the terminal is refreshed, other cloud account numbers are switched to the terminal, the SIM card of the terminal is replaced, the lost information cannot be deleted under the condition that the terminal is refreshed, and the cloud account numbers cannot be deleted under the condition that the terminal is refreshed.

10. The terminal of claim 9, wherein the terminal may be currently in a lost state, comprising:

11. A terminal according to claim 9 or 10, characterized in that the loss information is kept in a non-volatile random access memory, NV, entry in the terminal.

12. The terminal of claim 9 or 10, wherein the processor is further configured to execute the computer instructions to cause the terminal to perform the steps of:

13. A computer-readable storage medium having instructions stored thereon, which when executed on a computer, cause the computer to perform the method of any one of claims 1 to 4.

14. A computer chip, characterized in that it causes a computer to perform the method of any of claims 1 to 4.