KR20230155919A - Electronic apparatus and substitute agreement method for inactive nodes in the mobile blockchain network - Google Patents

Abstract

Electronic devices constituting a blockchain node included in a blockchain network according to various embodiments include a communication module, a memory for storing a partial ledger or the entire ledger including a portion of the entire ledger for the blockchain network, the communication module, and the Comprising at least one processor electrically connected to a memory, wherein the ledger includes at least one block corresponding to each of at least one transaction in which the electronic device participated in an agreement, and wherein the at least one processor operates the communication module. Establishing a proxy agreement relationship with the first external electronic device by communicating with the first external electronic device through the communication module, and providing a service between the first external electronic device and the second external electronic device through the communication module Receiving an agreement request for a first transaction for a first transaction for a service between the first external electronic device and the second external electronic device based on receiving a request to start a proxy agreement of the first external electronic device It may be set to perform an agreement operation on behalf of the first external electronic device and transmit the completed result of the proxy agreement to the second external electronic device through the communication module.

Description

{ELECTRONIC APPARATUS AND SUBSTITUTE AGREEMENT METHOD FOR INACTIVE NODES IN THE MOBILE BLOCKCHAIN NETWORK}

Various embodiments relate to proxy agreement methods and devices for inactive nodes in a mobile blockchain network.

A blockchain network may refer to a network in which decisions are made according to the consensus algorithm of nodes participating in the blockchain network. Nodes participating in a blockchain network must participate in consensus operations for transactions performed in the blockchain network.

Nodes participating in a blockchain network may consist of electronic devices (e.g., mobile devices). However, mobile devices such as smartphones may be affected by power status due to their nature. For example, a mobile device enters a deactivated (e.g. idle/sleep) mode to save power, which restricts program operation, or enters a low-voltage or power-off state, or reduces connectivity to the blockchain network due to poor wireless network connectivity. This may break. Additionally, mobile devices may have very limited storage space.

Accordingly, the network for mobile blockchain (or mobile blockchain network) can be configured to have relay nodes (e.g. server nodes) that can always operate and wake up inactive mobile nodes to connect and participate in the blockchain network. . In addition, storage issues in blockchain networks can be resolved by storing only some ledgers (e.g., partial ledgers) in the storage of mobile nodes and all ledgers (e.g., full ledgers) in some mobile nodes.

Mobile blockchain networks can provide users with a variety of blockchain-based services due to the advantage of ensuring the integrity and reliability of information. In particular, a mobile blockchain network allows the user/user's mobile device to participate in the blockchain as a mobile node.

For example, services that provide transaction contracts for personal assets or announcements that require counterparty confirmation (e.g., NFT, real estate, financial services) can be provided through mobile blockchain. When mobile devices owned by specific users are used as participating nodes in a blockchain, reliability of content or actions can be increased by allowing users to directly agree to or notify transactions through fingerprint recognition, pattern recognition, or password entry.

However, when an arbitrary mobile node needs to reach an agreement with another mobile node that is the subject of an agreement, such as a smart contract, the other mobile node may enter an inactive state, making it difficult to participate in the blockchain network. At this time, the mobile node requesting consensus does not receive consensus completion from other mobile nodes, so the service cannot proceed any further, and transactions for smart contracts are processed in error or discarded. As a result, an unnecessary situation arises in which any mobile node has to re-request agreement with another mobile mode.

Various embodiments propose a method for continuously forming a chain by enabling consensus even when mobile nodes participating in agreement on transactions on a mobile blockchain network are in an inactive state.

Electronic devices constituting a blockchain node included in a blockchain network according to various embodiments include a communication module, a memory for storing a partial ledger or the entire ledger including a portion of the entire ledger for the blockchain network, the communication module, and the Comprising at least one processor electrically connected to a memory, wherein the ledger includes at least one block corresponding to each of at least one transaction in which the electronic device participated in an agreement, and wherein the at least one processor operates the communication module. Establishing a proxy agreement relationship with the first external electronic device by communicating with the first external electronic device through the communication module, and providing a service between the first external electronic device and the second external electronic device through the communication module Receiving an agreement request for a first transaction for a first transaction for a service between the first external electronic device and the second external electronic device based on receiving a request to start a proxy agreement of the first external electronic device It may be set to perform an agreement operation on behalf of the first external electronic device and transmit the completed result of the proxy agreement to the second external electronic device through the communication module.

A proxy agreement method for an inactive node in a blockchain network according to various embodiments includes the operation of establishing a proxy agreement relationship with a first external electronic device among mobile nodes participating in the blockchain network, and mobile nodes participating in the blockchain network. An operation of receiving an agreement request for a first transaction for a service between the first external electronic device and the second external electronic device from a second external electronic device, upon receiving a request to start a proxy agreement from the first external electronic device. Based on this, an operation of performing an agreement operation on behalf of the first external electronic device for a first transaction for a service between the first external electronic device and the second external electronic device, and sending the agreed upon completion result to the blockchain In response to the operation of transmitting to the second external electronic device through the network and the completion of the first transaction agreement between the first external electronic device and the second external electronic device, the ledger of each node participating in the blockchain network is updated. The ledger may include at least one block corresponding to each of at least one transaction in which the electronic device participates in an agreement.

According to various embodiments, when service agreement between nodes is required in a mobile blockchain network, if the second node participating in the agreement at the request of the first node is in a network unavailable state, another third node with delegated agreement authority By reaching a proxy agreement with the first node, blockchain network services can continue to proceed smoothly without blocking.

1 is a block diagram of an electronic device in a network environment according to various embodiments.
Figure 2 is a diagram for explaining a blockchain platform of an electronic device according to an embodiment.
Figure 3 is a diagram for explaining a mobile blockchain system according to an embodiment.
Figure 4 illustrates a method of establishing proxy agreement for electronic devices in a mobile blockchain network according to an embodiment.
Figure 5 illustrates a proxy agreement method between electronic devices in a mobile blockchain network according to an embodiment.
Figures 6a and 6b illustrate a method of changing the proxy agreement path between electronic devices in a mobile blockchain network according to an embodiment.
Figure 7 illustrates a method for stopping proxy agreement between electronic devices in a mobile blockchain network according to an embodiment.
Figure 8 illustrates a method of deleting proxy agreement settings between electronic devices in a mobile blockchain network according to an embodiment.
9A and 9B illustrate a proxy agreement method between a plurality of electronic devices in a mobile blockchain network according to an embodiment.
Figures 10a and 10b illustrate a proxy agreement method between a plurality of electronic devices in a mobile blockchain network according to an embodiment.
Figure 11 illustrates a proxy agreement method for electronic devices in a mobile blockchain network according to an embodiment.

The electronic device 101 according to various embodiments disclosed in this document may be of various types. The electronic device 101 may include, for example, a portable communication device (eg, a smartphone), a computer device, a portable multimedia device, a portable medical device, a camera, a wearable device, or a home appliance device. The electronic device 101 according to an embodiment of this document is not limited to the devices described above.

FIG. 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, 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 the 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, coprocessor 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 device) 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, where artificial intelligence 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 A 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 various embodiments, 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.

The electronic device 101 according to various embodiments may include a blockchain platform corresponding to at least one blockchain application or blockchain module that performs blockchain-related operations.

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 modes to store the same data block for security purposes.

According to one embodiment, the electronic device 101 stores blocks related to nodes and ledgers related to blocks partially (e.g., partial ledger) among the distributed ledgers for the blockchain network, or stores the distributed ledger for the blockchain network. The entirety (or entire ledger) can be stored. 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.

Figure 2 is a diagram for explaining a blockchain platform of an electronic device according to an embodiment.

Referring to FIG. 2, the electronic device 101 according to one embodiment may include a blockchain platform 200.

According to one embodiment, the blockchain platform 200 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.

According to one embodiment, the blockchain platform 200 includes a smart contract 210, a distributed ledger 220, a blockchain processor 230, a transaction consensus module 240, and a blockchain network management module 250. ) may include. According to various embodiments, the blockchain platform 200 may further include various components or some components may be omitted to perform operations related to the blockchain.

The blockchain processor 230 may be included in a processor (eg, processor 120 of FIG. 1). The blockchain processor 230 can control the operations of components included in the blockchain platform 200. For example, blockchain processor 230 may perform execution of transactions, including synchronizing ledgers, signing transactions, and/or performing transaction records on a blockchain network.

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

According to one embodiment, the distributed ledger 220 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 220 may include a partial ledger containing blocks and data for transactions involving electronic device 101 among the overall ledger storing blocks and data associated with all transactions in the blockchain network. there is.

According to another embodiment, distributed ledger 220 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 220 may include at least one block 221 and a state database (data base) 222 generated through a blockchain network. Block 221 may be composed of transactions containing information for performing the smart contract 210. In one embodiment, blocks of the distributed ledger 220 are in the form of a blockchain and may include block data. For example, block 221 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 221 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 221 constituting the blockchain (221) can 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 222 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 222 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 222 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 222 to confirm final values resulting from transaction execution within the blockchain network. State data stored in the state database 222 may have characteristics such as global variables within the blockchain network.

According to one embodiment, the state database 222 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 transaction consensus module 240 may control operations for the electronic device 101 to perform a transaction consensus procedure in a blockchain network. For example, the transaction consensus module 240 may perform an operation to process transaction consensus based on the consensus algorithm used in the blockchain network. The transaction consensus module 240 can support various consensus algorithms used in typical blockchains. For example, the transaction consensus module 240 may be used to connect nodes included in the blockchain network (e.g., based on proof of work (POW), proof of state (POS), practical byzantine fault tolerance (PBFT), and/or RAFT). : Transaction agreement can be performed with mobile nodes).

According to one embodiment, the blockchain network management module 250 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 network management module 250 can form a blockchain network and perform operations related to other nodes (external electronic devices) included in the blockchain network.

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

Referring to FIG. 3, 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) can switch to an active state (e.g., running state) in response to receiving a wake-up signal from the relay node 304 and participate in blockchain network services by connecting to the blockchain network. there is. The mobile node (eg, 301, 302 or 303) may transmit a response signal to the relay node 304 in response to the wake-up signal. When a response signal is received from a mobile node (e.g., 301, 302 or 303) participating in a transaction, the relay node 304 can relay the transaction 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.

According to one embodiment, in a mobile blockchain network, at least some of the mobile nodes (e.g., 303) may store (or own) the entire ledger of the distributed ledger of the blockchain network. The mobile node (e.g., 303) or relay node 304 that stores the entire ledger may be a node that receives consensus authority from another mobile node and performs proxy consensus operations.

According to one embodiment, among mobile nodes participating in a blockchain network, a mobile node (e.g., 301 or 302) that stores a partial ledger requests that another mobile node (e.g., 303) perform a proxy agreement on the transaction agreement (e.g., 303). Alternatively, a transaction may be executed based on the proxy agreement agreement.

For example, the first node 301 may establish a proxy agreement relationship with the third node 303. The first node 301 requests the third node 303 to make a proxy agreement on behalf of the first node 301 for a transaction related to the first node 301, and the third node 303 participates in the proxy agreement. We can agree on this. The relay node 304 may store setting information (e.g., proxy agreement information table, agreement path change table) about the proxy agreement relationship between the first node 301 and the third node 303.

According to one embodiment, among mobile nodes participating in a blockchain network, a mobile node (e.g., 303) that stores the entire ledger performs a proxy agreement operation (or procedure) on behalf of other mobile nodes for transactions related to other mobile nodes. It can be done.

For example, the second node 302 may execute a smart contract transaction with the first node 301 and request agreement from the first node 301. The relay node 304 may confirm the proxy agreement relationship between the first node 301 and the third node 303 and request the third node 303 to perform a transaction agreement operation of the second node 302.

The third node 303 makes a proxy agreement on behalf of the first node 301 for the transaction agreement requested from the second node 302 to the first node 301, and sends the proxy agreement result to the relay node 304. It can be transmitted to the second node 302 through.

According to various embodiments, among mobile nodes participating in a blockchain network, a mobile node (e.g., 301 or 302) that stores a partial ledger may establish a proxy agreement relationship with other mobile nodes, request to start a proxy agreement, request to stop a proxy agreement, or An agreement can be reached with another mobile node (e.g. 303) by executing a transaction related to a request to delete proxy agreement information.

In some embodiments, the relay node 304 and the third node 303 may be integrated, and the relay node 304 may perform the role of the third node 303.

An electronic device constituting a blockchain node included in a blockchain network according to various embodiments (e.g., the electronic device 101 in FIG. 1, the third node 303 in FIG. 3) uses a communication module (e.g., the electronic device 101 in FIG. 1). Communication module 190), a memory that stores a partial ledger or the entire ledger including part of the entire ledger for the blockchain network (e.g., memory 130 in FIG. 1), electrically connected to the communication module and the memory It includes at least one processor (e.g., the processor 120 of FIG. 1 and the blockchain processor 230 of FIG. 2), and the ledger has at least one transaction corresponding to each of at least one transaction in which the electronic device participated in the agreement. and a block, wherein the at least one processor communicates with a first external electronic device (e.g., the first node 301 of FIG. 3) through the communication module to establish a proxy agreement relationship with the first external electronic device. Setting, and requesting agreement on a first transaction for a service between the first external electronic device and the second external electronic device through the communication module from a second external electronic device (e.g., the second node 302 in FIG. 3) Receives, and sends the first external electronic device to the first external electronic device for a first transaction for a service between the first external electronic device and the second external electronic device based on the proxy agreement start request of the first external electronic device being received. It may be set to perform an agreement operation on behalf of the user and transmit the completed result of the proxy agreement to the second external electronic device through the communication module.

According to various embodiments, the at least one processor is configured to update the ledger of each node participating in the blockchain network in response to completion of the first transaction agreement between the first external electronic device and the second external electronic device. A request can be made through the communication module.

According to various embodiments, the at least one processor may be further configured to transmit the proxy agreement completed block data to the first external electronic device when a request to stop proxy agreement is received from the first external electronic device. .

According to various embodiments, the first external electronic device and the second external electronic device are mobile nodes, and the at least one processor is connected to the first external electronic device and the second external electronic device through a relay node in the blockchain network. It can be set to communicate with an external electronic device.

According to various embodiments, when establishing a proxy agreement relationship with the first external electronic device, the at least one processor includes a node item requesting proxy agreement and an item checking whether a proxy agreement is possible on behalf of the requesting node. It may be further configured to store and manage the proxy agreement information table.

According to various embodiments, the at least one processor is configured to respond to the first transaction based on a proxy agreement possible state in relation to the first external electronic device being recorded as on in the proxy agreement information table. It may be further configured to perform a consensus operation on behalf of the first external electronic device.

According to various embodiments, the at least one processor records the proxy agreement possible state with respect to the first external electronic device as off in the proxy agreement information table, If a proxy agreement start request is not received, a proxy agreement information change request is received from the relay node, and a proxy agreement possible state is established with respect to the first external electronic device based on the proxy agreement information change received from the relay node. It may be further set to update to on.

According to various embodiments, the at least one processor may be set to record proxy agreement relationship establishment information, proxy agreement operation information, or proxy agreement suspension information with the first external electronic device in the ledger within the blockchain network. .

According to various embodiments, the at least one processor may be set to record information about deletion of the proxy agreement relationship in the ledger within the blockchain network when a request to delete the proxy agreement relationship setting is received from the first external electronic device. You can.

Below, we will explain various cases related to proxy agreement operations within a blockchain network. The electronic device 101 according to various embodiments may be set to automatically perform proxy agreement operations depending on the implementation of a smart contract requiring service agreement, and may use pattern recognition and/or biometric information recognition ( You can also set up additional user authentication, such as fingerprint recognition.

Figure 4 illustrates a method of establishing proxy agreement for electronic devices in a mobile blockchain network according to an embodiment.

Referring to FIG. 4, the electronic device 101 according to various embodiments is a mobile node participating in a blockchain network, and in order to prevent non-participation in the blockchain according to changes in the state of the electronic device, other nodes participating in the blockchain network ( A proxy agreement relationship with another mobile node or relay node) can be established in advance.

In the embodiment of FIG. 4, the first node (e.g., 301 in FIG. 3) is the proxy agreement setter (or agreeer), and the third node (e.g., 303 in FIG. 3) acts on behalf of the first node (301). It may be a proxy agreeer participating in transaction agreement. For example, the first node 301 may be any mobile node that owns a partial ledger in a blockchain network.

In operation 410, the first node 301 executes a smart contract transaction in which the third node 303 requests the establishment of a proxy agreement on behalf of the first node 301, and transmits the agreement on the establishment of the proxy agreement to the relay node 304. ) can be requested. For example, the first node 301 may transmit proxy agreement relationship establishment request information as transaction data (eg, data 1). The proxy agreement relationship setting information may include request relationship information between nodes (e.g., node 1 -> node 3) and agreement target information (e.g., node 1, which is the proxy agreement requester, and node 3, which is the proxy agreeer).

In operation 415, the relay node 304 may transmit transaction data (eg, data 1) requesting establishment of a proxy agreement relationship of the first node 301 to the third node 303. In operation 420, the third node 303 may agree to establish a proxy agreement relationship and transmit the agreed upon completion information to the relay node 304.

In operation 425, the relay node 304 may transmit completion information agreed upon in establishing the proxy agreement relationship of the third node 303 to the first node 301.

In operation 430, each node (e.g., the first node 301, the relay node 304, and the third node 303) receives transaction data regarding the establishment of a proxy agreement between the first node 301 and the third node 303. (e.g. data 1) can be recorded in the distributed ledger of each node.

According to some embodiments, the relay node 304 may only perform the role of delivering proxy agreement setting information between nodes to each node without storing the distributed ledger of each node. In operation 440, the third node 303 may update the proxy agreement information table based on the proxy agreement relationship establishment agreement.

According to one embodiment, a random node (e.g., the third node 303) performing the proxy agreement role acts as a proxy based on proxy agreement relationship setting information requested from at least one other mobile node within the blockchain network. It can be configured and managed as a consensus information table. For example, the proxy agreement information table may include a request node item requesting a proxy agreement and an item checking whether a proxy agreement is possible. The item that checks whether a proxy agreement is possible is turned on when a proxy agreement start request or an inactive mode entry signal is received from the mobile node that requested the proxy agreement (e.g., the first node 301). ), and when a proxy agreement stop request or active mode entry information is received from the mobile node that requested the proxy agreement (e.g., the first node 301), the proxy agreement possible status item may be recorded as off. there is.

For example, when requesting consensus on a transaction related to the request node, the third node 303 may perform a transaction consensus operation on behalf of the request node if the request node's proxy agreement possible item is recorded as on. there is.

Figure 5 illustrates a proxy agreement method between electronic devices in a mobile blockchain network according to an embodiment.

Referring to FIG. 5, the electronic device 101 according to various embodiments may request the start of a proxy agreement from another node (eg, another mobile node or relay node) participating in the blockchain network.

In operation 510, the first node 301 may detect whether the electronic device 101 enters a network inactive mode (or power saving state). For example, the first node 301 monitors whether the remaining battery capacity of the electronic device 101 falls below a set reference value or whether a wireless communication signal (e.g., received signal strength indicator (RSSI)) is received at a strength below the reference value. You can monitor whether it enters an inactive mode where network communication is not possible.

In operation 515, before the electronic device 101 enters the network inactive mode, the first node 301 executes a smart contract requesting the start of a proxy agreement with the blockchain network to reach an agreement on the start of the proxy agreement with the relay node 304. ) can be requested. For example, the first node 301 may transmit transaction data (eg, data 2) to the relay node 304 to initiate a proxy agreement from the third node 303 with which a prior proxy agreement relationship has been established.

In operation 520, the relay node 304 may transmit the first transaction data (e.g., data 2) requesting the start of proxy agreement of the first node 301 to the third node 303, which is a proxy agreeer.

In operation 530, the third node 303 may record information about the start of the proxy agreement (e.g., data 2) on behalf of the first node 301 in the full ledger or the partial ledger associated with the first node 301. there is.

For example, the third node 303 does not transmit a response signal to the first node 301 in response to the first transaction data (e.g., data 2) transmitted from the first node 301, but transmits the entire ledger or First transaction data (eg, data 2) may be recorded in the partial ledger related to the first node 301.

In operation 535, the third node 303 may update the proxy agreement information table in response to the proxy agreement start request.

For example, when the first node 301 is a requesting node with a prior proxy agreement relationship, the third node 303 is an item that checks the proxy agreement availability status related to the first node 301 in the proxy agreement information table. can be updated from off to on.

In operation 540, the third node 303 may transmit an agreement path change request message to the relay node 304 on behalf of the first node 301, informing that the state has changed to a state where proxy agreement is possible.

At operation 545, relay node 304 may update the consensus reroute table. For example, the consensus path change table may include a node entry before the proxy consensus path change (e.g., the first node) and a node entry after the proxy consensus path change (e.g., the third node).

According to one embodiment, the relay node 304 may create and manage a consensus route change table related to at least one mobile node participating in the blockchain network. The relay node 304 may update the consensus path change table to change the consensus target related to the first node 301 to the third node 303 rather than the first node 301 based on the consensus path change request message. there is.

In operation 550, the second node 302 may execute a smart contract transaction requiring service agreement with the first node 301 and request service agreement from the relay node 304. For example, the second node 302 may transmit transaction data (eg, data 3) requesting service agreement with the first node 301 to the relay node 304. At this time, the second node 302 may specify whether a proxy agreement is possible regarding transaction agreement by considering service characteristics or service policy.

Transaction data requesting service agreement (e.g., data 3) may include service information requiring agreement, information on parties to agreement (e.g., first node and second node), and information on whether proxy agreement is possible.

In operation 555, the relay node 304 may check whether proxy agreement is possible and the agreement path based on transaction data (e.g., data 3) transmitted from the second node 302.

For example, if proxy agreement is possible for a transaction through transaction data (e.g., data 3), the relay node 304 checks whether the first node 301 is included in the consensus path change table, and determines whether the first node 301 is included in the first node 301. It can be seen that the path of node 301 has changed to the third node 303.

In operation 560, the relay node 304 may transmit transaction data (eg, data 3) requesting service agreement with the first node 301 to the third node 303.

In operation 565, the third node 303 makes a proxy agreement on the service with the first node 301 and the second node 302 on behalf of the second node 302, and sends the agreed completion information to the relay node 304. ) can be transmitted. For example, proxy agreement completion information may include, but is not limited to, agreement information on transaction data, and may additionally include or include information that the third node 303 reached an agreement on behalf of the first node 301. You may not.

In operation 570, the relay node 304 may transmit the service agreement completion information between the first node 301 and the second node 302 delivered from the third node 303 to the second node 302.

In operation 580, the second node 302, the relay node 304, and the third node 303 record the results of transaction agreements for services with the first node 301 and the second node 302 in each distributed ledger. Or you can update it.

Although not shown in the drawing, if the first node 301 returns to a state where it can participate in the blockchain network, the third node 303 sends the results or data of proxy agreement to the first node 301 to the first node. It can be delivered to (301). The first node 301 may record the proxy agreement result or data received from the third node 303 in the distributed ledger of the first node 301.

Figures 6a and 6b illustrate a method of changing the proxy agreement path between electronic devices in a mobile blockchain network according to an embodiment.

Referring to FIGS. 6A and 6B, the electronic device 101 (e.g., relay node) according to one embodiment may initiate a preliminary proxy agreement with the mobile node participating in the blockchain network without requesting start of proxy agreement, if communication is not achieved. The proxy agreement path can be arbitrarily changed based on setting information.

The first node 301 and the third node 303 may proceed with the procedure shown in FIG. 4 to complete pre-establishment of the proxy agreement relationship.

For example, in a situation where the proxy agreement relationship has been pre-established, the first node 301 makes a proxy agreement on the blockchain network before the electronic device 101 enters the network deactivation mode, as shown in operation 610. You may not be able to request startup. For example, the electronic device 101 may be turned off or network connection may be lost due to an unexpected situation.

At this time, as shown in operation 615, the third node 303 is in a state where proxy agreement is possible for the first node 301 in the proxy agreement information table through a pre-established proxy agreement relationship with the first node 301. The item checked may be recorded as off.

Independently, within the blockchain network, the second node 302 may execute a smart contract transaction requiring service agreement with the first node 301 and request service agreement from the relay node 304 in operation 620. For example, the second node 302 may transmit transaction data (eg, data 3) requesting service agreement with the first node 301 to the relay node 304. Transaction data requesting service agreement (e.g., data 3) may include service information requiring agreement, information on parties to agreement (e.g., first node and second node), and information on whether proxy agreement is possible.

In operation 630, the relay node 304 provides information about the second transaction to the first node 301 based on the agreement target included in the transaction data (e.g., data 3) requesting service agreement with the first node 301. A consensus request can be sent. In this case, the first node 301 enters an inactive mode and is disconnected from the network, so it may not receive a consensus request from the relay node 304.

In operation 635, when the relay node 304 does not receive a response signal to the service agreement request from the first node 301 and a set time elapses (e.g., time out), the relay node 301 repeats N times ), you can attempt to request a service agreement.

In operation 640, if the relay node 304 attempts to request agreement with the first node 301 N times but fails to receive a response, it is possible to determine whether proxy agreement is possible and change the agreement path based on transaction data requesting service agreement. can confirm.

For example, the relay node 304 may check information about the third node 303 with which a proxy agreement relationship is established with the first node 301. If proxy agreement is possible for the service agreement, the relay node 304 can forcibly change the agreement path to the third node 303, which is the proxy agreement of the first node 301, based on the proxy agreement information table.

In operation 650, the relay node 304 may transmit a message requesting a change to the proxy agreement information of the first node 301 to the third node 303.

In operation 655, the third node 303 may update the proxy agreement information table based on the proxy agreement information change request message. For example, the third node 303 may update the item that checks the possibility of proxy agreement for the first node 301 from off to on in the proxy agreement information table.

In operation 660, the third node 303 may record information about the start of the proxy agreement on behalf of the first node 301 in the entire ledger or a partial ledger related to the first node 301.

In operation 670, the third node 303 may transmit a request message to change the proxy agreement path to the relay node 304.

In operation 675, based on the consensus path change request message, the relay node 304 updates the consensus path change table so that the third node 303 makes a proxy agreement on behalf of the first node 301 according to the service agreement request. You can.

In operation 680, the relay node 304 may transmit transaction data (eg, data 3) requesting service agreement from the first node 301 to the third node 303.

In operation 685, the third node 303 makes a proxy agreement on behalf of the first node 301 for the service with the first node 301 and the second node 302, and sends the agreed completion information to the relay node 304. ) can be transmitted.

In operation 690, the relay node 304 may transmit the result of completion of the proxy agreement for the second transaction to the second node 302. In operation 695, the first node 301, the relay node 304, and the third node 303 record the results of transaction agreements for services with the first node 301 and the second node 302 in each distributed ledger. Or you can update it.

According to some embodiments, if the relay node 304 does not store the distributed ledger of each node and only serves to transmit data between each node, it may not store the result of the transaction agreement.

Figure 7 illustrates a method for stopping proxy agreement between electronic devices in a mobile blockchain network according to an embodiment.

Referring to FIG. 7, the electronic device 101 according to one embodiment may request the suspension of proxy agreement with another node (eg, another mobile node or relay node) participating in the blockchain network.

The relay node 304 and the third node 303 proceed with the procedure shown in FIG. 5 or 6 to change the proxy agreement path, and the third node 303 acts as a proxy on behalf of the first node 301. The state may be set to enable agreement. In this case, the first node 301 may be in a non-networkable state.

For example, in the third node 303, a proxy agreement possible state (e.g., on) is recorded for the first node 301 in the proxy agreement information table, and in the relay node 304, the first node 301 is recorded in the proxy agreement information table. The consensus path for node 301 may have been changed and recorded to a third node.

In operation 710, when a transaction agreement request related to the first node 301 is received within the blockchain network, the relay node 304 performs proxy agreement on the third node 303 on behalf of the first node 301. Transaction data can be transmitted to the third node 303 to do so.

In operation 720, the first node 301 may detect a change from the network inactive state to the network active state. For example, it can be monitored whether the electronic device 101 wakes up from sleep mode to active mode, the remaining battery capacity of the electronic device 101 enters a range above a set reference value, or whether a wireless communication signal is received at a strength above the reference value. .

In operation 730, the first node 301 executes a smart contract transaction to stop the proxy agreement, based on the change to the network active state, and sends transaction data (e.g., data 4) requesting the stop of the proxy agreement to the relay node ( 304). The target node for suspending the proxy agreement may be the third node 303.

In operation 735, the relay node 304 may transmit transaction data (eg, data 4) requesting suspension of the proxy agreement to the third node 303.

In operation 740, the third node 303 may record information about the suspension of the proxy agreement in the entire ledger or a partial ledger related to the first node 301. In operation 745, the third node 303 may update the proxy agreement information table according to the request to stop proxy agreement. For example, the third node 303 may update the proxy agreement availability status of the first node 301 from on to off.

In operation 750, the third node 303 may transmit a request message to delete the consensus change path of the first node to the relay node 304.

In operation 755, the relay node 304 may update the consensus route change table to delete the route change record of the first node 301.

In operation 760, the third node 303 may agree on a request to stop proxy agreement for the first node 301 and transmit agreement completion information to the relay node 304.

In operation 765, the relay node 304 may transmit the result of agreement completion for suspending the proxy agreement to the first node 301.

In operation 770, the first node 301 may request the relay node 304 for the result or data of the third node's proxy agreement while the network is inactive.

In operation 775, the relay node 304 requests data or blocks agreed upon on behalf of the first node 301 by the third node 303, which is a proxy agreeer, and in operation 780, the third node 303 makes a proxy agreement. A block (or data) for the result may be transmitted to the first node 301.

Figure 8 illustrates a method of deleting proxy agreement settings between electronic devices in a mobile blockchain network according to an embodiment.

Referring to FIG. 8, the electronic device 101 according to one embodiment may request deletion of proxy agreement setting information set in the blockchain network.

The relay node 304 and the third node 303 proceed with the procedure shown in FIG. 7 to complete the setting of stopping the proxy agreement between nodes, and the third node 303 selects the first node 301 in the proxy agreement information table. ) may be recorded as a state in which proxy agreement is possible (e.g., off).

In operation 810, the first node 301 executes a smart contract transaction to delete the setting information of the proxy agreement related to the first node 301 and sends transaction data (e.g., data 5) requesting deletion of the proxy agreement information. It can be transmitted to the relay node 304. The target node for deletion of proxy agreement information may be the third node 303.

In operation 815, the relay node 304 may transmit transaction data (eg, data 5) requesting deletion of proxy agreement information to the third node 303.

In operation 820, the third node 303 may delete the record for the first node 301 in the proxy agreement information table according to the request for deletion of the proxy agreement settings of the first node 301.

In operation 830, the third node 303 may agree on the deletion request for the proxy agreement setting of the first node 301 and transmit the agreed-upon completion information to the relay node 304. In operation 835, the relay node 304 may transmit the result of the agreement on the request to delete the proxy agreement settings to the first node 301.

In operation 840, the third node 303 and the first node 301 may record information about deletion of the proxy agreement settings of the first node 301 in each distributed ledger.

9A and 9B illustrate a proxy agreement method between a plurality of electronic devices in a mobile blockchain network according to an embodiment.

Referring to FIGS. 9A and 9B, an electronic device 101 (e.g., relay node) according to various embodiments has a proxy agreement relationship with a plurality of nodes (e.g., owning a partial ledger) participating in a blockchain network. You can configure a list of proxy agreement candidates by setting this.

In one embodiment, the first node 301 may execute a smart contract transaction requesting a proxy agreement preset from the fourth node 305, the fifth node 306, and the sixth node 307, respectively.

In operation 910, the first node 301 executes a smart contract transaction requesting the establishment of a proxy agreement with the fourth node 305, which owns a partial ledger among mobile nodes participating in the blockchain network, to reach an agreement on the establishment of the proxy agreement. can be requested from the relay node 304. For example, the first node 301 may transmit proxy agreement relationship establishment request information as transaction data (eg, data 1-1). The proxy agreement relationship setting information may include request relationship information between nodes (e.g., node 1 -> node 4) and agreement target information (e.g., node 1, which is the proxy agreement requester, and node 4, which is the proxy agreeer).

In operation 915, the relay node 304 may transmit transaction data (eg, data 1-1) requesting establishment of a proxy agreement relationship of the first node 301 to the fourth node 305.

In operation 920, the fourth node 305 may agree to establish a proxy agreement relationship and record a proxy agreement information table based on the proxy agreement relationship setting. The fourth node 305 records the item checking the possible status of proxy agreement for the first node 301 as off, and then, when a request to start proxy agreement is received, the item checking the possible status of proxy agreement can be recorded as on. When the proxy agreement possible state for the first node 301 is on, the fourth node 305 performs a consensus operation (or procedure) can be performed.

In operation 925, the fourth node 305 may transmit completed information agreed to establish the proxy agreement relationship to the relay node 304.

In operation 930, the relay node 304 may transmit completion information agreed upon in establishing the proxy agreement relationship of the fourth node 305 to the first node 301.

In operation 935, each node (e.g., the first node 301, the relay node 304, and the fourth node 305) executes a transaction related to establishing a proxy agreement between the first node 301 and the fourth node 305. Data (e.g. data 1-1) can be recorded in the distributed ledger of each node.

According to some embodiments, when the relay node 304 does not store the distributed ledger of each node and only serves to transmit data between each node, the transaction agreement result (e.g., transaction data (e.g., data 1-1 )) may not be saved.

In operation 940, the first node 301 executes a smart contract transaction requesting the establishment of a proxy agreement with the fifth node 306, which owns the partial ledger among the mobile nodes, to reach an agreement on the establishment of the proxy agreement with the relay node 304. It can be passed on. For example, the first node 301 transmits proxy agreement relationship establishment request information including request relationship information between nodes (e.g., node 1 -> node 5) and agreement target information (e.g., node 1, node 5) into a transaction. It can be passed as data (e.g. data 1-2).

In operation 945, the relay node 304 may transmit transaction data (eg, data 1-2) requesting establishment of a proxy agreement relationship with the fifth node 306 to the fifth node 306.

In operation 950, the fifth node 306 may agree to establish a proxy agreement relationship and record a proxy agreement information table based on the proxy agreement relationship setting. The fifth node 306 records the item checking the possible status of proxy agreement for the first node 301 as off, and then, when a request to start proxy agreement is received, the item checking the possible status of proxy agreement can be recorded as on.

In operation 955, the fifth node 306 may transmit completed information agreed upon in establishing the proxy agreement relationship to the relay node 304.

In operation 960, the relay node 304 may transmit completion information agreed upon in establishing the proxy agreement relationship of the fifth node 306 to the first node 301.

In operation 965, each node (e.g., the first node 301, the relay node 304, and the fifth node 306) performs a transaction regarding establishment of a proxy agreement between the first node 301 and the fifth node 306. Data (e.g. data 1-2) can be recorded in the distributed ledger of each node.

In operation 970, the first node 301 executes a smart contract transaction requesting the establishment of a proxy agreement with the sixth node 307, which owns the partial ledger among the mobile nodes, to reach an agreement on the establishment of the proxy agreement with the relay node 304. You can request it with . For example, the first node 301 transmits proxy agreement relationship establishment request information including request relationship information between nodes (e.g., node 1 -> node 6) and agreement target information (e.g., node 1, node 6) into a transaction. It can be passed as data (e.g. data 1-3).

In operation 975, the relay node 304 may transmit transaction data (eg, data 1-3) requesting establishment of a proxy agreement relationship with the sixth node 307 to the sixth node 307. However, if the sixth node 307 is in a network inactive state and does not receive a request to establish a proxy agreement relationship, the first node 301 may not receive the agreement completion result for the proxy agreement relationship from the sixth node 307. You can.

The first node 301 constructs a list of proxy agreement candidates (e.g., the fourth node and the fifth node) based on the nodes that have received the agreement completion result for the proxy agreement relationship, and sends the list of proxy agreement candidates to the relay node 304. ) and third nodes (e.g. mobile nodes that own the entire ledger).

In one embodiment, the list of proxy agreement candidates may be constructed based on the time of agreement history and/or the number of times of agreement history. For example, the list can be constructed by giving the mobile node with the consensus input at least once and the most recent consensus time as the highest priority among the proxy agreement candidates.

In another embodiment, the proxy agreement candidate list may be constructed by user input.

In one embodiment, the list of proxy agreement candidates may be updated at regular intervals. The electronic device 101 may review the proxy agreement candidates at regular intervals and delete candidates that have elapsed a certain validity time. In one embodiment, when all candidates in the proxy agreement candidate list are deleted, a candidate node can be added to the proxy agreement candidate list through user settings.

Figures 10a and 10b illustrate a proxy agreement method between a plurality of electronic devices in a mobile blockchain network according to an embodiment.

Referring to FIGS. 10A and 10B, the electronic device 101 (e.g., relay node 304) according to various embodiments may sequentially request proxy agreement based on a proxy agreement candidate list.

For example, the first node 301 has a pre-established proxy agreement relationship with the fourth node 305 and the fifth node 306, and the fourth node 305 and the fifth node 306 ) may not have received a request to start a proxy agreement from the first node 301, and the proxy agreement possible state for the first node 301 may be recorded as off.

As shown in operation 1010, the first node 301 may not request the start of proxy agreement with the blockchain network before the electronic device 101 enters the network deactivation mode.

Independently, within the blockchain network, the second node 302 may execute a smart contract transaction requiring service agreement with the first node 301 in operation 1020 and request service agreement from the relay node 304. For example, the second node 302 may transmit transaction data (eg, data 3) requesting service agreement with the first node 301 to the relay node 304.

In operation 1025, the relay node 303 requests agreement on a transaction with the first node 301 based on the agreement target included in the transaction data (e.g., data 3) requesting service agreement with the first node 301. can be transmitted. In this case, the first node 301 enters an inactive mode and is disconnected from the network, so it may not receive a consensus request from the relay node 304.

In operation 1030, when a set time elapses (e.g., time out) without receiving a response signal to the service agreement request from the first node 301, the relay node 304 repeatedly connects the first node 301 N times. ), you can attempt to request a service agreement.

In operation 1035, if the relay node 304 attempts to request consensus with the first node 301 N times but fails, it can confirm whether proxy agreement is possible and whether the agreement path can be changed based on the transaction data requesting service agreement. there is.

In operation 1040, the relay node 304 may transmit a message requesting a list of proxy agreement candidates to the third node 303, which owns the entire ledger, among mobile nodes. The third node 303 may have stored a list of proxy agreement candidates for the first node 301 through the operations shown in FIG. 9 .

In operation 1045, the third node 303 may transmit information on a list of candidates (e.g., node 4, node 5) for which a proxy agreement has been preset with the first node 301 to the relay node 304.

In operation 1050, the relay node 304 transmits transaction data (e.g., data 3) requesting service agreement with the first node 301 to the fourth node 305 based on the candidate group list transmitted from the third node 303. ) can be transmitted.

However, if the fourth node 305 is in an inactive state, the relay node 304 may not receive a response signal to the consensus request from the fourth node 305. For example, referring to FIG. 10A, the fourth node 305 may be in an inactive mode in which network communication is not possible because the remaining battery capacity is below a set reference value or a wireless communication signal is received at a strength below the reference value. .

In operation 1055, when the relay node 304 does not receive a response signal from the fourth node 305 for a set time, it enters into a service agreement with the first node 301 with the fifth node 306 included in the candidate list. Requested transaction data (e.g. data 3) can be transmitted.

In operation 1060, the fifth node 306 turns on the proxy agreement enabled state with respect to the first node 301 according to a transaction agreement request related to the first node 301 that is preset by proxy agreement, proxy agreement information. The table can be updated and proxy agreement can be started on behalf of the first node 301.

In operation 1065, the fifth node 306 may request block data required for transaction agreement related to the first node 301 from the third node 303. In operation 1070, the third node 303 may transmit block data required for service agreement with the first node 301 and the second node 302 to the fifth node 306.

In operation 1075, the fifth node 306 may process a proxy agreement operation (or procedure) based on block data required for service agreement with the first node 301 and the second node 302.

In operation 1080, the fifth node 306 may transmit proxy-agreed completion information and proxy-agreed path change information for the service with the first node 301 and the second node 302 to the relay node 304.

In operation 1085, the relay node 304 may transmit the result of completing the proxy agreement of the transaction to the second node 302. In operation 1090, the relay node 304 may update the consensus path change table so that the fifth node 306 proxy-agrees on the transaction related to the first node 301.

In operation 1095, each node (e.g., the second node 302, the relay node 304, the third node 303, and the fifth node 306) is connected to the first node 301 and the second node ( 302) The transaction agreement results for the service can be recorded or updated in each distributed ledger.

Figure 11 illustrates a proxy agreement method for electronic devices in a mobile blockchain network according to an embodiment.

Referring to FIG. 11, an electronic device (e.g., the electronic device 101 in FIG. 1, the third node 303 in FIG. 3) or a processor of the electronic device 101 participating in a mobile blockchain network according to an embodiment. (e.g., processor 120 in FIG. 1, blockchain processor 230 in FIG. 2), in operation 1110, a first external electronic device (e.g., first node 301 in FIG. 3) participating in the mobile blockchain network. ) can establish a proxy agreement relationship with the first external electronic device. For example, the electronic device 101 may establish a proxy agreement relationship with a first external electronic device (eg, a first node) by performing the procedures of FIG. 4 .

In operation 1120, the electronic device 101 receives a transaction agreement request for services between the first external electronic device and the second external electronic device from the second external electronic device (e.g., the second node 302 in FIG. 3). can do. For example, the electronic device 101 may receive a transaction agreement request for a service through a second external electronic device or a relay node in the mobile blockchain network (eg, relay node 304 in FIG. 3).

In operation 1130, the electronic device 101 may check whether a request to start a proxy agreement has been received.

For example, the electronic device 101 receives transaction data requesting the start of a proxy agreement before the first external electronic device enters the network inactive state from the first external electronic device or the relay node, or receives the first external electronic device from the relay node. You can receive a message requesting to start a proxy agreement by changing the status of proxy agreement with the electronic device.

When a request to start a proxy agreement on behalf of the first external electronic device is received from the first external electronic device or a relay node, the electronic device 101 updates the proxy agreement information table stored in the electronic device 101 to make the first The status of possible proxy agreement for an external electronic device can be recorded from off to on.

If the electronic device 101 does not receive a request to start a proxy agreement, the process may be terminated.

In operation 1140, the electronic device 101 receives a proxy agreement start request for the first external electronic device (or changes the proxy agreement possible state for the first external electronic device from off to on). ), the agreement on service agreement between the first external electronic device and the second external electronic device may be processed (or agreed upon on behalf of the first external electronic device) on behalf of the first external electronic device.

In operation 1150, the electronic device 101 may transmit the result of completing the proxy agreement based on the transaction agreement request to the second external electronic device. For example, the electronic device 101 may transmit the proxy agreement completion result to a second external electronic device through a relay node in the mobile blockchain network.

In operation 1160, the electronic device 101 may check whether a request to stop proxy agreement is received. For example, when a first external electronic device that has established a proxy agreement relationship with the electronic device 101 enters an active state in which network communication is possible from a network inactive state, the first external electronic device can communicate through the mobile blockchain network. You can inform and send a request to stop the proxy agreement. The electronic device 101 may receive a request to stop proxy agreement from the first external electronic device through a relay node in the mobile blockchain network.

In operation 1170, when receiving a request to stop proxy agreement, the electronic device 101 may transmit block data on which proxy agreement has been completed to the first external electronic device. For example, the electronic device 101 may transmit the block data on which the proxy agreement has been completed to the first external electronic device through a relay node in the mobile blockchain network.

When the electronic device 101 does not receive the proxy agreement stop request, the electronic device 101 returns to operation 1140 and, on behalf of the first external electronic device, makes a proxy agreement on the transaction agreement request related to the first external electronic device. The action can be performed.

A proxy consensus method for an inactive node in a blockchain network according to various embodiments is a first among mobile nodes (e.g., the electronic device 101 in FIG. 1 and the third node 303 in FIG. 3) participating in the blockchain network. An operation of establishing a proxy agreement relationship with an external electronic device (e.g., the first node 301 in FIG. 3), and a second external electronic device among mobile nodes participating in the blockchain network (e.g., the second node (301 in FIG. 3) An operation of receiving an agreement request for a first transaction for a service between the first external electronic device and the second external electronic device from 302)), based on receiving a proxy agreement start request of the first external electronic device An operation of performing an agreement operation on behalf of the first external electronic device for a first transaction for a service between the first external electronic device and the second external electronic device, and transmitting the proxy-agreed completion result through the blockchain network. An operation of transmitting to the second external electronic device and an operation of updating the ledger of each node participating in the blockchain network in response to completion of the first transaction agreement between the first external electronic device and the second external electronic device. and the ledger may include at least one block corresponding to each of at least one transaction in which the electronic device participates in an agreement.

A method according to various embodiments includes, when a request to stop proxy agreement is received from the first external electronic device after performing an agreement operation on behalf of the first external electronic device, the block data on which the proxy agreement has been completed is sent to the It may further include transmitting to a first external electronic device.

According to various embodiments, the first external electronic device and the second external electronic device may be mobile nodes.

According to various embodiments, the operation of establishing a proxy agreement relationship with the first external electronic device includes a node item requesting proxy agreement and a proxy on behalf of the requesting node when establishing a proxy agreement relationship with the first external electronic device. The operation of storing a proxy agreement information table including an item for checking the agreement possible state may be further included.

According to various embodiments, the operation of performing a consensus operation on behalf of the first external electronic device may be performed when a proxy agreement possible state with respect to the first external electronic device is recorded as on in the proxy agreement information table. Based on this, a consensus operation may be performed on behalf of the first external electronic device for the first transaction.

According to various embodiments, the operation of performing a consensus operation on behalf of the first external electronic device may be performed when a proxy agreement possible state with respect to the first external electronic device is recorded as off in the proxy agreement information table. In this state, when the proxy agreement start request from the first external electronic device is not received, the first agent based on the operation of receiving a proxy agreement information change request from the relay node and the proxy agreement information change received from the relay node It may further include updating the proxy agreement possible state to on in relation to the external electronic device.

A method according to various embodiments provides, when a request to delete a proxy agreement relationship setting is received from the first external electronic device after performing an agreement operation on behalf of the first external electronic device, information about deletion of the proxy agreement relationship. It may further include the operation of recording in the ledger within the blockchain network.

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. can be used 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 via an application store (e.g. Play Store ^TM ) 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. . 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, omitted, or , or one or more other operations may be added.

Claims (16)

In the electronic device constituting a blockchain node included in a blockchain network,
communication module;
Memory that stores partial or full ledgers, including parts of the full ledger for a blockchain network;
Comprising at least one processor electrically connected to the communication module 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 at least one processor,
Establishing a proxy agreement relationship with the first external electronic device by communicating with the first external electronic device through the communication module,
Receiving an agreement request for a first transaction for a service between the first external electronic device and the second external electronic device through the communication module from a second external electronic device,
An agreement operation on behalf of the first external electronic device for a first transaction for a service between the first external electronic device and the second external electronic device based on receiving a proxy agreement start request from the first external electronic device. Do this,
An electronic device configured to transmit the proxy-agreed completion result to the second external electronic device through the communication module. According to paragraph 1,
The at least one processor,
An electronic device that requests, through the communication module, to update the ledgers of each node participating in the blockchain network in response to completion of a first transaction agreement between the first external electronic device and the second external electronic device. According to paragraph 1,
The at least one processor,
When a request to stop proxy agreement is received from the first external electronic device, the electronic device is further configured to transmit the block data on which the proxy agreement has been completed to the first external electronic device. According to paragraph 1,
The first external electronic device and the second external electronic device are mobile nodes,
The at least one processor,
An electronic device configured to communicate with the first external electronic device and the second external electronic device through a relay node in the blockchain network. According to paragraph 4,
The at least one processor,
When establishing a proxy agreement relationship with the first external electronic device, the electronic device is further configured to store and manage a proxy agreement information table including a node item requesting proxy agreement and an item checking the status of possible proxy agreement on behalf of the requesting node. According to clause 5,
The at least one processor,
To perform an agreement operation on behalf of the first external electronic device for the first transaction based on the proxy agreement possible state in relation to the first external electronic device being recorded as on in the proxy agreement information table. More set up electronics. According to clause 5,
The at least one processor,
If a proxy agreement start request from the first external electronic device is not received while the proxy agreement possible state with respect to the first external electronic device is recorded as off in the proxy agreement information table, the relay node An electronic device further configured to receive a proxy agreement information change request from and update a proxy agreement enabled state with respect to the first external electronic device to on based on the proxy agreement information change received from the relay node. In clause 7,
The at least one processor,
An electronic device configured to record proxy agreement relationship establishment information, proxy agreement operation information, or proxy agreement stop information with the first external electronic device in the ledger within the blockchain network. According to paragraph 1,
The at least one processor,
An electronic device configured to record information about deletion of the proxy agreement relationship in the ledger within the blockchain network when a request to delete the proxy agreement relationship setting is received from the first external electronic device. In the proxy consensus method for inactive nodes in a blockchain network,
An operation of establishing a proxy agreement relationship with a first external electronic device among mobile nodes participating in the blockchain network;
Receiving an agreement request for a first transaction for a service between the first external electronic device and the second external electronic device from a second external electronic device among mobile nodes participating in the blockchain network;
An agreement operation on behalf of the first external electronic device for a first transaction for a service between the first external electronic device and the second external electronic device based on receiving a proxy agreement start request from the first external electronic device. An action to perform;
An operation of transmitting the proxy agreed upon completion result to the second external electronic device through the blockchain network; and
In response to completion of a first transaction agreement between the first external electronic device and the second external electronic device, updating the ledger of each node participating in the blockchain network,
The ledger includes at least one block corresponding to each of at least one transaction in which the electronic device participates in an agreement. According to clause 10,
After performing an agreement operation on behalf of the first external electronic device,
When a request to stop proxy agreement is received from the first external electronic device, the method further includes transmitting block data on which the proxy agreement has been completed to the first external electronic device. According to clause 10,
The method wherein the first external electronic device and the second external electronic device are mobile nodes. According to clause 10,
The operation of establishing a proxy agreement relationship with the first external electronic device includes:
When establishing a proxy agreement relationship with the first external electronic device, the method further includes storing a proxy agreement information table including a node item requesting proxy agreement and an item checking whether a proxy agreement is possible on behalf of the requesting node. . According to clause 13,
The operation of performing an agreement operation on behalf of the first external electronic device is:
Performing an agreement operation on behalf of the first external electronic device for the first transaction based on the fact that the proxy agreement possible state with respect to the first external electronic device is recorded as on in the proxy agreement information table. A method characterized by: According to clause 10,
The operation of performing an agreement operation on behalf of the first external electronic device is:
If a proxy agreement start request from the first external electronic device is not received while the proxy agreement possible state with respect to the first external electronic device is recorded as off in the proxy agreement information table, the relay node An operation of receiving a request to change proxy agreement information from; and
The method further includes updating a proxy agreement enabled state with respect to the first external electronic device to on based on a change in proxy agreement information received from the relay node. According to clause 10,
After performing an agreement operation on behalf of the first external electronic device,
When a request to delete the proxy agreement relationship setting is received from the first external electronic device, the method further includes recording information about deletion of the proxy agreement relationship in the ledger in the blockchain network.

Images