WO2019145799A1 - Système et procédé de validation décentralisée d'échange de données dans un réseau informatique - Google Patents

Système et procédé de validation décentralisée d'échange de données dans un réseau informatique Download PDF

Info

Publication number
WO2019145799A1
WO2019145799A1 PCT/IB2019/050063 IB2019050063W WO2019145799A1 WO 2019145799 A1 WO2019145799 A1 WO 2019145799A1 IB 2019050063 W IB2019050063 W IB 2019050063W WO 2019145799 A1 WO2019145799 A1 WO 2019145799A1
Authority
WO
WIPO (PCT)
Prior art keywords
data type
conversion
token data
computer network
amount
Prior art date
Application number
PCT/IB2019/050063
Other languages
English (en)
Inventor
Levy Cohen
Limor ROZEN
Tamir AGMON
Dikla BATTAT
Original Assignee
Seamless Logic Software Limited
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Seamless Logic Software Limited filed Critical Seamless Logic Software Limited
Publication of WO2019145799A1 publication Critical patent/WO2019145799A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/50—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols using hash chains, e.g. blockchains or hash trees
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/04—Payment circuits
    • G06Q20/06—Private payment circuits, e.g. involving electronic currency used among participants of a common payment scheme
    • G06Q20/065—Private payment circuits, e.g. involving electronic currency used among participants of a common payment scheme using e-cash
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/381—Currency conversion
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/04—Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q2220/00—Business processing using cryptography

Definitions

  • the present invention relates to data exchange in decentralized systems. More particularly, the present invention relates to systems and methods for validation of data conversion and/or exchange in computer networks.
  • Algorithms for operation of decentralized computer networks typically require that data transfer between computing nodes of the network is registered on the data ledger and also accompanied with an exchange of data tokens.
  • Each data token includes dedicated code that is associated with the corresponding decentralized computer network.
  • Data tokens may include various types of data, for instance addresses, passwords, medical records, inventory list, etc., where different computer networks may have tokens with different types of data.
  • a user In order to exchange two different types of such data tokens, a user typically must use a third trusted central party to exchange a data token (e.g., a“Bitcoin” of type‘A’) with a commonly available commodity (e.g., fiat currency, typically government issued currency) and then exchange again the received commodity, usually with a different trusted party, for a data token of a different type (e.g., of type‘B’).
  • a data token e.g., a“Bitcoin” of type‘A’
  • a commonly available commodity e.g., fiat currency, typically government issued currency
  • a method of data conversion in a computer network comprising a plurality of computing nodes, each computing node comprising a processor, the method comprising: receiving, by at least one processor of the computer network, a plurality of requests for conversion between tokens with different data types; determining, by the at least one processor, a first request corresponding to a first conversion from a first token data type to a second token data type and a second request corresponding to a second conversion from the second token data type to the first token data type assigning, by the at least one processor, a first node of the computer network to: receive a first amount of the first token data type from a first computerized device associated with the computer network; and exchange the first amount of first token data type with a first amount of a conversion token data type; and assigning, by the at least one processor, a second node of the computer network to: receive a second amount of second token data type from a second computerized device associated with the computer network; and
  • the method may further comprise: transferring, by the first node, the first amount of first token data type to the second computerized device associated with the computer network; receiving, by the first node, the second amount of the conversion token data type; transferring, by the second node, the second amount of second token data type to the first computerized device associated with the computer network; and receiving, by the second node, the first amount of the conversion token data type.
  • the computer network may be associated with a decentralized blockchain network, and all operations of the computer network may be carried out automatically.
  • Each conversion from a token data type to a conversion token data type may be registered on a separate blockchain network.
  • the method may further comprise determining the exchange rate from each token data type to the conversion token data type.
  • the exchange rate may be determined for a predetermined time period.
  • At least some operations of the computer network may be carried out utilizing the processing power of computerized devices associated with the computer network.
  • Each node of the computer network may be assigned to perform conversions for a specific token data type.
  • a data conversion system comprising: a computer network with at least first and second computing nodes, wherein each computing node comprises a processor and is assigned to perform data type conversions for a specific token data type; and at least two data receivers, to allow receipt of requests from a plurality of computerized devices associated with the computer network, wherein at least one of said at least first and second processor is configured to: receive a plurality of requests for conversion between tokens with different data types; determine a first request corresponding to a first conversion from a first token data type to a second token data type and a second request corresponding to a second conversion from the second token data type to the first token data type; assign a first computing node of the computer network to: receive a first amount of first token data type from a first computerized device associated with the computer network; and exchange the first amount of first token data type with a first amount of a conversion token data type; and assign a second computing node of the computer network to:
  • the at least one processor may be further configured to: transfer the first amount of first token data type to the second computerized device associated with the computer network; and receive the second amount of the conversion token data type.
  • the at least one processor may be further configured to: transfer the second amount of second token data type to the first computerized device associated with the computer network; and receive the first amount of the conversion token data type.
  • Each one of said at least first and second computing node of the computer network may be associated with a single blockchain, and each conversion from a token data type to a conversion token data type may be registered on a separate blockchain network.
  • At least one of said at least first and second computing node of the computer network may be configured to determine an exchange rate from each token data type to the conversion token data type.
  • the exchange rate may be determined for a predetermined time period.
  • At least some operations of the computer network may be carried out utilizing the processing power of computerized devices associated with the computer network.
  • the computer network may be associated with a decentralized blockchain network, and all operations of the computer network may be carried out automatically.
  • Fig. 1 shows a block diagram of an examplary computing device, according to some embodiments of the invention
  • FIG. 2 A shows a block diagram of a data conversion system, according to some embodiments of the invention.
  • FIG. 2B shows a block diagram of computer network, according to some embodiments of the invention.
  • FIG. 3A shows a block diagram of data type conversions in the computer network, according to some embodiments of the invention.
  • FIG. 3B schematically illustrates initial data type conversions between computerized devices with the data conversion system, according to some embodiments of the invention
  • FIG. 3C schematically illustrates final data type conversions between computerized devices with the data conversion system, according to some embodiments of the invention.
  • FIG. 4 shows a flowchart for a method of data conversion in a computer network, according to some embodiments of the invention.
  • the terms“plurality” and“a plurality” as used herein may include, for example,“multiple” or“two or more”.
  • the terms“plurality” or“a plurality” may be used throughout the specification to describe two or more components, devices, elements, units, parameters, or the like.
  • the term set when used herein may include one or more items.
  • the method embodiments described herein are not constrained to a particular order or sequence. Additionally, some of the described method embodiments or elements thereof can occur or be performed simultaneously, at the same point in time, or concurrently.
  • Data Token - when applied to data security is a non-sensitive equivalent data that substitutes a sensitive data element.
  • the data token is a reference (i.e. identifier) that maps back to the sensitive data through a tokenization system. This is the actual data of the token.
  • Token Data Type the type of the token data which can be different from the data itself.
  • Conversion Token - is a token that can be used for conversion between two token data types
  • methods and systems are provided for automatic validation of data conversion and/or exchange in a trustless decentralized computer network, with automatic identification of compatible requests for conversion and/or exchange between tokens with different data types and assignment of computing nodes to convert and/or exchange the data tokens.
  • conversion between different data types may be facilitated with at least one conversion token that is associated with the computer network, for instance a data token facilitating data exchange in an associated blockchain network or a data token including information of data type that was exchanged between at least two computing nodes of the computer network. It should be noted that while data tokens are discussed hereinafter, the following may also apply to any type of data exchange.
  • a device 100 may include a controller 105 that may be, for example, a central processing unit processor (CPU), a chip or any suitable computing or computational device, an operating system 115, a memory 120, executable code 125, a storage system 130 and optionally input devices 135 and output devices 140. Controller 105 (or one or more controllers or processors, possibly across multiple units or devices) may be configured to carry out methods described herein, and/or to execute or act as the various modules, units, etc. More than one computing device 100 may be included in, and one or more computing devices 100 may act as the components of, a system according to embodiments of the invention.
  • a controller 105 may be, for example, a central processing unit processor (CPU), a chip or any suitable computing or computational device, an operating system 115, a memory 120, executable code 125, a storage system 130 and optionally input devices 135 and output devices 140.
  • Controller 105 (or one or more controllers or processors, possibly across multiple units or devices) may be configured to carry out methods
  • Operating system 115 may be or may include any code segment (e.g., one similar to executable code 125 described herein) designed and/or configured to perform tasks involving coordination, scheduling, arbitration, supervising, controlling or otherwise managing operation of computing device 100, for example, scheduling execution of software programs or tasks or enabling software programs or other modules or units to communicate.
  • Operating system 115 may be a commercial operating system. It will be noted that an operating system 115 may be an optional component, e.g., in some embodiments, a system may include a computing device that does not require or include an operating system 115.
  • a computer system may be, or may include, a microcontroller, an application specific circuit (ASIC), a field programmable array (FPGA) and/or system on a chip (SOC) that may be used without an operating system.
  • ASIC application specific circuit
  • FPGA field programmable array
  • SOC system on a chip
  • Memory 120 may be or may include, for example, a Random Access Memory (RAM), a read only memory (ROM), a Dynamic RAM (DRAM), a Synchronous DRAM (SD-RAM), a double data rate (DDR) memory chip, a Flash memory, a volatile memory, a non-volatile memory, a cache memory, a buffer, a short term memory unit, a long term memory unit, or other suitable memory units or storage units.
  • Memory 120 may be or may include a plurality of, possibly different memory units.
  • Memory 120 may be a computer or processor non-transitory readable medium, or a computer non- transitory storage medium, e.g., a RAM.
  • Executable code 125 may be any executable code, e.g., an application, a program, a process, task or script. Executable code 125 may be executed by controller 105 possibly under control of operating system 115. Although, for the sake of clarity, a single item of executable code 125 is shown in Fig. 1, a system according to some embodiments of the invention may include a plurality of executable code segments similar to executable code 125 that may be loaded into memory 120 and cause controller 105 to carry out methods described herein.
  • Storage system 130 may be or may include, for example, a flash memory as known in the art, a memory that is internal to, or embedded in, a micro controller or chip as known in the art, a hard disk drive, a CD-Recordable (CD-R) drive, a Blu-ray disk (BD), a universal serial bus (ETSB) device or other suitable removable and/or fixed storage unit.
  • Content may be stored in storage system 130 and may be loaded from storage system 130 into memory 120 where it may be processed by controller 105.
  • controller 105 In some embodiments, some of the components shown in Fig. 1 may be omitted.
  • memory 120 may be a non-volatile memory having the storage capacity of storage system 130.
  • Input devices 135 may be or may include any suitable input devices, components or systems, e.g., a detachable keyboard or keypad, a mouse and the like.
  • Output devices 140 may include one or more (possibly detachable) displays or monitors, speakers and/or any other suitable output devices. Any applicable input/output (I/O) devices may be connected to computing device 100 as shown by blocks 135 and 140.
  • NIC network interface card
  • USB universal serial bus
  • input devices 135 and output device 140 may be operatively connected to computing device 100 as shown by blocks 135 and 140.
  • input devices 135 and output devices 140 may be used by a technician or engineer in order to connect to a computing device 100, update software and the like.
  • Input and/or output devices or components 135 and 140 may be adapted to interface or communicate.
  • Embodiments of the invention may include an article such as a computer or processor non-transitory readable medium, or a computer or processor non-transitory storage medium, such as for example a memory, a disk drive, or a USB flash memory, encoding, including or storing instructions, e.g., computer-executable instructions, which, when executed by a processor or controller, carry out methods disclosed herein.
  • a storage medium such as memory 120
  • computer-executable instructions such as executable code 125
  • controller such as controller 105.
  • the storage medium may include, but is not limited to, any type of disk including magneto-optical disks, semiconductor devices such as read-only memories (ROMs), random access memories (RAMs), such as a dynamic RAM (DRAM), erasable programmable read-only memories (EPROMs), flash memories, electrically erasable programmable read-only memories (EEPROMs), magnetic or optical cards, or any type of media suitable for storing electronic instructions, including programmable storage devices.
  • ROMs read-only memories
  • RAMs random access memories
  • DRAM dynamic RAM
  • EPROMs erasable programmable read-only memories
  • flash memories electrically erasable programmable read-only memories (EEPROMs)
  • magnetic or optical cards or any type of media suitable for storing electronic instructions, including programmable storage devices.
  • Embodiments of the invention may include components such as, but not limited to, a plurality of central processing units (CPU) or any other suitable multi-purpose or specific processors or controllers (e.g., controllers similar to controller 105), a plurality of input units, a plurality of output units, a plurality of memory units, and a plurality of storage units.
  • a system may additionally include other suitable hardware components and/or software components.
  • a system may include or may be, for example, a personal computer, a desktop computer, a mobile computer, a laptop computer, a notebook computer, a terminal, a workstation, a server computer, a Personal Digital Assistant (PDA) device, a tablet computer, a network device, or any other suitable computing device.
  • PDA Personal Digital Assistant
  • a system may include or may be, for example, a plurality of components that include a respective plurality of central processing units, e.g., a plurality of CPUs as described, a plurality of chips, FPGAs or SOCs, a plurality of computer or network devices, or any other suitable computing device.
  • a system as described herein may include one or more devices such as the computing device 100.
  • FIG. 2A shows a block diagram of a data conversion system 200, according to some embodiments of the invention.
  • the direction of arrows in Fig. 2A may indicate the direction of information flow.
  • the data conversion system 200 may include a decentralized computer network 210 with a plurality of computing nodes 20 la, 20 lb, 20 lc.
  • Each computing node may include a processor (e.g., similar to controller 105 as shown in Fig. 1) and perform data type conversions and/or exchange for at least one specific token data type. It should be noted that while only three computing nodes are shown in Fig. 2A, the computer network 210 may include any number of such nodes.
  • conversion and/or exchange between data tokens may refer to conversion between different data types.
  • conversion and/or exchange between data tokens may refer to conversion and/or exchange between data types having different data formats (e.g., exchanging an IoT data type with an electric power meter data type).
  • conversion and/or exchange between data types may be carried out with data tokens having different cryptographic codes (e.g., converting a data token with SHA-256 hash for a data token with MD5 hash cryptographic codes).
  • each computing node may include memory and a dedicated operating system (e.g., similar to memory 120 and a dedicated operating system 115 as shown in Fig. 1) such that a conversion algorithm (e.g., similar to executable code 125 as shown in Fig. 1) may be implemented in computer network 210 in each computing nodes 20 la, 20 lb, 20 lc.
  • a conversion algorithm e.g., similar to executable code 125 as shown in Fig. 1
  • computing nodes 20 la, 20 lb, 20 lc may be connected via a network , for instance associated with a decentralized blockchain network.
  • the network is shown in the figures only partially, but may be one or more networks connecting all relevant devices, such as the internet.
  • decentralized computer network 210 may include at least two communication modules 202 configured to receive conversion requests for data 205a, 205b (Fig. 3A) from a plurality of computerized devices 203, 204 associated with the computer network 210.
  • a user may use computerized device 204 (e.g., a PC, similar to device 100 as shown in Fig. 1) with a dedicated algorithm to allow data exchange with the decentralized computer network 210.
  • communication modules 202 may distribute the received conversion requests 205a, 205b throughout the computer network 210 such that each computing node 20 la, 20 lb, 20 lc may anonymously record all of the received conversion requests 205a, 205b, since the source and target of the requests are unaware of the each other thereby creating trustless data exchange.
  • communication modules 202 may only receive requests in unidirectional communication, whereby users of computerized devices 203, 204 associated with the computer network 210 may check operations of computer network 210 using a network connection (e.g., via the internet) to blockchain networks 22 la, 22 lb, 22 lc to observe transactions carried thereon, thus also reducing processing power on computer network 210 since computerized devices 203, 204 may broadcast requests 205a, 205b without a corresponding response for each request.
  • a network connection e.g., via the internet
  • users with data tokens are typically required to use dedicated software applications (or “wallets”) with their personal password (or private key) such that tokens may be transferred to a different node of that blockchain network.
  • users with data token may utilize data conversion system 200 to convert and/or exchange the data type of some or all of their tokens.
  • At least one computing node 20 la, 20 lb, 20 lc may be assigned by the computer network 210 to analyze the received conversion requests 205a, 205b and determine a first request 205a (e.g., as shown in Fig. 3A) corresponding to a first conversion 301 from a first token data type 21 la to a second token data type 21 lb and a second request 205b corresponding to a second conversion 302 from the second token data type 21 lb to the first token data type 21 la, the first and second conversions 301, 302 being opposite to each other, e.g. in the reverse direction.
  • a first request 205a e.g., as shown in Fig. 3A
  • a second request 205b corresponding to a second conversion 302 from the second token data type 21 lb to the first token data type 21 la
  • the at least one computing node 20 la, 20 lb, 20 lc may also determine a third request 205c corresponding to a third conversion 303 from the second token data type 21 lb to a third token data type 21 lc.
  • the first conversion 301 may be from type‘A’ to type‘B’
  • the second conversion 302 may be from type‘B’ to type‘C’
  • the third conversion 303 may be from type‘C’ to type‘A’ so that decentralized computer network 210 may determine an exchange between the first, second, and third conversions 301, 302, 303 to finally convert type‘A’ to‘C’.
  • the decentralized computer network 210 may determine and execute partial exchange between the first, second, and third conversions 301, 302, 303.
  • the computer network 210 may be associated with a decentralized blockchain network with dedicated conversion data tokens 206, and all operations of the computer network may be carried out automatically.
  • operations of conversion data token 206 such as transition between different computing nodes and/or computerized devices, may be registered on the associated decentralized blockchain network.
  • exchanges may be registered on the ledger of the corresponding blockchain network, while other operations (e.g., exchange rate determination, recording of requests, etc.) may be registered elsewhere, for instance on a dedicated decentralized database 250 as shown in Fig. 2B, thereby also reducing processing requirements of the associated decentralized blockchain network.
  • Token registration on a ledger may be, in some embodiments, carried out with registration of token exchange between at least two computing nodes (e.g., registering amount of tokens before and after the exchange in each computing node).
  • each token data type 21 la, 21 lb, 21 lc processed by computer network 210 may be associated with a single blockchain network 22 la, 22lb, 22 lc.
  • a data token 21 lb e.g., a token with information of internet of things, IOT, devices
  • IOT blockchain network 22 lb may be handled by an IOT blockchain network 22 lb.
  • each computing node 20la, 20lb, 20lc may store a predetermined amount (e.g., number of tokens) of conversion data tokens 206 in order to be able to carry out conversions and/or exchanges between data type tokens.
  • the conversion data token 206 may be utilized for data transfer with a blockchain network associated with the computer network 210, wherein the conversion data token 206 may differ from other data tokens in data type.
  • the conversion data token 206 may include data that may be transferred between computing nodes of the computer network 210 via an exchange of the conversion data token 206.
  • a single computing node 20la, 20lb, 20lc may be assigned by the computer network 210 to carry out each data type conversion.
  • a first computing node 20 la may be assigned to handle the first token data type 21 la and carry out the first conversion 301
  • second computing node 20 lb may be assigned to handle the second token data type 21 lb and carry out the second conversion 302.
  • computer network 210 may determine an exchange rate (e.g., for a predetermined time period) for each conversion between two data types such that an amount of data token for each exchange may be thereby determined.
  • An example of conversion between two data types is shown below in Figs. 3B-3C.
  • Fig. 2B shows a block diagram of computer network 210, according to some embodiments of the invention. The direction of arrows in Fig. 2B may indicate the direction of information flow.
  • computer network 210 may include at least one database 250, for instance each or some of the computing node 20 la, 20 lb, 20 lc may have corresponding databases 250 (e.g., similar to the storage system 130 as shown in Fig. 1), in order to store the received conversion requests 205.
  • all databases 250 may store the received conversion requests 205 in parallel and/or store the determined first conversion 301 and second conversion 302 in parallel.
  • the computer network 210 may be associated with a decentralized blockchain network with a dedicated conversion data token 206, and thus each database 250 may store a complete data ledger of the entire blockchain for exchanges of the conversion data token 206, such that operations of computer network 210 may be substantially simultaneously registered in each database 250.
  • computer network 210 may be configured to assign the first computing node 20 la to receive a first amount of first token data type 21 la from first computerized device 203 associated with the computer network in accordance with at least one conversion request 205a, 205b, and convert and/or exchange from the first amount of first token data type 21 la to a first amount of a conversion token data type 206.
  • Computer network 210 may also assign a second computing node 20 lb to receive a second amount of second token data type 21 lb from a second computerized device 204 associated with the computer network 210, and convert and/or exchange the second amount of second token data type 21 lb with a second amount of the conversion token data type 206.
  • the amount of conversion token data type 206 may correspond to an exchange rate from each token data type 21 la, 21 lb, 21 lc to the conversion token data type 206, for instance an aggregated exchange rate that may be determined for a predetermined time period (e.g., calculated every five minutes, or may be valid for only a certain time period) by at least one computing node 20la, 20lb, 20lc (e.g., selected randomly).
  • a predetermined time period e.g., calculated every five minutes, or may be valid for only a certain time period
  • an exchange rate may be determined for a predetermined time period (e.g., five minutes) and accordingly the amount of data tokens corresponding to that exchange rate may be determined (e.g., four tokens of type‘A’ in exchange of seven tokens of type‘B’) until the exchange rate changes.
  • each conversion from a token data type 21 la, 21 lb, 21 lc to a conversion token data type 206 may be at least partially registered on a separate blockchain network 22 la, 22 lb, 22 lc, as further described hereinafter.
  • At least some operations of the computer network 210 may be carried out utilizing the processing power of computerized devices 203, 204 associated with the computer network 210.
  • calculation of the aggregated exchange rate may be carried out utilizing the processing power of at least one computerized device 203, 204 and then distributed to computer network 210.
  • a first user of first computerized device 203 associated with computer network 210 may request a conversion and/or exchange from a first token data type 21 la in an amount of five tokens to be exchanged with a second token data type 21 lb in accordance with the determined exchange rate where each first token data type 21 la may be exchanged for two second token data type 21 lb.
  • a second user of second computerized device 204 associated with computer network 210 may request an opposite conversion and/or exchange, from a second token data type 21 lb in an amount of ten tokens to be exchanged with a first token data type 21 la in accordance with the determined exchange rate.
  • computer network 210 may assign the first computing node 20la for the first conversion 301, and assign the second computing node 20lb for the second conversion 302.
  • at least three conversions 301, 302, 303 may be calculated by computer network 210 to perform a complex exchange such that all parties receive the desired data type, for instance if a pair of opposite conversions is not identified.
  • FIG. 3A shows a block diagram of data type conversions 301, 302, 303 in the computer network 210, according to some embodiments of the invention.
  • the direction of arrows in Fig. 3A may indicate the direction of information flow.
  • computer network 210 may be configured to assign the first computing node 20 la to carry out the first conversion 301 (for the first conversion request 205a) and transfer the first amount of first token data type 21 la to the second computerized device 204, and receive the second amount of the conversion token data type 206.
  • computer network 210 may be configured to assign the second computing node 20lb to carry out the second conversion 302 (for the second conversion request 205b) and transfer the second amount of second token data type 21 lb to the first computerized device 203, and receive the first amount of the conversion token data type 206.
  • Computer network 210 may similarly be configured to assign the third computing node 20 lc to carry out the third conversion 303 (for the third conversion request 205c) and transfer a third amount of second token data type 21 lc to the first computerized device 203, and receive a third amount of the conversion token data type 206. It should be noted that each conversion and/or exchange between data types 301, 302, 303 may be accomplished with at least two computing nodes 20la, 20 lb, 20 lc, since each conversion request 205a, 205b, 205c requires two computing nodes 20 la, 20 lb, 20 lc (one for each token data type).
  • data conversion facilitated with conversion token data type 206 may be carried out with at least one smart contract, for instance utilizing‘ERC20’ compatible“Ethereum” blockchain network.
  • FIG. 3B-3C schematically illustrate data type conversions between computerized devices 203, 204 with data conversion system 200, according to some embodiments of the invention.
  • First computerized device 203 may send a first request 205a to computer network 210 for conversion of first data token type 21 la with second data token type 21 lb (to be determined as a first conversion 301), and similarly the second computerized device 204 may send a second request 205b to computer network 210 for conversion of second data token type 21 lb with first data token type 21 la (to be determined as a second conversion 302).
  • a first computing node 20 la associated with the first conversion 301 may receive a first amount of first data token type 21 la from the first computerized device 203 via a registered transaction in a first blockchain network 22 la and in exchange send a first amount of conversion token data type 206 to the first computerized device 203.
  • a second computing node 20lb associated with the second conversion 302 may receive a second amount of second data token type 21 lb from the second computerized device 204 via a registered transaction in a second blockchain network 22 lb and in exchange send a second amount of conversion token data type 206 to the second computerized device 204.
  • Sending an amount of data tokens may correspond to automatic registration on the ledger of an associated blockchain network that this amount of data tokens is exchanged between two parties, such that the target of the exchange owns the data tokens at the end of the exchange.
  • the first and second computerized devices 203, 204 are holding the conversion token data type 206, while the first and second computing nodes 20 la, 20 lb are holding (e.g., registered as owners of data tokens on a ledger of an associated blockchain network) the first and second data token type 21 la, 21 lb respectively.
  • a transaction may be registered in a blockchain network assigning a particular amount of data token type to the corresponding computing node.
  • the first amount of conversion token data type 206 may be transferred from the first computerized device 203 to the second computing node 20 lb in exchange of the second amount of second data token type 21 lb.
  • the second amount of conversion token data type 206 may be transferred from the second computerized device 204 to the first computing node 20 la in exchange of the first amount of first data token type 21 la such that the final transaction of data token type 21 la, 21 lb may also be registered on the corresponding blockchain network 22 la, 22lb.
  • transactions of the conversion token data type 206 may be registered on a ledger of a blockchain network associated with computer network 210.
  • each computerized device 203, 204 may receive the desired type of data token 21 la, 21 lb in a trustless (e.g., without a single party guaranteeing successful exchange) and anonymous manner wherein each party is unaware of the other parties and of the computing nodes that carried out the data conversion and/or exchange.
  • the decentralized computer network 210 of system 200 may allow decentralized validation of data exchanges, whereby each computerized device 203, 204 only sent a conversion request and decentralized computer network 210 automatically maintained and validated the execution of the exchange via the computing nodes.
  • each computing node 20la, 20lb handled only a single type of data token 21 la, 21 lb as well as the conversion token data type 206.
  • at least one computing node may be registered with several blockchain networks 22 la, 22 lb and handle multiple types of data tokens.
  • a first user of first computerized device 203 may use a dedicated software algorithm (e.g., a cryptocurrency wallet) associated with computer network 210 to send a first conversion request for conversion from six“Bitcoin” tokens 21 la owned by the first user (e.g., registered on a“Bitcoin” blockchain 22la) to a different type of token, e.g.,“Ripple” tokens 21 lb.
  • a second user of second computerized device 204 may use the dedicated software algorithm associated with computer network 210 to send a second conversion request for conversion from twenty“Ripple” tokens 21 lb owned by the second user to“Bitcoin” tokens 21 la.
  • Computer network 210 may receive conversion requests and determine a match between the first and second conversion requests, with a corresponding exchange rate of 1 :3 between“Bitcoin” and“Ripple” tokens (e.g., calculated for a predetermined time period with an aggregated average of exchange rates).
  • a first computing node 20 la may be assigned for conversion of “Bitcoin” tokens 21 la and automatically communicate with the“Bitcoin” blockchain 22la (e.g., via a network connection) to register an exchange of six“Bitcoin” tokens 21 la from an address associated with the first user to an address associated with the first computing node 20 la.
  • a second computing node 20lb may be assigned for conversion of“Ripple” tokens 21 lb and automatically communicate with the“Ripple” blockchain 22 lb to register an exchange of eighteen“Ripple” tokens 21 lb from an address associated with the second user to an address associated with the second computing node 20 lb, such that the second user keeps two “Ripple” tokens 21 lb in accordance with the calculated exchange rate.
  • the first and second users may receive conversion data tokens 206.
  • the first and second users may receive three and nine conversion data tokens 206 respectively in accordance with a conversion token exchange rate, and the exchange registered on a blockchain network associated with the computer network 210.
  • the first computing node 20 la may register on the“Bitcoin” blockchain 22 la an exchange of six“Bitcoin” tokens 21 la to the address associated with the second computerized device 204, while nine conversion data tokens 206 may be exchanged from the second computerized device 204 to the first computing node 20 la.
  • the second computing node 20 lb may register on the “Ripple” blockchain 22lb an exchange of eighteen “Ripple” tokens 21 lb to the address associated with the first computerized device 203, while three conversion data tokens 206 may be exchanged from the first computerized device 203 to the second computing node 20 lb.
  • each user may receive the desire token without knowing and/or trusting other parties involved with the exchange, wherein tokens of different data formats were exchanged (or converted).
  • FIG. 4 shows a flowchart for a method of data conversion in a computer network, according to some embodiments of the invention.
  • At least one processor (e.g., in a computing node) of the computer network 210 may receive 401 a plurality of requests 205 for conversion between tokens 21 la, 21 lb, 21 lc with different data types.
  • the at least one processor may determine 402 a first request 205a corresponding to a first conversion 301 from a first token data type 21 la to a second token data type 21 lb, and a second request 205b corresponding to a second conversion 302 from the second token data type 21 lb to the first token data type 21 la, the first and second conversions 301, 302 being opposite to each other.
  • the at least one processor may receive 403 a first amount of the first token data type 21 la from a first computerized device 203 associated with the computer network 210, and convert and/or exchange 404 the first amount of first token data type 21 la with a first amount of a conversion token data type 206.
  • the at least one processor may receive 405 a second amount of second token data type 21 lb from a second computerized device 204 associated with the computer network 210, and convert and/or exchange 406 the second amount of second token data type 21 lb with a second amount of the conversion token data type 206.
  • Embodiments of the present invention may allow conversion and/or exchange between data tokens or between data types having different data formats (e.g., exchanging an IoT data type with an electric power meter data type).
  • Current token/blockchain technology does not allow such conversion between data tokens or between data types as provided above, and thus, embodiments of the present invention improve the existing token technology.

Landscapes

  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Engineering & Computer Science (AREA)
  • Finance (AREA)
  • General Physics & Mathematics (AREA)
  • Strategic Management (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • Theoretical Computer Science (AREA)
  • Economics (AREA)
  • Development Economics (AREA)
  • Marketing (AREA)
  • Technology Law (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

L'invention concerne un procédé de conversion de données dans un réseau informatique comprenant une pluralité de nœuds de calcul, chaque nœud de calcul comprenant un processeur, le procédé comprenant : la réception, par au moins un processeur, d'une pluralité de demandes de conversion entre des jetons ayant différents types de données ; la détermination d'une première demande correspondant à une première conversion d'un premier type de données de jeton à un deuxième type de données de jeton et d'une deuxième demande correspondant à une deuxième conversion du deuxième type de données de jeton au premier type de données de jeton ; l'attribution d'un premier nœud du réseau informatique pour : recevoir une première quantité du premier type de données de jeton depuis un premier dispositif informatisé ; et échanger la première quantité de premier type de données de jeton avec une première quantité d'un type de données de jeton de conversion ; et l'attribution d'un deuxième nœud du réseau informatique pour : recevoir une deuxième quantité de deuxième type de données de jeton depuis un deuxième dispositif informatisé ; et échanger la deuxième quantité de deuxième type de données de jeton avec une deuxième quantité du type de données de jeton de conversion, le jeton de conversion étant associé au réseau informatique et la quantité de type de données de jeton de conversion correspondant à un taux d'échange entre chaque type de données de jeton et le type de données de jeton de conversion.
PCT/IB2019/050063 2018-01-29 2019-01-04 Système et procédé de validation décentralisée d'échange de données dans un réseau informatique WO2019145799A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201862623047P 2018-01-29 2018-01-29
US62/623,047 2018-01-29

Publications (1)

Publication Number Publication Date
WO2019145799A1 true WO2019145799A1 (fr) 2019-08-01

Family

ID=67394557

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2019/050063 WO2019145799A1 (fr) 2018-01-29 2019-01-04 Système et procédé de validation décentralisée d'échange de données dans un réseau informatique

Country Status (1)

Country Link
WO (1) WO2019145799A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220156725A1 (en) * 2020-11-18 2022-05-19 International Business Machines Corporation Cross-chain settlement mechanism
WO2022125726A1 (fr) * 2020-12-09 2022-06-16 Wellfield Technology Ir Limited Système et procédé d'échange décentralisé de contenus numériques dans un réseau informatique

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150170112A1 (en) * 2013-10-04 2015-06-18 Erly Dalvo DeCastro Systems and methods for providing multi-currency platforms comprising means for exchanging and interconverting tangible and virtual currencies in various transactions, banking operations, and wealth management scenarios
US20150363876A1 (en) * 2014-06-16 2015-12-17 Bank Of America Corporation Cryptocurrency Transformation System
US20160092988A1 (en) * 2014-09-30 2016-03-31 Raistone, Inc. Systems and methods for transferring digital assests using a de-centralized exchange
US20170154331A1 (en) * 2015-11-30 2017-06-01 ShapeShift Systems and methods for improving security in blockchain-asset exchange
WO2017145017A1 (fr) * 2016-02-23 2017-08-31 nChain Holdings Limited Procédés et systèmes de transfert efficace d'entités sur une chaîne de blocs

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150170112A1 (en) * 2013-10-04 2015-06-18 Erly Dalvo DeCastro Systems and methods for providing multi-currency platforms comprising means for exchanging and interconverting tangible and virtual currencies in various transactions, banking operations, and wealth management scenarios
US20150363876A1 (en) * 2014-06-16 2015-12-17 Bank Of America Corporation Cryptocurrency Transformation System
US20160092988A1 (en) * 2014-09-30 2016-03-31 Raistone, Inc. Systems and methods for transferring digital assests using a de-centralized exchange
US20170154331A1 (en) * 2015-11-30 2017-06-01 ShapeShift Systems and methods for improving security in blockchain-asset exchange
WO2017145017A1 (fr) * 2016-02-23 2017-08-31 nChain Holdings Limited Procédés et systèmes de transfert efficace d'entités sur une chaîne de blocs

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220156725A1 (en) * 2020-11-18 2022-05-19 International Business Machines Corporation Cross-chain settlement mechanism
WO2022125726A1 (fr) * 2020-12-09 2022-06-16 Wellfield Technology Ir Limited Système et procédé d'échange décentralisé de contenus numériques dans un réseau informatique

Similar Documents

Publication Publication Date Title
CN108595157B (zh) 区块链数据的处理方法、装置、设备和存储介质
TWI706665B (zh) 基於區塊鏈的資料核對系統、方法、計算設備及儲存媒體
TWI743458B (zh) 一種並行化執行區塊鏈交易的方法、裝置及系統
US10579973B2 (en) System for efficient processing of transaction requests related to an account in a database
US10956596B2 (en) System and method for automatically securing sensitive data in public cloud using a serverless architecture
US20180276625A1 (en) Contract ratification by automated agents through distributed ledger technology
CN107196900A (zh) 一种共识校验的方法及装置
TW201822033A (zh) 資源處理方法及裝置
CN112130748B (zh) 一种数据访问方法、网卡及服务器
KR102450411B1 (ko) 블록체인 기반 트랜잭션 처리 방법, 장치 및 그 시스템
US11520737B2 (en) Blockchain-as-a-service integrated hybrid object storage system in multi-cloud computing environment
CN112685391B (zh) 一种服务数据迁移方法、装置、计算机设备和存储介质
CN111598575B (zh) 业务流程控制方法、装置、电子设备和可读存储介质
WO2019001125A1 (fr) Procédé et dispositif de traitement de fichiers de transaction, support de stockage et appareil informatique
WO2019145799A1 (fr) Système et procédé de validation décentralisée d'échange de données dans un réseau informatique
CN113220717A (zh) 基于区块链的数据核验方法及装置、电子设备
US11816109B2 (en) Data provision method in a data utilization system
US12026268B2 (en) Cloud server and method for controlling cloud server thereof
US9830173B1 (en) Proxy simulation service for testing stateless systems
CN107276998B (zh) 一种基于OpenSSL的性能优化方法及装置
CN112291321A (zh) 业务处理方法、装置及系统
TWI662486B (zh) 檢查分布式業務處理完整度的方法及裝置
WO2022125726A1 (fr) Système et procédé d'échange décentralisé de contenus numériques dans un réseau informatique
CN111949500B (zh) 资源匹配方法、装置、电子设备及可读存储介质
US11687542B2 (en) Techniques for in-memory data searching

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19744375

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19744375

Country of ref document: EP

Kind code of ref document: A1