Electronic device and method for receiving push messages stored in blockchain

By using encrypted push keys and blockchain networks in electronic devices, the security problem of distributing and storing user personal information in multiple servers is solved, and the secure distribution and storage of information is realized, avoiding the risk of centralization of information.

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

Patent Information

Application Number
CN202080036169.6
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2019-05-13
Filing Date
2020-05-13
Publication Date
2024-11-26
Estimated Expiration
2040-05-13

AI Technical Summary

Technical Problem

There is a need for a scheme to distribute and store user personal information in multiple servers without the need to concentrate personal information.

Method used

Through electronic devices, a communication circuit is used to request the management server to encrypt the push key received from the push server, and the encrypted push key is sent to the blockchain network, and transactions are generated based on smart contracts, push messages are stored and managed to ensure information Distribute and store across multiple servers.

Benefits of technology

The security and privacy of distributing and storing user personal information in multiple servers is realized, and the risk of information centralization is avoided.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN113826137B_ABST
    Figure CN113826137B_ABST
Patent Text Reader

Abstract

An electronic device is provided. The electronic device includes: a communication circuit configured to communicate; at least one processor operably connected to the communication circuit; and a memory operably connected to the at least one processor, wherein the memory may store instructions that, when executed, cause the at least one processor to perform the following operations: using the communication circuit to request a management server to encrypt a push key received from a push server, in response to the request, receiving the encrypted push key from the management server, generating at least one transaction based on the encrypted push key, and sending the transaction to a blockchain network.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates to an electronic device and method for receiving a push message stored in a blockchain. Background Art

[0002] The electronic device may sign a contract with an external electronic device to agree to receive push messages, and record the contract content in the blockchain. If the conditions based on the contract are met, the electronic device may receive a push message according to the contract content recorded in the blockchain from the external electronic device.

[0003] The blockchain network can be referred to as a distributed computing device that records cryptocurrency transactions. The blockchain network can record transactions including program codes (hereinafter referred to as smart contracts) in blocks to execute contracts between contracting parties.

[0004] The technical objectives that the present disclosure intends to achieve are not limited to the above-mentioned technical objectives, and other technical objectives that are not mentioned may be clearly understood by those skilled in the art in the technical field of the present disclosure through the following description.

[0005] The above information is presented as background information only to assist with an understanding of the present disclosure. No determination has been made, and no assertion is made, as to whether any of the above might be applicable as prior art with respect to the present disclosure. Summary of the invention

[0006] Technical issues

[0007] A solution is needed for distributing and storing a user's personal information in multiple servers without centralizing the personal information.

[0008] Solution to the problem

[0009] Aspects of the present disclosure are to at least address the above-mentioned problems and / or disadvantages and to provide at least the advantages described below. Therefore, one aspect of the present disclosure is to provide an apparatus and method for receiving a push message stored in a blockchain.

[0010] Additional aspects will be set forth in part in the description which follows and, in part, will be obvious from the description, or may be learned by practice of the presented embodiments.

[0011] According to one aspect of the present disclosure, an electronic device is provided. The electronic device includes: a communication circuit configured to communicate; at least one processor operably connected to the communication circuit; and a memory operably connected to the at least one processor, wherein the memory may store instructions that, when executed, cause the at least one processor to perform the following operations: using the communication circuit to request a management server to encrypt a push key received from a push server, in response to the request, receiving the encrypted push key from the management server, generating at least one transaction based on the encrypted push key, and sending the transaction to a blockchain network.

[0012] According to another aspect of the present disclosure, an electronic device is provided. The electronic device includes: a communication circuit configured to communicate; at least one processor operably connected to the communication circuit; and a memory operably connected to the at least one processor, wherein the memory stores instructions that, when executed, cause the at least one processor to perform the following operations: using the communication circuit to request a management server to encrypt a push key received from a push server, receiving the encrypted push key from the management server in response to the request, and receiving a push message associated with a push event based on a smart contract from the management server via the push server.

[0013] According to another aspect of the present disclosure, an electronic device is provided. The electronic device includes: a communication circuit configured to communicate; at least one processor operably connected to the communication circuit; and a memory operably connected to the at least one processor, wherein the memory stores instructions that, when executed, cause the at least one processor to perform the following operations: using the communication circuit to identify a push event related to a smart contract recorded in at least one block managed by a blockchain network, decrypting at least one push key related to the push event, and using a push server to send the decrypted at least one push key and a push message to at least one external electronic device corresponding to the decrypted at least one push key.

[0014] According to another aspect of the present disclosure, a computer-readable recording medium records a program, wherein the program is used to perform the following operations: recording an address of at least one external electronic device and an encrypted push key for the at least one external electronic device in a block of a blockchain network; recording a push event in a block of the blockchain network, wherein the push event includes the address of the at least one external electronic device, the address of a smart contract, and a push message; recording the push event in the block, and then receiving a sending request for the encrypted push key corresponding to the address of a first external electronic device from a management server; and in response to receiving the sending request for the encrypted push key, sending the encrypted push key corresponding to the address of the first external electronic device to the management server.

[0015] Other aspects, advantages, and salient features of the present disclosure will become apparent to those skilled in the art from the following detailed description, which, taken in conjunction with the accompanying drawings, discloses various embodiments of the present disclosure.

[0016] Beneficial Effects of the Invention

[0017] As described above, the electronic device and method according to the embodiment may distribute and store the user's personal information in a plurality of servers without centralizing the personal information. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] The above and other aspects, features and advantages of certain embodiments of the present disclosure will become more apparent through the following description in conjunction with the accompanying drawings, in which:

[0019] Figure 1 A block diagram showing an electronic device in a network environment according to an embodiment of the present disclosure;

[0020] Figure 2A Showing a network environment according to an embodiment of the present disclosure;

[0021] Figure 2B showing data according to an embodiment of the present disclosure;

[0022] Figure 3 A flowchart showing the operation of an electronic device according to an embodiment of the present disclosure;

[0023] Figure 4 A flowchart showing the operation of an electronic device according to an embodiment of the present disclosure;

[0024] Figure 5 a flowchart showing the operation of the electronic device according to an embodiment of the present disclosure; and

[0025] Figure 6 A flowchart illustrating the operation of an electronic device according to an embodiment of the present disclosure.

[0026] Throughout the drawings, like reference numerals will be understood to refer to like parts, components and structures. DETAILED DESCRIPTION

[0027] The following description with reference to the accompanying drawings is provided to assist in a comprehensive understanding of the various embodiments of the present disclosure as defined by the claims and their equivalents. The following description includes various specific details to assist in understanding, but these details are considered to be exemplary only. Therefore, it will be appreciated by those of ordinary skill in the art that various changes and modifications may be made to the various embodiments described herein without departing from the scope and spirit of the present disclosure. In addition, descriptions of well-known functions and structures may be omitted for clarity and conciseness.

[0028] The terms and words used in the following description and claims are not limited to the bibliographical meanings, but are merely used by the inventor to enable a clear and consistent understanding of the present disclosure. Therefore, it will be apparent to those skilled in the art that the following description of various embodiments of the present disclosure is provided for illustrative purposes only and not for the purpose of limiting the present disclosure as defined by the appended claims and their equivalents.

[0029] It should be understood that the singular forms "a," "an," and "the" include plural referents unless the context clearly dictates otherwise. Thus, for example, reference to "a component surface" includes reference to one or more of such surfaces.

[0030] Figure 1 is a block diagram illustrating electronic devices in a network environment according to an embodiment of the present disclosure.

[0031] Reference Figure 1, the electronic device 101 in the network environment 100 may communicate with the electronic device 102 via the first network 198 (e.g., a short-range wireless communication network), or communicate with the electronic device 104 or the server 108 via the second network 199 (e.g., a long-range wireless communication network). According to an embodiment of the present disclosure, the electronic device 101 may communicate with the electronic device 104 via the server 108. According to an embodiment of the present disclosure, the electronic device 101 may include a processor 120, a memory 130, an input device 150, a sound output device 155, a display device 160, an audio module 170, a sensor module 176, an interface 177, a haptic module 179, a camera module 180, a power management module 188, a battery 189, a communication module 190, a user identification module (SIM) 196, or an antenna module 197. In some embodiments of the present disclosure, at least one of the components (e.g., display device 160 or camera module 180) may be omitted from electronic device 101, or one or more other components may be added to electronic device 101. In embodiments of the present disclosure, some of the components may be implemented as a single integrated circuit. For example, sensor module 176 (e.g., fingerprint sensor, iris sensor, or illumination sensor) may be implemented as embedded in display device 160 (e.g., display).

[0032] The processor 120 may run, for example, software (e.g., program 140) to control at least one other component (e.g., hardware component or software component) of the electronic device 101 that is combined with the processor 120, and may perform various data processing or calculations. According to an embodiment of the present disclosure, as at least part of the data processing or calculation, the processor 120 may load a command or data received from another component (e.g., sensor module 176 or communication module 190) into a volatile memory 132, process the command or data stored in the volatile memory 132, and store the result data in a non-volatile memory 134. According to an embodiment of the present disclosure, the processor 120 may include a main processor 121 (e.g., a central processing unit (CPU) or an application processor (AP)) and an auxiliary processor 123 (e.g., a graphics processing unit (GPU), an image signal processor (ISP), a sensor hub processor, or a communication processor (CP)) that is operationally independent or combined with the main processor 121. Additionally or alternatively, the auxiliary processor 123 may be adapted to consume less power than the main processor 121, or adapted to be specifically used for a specified function. The auxiliary processor 123 may be implemented separately from the main processor 121, or implemented as part of the main processor 121.

[0033] When the main processor 121 is in an inactive (e.g., sleep) state, the auxiliary processor 123 (rather than the main processor 121) may control at least some of the functions or states related to at least one component (e.g., display device 160, sensor module 176, or communication module 190) among the components of the electronic device 101, or when the main processor 121 is in an active state (e.g., running an application), the auxiliary processor 123 may control at least some of the functions or states related to at least one component (e.g., display device 160, sensor module 176, or communication module 190) among the components of the electronic device 101 together with the main processor 121. According to an embodiment of the present disclosure, the auxiliary processor 123 (e.g., an image signal processor or a communication processor) may be implemented as part of another component (e.g., camera module 180 or communication module 190) that is functionally related to the auxiliary processor 123.

[0034] The memory 130 may store various data used by at least one component of the electronic device 101 (e.g., the processor 120 or the sensor module 176). The various data may include, for example, software (e.g., the program 140) and input data or output data for commands related thereto. The memory 130 may include a volatile memory 132 or a nonvolatile memory 134.

[0035] The program 140 may be stored as software in the memory 130 , and may include, for example, an operating system (OS) 142 , middleware 144 , or applications 146 .

[0036] The input device 150 may receive commands or data from outside the electronic device 101 (e.g., a user) to be used by other components of the electronic device 101 (e.g., the processor 120). The input device 150 may include, for example, a microphone, a mouse, a keyboard, or a digital pen (e.g., a stylus).

[0037] The sound output device 155 can output a sound signal to the outside of the electronic device 101. The sound output device 155 may include, for example, a speaker or a receiver. The speaker can be used for general purposes such as playing multimedia or playing records, and the receiver can be used for incoming calls. According to an embodiment of the present disclosure, the receiver can be implemented as a separate part from the speaker, or as a part of the speaker.

[0038] The display device 160 may visually provide information to the outside of the electronic device 101 (e.g., a user). The display device 160 may include, for example, a display, a holographic device, or a projector, and a control circuit for controlling a corresponding one of the display, the holographic device, and the projector. According to an embodiment of the present disclosure, the display device 160 may include a touch circuit adapted to detect a touch or a sensor circuit (e.g., a pressure sensor) adapted to measure the strength of a force caused by a touch.

[0039] The audio module 170 can convert sound into an electrical signal, or vice versa. According to an embodiment of the present disclosure, the audio module 170 can obtain sound via the input device 150, or output sound via the sound output device 155 or an earphone of an external electronic device (e.g., electronic device 102) directly (e.g., wired) or wirelessly combined with the electronic device 101.

[0040] The sensor module 176 may detect an operating state (e.g., power or temperature) of the electronic device 101 or an environmental state (e.g., a state of a user) outside the electronic device 101, and then generate an electrical signal or data value corresponding to the detected state. According to an embodiment of the present disclosure, the sensor module 176 may include, for example, a gesture sensor, a gyro sensor, an atmospheric pressure sensor, a magnetic sensor, an acceleration sensor, a grip sensor, a proximity sensor, a color sensor, an infrared (IR) sensor, a biometric sensor, a temperature sensor, a humidity sensor, or an illumination sensor.

[0041] The interface 177 may support one or more specific protocols to be used to connect the electronic device 101 directly (e.g., wired) or wirelessly to an external electronic device (e.g., the electronic device 102). According to an embodiment of the present disclosure, the interface 177 may include, for example, a high-definition multimedia interface (HDMI), a universal serial bus (USB) interface, a secure digital (SD) card interface, or an audio interface.

[0042] The connection end 178 may include a connector, wherein the electronic device 101 can be physically connected to an external electronic device (e.g., the electronic device 102) via the connector. According to an embodiment of the present disclosure, the connection end 178 may include, for example, an HDMI connector, a USB connector, an SD card connector, or an audio connector (e.g., a headphone connector).

[0043] The haptic module 179 may convert the electrical signal into mechanical stimulation (eg, vibration or motion) or electrical stimulation that can be recognized by the user via his sense of touch or kinesthetic sense. According to an embodiment of the present disclosure, the haptic module 179 may include, for example, a motor, a piezoelectric element, or an electrical stimulator.

[0044] The camera module 180 may capture still images or moving images. According to an embodiment of the present disclosure, the camera module 180 may include one or more lenses, an image sensor, an image signal processor, or a flash.

[0045] The power management module 188 may manage power supply to the electronic device 101. According to an exemplary embodiment of the present disclosure, the power management module 188 may be implemented as, for example, at least a part of a power management integrated circuit (PMIC).

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

[0047] The communication module 190 may support establishing a direct (e.g., wired) communication channel or a wireless communication channel between the electronic device 101 and an external electronic device (e.g., electronic device 102, electronic device 104, or server 108), and perform communication via the established communication channel. The communication module 190 may include one or more communication processors capable of operating independently from the processor 120 (e.g., an application processor (AP)) and supporting direct (e.g., wired) communication or wireless communication. According to an embodiment of the present disclosure, the communication module 190 may include a wireless communication module 192 (e.g., a cellular communication module, a short-range wireless communication module, or a global navigation satellite system (GNSS) communication module) or a wired communication module 194 (e.g., a local area network (LAN) communication module or a power line communication (PLC) module). A corresponding one of these communication modules may communicate via a first network 198 (e.g., a short-range communication network such as Bluetooth TM The wireless communication module 192 may communicate with an external electronic device via a wireless communication network (e.g., a wireless fidelity (Wi-Fi) direct connection, or an infrared data association (IrDA)) or a second network 199 (e.g., a long-distance communication network such as a cellular network, the Internet, or a computer network (e.g., a LAN or a wide area network (WAN))). These various types of communication modules may be implemented as a single component (e.g., a single chip), or may be implemented as multiple components separated from each other (e.g., multiple chips). The wireless communication module 192 may identify and authenticate the electronic device 101 in a communication network (such as a first network 198 or a second network 199) using user information (e.g., an international mobile subscriber identity (IMSI)) stored in the user identification module 196.

[0048] The antenna module 197 may transmit a signal or power to the outside of the electronic device 101 (e.g., an external electronic device) or receive a signal or power from the outside of the electronic device 101 (e.g., an external electronic device). According to an embodiment of the present disclosure, the antenna module 197 may include an antenna including a radiating element, the radiating element being composed of a conductive material or a conductive pattern formed in or on a substrate (e.g., a printed circuit board (PCB)). According to an embodiment of the present disclosure, the antenna module 197 may include a plurality of antennas. In this case, at least one antenna suitable for a communication scheme used in a communication network (such as the first network 198 or the second network 199) may be selected from the plurality of antennas by, for example, the communication module 190 (e.g., the wireless communication module 192). A signal or power may then be transmitted or received between the communication module 190 and the external electronic device via the selected at least one antenna. According to an embodiment of the present disclosure, another component (e.g., a radio frequency integrated circuit (RFIC)) other than the radiating element may be additionally formed as a part of the antenna module 197.

[0049] At least some of the above components may be coupled to each other via an inter-peripheral communication scheme (e.g., a bus, a general purpose input output (GPIO), a serial peripheral interface (SPI), or a mobile industry processor interface (MIPI)) and communicatively transmit signals (e.g., commands or data) therebetween.

[0050] According to an embodiment of the present disclosure, a command or data may be sent or received between the electronic device 101 and the external electronic device 104 via the server 108 combined with the second network 199. Each of the electronic device 102 and the electronic device 104 may be a device of the same type as the electronic device 101, or a device of a different type from the electronic device 101. According to an embodiment of the present disclosure, all or some operations to be executed in the electronic device 101 may be executed in one or more of the external electronic device 102, the external electronic device 104, or the server 108. For example, if the electronic device 101 should automatically execute a function or service or should execute a function or service in response to a request from a user or another device, the electronic device 101 may request the one or more external electronic devices to execute at least part of the function or service instead of executing the function or service, or the electronic device 101 may request the one or more external electronic devices to execute at least part of the function or service in addition to executing the function or service. The one or more external electronic devices that receive the request may execute the requested at least part of the function or service, or execute another function or another service related to the request, and transmit the result of the execution to the electronic device 101. The electronic device 101 may provide the result as at least a partial reply to the request with or without further processing the result. To this end, for example, cloud computing technology, distributed computing technology, or client-server computing technology may be used.

[0051] The electronic device according to the embodiment may be one of various types of electronic devices. The electronic device may include, but is not limited to, for example, a portable communication device (e.g., a smart phone), a computer device, a portable multimedia device, a portable medical device, a camera, a wearable device, a household appliance, etc. According to an embodiment of the present disclosure, the electronic device is not limited to those electronic devices described above.

[0052] It should be understood that the embodiments of the present disclosure and the terms used therein are not intended to limit the technical features set forth herein to specific embodiments, but include various changes, equivalent forms or alternative forms for corresponding embodiments. For the description of the accompanying drawings, similar reference numerals may be used to refer to similar or related elements. It will be understood that the noun corresponding to the project in the singular form may include one or more things, unless the relevant context clearly indicates otherwise. As used herein, each phrase in the phrases such as "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" may include any one or all possible combinations of the items listed together with the corresponding one of the multiple phrases. As used herein, terms such as "1st" and "2nd" or "first" and "second" may be used to simply distinguish the corresponding component from another component, and do not limit the component in other aspects (e.g., importance or order). It will be understood that if an element (e.g., a first element) is referred to as being "coupled with another element (e.g., a second element)", "coupled to another element (e.g., the second element)", "connected with another element (e.g., the second element)" or "connected to another element (e.g., the second element)" when the terms "operably" or "communicatively" are used or when the terms "operably" or "communicatively" are not used, the element may be directly (e.g., wired) connected to the other element, wirelessly connected to the other element, or connected to the other element via a third element.

[0053] As used herein, the term "module" may include a unit implemented in hardware, software or firmware, or any combination of hardware, software and firmware, and may be used interchangeably with other terms (e.g., "logic", "logic block", "part" or "circuit"). A module may be a single integrated component adapted to perform one or more functions or the smallest unit or part of the single integrated component. For example, according to an embodiment of the present disclosure, a module may be implemented in the form of an application specific integrated circuit (ASIC).

[0054] The embodiments described herein may be implemented as software (e.g., program 140) including one or more instructions stored in a storage medium (e.g., internal memory 136 or external memory 138) that can be read by a machine (e.g., electronic device 101). For example, under the control of a processor, a processor (e.g., processor 120) of the machine (e.g., electronic device 101) may call at least one of the one or more instructions stored in the storage medium and execute the at least one instruction with or without the use of one or more other components. This enables the machine to operate to perform at least one function according to the at least one instruction called. The one or more instructions may include code generated by a compiler or code that can be run by an interpreter. A machine-readable storage medium may be provided in the form of a non-transitory storage medium. Among them, "non-transitory" only means that the storage medium is a tangible device and may not include a signal (e.g., an electromagnetic wave), but the term does not distinguish between data being semi-permanently stored in a storage medium and data being temporarily stored in a storage medium.

[0055] According to an embodiment of the present disclosure, the method according to an embodiment of the present disclosure may be included and provided in a computer program product. The computer program product may be traded between a seller and a buyer as a product. The computer program product may be released in the form of a machine-readable storage medium (e.g., a compact disk read-only memory (CD-ROM)), or may be downloaded via an application store (e.g., Play Store TM ) The computer program product may be published (e.g., downloaded or uploaded) online, or the computer program product may be distributed (e.g., downloaded or uploaded) directly between two user devices (e.g., smart phones). If published online, at least part of the computer program product may be temporarily generated, or at least part of the computer program product may be at least temporarily stored in a machine-readable storage medium (such as a memory of a manufacturer's server, an application store's server, or a forwarding server).

[0056] According to an embodiment of the present disclosure, each component (e.g., module or program) in the above-mentioned components may include a single entity or multiple entities. According to an embodiment of the present disclosure, one or more components in the above-mentioned components may be omitted, or one or more other components may be added. Alternatively or additionally, multiple components (e.g., modules or programs) may be integrated into a single component. In this case, according to an embodiment of the present disclosure, the integrated component may still perform the one or more functions of each of the multiple components in the same or similar manner as a corresponding one of the multiple components performing one or more functions before integration. According to an embodiment of the present disclosure, the operations performed by a module, a program or another component may be performed sequentially, in parallel, repeatedly or in a heuristic manner, or one or more operations in the operations may be run or omitted in a different order, or one or more other operations may be added.

[0057] Figure 2A A network environment according to an embodiment of the present disclosure is shown.

[0058] Figure 2B Data according to an embodiment of the present disclosure is shown.

[0059] In the embodiments of the present disclosure, Figure 2A The electronic device 210 and the electronic device 250 may be connected with Figure 1 The electronic device 101 corresponds. In the embodiment of the present disclosure, Figure 2A The push server 220, the management server 230, or the combination of the push server 220 and the management server 230 can be used with Figure 1 In the embodiment of the present disclosure, Figure 2A The network 290 can be connected with Figure 1 The first network 198, the second network 199, or the combination of the first network 198 and the second network 199 corresponds to the first network 198, the second network 199, or the combination of the first network 198 and the second network 199. Figure 1 The configuration of the electronic device 101 is described Figure 2A components.

[0060] Reference Figure 2A , the electronic device 210 and the electronic device 250, the push server 220, the management server 230 and the blockchain network 240 can construct a network environment 200.

[0061] Reference Figure 2B , according to an embodiment, the processor of the electronic device 210 (eg, Figure 1The processor 120 of the electronic device 210 may identify a request of a running application. In an embodiment of the present disclosure, the processor 120 of the electronic device 210 may identify a request indicating permission for at least one smart contract (e.g., smart contract 241) related to the running application, wherein the at least one smart contract is at least one smart contract among smart contracts 241, smart contracts 243, and smart contracts 245 recorded in a block managed by the blockchain network 240. In an embodiment of the present disclosure, the smart contract 241 may be related to a push service of any application. In an embodiment of the present disclosure, the request may also include information of the address 242 of the smart contract 241.

[0062] In an embodiment of the present disclosure, smart contracts 241, smart contracts 243, and smart contracts 245 may include program codes written in a specified format. In an embodiment of the present disclosure, smart contracts 241, smart contracts 243, and smart contracts 245 may include program codes written in a specified language (e.g., Solidity). In an embodiment of the present disclosure, smart contracts 241, smart contracts 243, and smart contracts 245 may include program codes for recording and executing contracts. In an embodiment of the present disclosure, smart contracts 241, smart contracts 243, and smart contracts 245 may include program codes for recording contracts related to push message transmission and sending push messages to electronic devices (e.g., electronic devices 210) of contracting parties. In an embodiment of the present disclosure, smart contracts 241, smart contracts 243, and smart contracts 245 may be deployed in blockchain network 240 by electronic device 250, and are therefore recorded in blocks of blockchain network 240. In an embodiment of the present disclosure, if the smart contract 241 is recorded in a block of the blockchain network 240, an address 242 of the smart contract 241 may be generated.

[0063] In an embodiment of the present disclosure, the processor 120 of the electronic device 210 may identify a consent request for a smart contract 241 associated with a running application. In an embodiment of the present disclosure, the processor 120 of the electronic device 210 may display a request on a display device (e.g., Figure 1 A user interface indicating a request for consent to the smart contract 241 associated with the running application is displayed on the display device 160. In an embodiment of the present disclosure, the smart contract 241 associated with the running application may be a smart contract associated with a push service.

[0064] In an embodiment of the present disclosure, the processor 120 of the electronic device 210 may identify an input received through the user interface. In an embodiment of the present disclosure, the processor 120 of the electronic device 210 may identify a push server 220 in response to the input. In an embodiment of the present disclosure, the processor 120 of the electronic device 210 may identify a push server 220 corresponding to the input among a plurality of push servers.

[0065] In an embodiment of the present disclosure, the processor 120 of the electronic device 210 may use a communication module (eg, Figure 1 The communication module 190 of the electronic device 210 may request a push key 221 from the push server 220. In an embodiment of the present disclosure, the processor 120 of the electronic device 210 may send a push key request including identification information 211 of the electronic device 210 to the push server 220. In an embodiment of the present disclosure, the push key 221 may be referred to as a push token. In an embodiment of the present disclosure, the push key 221 may be data for identifying the electronic device 210 to which the push server 220 will send a push message.

[0066] In an embodiment of the present disclosure, the processor 120 of the electronic device 210 may receive a push key 221 from the push server 220 using the communication module 190. In an embodiment of the present disclosure, the processor 120 of the electronic device 210 may receive a push key 221 generated by the push server 220 in response to a push key request from the push server 220. In an embodiment of the present disclosure, the electronic device 210 may store the push key 221.

[0067] In an embodiment of the present disclosure, the processor 120 of the electronic device 210 may use the communication module 190 to request the management server 230 to encrypt the push key 221. In an embodiment of the present disclosure, the processor 120 of the electronic device 210 may send a push key encryption request including the push key 221, the address 242 of the smart contract 241, or a combination of the push key 221 and the address 242 of the smart contract 241 to the management server 230. In an embodiment of the present disclosure, the push key encryption request may also include an identifier of the push server 220.

[0068] In an embodiment of the present disclosure, the processor 120 of the electronic device 210 may receive the encrypted push key 244 from the management server 230 using the communication module 190. In an embodiment of the present disclosure, the processor 120 of the electronic device 210 may receive the push key 244 encrypted by the management server 230 in response to the push key encryption request from the management server 230. In an embodiment of the present disclosure, the electronic device 210 may store the encrypted push key 244.

[0069] In an embodiment of the present disclosure, the management server 230 may encrypt the push key in response to the push key encryption request, and send the encrypted push key 244 to the electronic device 210. In an embodiment of the present disclosure, the management server 230 may encrypt the push key based on the encrypted key corresponding to the address 242 of the smart contract 241. The management server 230 may encrypt the push key based on the encryption key 231 among the multiple encryption keys, wherein the encryption key 231 corresponds to the identifier of the push server 220, the address 242 of the smart contract 241, or the combination of the identifier of the push server 220 and the address 242 of the smart contract 241. In an embodiment of the present disclosure, as an example, the management server 230 may encrypt the push key based on the encryption key 231. In an embodiment of the present disclosure, the management server 230 may encrypt the push key using a reversible cryptographic system, wherein the reversible cryptographic system is used to decrypt the encrypted push key using the original push key. In an embodiment of the present disclosure, the management server 230 may encrypt the push key based on a symmetric cryptographic system. In an embodiment of the present disclosure, the management server 230 may encrypt the push key using a key (e.g., a secret key) based on a symmetric cryptographic system, and decrypt the encrypted push key using the same key. In an embodiment of the present disclosure, the management server 230 may encrypt the push key based on an asymmetric cryptographic system. In an embodiment of the present disclosure, the management server 230 may be a pair of keys based on an asymmetric cryptographic system. The management server 230 may generate a first key (private key) and a second key (public key), encrypt the push key based on the first key (public key), and decrypt the encrypted push key based on the second key (private key) in the key pair.

[0070] In an embodiment of the present disclosure, as an example, the electronic device 210 requests the push key 221 from the push server 220, and directly requests the management server 230 to encrypt the push key. In an embodiment of the present disclosure, the electronic device 210 may request the push key 221 and the encrypted push key 244 from the push server 220. In an embodiment of the present disclosure, the push server 220 may generate the push key 221 in response to the push key request, and request the management server 230 to encrypt the generated push key 221. In an embodiment of the present disclosure, the push server 220 may send the encrypted push key 244 received from the management server 230 to the electronic device 210. In an embodiment of the present disclosure, the electronic device 210 may request the push key 221 from the push server 220, and also send the address 242 of the smart contract 241.

[0071] In an embodiment of the present disclosure, the processor 120 of the electronic device 210 may use the communication module 190 to send a transaction for recording as a contracting party of the smart contract 241 to the blockchain network 240. In an embodiment of the present disclosure, the processor 120 of the electronic device 210 may send a transaction for recording as a contracting party to the blockchain network 240, wherein the transaction includes a user address (e.g., the user's email address for the blockchain network 240), an encrypted push key 244, an instruction set corresponding to the smart contract 241, an address 242 of the smart contract 241, and a combination of a user address (e.g., the user's email address for the blockchain network 240), an encrypted push key 244, an instruction set corresponding to the smart contract 241, and an address 242 of the smart contract 241.

[0072] In an embodiment of the present disclosure, after a transaction for recording as a contracting party is recorded in a block of the blockchain network 240, the processor 120 of the electronic device 210 may receive a push message according to the smart contract 241 via the push server 220 and the management server 230 using the communication module 190.

[0073] In an embodiment of the present disclosure, the blockchain network 240 may identify a push event. In an embodiment of the present disclosure, the blockchain network 240 may identify a program code execution request for a smart contract (e.g., smart contract 241) based on execution requests of other smart contracts (e.g., smart contract 243). In an embodiment of the present disclosure, the blockchain network 240 may receive a program code execution request for a smart contract (e.g., smart contract 241) from an electronic device 250. In an embodiment of the present disclosure, the blockchain network 240 may identify a program code execution request as a push event. In an embodiment of the present disclosure, the program code execution request may include a push message, an address of a smart contract 241, an address of a contracting party, or a combination of a push message, an address of a smart contract 241, and an address of a contracting party. In an embodiment of the present disclosure, the step of identifying a push event at the blockchain network 240 may be understood as a node participating in the blockchain network 240 (e.g., Figure 1 The push event is identified at the electronic device 102 and the electronic device 104 and the server 108).

[0074] In an embodiment of the present disclosure, in response to identifying a push event, the blockchain network 240 may execute the program code of the smart contract 241 corresponding to the push event. In an embodiment of the present disclosure, the blockchain network 240 may record the execution result of the smart contract 241 corresponding to the push event in a block. In an embodiment of the present disclosure, the blockchain network 240 may record a push event log in a block based on the execution result of the smart contract 241 corresponding to the push event. In an embodiment of the present disclosure, the execution result of the smart contract 241 may include a push message, an address of the smart contract 241, an address of a contracting party, or a combination of a push message, an address of the smart contract 241, and an address of a contracting party. In an embodiment of the present disclosure, the step of executing program code at the blockchain network 240 may be understood as executing a push message at a node participating in the blockchain network 240 (e.g., Figure 1 The program code is executed at the electronic device 102 and the electronic device 104 and the server 108).

[0075] In an embodiment of the present disclosure, the management server 230 may identify an event log based on data recorded in a block of the blockchain network 240. In an embodiment of the present disclosure, the management server 230 may identify an event log based on an address of a smart contract 241 among data recorded in a block. In an embodiment of the present disclosure, the management server 230 may identify a push event log based on information indicating a type of an event log among a plurality of event logs.

[0076] In an embodiment of the present disclosure, in response to identifying a push event log, the management server 230 may request an encrypted push key 244 from the blockchain network 240. In an embodiment of the present disclosure, in response to identifying a push event log, the management server 230 may request an encrypted push key 244 corresponding to the address of the contracting party from the blockchain network 240.

[0077] In an embodiment of the present disclosure, the management server 230 may obtain an encrypted push key 244 corresponding to the address of the contracting party from the blockchain network 240 based on the transaction recorded as a contracting party to the smart contract 241.

[0078] In an embodiment of the present disclosure, the management server 230 may decrypt the encrypted push key 244 based on the encryption key 231 corresponding to the encrypted push key 244 .

[0079] In an embodiment of the present disclosure, the management server 230 may identify the push server 220 based on the push key 221, the address 242 of the smart contract 241, the encrypted push key 244, or a combination of the push key 221, the address 242 of the smart contract 241, and the encrypted push key 244. In an embodiment of the present disclosure, the management server 230 may request the push server 220 to send a push message. In an embodiment of the present disclosure, the push message sending request may include a push message, a decrypted push key 221, or a combination of a push message and a decrypted push key 221.

[0080] In an embodiment of the present disclosure, the push server 220 may receive a push message sending request from the management server 230. In an embodiment of the present disclosure, the push server 220 may receive a push message sending request including a push message, a decrypted push key 221, or a combination of a push message and a decrypted push key 221 from the management server 230.

[0081] In an embodiment of the present disclosure, the push server 220 may identify the electronic device 210 based on the decrypted push key 221. In an embodiment of the present disclosure, the push server 220 may identify the electronic device 210 having the identification information 211 matching the decrypted push key 221. In an embodiment of the present disclosure, the push server 220 may send a push message to the electronic device 210.

[0082] In an embodiment of the present disclosure, the electronic device 210 may use the communication module 190 to receive a push message according to the smart contract 241 via the push server 220 .

[0083] In an embodiment of the present disclosure, the electronic device 250 may be a device of a developer who programs an application and smart contracts 241 , 243 , and 245 corresponding to the application.

[0084] In an embodiment of the present disclosure, the electronic device 250 may deploy a smart contract (eg, smart contract 241) in the blockchain network 240, wherein the blockchain network 240 records the smart contract 241 in a block. In an embodiment of the present disclosure, Table 1 may show an example of a smart contract.

[0085]

Table 1

[0086]

[0087] The pragma solidity^0.5.4 of Table 1 may be a program code for indicating a definition of a programming language (Solidity) and its version 0.5.4.

[0088] The interface ERCPush of Table 1 may be a program code for indicating the interface definition ERCPush. The interface ERCPush of Table 1 may include a program code for indicating the following items: a definition of a Push event, a definition of a registerKey function, a definition of a getKey function, a definition of a sendPush function, or a combination of the definition of a Push event, the definition of a registerKey function, the definition of a getKey function, and the definition of a sendPush function.

[0089] In an embodiment of the present disclosure, the event Push of Table 1 may be a program code for defining a Push event. In an embodiment of the present disclosure, the event Push of Table 1 may include data address[]indexed_to indicating an address of a contracting party, data address indexed_operator indicating an address of a smart contract, data string_msg indicating a push message, and a combination of data address[]indexed_to indicating an address of a contracting party, data address indexed_operator indicating an address of a smart contract, and data string_msg indicating a push message.

[0090] In an embodiment of the present disclosure, the function registerKey of Table 1 may be a program code for defining a registerKey function. In an embodiment of the present disclosure, the registerKey function may define a function for the electronic device 210 to request a record of a contracting party to the smart contract 241. In an embodiment of the present disclosure, the function registerKey of Table 1 may include data string_encPushKey indicating an encrypted push key of a contracting party. In an embodiment of the present disclosure, the public of the registerKey function may indicate that the execution result of the registerKey function can be accessed externally. In an embodiment of the present disclosure, the returns (bool result) of the registerKey function may indicate a return value according to the execution result of the registerKey function.

[0091] In an embodiment of the present disclosure, in order to be recorded as a contracting party to the smart contract 241 in a block of the blockchain network 240 , the electronic device 210 may request the blockchain network 240 to execute a registerKey function including an encrypted push key obtained from the management server 230 .

[0092] In an embodiment of the present disclosure, function getKey of Table 1 may be a program code for defining a getKey function. In an embodiment of the present disclosure, the getKey function may define a function for the management server 230 to request encryption of a contracting party address identifiable in an event log. In an embodiment of the present disclosure, function getKey of Table 1 may include data address_to indicating the address of the contracting party. In an embodiment of the present disclosure, public of the getKey function may indicate that the execution result of the getKey function can be accessed externally. In an embodiment of the present disclosure, returns (string encPushKey) of the getKey function may indicate that an encrypted push key corresponding to the address of the contracting party is returned according to the execution result of the getKey function.

[0093] In an embodiment of the present disclosure, the management server 230 may request the blockchain network 240 to execute the getKey function based on the push event log recorded in the block of the blockchain network 240. In an embodiment of the present disclosure, the management server 230 may request the blockchain network 240 to execute the getKey function, wherein the getKey function requests to return an encrypted push key corresponding to the address of the contracting party in the push event log.

[0094] In an embodiment of the present disclosure, the function sendPush of Table 1 may be a program code for defining a sendPush function. In an embodiment of the present disclosure, the sendPush function may define a function for the manager of the smart contract 241 to request the blockchain network 240 to execute a push event. In an embodiment of the present disclosure, the function sendPush of Table 1 may include data address[]_to indicating the address of the contracting party, data address_operator indicating the address of the smart contract, data string_msg indicating the push message, and a combination of data address[]_to indicating the address of the contracting party, data address_operator indicating the address of the smart contract, and data string_msg indicating the push message. In an embodiment of the present disclosure, the external of the sendPush function may indicate that the execution result of the sendPush function can be accessed externally. In an embodiment of the present disclosure, the returns (bool result) of the sendPush function may indicate a return value according to the execution result of the sendPush function.

[0095] In an embodiment of the present disclosure, the function sendPush may include issuing Push. In an embodiment of the present disclosure, issuing Push may be a program code for recording the execution result of sendPush in an event log.

[0096] In an embodiment of the present disclosure, the electronic device 250 may request the blockchain network 240 to execute a sendPush function to record a push event in a block of the blockchain network 240. In an embodiment of the present disclosure, the electronic device 250 may request the blockchain network 240 to execute a sendPush function, wherein the sendPush function includes an address of a contracting party, an address of a smart contract, a push message, or a combination of an address of a contracting party, an address of a smart contract, and a push message.

[0097] In an embodiment of the present disclosure, the electronic device 250 may request the management server 230 to manage push events of the smart contract 241 based on the address of the smart contract 241 generated by being deployed to the blockchain network 240. In an embodiment of the present disclosure, the push event management request may include data indicating the smart contract 241, the address of the smart contract 241, or a combination of data indicating the smart contract 241 and the address of the smart contract 241.

[0098] In an embodiment of the present disclosure, the management server 230 may verify the smart contract 241 based on data indicating the smart contract 241. In an embodiment of the present disclosure, the management server 230 may verify the smart contract 241 by identifying whether the smart contract 241 is generated in a specified format defined by the management server 230.

[0099] In an embodiment of the present disclosure, if the smart contract 241 is verified, the management server 230 may generate an encryption key for the smart contract 241. In an embodiment of the present disclosure, the management server 230 may match and store the encryption key for the smart contract 241 with the address of the smart contract 241.

[0100] In an embodiment of the present disclosure, in response to verifying the smart contract 241 , the management server 230 may send a confirmation response to the push event management request to the electronic device 250 .

[0101] In an embodiment of the present disclosure, the management server 230 may monitor a push event log associated with a smart contract 241 recorded in the blockchain network 240. In an embodiment of the present disclosure, in response to identifying a push event log associated with the smart contract 241, the management server 230 may send a push message to an electronic device of a contracting party (e.g., the electronic device 210) according to the push event log.

[0102] Figure 3A flowchart showing the operation of an electronic device according to an embodiment of the present disclosure is shown. Figure 2A Components to describe Figure 3 operation.

[0103] Reference Figure 3 , at operation 310, the electronic device 210 may request a blockchain network (e.g., Figure 2A In an embodiment of the present disclosure, if a node of the blockchain network 240 satisfies a specific condition, the electronic device 210 may generate a smart contract to be executed (e.g., Figure 2A Smart contract 241). For example, the smart contract may be included in the transaction as code and sent to the blockchain network 240, and if a specific event of the smart contract occurs, the electronic device 210 may register for a push service for receiving push messages via the push server 220. To this end, the electronic device 210 may request registration for the push service by sending a smart contract including instructions for the push event to the blockchain network 240. In an embodiment of the present disclosure, the transaction may include the user's address, an encrypted push key, an instruction set corresponding to the smart contract, the address of the smart contract 241, or a combination of the user's address, an encrypted push key, an instruction set corresponding to the smart contract, and the address of the smart contract 241. In an embodiment of the present disclosure, the push key may be data for identifying the electronic device to which the push server 220 (e.g., Google push server, etc.) will send a push message. In an embodiment of the present disclosure, the push key is sent by a management server (e.g., Figure 2A The data generated by encrypting the push key based on the encryption key corresponding to the smart contract 241 by the management server 230 of the push server can be used as the push data. In an embodiment of the present disclosure, the push key can be generated by the push server (for example, Figure 2A The data generated by the push server 220).

[0104] In an embodiment of the present disclosure, in response to a request to register a push service, the blockchain network 240 may send a transaction to one or more nodes of the blockchain network 240, and the transaction verified by the node may be included in a new block linked to the old block.

[0105] Reference Figure 3, in operation 350, the electronic device 210 may receive a push message corresponding to the identified push event from the management server 230 via the push server 220. In an embodiment of the present disclosure, if the blockchain network 240 executes the program code of the smart contract 241 corresponding to the push event, the push message may be recorded in the push event log. In an embodiment of the present disclosure, the management server 230 may identify the push event log, and send the push message recorded in the push event log to the push server 220 that publishes the push key. In an embodiment of the present disclosure, the push server 220 may identify the electronic device 210 based on the push key, and send the push message to the identified electronic device 210.

[0106] Figure 4 A flowchart showing the operation of an electronic device according to an embodiment of the present disclosure is shown. In an embodiment of the present disclosure, Figure 4 The operations can be included in Figure 3 In operation 310. In an embodiment of the present disclosure, Figure 4 The electronic device 401, the push server 402, the management server 403 or the blockchain network 404 can be connected with Figure 2A The electronic device 210, the push server 220, the management server 230 or the blockchain network 240 correspond respectively. In the embodiment of the present disclosure, by referring to Figure 2A Components to describe Figure 4 operation.

[0107] Reference Figure 4 In operation 411, the electronic device 401 may request the push server 402 to issue a push key. In an embodiment of the present disclosure, in response to an input received through a user interface, the electronic device 401 may request a push server 402 corresponding to the input among multiple push servers to issue a push key. In an embodiment of the present disclosure, in response to an instruction to apply a smart contract (e.g., Figure 2A The request for consent of the smart contract 241) can be made by the electronic device 401 on a display device (e.g., Figure 1 The user interface is displayed on the display device 160).

[0108] Reference Figure 4 In operation 413, in response to the push key publishing request, the push server 402 may generate a push key and store the generated push key. In an embodiment of the present disclosure, the push server 402 may match and store the generated push key with the identification information (e.g., IP address, device ID) of the electronic device 401. In an embodiment of the present disclosure, the push key may be referred to as a push token.

[0109] Reference Figure 4In operation 415 , the push server 402 may send the generated push key to the electronic device 401 .

[0110] Reference Figure 4 In operation 421, the electronic device 401 may request the management server 403 to encrypt the push key. In an embodiment of the present disclosure, in response to an input received through a user interface, the electronic device 401 may request a management server 403 corresponding to the input among multiple management servers to encrypt the push key.

[0111] In an embodiment of the present disclosure, the electronic device 401 may send a push key encryption request to the management server 403, wherein the push key encryption request includes the address of the smart contract 241, the identification information of the push server 402 that publishes the push key, or a combination of the address of the smart contract 241 and the identification information of the push server 402 that publishes the push key.

[0112] Reference Figure 4 In operation 423 , in response to the push key encryption request, the management server 403 may encrypt the push key. In an embodiment of the present disclosure, the management server 403 may not store the identification information of the electronic device 401 .

[0113] In an embodiment of the present disclosure, the management server 403 may encrypt the push key using an encryption key corresponding to the address of the smart contract 241, the push server 402, or a combination of the address of the smart contract 241 and the push server 402. In an embodiment of the present disclosure, the management server 403 may manage one encryption key corresponding to the address of the smart contract 241, or one or more encryption keys corresponding to the address of the smart contract 241. In an embodiment of the present disclosure, the management server 403 may make one or more encryption keys corresponding to the address of the smart contract 241 correspond to multiple push servers respectively. In an embodiment of the present disclosure, the management server 403 may send a push key to the push server 402 according to an external electronic device (e.g., Figure 2A In the embodiment of the present disclosure, if a request is received from an external electronic device (e.g., a distributed application (dapp)), the encryption key is matched, stored and managed with multiple applications (e.g., dapps). Figure 2A When the electronic device 210 receives a push key encryption request from any application, the management server 403 may use the encryption key corresponding to the application to encrypt the push key, and the encrypted push key may be sent to the external electronic device (e.g., Figure 2A The electronic device 210) is requested and stored through the nodes of the blockchain network 240.

[0114] Reference Figure 4, in operation 425 , the management server 403 may send the encrypted push key to the electronic device 401 .

[0115] refer to Figure 4 , in operation 431, the electronic device 401 may send a push service registration request to the blockchain network 404. In an embodiment of the present disclosure, the electronic device 401 may generate a transaction including the address of the smart contract 241, the encrypted push key, the address of the electronic device 401 (or the user address of the electronic device 401), or a combination of the address of the smart contract 241, the encrypted push key, and the address of the electronic device 401 (or the user address of the electronic device 401), send the generated transaction to the blockchain network 404, and thus send the push service registration request to the blockchain network 404. In an embodiment of the present disclosure, the transaction may indicate consent to the smart contract 241.

[0116] In an embodiment of the present disclosure, the step of generating a transaction may include using a memory stored in the electronic device 401 (eg, Figure 1 The information in the transaction (e.g., recipient address, amount, smart contract, etc.) is digitally signed using a private key in the memory 130 of the electronic device 401. In an embodiment of the present disclosure, the electronic device 401 may send a push service registration request to the blockchain network 404 by sending the transaction to the blockchain network 404. In an embodiment of the present disclosure, the blockchain network 404 may verify the transaction based on a public key corresponding to the private key. In an embodiment of the present disclosure, in response to verifying that the user signed the transaction of the electronic device 401, the blockchain network 404 may record the transaction in a block. In an embodiment of the present disclosure, the electronic device 401 may use a private key stored in a device electrically connected to the electronic device 401 (e.g., a USB storage device, a USB mobile (OTG) storage device) for a digital sign to create a transaction. In an embodiment of the present disclosure, the wallet address of the user's blockchain network 404 may be generated based on the public key corresponding to the private key.

[0117] In an embodiment of the present disclosure, the electronic device 401 may generate a key pair (private key-public key pair) based on the root seed of the blockchain network 404. In an embodiment of the present disclosure, the electronic device 401 may generate a key pair using an algorithm (e.g., Rivest-Samour-Adleman (RSA), elliptic curve cryptography (ECC)). In an embodiment of the present invention, RSA and ECC are merely examples of algorithms for creating a key pair, and the present invention is not limited thereto. In an embodiment of the present disclosure, the electronic device 401 may generate a key pair using an algorithm other than RSA or ECC. In an embodiment of the present disclosure, the root seed may indicate a value randomly generated within an available range in the blockchain network 404. In an embodiment of the present disclosure, the electronic device 401 may generate a root seed according to a dynamic characteristic or a unique value of a configuration in the electronic device 401.

[0118] Reference Figure 4 In operation 433, the blockchain network 404 may record the encrypted push key in a block of the blockchain network 404 in response to the push service registration request. In an embodiment of the present disclosure, the blockchain network 404 may record the encrypted push key by recording the transaction from the electronic device 401 in a block of the blockchain network 404.

[0119] Figure 5 A flowchart showing the operation of an electronic device according to an embodiment of the present disclosure is shown. In an embodiment of the present disclosure, Figure 5 The operations can be included in Figure 3 In operation 350. In an embodiment of the present disclosure, Figure 5 The electronic device 501, the push server 502, the management server 503 or the blockchain network 504 can be connected with Figure 2A The electronic device 210, the push server 220, the management server 230 or the blockchain network 240 correspond respectively. In the embodiment of the present disclosure, by referring to Figure 2A Components to describe Figure 5 operation.

[0120] Reference Figure 5 In operation 511, the blockchain network 504 may identify that a push event occurs. In an embodiment of the present disclosure, the blockchain network 504 may identify a program code execution request of a smart contract (e.g., smart contract 241) based on an execution result of another smart contract (e.g., smart contract 243).

[0121] In an embodiment of the present disclosure, the blockchain network 504 may call a smart contract (e.g., smart contract 241) in response to identifying a program code execution request of the smart contract (e.g., smart contract 241).

[0122] In an embodiment of the present disclosure, the blockchain network 504 may identify a push event based on a program code execution request. In an embodiment of the present disclosure, the blockchain network 504 may receive a push event from an application manager (e.g., Figure 2A The electronic device 250 of the present disclosure receives the program code execution request of the smart contract 241. In an embodiment of the present disclosure, the blockchain network 504 may identify a push event based on the program code execution request. In an embodiment of the present disclosure, the program code execution request may include a push message, an address of the smart contract 241, an address of a contracting party, or a combination of a push message, an address of the smart contract 241, and an address of a contracting party.

[0123] Reference Figure 5If the push event is identified in operation 511 (yes), the blockchain network 504 may perform operation 513. If the push event is not identified in operation 511 (no), the blockchain network 504 may perform operation 511 again.

[0124] Reference Figure 5 , in operation 513, the blockchain network 504 may execute the program code corresponding to the push event. In an embodiment of the present disclosure, the blockchain network 504 may execute the program code of the smart contract 241 corresponding to the push event, and record the execution result in a block of the blockchain network 504. In an embodiment of the present disclosure, the execution result of the smart contract 241 may include a push message, an address of the smart contract 241, an address of a contracting party, or a combination of a push message, an address of the smart contract 241, and an address of a contracting party.

[0125] Reference Figure 5 , in operation 521, the management server 503 may obtain a push event log from the blockchain network 504. In an embodiment of the present disclosure, the management server 503 may periodically obtain an event log from the blockchain network 504. In an embodiment of the present disclosure, the management server 503 may obtain an event log based on data recorded in a block of the blockchain network 504. In an embodiment of the present disclosure, the management server 503 may obtain an event log based on the address of the smart contract 241 in the data recorded in the block of the blockchain network 504. In an embodiment of the present disclosure, the management server 503 may identify the event log of the smart contract 241 that generates the push event using the address of the smart contract 241 in the event log, and also obtain the push event log from a plurality of event logs based on information indicating the type of event in the event log.

[0126] Reference Figure 5 In operation 523, the management server 503 may identify the occurrence of a push request event based on the acquired push event log. In an embodiment of the present disclosure, if a new push event log is acquired, the management server 503 may identify the occurrence of a push request event.

[0127] In an embodiment of the present disclosure, in response to identifying that a push request event occurs, the management server 503 may obtain an encrypted push key corresponding to the address of the contracting party in the push event log from the blockchain network 504. In an embodiment of the present disclosure, the management server 503 may request the blockchain network 504 to execute the program code of the smart contract 241 to obtain the encrypted push key corresponding to the address of the contracting party. In an embodiment of the present disclosure, the management server 503 may obtain the encrypted push key by obtaining the execution result of the program code of the smart contract 241 from the blockchain network 504.

[0128] Reference Figure 5 If the push request event is identified to occur in operation 523 (yes), the blockchain network 504 may perform operation 525. If the push request event is not identified to occur in operation 523 (no), the blockchain network 504 may re-perform operation 521.

[0129] Reference Figure 5 In operation 525, the management server 503 may decrypt the encrypted push key in response to identifying the push request event. In an embodiment of the present disclosure, the management server 503 may decrypt the encrypted push key based on the encryption key corresponding to the address of the smart contract 241, the encrypted push key, or a combination of the encryption key corresponding to the address of the smart contract 241 and the encrypted push key.

[0130] In an embodiment of the present disclosure, the management server 503 may identify the push server 502 among multiple push servers based on the address of the smart contract 241, the encrypted push key, the decrypted push key, or a combination of the address of the smart contract 241, the encrypted push key, and the decrypted push key.

[0131] Reference Figure 5 In operation 527, the management server 503 may send a push message based on the decrypted push key to the push server 502. In an embodiment of the present disclosure, the management server 503 may send a push message including the decrypted push key to the push server 502.

[0132] In an embodiment of the present disclosure, the push server 502 may identify the electronic device 501 among a plurality of electronic devices based on the decrypted push key.

[0133] Reference Figure 5 In operation 529 , the push server 502 may send a push message based on the decrypted push key to the electronic device 501 .

[0134] Figure 6 A flowchart showing the operation of an electronic device according to an embodiment of the present disclosure is shown. In an embodiment of the present disclosure, Figure 6 The electronic device 605, the management server 603 or the blockchain network 604 can be connected with Figure 2A The electronic device 250, the management server 230 or the blockchain network 240 respectively corresponds to the electronic device 250, the management server 230 or the blockchain network 240. In the embodiment of the present disclosure, by referring to Figure 2A Components to describe Figure 6 operation.

[0135] Reference Figure 6 At operation 611, the electronic device 605 may deploy a smart contract in the blockchain network 604 (e.g., Figure 2AThe smart contract 241 is a smart contract 241 of the blockchain network 604, wherein the blockchain network 604 records the smart contract 241 in a block of the blockchain network 604. In an embodiment of the present disclosure, the smart contract 241 may be a program code written in a specified format by the management server 603 for processing requests for events according to the smart contract 241.

[0136] In an embodiment of the present disclosure, the smart contract 241 may be a smart contract for an event of a service (e.g., an application, a website, or a combination of an application and a website) programmed by a user of the electronic device 605. In an embodiment of the present disclosure, the event of the service (e.g., an application, a website, or a combination of an application and a website) may be a push event.

[0137] In an embodiment of the present disclosure, the smart contract 241 may include at least a program code for defining a push event, a program code for registering an encrypted push key, a program code for obtaining an encryption key based on an address of a contracting party, a program code for requesting to send a push message, or a combination of a program code for defining a push event, a program code for registering an encrypted push key, a program code for obtaining an encryption key based on an address of a contracting party, and a program code for requesting to send a push message. In an embodiment of the present disclosure, the program code for requesting to send a push message may include a program code for requesting that the occurrence of a push event be recorded in a push event log of the blockchain network 604.

[0138] Reference Figure 6 In operation 613, in response to the deployment of the electronic device 605, the blockchain network 604 may record the smart contract 241 in a block. In an embodiment of the present disclosure, the blockchain network 604 may generate an address of the smart contract 241 and also record the address of the smart contract 241 in a block.

[0139] Reference Figure 6 , in operation 615 , the electronic device 605 may obtain the address of the smart contract 241 by identifying a block of the blockchain network 604 .

[0140] Reference Figure 6 At operation 621, the electronic device 605 may request the management server 603 for push management of the smart contract 241. In an embodiment of the present disclosure, the push management may be a method for identifying a push event log recorded in a block of the blockchain network 604 and sending a push message to the electronic device based on the push event log (e.g., Figure 2A In an embodiment of the present disclosure, the electronic device 605 may send a push management request including the address of the smart contract 241 to the management server 603.

[0141] Reference Figure 6In operation 623, the management server 603 may verify the smart contract 241. In an embodiment of the present disclosure, the management server 603 may verify the smart contract 241 by identifying whether the smart contract 241 is written in a specified format.

[0142] Reference Figure 6 In operation 625, in response to verifying the smart contract 241, the management server 603 may generate an encryption key for the smart contract. In an embodiment of the present disclosure, the management server 603 may generate one or more encryption keys for the smart contract.

[0143] Reference Figure 6 In operation 627, in response to generating the encryption key, the management server 603 may match and store the address of the smart contract 241 with the encryption key.

[0144] Reference Figure 6 In operation 629, in response to storing the encryption key, the management server 603 may send a confirmation response to the push management request to the electronic device 605. In an embodiment of the present disclosure, in response to the confirmation response of the management server 603, the electronic device 605 may set the permissions of the smart contract 241 for the management server 603. In an embodiment of the present disclosure, the permissions of the smart contract 241 may include permissions for obtaining an encrypted push key based on an address of a contracting party, permissions for obtaining an event log of the smart contract 241, or a combination of permissions for obtaining an encrypted push key based on an address of a contracting party and permissions for obtaining an event log of the smart contract 241.

[0145] Reference Figure 6 , at operation 631, the management server 603 may monitor the event log of the smart contract 241 from the blockchain network 604. In an embodiment of the present disclosure, the management server 603 may monitor the event log based on the address of the smart contract 241. In an embodiment of the present disclosure, the management server 603 may monitor the push event log among the multiple event logs of the smart contract 241 based on the information indicating the type of the event log.

[0146] As described above, the electronic device and method according to the embodiment may distribute and store the user's personal information in a plurality of servers without centralizing the personal information.

[0147] As described above, an electronic device according to an embodiment may include: a communication circuit configured to communicate; a processor operably connected to the communication circuit; and a memory operably connected to the processor, wherein the memory may store instructions that, when executed, cause the processor to perform the following operations: requesting a management server to encrypt a push key received from a push server using the communication circuit, receiving the encrypted push key from the management server in response to the request, generating at least one transaction based on the encrypted push key, and sending the transaction to a blockchain network.

[0148] In an embodiment of the present disclosure, the transaction may include, in addition to the encrypted push key, the address of the electronic device and the address of the smart contract.

[0149] In an embodiment of the present disclosure, the electronic device may further include a display, wherein the instructions, when executed, may cause the processor to perform the following operations: display a user interface related to the smart contract on the display, and in response to user input on the user interface, request a push key from a push server.

[0150] In an embodiment of the present invention, the instructions, when executed, may cause the processor to perform the following operations: receive user input selecting a first push server among multiple push servers, in response to the user input, request a push key from the first push server, in response to receiving the push key from the first push server, request the management server to encrypt the push key received from the first push server, and in response to the push key encryption request, receive the encrypted push key from the management server.

[0151] In an embodiment of the present invention, when the instructions are executed, they may cause the processor to perform the following operations: receiving a push message from the management server via the first push server.

[0152] In an embodiment of the present disclosure, when executed, the instructions may cause the processor to perform the following operations: receive user input selecting a first management server among multiple management servers, and in response to the user input, request the first management server to encrypt a push key received from the push server.

[0153] According to an embodiment, an electronic device may include: a communication circuit configured to communicate; a processor operably connected to the communication circuit; and a memory operably connected to the processor, wherein the memory may store instructions that, when executed, cause the processor to perform the following operations: using the communication circuit to request a management server to encrypt a push key received from a push server, in response to the request, receiving the encrypted push key from the management server, and in response to the occurrence of a push event based on a smart contract, receiving a push message associated with the push event from the management server via the push server.

[0154] According to an embodiment, the electronic device may include: a communication circuit configured to communicate; a processor operably connected to the communication circuit; and a memory operably connected to the processor, wherein the memory may store instructions that, when executed, cause the processor to perform the following operations: using the communication circuit to identify a push event related to a smart contract recorded in at least one block managed by a blockchain network, decrypting at least one push key related to the push event, and using a push server to send the decrypted at least one push key and a push message to at least one external electronic device corresponding to the decrypted at least one push key.

[0155] In an embodiment of the present disclosure, when the instruction is executed, it causes the processor to perform the following operations: based on the address of the smart contract, identify a push event related to the address of the smart contract among push events related to at least one smart contract recorded in the at least one block.

[0156] In an embodiment of the present disclosure, when the instructions are executed, the processor is caused to perform the following operations: identifying a push event based on information indicating a type of event among multiple events related to the address of the smart contract.

[0157] In an embodiment of the present disclosure, when the instructions are executed, the processor is caused to perform the following operations: in response to identifying a push event, identifying at least one recipient address in the push event, and in response to identifying the at least one recipient address, receiving at least one encrypted push key corresponding to the at least one recipient address from the blockchain network.

[0158] In an embodiment of the present disclosure, when the instructions are executed, the processor is caused to perform the following operations: receiving data indicating a smart contract from a first external electronic device, identifying whether the data is in a specified format, and in response to identifying whether the data is in the specified format, identifying a push event.

[0159] In an embodiment of the present disclosure, if the first external electronic device deploys data indicating a smart contract in a blockchain network, an address of the smart contract may be generated.

[0160] In an embodiment of the present disclosure, the instructions, when executed, cause the processor to perform the following operations: receive an address of a smart contract from a second external electronic device, and based on the address of the smart contract, identify, using a communication circuit, a push event related to the smart contract recorded in at least one block managed by the blockchain network.

[0161] In an embodiment of the present disclosure, the instructions, when executed, cause the processor to perform the following operations: in response to receiving the address of the smart contract from the second external electronic device, generate an encryption key related to the smart contract.

[0162] In an embodiment of the present disclosure, when the instructions are executed, the processor is caused to perform the following operations: decrypting the at least one push key based on the encryption key.

[0163] According to an embodiment, a computer-readable recording medium may record a program, wherein the program is used to perform the following operations: recording an address of at least one external electronic device and an encrypted push key for the at least one external electronic device in a block of a blockchain network; recording a push event in a block of the blockchain network, wherein the push event includes the address of the at least one external electronic device, the address of a smart contract, and a push message; recording the push event in a block, and then receiving a sending request for an encrypted push key corresponding to the address of a first external electronic device from a management server; and in response to receiving the sending request for the encrypted push key, sending the encrypted push key corresponding to the address of the first external electronic device to the management server.

[0164] In an embodiment of the present disclosure, a computer-readable recording medium may record a program, wherein the program is also used to perform the following operations: receiving a transaction including a smart contract from a first external electronic device, recording the transaction in a block of a blockchain network, and recording the address of the smart contract.

[0165] In an embodiment of the present disclosure, a computer-readable recording medium may record a program, wherein the program is also used to perform the following operations: in response to receiving a request to send an encrypted push key, identifying the authority of the management server, and in response to identifying that the authority of the management server is a designated authority, sending an encrypted push key corresponding to the address of the first external electronic device to the management server.

[0166] In an embodiment of the present disclosure, the encrypted push key may be encrypted by the management server.

[0167] In an embodiment of the present disclosure, a smart contract may include program code for recording and executing the smart contract between contracting parties.

[0168] In an embodiment of the present disclosure, when a smart contract is recorded in a block of a blockchain network, an address of the smart contract may be generated.

[0169] The method according to the embodiment of the present disclosure may be implemented in hardware, software, or a combination of hardware and software.

[0170] When the method is implemented by software, a computer-readable storage medium for storing one or more programs (software modules) may be provided. The one or more programs stored in the computer-readable storage medium may be configured to be executed by one or more processors in the electronic device. The one or more programs may include instructions that cause the electronic device to perform the method according to the embodiments of the present disclosure defined by the attached claims and / or disclosed herein.

[0171] Programs (software modules or software) may be stored in non-volatile memory, including random access memory and flash memory, read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), magnetic disk storage, compact disk-ROM (CD-ROM), digital versatile disk (DVD) or other types of optical storage devices or tapes. Any combination of some or all of them may form a memory storing a program. In addition, a plurality of such memories may be included in an electronic device.

[0172] In addition, the program may be stored in an attachable storage device, wherein the attachable storage device is accessible through a communication network (such as the Internet, an intranet, a local area network (LAN), a wide area network (WAN), and a storage area network (SAN), or a combination of the Internet, an intranet, a local area network (LAN), a wide area network (WAN), and a storage area network (SAN)). Such a storage device can be accessed to the electronic device via an external port. In addition, a separate storage device on a communication network can be accessed to a portable electronic device.

[0173] Furthermore, a plurality of elements expressed in the specification may be configured as a single element, or a single element in the specification may be configured as a plurality of elements.

[0174] While the present disclosure has been shown and described with reference to various embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the true spirit and full scope of the present disclosure as defined by the appended claims and their equivalents.

Claims

1. An electronic device, include: a communication circuit configured to communicate; at least one processor operably connected to the communication circuit; as well as a memory operably connected to the at least one processor, The memory stores instructions, which, when executed, cause the at least one processor to perform the following operations: Request the push server to generate a push key. requesting a management server to encrypt the push key received from the push server using the communication circuit, receiving an encrypted push key from the management server in response to the request, generating at least one transaction based on the encrypted push key, wherein the at least one transaction is related to requesting a push service registration from a blockchain network, sending the at least one transaction to the blockchain network causing the blockchain network to record the encrypted push key in at least one block, and In response to the occurrence of a push event based on the smart contract, a push message associated with the push event is received from the management server via the push server based on the encrypted push key recorded in the at least one block.

2. The electronic device according to claim 1, in, The at least one transaction comprises: the encrypted push key, the address of the electronic device, and The address of the smart contract.

3. The electronic device according to claim 1, further comprising: include: monitor, Wherein, when the instruction is executed, the at least one processor is further prompted to perform the following operations: displaying a user interface associated with the smart contract on the display, and In response to user input on the user interface, the push key is requested from the push server.

4. The electronic device according to claim 1, in, When executed, the instructions further cause the at least one processor to perform the following operations: receiving a user input selecting a first push server among a plurality of push servers, In response to the user input, requesting the push key from the first push server, In response to receiving the push key from the first push server, requesting the management server to encrypt the push key received from the first push server, and The encrypted push key is received from the management server in response to a push key encryption request.

5. The electronic device according to claim 1, in, When executed, the instructions further cause the at least one processor to perform the following operations: receiving a user input selecting a first management server among a plurality of management servers, and In response to the user input, the first management server is requested to encrypt the push key received from the push server.

6. An electronic device, include: a communication circuit configured to communicate; at least one processor operably connected to the communication circuit; as well as a memory operably connected to the at least one processor, The memory stores instructions, which, when executed, cause the at least one processor to perform the following operations: In response to receiving a request from an external electronic device to encrypt a push key generated by a push server, encrypting the push key associated with the smart contract and sending the encrypted push key to the external electronic device, identifying, using the communication circuit, a push event related to the smart contract recorded in at least one block managed by a blockchain network, wherein a push service is registered based on a transaction sent from the external electronic device, decrypting at least one encrypted push key associated with the push event, and The decrypted at least one push key and a push message are transmitted to at least one external electronic device corresponding to the decrypted at least one push key using the push server.

7. The electronic device according to claim 6, in, When executed, the instructions further cause the at least one processor to perform the following operations: Based on the address of the smart contract, a push event related to the address of the smart contract is identified among push events related to at least one smart contract recorded in the at least one block.

8. The electronic device according to claim 6, in, When executed, the instructions further cause the at least one processor to perform the following operations: A push event is identified among a plurality of events associated with the address of the smart contract based on information indicating an event type.

9. The electronic device according to claim 6, in, When executed, the instructions further cause the at least one processor to perform the following operations: In response to identifying the push event, identifying at least one recipient address in the push event, and In response to identifying the at least one recipient address, receiving the at least one push key encrypted corresponding to the at least one recipient address from the blockchain network.

10. The electronic device according to claim 6, in, When executed, the instructions further cause the at least one processor to perform the following operations: receiving data indicative of the smart contract from a first external electronic device, identifying whether the data is in a specified format, and In response to identifying whether the data is in the specified format, the push event is identified.

11. The electronic device according to claim 6, in, When the first external electronic device deploys data indicating the smart contract in the blockchain network, the address of the smart contract is generated.

12. The electronic device according to claim 6, in, When executed, the instructions further cause the at least one processor to perform the following operations: receiving the address of the smart contract from a second external electronic device, and Based on the address of the smart contract, identifying, using the communication circuit, a push event related to the smart contract recorded in the at least one block managed by the blockchain network.

13. The electronic device according to claim 12, in, When executed, the instructions further cause the at least one processor to perform the following operations: In response to receiving the address of the smart contract from the second external electronic device, a cryptographic key associated with the smart contract is generated.