KR20240045032A - Apparatus and method for transmitting data by block-chain - Google Patents

Abstract

The electronic device includes communication circuitry, a memory and a processor to store a partial or full ledger including a portion of the entire ledger for a blockchain network, wherein each of at least one transaction on which the electronic device participates in consensus It may contain at least one block corresponding to . The processor creates a first transaction using a smart contract containing information about the shared data of the electronic device and the external user who will receive the shared data, and transmits the first transaction to the blockchain network. request, verify the first transaction using a node that generates at least one block corresponding to each of at least one transaction in which the electronic device participated in the agreement, and confirm the reliability of the first transaction on the blockchain network. Send a first transaction, create a first block corresponding to the first transaction, verify the second transaction based on receiving a second transaction comprising a request to provide shared data from the blockchain network, and Based on confirming the reliability of , the smart contract can be executed and a second block corresponding to the second transaction can be created.

Description

Blockchain-based data transmission method and device {APPARATUS AND METHOD FOR TRANSMITTING DATA BY BLOCK-CHAIN}

Various embodiments of this document may include electronic devices and data transmission methods that transmit data based on blockchain.

Blockchain is a data structure that stores information in blocks and continuously connects them to existing blocks to form a chain. It is not a data storage structure like a database running on a single computer, but a node-to-node (peer-to-peer, P2P) structure. ) It can refer to a distributed data structure using a network system. Blockchain allows all nodes to store the same data block for security purposes.

Electronic devices may store blocks related to nodes and ledgers related to blocks partially (e.g., a partial ledger) among the distributed ledgers for the blockchain network, or store the entire distributed ledger for the blockchain network (or the entire ledger). You can. For example, a distributed ledger may include at least one block and state database, each containing at least one transaction in the blockchain network. At least one block included in each distributed ledger can be linked using a hash field. Therefore, if the connection through the hash field is lost or a different distributed ledger is discovered, blockchain nodes may question the reliability and validity of the block.

When exchanging data between devices or servers, specifications must be defined for each other, which can take a lot of time and effort. And when the application or desired data changes, an update of the application or server may be required. Additionally, if the connected device changes, the device may need to be updated.

Additionally, even if data is exchanged between devices or servers, it may be difficult to prove whether the data is trustworthy. It may be difficult for third-party devices or servers to check the data transmission history.

In one embodiment, the electronic device includes communication circuitry, a memory and a processor to store a partial ledger or full ledger including a portion of the entire ledger for a blockchain network, the ledger being the part of the electronic device participating in the consensus. It may include at least one block corresponding to each of at least one transaction. The processor creates a first transaction using a smart contract containing information about the shared data of the electronic device and the external user who will receive the shared data, and transmits the first transaction to the blockchain network. request, verify the first transaction using a node that generates at least one block corresponding to each of at least one transaction in which the electronic device participated in the agreement, and confirm the reliability of the first transaction on the blockchain network. Send a first transaction, create a first block corresponding to the first transaction, verify the second transaction based on receiving a second transaction comprising a request to provide shared data from the blockchain network, and Based on confirming the reliability of , the smart contract can be executed and a second block corresponding to the second transaction can be created.

The server may include communication circuitry, memory and a processor to store the full ledger or a partial ledger containing a portion of the full ledger. The processor receives a first transaction containing a smart contract related to shared data and information about an external user to be provided with the shared data from a first node of a first external device, and a second node of a second external device Based on receiving a second transaction including a request for provision of shared data from , Shared data can be transmitted to a second external device based on the match between the information about the second external device and the external user who will receive the shared data on the smart contract.

A method for managing data transmission of an electronic device includes the operation of creating a first transaction using a smart contract containing information about the shared data of the electronic device and an external user who will receive the shared data, the first transaction An operation to request transmission to a blockchain network, an operation to verify the first transaction and transmit the first transaction to the blockchain network based on confirming the reliability of the first transaction, and to respond to the first transaction. creating a first block, verifying the second transaction based on receiving a second transaction containing a request for provision of shared data from the blockchain network, and creating a smart contract based on verifying the authenticity of the second transaction. It may include the operation of executing and generating a second block corresponding to the second transaction.

According to one embodiment, when transmitting necessary data between applications, an electronic device can safely exchange necessary data by recording it in the ledger without a separate update.

According to one embodiment, electronic devices can easily track and manage data transmission details by recording contents in a ledger when exchanging necessary data between applications.

1 is a block diagram of an electronic device in a network environment, according to various embodiments.
Figure 2 is a hardware block diagram of an electronic device, according to one embodiment.
Figure 3a is a diagram for explaining a mobile blockchain system according to an embodiment. Figure 3b is a diagram for explaining the configuration of a blockchain network according to an embodiment.
FIG. 4 is an operational flowchart showing the relationship between an electronic device, a blockchain, and an external device, according to an embodiment.
FIG. 5A illustrates a data transmission situation through a blockchain of an electronic device according to an embodiment.
FIG. 5B illustrates a situation in which an electronic device rejects a data transmission request from an unauthorized application, according to one embodiment.
Figure 6 is a flowchart showing a data management method of an electronic device according to an embodiment.

1 is a block diagram of an electronic device 101 in a network environment 100, according to various embodiments. Referring to FIG. 1, in the network environment 100, the electronic device 101 communicates with the electronic device 102 through a first network 198 (e.g., a short-range wireless communication network) or a second network 199. It is possible to communicate with at least one of the electronic device 104 or the server 108 through (e.g., a long-distance wireless communication network). According to one embodiment, the electronic device 101 may communicate with the electronic device 104 through the server 108. According to one embodiment, the electronic device 101 includes a processor 120, a memory 130, an input module 150, an audio output module 155, a display module 160, an audio module 170, and a sensor module ( 176), interface 177, connection terminal 178, haptic module 179, camera module 180, power management module 188, battery 189, communication module 190, subscriber identification module 196 , or may include an antenna module 197. In some embodiments, at least one of these components (eg, the connection terminal 178) may be omitted or one or more other components may be added to the electronic device 101. In some embodiments, some of these components (e.g., sensor module 176, camera module 180, or antenna module 197) are integrated into one component (e.g., display module 160). It can be.

The processor 120, for example, executes software (e.g., program 140) to operate at least one other component (e.g., hardware or software component) of the electronic device 101 connected to the processor 120. It can be controlled and various data processing or calculations can be performed. According to one embodiment, as at least part of data processing or computation, the processor 120 stores commands or data received from another component (e.g., sensor module 176 or communication module 190) in volatile memory 132. The commands or data stored in the volatile memory 132 can be processed, and the resulting data can be stored in the non-volatile memory 134. According to one embodiment, the processor 120 includes a main processor 121 (e.g., a central processing unit or an application processor) or an auxiliary processor 123 that can operate independently or together (e.g., a graphics processing unit, a neural network processing unit ( It may include a neural processing unit (NPU), an image signal processor, a sensor hub processor, or a communication processor). For example, if the electronic device 101 includes a main processor 121 and a secondary processor 123, the secondary processor 123 may be set to use lower power than the main processor 121 or be specialized for a designated function. You can. The auxiliary processor 123 may be implemented separately from the main processor 121 or as part of it.

The auxiliary processor 123 may, for example, act on behalf of the main processor 121 while the main processor 121 is in an inactive (e.g., sleep) state, or while the main processor 121 is in an active (e.g., application execution) state. ), together with the main processor 121, at least one of the components of the electronic device 101 (e.g., the display module 160, the sensor module 176, or the communication module 190) At least some of the functions or states related to can be controlled. According to one embodiment, co-processor 123 (e.g., image signal processor or communication processor) may be implemented as part of another functionally related component (e.g., camera module 180 or communication module 190). there is. According to one embodiment, the auxiliary processor 123 (eg, neural network processing unit) may include a hardware structure specialized for processing artificial intelligence models. Artificial intelligence models can be created through machine learning. For example, such learning may be performed in the electronic device 101 itself on which the artificial intelligence model is performed, or may be performed through a separate server (e.g., server 108). Learning algorithms may include, for example, supervised learning, unsupervised learning, semi-supervised learning, or reinforcement learning, but It is not limited. An artificial intelligence model may include multiple artificial neural network layers. Artificial neural networks include deep neural network (DNN), convolutional neural network (CNN), recurrent neural network (RNN), restricted boltzmann machine (RBM), belief deep network (DBN), bidirectional recurrent deep neural network (BRDNN), It may be one of deep Q-networks or a combination of two or more of the above, but is not limited to the examples described above. In addition to hardware structures, artificial intelligence models may additionally or alternatively include software structures.

The memory 130 may store various data used by at least one component (eg, the processor 120 or the sensor module 176) of the electronic device 101. Data may include, for example, input data or output data for software (e.g., program 140) and instructions related thereto. Memory 130 may include volatile memory 132 or non-volatile memory 134.

The program 140 may be stored as software in the memory 130 and may include, for example, an operating system 142, middleware 144, or application 146.

The input module 150 may receive commands or data to be used in a component of the electronic device 101 (e.g., the processor 120) from outside the electronic device 101 (e.g., a user). The input module 150 may include, for example, a microphone, mouse, keyboard, keys (eg, buttons), or digital pen (eg, stylus pen).

The sound output module 155 may output sound signals to the outside of the electronic device 101. The sound output module 155 may include, for example, a speaker or a receiver. Speakers can be used for general purposes such as multimedia playback or recording playback. The receiver can be used to receive incoming calls. According to one embodiment, the receiver may be implemented separately from the speaker or as part of it.

The display module 160 can visually provide information to the outside of the electronic device 101 (eg, a user). The display module 160 may include, for example, a display, a hologram device, or a projector, and a control circuit for controlling the device. According to one embodiment, the display module 160 may include a touch sensor configured to detect a touch, or a pressure sensor configured to measure the intensity of force generated by the touch.

The audio module 170 can convert sound into an electrical signal or, conversely, convert an electrical signal into sound. According to one embodiment, the audio module 170 acquires sound through the input module 150, the sound output module 155, or an external electronic device (e.g., directly or wirelessly connected to the electronic device 101). Sound may be output through the electronic device 102 (e.g., speaker or headphone).

The sensor module 176 detects the operating state (e.g., power or temperature) of the electronic device 101 or the external environmental state (e.g., user state) and generates an electrical signal or data value corresponding to the detected state. can do. According to one embodiment, the sensor module 176 includes, for example, a gesture sensor, a gyro sensor, an air pressure sensor, a magnetic sensor, an acceleration sensor, a grip sensor, a proximity sensor, a color sensor, an IR (infrared) sensor, a biometric sensor, It may include a temperature sensor, humidity sensor, or light sensor.

The interface 177 may support one or more designated protocols that can be used to connect the electronic device 101 directly or wirelessly with an external electronic device (eg, the electronic device 102). According to one embodiment, the interface 177 may include, for example, a high definition multimedia interface (HDMI), a universal serial bus (USB) interface, an SD card interface, or an audio interface.

The connection terminal 178 may include a connector through which the electronic device 101 can be physically connected to an external electronic device (eg, the electronic device 102). According to one embodiment, the connection terminal 178 may include, for example, an HDMI connector, a USB connector, an SD card connector, or an audio connector (eg, a headphone connector).

The haptic module 179 can convert electrical signals into mechanical stimulation (e.g., vibration or movement) or electrical stimulation that the user can perceive through tactile or kinesthetic senses. According to one embodiment, the haptic module 179 may include, for example, a motor, a piezoelectric element, or an electrical stimulation device.

The camera module 180 can capture still images and moving images. According to one embodiment, the camera module 180 may include one or more lenses, image sensors, image signal processors, or flashes.

The power management module 188 can manage power supplied to the electronic device 101. According to one embodiment, the power management module 188 may be implemented as at least a part of, for example, a power management integrated circuit (PMIC).

The battery 189 may supply power to at least one component of the electronic device 101. According to one embodiment, the battery 189 may include, for example, a non-rechargeable primary battery, a rechargeable secondary battery, or a fuel cell.

Communication module 190 is configured to provide a direct (e.g., wired) communication channel or wireless communication channel between electronic device 101 and an external electronic device (e.g., electronic device 102, electronic device 104, or server 108). It can support establishment and communication through established communication channels. Communication module 190 operates independently of processor 120 (e.g., an application processor) and may include one or more communication processors that support direct (e.g., wired) communication or wireless communication. According to one embodiment, the communication module 190 is a wireless communication module 192 (e.g., a cellular communication module, a short-range wireless communication module, or a global navigation satellite system (GNSS) communication module) or a wired communication module 194 (e.g., : LAN (local area network) communication module, or power line communication module) may be included. Among these communication modules, the corresponding communication module is a first network 198 (e.g., a short-range communication network such as Bluetooth, wireless fidelity (WiFi) direct, or infrared data association (IrDA)) or a second network 199 (e.g., legacy It may communicate with an external electronic device 104 through a telecommunication network such as a cellular network, a 5G network, a next-generation communication network, the Internet, or a computer network (e.g., LAN or WAN). These various types of communication modules may be integrated into one component (e.g., a single chip) or may be implemented as a plurality of separate components (e.g., multiple chips). The wireless communication module 192 uses subscriber information (e.g., International Mobile Subscriber Identifier (IMSI)) stored in the subscriber identification module 196 within a communication network such as the first network 198 or the second network 199. The electronic device 101 can be confirmed or authenticated.

The wireless communication module 192 may support 5G networks after 4G networks and next-generation communication technologies, for example, NR access technology (new radio access technology). NR access technology provides high-speed transmission of high-capacity data (eMBB (enhanced mobile broadband)), minimization of terminal power and access to multiple terminals (mMTC (massive machine type communications)), or high reliability and low latency (URLLC (ultra-reliable and low latency). -latency communications)) can be supported. The wireless communication module 192 may support high frequency bands (eg, mmWave bands), for example, to achieve high data rates. The wireless communication module 192 uses various technologies to secure performance in high frequency bands, for example, beamforming, massive array multiple-input and multiple-output (MIMO), and full-dimensional multiplexing. It can support technologies such as input/output (FD-MIMO: full dimensional MIMO), array antenna, analog beam-forming, or large scale antenna. The wireless communication module 192 may support various requirements specified in the electronic device 101, an external electronic device (e.g., electronic device 104), or a network system (e.g., second network 199). According to one embodiment, the wireless communication module 192 supports Peak data rate (e.g., 20 Gbps or more) for realizing eMBB, loss coverage (e.g., 164 dB or less) for realizing mmTC, or U-plane latency (e.g., 164 dB or less) for realizing URLLC. Example: Downlink (DL) and uplink (UL) each of 0.5 ms or less, or round trip 1 ms or less) can be supported.

The antenna module 197 may transmit or receive signals or power to or from the outside (eg, an external electronic device). According to one embodiment, the antenna module 197 may include an antenna including a radiator made of a conductor or a conductive pattern formed on a substrate (eg, PCB). According to one embodiment, the antenna module 197 may include a plurality of antennas (eg, an array antenna). In this case, at least one antenna suitable for a communication method used in a communication network such as the first network 198 or the second network 199 is connected to the plurality of antennas by, for example, the communication module 190. can be selected. Signals or power may be transmitted or received between the communication module 190 and an external electronic device through the at least one selected antenna. According to some embodiments, in addition to the radiator, other components (eg, radio frequency integrated circuit (RFIC)) may be additionally formed as part of the antenna module 197.

According to one embodiment, the antenna module 197 may form a mmWave antenna module. According to one embodiment, a mmWave antenna module includes: a printed circuit board, an RFIC disposed on or adjacent to a first side (e.g., bottom side) of the printed circuit board and capable of supporting a designated high frequency band (e.g., mmWave band); And a plurality of antennas (e.g., array antennas) disposed on or adjacent to the second side (e.g., top or side) of the printed circuit board and capable of transmitting or receiving signals in the designated high frequency band. can do.

At least some of the components are connected to each other through a communication method between peripheral devices (e.g., bus, general purpose input and output (GPIO), serial peripheral interface (SPI), or mobile industry processor interface (MIPI)) and signal ( (e.g. commands or data) can be exchanged with each other.

According to one embodiment, commands or data may be transmitted or received between the electronic device 101 and the external electronic device 104 through the server 108 connected to the second network 199. Each of the external electronic devices 102 or 104 may be of the same or different type as the electronic device 101. According to one embodiment, all or part of the operations performed in the electronic device 101 may be executed in one or more of the external electronic devices 102, 104, or 108. For example, when the electronic device 101 needs to perform a certain function or service automatically or in response to a request from a user or another device, the electronic device 101 may perform the function or service instead of executing the function or service on its own. Alternatively, or additionally, one or more external electronic devices may be requested to perform at least part of the function or service. One or more external electronic devices that have received the request may execute at least part of the requested function or service, or an additional function or service related to the request, and transmit the result of the execution to the electronic device 101. The electronic device 101 may process the result as is or additionally and provide it as at least part of a response to the request. For this purpose, for example, cloud computing, distributed computing, mobile edge computing (MEC), or client-server computing technology can be used. The electronic device 101 may provide an ultra-low latency service using, for example, distributed computing or mobile edge computing. In another embodiment, the external electronic device 104 may include an Internet of Things (IoT) device. Server 108 may be an intelligent server using machine learning and/or neural networks. According to one embodiment, the external electronic device 104 or server 108 may be included in the second network 199. The electronic device 101 may be applied to intelligent services (e.g., smart home, smart city, smart car, or healthcare) based on 5G communication technology and IoT-related technology.

Electronic devices according to various embodiments disclosed in this document may be of various types. Electronic devices may include, for example, portable communication devices (e.g., smartphones), computer devices, portable multimedia devices, portable medical devices, cameras, wearable devices, or home appliances. Electronic devices according to embodiments of this document are not limited to the above-described devices.

The various embodiments of this document and the terms used herein are not intended to limit the technical features described in this document to specific embodiments, and should be understood to include various changes, equivalents, or replacements of the embodiments. In connection with the description of the drawings, similar reference numbers may be used for similar or related components. The singular form of a noun corresponding to an item may include one or more of the above items, unless the relevant context clearly indicates otherwise. As used herein, “A or B”, “at least one of A and B”, “at least one of A or B”, “A, B or C”, “at least one of A, B and C”, and “A Each of phrases such as “at least one of , B, or C” may include any one of the items listed together in the corresponding phrase, or any possible combination thereof. Terms such as "first", "second", or "first" or "second" may be used simply to distinguish one component from another, and to refer to that component in other respects (e.g., importance or order) is not limited. One (e.g., first) component is said to be “coupled” or “connected” to another (e.g., second) component, with or without the terms “functionally” or “communicatively.” When mentioned, it means that any of the components can be connected to the other components directly (e.g. wired), wirelessly, or through a third component.

The term “module” used in various embodiments of this document may include a unit implemented in hardware, software, or firmware, and is interchangeable with terms such as logic, logic block, component, or circuit, for example. It can be used as A module may be an integrated part or a minimum unit of the parts or a part thereof that performs one or more functions. For example, according to one embodiment, the module may be implemented in the form of an application-specific integrated circuit (ASIC).

Various embodiments of the present document are one or more instructions stored in a storage medium (e.g., built-in memory 136 or external memory 138) that can be read by a machine (e.g., electronic device 101). It may be implemented as software (e.g., program 140) including these. For example, a processor (e.g., processor 120) of a device (e.g., electronic device 101) may call at least one command among one or more commands stored from a storage medium and execute it. This allows the device to be operated to perform at least one function according to the at least one instruction called. The one or more instructions may include code generated by a compiler or code that can be executed by an interpreter. A storage medium that can be read by a device may be provided in the form of a non-transitory storage medium. Here, 'non-transitory' only means that the storage medium is a tangible device and does not contain signals (e.g. electromagnetic waves), and this term refers to cases where data is semi-permanently stored in the storage medium. There is no distinction between temporary storage cases.

According to one embodiment, methods according to various embodiments disclosed in this document may be included and provided in a computer program product. Computer program products are commodities and can be traded between sellers and buyers. The computer program product may be distributed in the form of a machine-readable storage medium (e.g. compact disc read only memory (CD-ROM)) or through an application store (e.g. Play StoreTM) or on two user devices (e.g. It can be distributed (e.g. downloaded or uploaded) directly between smart phones) or online. In the case of online distribution, at least a portion of the computer program product may be at least temporarily stored or temporarily created in a machine-readable storage medium, such as the memory of a manufacturer's server, an application store's server, or a relay server.

According to various embodiments, each component (e.g., module or program) of the above-described components may include a single or plural entity, and some of the plurality of entities may be separately placed in other components. there is. According to various embodiments, one or more of the components or operations described above may be omitted, or one or more other components or operations may be added. Alternatively or additionally, multiple components (eg, modules or programs) may be integrated into a single component. In this case, the integrated component may perform one or more functions of each component of the plurality of components in the same or similar manner as those performed by the corresponding component of the plurality of components prior to the integration. . According to various embodiments, operations performed by a module, program, or other component may be executed sequentially, in parallel, iteratively, or heuristically, or one or more of the operations may be executed in a different order, or omitted. Alternatively, one or more other operations may be added.

Figure 2 is a hardware block diagram of an electronic device, according to one embodiment.

Referring to FIG. 2, the electronic device 101 (e.g., the electronic device 101 of FIG. 1) according to an embodiment includes a display 210 (e.g., the display device 160 of FIG. 1) and a communication circuit 220. ) (e.g., the communication module 190 of FIG. 1), a memory 230 (e.g., the memory 130 of FIG. 1, and a processor 240 (e.g., the processor 120 of FIG. 1), Some of the components of Figure 1 may be added.

According to one embodiment, the electronic device 101 may further include a blockchain management module 245. The blockchain management module 245 may be driven by blockchain management software (SW) (e.g., blockchain keystore).

The display 210 may output information related to the blockchain network under the control of the processor 240. The display 210 may output data processed by a general OS and data processed by a secure OS under the control of the processor 240.

The communication circuit 220 can transmit and receive data based on a blockchain network. For example, the blockchain network may be, but is not limited to, the Ethereum network.

According to one embodiment, the communication circuit 220 may transmit a smart contract to a blockchain network under the control of the processor 240. The smart contract sent to the blockchain is synchronized with all nodes in the blockchain, so the contents of the smart contract can be made public to all nodes in the blockchain. Smart contract is an automated contract technology based on blockchain and can refer to a computer transaction protocol that executes the terms of a contract. For example, a smart contract can refer to a digital contract method in which contract terms are coded based on blockchain technology and the contract is implemented when the conditions are met.

According to one embodiment, the communication circuit 220 receives blockchain data (e.g., a message) when connecting to a blockchain network, or data signed with a private key stored in the electronic device 101 (e.g., an electronically signed message). It can be transmitted to the blockchain network.

Memory 230 may store information related to the blockchain. For example, the memory 230 may store at least one of a decentralized application accessible through a blockchain network, a cryptocurrency wallet application, a blockchain security application, and a secure user interface application. For example, decentralized applications and cryptocurrency wallet applications may operate in a rich execution environment (REE), while blockchain security applications and secure user interface applications may operate in a trunsted execution environment (TEE). When operating in a secure OS, data stored may be stored in an encrypted state. The electronic device 101 may include a separate secure storage area (e.g., embedded secure element (eSE), embedded subscriber identity module (eSIM)) for blockchain management in the memory 230.

According to one embodiment, the memory 230 may store blockchain management software (SW). Blockchain management software may be software (e.g., an android package kit (APK) file) applied to mobile devices such as smartphones. Blockchain management software may be built into or installed on the electronic device 101. Alternatively, blockchain management software can be downloaded from a server through the App Store and installed on an electronic device.

The processor 240 may perform operations or data processing related to control and/or communication of each component of the electronic device 101. The processor 240 may include at least some of the components and/or functions of the processor 120 of FIG. 1 . The processor 240 may control the operation of the blockchain management module 245 based on blockchain management software.

According to one embodiment, the processor 240 may be operated separately into a general OS and a security OS. The resource area operated when the processor 240 runs in a general OS can be understood as a general area, and the resource area operated when the processor 240 runs in a secure OS can be understood as a security area.

According to one embodiment, the processor 240 may control at least one of blockchain management software, cryptocurrency application, and decentralized application to perform access, approval, and transaction operations of the blockchain network.

According to one embodiment, the blockchain management module 245 may operate by blockchain management software under the control of the processor 240. The blockchain management module 245 can process data of blockchain security applications and security user interface applications running on a security OS in conjunction with blockchain network-related applications. The blockchain management module 245 can be understood to have the same meaning as blockchain management software.

According to one embodiment, the blockchain management module 245 applies an encryption algorithm based on the blockchain message at the time of the wallet account through the cryptocurrency wallet application to generate the public key and private key used in the blockchain network. (private key) can be created.

According to another embodiment, the blockchain management module 245 applies an encryption algorithm based on the user personal information and blockchain message set in the electronic device 101 when creating a wallet account to use a public key (public key) used in the blockchain network. key) and private key can be generated.

According to one embodiment, the blockchain management module 245 may generate a public key and a private key as a pair. The private key generated by the blockchain management module 245 may be stored or recorded in blockchain management software. Public keys can be transferred to blockchain networks through cryptocurrency wallet applications and decentralized applications.

According to one embodiment, the blockchain management module 245 may perform an electronic signature on a message delivered through a cryptocurrency wallet application using a private key stored based on an encryption algorithm within a secure area.

According to one embodiment, the blockchain management module 245 may configure a user authentication request screen to confirm signature authentication from the user based on the signature authentication request message delivered to the security area. The processor 240 may control the authentication request screen to be output on the display 210 . Blockchain management module 245 may receive user authentication input. The blockchain management module 245 may perform an electronic signature on the signature authentication request message using the private key stored in the secure area of the memory 230 in response to user authentication input information.

According to one embodiment, when the user authentication input information includes user personal information, the blockchain management module 245 may perform an electronic signature under the condition that the user personal information and the set user personal information match.

If it does not match the user's personal information, the blockchain management module 245 may not perform an electronic signature or may perform an electronic signature with information that is different from the public key and the corresponding private key. If the electronic signature is incorrect, the blockchain can recognize that the user account of the electronic device 101 is not a legitimate participant due to the incorrectly signed message.

According to one embodiment, the blockchain management module 245 may deliver the electronically signed message to a cryptocurrency wallet application operating in a general area of memory.

According to one embodiment, the processor 240 may transmit the electronically signed message delivered to the cryptocurrency wallet application to the blockchain network through the decentralized application. The electronic device 101 can use the blockchain network service when verification of participants in the blockchain network is completed.

Figure 3a is a diagram for explaining a mobile blockchain system according to an embodiment.

Referring to FIG. 3A, according to one embodiment, an electronic device (e.g., electronic device 101 of FIG. 1) in a mobile blockchain network communicates with at least one device through a communication module (e.g., communication module 190 of FIG. 1). A blockchain network can be formed with external electronic devices.The electronic device 101 can transmit and receive data with at least one external electronic device included in the blockchain network and participate in transaction agreement in the blockchain network.

According to one embodiment, a mobile blockchain network may be composed of a plurality of electronic devices (301, 302, 303, and 304).

The plurality of electronic devices 301, 302, 303, and 304 include a plurality of mobile nodes (or participating nodes) (e.g., 301, 302, 303) participating in the blockchain service and a relay node (or server node) (e.g., 304) connecting each mobile node. can do. A mobile node (e.g., 301, 302, or 303) may be a portable electronic device (e.g., a cell phone, tablet PC, or laptop). The relay node (e.g. 304) may be a server device.

According to one embodiment, the mobile nodes 301, 302, and 303 and the relay node 304 included in the blockchain network may store (or own) the entire ledger or partial ledger, respectively.

According to one embodiment, the relay node 304 (or an electronic device serving as a relay) may be configured to participate in the execution of all transactions. The relay node 304 can record all blocks and consensus on all transactions in the blockchain network. The relay node 304 participates in consensus on all transactions and can store blocks and state data of all transactions in the blockchain network. The relay node 304 can store the entire ledger, which is a distributed ledger of the blockchain network.

According to one embodiment, the relay node 304 may transmit a wake-up signal (e.g., wake up signal, push message) to a mobile node (e.g., 301, 302 or 303) that is in an inactive state (e.g., idle/sleep state). . The mobile node (e.g., 301, 302 or 303) switches to an active state (e.g., running state) in response to receiving a wake-up signal from the relay node 304 and can participate in blockchain network services by connecting to the blockchain network. . The mobile node (eg, 301, 302 or 303) may receive a wake-up signal and transmit a response signal to the wake-up signal to the relay node 304. When the relay node 304 receives a response signal from a mobile node (e.g., 301, 302 or 303) participating in the transaction, it can relay it to create a transaction and perform a consensus operation between nodes.

According to one embodiment, a mobile node (or electronic devices used as a mobile node) (eg, 301, 302 or 303) may record the creation and block of transactions related to each electronic device.

According to one embodiment, mobile nodes (e.g., 301, 302 or 303) may be configured to only participate in the execution of transactions related to each electronic device. For example, a mobile node (e.g., 301,302 or 303) may participate in transaction consensus related to a user (or user device) and store only the block and state data of the transaction (e.g., a partial ledger) of the entire ledger of the blockchain network. there is. Mobile nodes (e.g., 301, 302 or 303) can store partial ledgers related to each electronic device among the distributed ledgers of the blockchain network.

According to one embodiment, a mobile node (e.g., 301, 302 or 303) executes a smart contract based on state data and determines whether to execute a transaction based on the results of a consensus process performed between other mobile nodes and each other. You can. For example, a mobile node (e.g., 301, 302 or 303) may determine that the agreement is successful if the resulting values generated by executing the smart contract match.

According to one embodiment, some of the mobile nodes participating in the blockchain network (e.g., 301 or 302) may store (or own) a partial ledger of the distributed ledger of the blockchain network. The mobile node (e.g. 301 or 302) that stores the partial ledger can be a node that requests transaction creation in the blockchain network, and can be a node that performs a consensus operation for the transaction according to the transaction creation request.

Figure 3b is a diagram for explaining the configuration of a blockchain network according to an embodiment.

According to one embodiment, the blockchain platform 300 is a blockchain application that performs a blockchain-related operation stored in the memory 130 of FIG. 1 or a blockchain application that performs a blockchain-related operation included in the processor 120 of FIG. 1. It can correspond to a blockchain module.

Referring to FIG. 3B, the blockchain platform 300 may include a smart contract 310, a distributed ledger 320, and/or a blockchain processor 330. The blockchain platform 300 may further include various components or some components may be omitted to perform operations related to the blockchain.

In one embodiment, distributed ledger 320 may store data about transactions related to electronic device 101 in a blockchain network.

According to one embodiment, the distributed ledger 320 may be a partial ledger that includes at least a portion of the entire ledger rather than the entire ledger of the blockchain network. For example, distributed ledger 320 may include a partial ledger containing blocks and data for transactions involving electronic device 101 among the overall ledger that stores blocks and data associated with all transactions in the blockchain network. there is.

According to another embodiment, distributed ledger 320 may include an overall ledger that stores blocks and data related to all transactions in a blockchain network.

According to one embodiment, the distributed ledger 320 may include at least one block 321 and a state database (data base) 322 generated through a blockchain network. Block 321 may be composed of transactions containing information for performing the smart contract 310. In one embodiment, blocks of the distributed ledger 320 are in the form of a blockchain and may include block data. For example, block 321 may include a hash field and block data. The hash field may include previous block information in the entire ledger of the blockchain network and previous block information in the partial ledger of the blockchain network.

According to one embodiment, at least one block 321 constituting the blockchain may be expressed as being connected based on previous block information included in the hash field. For example, at least one block 321 constituting a blockchain may be connected in a directed acyclic graph (DAG) structure. According to one embodiment, when at least one block included in the entire ledger of the blockchain network is connected in a DAG structure, the partial ledger of the blockchain network may be connected in a subgraph structure of the entire ledger.

The state database 322 can store values changed due to transaction execution in the blockchain network in key-value form. In one embodiment, data stored in the state database 322 may be expressed as state data. State data may refer, for example, to data stored in world state, a database used in Hyperledger Fabric. However, it is not limited to this.

The state database 322 is a type of database used in Hyperledger Fabric, and can store final values changed by executing a transaction in the form of key values. Accordingly, the electronic device 101 can check the state database 322 to confirm final values resulting from transaction execution within the blockchain network. State data stored in the state database 322 may have characteristics such as global variables within the blockchain network.

According to one embodiment, the state database 322 may store data about transactions in which the user of the electronic device 101 participates. For example, in a blockchain network, values changed due to execution of a transaction related to the electronic device 101 may be stored.

According to one embodiment, the blockchain processor 330 can control the operation of components included in the blockchain platform 300. For example, blockchain processor 330 may perform execution of transactions, including synchronizing ledgers, signing transactions, and/or performing transaction records on a blockchain network.

According to one embodiment, the blockchain processor 330 may perform operations related to a blockchain network in which the electronic device 101 participates as a node (eg, a mobile node). According to one embodiment, the blockchain processor 330 can form a blockchain network and perform operations related to other nodes (external electronic devices) included in the blockchain network.

FIG. 4 is an operational flowchart showing the relationship between an electronic device, a blockchain, and an external device, according to an embodiment.

Referring to the operation flow chart 400, the electronic device 410 (e.g., the electronic device 101 in FIG. 1) may transmit a smart contract for transmission of shared data to the blockchain 420, and the external device 430 ) (e.g., a server of a company providing a service) can request the provision of personal information to the blockchain 420 (or blockchain network) and receive shared data from the blockchain 420 based on a smart contract. there is.

According to one embodiment, the electronic device 410 may create a smart contract in operation 401. The smart contract may be, for example, a contract for personal information transaction between the user of the electronic device 410 and the external device 430. External user refers to a user of an external device. The external device may include information about the external user, and an operation performed by the external device may be recognized as an operation performed by the external user. A smart contract may include information about shared data on the electronic device and external users who will receive the shared data.

According to one embodiment, the processor of the electronic device 410 (e.g., the processor 240 of FIG. 2) may create a smart contract regarding the transmission of shared data. A smart contract regarding the transmission of shared data may include, for example, information about data to be provided to external users and information about external users to provide personal information. Contents included in the smart contract can be set by the user of the electronic device 410. The processor 240 may control the display 230 to output a settings screen for setting shared data to be provided to external users and external users who will receive the shared data.

In operation 403, the electronic device 410 may transmit the smart contract to the blockchain 420.

At operation 405, the transmitted smart contract may be synchronized on blockchain 420. Smart contracts synchronized to the blockchain 420 are disclosed to all users (e.g., multiple nodes) within the blockchain 420 and are distributed and stored. When transacting through a smart contract based on the blockchain 420, transparency of transactions can be increased and stability against forgery/tampering can be increased.

In operation 407, the external device 430 may request the blockchain 420 to provide data. For example, the external device 430 may request desired data through a query. A query may refer to a request from a specific subject (e.g., external device 430) to show specific data to the database. In operation 409, the blockchain 420 may execute a smart contract based on a data provision request from the external device 430. When the blockchain 420 receives a query request for personal information from the external device 430, a smart contract synchronized to the blockchain 420 may be executed. When a smart contract synchronized to the blockchain 420 is executed, the blockchain 420 may transmit a data provision request to the electronic device 410 in response to the execution of the smart contract. In operation 411, the blockchain ( 420) may transmit a request to provide data according to execution of a smart contract to the electronic device 410. The blockchain 420 according to one embodiment can check whether the data requested by the external device 430 meets the data provision conditions in the smart contract. If the personal information requested by the external device 430 meets the information provision conditions in the smart contract, the blockchain 420 may transmit a data provision request to the electronic device 410 that is a party to the smart contract. If the personal information requested by the external device 430 does not meet the data provision conditions in the smart contract, the blockchain 420 may not execute the smart contract. If the smart contract is not executed, the blockchain 420 may not transmit a data provision request to the electronic device 410.

In operation 413, the electronic device 410 may check whether the data provision request from the external device 430 meets the data provision conditions included in the smart contract. For example, the electronic device 410 determines whether the external user of the external device 430 that requested data corresponds to an external user to be provided with data included in a smart contract and whether the data requested by the external device 430 is a smart contract. You can check whether it is included in the information category that can be provided to external users included in the contract.

In one embodiment, if the data requested by the external device 430 meets the data provision conditions in the smart contract, the electronic device 410 may process the information to match the information de-identification level in the smart contract. Methods of processing data include, for example, pseudonymization, aggregation, data reduction, data suppression, data masking or differential privacy. It may be a method of de-identifying data using at least one of the following methods.

In operation 417, the electronic device 410 may transmit the processed information to the blockchain 420. The method of transmitting to the blockchain 420 may be, for example, a method by which the electronic device 410 performs a transaction. A smart contract transmitted to the blockchain 420 can be executed through a transaction performed by the electronic device 410.

In operation 419, the blockchain 420 may execute a smart contract in response to receiving processed information from the electronic device 410. Transactions performed by the electronic device 410 may execute a smart contract on the blockchain 420.

In operation 421, the blockchain 420 may transmit processed data in response to execution of the smart contract to the external device 430.

FIG. 5A illustrates a data transmission situation through a blockchain of an electronic device according to an embodiment.

In one embodiment, the electronic device 101 may include a first application 510 and a first node 515. The first node 515 may refer to a specific application running on the electronic device 101, for example. Certain applications may provide functions related to performing the role of a blockchain node. The first node 515 can perform ledger management. The ledger can record the information of the subject wishing to transmit data, the data to be transmitted, and the authority to determine whether the recipient is a restricted recipient. The first node 515 can perform the role of a blockchain node.

In one embodiment, the first application 510 may use the first node 515. The first application 510 may store the smart contract in an uncompiled state. The first application 510 may request to create a transaction on the first node 515 for data to be recorded in the blockchain ledger. A transaction can refer to a unit of work performed by changing the state of the database.

In operation 501, the first application 510 may request the first node 515 to create a first transaction 512. The first transaction 512 may include information about data to be shared (e.g., key1/data1) and a target to allow sharing. The first application 510 may allow sharing only to limited applications (eg, the second application 520), or may allow sharing to all applications (or user terminals) without limitation. The subjects for which sharing is permitted are not limited to this and may vary depending on the settings on the first application 510.

At operation 502, the first node 515 may perform verification of the first transaction 512. The first node 515 can verify who the signer of the transaction is. The first node 515 can verify whether the parameter values of the smart contract are correct. The first node 515 can check whether the smart contract can be executed normally.

In operation 503, the first node 515 may request block generation from a consensus node (not shown). When a block is created, the first node 515 can notify the nodes constituting the blockchain network 530 of the block creation. Consensus nodes can create blocks based on transaction submission requests. Consensus nodes can have original data from the ledger. Depending on the configuration of the blockchain network 530, the consensus node may have an address containing a hash value and original data, rather than the original data. The blockchain network 530 can connect and store the created blocks (e.g., the first block 531 and the second block 532). The first block 531 and the second block 532 may be generated based on a transaction submission request from the consensus node. The second block 532 may be created after the first block 531 is created and may be connected to the first block 531.

In operation 504, the first node 515 may notify the first application 510 of the verified transaction and block creation.

In one embodiment, the external device 103 may include a second application 520 and a second node 525. The second node 525 may perform ledger management. The ledger can record the information of the subject wishing to transmit data, the data to be transmitted, and the authority to determine whether the recipient is a restricted recipient. The second node 525 can perform the role of a blockchain node. The second application 520 may use the first node 525. The second application 520 may store the smart contract in an uncompiled state. The second application 520 may request the creation of a transaction on the second node 525 for data to be recorded in the blockchain ledger.

In operation 505, the second application 520 may request the creation of a second transaction 522 on the second node 525. The second transaction 522 may include information about data to be transmitted. Information about the data to be transmitted may include, for example, information about the data1 value corresponding to key1 among app1data.

At operation 506, the second node 525 may perform verification of the second transaction 522. The second node 525 can verify who the signer of the transaction is. The second node 525 can verify whether the parameter values of the smart contract are correct. The second node 525 can check whether the smart contract can be executed normally. The second node 525 can obtain information about the object to be shared on the smart contract. The second node 525 may check whether the second application 520 is included in the list of subjects for which sharing is permitted.

In operation 507, the second node 525 may request a consensus node (not shown) to generate a block based on confirmation that the second application 520 is included in the list of subjects for which sharing is permitted. When a block is created, the second node 525 can notify the nodes constituting the blockchain network 530 of the block creation. Nodes constituting the blockchain network 530 may connect the corresponding block (e.g., the third block 533) to existing blocks (e.g., the first block 531 and the second block 532). The third block 533 may be generated temporally after the first block 531 and the second block 532 are created.

In operation 508, the second node 525 may notify the second application 520 of the verified transaction and block creation. The second node 525 may transmit the data requested by the second application 520 to the second application 520 .

FIG. 5B illustrates a situation in which an electronic device rejects a data transmission request from an unauthorized application, according to one embodiment.

In one embodiment, the electronic device 101 may include a first application 510 and a first node 515. The first node 515 can perform ledger management. The ledger can record the information of the subject wishing to transmit data, the data to be transmitted, and the authority to determine whether the recipient is a restricted recipient. The first node 515 can perform the role of a blockchain node. The first application 510 may use the first node 515. The first application 510 may store the smart contract in an uncompiled state. The first application 510 may request to create a transaction on the first node 515 for data to be recorded in the blockchain ledger.

In operation 501, the first application 510 may request the first node 515 to create a first transaction 512. The first transaction 512 may include data to be shared (e.g., key1/data1) and information about a target to allow sharing (e.g., a second application 520 or a second user).

At operation 502, the first node 515 may perform verification of the first transaction 512. The first node 515 can verify who the signer of the transaction is. The first node 515 can verify whether the parameter values of the smart contract are correct. The first node 515 can check whether the smart contract can be executed normally.

In operation 503, the first node 515 may request block generation from a consensus node (not shown). When a block is created, the first node 515 can notify the nodes constituting the blockchain network 530 of the block creation.

In operation 504, the first node 515 may notify the first application 510 of the verified transaction and block creation.

In one embodiment, the external device 103 may include a second application 520 and a second node 525. The second node 525 may perform ledger management. The ledger can record the information of the subject wishing to transmit data, the data to be transmitted, and the authority to determine whether the recipient is a restricted recipient. The second node 525 can perform the role of a blockchain node. The second application 520 may use the first node 525. The second application 520 may store the smart contract in an uncompiled state. The second application 520 may request the creation of a transaction on the second node 525 for data to be recorded in the blockchain ledger.

In operation 505, the second application 520 may request the creation of a second transaction 522 on the second node 525. The second transaction 522 may include information about data to be transmitted. Information about the data to be transmitted may include, for example, information about the data1 value corresponding to key1 among app1data.

At operation 506, the second node 525 may perform verification of the second transaction 522. The second node 525 can verify who the signer of the transaction is. The second node 525 can verify whether the parameter values of the smart contract are correct. The second node 525 can check whether the smart contract can be executed normally. The second node 525 can obtain information about the object to be shared on the smart contract. The second node 525 may check whether the second application 520 is included in the list of subjects for which sharing is permitted. The second node 525 may not send the second transaction 522 to the blockchain network 530 based on confirmation that the second application 520 is not included in the list of subjects for which sharing is permitted.

In operation 508, the second node 525 may transmit a signal (eg, a fail indication) indicating that the requested data cannot be sent to the second application 520.

Figure 6 is a flowchart showing a data management method of an electronic device according to an embodiment.

Operations described with reference to FIG. 6 may be implemented based on instructions that can be stored in a computer recording medium or memory (eg, memory 130 in FIG. 1). The illustrated method 600 can be executed by the electronic device previously described with reference to FIGS. 1 to 5 (e.g., the electronic device 101 of FIG. 2), and technical features described above will be omitted below. The order of each operation in FIG. 6 may be changed, some operations may be omitted, and some operations may be performed simultaneously.

In operation 610, the processor (e.g., processor 240 in FIG. 2) uses a smart contract that includes shared data of the electronic device 101 and information about external users who will receive the shared data. You can create a transaction. A transaction can refer to a unit of work performed by changing the state of the database.

In operation 620, the processor 240 may request to transmit the first transaction to a blockchain network (eg, blockchain network 530 in FIG. 5A).

At operation 630, the processor 240 sends a first block (e.g., first block 531 in FIG. 5A) corresponding to the first transaction onto a first node (e.g., first node 515 in FIG. 5A). You can request to create it. The first node 515 may verify the first transaction. The first node 515 can perform ledger management. The ledger can record the information of the subject wishing to transmit data, the data to be transmitted, and the authority to determine whether the recipient is a restricted recipient. The first node 515 can perform the role of a blockchain node. The first node 515 may transmit the first transaction on the blockchain network based on confirming the reliability of the first transaction and generate the first block 531 corresponding to the first transaction. The electronic device 101 may include a first node 515 that generates a block. The electronic device 101 can use the first node 515 to verify the reliability of data requesting block creation. For example, the electronic device 101 may store a file created in a verified application on a memory (e.g., memory 230 of FIG. 2) and simultaneously request the creation of a non-fungible token (NFT). The electronic device 101 can confirm that the file for which NFT (non-fungible token) creation is requested was created by a specific user because the application has already been verified. The first node 515 may have the form of an application or a server. The first node 515 may further include a value corresponding to the owner in addition to the key and value. The processor 240 can use the value corresponding to the owner to verify the user who has the authority to change the key and value.

In operation 640, the processor 240 may receive a second transaction including a request to provide shared data from the blockchain network 530. Processor 240 may request verification of the second transaction on first node 515.

At operation 650, the first node 515 may execute the smart contract based on verifying the authenticity of the second transaction. The first node 515 may generate a block corresponding to the second transaction.

In one embodiment, the first node 515 may request block generation from a consensus node (not shown). When a block is created, the first node 515 can notify the nodes constituting the blockchain network 530 of the block creation. Consensus nodes can create blocks based on transaction submission requests. Consensus nodes can have original data from the ledger. Depending on the configuration of the blockchain network 530, the consensus node may have an address containing a hash value and original data, rather than the original data.

In one embodiment, the first node 515 may send the second transaction back onto the second node (e.g., the second node 525 in FIG. 5A) if it fails to confirm the authenticity of the second transaction. The first node 515 executes the second transaction on the second node 525 when the information about the second node 525 that requested execution of the second transaction does not match the information about the external user who will receive the shared data. can be sent back. The first node 515 may refuse to create a block corresponding to the second transaction.

In one embodiment, an electronic device (e.g., electronic device 101 of FIG. 1) includes a communication circuit (e.g., communication circuit 220 of FIG. 2), a portion of the overall ledger for a blockchain network. It includes a memory (e.g., memory 230 in FIG. 2) and a processor (e.g., processor 240 in FIG. 2) that stores a partial ledger or an entire ledger, and the ledger is at least one in which the electronic device 101 participates in the agreement. It may contain at least one block corresponding to each transaction. The processor 240 creates a first transaction using a smart contract containing information about the shared data of the electronic device and the external user who will receive the shared data, and sends the first transaction to the blockchain network. requesting transmission to the blockchain, verifying the first transaction using a node that generates at least one block corresponding to each of at least one transaction in which the electronic device participated in the agreement, and confirming the reliability of the first transaction. sending a first transaction onto the network, creating a first block corresponding to the first transaction, and verifying the second transaction based on receiving a second transaction from the blockchain network including a request to provide shared data; Based on confirming the reliability of the second transaction, the smart contract can be executed and a second block corresponding to the second transaction can be created.

According to one embodiment, the node may verify the second block and record it on the blockchain network based on the second block being verified.

According to one embodiment, the processor 240 may request to update the ledger of each node participating in the blockchain network using a communication circuit based on the completion of a transaction agreement between the external device and the blockchain network.

According to one embodiment, the processor 240 can use the ledger on the blockchain network to check whether a smart contract is executed and whether shared data of the electronic device is shared.

According to one embodiment, the electronic device and the external device are mobile nodes, and the processor can communicate with the external device through a relay node in the blockchain network.

According to one embodiment, the processor 240 may control the display to output a settings screen on which information about the shared data of the electronic device and the external user who will receive the shared data can be set.

According to one embodiment, the node executes the second transaction based on the match between the information about the external user who will be provided with the shared data in the second transaction and the information about the external user who will be provided with the shared data recorded on the smart contract. , a block containing information indicating that shared data has been transmitted to an external device can be created.

According to one embodiment, the node may verify the second transaction and execute the second transaction based on the reliability of the second transaction being verified.

The server may include a communication circuit 220, a memory 230 that stores the entire ledger or a partial ledger including a portion of the entire ledger, and a processor 240. The processor receives a first transaction containing a smart contract related to shared data and information about an external user to be provided with the shared data from a first node of a first external device, and a second node of a second external device Based on receiving a second transaction including a request for provision of shared data from , Shared data can be transmitted to a second external device based on the match between the information about the second external device and the external user who will receive the shared data on the smart contract.

According to one embodiment, the processor may record the first block corresponding to the first transaction on the blockchain network based on completion of verification of the first transaction from the first node.

According to one embodiment, the processor may record a second block corresponding to the second transaction on the blockchain network based on completion of verification of the second transaction from the first node.

According to one embodiment, the processor transmits shared data to a second external device based on completion of verification of the second transaction from the first node, and provides information indicating that the second external device has received the shared data. Can be transmitted on 1 node.

The data transmission management method of the electronic device 101 creates a first transaction using a smart contract containing information about the shared data of the electronic device 101 and an external user who will receive the shared data. An operation to request transmission of the first transaction to the blockchain network, an operation to verify the first transaction and transmit the first transaction to the blockchain network based on confirming the reliability of the first transaction. , generating a first block corresponding to the first transaction, verifying the second transaction based on receiving a second transaction including a request for provision of shared data from the blockchain network, and verifying the reliability of the second transaction. Based on this, the smart contract may be executed and a second block corresponding to the second transaction may be generated.

Claims (20)

In electronic devices,
communication circuit;
Memory that stores a partial ledger or full ledger, including a portion of the full ledger for a blockchain network; and
Includes a processor electrically connected to the communication circuit and the memory,
The ledger includes at least one block corresponding to each of at least one transaction in which the electronic device participated in an agreement,
The processor is
Creating a first transaction using a smart contract containing shared data of the electronic device and information about an external user who will receive the shared data,
requesting to transmit the first transaction to the blockchain network,
The electronic device verifies the first transaction using a node that generates at least one block corresponding to each of at least one transaction in which the electronic device participated in the agreement,
Based on confirming the reliability of the first transaction, transmitting the first transaction on the blockchain network and generating a first block corresponding to the first transaction,
Verifying the second transaction based on receiving a second transaction including a request to provide the shared data from the blockchain network,
An electronic device that executes the smart contract based on verifying the reliability of the second transaction and generates a second block corresponding to the second transaction. According to clause 1,
The node is
An electronic device that verifies the second block and records it on the blockchain network based on the second block being verified. According to clause 1,
The processor is
Based on the transaction agreement between the external device and the blockchain network being completed
An electronic device that requests to update the ledger of each node participating in the blockchain network using the communication circuit. According to clause 1,
The processor is
An electronic device that uses the ledger on the blockchain network to check whether the smart contract is executed and whether shared data of the electronic device is shared. According to clause 1,
The electronic device and external device are mobile nodes,
The processor is
An electronic device configured to communicate with the external device through a relay node in the blockchain network. According to clause 1,
The processor is
An electronic device that controls a display to output a settings screen for setting shared data of the electronic device and information about external users who will receive the shared data. According to clause 1,
The node is
Based on the fact that the information about the external user who will be provided with the shared data in the second transaction matches the information about the external user who will be provided with the shared data recorded on the smart contract
An electronic device that executes the second transaction and generates a block containing information indicating that the shared data has been transmitted to an external device. According to clause 1,
The node is
Verify the second transaction,
An electronic device that executes the second transaction based on verification of reliability of the second transaction. On the server,
communication circuit;
Memory that stores a partial ledger or full ledger containing a portion of the full ledger;
Includes a processor,
The processor is
Receiving a first transaction including a smart contract related to shared data and information about an external user who will receive the shared data from a first node of a first external device,
Information about an external user to be provided with the shared data on the smart contract based on receiving a second transaction including a request for provision of the shared data from a second node of a second external device and information about the second external device Request verification from the first node whether the information matches,
A server that transmits the shared data to the second external device based on matching information about the second external device and the external user who will receive the shared data on the smart contract. According to clause 9,
The processor is
A server that records a first block corresponding to the first transaction on a blockchain network based on completion of verification of the first transaction from the first node. According to clause 9,
The processor is
A server that records a second block corresponding to the second transaction on a blockchain network based on completion of verification of the second transaction from the first node. According to clause 9,
The processor is
Transmitting the shared data from the first node to the second external device based on completion of verification of the second transaction,
A server transmitting information indicating that the second external device has received the shared data to the first node. In a method for managing data transmission of an electronic device,
Generating a first transaction using a smart contract including shared data of the electronic device and information about an external user who will receive the shared data;
Requesting to transmit the first transaction to a blockchain network;
Verifying the first transaction and transmitting the first transaction onto the blockchain network based on confirming reliability of the first transaction;
generating a first block corresponding to the first transaction;
Verifying the second transaction based on receiving a second transaction including a request to provide the shared data from the blockchain network; And
Executing the smart contract based on verifying the reliability of the second transaction and generating a second block corresponding to the second transaction. According to clause 13,
The electronic device includes a node,
The node is
A method of verifying the second block and recording it on the blockchain network based on the second block being verified. According to clause 13,
Based on the transaction agreement between the external device and the blockchain network being completed
A method further comprising requesting to update the ledger of each node participating in the blockchain network using a communication circuit. According to clause 13,
The method further includes confirming whether the smart contract is executed using a ledger on the blockchain network and confirming whether shared data of the electronic device is shared. According to clause 13,
The electronic device and external device are mobile nodes,
A method further comprising setting up to communicate with the external device through a relay node in the blockchain network. According to clause 13,
The method further includes controlling the display to output a settings screen for setting shared data of the electronic device and information about an external user who will receive the shared data. According to clause 13,
The electronic device further includes a node,
The node is
Based on the fact that the information about the external user who will be provided with the shared data in the second transaction matches the information about the external user who will be provided with the shared data recorded on the smart contract
A method of executing the second transaction and generating a block containing information indicating that the shared data has been transmitted to an external device. According to clause 13,
The electronic device further includes a node,
The node is
Verify the second transaction,
A method of executing the second transaction based on verification of the reliability of the second transaction.

Images