KR20210076808A - Smartphone loss and found management method - Google Patents

Abstract

Disclosed are a device loss and retrieval management method. The method includes: a step wherein a first application executed by a processor of a first computing device having a phone function owned by a first user makes a request for registration by transmitting information for device retrieval including unique identification information of the first computing device and information about a second user acting as an agent for the first user to perform retrieval when the first computing device is lost; a step wherein a loss management server registers the information for device retrieval received from the first application in a database; a step wherein the loss management server performs loss management with respect to the information for device retrieval registered in the database when receiving a loss report about the first computing device from the online-connected first user or a second application executed by a processor of a second computing device; and a step wherein the loss management server requests a related communication service provider of the first computing device reported as being lost to stop the use of the first computing device. Therefore, the present invention is capable of providing a useful service to a user even when the user has lost his or her smartphone.

Description

Device loss and recovery management method {Smartphone loss and found management method}

The present invention relates to a technology for providing a service related to the loss of a device having a telephone function.

Techniques for preventing loss of belongings are well known. Typically, when an electronic tag attached to belongings and a smart phone are separated by a predetermined distance or more, there is a technology that generates an alarm in the smart phone so that the user can recognize it. In addition to such a loss prevention technology, a service technology for recovering lost and found is also known. As a related technology, Korean Patent Publication No. 10-1888543 discloses a lost and found recovery management guide system. This lost and found collection management guide system provides a service that allows users to recover their lost belongings using an app for managing belongings mounted on their smartphone. However, this system has a limitation in that it cannot provide a service related to lost and found to a user when a user loses a smartphone equipped with an app for managing belongings.

Domestic Registered Patent Publication No. 10-1888543 (Announced on August 16, 2018)

An object of the present invention is to provide a method for providing a useful service to a user when the lost item is a smartphone.

In a smartphone loss and collection management method according to an aspect, a first application executed by a processor of a first computing device having a phone function owned by a first user includes the unique identification information of the first computing device and the first computing device. Sending device recovery information including the second user information that will act as an agent of the first user for recovery in case of loss to the loss management server and requesting registration, the loss management server collects the device recovery information received from the first application Registering in the database, when a loss report for the first computing device is received from the first user or the second application executed by the processor of the second computing device to which the loss management server is online-connected, information for retrieving the device registered in the database The step of managing the loss, and the loss management server may include the step of requesting the suspension of use of the first computing device to the related communication company server of the first computing device to which the loss report is received.

In the device recovery information registration step, the second user information is checked in the device recovery information received from the first application, and the second application of the confirmed second user requests whether to consent to the agent for the first user and agrees. Only for , device recovery information including the second user information may be registered in the database.

Smartphone loss and collection management method includes the steps of transmitting the loss notification information to the first application of the lost first computing device by the loss management server, and the first application transmits the loss notification information received from the loss management server to the first computing device It may further include the step of displaying on the lock screen of.

The smartphone loss and recovery management method backs up the data to be backed up and/or deleted by the first user from the first computing device to the cloud storage of the first user when the first application receives the loss notification information from the loss management server and/or deleting may be further included.

In the smartphone loss and collection management method, when a loss report is received by the loss management server, device loss information on the first computing device is transmitted from the loss location of the first computing device to the computing devices of members within a predetermined range to help with loss recovery It may further include the step of requesting.

The smartphone loss and collection management method further includes the step of generating a loss certificate for the loss proof of the first computing device when the loss management server receives a loss report and providing it to the access device of the first user or providing it as a second application can do.

The smart phone loss and collection management method is a third application executed by the processor of the third computing device owned by the learner who has acquired the first computing device through the tagging of the third computing device to the electronic tag of the first computing device. The method may further include obtaining the second user's phone number from the electronic tag and allowing the learner to make a phone call with the second user.

According to the disclosure, even when a user loses a smartphone, a useful service can be provided.

1 is a block diagram of a device loss and recovery management system according to an embodiment.
2 is a flowchart of registering information for device collection according to an embodiment.
3 is an exemplary diagram of a user interface screen of a first application.
4 is a flowchart illustrating a device loss process according to an embodiment.
5 is a flowchart illustrating a device loss process according to another embodiment.
6 is a flowchart of a device acquisition process according to an embodiment.
7 is a flowchart of a device acquisition process according to another embodiment.
8 is a flowchart illustrating a device loss release process according to an embodiment.
9 is a block diagram of a computing device according to one embodiment.

The foregoing and further aspects of the present invention will become more apparent through preferred embodiments described with reference to the accompanying drawings. Hereinafter, the present invention will be described in detail so that those skilled in the art can easily understand and reproduce it through these examples.

1 is a block diagram of a device loss and recovery management system according to an embodiment. The first computing device 100 , the second computing device 200 , the third computing device 300 , and each helper device 400 are communicable computing devices used by different users, and are all unique phone numbers. It is a mobile device, such as a smartphone, that can provide a phone service to a user. At least some of the above computing devices may include a tag reader capable of reading information recorded in an electronic tag such as an NFC tag. In addition, the computing devices 100 , 200 , 300 , and 400 may include applications 110 , 210 , 310 , and 410 that are executed by a processor to provide a loss and recovery service to a user. These applications may or may not all be effectively the same application. In addition, each application may acquire tag information recorded in an electronic tag of another computing device by using a tag reader provided in the computing device.

The first computing device 100 is a device owned by the first user. The first user registers information for device recovery in the loss management server 500 in advance for fear of loss of the first computing device 100 , and provides related services when the first computing device 100 is actually lost receive The second computing device 200 is a device owned by the second user. The second user acts as a representative of the first user, and serves to help retrieve the first computing device 100 in case the first computing device 100 is lost. The third computing device 300 is a device owned by a third user. The third user is a learner who will acquire the lost first computing device 100 , and serves to find the first computing device 100 to the first user through a phone call with the second user. The first user and the second user are members subscribed to the loss and recovery service, and the third user may or may not be a member. And, the helper devices 400 are all devices owned by registered users (helpers). The helpers are responsible for directly finding the first computing device 100 in the place where the first computing device 100 was lost. When a helper finds the first computing device 100 that helper becomes a learner.

The lost management server 500 is a server system composed of one or more computing devices, and may be operated under various operating systems including or not included in a Windows-based operating system or MacOS, Java, UNIX, or Linux. Loss management server 500 is lost and retrieved to users in conjunction with at least some user devices 100, 200, 300, 400 or at least some applications 110, 210, 310, 410 through a communication network provide services. In addition, the loss management server 500 may also communicate data with the cooperative server 600 for one or more lost and retrieved services. The cooperative servers 600 may include, for example, a mobile communication company server, an insurance company server, and a cloud server. Meanwhile, the communication network may include a plurality of heterogeneous networks and may support a plurality of communication protocols. For example, the communication network supports at least some of the communication protocols such as TCP/IP, IPX, SPX, NetBIOS, Ethernet, ARCNET, Fiber Distributed Date Interface (FDDI), IEEE 802.11, IEEE 802.11a, and direct synchronization connections. .

2 is a flowchart of registering information for device collection according to an embodiment. The first application 110 generates device recovery information used to recover the first computing device 100 when the first user is concerned about loss when the actual loss occurs, and the generated device information is stored in the lost management server. A registration request is requested while transmitting to (500) (S100) (S110). The device recovery information includes device information and second user information, and may also include a password. The device information is information about the first computing device 100 and includes one or more unique identification information for identifying the first computing device 100 . The unique identification information may be an International Mobile Equipment Identity (IMEI). In addition, the device information may include information such as a device product name or product image, and tag information on an electronic tag such as an NFC tag provided inside the first computing device 100 or the outside of the first computing device 100 . A tag identifier (tag ID) recorded in an electronic tag such as a sticker-type NFC tag provided in the . The second user information includes a second user's phone number, and may also include a second user name or a second user ID. In addition, the password may be used to authenticate the user when the first user or the second user reports the loss or recovery of the first computing device 100 to the loss management server 500 .

3 illustrates a user interface screen of the first application for registering information for device collection. The first application 110 displays the user interface shown in FIG. 3 on the display of the first computing device 100 so that the first user can register the belongings concerned about loss. The first user may select a mobile phone from among various items such as a laptop, a mobile phone, a key, a wallet, and a handbag, and designate the first computing device 100 as a registered possession. When a mobile phone is designated, the first application 110 may check the product model name information of the first computing device 100 and automatically display the corresponding model image in the image area 10, and the product name recorded in the internal memory and By checking the serial number and registration code, it can be displayed in the general information area 20 . The special item area 30 is an area where a message is written by the first user, and the written message may be an acquisition reward message containing text content to reward the learner.

The agent contact area 40 is an area where the second user information is determined by the first user. The first user may directly input the second user information or may search for and designate a desired second user through the agent search function. The "Register" button on the lower left is for registering information for device retrieval to the lost management server 500, and when the "Register" button is touch input, the first application 110 includes data generated through FIG. The information for device recovery is transmitted to the loss management server 500 to request registration. As an example, when the “registration” button is touched and inputted, the first application 110 displays a pop-up window requesting the first user to input a password, and includes the password entered through this in the device recovery information to the lost management server ( 500) is sent. As another example, an area for inputting a password may be provided on the UI of FIG. 3 .

Loss management server 500 identifies the second user by checking the second user information in the device recovery information received from the first application 110, and the first to the second application 210 of the identified second user. A message is transmitted to inquire whether the user agrees to register the second user as an agent (S120). The second application 210 receives the consent confirmation request message from the loss management server 500 and displays the screen so that the second user can check it, and agrees to the loss management server 500 according to the second user's input A response message or a rejection response message is transmitted (S130). Lost management server 500 registers the device retrieval information received from the first application 110 in the database when the consent response message is received from the second application 210 (S140), and the device to the first application 110 Notifies that the registration of the recovery information has been normally completed (S150).

When the rejection response message is transmitted in S130, the loss management server 500 does not register the device recovery information received from the first application 110 in the database or deletes the second user information from the device recovery information in the database. Register and manage. In the latter case, the loss management server 500 requests and receives new second user information from the first application 110, and then includes it in the information for retrieving the device registered in the database through the consent of the new second user. can

Among the above-described processes, steps S120 and S130 may be omitted. That is, the loss management server 500 may directly register the information for device retrieval received in S110 to the database. On the other hand, when the second user is not a member, the loss management server 500 sends link information for downloading the second application 210 to the second computing device 200 before performing S120 through a text message such as SMS. and so on so that the second application 210 is installed on the second computing device 200 . In this case, a remote control program capable of remotely controlling the first computing device 100 from the second computing device 200 may be installed together. Alternatively, a remote control function may be included in the second application 210 . On the other hand, the first application 110 searches for the second user's phone number from the phone number list recorded in the internal memory of the first computing device 100 when the device recall information is generated, and the retrieved second user's phone number You can set the number to be the agent's phone number.

4 is a flowchart illustrating a device loss process according to an embodiment. The first user who has lost the first computing device 100 may report the loss of the first computing device 100 by online access (eg, web access) to the loss management server 500 through another electronic device. can At this time, the loss management server 500 provides the first user with a list of belongings of the first user registered in the database, and selects the first computing device that is the lost possession from the first user so as to report the loss. can The loss report is also possible by the second user who is the agent of the first user, and the second application 210 reports that the first computing device 100 is lost to the loss management server 500 according to the input command of the second user. can At this time, the loss management server 500 provides the second user with only a list of possessions for which the second user has agent authority among the registered possessions of the first user with the second application 210, and is lost from the second user. A loss report may be made by selecting the first computing device, which is a possessed possession.

The loss management server 500 receives a loss report of the first computing device 100 from the first user or the second application 210 (S200). In one embodiment, the loss management server 500 requests the input of a password for authentication of the loss report to the electronic device or the second application 210 accessed by the first user online, and the entered password is registered in the database. It is verified by comparing it with the password included in the device recovery information, and if the authentication is successful, it is regarded as a normal loss report and received and processed. When the report of loss is normally received, the loss management server 500 manages the loss of the first computing device 100 identified by the device recovery information (S210). The loss management server 500 transmits the device loss information to the helper applications 410 of the helper devices 400 located within a predetermined range in the place where the first computing device 100 is lost, so that the helpers can make the first computing Requests help for recovering the loss of the device 100 (S220).

The device loss information includes at least a part of product information (product name, product image, etc.) of the first computing device 100, lost time information, and lost location information, and may also include an acquisition compensation message. Here, the product information and the acquisition compensation message may be previously registered through FIG. 2 , and the lost time information and the lost location information are information to be acquired at or after the time when the first computing device 100 is lost. As an example, the first user or the second user may directly input the lost time information and the lost location information when reporting the loss of the first computing device 100 and provide the information to the loss management server 500 . Additionally, the device lost information may also include second user information, and only the second user's phone number may be included among the second user information.

On the other hand, each helper application 410 displays the device loss information received from the loss management server 500 on the screen so that the helper (user) can check it. Accordingly, the helpers can grasp information about the lost first computing device 100 through the device loss information, and are motivated to receive compensation when they find the first computing device 100, 1 Efforts can be made to find computing device 100 .

In addition, the loss management server 500 may request to stop the communication service of the first computing device 100 to the corresponding cooperative server 600 that is a communication company server that provides a communication service to the first computing device 100 (S230). . In this case, the loss management server 500 may request to stop the communication service of the first computing device 100 while transmitting the unique identification information of the first computing device 100 to the communication company server. Accordingly, the communication company server stops using the first computing device 100 so that the communication service is no longer used. For reference, when the unique identification information of the first computing device 100 transmitted to the communication company server for a communication service stop request is the IMEI given to the device itself, a malicious user sends the first computing device 100 to the USIM (Universal Even if only the Subscriber Identity Module) is replaced, the first computing device 100 cannot be used. This is because the use of the communication service is stopped with the device's own unique identification information.

In addition, the loss management server 500 may generate a lost certificate for proving that the first computing device 100 is lost and issue it to the electronic device or the second application 210 of the first user who has accessed online (S240). ). In one embodiment, the loss management server 500 generates and issues a lost certificate only when a preset loss certificate issuance condition is satisfied. The loss certificate issuance condition may be a case in which recovery of the first computing device 100 fails within a predetermined period from the time of loss, that is, a case in which a loss release request is not received from the first user or the second user.

In one embodiment, the loss management server 500 is the owner (first user) information of the first computing device 100, lost location information, lost time information, product information, loss progress result information, loss management server 500 ), a certificate of loss that includes at least some information among the name of the certification body, the contact information of the certification body, the serial number and the validity period of the certificate of loss. At this time, the loss management server 500 may generate a barcode or QR code for providing the above information according to a predefined code system and reflect it together in the lost certificate. The loss management server 500 issues the generated lost certificate to the electronic device or the second application 210 of the first user who has online access. Accordingly, the first user's electronic device or the second application 210 may store the issued lost certificate in the internal memory of the device or print it through an output device interworking with the device. The certificate of loss issued in this way can be used for submission to insurance companies for loss compensation, etc. Meanwhile, parts of S220, S230, and S240 of FIG. 4 described above may be omitted, and the order of operations may be reversed, and at least some steps may be simultaneously performed.

5 is a flowchart illustrating a device loss process according to another embodiment. S300, S310, S330, S380, and S390 of FIG. 5 are substantially the same as S200, S210, S220, and S230 of FIG. 4, and thus a redundant description thereof will be omitted. When the report of loss is normally received in S300, the loss management server 500 notifies the fact of the loss of the first computing device 100 to the first application 110 (S320). Accordingly, the first application 110 displays a message for informing the learner that the first computing device 100 is lost on the lock screen of the first computing device 100 (S340). In this case, the message displayed on the lock screen may include a request for tagging the electronic tag of the first computing device 100 to the learner to retrieve the first computing device 100 .

In one embodiment, the loss management server 500 generates a loss notification information including the acquisition compensation message and/or the second user information written by the first user in S320 and transmits it to the first application 110 . In this case, only the second user's phone number may be included in the second user information. And the first application 110 displays the loss notification information received from the loss management server 500 on the lock screen of the first computing device 100 in S340. Therefore, the learner can know that the reward is given when the loss notification information includes the acquisition reward message, and when the second user information is included, the second user is contacted by phone to contact the first computing device ( 100) can be found to the original owner.

In addition, the first application 110, when a loss notification is received from the loss management server 500, the first user's cloud from the first computing device 100 to the backup and / or deletion target data specified in advance by the first user Backup to storage and/or delete processing in the first computing device 100 (S350). That is, the first application 110 may perform deletion processing after backing up the deletion target data, may only perform backup processing, or may only perform deletion processing. To this end, the first application 110 receives and manages data to be backed up and/or deleted from the first user in advance, and provides a list of data to be backed up and/or deleted to the first user and on the list, the first user Data to be backed up and/or deleted can be designated and managed. Here, the data to be backed up and/or deleted may include photos, videos, contacts, documents, messages, and the like, as well as applications and programs.

After performing S340 and S350, the first application 110 may respond to the completion of processing according to the loss notification to the loss management server 500, and may switch the first computing device 100 from the active mode to the inactive mode. There is (S360) (S370). Here, the deactivation mode means that at least some functions of the first computing device 100 are deactivated, for example, it may mean a mode in which functions such as cellular communication, Bluetooth, and Wi-Fi are deactivated. In addition, although not shown in FIG. 5 , the first application 110 may provide the location information of the first computing device 100 to the loss management server 500 according to the loss notification from the loss management server 500 . have. The location information may be provided by being included in S360, but of course it may also be performed through a separate step. And the location information provided to the loss management server 500 may be included in the device lost information in S320 to be used. Meanwhile, at least some of S320 to S390 of FIG. 5 may be omitted, and the order of operations may be reversed, and some steps may be simultaneously performed.

6 is a flowchart of a device acquisition process according to an embodiment. 6 and 7 to be described later are all examples of a case in which a third user acquires the lost first computing device 100 . A sticker-type electronic tag may be attached to the outer surface of the first computing device 100 . This electronic tag is for the first computing device 100 to be recovered, and a phrase requesting tagging is printed to the learner. there may be Accordingly, the learner may check the sticker-type electronic tag and take action to find the lost item to the first user. Alternatively, the first computing device 100 may include an electronic tag for recovery of loss therein, and may display a message indicating that the device is lost on the lock screen. Through this, the learner can check the lock screen and take action to find the lost object to the first user.

After recognizing that the first computing device 100 is lost, the third user executes the third application 310 of the third computing device 300 and then transfers the third computing device 300 to the first computing device 100 . Tagging for electronic tags of Accordingly, the third application 310 obtains tag information from the electronic tag of the first computing device 100 when the third computing device 300 is tagged with respect to the electronic tag of the first computing device 100 (S400). . The tag information may include second user information, and the second user information may be only the second user's phone number. The third application 310 allows the third user to make a call to the second user by displaying the second user's phone number included in the tag information on the screen (S410). Accordingly, the second user can retrieve the first computing device 100 owned by the first user through a phone call with the third user. On the other hand, S410 and S420 may be performed in reverse order, and may be respectively performed regardless of precedence.

In addition, the third application 310 generates the device acquisition information when the tag information is obtained through S400 and transmits it to the loss management server 500 (S420). The device acquisition information may include at least a part of a tag ID included in the tag information, third user (acquirer) information, and an acquisition location and acquisition time of the first computing device 100 . Here, the acquisition location of the first computing device 100 may be the location of the third computing device 300 at the time when the tag information is acquired, and the acquisition time may be time information at the time when the tag information is acquired. can The lost management server 500 searches the database for device recovery information with a tag ID belonging to the device acquisition information received from the third application 310, and checks the second user information belonging to the retrieved device recovery information, The device acquisition information is transferred to the second application 210 of the confirmed second user (S430). In this case, the tag ID may be excluded from the device acquisition information delivered to the second application 210 . The second application 210 by displaying the device acquisition information received from the loss management server 500 on the screen, allowing the second user to grasp the fact that the first computing device 100 is acquired by the acquirer (S440) ).

Meanwhile, in FIG. 6 , the second user information may not be recorded in the electronic tag of the first computing device 100 . In this case, S410 is naturally omitted. In addition, the tag information may include unique identification information of the first computing device 100 . In this case, the device acquisition information may include unique identification information of the first computing device 100 instead of the tag ID, and the loss management server 500 may search for device recovery information with the unique identification information.

7 is a flowchart of a device acquisition process according to another embodiment. The third application 310 obtains tag information from the electronic tag of the first computing device 100 (S500). The tag information may include at least one of a tag ID and unique identification information of the first computing device 100 . The third application 310 transmits the tag information to the lost management server (S510). The lost management server 500 searches the database for device recovery information with the tag information received from the third application 310 (S520). That is, the device retrieve information including the tag ID of the tag information or the unique identification information of the first computing device 100 is searched. The lost management server 500 provides the second user information belonging to the retrieved device recovery information to the third application 310 (S530). In this case, only the second user phone number belonging to the second user information may be provided to the third application 310 . The third application 310 displays the second user information received from the loss management server 500 on the screen to allow the third user to make a call to the second user (S540).

In another embodiment, the loss management server 500 checks the device information in the device recovery information retrieved in S520, and the first application 110 of the first computing device 100 identified by the confirmed device information. 1 A fact of acquisition of the computing device 100 may be notified. Accordingly, the first application 110 receiving the acquisition notification displays the second user's phone number set as the agent's phone number from the phone number list recorded in the internal memory on the lock screen so that the third user can check it. In this embodiment, S530 and S540 may be omitted.

8 is a flowchart illustrating a device loss release process according to an embodiment. The loss management server 500 receives a report of collection of the first computing device 100 from the electronic device or the second application 210 accessed by the first user online (S600). In one embodiment, the loss management server 500 requests the input of a password for the recovery report authentication to the electronic device or the second application 210 accessed by the first user online, and the input password is registered in the database. It is verified by comparing it with the password included in the device recall information, and if the authentication is successful, it is regarded as a normal recall report and received and processed. When the recovery report is normally received, the loss management server 500 requests the communication company server to cancel the communication service suspension of the first computing device 100 ( S610 ). In this case, the loss management server 500 may request the release of the communication service stop of the first computing device 100 while transmitting the unique identification information of the first computing device 100 to the communication company server. Accordingly, the communication company server cancels the communication service stop of the first computing device 100 .

On the other hand, the first user designates not only a smartphone but also various belongings (belongings) concerned about loss, for example, laptops, keys, wallets, handbags, ID cards, etc. can be registered. In addition, when registering such possessions, the process of registering the second user as an agent and the process of the second user reporting loss on behalf of the first user may be omitted. This is because, of course, the first user can report the loss directly with his or her smartphone and can make a phone call with the acquirer. In addition, when the first user loses possessions serving as proof, such as an identification card, the loss management server 500 generates a lost certificate and/or temporary identification card for the identification card, etc. to be issued to the first application 110 . can The provisional ID card issuance condition may be a case in which ID card collection fails within a predetermined period from the time of loss, that is, a case in which a loss release request is not received from the first user.

9 is an exemplary configuration diagram of a computing device. The above-described methods may be performed by one or more computing devices, and specifically may be performed by one or more processors belonging to the computing device. As shown in FIG. 9 , the computing device may include a processor 710 , a memory 720 , a storage device 730 , an input/output interface 740 , and a communication interface 750 . The processor 710 may include a central processing unit (CPU), a graphic processing unit (GPU), or a microprocessor having one or more processing cores similar thereto. The memory 720 may store data, metadata, and a program for execution by the processor 710 . Memory 720 may include one or more volatile and non-volatile memories, and may be internal or distributed memory. The storage device 730 is a storage medium for storing data and commands, and may include non-transitory storage. The storage device 730 may include at least some of a hard disk drive, a flash memory, an optical disk, a magneto-optical disk, a universal serial bus (USB) drive, and the like.

Input/output interface 740 may include one or more input and/or output devices that allow a user to provide input, receive output, and send and receive data to and from other computing devices. The input/output interface 740 may be a mouse, keypad or keyboard, camera, optical scanner, network interface, modem, or other known I/O device, and may include a combination thereof. The input/output interface 740 may include at least some of a graphic engine, a display, one or more output drivers (eg, a display driver), one or more audio speakers, and one or more audio drivers. Communication interface 750 may provide one or more interfaces for network communication (eg, packet-based communication) between the computing device and one or more other computing devices. For example, the communication interface 750 may include a network interface controller (NIC) or network adapter for communicating over an Ethernet or other wire-based network, or a wireless NIC or wireless adapter for communicating over a wireless network such as Wi-Fi.

On the other hand, the bus may include hardware, software, or both for connecting components of the computing device to each other. For example, a bus can be an Accelerated Graphics Port (AGP) or other graphics bus, an Enhanced Industry Standard Architecture (EISA) bus, a front-side bus (FSB), a hypertransport (HT) interconnect, an Industry Standard Architecture (ISA) bus, an INFINIBAND interconnect , low-pin-count (LPC) bus, memory bus, MAC (Micro Channel Architecture) bus, PCI (Peripheral Component Interconnect) bus, PCIe (PCI-Express) bus, SATA (serial technology attachment) bus, VL (VESA Local) bus , VESA: Video Electronics Standard Association Local) bus, other suitable bus, or a combination thereof. The above configurations of FIG. 9 are exemplary, and the computing device may include at least a portion of the configurations of FIG. 9 , and other configurations not shown may be included as a matter of course.

So far, with respect to the present invention, the preferred embodiments have been looked at. Those of ordinary skill in the art to which the present invention pertains will understand that the present invention can be implemented in a modified form without departing from the essential characteristics of the present invention. Therefore, the disclosed embodiments are to be considered in an illustrative rather than a restrictive sense. The scope of the present invention is indicated in the claims rather than the foregoing description, and all differences within the scope equivalent thereto should be construed as being included in the present invention.

100: first computing device 110: first application
200: second computing device 210: second application
300: third computing device 310: third application
400: helper device 410: helper application
500: lost management server 600: cooperative server

Claims (10)

The first application executed by the processor of the first computing device with the phone function owned by the first user serves as an agent of the first user to retrieve the unique identification information of the first computing device and the first computing device in case of loss. transmitting device retrieval information including second user information to be performed to a lost management server to request registration;
Loss management server registering the information for retrieval of the device received from the first application in the database;
When the loss management server receives a report of loss for the first computing device from the second application executed by the processor of the first user or the second computing device connected online, the step of managing lost information for device recovery registered in the database ; and
The loss management server comprises: requesting to stop using the first computing device to the related communication company server of the first computing device to which the loss report is received;
A smartphone loss and recovery management method comprising a. The method of claim 1, wherein the step of registering information for device collection comprises:
Confirming the second user information in the device recovery information received from the first application, and requesting whether to consent to the agent for the first user with the second application of the confirmed second user, and only when consent is obtained, the second user information Smartphone loss and collection management method that registers the included device recovery information in the database. The method of claim 1,
Loss management server transmitting the loss notification information to the first application of the lost first computing device; and
The first application comprising: displaying the loss notification information received from the loss management server on the lock screen of the first computing device;
Smartphone loss and recovery management method further comprising. 4. The method of claim 3,
Loss notification information includes the acquisition compensation message and the second user phone number belonging to the second user information, the smartphone loss and recovery management method. The method of claim 1,
Backing up and/or deleting the first application data to be backed up and/or deleted from the first computing device to the cloud storage of the first user specified by the first user when the loss notification information is received from the loss management server;
Smartphone loss and recovery management method further comprising. The method of claim 1,
When a loss report is received, the loss management server transmits device loss information on the first computing device to the computing devices of members within a predetermined range from the lost location of the first computing device to request assistance in recovering the loss;
Smartphone loss and recovery management method further comprising. The method of claim 1,
The loss management server generates a loss certificate for proof of loss of the first computing device when a report of loss is received, and provides it to the access device of the first user or a smartphone loss and recovery management method for providing as a second application. The method of claim 1,
The third application executed by the processor of the third computing device owned by the learner who has acquired the first computing device is the second user's phone from the electronic tag through the tagging of the third computing device to the electronic tag of the first computing device. acquiring a number to enable a learner to make a phone call with a second user;
Smartphone loss and recovery management method further comprising. The method of claim 1,
The third application executed by the processor of the third computing device owned by the learner who has acquired the first computing device is the unique identification information of the first computing device through the tagging of the third computing device with the electronic tag of the first computing device. Transmitting to a lost management server to obtain a; and
The lost management server searches for device recovery information with the unique identification information received from the third application, and provides a second user phone number belonging to the second user information of the retrieved device recovery information to a third application;
Smartphone loss and recovery management method further comprising. The method of claim 1,
The third application executed by the processor of the third computing device owned by the learner who has acquired the first computing device is the unique identification information of the first computing device through the tagging of the third computing device with the electronic tag of the first computing device. acquiring, generating acquisition information including acquisition location, acquisition time, and acquirer information, and transmitting the acquired unique identification information and generated acquisition information to a loss management server; and
The loss management server retrieves the device recovery information of the first user with the unique identification information received from the third application, identifies the second user through the retrieved device recovery information, and returns to the second application of the identified second user. providing acquisition information;
Smartphone loss and recovery management method further comprising.

Images