KR20210132462A - Smartphone loss and found management method based on blockchain - Google Patents

Abstract

Disclosed is a blockchain-based device loss and collection management method. The method includes: a step in which a first computing device having a telephone function of a first user generates information for device collection, including unique identification information of the first computing device and information on a second user acting as a representative for the first user for collecting the first computing device when the device is lost, as a transaction to submit the same to a blockchain network; a step in which the blockchain network registers the information for device collection in a smart contract after verifying the transaction; a step in which a second computing device of the second user generates a transaction for reporting the loss of the first computing device to submit the same to the blockchain network; and a step in which the blockchain network causes a loss event for the first computing device after verifying the transaction for reporting the loss of the same. Therefore, the present invention is capable of providing a beneficial service to a user who has lost his or her smartphone.

Description

Blockchain-based device loss and recovery management method {Smartphone loss and found management method based on blockchain}

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 technical method capable of providing a useful service to a user in relation to a user's loss of a smartphone.

A block chain-based smartphone loss and collection management method according to an aspect is a first computing device having a phone function owned by a first user to recover the unique identification information of the first computing device and the first computing device when lost 1 The step of generating device recovery information including the second user information to act as a user’s agent as a transaction and submitting it to the blockchain network, registering the device recovery information in the smart contract after the blockchain network verifies the transaction , the second computing device of the second user generates a transaction for reporting the loss of the first computing device and submits it to the blockchain network, and after the blockchain network validates the transaction for reporting the loss of the first computing device to the first computing device It may include the step of generating a lost event for the.

In the blockchain-based smartphone loss and recall management method, the loss management server polls whether an event occurs and requests the communication service stop of the first computing device to be stopped by the communication company server that provides communication service to the first computing device according to the detected loss event It may further include the step of

In the device recovery information registration step, the blockchain network generates a consent request event for registration after the second user agrees to the device recovery information after transaction verification, and the second computing device polls whether the event occurs to request consent Detect an event, display at least a part of device recovery information on the display of the second computing device according to the detection of the consent request event, and obtain the second user's consent information for device recovery information according to the second user's consent input Creating a transaction and submitting it to the blockchain network, and the blockchain network may include registering the device recovery information agreed by the second user to the smart contract after the transaction is verified.

The block chain-based smartphone loss and collection management method may further include displaying, on the lock screen, loss notification information confirmed through the detected loss event by polling whether the first computing device has occurred.

The loss notification information may include a second user phone number belonging to the acquisition reward message and the second user information.

The block chain-based 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 computing device detects a loss event and / or may further include the step of deleting.

In the blockchain-based smartphone loss and recall management method, the computing device for each user, except for the first user, polls whether an event occurs and displays the loss notification information confirmed through the detected loss event on the screen, but The method may further include displaying only when the lost location of the first computing device is within a predetermined range from the current location of the user of the computing device.

The blockchain-based smartphone loss and recall management method generates an event for issuing a certificate of loss if the blockchain network does not submit a transaction for canceling the report of loss from the first computing device or the second computing device within a predetermined time after the occurrence of the loss event. step, and the loss management server polls whether an event has occurred, and generates a lost certificate for proof of loss of the first computing device according to the detected event for issuing a lost certificate and issuing it to the first user or the second user can do.

In the blockchain-based smartphone loss and collection management method, the third computing device owned by the learner who has acquired the first computing device acquires the second user's phone number from the electronic tag through the tagging of the first computing device. It may further include the step of providing to the learner.

The block chain-based smartphone loss and collection management method is a third computing device owned by the learner who has acquired the first computing device through tagging of the electronic tag of the first computing device, unique identification information of the first computing device from the electronic tag obtaining, by the third computing device, generating device acquisition information including the acquired unique identification information of the first computing device as a transaction and submitting it to the blockchain network, the blockchain network generating an acquisition event after verifying the transaction The method may further include a step, and the second computing device polls whether the event occurs to detect the acquisition event, and displays device acquisition information confirmed through the detected acquisition event on the screen to provide the second user.

The device acquisition information may further include at least a portion of the acquisition location, acquisition time, and acquirer information of the first computing device.

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

1 is a block diagram of a block chain-based 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 the first computing device.
4 is a flowchart of registering information for device collection according to another embodiment.
5 to 8 are flowcharts of a device loss process according to an embodiment.
9 is a flowchart of a device acquisition process according to an embodiment.
10 is a flowchart illustrating a device loss release process according to an embodiment.
11 is a block diagram of a computing device according to an 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 through these examples.

A blockchain-based device loss and recovery management system utilizes the decentralized nature of the blockchain. The blockchain guarantees the integrity of the information contained in the blocks agreed upon among the participants on the network, and selects block producers to sustain a decentralized network without administrators. In one embodiment, the device loss and recovery management system uses Ethereum as a blockchain. Unlike Bitcoin, which supports Turing incomplete scripts that can only perform simple operations, Ethereum supports the creation and distribution of smart contracts for DApp (Decentralized Application) development. Smart contracts written in Solidity, a Turing-complete language, and recorded on a distributed ledger ensure automated execution and integrity of results. Smart contracts written in Solidity are compiled and stored in the form of Ethereum virtual machine byte code (EVM Byte Code) to ensure the integrity of the contract contents.

Ethereum uses an Elliptic Curve Digital Signature Algorithm (ECDSA) digital signature to authenticate the account holder and verify the authentication and integrity of the transaction. ECDSA is based on the safety of ECDLP (Elliptic Curve Discrete Logarithm Problem), which is a discrete logarithmic problem on the elliptic curve. In addition, elliptic curve cryptography (ECC) such as ECDSA has the advantage of providing high security with a smaller number of bits compared to other encryption algorithms.

Additionally, a metamask will be described. A blockchain wallet not only manages the balance of a blockchain account, but also stores the user's private key and creates and broadcasts a transaction on behalf of the user. In this sense, wallets are the easiest way for regular users to access the blockchain network. MetaMask is the most representative web-based wallet extension that runs in the browser and currently supports Chrome, Firefor, Opera, and Brave Browser, and supports Ethereum account creation and linkage, electronic signatures, and transaction creation. Therefore, users can easily access smart contracts on the blockchain by using Metamask on the browser in addition to the DApp.

Users can join the network as a blockchain node through the Ethereum client to access the Ethereum network. Alternatively, you can use MetaMask, which uses Infura API, a cloud service for network access to wallet users. When using MetaMask, users can connect to the Ethereum network as they do not directly operate nodes, operate smart contracts, and receive results. For reference, Ethereum supports the web.JS standard API for communicating with the Ethereum network using JSON-RPC in web applications, and MetaMask provides it to the running browser itself.

1 is a block diagram of a block chain-based 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. And each of the above computing devices 100, 200, 300, 400 may include one or more applications to be executed by a processor to provide a loss and recovery service to a user, including a DApp and/or a metamask. can Such computing devices 100 , 200 , 300 , 400 are capable of data communication with the loss management server 500 as well as access to the block chain network 700 .

The first computing device 100 is a device owned by the first user. The first user is concerned about the loss of the first computing device 100 and registers the device recovery information in the smart contract for loss and recovery distributed on the block chain network 700 in advance, and the first computing device 100 In the event that the is actually lost, the relevant service is provided through the automatic execution of the smart contract. Here, the smart contract for loss and recovery may be prepared and distributed in advance by the operator operating the loss management server 500, and a DApp or metamask for smart contract connection may also be provided by the above operator. The second computing device 200 is a device owned by the second user. The second user is a representative of the first user, and serves to help retrieve the first computing device 100 when 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. And the helper devices 400 are all devices owned by users (helpers) who want to help find the lost first computing device 100 . Of course, when the helper finds the first computing device 100 , the 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. The loss management server 500 may become a block chain node by itself and connect to the block chain network 700 , or may be connected to a separate block chain node to access the block chain network 700 . The loss management server 500 may also communicate data with one or more cooperative servers 600 for loss and recovery services. The cooperative servers 600 may include, for example, a mobile communication company server, an insurance company server, and a cloud server. Meanwhile, a communication network for communication between computing devices 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 computing device 100 generates, as a transaction, device recovery information used to recover the first computing device 100 when the first user is concerned about loss, as a transaction, and blocks the generated transaction. It is transmitted and submitted to the chain network 700 (S100). After verifying the transaction submitted through S100, the blockchain network 700 calls the smart contract and registers device recovery information in the smart contract (S110) (S120).

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) or a serial number registration code. 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 . In addition, the second user information includes a second user phone number, and may also include a second user name or a second user ID. In addition, the password may be used for report authentication when the first user or the second user reports loss or collection of the first computing device 100 .

3 illustrates a user interface screen of the first computing device for registering information for device collection. The user interface of FIG. 3 may be provided by a DApp or other application running on the first computing device 100 . The first computing device 100 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 computing device 100 may check the model name information of the device and automatically display the corresponding model image in the image area 10, and the product name and manufacturing number and registration code recorded in the internal memory. It can be checked and 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 the device recovery information to the loss management server 500, and when the “Register” button is touch-inputted, the first computing device 100 includes the data generated through FIG. information for device recall can be generated as a transaction and submitted to the blockchain network 700 . As an example, when a “registration” button is touched, the first computing device 100 displays a pop-up window requesting the first user to input a password, and through this, information for device recovery including the input password is generated as a transaction. do. As another example, an area for inputting a password may be separately provided on the UI of FIG. 3 .

4 is a flowchart of registering information for device collection according to another embodiment. S200 and S210 of FIG. 4 are the same as S100 and S110 of FIG. 2 . The blockchain network 700 generates a consent request event for obtaining the consent of the second user for the registration of the second user information included in the device recovery information after transaction verification (S220). Accordingly, the second computing device 200 detects a consent request event. In other words, a blockchain-based app detects newly generated events by periodically polling whether there is a newly generated event in the block chain. That is, the blockchain-based app of the second computing device 200 detects a consent request event through periodic polling. When the second computing device 200 detects the consent request event, it displays at least a part of the device recovery information confirmed through the event on the screen so that the second user can check it ( S230 ). Accordingly, when the second user confirms the screen content and agrees to become the agent of the first user, the second user can respond to consent. When the second user inputs the consent response, the second computing device 200 generates the consent information of the second user as a transaction and submits it to the blockchain network (S240). After verifying the transaction submitted through S240, the blockchain network 700 calls the smart contract and registers the device recovery information and the second user's consent information to the smart contract (S250) (S260).

5 to 8 are flowcharts of a device loss process according to an embodiment. The first user who has lost the first computing device 100 may have a second user who is his/her representative report the loss, and the second computing device 200 according to the operation of the second user (100) creates a transaction to report device loss report information for reporting that it is lost and submits it to the block chain network 700 (S300). The device loss report information may include device information about the first computing device 100 , and may include at least a portion of lost location information and a password input from the second user. Here, the device information may be provided in advance from the first user and stored inside the second computing device 200 , and is obtained from the device recovery information confirmed through the above-described consent request event to obtain the second computing device 200 . ) may be stored in advance. Alternatively, the first user may directly report the loss using another electronic device, and may report the loss as described above using a metamask.

After verifying the transaction generated by the first user or the second user, the blockchain network 700 calls the smart contract to generate a lost event (S310) (S320). In S320, the block chain network 700 identifies the device recovery information previously registered as device information included in the device loss report information, and compares whether the password included in the device loss report information and the password included in the device recovery information match. , a loss event can be generated only when they match.

In FIG. 6 , the first computing device 100 detects a lost event by periodically polling whether an event newly generated by a smart contract in the block chain exists ( S400 ). The first computing device 100 checks the loss notification information through the detected loss event, and displays the checked loss notification information on the lock screen of the first computing device 100 . The loss notification information may include at least a part of device recovery information, and may include second user information and/or an acquisition reward message. Here, only the second user's phone number may be included in the second user information. In addition, the loss notification information may include content requesting the acquirer to tag the electronic tag of the first computing device 100 .

Additionally, the first computing device 100 confirming the loss notification information backs up and/or data to be deleted in advance by the first user from the first computing device 100 to the cloud storage of the first user and/or A deletion process may be performed in the first computing device 100 (S420). That is, the first computing device 100 may perform a deletion processing after backing up the deletion target data, may only perform a backup processing, or may only perform a deletion processing. To this end, the first computing device 100 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 provides the first user on the list. Data to be backed up and/or deleted can be designated and managed by the user. 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.

The first computing device 100 generates backup/deletion completion information as a transaction after processing S420 is completed and submits it to the blockchain network 700 (S430). However, S430 may be omitted. The first computing device 100 may switch the first computing device 100 from the active mode to the inactive mode after completing S420 or after completing S430 ( S440 ). Here, the inactive mode refers to a mode in which at least some functions of the first computing device 100 are deactivated, for example, a mode in which functions such as cellular communication, Bluetooth, and Wi-Fi are deactivated.

The blockchain network 700 generates a communication stop event for stopping the mobile communication service for the first computing device 200 by calling the smart contract after verifying the transaction in S430 (S450) (S460). The loss management server 500 detects a communication stop event by periodically polling whether there is an event newly generated by a smart contract in the block chain, and provides a communication service to the first computing device 100 through the detected communication stop event. The provided mobile carrier information is checked, and a mobile communication service stop for the first computing device 100 is requested to the mobile carrier server according to the checked mobile carrier information (S470). Alternatively, the loss management server 500 may detect a loss event and request a mobile communication service stop for the first computing device 100 from the mobile communication company server.

The mobile communication company server stops the service so that the first computing device 100 can no longer use the mobile communication service according to the mobile communication service stop request. For reference, when the unique identification information of the first computing device 100 delivered to the communication company server for a mobile communication service stop request is the IMEI given to the device itself, a malicious user sends the USIM ( Even if only the Universal 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 FIG. 7 , each helper device 400 detects a lost event by periodically polling whether an event newly generated by a smart contract in the block chain exists ( S500 ). The helper device 400 checks the loss notification information through the detected loss event, and whether the lost location information of the first computing device 100 belonging to the checked loss notification information is within a predetermined range from the current location of the user (helper) It is determined whether or not the information is lost, and only when it is within a predetermined range as a result of the identification, information about the loss is displayed on the screen (S510) (S520).

In FIG. 8 , the second computing device 200 generates lost certificate issuance request information as a transaction according to the operation of the second user and submits it to the blockchain network 700 ( S600 ). After verifying the transaction submitted in S600, the blockchain network 700 calls the smart contract to generate a lost certificate issuance request event (S610) (S620). In one embodiment, the block chain network 700 generates a loss certificate issuance request event only when a loss release report is not made within a predetermined time from the time when the loss event is generated. The loss management server 500 detects a lost certificate issuance request event by periodically polling whether there is an event newly generated by a smart contract in the block chain, and first user information confirmed through the detected lost certificate issuance request event and A certificate of loss in which information about the first computing device 100 is reflected is generated as a transaction and submitted to the blockchain network 700 (S630). After verifying the transaction submitted in S630, the blockchain network 700 calls the smart contract to generate a lost certificate issuance event (S640) (S650). The second computing device 200 detects a lost certificate issuance event by periodically polling whether there is an event newly generated by a smart contract in the block chain, and obtains a lost certificate provided through the detected lost certificate issuance event (S660) ).

Among the above procedures, steps S600 and S660 performed by the second computing device 200 may be performed by another electronic device used by the first user, and may be performed through a metamask. On the other hand, 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 to operate A certificate of loss including at least some information among the name of the certification authority, the contact information of the certification authority, the serial number of the certificate of loss and the validity period may be generated. Here, the first user information, loss location information, loss time information, product information, and loss progress result information may be confirmed through a loss certificate issuance request event. And 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.

9 is a flowchart of a device acquisition process according to an embodiment. 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.

If a third user (acquirer) recognizing that the first computing device 100 is lost, tagging the third computing device 300 with respect to the electronic tag of the first computing device 100, the third computing device 300 ) obtains tag information from the electronic tag of the first computing device 100 (S700). The tag information may include second user information, and the second user information may be only the second user's phone number. When the tag information includes the second user information, the third computing device 300 displays the second user information on the screen so that the third user can make a call to the second user.

When the tag information is obtained from the first computing device 100, the third computing device 300 may generate the device acquisition information as a transaction and submit it to the blockchain network 700 (S710). The device acquisition information may include at least a part of a tag ID (or unique identification information of the first computing device) included in the tag information, 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. have. And the acquirer information may include the acquirer's phone number.

After verifying the transaction submitted in S710, the blockchain network 700 calls a smart contract according to the registered device recall information identified by the tag ID included in the device acquisition information or the unique identification information of the first computing device. A learning event for the first computing device is generated (S720) (S730). The second computing device 200 detects the acquisition event by periodically polling whether an event newly generated by the smart contract in the block chain exists, and displays at least a portion of the device acquisition information confirmed through the detected acquisition event on the screen. It is provided to the second user (S740).

10 is a flowchart illustrating a device loss release process according to an embodiment. The second computing device 200 generates a transaction for reporting device loss of the first computing device 100 and submits it to the blockchain network 700 ( S800 ). The blockchain network 700 generates a loss release event for the first computing device 100 after verifying the transaction (S810) (S820). The loss management server 500 periodically polls whether there is an event newly generated by the smart contract in the block chain and checks the mobile operator information about the first computing device 100 recovered through the detected loss release event, A request is made to resume the mobile communication service for the first computing device 100 to the mobile carrier server according to the confirmed mobile carrier information (S830). Meanwhile, in FIG. 10 , the role of the second computing device 200 may be replaced with the first computing device 100 or another electronic device of the first user.

On the other hand, the first user designates not only a smartphone but also various belongings (belongings) concerned about loss, such as a laptop, keys, wallets, handbags, ID cards, etc. can register. 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 may generate a lost certificate and/or temporary identification card for the identification card, etc. to be issued to the first user. . 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.

11 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. 11 , the computing device may include a processor 910 , a memory 920 , a storage 930 , an input/output interface 940 , and a communication interface 950 . The processor 910 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 920 may store data, metadata, and a program for execution by the processor 910 . Memory 920 may include one or more volatile and non-volatile memories, and may be internal or distributed memory. The storage device 930 is a storage medium for storing data and commands, and may include non-transitory storage. The storage device 930 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 940 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 940 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 940 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 950 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 950 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. 11 are exemplary, and the computing device may include at least a portion of the configurations of FIG. 11 , and other configurations not shown may be included as a matter of course.

Meanwhile, the user devices 100 , 200 , 300 and 400 , which are one of the operating subjects in FIGS. 2 and 4 to 11 described above, may be specifically performed by a blockchain-based application executed in the device. 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 200: second computing device
300: third computing device 400: helper device
500: lost management server 600: cooperative server
700: Blockchain Network

Claims (11)

The first computing device with the first user-owned phone function includes device information including unique identification information of the first computing device and second user information to act as an agent of the first user for retrieval of the first computing device in case of loss. generating acceptance information as a transaction and submitting it to a blockchain network;
After the blockchain network verifies the transaction, registering information for device recovery in the smart contract;
generating, by the second computing device of the second user, a transaction for reporting the loss of the first computing device and submitting it to the blockchain network; and
The block chain network may include: generating a loss event for the first computing device after verifying the transaction for reporting the loss;
A blockchain-based smartphone loss and recovery management method, including The method of claim 1,
The loss management server polls whether an event occurs and requests a communication service stop of the first computing device to a communication company server that provides a communication service to the first computing device according to the detected lost event;
A blockchain-based smartphone loss and recovery management method further comprising a. The method according to claim 1, wherein in the device collection information registration step:
The block chain network may include: generating a consent request event for registration after the second user's consent for device recovery information after transaction verification;
The second computing device detects a consent request event by polling whether an event has occurred, and displays at least a portion of device recovery information on the display of the second computing device according to the consent request event detection, according to the consent input of the second user generating a second user's consent information for device recovery information as a transaction and submitting it to a blockchain network; and
The blockchain network includes: registering information for device retrieval agreed by the second user to the smart contract after transaction verification;
A blockchain-based smartphone loss and recovery management method, including The method of claim 1,
The first computing device polling whether an event has occurred and displaying information about the loss notification confirmed through the detected loss event on the lock screen;
A blockchain-based smartphone loss and recovery management method further comprising a. 5. The method of claim 4,
Loss notification information includes an acquisition reward message and a second user phone number belonging to the second user information. A block chain-based smartphone loss and recovery management method. 5. The method of claim 4,
backing up and/or deleting, by the first computing device, data to be backed up and/or deleted predetermined by the first user from the first computing device to the cloud storage of the first user when a loss event is detected;
A blockchain-based smartphone loss and recovery management method further comprising a. The method of claim 1,
The computing device for each user except the first user polls whether an event has occurred and displays the loss notification information confirmed through the detected loss event on the screen, but the location of the loss of the first computing device confirmed through the loss notification information is the corresponding computing device displaying only when it is within a predetermined range from the user's current location;
A blockchain-based smartphone loss and recovery management method further comprising a. The method of claim 1,
The block chain network may include: generating an event for issuing a certificate of loss if a transaction for releasing a report of loss is not submitted from the first computing device or the second computing device within a predetermined time after the occurrence of the loss event; and
The loss management server polls whether an event occurs, and according to the detected event for issuing a lost certificate, generating a lost certificate for proof of loss of the first computing device and issuing it to a first user or a second user;
A blockchain-based smartphone loss and recovery management method further comprising a. The method of claim 1,
The third computing device owned by the learner who has acquired the first computing device includes: obtaining the second user's phone number from the electronic tag through tagging of the first computing device and providing the second user's phone number to the learner;
Smartphone loss and recovery management method further comprising. The method of claim 1,
acquiring, by the third computing device owned by the learner who has acquired the first computing device, unique identification information of the first computing device from the electronic tag through tagging of the first computing device;
generating, by the third computing device, device acquisition information including the acquired unique identification information of the first computing device as a transaction and submitting it to the blockchain network;
The blockchain network generates an acquisition event after transaction verification; and
The second computing device detects a learning event by polling whether an event has occurred, and provides device acquisition information confirmed through the detected acquisition event to the second user by displaying the screen;
Smartphone loss and recovery management method further comprising. 11. The method of claim 10,
The device acquisition information includes at least a portion of the acquisition location, acquisition time, and acquirer information of the first computing device.

Images