Electronic device and method for sharing file

Abstract

Provided are an electronic device and method for sharing a file. The method by which a first electronic device shares a file comprises: a step for selecting a second electronic device registered in a server for a security sharing service; a step for identifying whether a network state and a system time setting of the second electronic device satisfy a preset criterion for the security sharing service; a step for encoding the file; a step for transmitting the encoded file to the second electronic device; a step (430) for generating a security channel for generating a blockchain for the security sharing service with the second electronic device as the preset criterion is satisfied; a step for generating transaction information related to the encoded file transmitted to the second electronic device; and a step for recording the generated transaction information in a blockchain ledger of the blockchain through the security channel.

Description

Electronic devices and methods for sharing files

[0001] The present disclosure relates to an electronic device and method for sharing files, and more particularly, to an electronic device and method for sharing files via a blockchain network.

[0002] A blockchain network is a decentralized network, distinct from a centralized network where decision-making is performed by a central server. A blockchain network can refer to a network where decisions are made based on a consensus algorithm among the nodes participating in the blockchain network.

[0003] The ledger existing in a blockchain network can be stored on each node participating in the blockchain network. The ledger existing in a blockchain network can be updated according to the consensus algorithm of the nodes participating in the blockchain network.

[0004] Blockchain is a technology that maintains security and integrity in a decentralized network environment without a centralized server. An example of a blockchain-based method for user authentication is issuing a key pair from a private blockchain network and authenticating the user using that key pair.

[0005] One embodiment of the present disclosure may provide a method for a first electronic device to share a file with a second electronic device, the method comprising: selecting the second electronic device registered on a server for a secure sharing service; identifying whether a network status and a system time setting of the second electronic device satisfy preset criteria for the secure sharing service; encrypting the file; transmitting the encrypted file to the second electronic device; generating a secure channel with the second electronic device for generating a blockchain for the secure sharing service when the preset criteria are satisfied; generating transaction information related to the encrypted file transmitted to the second electronic device; and recording the generated transaction information in a blockchain ledger of the blockchain through the secure channel.

[0006] In addition, one embodiment of the present disclosure may provide a first electronic device including: a first communication interface; a second communication interface; a memory storing commands; and a processor; wherein the commands, when executed by the processor, cause the first electronic device to: select the second electronic device registered with a server (130) for a secure sharing service, identify whether a network status and a system time setting of the second electronic device satisfy preset criteria for the secure sharing service, encrypt the file, transmit the encrypted file to the second electronic device, and, when the preset criteria are satisfied, create a secure channel with the second electronic device for creating a blockchain for the secure sharing service, create transaction information related to the encrypted file transmitted to the second electronic device, and record the created transaction information in a blockchain ledger of the blockchain through the secure channel.

[0007] In addition, one embodiment of the present disclosure may provide a computer-readable recording medium having recorded thereon a program for executing the following operations: selecting the second electronic device registered on a server for a secure sharing service; identifying whether a network status and a system time setting of the second electronic device satisfy preset criteria for the secure sharing service; encrypting the file; transmitting the encrypted file to the second electronic device; generating a secure channel with the second electronic device for generating a blockchain for the secure sharing service when the preset criteria are satisfied; generating transaction information related to the encrypted file transmitted to the second electronic device; and recording the generated transaction information in a blockchain ledger of the blockchain through the secure channel.

[0008] An embodiment of the present disclosure may provide a method for a first electronic device to share a file with a second electronic device, the method comprising: selecting a second electronic device registered on a server for a secure sharing service when a secure sharing function of a file sharing application of the first electronic device is activated; identifying whether a network status and a system time setting of the second electronic device satisfy preset criteria for the secure sharing service; establishing a communication connection with the second electronic device through a D2D communication network; encrypting the file; transmitting the encrypted file to the second electronic device through the D2D communication network; generating a secure channel with the second electronic device for generating a blockchain for the secure sharing service through the D2D communication when the preset criteria are satisfied; generating transaction information related to the encrypted file transmitted to the second electronic device; and recording the generated transaction information in a blockchain ledger of the blockchain through the secure channel.

[0009] FIG. 1 is a schematic diagram of a file sharing system using blockchain according to one embodiment of the present disclosure.

[0010] FIG. 2 is a block diagram of an electronic device according to one embodiment.

[0011] FIG. 3 is a diagram illustrating a blockchain network according to one embodiment.

[0012] FIG. 4 is a flowchart of a method for a first electronic device and a second electronic device to share and manage files through a blockchain network according to one embodiment of the present disclosure.

[0013] FIG. 5 is a flowchart illustrating a method for a first electronic device to share a file with a second electronic device registered to a security sharing service through a blockchain network according to one embodiment.

[0014] FIG. 6 is a diagram illustrating an example of a first electronic device according to an embodiment of the present disclosure creating a secure channel, transmitting a file to a second electronic device, and synchronizing a blockchain ledger through D2D communication.

[0015] FIG. 7 is a diagram illustrating an example in which a first electronic device creates a secure channel through D2D communication, transmits a file to a second electronic device, and synchronizes a blockchain ledger after the D2D communication connection is released, according to one embodiment of the present disclosure.

[0016] FIG. 8 is a diagram illustrating an example of a first electronic device transmitting a file to a second electronic device via D2D communication, and creating a secure channel and synchronizing a blockchain ledger after the D2D communication connection is released, according to one embodiment of the present disclosure.

[0017] FIG. 9 is a drawing showing an example of an execution screen in a general sharing mode of a file sharing application displayed on a screen of a first electronic device according to one embodiment of the present disclosure.

[0018] FIG. 10 is a drawing showing an example of an execution screen in a secure sharing mode of a file sharing application displayed on a screen of a first electronic device according to one embodiment of the present disclosure.

[0019] FIG. 11 is a diagram illustrating changes in icons and text corresponding to a second electronic device displayed on a screen of a first electronic device according to a status of a sharing procedure as procedures for secure sharing of files between a first electronic device and a second electronic device are performed according to an embodiment of the present disclosure.

[0020] FIG. 12 is a drawing showing an example of an execution screen of a file sharing application displayed on a screen of a second electronic device as procedures for secure file sharing between a first electronic device and a second electronic device are performed according to an embodiment of the present disclosure.

[0021] FIG. 13 is a block diagram of an electronic device within a network environment according to various embodiments.

[0022] Below, embodiments of the present disclosure are described in detail with reference to the attached drawings so that those skilled in the art can easily implement the present disclosure. However, the present disclosure may be implemented in various different forms and is not limited to the embodiments described herein. In addition, for the purpose of clearly explaining the present disclosure in the drawings, parts irrelevant to the description are omitted, and similar parts are designated with similar reference numerals throughout the specification.

[0023] The terms used in this disclosure are described as currently common terms, taking into account the functions mentioned herein. However, these terms may mean various other terms depending on the intentions of those skilled in the art, precedents, the emergence of new technologies, etc. Therefore, the terms used in this disclosure should not be interpreted solely based on their names, but rather based on the meanings of the terms and the overall content of this disclosure.

[0024] Additionally, while terms such as first, second, etc. may be used to describe various components, the components should not be limited by these terms. These terms are used to distinguish one component from another.

[0025] Throughout the specification, when a part is said to be "connected" to another part, this includes not only the "direct connection" but also the "electrical connection" with other elements intervening between them. Furthermore, when a part is said to "include" a component, this does not exclude other components, but rather includes the possibility of including other components, unless otherwise stated.

[0026] The phrases “in one embodiment” and the like appearing in various places throughout this disclosure do not necessarily all refer to the same embodiment.

[0027] An embodiment of the present disclosure may be represented by functional block configurations and various processing steps. Some or all of these functional blocks may be implemented by various hardware and / or software configurations that perform specific functions. For example, the functional blocks of the present disclosure may be implemented by one or more microprocessors or by circuit configurations for a given function. Furthermore, for example, the functional blocks of the present disclosure may be implemented in various programming or scripting languages. The functional blocks may be implemented by algorithms that execute on one or more processors. Furthermore, the present disclosure may employ conventional techniques for electronic configuration, signal processing, and / or data processing. Terms such as "mechanism," "element," "means," and "configuration" may be used broadly and are not limited to mechanical and physical configurations.

[0028] Additionally, the connecting lines or connecting members between components depicted in the drawings are merely exemplary representations of functional connections and / or physical or circuit connections. In an actual device, connections between components may be represented by various functional connections, physical connections, or circuit connections that may be replaced or added.

[0029] The present disclosure will be described in detail with reference to the attached drawings below.

[0030] FIG. 1 is a schematic diagram of a file sharing system using blockchain according to one embodiment of the present disclosure.

[0031] Referring to FIG. 1, a file sharing system according to one embodiment may include a first electronic device (110), a second electronic device (120), and a server (130).

[0032] According to one embodiment, a first electronic device (110) is connected to a second electronic device (120) for communication, and the first electronic device (110) can transmit a file to be shared to the second electronic device (120). The first electronic device (110) and the second electronic device (120) may be electronic devices pre-registered with a server (130) that provides a secure sharing service. The secure sharing service may be a service that provides security for files shared between electronic devices using blockchain technology and manages file usage rights. For example, the first electronic device (110) and the second electronic device (120) may be connected to each other for communication using D2D (device to device) communication, and files may be transmitted between the first electronic device (110) and the second electronic device (120) through D2D communication.

[0033] According to one embodiment, the first electronic device (110) may create a secure channel for the blockchain network with the second electronic device (120) in order to record information related to file transfer in a blockchain ledger within the blockchain network. For example, the first electronic device (110) may create a secure channel for the blockchain network with the second electronic device (120) by transmitting and receiving data for forming the secure channel through D2D communication between the first electronic device (110) and the second electronic device (120). Furthermore, for example, the first electronic device (110) may create a secure channel for the blockchain network together with the second electronic device (120) and the server (130).

[0034] In one embodiment, the first electronic device (110) may record transaction information related to the transmission of a file generated by the first electronic device (110) and the second electronic device (120) in a blockchain ledger within a blockchain network. Accordingly, the first electronic device (110) and the second electronic device (120) may manage the security and usage rights of the file transmitted between the first electronic device (110) and the second electronic device (120) using the blockchain network.

[0035] According to one embodiment, the first electronic device (110) is a device capable of transmitting and receiving data over a network, and may be, but is not limited to, a smartphone, a tablet PC, a mobile phone, a personal digital assistant (PDA), a laptop, a media player, a global positioning system (GPS) device, an e-book reader, a digital broadcasting terminal, a navigation device, a digital camera, a home appliance, or other mobile / non-mobile computing device.

[0036] According to one embodiment, the second electronic device (120) is a device capable of transmitting and receiving data over a network, and may be, but is not limited to, a smartphone, a tablet PC, a mobile phone, a personal digital assistant (PDA), a laptop, a media player, a global positioning system (GPS) device, an e-book reader, a digital broadcasting terminal, a navigation device, a digital camera, a home appliance, or other mobile / non-mobile computing device.

[0037] According to one embodiment, the file shared between the first electronic device (110) and the second electronic device (120) may be content data. For example, the file may be content data such as an e-book, a document, an image, audio, a video, an application, or a combination thereof, but is not limited thereto.

[0038] FIG. 2 is a block diagram of an electronic device according to one embodiment.

[0039] Referring to FIG. 2, the first electronic device (110) may include a memory (111), a communication module (112), a processor (113), and a display (114), or a combination thereof. According to one embodiment, the memory (121), the communication module (122), the processor (123), and the display (124) of the second electronic device (120) may correspond to the memory (111), the communication module (112), the processor (113), and the display (114) of the first electronic device (110), respectively, and may perform the same function. In one embodiment, the first electronic device (110) and the second electronic device (120) may include additional components in addition to the components illustrated in FIG. 1, or may omit at least one of the components illustrated in FIG. 1.

[0040] According to one embodiment, the memory (111) may store instructions that cause the processor (113) to process data or control components of the first electronic device (110) to perform operations of the first electronic device (110) when executed. The memory (111) may include a secure area or a separate secure storage medium (e.g., a secure memory area (e.g., a trust zone) that is accessible only through a secure OS).

[0041] According to one embodiment, the communication module (112) may be configured to be connected to an external device to transmit and receive files. The communication module (112) may include a first communication module (112-1) that performs short-range communication and a second communication module (112-2) that performs communication with a server (130). The first communication module (112-1) is a module for D2D (device to device) communication, and may be, for example, a module for Bluetooth (e.g., BLE) communication and WiFi (e.g., WiFi-direct, WiFi-aware) communication. In addition, the second communication module (112-2) may be a module for wireless communication rather than short-range communication. According to one embodiment, the communication module (112) may transmit and receive files with a second electronic device (120). According to one embodiment, the communication module (112) may communicate with various external servers. For example, the first electronic device (110) can transmit a file to an external server and receive a response from the external server using the communication module (112).

[0042] According to one embodiment, the processor (113) may be electrically or operatively connected to the memory (111), the communication module (112), and the display (114). According to one embodiment, the processor (113) may execute operations or data processing related to control and / or communication of at least one other component of the first electronic device (110) using instructions stored in the memory (111). According to one embodiment, the processor (113) may include at least one of a central processing unit (CPU), a graphics processing unit (GPU), a micro controller unit (MCU), a sensor hub, a supplementary processor, a communication processor, an application processor, an application specific integrated circuit (ASIC), and a field programmable gate array (FPGA), and may have a plurality of cores.

[0043] According to one embodiment, the display (114) can display various contents (e.g., text, images, videos, icons, and / or symbols, etc.).

[0044] According to one embodiment, the processor (113) may execute instructions contained in the memory (111) to generate a key pair using an asymmetric key cryptography method (e.g., public-key cryptography). In one embodiment, the memory (111) may store the generated private key. In one embodiment, the memory (111) in which the generated key pair is stored may refer to a secure memory, which is a memory that provides a security environment.

[0045] According to one embodiment, the processor (113) may generate a blockchain address using an encryption key (e.g., a private key). For example, the processor (113) may generate a public key using a predetermined algorithm using the private key, and may generate an address usable in the blockchain using a hash function from the generated public key. According to one embodiment, the processor (113) may determine at least one second electronic device (120) with which to share a file. For example, the user of the second electronic device (120) with which the file of the first electronic device (110) will be shared may be determined by the user of the first electronic device (110).

[0046] According to one embodiment, the processor (113) can transmit a file to a second electronic device (120) to share the file using the communication module (112).

[0047] In one embodiment, the processor (113) may create a blockchain network to share files with the second electronic device (120). For example, the processor (113) may create a blockchain network including the second electronic device (120) as a node based on a response message received from the second electronic device (120) in response to an invitation message from a user of the first electronic device (110). In one embodiment, the processor (113) may store information about the created blockchain network in the server (130) using the communication module (112).

[0048] According to one embodiment, the processor (113) can perform the operations of the first electronic device (110) in FIGS. 4 to 12, which will be described later.

[0049] According to one embodiment, the processor (113) may select a second electronic device (120) registered with the server (130) for a secure sharing service of the first electronic device (110). According to one embodiment, the processor (113) may connect the first electronic device (110) to the second electronic device (120) via short-range wireless communication. According to one embodiment, the processor (113) may receive status information for the secure sharing service from the second electronic device (120). According to one embodiment, the processor (113) may identify whether the second electronic device (120) satisfies a condition for the secure sharing service. According to one embodiment, the processor (113) may encrypt a file to be shared with the second electronic device (120). According to one embodiment, the processor (113) may transmit the encrypted file to the second electronic device (120). In one embodiment, the processor (113) may create a secure channel for a blockchain network with a second electronic device (120). In one embodiment, the processor (113) may create transaction information regarding file sharing. In one embodiment, the processor (113) may transmit transaction information regarding file transfer to the second electronic device (120). In one embodiment, the processor (113) may record the transaction information in a blockchain ledger via the secure channel.

[0050] According to one embodiment, the processor (113) may register the first electronic device (110) with the server (130) for a secure sharing service. According to one embodiment, the processor (113) may activate a secure sharing function. According to one embodiment, the processor (113) may transmit at least one inquiry message including conditions for the secure sharing service to the second electronic device (120), and according to one embodiment, the processor (113) may receive at least one response message from the second electronic device (120) regarding whether the conditions for the secure sharing service are satisfied. According to one embodiment, the processor (113) may identify whether the second electronic device (120) satisfies the conditions for the secure sharing service. According to one embodiment, the processor (113) may encrypt a file. According to one embodiment, the processor (113) may transmit the encrypted file to the second electronic device (120). According to one embodiment, the processor (113) may generate transaction information. In one embodiment, the processor (113) may provide transaction information to the second electronic device (120). In one embodiment, the processor (113) may identify whether a secure channel exists. In one embodiment, the processor (113) may create a secure channel with the second electronic device (120). In one embodiment, the processor (113) may synchronize the blockchain ledger.

[0051] FIG. 3 is a diagram illustrating a blockchain network according to one embodiment.

[0052] Referring to FIG. 3, a plurality of electronic devices (110, 120) may form a blockchain network (200). Although the present disclosure has been described as comprising two electronic devices for convenience of explanation, the present disclosure is not limited thereto. According to one embodiment, a first electronic device (110) may form a blockchain network (200) with at least one external electronic device with which to share a file. For example, the first electronic device (110) may form a blockchain network (200) with a second electronic device (120) as a node. According to one embodiment, the first electronic device (110) may create a plurality of blockchain networks to share files. For example, a first blockchain network may be formed by the first electronic device (110) and another external electronic device (not shown), and a second blockchain network may be formed by the first electronic device (110) and external electronic devices (120, 130).

[0053] According to one embodiment, the first electronic device (110) may generate a plurality of public keys and private keys corresponding to the public keys based on a root seed. According to one embodiment, the first electronic device (110) may generate a plurality of public keys and private keys corresponding to each of a plurality of blockchain networks that include the first electronic device (110) as a node. Based on each of the plurality of public keys, blockchain networks corresponding to each of the plurality of public keys may be formed.

[0054] In this document, a blockchain network (200) created for file sharing can be formed by a secure shared channel. Each secure shared channel can be distinguished based on the electronic devices (users) included in the secure shared channel. For example, if the electronic devices constituting the blockchain network (200) are different, they can be distinguished by different secure shared channels, but this is not a limitation.

[0055] According to one embodiment, the blockchain network (200) may include a blockchain ledger based on the blockchain network. That is, there may be a blockchain ledger corresponding to each blockchain network. In one embodiment, the blockchain ledger may be composed of a block ledger in which transaction information is stored and a world state data that stores values ​​changed by executing transactions in the form of key values. The world state data may be, for example, data stored in a world state, a database used in Hyperledger Fabric, but is not limited thereto.

[0056] The world state is a type of database used in Hyperledger Fabric. It can store the final values ​​changed by executing transactions in the form of key values. Therefore, to verify the final values ​​resulting from transaction execution within the blockchain network (200), the world state data can be checked. The world state data stored in the world state can appear as the same value on all electronic devices constituting the blockchain network. In other words, the world state data can have characteristics similar to global variables within the blockchain network.

[0057] In one embodiment, a block may consist of transactions containing information for executing a smart contract. Accordingly, blocks in a blockchain ledger form a chain and block data can be stored in the block ledger. In one embodiment, all blockchain nodes included in a blockchain network (200) may possess the same blockchain ledger. Therefore, if a different blockchain ledger is discovered, blockchain nodes may question the reliability and validity of the block.

[0058] A block ledger may include a block header and transaction data. In one embodiment, the block header may include, but is not limited to, at least one of a hash value of the header and data area, a hash value of a previous block, a height value of the block, a hash value of world state data after performing a transaction included in the block, a public key of the block creator, a value obtained by signing a hash with the block creator's private key, an attestation key certificate chain, or a value obtained by signing a hash value with an attestation key.

[0059] Block data may include, but is not limited to, at least one of a hash value of at least a portion of transaction data, version information of a smart contract, a smart contract ID, a smart contract function ID, smart contract data which is an argument value required for a smart contract function, a nonce value which is the transaction generation number of the transaction creator, a value obtained by signing a hash value with the transaction creator's private key, a proof key authentication chain, or a value obtained by signing a hash value with a proof key.

[0060] FIG. 4 is a flowchart of a method for a first electronic device and a second electronic device to share and manage files through a blockchain network according to one embodiment of the present disclosure.

[0061] In operation 400, the first electronic device (110) can select a second electronic device (120) registered with the server (130) for a secure sharing service. The first electronic device (110) can display a list of electronic devices capable of receiving a file transmitted by the first electronic device (110) on the screen of the first electronic device (110), and can select the second electronic device (120) from the list of electronic devices based on a user input.

[0062] According to one embodiment, the list of electronic devices may include identification values ​​of electronic devices pre-registered with the server (130) providing the secure sharing service. For example, an electronic device registered with the server (130) providing the secure sharing service may be issued a private number by the server (130), and the server (130) may register the phone number and private number of the electronic device.

[0063] According to one embodiment, when the first electronic device (110) activates the secure sharing function, a list of electronic devices registered with the server (130) may be displayed on the screen of the first electronic device (110). For example, the first electronic device (110) may execute an application for file sharing and receive a user input for selecting an object for activating the secure sharing function on the screen of the application. In response to the user input, the first electronic device (110) may display a list of electronic devices registered with the server (130) that provides the secure sharing service.

[0064] In one embodiment, for example, the first electronic device (110) may search for electronic devices in the vicinity via Bluetooth communication (e.g., BLE) and display a list of electronic devices based on response packets received from the electronic devices in the vicinity. In this case, the search request packet broadcast by the first electronic device (110) to search for electronic devices in the vicinity may include data inquiring whether the electronic device is registered with the server (130).

[0065] In operation 405, the first electronic device (110) may be connected to the second electronic device (120) via short-range wireless communication. For example, the first electronic device (110) may be connected to the second electronic device (120) via Bluetooth communication (e.g., BLE communication). Alternatively, for example, the first electronic device may be connected to the second electronic device (120) via WiFi communication (e.g., WiFi-direct, WiFi-aware).

[0066] In operation 410, the first electronic device (110) may receive status information for a secure sharing service from the second electronic device (120). According to one embodiment, the first electronic device (110) may receive information regarding the network status of the second electronic device (120) and the time setting of the second electronic device (120) from the second electronic device (120). According to one embodiment, the information regarding the network status of the second electronic device (120) may be information indicating whether a communication function of a network designated to enable the second electronic device (120) to transmit and receive data is activated. For example, since a designated network function must be activated to create a secure channel or update a blockchain ledger, the first electronic device (110) may receive information regarding the network status of the second electronic device (120) from the second electronic device (120).

[0067] According to one embodiment, the information regarding the time setting of the second electronic device (120) may be information regarding whether the system time of the second electronic device (120) is set to be synchronized with a reference time (e.g., standard time). For example, in order to synchronize the transmission time of a file between the first electronic device (110) and the second electronic device (120) for updating a blockchain ledger, the first electronic device (110) may receive information regarding the time setting of the second electronic device (120) from the second electronic device (120).

[0068] In operation 415, the first electronic device (110) can identify whether the second electronic device (120) satisfies the conditions for a secure sharing service. Based on the status information for the secure sharing service received from the second electronic device (120), the first electronic device (110) can identify whether the second electronic device (120) satisfies the conditions for sharing files through the secure sharing service. For example, the first electronic device (110) can identify whether a communication function of a network designated to enable the second electronic device (120) to transmit and receive data is activated. For example, the first electronic device (110) can identify whether the time of the second electronic device (120) is set to be synchronized with a reference time.

[0069] In operation 420, the first electronic device (110) can encrypt a file to be shared with the second electronic device (120). The first electronic device (110) can encrypt the file to be transmitted to the second electronic device (120) using a preset encryption key. For example, the first electronic device (110) can encrypt the file using a symmetric key pre-specified by the first electronic device (110) and the second electronic device.

[0070] According to one embodiment, the first electronic device (110) may generate detailed information about a file to be shared. The detailed information about the file to be shared may include, for example, at least one of a validity period of the file to be shared, an encrypted file list, a secure sharing ID, a mime type of the file, a file key, a file name, a thumbnail file key, or a thumbnail file name.

[0071] In operation 425, the first electronic device (110) may transmit an encrypted file to the second electronic device (120). The first electronic device (110) may transmit the encrypted file to the second electronic device (120) via short-range communication in operation 405, but is not limited thereto. The encrypted file may be stored in each of the first electronic device (110) and the second electronic device (120).

[0072] In steps 430 and 435, the first electronic device (110) and the second electronic device (120) can create a secure channel for a blockchain network.

[0073] According to one embodiment, a first electronic device (110) can create a secure channel for a blockchain network by transmitting and receiving information necessary for creating a secure channel with a second electronic device (120) through short-range communication. The first electronic device (110) can request the second electronic device (120) to create a secure channel, and can exchange information for creating the secure channel with the second electronic device (120). For example, the first electronic device (110) can request the creation of a secure channel using a unique number of the second electronic device (120), update device information of the second electronic device (120), and wait for the creation of the secure channel, and the second electronic device (120) can update device information of the first electronic device (110) and wait for the creation of the secure channel.

[0074] According to one embodiment, when a first electronic device (110) and a second electronic device (120) transmit and receive information necessary for creating a secure channel through D2D communication, at least one authentication procedure for requesting an invitation for creating a secure channel, accepting the invitation, and validating the inviter may be omitted. For example, since a secure channel can be established through message transmission and reception between the first electronic device (110) and the second electronic device (120) through D2D communication, encryption and signing of data for creating a channel, data for an invitation, and data for accepting the invitation may be omitted. For example, the first electronic device (110) may generate a Root Seed based on a Mnemonic Hash, generate a public key based on HdPath, and transmit invitation information to the second electronic device (120), but a procedure for signing the invitation information with a private key and a procedure for signing the invitation information with an attestation key may be omitted. For example, the second electronic device (120) may generate invitation acceptance data, but the procedure for verifying invitation information through signature verification of the proof key and signature verification of the public key and the procedure for signing invitation acceptance data may be omitted. For example, the first electronic device (110) may receive an invitation acceptance message, and the procedure for verifying the invitation acceptance message through signature verification of the proof key and signature verification of the public key may be omitted. In addition, for example, since the first electronic device (110) and the second electronic device (120) transmit and receive data through D2D communication that can trust each other, data transmitted and received between the first electronic device (110) and the second electronic device (120) through D2D communication may not be encrypted.

[0075] According to one embodiment, a first electronic device (110) that receives an invitation acceptance message may provide a genesis transaction to a second electronic device (120), and a blockchain network and secure channel for secure sharing may be formed between the first electronic device (110) and the second electronic device (120). Accordingly, a procedure for a genesis transaction for creating a secure channel and adding members between the first electronic device (110) and the second electronic device (120) may be performed quickly and simply.

[0076] According to one embodiment, verification of a genesis transaction for creating a secure channel and adding members may be performed by, but is not limited to, a first electronic device (110) and / or a second electronic device (120) via a server (130).

[0077] In one embodiment, the address of the generated secure channel may be registered with the server (130), but is not limited thereto. If the server (130) does not participate in a secure sharing service via a blockchain network, the process of registering the address of the generated secure channel with the server (130) may be omitted.

[0078] Alternatively, according to one embodiment, after the short-range communication connection between the first electronic device (110) and the second electronic device (120) is terminated, the first electronic device (110) may create a secure channel for the blockchain network with the second electronic device (120). In this case, the first electronic device (110) may create a secure channel for the blockchain network by exchanging information for creating the secure channel with the second electronic device (120) through the server (130). The first electronic device (110) may request the second electronic device (120) to create a secure channel, and may exchange information for creating the secure channel with the second electronic device (120). For example, the first electronic device (110) may request the creation of a secure channel using the unique number of the second electronic device (120), update the device information of the second electronic device (120), and wait for the creation of the secure channel, and the second electronic device (120) may update the device information of the first electronic device (110) and wait for the creation of the secure channel. According to one embodiment, when the first electronic device (110) and the second electronic device (120) transmit and receive information necessary for the creation of a secure channel through the server (130), at least one authentication procedure for an invitation request for the creation of a secure channel, an invitation acceptance procedure, and an inviter validity procedure may be performed. For example, encryption and signing may be performed on data for channel creation, data for invitation, and data for invitation acceptance. For example, the first electronic device (110) can generate a Root Seed based on a Mnemonic Hash, generate a public key based on HdPath, and transmit invitation information to the second electronic device (120). In this case, a procedure for signing the invitation information with a private key and a procedure for signing the invitation information with an attestation key can be performed.In addition, for example, the second electronic device (120) can generate invitation acceptance data, and for this purpose, can perform a procedure for verifying invitation information through signature verification of a proof key and signature verification of a public key, and a procedure for signing invitation acceptance data. In addition, for example, the first electronic device (110) can receive an invitation acceptance message, and can perform a procedure for verifying the invitation acceptance message through signature verification of a proof key and signature verification of a public key. In addition, for example, since the first electronic device (110) and the second electronic device (120) transmit and receive data through the server (130), data transmitted and received between the first electronic device (110) and the second electronic device (120) through the server (130) can be encrypted. In addition, according to one embodiment, the address of the generated secure channel can be registered in the server (130), and verification of a genesis transaction for creating a secure channel and adding members can be performed through the server (130).

[0079] In operation 440, the first electronic device (110) may generate transaction information regarding file sharing. According to one embodiment, the first electronic device (110) may generate transaction information including detailed information regarding file sharing. For example, after the first electronic device (110) transmits a file to the second electronic device (120), the mapping of file information and a unique key required for synchronizing the blockchain ledger may be updated in the first electronic device (110) and the second electronic device (120) so that transaction information including detailed information regarding file sharing can be generated. In this case, the first electronic device (110) providing the file to be shared may set permissions regarding reading, deleting, and modifying the file, and may generate transaction information by setting a validity period for accessing the file.

[0080] For example, information for synchronizing a blockchain ledger can be shared and updated by a first electronic device (110) and a second electronic device (120). For example, the first electronic device (110) can generate a message including a unique number of the first electronic device (110), a sharing expiration date, and file information, and transmit the message to the second electronic device (120). For example, the second electronic device (120) can update information within the second electronic device (120) based on the received message and transmit a response message to the first electronic device (110). For example, the first electronic device (110) and the second electronic device (120) can exchange messages in a format as shown in below.

[0081]

[0082] Transaction information may include, but is not limited to, at least one of, for example, a unique number of the first electronic device (110), a validity period (or expiration date) of a file to be shared, an identification value of an encrypted file, a secure sharing ID, a mime type of the file, an identification value of a file for decrypting an encrypted file, a file key, a file name, a thumbnail file key, or a thumbnail file name. In addition, for example, the file key or the thumbnail file key may be generated and managed separately from the transaction information.

[0083] In operation 445, the first electronic device (110) may transmit transaction information regarding file transfer to the second electronic device (120). The first electronic device (110) may provide the transaction information to the second electronic device (120) via D2D communication. Alternatively, the first electronic device (110) may provide the transaction information to the second electronic device (120) via a secure channel. The transaction information provided to the second electronic device (120) may be validated by the second electronic device (120).

[0084] In steps 450 and 455, the first electronic device (110) and the second electronic device (120) may record transaction information in a blockchain ledger via a secure channel. Once the transaction information is verified by the second electronic device (120), the first electronic device (110) and the second electronic device (120) may synchronize blocks containing the transaction information. Each of the first electronic device (110) and the second electronic device (120) may include blocks containing the transaction information in a blockchain ledger within a blockchain network.

[0085] In one embodiment, if transaction information occurs normally, the transaction information may be data for recording the transaction's contents in a blockchain ledger. For example, the transaction information may include data indicating file transfer history between accounts within a blockchain network. A transaction may refer to an act that causes a change in the contents of a blockchain ledger. For example, transaction information that is successfully signed may be recorded in the blockchain ledger, while transaction information that is not successfully signed may not be recorded in the ledger. For example, whether transaction information is recorded in a block by a transaction can be tracked through a transaction ID. For example, transaction information may be recorded in the blockchain ledger using a smart contract.

[0086] In one embodiment, a blockchain ledger may be a chain of data, where each block containing transaction information for at least one transaction references a previous block containing transaction information for another transaction. In one embodiment, at least a portion of the blockchain ledger may be stored on nodes within the blockchain network (e.g., the first electronic device (110) and the second electronic device (120)).

[0087] FIG. 5 is a flowchart illustrating a method for a first electronic device to share a file with a second electronic device registered to a security sharing service through a blockchain network according to one embodiment.

[0088] In operation 500, the first electronic device (110) may register the first electronic device (110) with the server (130) for a secure sharing service. The first electronic device (110) may request the server (130) providing the secure sharing service to register the first electronic device (110). Accordingly, a unique number for secure sharing may be issued by the server (130). For example, a push token capable of receiving a push from the server (130) may be registered with the server (130), thereby issuing a private number of the first electronic device (110) by the server (130). In addition, for example, the phone number and private number of the first electronic device (110) may be registered with the server (130).

[0089] In operation 505, the second electronic device (120) may register the second electronic device (120) with the server (130) for a secure sharing service. The second electronic device (120) may request the server (130) providing the secure sharing service to register the second electronic device (120). Accordingly, a unique number for secure sharing may be issued by the server (130). For example, a push token capable of receiving a push from the server (130) may be registered with the server (130), thereby issuing a private number of the second electronic device (120) by the server (130). In addition, for example, the phone number and private number of the second electronic device (120) may be registered with the server (130).

[0090] In operation 510, the first electronic device (110) may activate a secure sharing function. For example, the first electronic device (110) may run an application for file sharing and receive a user input selecting an object for activating the secure sharing function on the application's screen. As the object for activating the secure sharing function is selected, the first electronic device (110) may activate the secure sharing function.

[0091] According to one embodiment, when a user input for activating a secure sharing function is received on the screen of an application, if the first electronic device (110) is not registered with the server (130) for the secure sharing service, the first electronic device (110) may display a GUI (graphical user interface) for registering the first electronic device (110) with the secure sharing service. In addition, the first electronic device (110) may perform operation 500 for registering the first electronic device (110) with the server (130) based on the user input for the GUI displayed on the screen.

[0092] In operation 515, the first electronic device (110) may transmit to the second electronic device (120) at least one inquiry message including conditions for a secure sharing service, and in operation 520, the second electronic device (120) may transmit to the first electronic device (110) at least one response message regarding whether the conditions for the secure sharing service are satisfied.

[0093] According to one embodiment, the first electronic device (110) can search for at least one external electronic device nearby using short-range communication. For example, the first electronic device (110) can broadcast a search request packet using Bluetooth communication (e.g., BLE (Bluetooth low energy)). In this case, at least one external electronic device including the second electronic device (120) can broadcast a search response packet in response to the search request packet from the first electronic device (110). For example, the second electronic device (120) can broadcast the search response packet via a low-power Bluetooth advertisement packet (BLE advertisement packet). In addition, the first electronic device (110) can receive the search response packet from the second electronic device (120) and display a list of searched electronic devices on the screen. In this case, the first electronic device (110) can include only external electronic devices registered with the server (130) that provides the secure unique service in the list. Additionally, the first electronic device (110) can receive a user input for selecting a second electronic device (120) from a list of electronic devices.

[0094] For example, when a first electronic device (110) searches for a second electronic device (120) via BLE communication, the first electronic device (110) may request information about a feature regarding whether the second electronic device (120) can use a secure sharing service from the second electronic device (120). For example, the first electronic device (110) may provide a message in a format as shown in below to the second electronic device (120), and the second electronic device (120) may provide a response message in a format as shown in below to the first electronic device (110).

[0095]

[0096] According to one embodiment, the first electronic device (110) may request a D2D communication connection (e.g., Wi-Fi communication) to the second electronic device (120), and during the D2D communication connection process, the second electronic device (120) may provide the unique number of the first electronic device (110). In addition, the second electronic device (120) may accept the D2D communication connection, thereby forming a D2D communication session for file transfer. For example, a Wi-Fi-Direct communication or Wi-Fi-Aware communication session for file transfer may be formed.

[0097] According to one embodiment, after D2D communication is established, the first electronic device (110) and the second electronic device (120) may exchange data to identify whether preset conditions for a secure sharing service are satisfied through two-way messaging. For example, when creating a secure channel, the first electronic device (110) and the second electronic device (120) must be connected to a network for communication with the server (130) in order to register a channel address with the server (130) or update the blockchain ledger. Therefore, the first electronic device (110) and the second electronic device (120) may exchange information regarding the network status. In addition, for example, to synchronize the blockchain ledger, the first electronic device (110) and the second electronic device (120) may exchange information indicating whether the system time is automatically set to a specified standard time.

[0098] In addition, for example, the first electronic device (110) and the second electronic device (120) can exchange a private number, a certificate issued from the server (130), and a hash value of a phone number, and update each other's information. Accordingly, when a friend device is searched for during a D2D search, contact information can be updated in the security record as well. For example, the first electronic device (110) and the second electronic device (120) can exchange messages in a format as shown in below.

[0099]

[0100] In operation 525, the first electronic device (110) can identify whether the second electronic device (120) satisfies the conditions for a secure sharing service. According to one embodiment, the first electronic device (110) can identify whether the second electronic device (120) satisfies the conditions for a secure sharing service based on the exchanged information by exchanging information with the second electronic device (120) as in operations 510 and 520. For example, if the second electronic device (120) is an electronic device registered with the server (130), the second electronic device (120) is connected to a network for communication with the server (130), and the system time of the second electronic device (120) is automatically set to a specified standard time, the first electronic device (110) can determine that the second electronic device (120) satisfies the conditions for a secure sharing service.

[0101] In addition, the second electronic device (120) can identify whether the first electronic device (110) satisfies the conditions for a secure sharing service based on the exchanged information by exchanging information with the first electronic device (110) as in operations 510 and 520. For example, if the first electronic device (110) is an electronic device registered with the server (130), the first electronic device (110) is connected to a network for communication with the server (130), and the system time of the first electronic device (110) is automatically set to a specified standard time, the second electronic device (120) can determine that the first electronic device (110) satisfies the conditions for a secure sharing service.

[0102] In one embodiment, operations 515, 520 and 525 may be performed prior to file transfer.

[0103] In operation 530, the first electronic device (110) may encrypt a file. According to one embodiment, the first electronic device (110) may encrypt a file to be transmitted to the second electronic device (120) using a preset encryption key. For example, the first electronic device (110) may encrypt the file using a symmetric key pre-specified by the first electronic device (110) and the second electronic device (120). According to one embodiment, when the second electronic device (120) is selected from the list of searched electronic devices, the first electronic device (110) may encrypt the file to be shared using a symmetric key known to both the first electronic device (110) and the second electronic device (120). According to one embodiment, the encrypted file may be copied to the internal storage for the file sharing application of the first electronic device (110).

[0104] In operation 535, the first electronic device (110) can transmit an encrypted file to the second electronic device (120). The first electronic device (110) can transmit the encrypted file to the second electronic device (120) via short-range communication. The first electronic device (110) can transmit the encrypted file to the second electronic device (120) via D2D communication established between the first electronic device (110) and the second electronic device (120). For example, the first electronic device (110) can transmit the encrypted file to the second electronic device (120) via WiFi communication (e.g., WiFi-Aware or WiFi-Direct).

[0105] In operation 540, the second electronic device (120) can store the encrypted file. The second electronic device (120) can store the received encrypted file in the internal storage for the file sharing application of the second electronic device (120).

[0106] According to one embodiment, by transmitting and receiving encrypted files through D2D communication between a first electronic device (110) and a second electronic device (120), there may not be any files to be shared on an external server, thereby enhancing the security of file sharing between the first electronic device (110) and the second electronic device (120).

[0107] In operation 545, the first electronic device (110) may generate transaction information. According to one embodiment, the first electronic device (110) may generate transaction information including detailed information regarding file sharing. For example, after the first electronic device (110) transmits an encrypted file to the second electronic device (120), the mapping of file information and a unique key required for synchronizing the blockchain ledger may be updated in the first electronic device (110) and the second electronic device (120) so that transaction information including detailed information regarding file sharing can be generated. In this case, the first electronic device (110) providing the file to be shared may set permissions regarding reading, deleting, and modifying the file, and may set a validity period for accessing the file to generate the transaction information.

[0108] For example, information for synchronizing a blockchain ledger can be shared and updated by a first electronic device (110) and a second electronic device (120). For example, the first electronic device (110) can generate a message including a unique number of the first electronic device (110), a sharing expiration date, and file information, and transmit the message to the second electronic device (120). For example, the second electronic device (120) can update information within the second electronic device (120) based on the received message and transmit a response message to the first electronic device (110). For example, the first electronic device (110) and the second electronic device (120) can exchange messages in a format such as . Additionally, for example, the transaction information may include, but is not limited to, at least one of, for example, a unique number of the first electronic device (110), a validity period (or expiration date) of a file to be shared, an identification value of an encrypted file, a secure sharing ID, a mime type of the file, an identification value of a file for decrypting an encrypted file, a file key, a file name, a thumbnail file key, or a thumbnail file name. Additionally, for example, the file key or the thumbnail file key may be generated and managed separately from the transaction information.

[0109] In operation 550, the first electronic device (110) may provide transaction information to the second electronic device (120), and in operation 555, the second electronic device (120) may store the transaction information. According to one embodiment, the first electronic device (110) and the second electronic device (120) may confirm with each other that the transaction information in the first electronic device (110) and the transaction information in the second electronic device (120) are synchronized.

[0110] In operation 560, the first electronic device (110) can identify whether a secure channel exists, and in operation 570, the second electronic device (120) can identify whether a secure channel exists. The first electronic device (110) and the second electronic device (120) can identify whether a secure channel for a secure sharing service via a blockchain network has been created.

[0111] If a secure channel does not exist between the first electronic device (110) and the second electronic device (120), the first electronic device (110) and the second electronic device (120) may create a secure channel in operations 565 and 575. For example, the first electronic device (110) and the second electronic device (120) may create a secure channel as in operations 430 and 435.

[0112] If a secure channel exists between the first electronic device (110) and the second electronic device (120), the first electronic device (110) and the second electronic device (120) can synchronize the blockchain ledgers in operation 580.

[0113] The first electronic device (110) may request synchronization with the blockchain ledger based on the transmitted file information and the information of the second electronic device (120) that received the file, and may send a message to the second electronic device (120). The second electronic device (120) may receive the message from the first electronic device (110), wait until the blockchain ledger is pushed to indicate that synchronization is complete, and transmit a response message to the first electronic device (110) when synchronization of the blockchain ledger is complete. For example, the first electronic device (110) and the second electronic device (120) may exchange messages in the format shown in below.

[0114]

[0115] In one embodiment, a first electronic device (110) and a second electronic device (120) can transmit and receive messages via D2D communication. In this case, messages for synchronizing a blockchain ledger can be directly transmitted and received between the first electronic device (110) and the second electronic device (120) via reliable D2D communication. Accordingly, the blockchain ledger synchronization process can be protected from man-in-the-middle attacks.

[0116] In one embodiment, a blockchain ledger can be synchronized by a first electronic device (110) and a second electronic device (120) sending and receiving messages via a server (130). In this case, messages for synchronizing the blockchain ledger can be sent and received between the first electronic device (110) and the second electronic device (120) via a secure channel.

[0117] According to one embodiment, the transaction information provided to the second electronic device (120) may be validated by the second electronic device (120). Once the transaction information is validated by the second electronic device (120), the first electronic device (110) and the second electronic device (120) may synchronize the blocks containing the transaction information. Each of the first electronic device (110) and the second electronic device (120) may include the blocks containing the transaction information in a blockchain ledger within the blockchain network.

[0118] In one embodiment, if transaction information occurs normally, the transaction information may be data for recording the details of the transaction in a blockchain ledger. For example, the transaction information may include data indicating the history of file transfers between accounts within a blockchain network. A transaction may refer to an act that causes a change in the contents of a blockchain ledger. For example, transaction information that is successfully signed may be recorded in the blockchain ledger, while transaction information that is not successfully signed may not be recorded in the ledger. For example, whether transaction information is recorded in a block by a transaction can be tracked through the transaction ID. For example, transaction information may be recorded in the blockchain ledger using a smart contract.

[0119] In one embodiment, a blockchain ledger may be a chain of data, where each block containing transaction information for at least one transaction references a previous block containing transaction information for another transaction. In one embodiment, at least a portion of the blockchain ledger may be stored on nodes within the blockchain network (e.g., the first electronic device (110) and the second electronic device (120)).

[0120] In one embodiment, after the blockchain ledgers are synchronized, the first electronic device (110) provides a message for terminating a session (Close session message) to the second electronic device (120), and the second electronic device (120) can also provide a message for terminating a session (Close session message) to the first electronic device (110) and request termination of file transfer. Upon receiving a response from the second electronic device (120), the first electronic device (110) can terminate messaging (e.g., custom control messaging). For example, messages exchanged between the first electronic device (110) and the second electronic device (120) for terminating a session can be messages in the format shown in below.

[0121]

[0122] According to one embodiment, the second electronic device (120) can decrypt an encrypted file received from the first electronic device (110) based on information about transaction information and file keys recorded in the blockchain ledger. For example, the second electronic device (120) can identify an encrypted file stored in the second electronic device (120) and a decryption key for the encrypted file based on information about transaction information and file keys, and can decrypt the encrypted file using the decryption key and execute the decrypted file.

[0123] FIG. 6 is a diagram illustrating an example of a first electronic device according to an embodiment of the present disclosure creating a secure channel, transmitting a file to a second electronic device, and synchronizing a blockchain ledger through D2D communication.

[0124] Referring to FIG. 6, a first electronic device (110) can register itself with a server (130) (600). The first electronic device (110) can register information related to the first electronic device (110) with the server (130) through a file sharing application that provides a secure sharing service using blockchain. For example, the first electronic device (110) can register a hash ID, a private number, and a push token with the server (130).

[0125] According to one embodiment, the first electronic device (110) can search for peripheral devices registered with the server (130) (605). The first electronic device (110) can activate the secure sharing function of the file sharing application based on a user input and search for peripheral devices registered with the server (130) that provides or manages the secure sharing service. In addition, the first electronic device (110) can select the second electronic device (120) from among the searched peripheral devices as the electronic device to receive the file.

[0126] In one embodiment, a first electronic device (110) can encrypt a file to be shared (610) and establish a D2D communication connection with a second electronic device (120) (615). The first electronic device (110) can request a D2D communication connection from the second electronic device (120), and the second electronic device (120) can provide the first electronic device (110) with a unique number of the second electronic device (120) registered with the server (130).

[0127] According to one embodiment, when a D2D communication connection is established between a first electronic device (110) and a second electronic device (120), the first electronic device (110) and the second electronic device (120) can create a secure channel for a blockchain through D2D communication (620, 625). The first electronic device (110) can request the second electronic device (120) to create a secure channel and provide a genesis block, and the second electronic device (120) that receives the genesis block can provide a response message to the first electronic device (110). When a secure channel is created between the first electronic device (110) and the second electronic device (120), a channel address of the secure channel can be registered with a server (130) (630). According to one embodiment, the channel address of the secure channel may not be registered with the server (130).

[0128] In one embodiment, a first electronic device (110) can transmit an encrypted file to a second electronic device (120) via D2D communication (635), and the second electronic device (120) can receive the encrypted file and store the received encrypted file (640). For example, the second electronic device (120) can store the encrypted file within a memory allocated to a file sharing application.

[0129] In one embodiment, the first electronic device (110) may record transaction information related to file transfer in a blockchain ledger (645). In this case, the transaction information may be verified by the second electronic device (120), and the blockchain ledger of the first electronic device (110) and the blockchain ledger of the second electronic device (120) may be synchronized with each other.

[0130] In one embodiment, a D2D communication connection between a first electronic device (110) and a second electronic device (120) may be released (650), and file transfer from the first electronic device (110) to the second electronic device (120) may be completed (655). Thereafter, the second electronic device (120) may open the encrypted file using transaction information and a file key included in the blockchain ledger (660).

[0131] FIG. 7 is a diagram illustrating an example in which a first electronic device creates a secure channel through D2D communication, transmits a file to a second electronic device, and synchronizes a blockchain ledger after the D2D communication connection is released, according to one embodiment of the present disclosure.

[0132] Since identification numbers 600 to 635 of FIG. 7 are common to identification numbers 600 to 635 of FIG. 6, their description will be omitted.

[0133] Referring to FIG. 7, the second electronic device (120) can store a file received from the first electronic device (110) (700). For example, the second electronic device (120) can store an encrypted file within memory allocated to a file sharing application.

[0134] In one embodiment, the first electronic device (110) may disconnect the D2D communication connection after transmitting an encrypted file to the second electronic device (120). In one embodiment, after the D2D communication connection is disconnected, the first electronic device (110) may record transaction information related to the file transfer in a blockchain ledger (710). In this case, the first electronic device (110) may transmit and receive information necessary to record the transaction information in the blockchain ledger to and from the second electronic device (120) via the server (130). The first electronic device (110) may transmit and receive data to and from the second electronic device (120) via a secure channel registered with the server (130). The transaction information provided from the first electronic device (110) may be verified by the second electronic device (120), and the blockchain ledger of the first electronic device (110) and the blockchain ledger of the second electronic device (120) may be synchronized with each other. Thereafter, the second electronic device (120) can open the encrypted file using the transaction information and file key included in the blockchain ledger (710).

[0135] FIG. 8 is a diagram illustrating an example of a first electronic device transmitting a file to a second electronic device via D2D communication, and creating a secure channel and synchronizing a blockchain ledger after the D2D communication connection is released, according to one embodiment of the present disclosure.

[0136] Since identification numbers 600 to 615 of FIG. 8 are common to identification numbers 600 to 615 of FIG. 6, their description will be omitted.

[0137] In one embodiment, a first electronic device (110) can transmit an encrypted file to a second electronic device (120) via D2D communication (800), and the second electronic device (120) can receive the encrypted file and store the received encrypted file (805). For example, the second electronic device (120) can store the encrypted file within a memory allocated to a file sharing application.

[0138] According to one embodiment, file transfer from the first electronic device (110) to the second electronic device (120) may be completed and the D2D communication connection between the first electronic device (110) and the second electronic device (120) may be released (810).

[0139] According to one embodiment, a first electronic device (110) and a second electronic device (120) can create a secure channel for a blockchain through a server (130) (815, 820). The first electronic device (110) can request the second electronic device (120) to create a secure channel through the server (130) and provide a genesis block. Upon receiving the genesis block, the second electronic device (120) can provide a response message to the first electronic device (110) through the server (130). When a secure channel is created between the first electronic device (110) and the second electronic device (120), a channel address of the secure channel can be registered with the server (130).

[0140] According to one embodiment, after a secure channel is created, the first electronic device (110) can record transaction information related to file transfer in a blockchain ledger (825). In this case, the first electronic device (110) can transmit and receive information necessary to record the transaction information in the blockchain ledger to and from the second electronic device (120) via the server (130). The first electronic device (110) can transmit and receive data to and from the second electronic device (120) via a secure channel registered with the server (130). The transaction information provided from the first electronic device (110) can be verified by the second electronic device (120), and the blockchain ledger of the first electronic device (110) and the blockchain ledger of the second electronic device (120) can be synchronized with each other. Thereafter, the second electronic device (120) can open the encrypted file using the transaction information and file key included in the blockchain ledger (830).

[0141] FIG. 9 is a drawing showing an example of an execution screen in a general sharing mode of a file sharing application displayed on a screen of a first electronic device according to one embodiment of the present disclosure.

[0142] Referring to FIG. 9, an execution screen of a file sharing application in a general sharing mode may be displayed on the screen of the first electronic device (110). The general sharing mode may be a mode for sharing files without using a blockchain network. The execution screen of the file sharing application in the general sharing mode may include a first area (900) for file sharing with another electronic device of the user of the first electronic device (110), a second area (905) for file sharing with an external electronic device connected via short-range communication, and a third area (910) for file sharing with an external electronic device based on contact information of the first electronic device (110).

[0143] According to one embodiment, when a menu button (915) on the execution screen of a file sharing application in a general sharing mode is selected by a user, the first electronic device (110) may display a GUI (920) for activating a secure file sharing function. For example, the GUI (920) may include an item (925) for activating a secure file sharing function. In addition, when the item (925) is selected by the user, the file sharing application may operate in a secure sharing mode.

[0144] According to one embodiment, when an item (925) is selected by a user, the first electronic device (110) may display a GUI (930) guiding a secure sharing service. The GUI (930) may include a button (935) for registering the first electronic device (110) with the secure sharing service. When the button (935) is selected by the user, the first electronic device (110) may register the first electronic device (110) with a server (130) providing the secure sharing service through predetermined procedures.

[0145] FIG. 10 is a drawing showing an example of an execution screen in a secure sharing mode of a file sharing application displayed on a screen of a first electronic device according to one embodiment of the present disclosure.

[0146] Referring to FIG. 10, an execution screen of a file sharing application in a secure sharing mode may be displayed on the screen of the first electronic device (110). The secure sharing mode may be a mode for sharing files using a blockchain network. The execution screen of the file sharing application in the secure sharing mode may include a fourth area (1000) for settings for secure sharing of files, a fifth area (1005) for file sharing with another electronic device of the user of the first electronic device (110), a sixth area (1010) for file sharing with an external electronic device connected via short-range communication, and a seventh area (1015) for file sharing with an external electronic device based on contact information of the first electronic device (110).

[0147] In this case, unlike the second area (905) and the third area (910) in the general sharing mode, only a list of external electronic devices registered to the server (130) for the secure sharing service may be displayed in the sixth area (1010) and the seventh area (1015). In addition, a list of external electronic devices searched for through short-range communication may be displayed in the sixth area (1010). The list of external electronic devices may include icons and / or text representing profiles of users of the external electronic devices. The first electronic device (110) may select the second electronic device (120) (or the user of the second electronic device (120)) from the list of external electronic devices included in the sixth area (1010) and execute procedures for secure sharing with the second electronic device (120).

[0148] According to one embodiment, within the fourth area (1000) for setting up secure sharing of a file, for example, a button (1020) for releasing secure sharing of a file, a button (1030) for providing a unique number of a first electronic device (110) related to secure sharing, and an object (1040) for setting the validity period of secure sharing of a file may be displayed.

[0149] For example, when a button (1020) to disable secure sharing of a file is selected by a user, a GUI (1025) including an item to disable secure sharing may be displayed.

[0150] For example, when a button (1030) for providing a unique number of the first electronic device (110) is selected, a GUI (1035) may be displayed to display the unique number of the first electronic device (110) registered in the server (130) and enable copying the unique number.

[0151] For example, when an object (1040) for setting the validity period of secure sharing of a file is selected, a GUI (1045) for setting the validity period of secure sharing of the file in detail may be displayed.

[0152] FIG. 11 is a diagram illustrating changes in icons and text corresponding to a second electronic device displayed on a screen of a first electronic device according to a status of a sharing procedure as procedures for secure sharing of files between a first electronic device and a second electronic device are performed according to an embodiment of the present disclosure.

[0153] Referring to FIG. 11, the states of the procedures for secure file sharing between the first electronic device (110) and the second electronic device (120) may include, for example, a waiting state (1100), an encryption state (1105), a connection state (1110), a transmission state (1115), a synchronization state (1120), a transmission completion state (1125), and a failure state (1130).

[0154] In addition, as the status of the procedures for secure sharing of files between the first electronic device (110) and the second electronic device (120) is a standby state (1100), an encryption state (1105), a connection state (1110), a transmission state (1115), a synchronization state (1120), a transmission completion state (1125), and a failure state (1130), the icon and text corresponding to the second electronic device (120) displayed in the sixth area (1010) of FIG. 10 may be changed.

[0155] FIG. 12 is a drawing showing an example of an execution screen of a file sharing application displayed on a screen of a second electronic device as procedures for secure file sharing between a first electronic device and a second electronic device are performed according to an embodiment of the present disclosure.

[0156] Referring to FIG. 12, a second electronic device (120) that has received a request for file sharing from a first electronic device (110) may display a GUI (1205) including a message indicating that the first electronic device (110) wishes to share the file on the screen of the second electronic device (120). When a user input is received for selecting a button (1210) for accepting file sharing within the GUI (1205), the second electronic device (120) may determine whether a network for secure file sharing is activated (1210).

[0157] If the network for secure file sharing is not activated, the second electronic device (120) can display a GUI (1215) that guides activation of the network for secure file sharing.

[0158] If the network for secure file sharing is activated, the second electronic device (120) can determine whether the system time of the second electronic device (120) is set to standard time.

[0159] If the system time of the second electronic device (120) is not set to the standard time, the second electronic device (120) can display a GUI (1220) that guides the user to set the system time to the standard time.

[0160] If the system time of the second electronic device (120) is set to the standard time, the second electronic device (120) can display a GUI (1225) that prepares for secure sharing of a file and display a GUI (1230) that indicates the transmission status of a file transmitted from the first electronic device (110).

[0161] For example, when the transfer of a file from a first electronic device (110) to a second electronic device (120) is completed, the second electronic device (120) may display a GUI (1235) that guides the completion of the file transfer. The GUI (1235) may include a button (1240) for providing a list of files being shared with the first electronic device (110).

[0162] For example, when a user input selecting a button (1240) is received, the second electronic device (120) may display a GUI (1245) including a list of files shared with the first electronic device (110) via a secure sharing service. For example, the GUI (1245) may display the file names of the shared files and the expiration date when the sharing of the files expires.

[0163] One embodiment of the present disclosure may provide an electronic device and method for sharing files, which can create and utilize a blockchain network for file sharing through reliable communication between electronic devices.

[0164] One embodiment of the present disclosure can provide an electronic device and method for sharing files, which can manage files shared between electronic devices connected through short-range communication through a blockchain network.

[0165] One embodiment of the present disclosure may provide an electronic device and method for sharing files between connected electronic devices through reliable D2D communication and for simply creating a channel for a blockchain network.

[0166] According to one embodiment of the present disclosure, a method for sharing a file between a first electronic device and a second electronic device may be provided, including: selecting the second electronic device registered on a server for a secure sharing service (400); identifying whether a network status and a system time setting of the second electronic device satisfy preset criteria for the secure sharing service (415); encrypting the file (420); transmitting the encrypted file to the second electronic device (425); generating a secure channel with the second electronic device for generating a blockchain for the secure sharing service when the preset criteria are satisfied (430); generating transaction information related to the encrypted file transmitted to the second electronic device (440); and recording the generated transaction information in a blockchain ledger of the blockchain through the secure channel (450).

[0167] According to one embodiment of the present disclosure, the blockchain ledger may include information for the second electronic device to decrypt the encrypted file.

[0168] According to one embodiment of the present disclosure, the unique number of the first electronic device registered on the server and the unique number of the second electronic device registered on the server are shared between the first electronic device and the second electronic device, and the operation of selecting the second electronic device may be selecting the second electronic device based on the unique number of the second electronic device.

[0169] According to one embodiment of the present disclosure, the operation of identifying whether the preset criterion is satisfied may include an operation of identifying whether a network function for communication with the server of the second electronic device is activated and a system time of the second electronic device is synchronized with a reference time.

[0170] According to one embodiment of the present disclosure, the method further includes an operation of establishing a communication connection with the second electronic device via a D2D (device to device) communication network; wherein the operation of transmitting the encrypted file may be transmitting the encrypted file to the second electronic device via the D2D communication network.

[0171] According to one embodiment of the present disclosure, the D2D communication network may be different from the network for communication with the server.

[0172] According to one embodiment of the present disclosure, the operation of creating the secure channel may be to create the secure channel for creating the blockchain while communicating with the second electronic device through the D2D communication.

[0173] According to one embodiment of the present disclosure, the operation of creating the secure channel may be to create the secure channel for creating the blockchain after the connection of the D2D communication network between the first electronic device and the second electronic device is released.

[0174] According to one embodiment of the present disclosure, the operation of recording the generated transaction information in the blockchain ledger may record the generated transaction information in the blockchain ledger while the second electronic device is connected to the communication via the D2D communication.

[0175] According to one embodiment of the present disclosure, the operation of recording the generated transaction information in the blockchain ledger may be to record the generated transaction information in the blockchain ledger after the D2D communication connection between the first electronic device and the second electronic device is released.

[0176] According to one embodiment of the present disclosure, the transaction information may include at least one of the identification values ​​of the transmission time, the expiration time of sharing the file, the link address of the encrypted content, or a decryption key for decrypting the encrypted content.

[0177] According to one embodiment, a file is transmitted between a first electronic device (110) and a second electronic device (120) through reliable D2D communication, thereby allowing only the first electronic device (110) and the second electronic device (120) sharing the file to view the file. Furthermore, according to one embodiment, after the file is transmitted, the first electronic device (110), which is the original owner of the file, can control the permissions of the file. Furthermore, by utilizing blockchain technology, the shared file can be encrypted and recorded in the blockchain ledger, thereby preventing hackers from arbitrarily manipulating or accessing the blockchain ledger. Furthermore, the owner of the file can safely share the file, and all users participating in the secure channel can have the same ledger contents. Furthermore, since the permissions for the shared file are created by the owner of the file, the person who has shared the file cannot arbitrarily change the permissions of the file or reshare the file with others.

[0178]

[0179] FIG. 13 is a block diagram of an electronic device (1301) within a network environment (1300) according to various embodiments. Referring to FIG. 13 , in the network environment (1300), the electronic device (1301) may communicate with the electronic device (1302) via a first network (1398) (e.g., a short-range wireless communication network), or may communicate with the electronic device (1304) or a server (1308) via a second network (1399) (e.g., a long-range wireless communication network). In one embodiment, the electronic device (1301) may communicate with the electronic device (1304) via the server (1308). According to one embodiment, the electronic device (1301) may include a processor (1320), a memory (1330), an input module (1350), an audio output module (1355), a display module (1360), an audio module (1370), a sensor module (1376), an interface (1377), a connection terminal (1378), a haptic module (1379), a camera module (1380), a power management module (1388), a battery (1389), a communication module (1390), a subscriber identification module (1396), or an antenna module (1397). In some embodiments, the electronic device (1301) may omit at least one of these components (e.g., the connection terminal (1378)), or may have one or more other components added. In some embodiments, some of these components (e.g., sensor module (1376), camera module (1380), or antenna module (1397)) may be integrated into a single component (e.g., display module (1360)).

[0180] The processor (1320) may, for example, execute software (e.g., a program (1340)) to control at least one other component (e.g., a hardware or software component) of the electronic device (1301) connected to the processor (1320) and perform various data processing or operations. According to one embodiment, as at least a part of the data processing or operations, the processor (1320) may store commands or data received from other components (e.g., a sensor module (1376) or a communication module (1390)) in a volatile memory (1332), process the commands or data stored in the volatile memory (1332), and store result data in a non-volatile memory (1334). According to one embodiment, the processor (1320) may include a main processor (1321) (e.g., a central processing unit or an application processor) or an auxiliary processor (1323) (e.g., a graphics processing unit, a neural processing unit (NPU), an image signal processor, a sensor hub processor, or a communication processor) that can operate independently or together with the main processor (1321). For example, when the electronic device (1301) includes the main processor (1321) and the auxiliary processor (1323), the auxiliary processor (1323) may be configured to use less power than the main processor (1321) or to be specialized for a given function. The auxiliary processor (1323) may be implemented separately from the main processor (1321) or as a part thereof.

[0181] The auxiliary processor (1323) may control at least a portion of functions or states associated with at least one component (e.g., the display module (1360), the sensor module (1376), or the communication module (1390)) of the electronic device (1301), for example, on behalf of the main processor (1321) while the main processor (1321) is in an inactive (e.g., sleep) state, or together with the main processor (1321) while the main processor (1321) is in an active (e.g., application execution) state. In one embodiment, the auxiliary processor (1323) (e.g., an image signal processor or a communication processor) may be implemented as a part of another functionally related component (e.g., a camera module (1380) or a communication module (1390)). In one embodiment, the auxiliary processor (1323) (e.g., a neural network processing unit) may include a hardware structure specialized for processing artificial intelligence models. The artificial intelligence models may be generated through machine learning. This learning can be performed, for example, on the electronic device (1301) where the artificial intelligence is performed, or can be performed through a separate server (e.g., server (1308)). The learning algorithm can include, for example, supervised learning, unsupervised learning, semi-supervised learning, or reinforcement learning, but is not limited to the examples described above. The artificial intelligence model can include multiple artificial neural network layers.The artificial neural network may be one of a deep neural network (DNN), a convolutional neural network (CNN), a recurrent neural network (RNN), a restricted Boltzmann machine (RBM), a deep belief network (DBN), a bidirectional recurrent deep neural network (BRDNN), a deep Q-network, or a combination of two or more of the above, but is not limited to the examples described above. In addition to, or alternatively to, a hardware structure, an artificial intelligence model may include a software structure.

[0182] The memory (1330) can store various data used by at least one component (e.g., the processor (1320) or the sensor module (1376)) of the electronic device (1301). The data can include, for example, software (e.g., the program (1340)) and input data or output data for commands related thereto. The memory (1330) can include volatile memory (1332) or non-volatile memory (1334).

[0183] The program (1340) may be stored as software in memory (1330) and may include, for example, an operating system (1342), middleware (1344), or an application (1346).

[0184] The input module (1350) can receive commands or data to be used in a component of the electronic device (1301) (e.g., a processor (1320)) from an external source (e.g., a user) of the electronic device (1301). The input module (1350) can include, for example, a microphone, a mouse, a keyboard, a key (e.g., a button), or a digital pen (e.g., a stylus pen).

[0185] The audio output module (1355) can output audio signals to the outside of the electronic device (1301). The audio output module (1355) can include, for example, a speaker or a receiver. The speaker can be used for general purposes, such as multimedia playback or recording playback. The receiver can be used to receive incoming calls. In one embodiment, the receiver can be implemented separately from the speaker or as part of the speaker.

[0186] The display module (1360) can visually provide information to an external party (e.g., a user) of the electronic device (1301). The display module (1360) may include, for example, a display, a holographic device, or a projector and a control circuit for controlling the device. In one embodiment, the display module (1360) may include a touch sensor configured to detect a touch, or a pressure sensor configured to measure the intensity of a force generated by the touch.

[0187] The audio module (1370) can convert sound into an electrical signal, or vice versa. According to one embodiment, the audio module (1370) can acquire sound through the input module (1350), output sound through the sound output module (1355), or an external electronic device (e.g., electronic device (1302)) (e.g., speaker or headphone) directly or wirelessly connected to the electronic device (1301).

[0188] The sensor module (1376) can detect the operating status (e.g., power or temperature) of the electronic device (1301) or the external environmental status (e.g., user status) and generate an electrical signal or data value corresponding to the detected status. According to one embodiment, the sensor module (1376) can include, for example, a gesture sensor, a gyro sensor, a barometric pressure sensor, a magnetic sensor, an acceleration sensor, a grip sensor, a proximity sensor, a color sensor, an IR (infrared) sensor, a biometric sensor, a temperature sensor, a humidity sensor, or an illuminance sensor.

[0189] The interface (1377) may support one or more designated protocols that may be used to directly or wirelessly connect the electronic device (1301) with an external electronic device (e.g., the electronic device (1302)). In one embodiment, the interface (1377) may include, for example, a high definition multimedia interface (HDMI), a universal serial bus (USB) interface, an SD card interface, or an audio interface.

[0190] The connection terminal (1378) may include a connector through which the electronic device (1301) may be physically connected to an external electronic device (e.g., the electronic device (1302)). In one embodiment, the connection terminal (1378) may include, for example, an HDMI connector, a USB connector, an SD card connector, or an audio connector (e.g., a headphone connector).

[0191] The haptic module (1379) can convert electrical signals into mechanical stimuli (e.g., vibration or movement) or electrical stimuli that a user can perceive through tactile or kinesthetic sensations. In one embodiment, the haptic module (1379) may include, for example, a motor, a piezoelectric element, or an electrical stimulation device.

[0192] The camera module (1380) can capture still images and videos. In one embodiment, the camera module (1380) may include one or more lenses, image sensors, image signal processors, or flashes.

[0193] The power management module (1388) can manage the power supplied to the electronic device (1301). According to one embodiment, the power management module (1388) can be implemented as, for example, at least a part of a power management integrated circuit (PMIC).

[0194] A battery (1389) may power at least one component of the electronic device (1301). In one embodiment, the battery (1389) may include, for example, a non-rechargeable primary battery, a rechargeable secondary battery, or a fuel cell.

[0195] The communication module (1390) may support the establishment of a direct (e.g., wired) communication channel or a wireless communication channel between the electronic device (1301) and an external electronic device (e.g., electronic device (1302), electronic device (1304), or server (1308)), and the performance of communication through the established communication channel. The communication module (1390) may operate independently from the processor (1320) (e.g., 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 (1390) may include a wireless communication module (1392) (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 (1394) (e.g., a local area network (LAN) communication module, or a power line communication module). Any of these communication modules may communicate with an external electronic device (1304) via a first network (1398) (e.g., a short-range communication network such as Bluetooth, wireless fidelity (WiFi) direct, or infrared data association (IrDA)) or a second network (1399) (e.g., a long-range communication network such as a legacy cellular network, a 5G network, a next-generation communication network, the Internet, or a computer network (e.g., a local area network or a wide area network)). These various types of communication modules may be integrated into a single component (e.g., a single chip) or implemented as multiple separate components (e.g., multiple chips). The wireless communication module (1392) may use subscriber information (e.g., an international mobile subscriber identity (IMSI)) stored in the subscriber identification module (1396) to verify or authenticate the electronic device (1301) within a communication network such as the first network (1398) or the second network (1399).

[0196] The wireless communication module (1392) can support 5G networks and next-generation communication technologies following the 4G network, such as NR access technology (new radio access technology). The NR access technology can support high-speed transmission of high-capacity data (eMBB (enhanced mobile broadband)), minimization of terminal power and connection of multiple terminals (mMTC (massive machine type communications)), or high reliability and low latency communications (URLLC (ultra-reliable and low-latency communications)). The wireless communication module (1392) can support, for example, a high-frequency band (e.g., mmWave band) to achieve a high data transmission rate. The wireless communication module (1392) may support various technologies for securing performance in high-frequency bands, such as beamforming, massive multiple-input and multiple-output (MIMO), full dimensional MIMO (FD-MIMO), array antenna, analog beam-forming, or large scale antenna. The wireless communication module (1392) may support various requirements specified in the electronic device (1301), an external electronic device (e.g., the electronic device (1304)), or a network system (e.g., the second network (1399)). According to one embodiment, the wireless communication module (1392) may support a peak data rate (e.g., 20 Gbps or more) for eMBB implementation, a loss coverage (e.g., 164 dB or less) for mMTC implementation, or a U-plane latency (e.g., 0.5 ms or less for downlink (DL) and uplink (UL), or 1 ms or less for round trip) for URLLC implementation.

[0197] The antenna module (1397) can transmit or receive signals or power to or from an external device (e.g., an external electronic device). In one embodiment, the antenna module (1397) may include an antenna including a radiator formed of a conductor or a conductive pattern formed on a substrate (e.g., a PCB). In one embodiment, the antenna module (1397) may include a plurality of antennas (e.g., 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 (1398) or the second network (1399), may be selected from the plurality of antennas by, for example, the communication module (1390). A signal or power may be transmitted or received between the communication module (1390) and an external electronic device via the at least one selected antenna. In some embodiments, in addition to the radiator, another component (e.g., a radio frequency integrated circuit (RFIC)) may be additionally formed as a part of the antenna module (1397).

[0198] According to various embodiments, the antenna module (1397) may form a mmWave antenna module. In one embodiment, the mmWave antenna module may include a printed circuit board, an RFIC disposed on or adjacent a first side (e.g., a bottom side) of the printed circuit board and capable of supporting a designated high frequency band (e.g., a mmWave band), and a plurality of antennas (e.g., an array antenna) disposed on or adjacent a second side (e.g., a top side or a side side) of the printed circuit board and capable of transmitting or receiving signals in the designated high frequency band.

[0199] At least some of the above components can be interconnected and exchange signals (e.g., commands or data) with each other via a communication method between peripheral devices (e.g., a bus, GPIO (general purpose input and output), SPI (serial peripheral interface), or MIPI (mobile industry processor interface)).

[0200] According to one embodiment, commands or data may be transmitted or received between the electronic device (1301) and an external electronic device (1304) via a server (1308) connected to a second network (1399). Each of the external electronic devices (1302 or 1304) may be the same or a different type of device as the electronic device (1301). According to one embodiment, all or part of the operations executed in the electronic device (1301) may be executed in one or more of the external electronic devices (1302, 1304, or 1308). For example, when the electronic device (1301) is to perform a certain function or service automatically or in response to a request from a user or another device, the electronic device (1301) may, instead of or in addition to executing the function or service itself, request one or more external electronic devices to perform the function or at least a part of the service. One or more external electronic devices that receive the request may execute at least a portion 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 (1301). The electronic device (1301) may process the result as is or additionally and provide it as at least a portion of a response to the request. For this purpose, cloud computing, distributed computing, mobile edge computing (MEC), or client-server computing technology may be used, for example. The electronic device (1301) may provide an ultra-low latency service by using distributed computing or mobile edge computing, for example. In another embodiment, the external electronic device (1304) may include an Internet of Things (IoT) device. The server (1308) may be an intelligent server utilizing machine learning and / or a neural network.According to one embodiment, an external electronic device (1304) or server (1308) may be included within the second network (1399). The electronic device (1301) may be applied to intelligent services (e.g., smart homes, smart cities, smart cars, or healthcare) based on 5G communication technology and IoT-related technology.

[0201] According to one embodiment, the electronic device (1301) of FIG. 13 may correspond to the first electronic device (110) or the second electronic device (120). When the electronic device (1301) of FIG. 13 corresponds to the first electronic device (110), the electronic device (1301) may perform the operations of the first electronic device (110) of FIGS. 1 to 12. When the electronic device (1301) of FIG. 13 corresponds to the second electronic device (120), the electronic device (1301) may perform the operations of the second electronic device (120) of FIGS. 1 to 12.

[0202] According to one embodiment, a first communication interface (112-1, 1390); a second communication interface (112-2, 1390); a memory (111, 1330) for storing commands; A first electronic device (110, 1301) comprising: a processor (113, 1320) operatively connected to the first communication interface, the second communication interface, and the memory; wherein the instructions, when executed by the processor, cause the first electronic device to: select the second electronic device registered with a server (130) for a secure sharing service, identify whether a network status and a system time setting of the second electronic device (120) satisfy preset criteria for the secure sharing service, encrypt the file, transmit the encrypted file to the second electronic device, and, when the preset criteria are satisfied, create a secure channel with the second electronic device for creating a blockchain for the secure sharing service, create transaction information related to the encrypted file transmitted to the second electronic device, and record the created transaction information in a blockchain ledger of the blockchain through the secure channel.

[0203] In one embodiment, the blockchain ledger may include information for the second electronic device to decrypt the encrypted file.

[0204] According to one embodiment, a unique number of the first electronic device registered with the server and a unique number of the second electronic device registered with the server are shared between the first electronic device and the second electronic device, and the commands, when executed by the processor, can cause the first electronic device to select the second electronic device based on the unique number of the second electronic device.

[0205] According to one embodiment, the second electronic device may include an operation for identifying whether a network function for communication with the server is activated and whether a system time of the second electronic device is synchronized to a reference time.

[0206] According to one embodiment, the second electronic device may be connected to the communication network through a D2D (device to device) communication network, and the encrypted file may be transmitted to the second electronic device through the D2D communication network.

[0207] In one embodiment, the D2D communication network may be different from the network for communication with the server.

[0208] According to one embodiment, the instructions, when executed by the processor, may cause the first electronic device to create a secure channel for generating the blockchain while in communication with the second electronic device via the D2D communication.

[0209] According to one embodiment, the instructions, when executed by the processor, may cause the first electronic device to create a secure channel for generating the blockchain after the D2D communication connection between the first electronic device and the second electronic device is disconnected.

[0210] According to one embodiment, the instructions, when executed by the processor, may cause the first electronic device to record the generated transaction information in the blockchain ledger while in communication with the second electronic device via the D2D communication.

[0211] According to one embodiment, the instructions, when executed by the processor, may cause the first electronic device to record the generated transaction information in the blockchain ledger after the D2D communication connection between the first electronic device and the second electronic device is disconnected.

[0212] According to one embodiment, the transaction information may include at least one of the following identifying values: the transmission time, the expiration time of sharing the file, the link address of the encrypted content, or a decryption key for decrypting the encrypted content.

[0213] Electronic devices according to the various embodiments disclosed in this document may take various forms. Electronic devices may include, for example, portable communication devices (e.g., smartphones), computer devices, portable multimedia devices, portable medical devices, cameras, wearable devices, or home appliances. Electronic devices according to the embodiments of this document are not limited to the aforementioned devices.

[0214] The various embodiments of this document and the terminology used therein are not intended to limit the technical features described in this document to specific embodiments, but should be understood to include various modifications, equivalents, or substitutes of the embodiments. In connection with the description of the drawings, similar reference numerals 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 items, unless the context clearly indicates otherwise. In this document, each of the phrases "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 "at least one of A, B, or C" can include any one of the items listed together in the corresponding phrase among those phrases, or all possible combinations thereof. Terms such as "first," "second," or "first" or "second" may be used merely to distinguish one component from another, and do not limit the components in any other respect (e.g., importance or order). When a component (e.g., a first component) is referred to as "coupled" or "connected" to another (e.g., a second component), with or without the terms "functionally" or "communicatively," it means that the component can be connected to the other component directly (e.g., wired), wirelessly, or through a third component.

[0215] The term "module" used in various embodiments of this document may include a unit implemented in hardware, software, or firmware, and may be used interchangeably with terms such as logic, logic block, component, or circuit. A module may be an integral component, or a minimum unit or part of such a component that performs one or more functions. For example, according to one embodiment, a module may be implemented in the form of an application-specific integrated circuit (ASIC).

[0216] Various embodiments of the present document may be implemented as software (e.g., a program (1340)) including one or more instructions stored in a storage medium (e.g., an internal memory (1336) or an external memory (1338)) readable by a machine (e.g., an electronic device (1301)). For example, a processor (e.g., a processor (1320)) of the machine (e.g., an electronic device (1301)) may call at least one instruction among the one or more instructions stored from the storage medium and execute it. This enables the machine to operate to perform at least one function according to the at least one called instruction. The one or more instructions may include code generated by a compiler or code executable by an interpreter. The machine-readable storage medium may be provided in the form of a non-transitory storage medium. Here, 'non-transitory' simply means that the storage medium is a tangible device and does not contain signals (e.g., electromagnetic waves), and the term does not distinguish between cases where data is stored semi-permanently or temporarily on the storage medium.

[0217] According to one embodiment, the method according to various embodiments disclosed in this document may be provided as a computer program product. The computer program product may be traded between sellers and buyers as a product. The computer program product may be distributed in the form of a device-readable storage medium (e.g., compact disc read-only memory (CD-ROM)) or may be provided through an application store (e.g., Play Store). TM ) or directly between two user devices (e.g., smart phones), online distribution (e.g., downloading or uploading). 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 an intermediary server.

[0218] According to various embodiments, each component (e.g., a module or a program) of the above-described components may include one or more entities, and some of the entities may be separated and placed in other components. According to various embodiments, one or more components or operations of the aforementioned components may be omitted, or one or more other components or operations may be added. Alternatively or additionally, a plurality of components (e.g., a module or a program) may be integrated into a single component. In such a case, the integrated component may perform one or more functions of each of the plurality of components identically or similarly to those performed by the corresponding component among the plurality of components prior to the integration. According to various embodiments, the 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 one or more other operations may be added.

Claims

1. A method for a first electronic device to share a file with a second electronic device, An action (400) to select the second electronic device registered on the server for a security sharing service; An operation (415) for identifying whether the network status and system time settings of the second electronic device satisfy preset criteria for the secure sharing service; Action of encrypting the above file (420); An action (425) of transmitting the encrypted file to the second electronic device; An operation (430) of creating a secure channel with the second electronic device for creating a blockchain for the secure sharing service, upon satisfaction of the above preset criteria; An operation (440) of generating transaction information related to an encrypted file transmitted to the second electronic device; and An operation (450) of recording the generated transaction information in the blockchain ledger of the blockchain through the above security channel; Including, A method wherein the blockchain ledger includes information for the second electronic device to decrypt the encrypted file.

2. In paragraph 1, The unique number of the first electronic device registered on the server and the unique number of the second electronic device registered on the server are shared between the first electronic device and the second electronic device, A method wherein the action of selecting the second electronic device selects the second electronic device based on the unique number of the second electronic device.

3. In either of paragraphs 1 and 2, A method according to claim 1, wherein the operation of identifying whether the above-described preset criterion is satisfied includes an operation of identifying whether a network function of the second electronic device for communication with the server is activated and whether the system time of the second electronic device is synchronized with a reference time.

4. In any one of clauses 1 to 3, An operation of communicating with the second electronic device through a D2D (device to device) communication network; Including more, The action of transmitting the above encrypted file is: A method for transmitting the encrypted file to the second electronic device through the D2D communication network.

5. In paragraph 4, A method wherein the above D2D communication network is different from the network for communication with the server.

6. In paragraph 4, The action of creating the above secure channel is: A method for creating a secure channel for generating the blockchain while communicating with the second electronic device through the D2D communication.

7. In paragraph 4, The action of creating the above secure channel is: A method for creating a secure channel for generating the blockchain after the connection of the D2D communication network between the first electronic device and the second electronic device is disconnected.

8. In paragraph 4, The action of recording the generated transaction information in the blockchain ledger is as follows: A method of recording the generated transaction information in the blockchain ledger while communicating with the second electronic device through the D2D communication.

9. In paragraph 4, The action of recording the generated transaction information in the blockchain ledger is as follows: A method of recording the generated transaction information in the blockchain ledger after the D2D communication between the first electronic device and the second electronic device is disconnected.

10. In any one of paragraphs 1 to 3, The above transaction information is, A method comprising at least one of the identification values: the transmission time, the expiration time of sharing the file, the link address of the encrypted content, or a decryption key for decrypting the encrypted content.

11. In the first electronic device (110, 1301), First communication interface (112-1, 1390); Second communication interface (112-2, 1390); Memory for storing commands (111, 1330); Processor (113, 1320); Including, The above instructions, when executed by the processor, cause the first electronic device to: Select the second electronic device registered to the server (130) for the security sharing service, Identify whether the network status and system time settings of the second electronic device (120) satisfy the preset criteria for the security sharing service, Encrypt the above file, Transmitting the encrypted file to the second electronic device; When the above preset criteria are satisfied, a secure channel for creating a blockchain for the secure sharing service is created with the second electronic device, Generate transaction information related to the encrypted file transmitted to the second electronic device; The generated transaction information is recorded in the blockchain ledger of the blockchain through the above security channel, A first electronic device, wherein the blockchain ledger comprises information for the second electronic device to decrypt the encrypted file.

12. In paragraph 11, The unique number of the first electronic device registered on the server and the unique number of the second electronic device registered on the server are shared between the first electronic device and the second electronic device, The above instructions, when executed by the processor, cause the first electronic device to select the second electronic device based on the unique number of the second electronic device; A first electronic device, wherein the transaction information includes at least one of the identification values: the transmission time, the expiration time of sharing the file, the link address of the encrypted content, or a decryption key for decrypting the encrypted content.

13. In any one of paragraphs 11 and 12, The above instructions, when executed by the processor, cause the first electronic device to: A first electronic device, wherein the second electronic device includes an operation for identifying whether a network function for communication with the server is activated and whether the system time of the second electronic device is synchronized to a reference time.

14. In any one of paragraphs 11 to 13, The above instructions, when executed by the processor, cause the first electronic device to: Communicates with the second electronic device through a D2D (device to device) communication network, A first electronic device that transmits the encrypted file to the second electronic device through the D2D communication network.

15. In paragraph 14, A first electronic device wherein the D2D communication network is different from a network for communication with the server, and the processor creates a secure channel for generating the blockchain while connected to the second electronic device through the D2D communication by executing the commands.

Images