User equipment using block chain, block chain system and product information management method thereof

Through the blockchain system, the high maintenance cost and low security problems of centralized authentication methods are solved, transparent tracking and security management of product ownership is achieved, and resistance to counterfeit products and hacker attacks is enhanced.

CN110557257BActive Publication Date: 2024-11-22SAMSUNG ELECTRONICS CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN201910481816.3
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2018-06-04
Filing Date
2019-06-04
Publication Date
2024-11-22
Estimated Expiration
2039-06-04

AI Technical Summary

Technical Problem

The existing centralized authentication methods have high maintenance costs, low security and vulnerability in product certification, especially in the face of flooding of counterfeit products and hacker leaks, which are difficult to effectively manage and recover.

Method used

Using a blockchain system to manage product information, through communication between user equipment and blockchain participants, use the founding block, ownership record block, ownership registration block and ownership transfer block to record and transfer product ownership, reducing the amount of product ownership to a separate authentication server. Reliance, improves security and transparency.

Benefits of technology

Reduces maintenance costs, improves security, and allows transparent tracking of product ownership transfer paths, enhancing resistance to counterfeit products and hacker attacks.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN110557257B_ABST
    Figure CN110557257B_ABST
Patent Text Reader

Abstract

The present application provides a product for participating in a block chain system, a user device for participating in a block chain system, a method for managing product information, and a non-transitory computer-readable storage medium configured to store block chain data. The product for participating in a block chain system includes: a network interface configured to communicate with a participant of the block chain system using a first network to share block chain data, the block chain data including at least one of an ownership record block and an ownership registration block for a product; an output circuit configured to output a notification signal; and a processor configured to determine whether the ownership of the product is registered in the block chain data during the boot operation of the product through the network interface, and control the output circuit to output a message requesting registration of the ownership of the product based on determining that the ownership of the product is not registered in the block chain data.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of Korean Patent Application No. 10-2018-0064479 filed on June 4, 2018 in the Korean Intellectual Property Office, the disclosure of which is incorporated herein by reference in its entirety. Technical Field

[0003] One or more exemplary embodiments of the present disclosure relate to a user device, a blockchain system and a product information management method thereof, and more particularly, to a user device, a blockchain system and a product information management method thereof for managing product information using blockchain. Background Art

[0004] Since the authenticity of products produced and sold by manufacturers may be directly related to the quality of the products, and the proliferation of counterfeit products may cause considerable damage to manufacturers, various products including electronic devices are subject to authenticity authentication before being sold and used by consumers.

[0005] Centralized authentication methods have been used for existing product authentication, in which a single authentication server authenticates each of multiple products. When such a centralized authentication method is used, it costs a lot of money to manage, maintain, and repair the authentication server, and it is difficult to restore the authentication information when it is leaked by various hackers, etc., and it is vulnerable to distributed denial of service (DDoS) attacks.

[0006] Therefore, there is a need for an authentication method and / or a product information management method that can solve the problems of the conventional centralized authentication method. Summary of the invention

[0007] One or more example embodiments provide a method and apparatus capable of reducing maintenance costs, improving security, and transparently tracking a transfer path of product ownership in a computing system, a block chain system including the same, and a product information management method thereof.

[0008] According to one aspect of an example embodiment, a product for participating in a block chain system is provided, the product comprising: a network interface configured to communicate with a participant of the block chain system using a first network to share block chain data, the block chain data comprising at least one of an ownership record block and an ownership registration block for a product; an output circuit configured to output a notification signal; and a processor configured to determine whether the ownership of the product is registered in the block chain data during a boot operation of the product through the network interface, and to control the output circuit to output a message requesting registration of the ownership of the product based on a determination that the ownership of the product is not registered in the block chain data.

[0009] According to another aspect of the example embodiment, a user device for participating in a block chain system is provided, the user device being configured to communicate with a product via a first network, the user device comprising: at least one processor; and at least one memory configured to store instructions, which, when executed by the at least one processor, causes the at least one processor to perform the following steps: receiving block chain data from at least one block chain participant connected to the user device via a second network; and requesting a first signer and the product to sign a first information including a first public key corresponding to the user device.

[0010] According to another aspect of an example embodiment, a method for managing product information using a block chain system is provided, the method comprising the following steps: generating a genesis block of block chain data used in the block chain system, the genesis block being generated based on a public key of a manufacturer of a product; generating a first payload including a first signature of the manufacturer for the public key of the product; generating an ownership record block of the product based on the first payload and an additional signature of the product for the first payload; and sending a link request message including the ownership record block to a participant of the block chain system.

[0011] According to another aspect of the example embodiment, a method for managing product information by a participant in a block chain system is provided, the method comprising the following steps: receiving, by a participant, a link request message including a new block, the new block including a first signature of a first signer for a first public key corresponding to a user device and a second signature for a product of the first public key corresponding to the user device; verifying the new block by the participant using block chain data stored in the participant; and linking the new block to the block chain data by the participant based on the verification of the new block.

[0012] According to another aspect of the example embodiment, there is provided a non-transitory computer-readable storage medium constructed to store block chain data, the block chain data being used to manage information about ownership of a product through user devices and participants of a block chain system, wherein the block chain data comprises: a genesis block generated by a manufacturer of the product and including a public key of the manufacturer; and a product ownership record block generated by the manufacturer of the product and including a first signature of the manufacturer for the public key of the product and a second signature of the product for warranty information of the product. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] These and / or other aspects of the present disclosure will become clear and more readily understood from the following description of example embodiments taken in conjunction with the accompanying drawings, in which:

[0014] Figure 1 is a diagram of a blockchain system according to an example embodiment;

[0015] Figure 2A is a diagram of blockchain data according to an example embodiment;

[0016] Figure 2B shows types of data blocks according to example embodiments;

[0017] Figure 3 is a diagram showing a construction of a founding block according to an example embodiment;

[0018] Figure 4 is a flowchart of a method of generating a genesis block according to an example embodiment;

[0019] Figure 5 is an illustration of products and manufacturers according to example embodiments;

[0020] Figure 6 is a diagram showing the construction of an ownership record block according to an example embodiment;

[0021] Figure 7 is a flowchart of a method of generating an ownership record block according to an example embodiment;

[0022] Figure 8 is a flow chart of a method of managing product information in a user device according to an example embodiment;

[0023] Fig. 9 is a diagram of a product, user equipment, and manufacturer according to an example embodiment;

[0024] Fig.10 is a diagram showing a construction of a property registration block according to an example embodiment;

[0025] Fig.11A and Fig. 11B is a flow chart of a method of generating a title registration block according to an example embodiment;

[0026] Fig. 12A and Fig. 12B is a diagram of a product, a first user device, and a second user device according to an example embodiment;

[0027] Fig.13 is a diagram showing the construction of an ownership transfer block according to an example embodiment;

[0028] FIG. 14A to FIG. 14C is a flow chart of a method of generating an ownership transfer block according to an example embodiment;

[0029] Fig.15 is a flow chart of a target verification method according to an example embodiment;

[0030] Fig.16A is a diagram of block chain data for explaining a target verification sequence in an ownership registration operation according to an example embodiment;

[0031] Fig. 16B is a diagram of block chain data for explaining a target verification sequence in an ownership transfer operation according to an example embodiment;

[0032] Fig.17 is a flow chart of a blockchain participation process according to an example embodiment;

[0033] Fig.18 is a flow chart of a new block verification method according to an example embodiment;

[0034] Fig.19A is a flow chart of a block chain participation process in an ownership record operation according to an example embodiment;

[0035] Fig.19B is a flow chart of a blockchain participation process in a title registration operation according to an example embodiment;

[0036] Fig.19C is a flow chart of a blockchain participation process in an ownership transfer operation according to an example embodiment;

[0037] Fig. 20 is a diagram of a blockchain system according to an example embodiment;

[0038] Fig.21 is a flowchart of a product booting method according to an example embodiment; and

[0039] Fig. 22 is a flow chart of a manufacturer's product repair process according to an example embodiment. DETAILED DESCRIPTION

[0040] Hereinafter, embodiments will be described in detail with reference to the accompanying drawings.

[0041] Figure 1 A block chain system 10 according to an example embodiment is shown. The block chain system 10 may include a product 100, a user device 200, a first participant (Participant_1) 300_1, a second participant (Participant_2) 300_2 ... and an Nth participant (Participant_3) 300_N (where N is a natural number) and a manufacturer 400 (or a manufacturer's device). Hereinafter, the terms "manufacturer" and "manufacturer's device" may be used interchangeably.

[0042] The product 100 may include any product that can communicate with the user device 200, such as an electronic product and an automotive product. For example, the product 100 may include, but is not limited to, household appliances, medical devices, navigation devices, automotive infotainment devices, marine electronic devices, avionics devices, security devices, industrial or household robots, automated teller machines (ATMs) of financial institutions, point of sale (POS) or Internet of Things (IoT) of stores, street lights, fitness devices, or electronic devices. For example, household appliances may include, but are not limited to, televisions (TVs), digital versatile disc (DVD) players, audio players, refrigerators, air conditioners, vacuum cleaners, ovens, microwave ovens, washing machines, air purifiers, set-top boxes, home automation control panels, security control panels, TV boxes, game consoles, electronic dictionaries, electronic keys, cameras, electronic photo frames, electric stoves, rice cookers, multi-purpose cookers, or coffee makers. Medical devices may include heart rate monitors, blood pressure monitors, magnetic resonance imaging (MRI) devices, or ultrasound devices. The electronic device may include a smartphone, a tablet personal computer (PC), a desktop PC, a notebook PC, a netbook computer, a workstation, a server, a personal digital assistant (PDA), a portable multimedia player (PMP), an MP3 player, a camera, a smart watch, or a solid-state drive (SSD).

[0043] The product 100 may communicate with the user device 200 through the first network (Network_1) 150. The first network 150 may be a wired network. For example, the product 100 and the user device 200 may be connected to each other through a wire. However, the present disclosure is not limited thereto, and the first network 150 may be a wireless network. For example, the first network 150 may be a short-range wireless network. For example, the first network 150 may support communication using at least one of technologies such as Bluetooth, radio frequency identification (RFID), infrared data association (IrDA), ultra-wideband (UWB), ZigBee, near field communication (NFC), wireless fidelity (Wi-Fi), Wi-Fi direct, wireless universal serial bus (wireless USB), etc. Information about the product 100 may be provided to the user device 200 through the first network 150, and the user device 200 may manage information about the product 100. In an embodiment, the user device 200 may manage information about the product 100 by registering ownership of the product 100 in a block chain. In addition, in an embodiment, the user device 200 of the user who receives the product 100 may manage information about the product 100 by linking information about the transfer of ownership of the product 100 to the ownership blockchain.

[0044] In this specification, the phrase "linking information to a blockchain" may be used to indicate including a data block generated using information in blockchain data by connecting the data block to blockchain data shared by participants (e.g., users, blockchain nodes). The phrase "linking information to a blockchain" may also refer to connecting information to a blockchain or may refer to adding information to a blockchain.

[0045] The user device 200 may be a user device that communicates with the product 100 through the first network 150. The user device 200 may include, but is not limited to, at least one of various computing devices such as a smart phone, a notebook PC, or a desktop PC.

[0046] The user device 200 can communicate with the participants of the block chain system 10 through the second network (Network_2) 250, and communicate with the manufacturer's device 400 (or the manufacturer's device 400) through the third network (Network_3) 350. The second network 250 can be (but not limited to) wired Internet or wireless Internet. For example, the third network 350 can also be (but not limited to) wired Internet or wireless Internet. In an embodiment, the second network 250 and the third network 350 can be the same type of network.

[0047] The user device 200 may receive blockchain data from at least one of the first participant 300_1 to the Nth participant 300_N through the second network 250. Figure 2A The user device 200 may generate a new block related to information about the product 100. The user device 200 may send a message requesting the first participant 300_1 to the Nth participant 300_N to link the new block to the blockchain through the second network 250.

[0048] The user equipment 200 may include a processor (or at least one processor) 220 and a memory (or at least one memory) 240. Instructions related to specific operations performed in the user equipment 200 may be stored in the memory 240, and specific operations may be performed by the user equipment 200 based on the instructions stored in the memory 240 executed by the processor 220. In other words, the operations of the user equipment 200, which will be described with reference to the following figures, may be performed by the instructions stored in the memory 240 executed by the processor 220.

[0049] The processor 220 may include a central processing unit, a microprocessor, a digital signal processor, an application processor, a programmable array, an application specific integrated circuit, etc.

[0050] The first participant 300_1 to the Nth participant 300_N may represent user devices that join the blockchain system 10. Each of the first participant 300_1 to the Nth participant 300_N may store blockchain data BC_Data. For example, each of the first participant 300_1 to the Nth participant 300_N may include a non-transitory computer-readable storage medium, and the non-transitory computer-readable storage medium may store blockchain data BC_Data. The blockchain data BC_Data may represent data used by the user device 200 and the participants of the blockchain system 10 to manage information about the ownership of the product 100. Reference will be made to Figure 2A and 2B The block chain data BC_Data is described in more detail.

[0051] In order to facilitate the description of the first participant 300_1 to the Nth participant 300_N, the first participant 300_1 will be described as an example. The first participant 300_1 may include a storage medium storing instructions for performing specific operations. Based on the instructions stored in the storage medium executed by at least one processor in the first participant 300_1, the specific operation may be performed by the first participant 300_1. In other words, the operation of the first participant 300_1, which will be described with reference to the following figures, may be performed by the instructions stored in the storage medium executed by the processor.

[0052] The manufacturer device 400 is a device of the manufacturer of the product 100, and can communicate with the user device 200 through the third network 350. The manufacturer device 400 can generate a genesis block of blockchain data. The manufacturer device 400 can also generate an ownership record block of the product 100 before selling the product 100 to the purchaser, and can record the ownership of the product 100 in the blockchain by linking the ownership record block to the blockchain. When generating the ownership registration block of the product 100 of the user device 200, the manufacturer device 400 can respond to the request of the user device 200 to send a signature of the public key corresponding to the user device 200 to the user device 200. The signature can be a digital signature.

[0053] According to the blockchain system 10 according to the example embodiment, by managing product information using blockchain, the manufacturer does not need to have a separate authentication server, thereby reducing maintenance costs, improving security, and allowing transparent tracking of the ownership transfer path.

[0054] Figure 2A is a diagram of block chain data BC_Data according to example embodiments.

[0055] Block chain data BC_Data may include a first block (BLK_1) 500_1 to an Mth block (BLK_M) 500_M (where M is a natural number). Each block may be referred to as a data block, and the first block 500_1 may be referred to as a genesis block. The second block (BLK_2) 500_2 may be connected to the first block 500_1. In an embodiment, the second block 500_2 may be connected to the first block 500_1 by including a hash value of the first block 500_1. Similarly, a third block (not shown) may be connected to the second block 500_2, and the Mth block 500_M may be connected to the (M-1)th block (not shown).

[0056] Reference Figure 1 , the participants of the block chain system 10 can share the block chain data BC_Data. In other words, each of the first participant 300_1 to the Nth participant 300_N can store the block chain data BC_Data. The new block can be linked to the block chain data BC_Data. In an embodiment, the new block producer sends a link request message of the new block to the participant, and the participant verifies the new block, so that only the verified new block can be linked to the block chain data BC_Data.

[0057] Figure 2B 5 is a diagram showing types of data blocks according to an example embodiment. The data blocks may include a genesis block 520, an ownership record block 540, an ownership registration block 560, and an ownership transfer block 580. However, these are merely examples, and the present disclosure is not limited thereto.

[0058] Reference Figure 2A , the genesis block 520 may be a block that is the root of the block chain data BC_Data. In an embodiment, the genesis block 520 may be generated by a manufacturer (or a manufacturer device). Figure 3 and Figure 4 The genesis block 520 and the generation process of the genesis block 520 are described in more detail.

[0059] The ownership record block 540 may be a block for initially recording the ownership of a product in a blockchain. In an embodiment, the ownership record block 540 may be generated by a manufacturer (or a manufacturer device), and the ownership record block 540 may be linked to the blockchain by the manufacturer requesting to be linked to a participant of the blockchain system. Figure 5 and Figure 6 The ownership record block 540 and the process of generating the ownership record block 540 are described in more detail.

[0060] The ownership registration block 560 may be a block for initially registering the ownership of a product in a blockchain. In an embodiment, the ownership registration block 560 may be generated by a user device, and the ownership registration block 560 may be linked to the blockchain by requesting a user device of a participant linked to the blockchain system. For example, the user may be the original purchaser (or initial purchaser) of the product. Fig. 9 , Fig.10 , Fig.11A and Fig. 11B The ownership registration block 560 and the process of generating the ownership registration block 560 are described in more detail.

[0061] The ownership transfer block 580 may be a block used to store information about the transfer of product ownership in the blockchain during or after the transfer of the product from the transferor to the transferee. In an embodiment, the ownership transfer block 580 may be generated by a user device, and the ownership transfer block 580 may be linked to the blockchain by requesting the user device of a participant linked to the blockchain system. For example, the user may be the transferee of the product. Fig.13 , Fig.14A and Fig. 14B The ownership transfer block 580 and the process of generating the ownership transfer block 580 are described in more detail.

[0062] Reference Figure 2A , at least a portion of the second block 500_2 to the Mth block 500_M may be one of the ownership recording block 540, the ownership registration block 560 and the ownership transfer block 580.

[0063] Figure 3 is a diagram showing the construction of the founding block 520 according to an example embodiment. Figure 1 describe Figure 3 .

[0064] The genesis block 520 may include a public key 522 of the manufacturer 400. In an embodiment, the genesis block 520 may include a header 524 and the public key 522 of the manufacturer 400. In an embodiment, the genesis block 520 may have a payload including the header 524 and the public key 522 of the manufacturer 400. In an embodiment, the genesis block 520 may include a signature 526 of the manufacturer 400 for the payload. The signature 526 may be a digital signature. The manufacturer 400 may generate a digital signature for the payload by encrypting a digest value of the payload (e.g., a hash value of the payload) using the key of the manufacturer 400.

[0065] Similar to the genesis block 520 described above, a data block other than the genesis block 520 may include a payload and a signature for the payload, wherein the signature for the payload may be referred to as an additional signature included in the data block.

[0066] In an embodiment, a genesis block 520 may be generated by a manufacturer 400, which will refer to Figure 4 Describe in more detail.

[0067] Figure 4 is a flow chart of a method for generating a genesis block according to an example embodiment. In an embodiment, a genesis block may be generated by a manufacturer. Figure 1 describe Figure 4 .

[0068] In operation S120, the manufacturer 400 may generate a payload using the public key Key_pub_MFG of the manufacturer 400. For example, the manufacturer 400 may generate a payload using the public key Key_pub_MFG of the manufacturer 400 and a header.

[0069] In operation S140, the manufacturer 400 may generate a first signature by signing the payload using the key Key_sec_MFG of the manufacturer 400. Here, the first signature may be an additional signature of the manufacturer 400.

[0070] In operation S160, the manufacturer 400 may generate a genesis block using the payload and the first signature.

[0071] Figure 5 is a diagram of a product 100 and a manufacturer 400 according to an example embodiment. Figure 5 Only shown Figure 1 The product 100 and the manufacturer 400 are described in detail to explain the process of generating the ownership record block for the product 100 of the manufacturer 400. Figure 5 of Figure 1 Repeated descriptions of similar or identical products 100 and manufacturers 400.

[0072] The manufacturer 400 may generate a public key Key_pub_P and a key Key_sec_P of the product 100 before producing and selling the product 100. The manufacturer 400 may provide the generated public key Key_pub_P and key Key_sec_P of the product 100 to the product 100. The key may be referred to as a private key. The manufacturer 400 may request a second signature Sign_2 of the product 100 for warranty information of the product 100 and a third signature Sign_3 of the product 100 for a payload to be included in the ownership record block, and receive the second signature Sign_2 and the third signature Sign_3 from the product 100. Each of the second signature Sign_2 and the third signature Sign_3 may be an electronic signature of the product 100 using the key Key_sec_P of the product 100.

[0073] The product 100 may include a security element 110. The security element 110 may represent a space for storing data requiring security in an environment where unauthorized access from the outside is not possible. The security element 110 may store a key Key_sec_P of the product 100. In an embodiment, in response to a signature request for warranty information of the product 100 received from the manufacturer 400, the product 100 may use the key Key_sec_P of the product 100 to send a second signature Sign_2 generated by the security element 110 to the manufacturer 400. In addition, in an embodiment, in response to a signature request for a payload received from the manufacturer 400, the product 100 may use the key Key_sec_P of the product 100 to send a third signature Sign_3 generated by the security element 110 to the manufacturer 400.

[0074] Figure 6 is a diagram showing the construction of the ownership record block 540 according to an example embodiment. Figure 5 describe Figure 6 .

[0075] The ownership record block 540 may include a first signature 542 of the manufacturer 400 for the public key Key_pub_P of the product 100 and a second signature 544 of the product 100 for the warranty information WAR_Info of the product 100. In an embodiment, the first signature 542 may be a signature of the manufacturer 400 for the first message (including the public key Key_pub_P of the product 100 and the timestamp TS), and the second signature 544 may be a signature of the product 100 for the second message (including the warranty information WAR_Info of the product 100 and the timestamp TS). In an embodiment, the ownership record block 540 may include a payload including the first signature 542 and the second signature 544, and the payload may include a header and a hash value 546 of a previous block. The previous block may be a data block to which the generated ownership record block 540 is directly linked as the last data block included in the block chain data at the time point when the manufacturer 400 generates the ownership record block 540. In addition, in an embodiment, the ownership record block 540 may include a third signature 548 of the product 100 for the payload. The third signature 548 may be referred to as an additional signature of the ownership record block 540. Figure 7 The process of generating ownership record block 540 is described in more detail.

[0076] Figure 7 is a flow chart of a method for generating an ownership record block according to an example embodiment. In an embodiment, the ownership record block may be generated by a manufacturer. Figure 5 describe Figure 7 .

[0077] In operation S210, the manufacturer 400 may generate a public key Key_pub_P and a secret key Key_sec_P of the product 100. The manufacturer 400 may inject the generated public key Key_pub_P and secret key Key_sec_P of the product 100 into the product 100.

[0078] In operation S220, the manufacturer 400 may generate a first signature by signing the public key Key_pub_P of the product 100 using the key Key_sec_MFG of the manufacturer 400. In an embodiment, the manufacturer 400 may generate a first signature by signing a first message including the public key Key_pub_P of the product 100 and a timestamp using the key Key_sec_MFG of the manufacturer 400.

[0079] In operation S230, the manufacturer 400 may receive a second signature indicating a signature of the warranty information WAR_Info of the product 100 using the key Key_sec_P of the product 100 from the product 100. In an embodiment, the second signature may be generated in a secure element of the product 100. In addition, in an embodiment, the second signature may be a signature of a second message including the warranty information WAR_Info of the product 100 and a timestamp using the key Key_sec_P of the product 100.

[0080] In operation S240, the manufacturer 400 may generate a payload using the hash value of the previous block, the first signature, and the second signature. In an embodiment, the manufacturer 400 may generate a payload using the header, the hash value of the previous block, the first signature, and the second signature.

[0081] In operation S250 , the manufacturer 400 may receive a third signature indicating a signature on the payload using the key Key_sec_P of the product 100 .

[0082] In operation S260, the manufacturer 400 may generate an ownership record block using the payload and the third signature.

[0083] The manufacturer 400 may generate an ownership record block and then send a link request message to a participant of the block chain system to link the ownership record block to the block chain as a new block. When the ownership record block is verified by a participant, the ownership record block may be linked to the block chain.

[0084] Figure 8 is a flow chart of a method for managing product information in a user device according to an example embodiment. Figure 1 describe Figure 8 .

[0085] In operation S300, the user device 200 may receive blockchain data BC_Data from at least one of the participants of the blockchain system 10. For example, the user device 200 may receive blockchain data BC_Data from the nearest participant among the first participant 300_1 to the Nth participant 300_N through the second network 250.

[0086] In operation S400, the user device 200 may request the first signer and the product 100 to respectively sign first information including a first public key corresponding to the user device 200. The first signer may be the manufacturer 400 or another user device.

[0087] In operation S500, the user device 200 may generate a new block using the first signature and the second signature respectively received from the first signer and the product 100. For example, the user device 200 may generate a payload including the first signature and the second signature, and may generate a new block by using a third signature on the payload and the payload, the payload using a key corresponding to the user device 200.

[0088] In operation S600, the user device 200 may request a participant of the blockchain system 10 to link the generated new block to the blockchain. For example, the user device 200 may request that the new block be linked to the blockchain by sending a link request message including the new block to the participant of the blockchain system 10. When the new block is verified by the participant, the new block may be linked to the blockchain.

[0089] In an embodiment, the Figure 8 The product information management method is applied to the generation of the ownership registration block and the ownership transfer block in the user device 200. Figures 9 to 11B The ownership registration block generation of the user device 200 is described in more detail and will be described with reference to FIGS. Fig. 14B The ownership transfer block generation of the user device 200 is described in more detail.

[0090] According to the blockchain system 10 according to the example embodiment, by managing product information using blockchain, manufacturers may not need a separate authentication server, which reduces maintenance costs, improves security, and allows transparent tracking of ownership transfer paths.

[0091] Fig. 9 A product 100 , a user device 200 , and a manufacturer 400 are shown according to an example embodiment. Fig. 9 Only shown Figure 1 The product 100, the user device 200 and the manufacturer 400 are described to explain the process of generating the ownership registration block of the user device 200. Figure 5 of Figure 1Repeated description of similar or identical products 100, user devices 200 and manufacturers 400.

[0092] The user device 200 may be a computing device of a user who wants to register the product 100 in the blockchain. For example, the user device 200 may be a computing device of a user who initially purchases and uses the product 100. The user device 200 may generate a secret key and a public key corresponding to the user device 200. For example, the user device 200 may generate a private key of the user and a public key of the user. The user device 200 may request a first signature Sign_1 of the manufacturer 400 for the user's public key by sending a first signature request signal REQ_Sign_1 to the manufacturer 400, and request a second signature Sign_2 of the product 100 for the user's public key by sending a second signature request signal REQ_Sign_2 to the product 100. The user device 200 may receive the first signature Sign_1 from the manufacturer 400 in response to the first signature request signal REQ_Sign_1, and may receive the second signature Sign_2 from the product 100 in response to the second signature request signal REQ_Sign_2.

[0093] The user device 200 can generate an ownership registration block using the first signature Sign_1 and the second signature Sign_2. Fig.10 Describe the construction of the ownership registration block in more detail.

[0094] Fig.10 is a diagram showing the construction of the ownership registration block 560 according to an example embodiment. Fig. 9 describe Fig.10 , assuming that the user of user device 200 is user A.

[0095] The ownership registration block 560 may include a first signature 562 of the manufacturer 400 for the public key Key_pub_A of user A and a second signature 564 of the product 100 for the public key Key_pub_A of user A. In an embodiment, the first signature 562 may be a signature of the manufacturer 400 for a first message including the public key Key_pub_A of user A and a timestamp TS, and the second signature 564 may be a signature of the product 100 for a second message including the public key Key_pub_A of user A and a timestamp TS. In an embodiment, the ownership registration block 560 may have a payload including the first signature 562 and the second signature 564, and the payload may include a header and a hash value 566 of a previous block. In addition, in an embodiment, the ownership registration block 560 may include a third signature 568 of the payload using the key of user A. The third signature 568 may be referred to as an additional signature of the ownership registration block 560. Reference will be made to Fig.11A and Fig. 11B The process of generating ownership registration block 560 is described in more detail.

[0096] Fig.11A and Fig. 11B is a flow chart of a method of generating a title registration block according to an example embodiment. Fig.11A It can be shown that Figure 8 The method is applied to the generation of ownership registration blocks. Figure 8 The embodiment of operation S500 described in Fig. 11B Can be shown in Fig.11A The embodiment of the operation of generating the ownership registration block before the operation S1540. Fig. 9 describe Fig.11A and Fig. 11B .

[0097] Reference Fig.11A In operation S1520, the user device 200 may receive a first signature Sign_1 indicating a signature of the public key Key_pub_A of the user A using the key Key_sec_MFG of the manufacturer 400 from the manufacturer 400. In an embodiment, the first signature Sign_1 may be a signature of the manufacturer 400 for the first message including the public key Key_pub_A of the user A and the timestamp TS.

[0098] In operation S1530, the user device 200 may receive, from the product 100, a second signature Sign_2 indicating a signature of the public key Key_pub_A of the user A using the key Key_sec_P of the product 100. In an embodiment, the second signature Sign_2 may be a signature of the product 100 for the second message including the public key Key_pub_A of the user A and the timestamp TS, and the second signature Sign_2 may be generated in a secure element of the product 100.

[0099] In operation S1540, the user device 200 may verify the manufacturer 400 and the product 100 as the signers of the first signature Sign_1 and the second signature Sign_2 using the blockchain data. Figures 15 to 16B A process of verifying a specific target such as the manufacturer 400 or the product 100 is described.

[0100] In operation S1550, when verification of the manufacturer 400 and the product 100 is completed, the user device 200 may generate a payload using the hash value of the previous block, the first signature Sign_1, and the second signature Sign_2. In an embodiment, the payload may further include a header.

[0101] In operation S1560, the user device 200 may generate a third signature indicating a signature on the payload using the key Key_sec_A of the user A. The third signature may be referred to as an additional signature of the user registration block.

[0102] In operation S1570, the user device 200 may generate an ownership registration block using the payload and the third signature.

[0103] The user device 200 may generate an ownership registration block and then send a link request message to a participant of the blockchain system to link the ownership registration block to the blockchain as a new block. When the ownership registration block is verified by the participant, the ownership registration block may be linked to the blockchain. Figures 17 to 19C Describes the process of linking a new block.

[0104] Reference Fig. 11B , in operation S1510, the user device 200 may generate a public key Key_pub_A and a secret key Key_sec_A of user A.

[0105] Operation S1522, operation S1524, and operation S1526 may correspond to Fig.11A In operation S1520 of FIG. 15, the user device 200 may request a signature of the manufacturer 400 for the public key Key_pub_A of user A. In operation S1524, the manufacturer 400 may generate a first signature Sign_1 by signing the public key Key_pub_A of user A using the key Key_sec_MFG of the manufacturer 400. In operation S1526, the manufacturer 400 may send the first signature Sign_1 to the user device 200.

[0106] Operations S1532, S1534, and S1536 may correspond to Fig.11A In operation S1530 of the embodiment. In operation S1532, the user device 200 may request a signature of the product 100 for the public key Key_pub_A of the user A. In operation S1534, the product 100 may generate a second signature Sign_2 by signing the public key Key_pub_A of the user A using the key Key_sec_P of the product 100. In operation S1536, the product 100 may send the second signature Sign_2 to the user device 200.

[0107] In operation S1540, the user device 200 may verify the manufacturer 400 and the product 100, which are signers of the first signature Sign_1 and the second signature Sign_2, using the blockchain data.

[0108] Fig. 12A and Fig. 12B are diagrams illustrating products 100a and 100b, first user devices 200a and 200b, and second user devices 230a and 230b, respectively, according to example embodiments. Fig. 12A and Fig. 12BThe products 100a and 100b, the first user devices 200a and 200b, and the second user devices 230a and 230b are shown to explain the process of generating the ownership transfer block of the first user devices 200a and 200b. Fig. 12A and Fig. 12B of Figure 1 A duplicate description of 100 similar or identical products.

[0109] The first user devices 200a and 200b may be computing devices of the assignees of the products 100a and 100b, and the second user devices 230a and 230b may be computing devices of the assignors of the products 100a and 100b. Assume that the assignor is user A and the assignee is user B.

[0110] Fig. 12A An embodiment is shown in which a transferee uses a first user device 200a to generate a title transfer block prior to receiving the product 100a from the transferor.

[0111] The first user device 200a may generate a secret key and a public key corresponding to the first user device 200a. For example, the first user device 200a may generate a public key of a transferee, that is, a public key of user B. The first user device 200a may request a first signature Sign_1 of the second user device 230a for the public key of user B by sending a first signature request signal REQ_Sign_1 to the second user device 230a, and request a second signature Sign_2 of the product 100a for the public key of user B by sending a second signature request signal REQ_Sign_2 to the second user device 230a.

[0112] In response to the second signature request signal REQ_Sign_2, the second user device 230a may request the second signature Sign_2 of the product 100a for the public key of user B by sending a third signature request signal REQ_Sign_3 to the product 100a. The second user device 230a may receive the second signature Sign_2 from the product 100a in response to the third signature request signal REQ_Sign_3. The second user device 230a may send the first signature Sign_1 and the second signature Sign_2 to the first user device 200a.

[0113] The first user device 200a can generate an ownership transfer block using the first signature Sign_1 and the second signature Sign_2. Fig.13 Describe the construction of the ownership transfer block in more detail.

[0114] Fig. 12BAn embodiment is shown in which the transferee uses the first user device 200b to generate an ownership transfer block after receiving the product 100b from the transferor. The first user device 200b may generate a key and a public key corresponding to the first user device 200b. For example, the first user device 200b may generate a key and a public key of user B. The first user device 200b may request the first signature Sign_1 of the second user device 230b for the public key of user B by sending a first signature request signal REQ_Sign_1 to the second user device 230b, and request the second signature Sign_2 of the product 100b for the public key of user B by sending a second signature request signal REQ_Sign_2 to the product 100b. The first user device 200b may receive the first signature Sign_1 from the second user device 230b in response to the first signature request signal REQ_Sign_1, and may receive the second signature Sign_2 from the product 100b in response to the second signature request signal REQ_Sign_2.

[0115] The first user device 200b can generate an ownership transfer block using the first signature Sign_1 and the second signature Sign_2. Fig.13 Describe the construction of the ownership transfer block in more detail.

[0116] Fig.13 is a diagram showing the construction of the ownership transfer block 580 according to an example embodiment. Fig. 12A and Fig. 12B describe Fig.13 .

[0117] The ownership transfer block 580 may include a first signature 582 of the second user device 230 for the public key Key_pub_B of user B and a second signature 584 of the product 100 for the public key Key_pub_B of user B. In an embodiment, the first signature 582 may be a signature of the second user device 230 for a first message including the public key Key_pub_B of user B and a timestamp TS, and the second signature 584 may be a signature of the product 100 for a second message including the public key Key_pub_B of user B and a timestamp TS. In an embodiment, the ownership transfer block 580 may have a payload including the first signature 582 and the second signature 584, and the payload may include a header and a hash value 586 of a previous block. In addition, in an embodiment, the ownership transfer block 580 may include a third signature 588 of the payload using the key of user B. The third signature 588 may be referred to as an additional signature of the ownership transfer block 580. Reference will be made to FIG. 14A to FIG. 14C The process of generating ownership transfer block 580 is described in more detail.

[0118] FIG. 14A to FIG. 14Cis a flow chart of a method of generating an ownership transfer block according to an example embodiment. Fig.14A It can be shown that Figure 8 The method is applied to the generation of ownership transfer blocks Figure 8 In an embodiment of operation S500, Fig. 14B It can be shown that according to Fig. 12A System Fig.14A The embodiment before operation S2540, and Fig. 14C It can be shown that according to Fig. 12B System Fig.14A The embodiment of generating the ownership transfer block before operation S2540. Fig. 12A and Fig. 12B describe Fig.14A , will refer to Fig. 12A describe Fig. 14B , and will refer to Fig. 12B describe Fig. 14C User A is described as transferor A and user B is described as transferee B.

[0119] Reference Fig.14A In operation S2520, the first user devices 200a and 200b may receive, from the second user devices 230a and 230b, respectively, a first signature Sign_1 indicating a signature of the public key Key_pub_B of the transferee B using the key Key_sec_A of the transferor A. In an embodiment, the first signature Sign_1 may be a signature of the transferor A for the first message including the public key Key_pub_B of the transferee B and the timestamp TS.

[0120] In operation S2530, the first user devices 200a and 200b may receive, from the products 100a and 100b, respectively, a second signature Sign_2 indicating a signature of the public key Key_pub_B of the transferee B using the keys Key_sec_P of the products 100a and 100b. In an embodiment, the second signature Sign_2 may be a signature of the products 100a and 100b for the second message including the public key Key_pub_B of the transferee B and the timestamp TS, and the second signature Sign_2 may be generated in the security elements of the products 100a and 100b.

[0121] In operation S2540, the first user devices 200a and 200b may verify the transferor A and the products 100a and 100b, which are signers of the first signature Sign_1 and the second signature Sign_2, respectively, using the blockchain data. Figures 15 to 16B A process of verifying a specific target such as transferor A or products 100a and 100b is described.

[0122] In operation S2550, when verification of the transferor A and the products 100a and 100b is completed, the first user devices 200a and 200b may generate a payload using the hash value of the previous block, the first signature Sign_1, and the second signature Sign_2. In an embodiment, the payload may further include a header.

[0123] In operation S2560, the first user devices 200a and 200b may generate a third signature indicating a signature on the payload using the key Key_sec_B of the transferee B. The third signature may be referred to as an additional signature of the user transfer block.

[0124] In operation S2570, the first user devices 200a and 200b may generate an ownership transfer block using the payload and the third signature.

[0125] The first user devices 200a and 200b may generate an ownership transfer block and then send a link request message to a participant of the blockchain system to link the ownership transfer block as a new block to the blockchain. When the ownership transfer block is verified by the participant, the ownership transfer block may be linked to the blockchain. When the ownership transfer block is normally linked to the blockchain, the transferee B may pay the transferor A for the products 100a and 100b. Figures 17 to 19C Describes the process of linking a new block.

[0126] Reference Fig. 14B In operation S2510a, the first user device 200a may generate a public key Key_pub_B and a secret key Key_sec_B of the transferee B.

[0127] Operation S2522a, operation S2524a, and operation S2526a may correspond to Fig.14A In operation S2520 of the embodiment. In operation S2522a, the first user device 200a may request a signature of the transferor A for the public key Key_pub_B of the transferee B. In operation S2524a, the second user device 230a of the transferor A may generate a first signature Sign_1 by signing the public key Key_pub_B of the transferee B using the key Key_sec_A of the transferor A. In operation S2526a, the second user device 230a may send the first signature Sign_1 to the first user device 200a.

[0128] Operation S2532a, operation S2534a, operation S2536a and operation S2538a may correspond to Fig.14AIn operation S2530 of the embodiment. In operation S2532a, the second user device 230a may request a signature of the product 100a for the public key Key_pub_B of the assignee B. In operation S2534a, the product 100 may generate a second signature Sign_2 by signing the public key Key_pub_B of the assignee B using the key Key_sec_P of the product 100a. In operation S2536a, the product 100a may send the second signature Sign_2 to the second user device 230a. In operation S2538a, the second user device 230a may send the second signature Sign_2 to the first user device 200a.

[0129] In operation S2540a, the first user device 200a may verify the transferor A and the product 100a, which are signers of the first signature Sign_1 and the second signature Sign_2, using the blockchain data.

[0130] Reference Fig. 14C , in operation S2510b, the second user device 200b may generate a public key Key_pub_B and a secret key Key_sec_B of the transferee B.

[0131] Operation S2522b, operation S2524b, and operation S2526b may correspond to Fig.14A In operation S2520 of , the first user device 200b may request a signature of the transferor A for the public key Key_pub_B of the transferee B. In operation S2522b, the first user device 200b may request a signature of the transferor A for the public key Key_pub_B of the transferee B. In operation S2524b, the second user device 230b of the transferor A may generate a first signature Sign_1 by signing the public key Key_pub_B of the transferee B using the key Key_sec_A of the transferor A. In operation S2526b, the second user device 230b may send the first signature Sign_1 to the first user device 200b.

[0132] Operation S2532b, operation S2534b, and operation S2536b may correspond to Fig.14A In operation S2530 of the embodiment. In operation S2532b, the first user device 200b may request a signature of the product 100b for the public key Key_pub_B of the transferee B. In operation S2534a, the product 100b may generate a second signature Sign_2 by signing the public key Key_pub_B of the transferee B using the key Key_sec_P of the product 100b. In operation S2536b, the product 100b may send the second signature Sign_2 to the first user device 200b.

[0133] In operation S2540, the first user device 200b may verify the transferor A and the product 100b, which are signers of the first signature Sign_1 and the second signature Sign_2, using the blockchain data.

[0134] Fig.15 4 is a flowchart of a method for verifying a target according to an exemplary embodiment. Based on the assumption that the user device 200 verifies a target X such as a product 100 or a manufacturer 400, referring to Figure 1 Describes Fig.15 .

[0135] In operation S720, the user device 200 may retrieve a target block including an additional signature of the target X in the block chain data.

[0136] In operation S740, the user device 200 compares the value obtained by decoding the additional signature of the target X included in the target block using the public key of the target X with the digest value of the payload of the target block, and determines whether the value obtained by decoding the additional signature and the digest value are the same value. In an embodiment, the digest value of the payload may be a hash value of the payload. The same process as in operation S740 may be referred to as authentication of the additional signature included in the data block.

[0137] In operation S760, the user device 200 may retrieve a signer block including an additional signature of a signer of a signature included in a payload of a target block in the block chain data. In an embodiment, operation S760 may be performed once the additional signature included in the target block is authenticated.

[0138] In operation S780, the user device 200 compares a value obtained by decoding the additional signature of the signer included in the signer block using the public key of the signer with a digest value of the payload of the signer block to determine whether the value obtained by decoding the additional signature of the signer and the digest value are the same value. In an embodiment, the digest value of the payload may be a hash value of the payload. The user device 200 may verify the target X based on determining that the value obtained by decoding the additional signature of the signer and the digest value of the payload of the signer block are the same value.

[0139] Fig.16A is a diagram of block chain data BC_Data for explaining a target verification sequence in an ownership registration operation according to an example embodiment. Fig.16A The genesis block (Block_1) 520a and the product ownership record block 540a are shown to explain the process for verifying the manufacturer and product. Fig.11AIn other words, the block chain data BC_Data may include a plurality of blocks, wherein the plurality of blocks may include a genesis block 520a as the first block and a product ownership record block (Block_i) 540a as the i-th block. Fig. 9 describe Fig.16A .

[0140] In operation S701a, in order to verify the manufacturer 400, the user device 200 may find the genesis block 520a by searching the block including the additional signature of the manufacturer 400 in the block chain data BC_Data. The authentication of the additional signature may follow Fig.15 Since the payload of genesis block 520a does not include a signature, no further verification of the signer may be performed.

[0141] In operation S711a, in order to verify the product 100, the user device 200 may find the product ownership record block 540a by retrieving a block including an additional signature of the product 100 in the block chain data BC_Data, and may Fig.15 The method of operation S740 of the present invention authenticates the additional signature included in the product ownership record block 540a. In operation S712a, the user device 200 may find the signer of the signature included in the payload of the ownership record block 540a. Then, in operation S713a, the user device 200 may perform a verification process on the manufacturer 400 as the signer.

[0142] Fig. 16B is a diagram of block chain data BC_Data for explaining a target verification sequence in an ownership transfer operation according to an example embodiment. Fig. 16B The origination block 520b, the product ownership record block 540b, and the product ownership registration block 560b are shown to explain the process for verifying the transferor and the product. Fig.14A In other words, the block chain data BC_Data may include a plurality of blocks, wherein the plurality of blocks may include a genesis block 520b as the first block, a product ownership record block 540b as the i-th block, and a product ownership registration block 560b as the j-th block. Fig. 12A and Fig. 12B describe Fig. 16B For ease of description, it is assumed that transferor A has registered product ownership.

[0143] In operation S701b, in order to verify the transferor A, the first user devices 200a and 200b may find the product ownership registration block 560b by retrieving the block including the additional signature of the transferor A, and may authenticate the additional signature included in the product ownership registration block 560b. The first user devices 200a and 200b may respectively perform operations S702b, S703b, S704b, S705b, S706b, and S707b to verify the manufacturer and product as the signer of the signature included in the payload of the product ownership registration block 560b.

[0144] In operation S711b, in order to verify the products 100a and 100b, the first user devices 200a and 200b may find the product ownership record block 540b by retrieving the block including the additional signature of the products 100a and 100b, and may authenticate the additional signature included in the product ownership record block 540b. The first user devices 200a and 200b may verify the manufacturer as the signer of the signature included in the payload of the product ownership record block 540b through operations S712b and S713b.

[0145] Fig.17 is a flow chart of a blockchain participation process according to an example embodiment. Fig.17 It can be used for example according to Figure 6 Ownership record block, according to Fig.10 Ownership registration block and / or according to Fig.13 A flowchart of the process of linking a new block of the ownership transfer block to the block chain. Figure 1 describe Fig.17 .

[0146] In operation S820, the producer of the new block may send a link request message including the new block to a participant of the block chain system 10. Depending on the type of the new block, the producer of the new block may be the manufacturer 400 or the user device 200. For example, the producer of the new block may send the link request message to the participant through the second network 250. Hereinafter, it is assumed that the new block is included in the block chain as the i-th block.

[0147] In operation S840, the participants of the blockchain system 10 may verify the new block included in the link request message. Fig.18 Operation S840 is described in more detail.

[0148] In operation S860, when the verification of the new block is completed, the participant of the blockchain system 10 may connect the new block to the blockchain as a certification block. That is, the participant may connect the new block to the blockchain by linking the new block to the (i-1)th block which is the last block of the blockchain data. As described above, the connection of the new block to the blockchain may be expressed as the linking of the new block to the blockchain.

[0149] Fig.18 is a flow chart of a new block verification method according to an example embodiment. Fig.18 Can show Fig.17 Reference will be made to the embodiment of operation S840. Figure 1 describe Fig.18 .

[0150] In operation S842, participants of the blockchain system 10 may authenticate additional signatures included in the new block. Fig.15 The additional signature authentication in operation S842 is performed in a manner similar to or identical to the method in operation S740.

[0151] In operation S844, the participants of the blockchain system 10 may verify the signer of the signature included in the payload of the new block. Fig.15 The verification method of the described target performs verification of the signer in a similar or identical manner.

[0152] In operation S846, the participant of the block chain system 10 may determine whether the first value and the second value are equal by comparing the first value with the second value. Here, the first value may indicate a value included as a hash value of the (i-1)th block in the new block. In addition, the second value may represent a hash value of the (i-1)th block obtained by applying a hash function process to the (i-1)th block included in the block chain data owned by the participant. New block verification is performed based on the comparison result between the first value and the second value.

[0153] Fig.19A is a flow chart of a blockchain participation process in an ownership record operation according to an example embodiment. Fig.19A It can be shown that Fig.17 The processing is applied to the chaining of ownership record blocks. Therefore, operations S820a, S840a and S860a may correspond to Fig.17 Operations S820, S840 and S860 in FIG. 1 are different in that the new block is limited to the ownership record block.

[0154] In operation S850a, in the process of linking the ownership record block, the participants of the blockchain system 10 may confirm whether a signer other than the product among the signers of the payload included in the ownership record block is equivalent to the manufacturer.

[0155] In addition, in operation S852a, each of the participants of the blockchain system 10 may confirm whether the ownership of the product has been recorded in the blockchain using the blockchain data owned by the participant.

[0156] In operation S860a, when the ownership record block is verified according to operation S840a, the signer is determined to be equal to the manufacturer, and the ownership is determined not to have been recorded before, the participant may connect the ownership record block to the block chain as an authentication block.

[0157] Fig.19B is a flow chart of a blockchain participation process in a title registration operation according to an example embodiment. Fig.19B It can be shown that Fig.17 The processing is applied to the embodiment of the linking of the ownership registration block. Therefore, operation S820b, operation S840b and operation S860b may correspond to Fig.17 The difference between operations S820, S840 and S860 in FIG. 1 is that the new block is limited to the ownership registration block.

[0158] Fig.19C is a flow chart of a blockchain participation process in an ownership transfer operation according to an example embodiment. Fig.19C It can be shown that Fig.17 The processing of is applied to the chaining of ownership transfer blocks. Therefore, except that the new block is limited to the ownership transfer block, operation S820c, operation S840c and operation S860c may correspond to Fig.17 Operation S820, operation S840 and operation S860 in.

[0159] In operation S850c, in the process of linking the ownership transfer block, the participants of the blockchain system 10 may confirm whether the transferor is the final owner. For example, each participant determines whether the final owner of the product obtained using the blockchain data owned by the participant is equal to the transferor, that is, the signer of the payload included in the ownership transfer block.

[0160] Fig. 20 A blockchain system 20 according to an example embodiment is shown. The blockchain system 20 may include a product 100 and a plurality of participants. The product 100 may communicate with a first participant 300_1 to an Nth participant 300_N through a second network 250. Fig. 20 Executable and Figure 1 The block chain system 20 has similar or identical functions to the block chain system 10, except that the product 100 can communicate directly with the multiple participants. In other words, the block chain system 20 can be realized by using the reference Figures 3 to 19C One or more methods are described to manage information about product 100 .

[0161] The product 100 may include a network interface 120, an indicator 130, and a processor 140. The product 100 may also include a predetermined memory. The network interface 120 may provide a communication function between the first participant 300_1 to the Nth participant 300_N and the product 100. The indicator (or output circuit) 130 may include any structure capable of performing a notification function to a user of the product 100 through various sensory methods (including (for example, but not limited to) a visual method, an auditory method, a tactile method). The indicator (or output circuit) 130 may also include (for example, but not limited to) a display, a speaker, a vibration motor, etc. The indicator 130 may be implemented in any manner capable of performing a notification function to a user of the product 100. The processor 140 may execute a specific operation performed on the product 100 instruction by instruction. For example, the memory of the product 100 may store instructions for performing a specific operation, and the product 100 may perform a specific operation as the processor 140 executes the instructions.

[0162] The processor 140 may include a central processing unit, a microprocessor, a digital signal processor, an application processor, a programmable array, an application specific integrated circuit, etc.

[0163] Fig.21 is a flow chart of a product boot method according to an example embodiment. Fig. 20 describe Fig.21 .

[0164] In operation S3100 , the product 100 may perform a booting operation in an activation phase of the product 100 .

[0165] In operation S3200 , the product 100 may confirm whether the ownership of the product 100 is registered in the blockchain system 20 .

[0166] In operation S3300, depending on whether the blockchain system 20 has registered the ownership of the product 100, subsequent operations may be performed differently.

[0167] In operation S3400, when the blockchain system 20 has ownership of the product 100, the product 100 may start operating normally.

[0168] In operation S3500, when the blockchain system 20 does not have the ownership of the product 100, the product 100 may not start normal operation, and at this time, the user of the product 100 may be notified of an ownership registration request message requesting to register the ownership of the product 100. In an embodiment, the product 100 may display the ownership registration request message to the user through the indicator 130.

[0169] Fig. 22 is a flow chart of a product repair process for a manufacturer according to an example embodiment

[0170] In operation S4100, the manufacturer may receive an after-sales service request for a product.

[0171] In operation S4200, the manufacturer may receive blockchain data from the blockchain system and confirm the ownership and production time information of the product (eg, information about when the product was produced) according to the blockchain data. For example, a timestamp included in a block in the blockchain data may be used.

[0172] In operation S4300, the manufacturer may confirm warranty information of the product based on the blockchain data. The warranty information of the product may be included in the ownership block for the product.

[0173] In operation S4400, subsequent operations may be performed differently depending on whether the current time point is within the warranty period and whether ownership exists in the blockchain data.

[0174] In operation S4500, when the current time point is within the warranty period and the ownership exists in the blockchain data, the manufacturer may repair the product for free.

[0175] On the other hand, in operation S4600, when the current time point is outside the warranty period or when the ownership does not exist in the blockchain data, the manufacturer may repair the product and charge a fee.

[0176] The exemplary embodiments may be implemented as computer readable codes on a computer readable recording medium. A computer readable recording medium is any data storage device that can store data that can be read later by a computer system. Examples of computer readable recording media include read-only memory (ROM), random access memory (RAM), CD-ROM, magnetic tape, floppy disk, and optical data storage devices. The computer readable recording medium may also be distributed on a network-connected computer system so as to store and execute the computer readable code in a distributed manner. In addition, the exemplary embodiments may be written as a computer program that is transmitted on a computer readable transmission medium such as a carrier wave and received and implemented on a general-purpose or special-purpose digital computer that executes the program.

[0177] At least one of the components, elements, modules or units described herein may be implemented as various numbers of hardware, software and / or firmware structures that perform the above-mentioned corresponding functions, and may include circuits, processors, microprocessors according to example embodiments. For example, at least one of these components, elements or units may use direct circuit structures such as memory, processors, logic circuits, lookup tables, etc. that can perform corresponding functions by controlling one or more microprocessors or other control devices. In addition, at least one of these components, elements or units may be specifically implemented by a module, program or a portion of code containing one or more executable instructions for performing a specific logical function and performed by one or more microprocessors or other control devices. In addition, at least one of these components, elements or units may also include a processor, microprocessor, etc. such as a central processing unit (CPU) that performs the corresponding function or is implemented by it. Two or more of these components, elements or units may be combined into a single component, element or unit that performs all operations or functions of two or more components, elements or units combined. In addition, at least a portion of the functions of at least one of these components, elements or units may be performed by another of the components, elements or units. In addition, although the bus is not shown in the block diagram above, the communication between the components, elements or units may be performed by the bus. The functional aspects of the above exemplary embodiments may be implemented according to algorithms executed on one or more processors. In addition, the electronic construction, signal processing and / or control, data processing, etc. of the components, elements or units represented by blocks or processing steps may adopt any number of existing technologies.

[0178] Example embodiments are shown and described in the accompanying drawings and in the above detailed description. Although specific terms are used to explain these example embodiments in the present disclosure, these specific terms are not intended to limit the scope, but are only used for better understanding. It should be understood by those of ordinary skill in the art that various changes in form and detail may be made without departing from the spirit and scope of the present invention as defined in the appended claims. Therefore, the scope is defined by the claims rather than by the specific embodiments.

Claims

1. A user device for participating in a block chain system, the user device being configured to communicate with a product via a first network, the user device include: at least one processor; as well as At least one memory configured to store instructions, which, when executed by the at least one processor, cause the at least one processor to perform the following steps: receiving blockchain data from at least one of the blockchain participants of the blockchain system, the at least one of the blockchain participants being connected to the user device via a second network; Requesting a digital signature of first information including a first public key corresponding to the user device from a first signer, and requesting a digital signature of first information including a first public key corresponding to the user device from the product; generating a new block using a first signature received from the first signer and a second signature received from the product; as well as The blockchain participants are requested to link the new block to the blockchain data.

2. The user equipment according to claim 1, in, The step of generating the new block includes generating the new block using a hash value of a last block included in the received block chain data, the first signature, and the second signature.

3. The user equipment according to claim 1, in, The steps of generating the new block include: generating a payload using the first signature and the second signature; generating a third signature by signing the payload using a first key corresponding to the first public key; and The new block is generated using the payload and the third signature.

4. The user equipment according to claim 1, in, The instructions further cause the at least one processor to perform at least one of the following steps: Verifying the first signer using the block chain data; and The product is verified using the blockchain data.

5. The user equipment according to claim 4, in, Verifying the first signer comprises the following steps: retrieving a target block including an additional signature of the first signer from the block chain data; authenticating the additional signature of the first signer included in the target block using the additional signature of the first signer and a target payload included in the target block; and Verify the signer of the signature included in the target payload.

6. The user equipment according to claim 5, in, The step of authenticating the additional signature of the first signer includes comparing a value obtained by decoding the additional signature of the first signer using a public key of the first signer with a digest value of the target payload.

7. The user equipment according to claim 6, in, The digest value of the target payload is a hash value of the target payload.

8. The user equipment according to claim 1, in, The first signatory comprises the manufacturer of the product.

9. The user equipment according to claim 8, in, The first signature includes a digital signature generated for the first information using a key of the manufacturer, and The second signature includes a digital signature generated for the first information using a key of the product.

10. The user equipment according to claim 8, in, The new block includes a data block for registering the product to the blockchain.

11. The user equipment according to claim 1, in, The first signer includes at least one of a transferor of the product and a user device of the transferor.

12. The user equipment according to claim 11, in, The first signature includes a digital signature generated for the first information using a key of a user device of the transferor, and The second signature includes a digital signature generated for the first information using a key of the product.

13. The user equipment according to claim 11, in, The new block includes a data block for writing information about the transfer of ownership of the product to the block chain.

14. The user equipment according to claim 1, in, The genesis block of the block chain data includes a genesis payload including a public key of a manufacturer and a digital signature of the manufacturer for the genesis payload.

15. The user equipment according to claim 1, in, The blockchain data includes a block of ownership records for the product, and The ownership record block of the product includes: The manufacturer's digital signature of the public key for the product; and A digital signature for the product and warranty information for the product.