WO2019145799A1

WO2019145799A1 - System and method for decentralized validation of data exchange in a computer network

Info

Publication number: WO2019145799A1
Application number: PCT/IB2019/050063
Authority: WO
Inventors: Levy Cohen; Limor ROZEN; Tamir AGMON; Dikla BATTAT
Original assignee: Seamless Logic Software Ltd
Current assignee: Seamless Logic Software Ltd
Priority date: 2018-01-29
Filing date: 2019-01-04
Publication date: 2019-08-01
Anticipated expiration: 2020-07-29

Abstract

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, a plurality of requests for conversion between tokens with different data types; determining 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 a first node of the computer network to: receive a first amount of the first token data type from a first computerized device; and exchange the first amount of first token data type with a first amount of a conversion token data type; and assigning a second node of the computer network to: receive a second amount of second token data type from a second computerized device; and exchange the second amount of second token data type with a second amount of the conversion token data type, wherein the conversion token is associated with the computer network, and wherein the amount of conversion token data type corresponds to an exchange rate between each token data type and the conversion token data type.

Description

SYSTEM AND METHOD FOR DECENTRALIZED VALIDATION OF DATA EXCHANGE IN A COMPUTER NETWORK

FIELD OF THE INVENTION

[001] 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.

BACKGROUND OF THE INVENTION

[002] It is desired that exchange of data or goods should only be carried out between trusted (or known) parties, such that at least the source and the target of the exchange are known to each other. In recent years blockchain technology has been integrated into multiple new domains such as shipping container management and medical record databases, while creating decentralized computer networks that are capable of performing complex computations without a central processor, and that allow various actions in at least pseudo-trustless environment. Each such decentralized computer network maintains a data ledger where all operations on the network are registered, and particularly each computing node of the network has a full copy of the ledger so that there is no need for a central processor to facilitate the computations.

[003] 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.

[004] Currently there is no decentralized solution for automatic matching and exchanging between different types of data tokens as well as exchanging between completely trustless and/or anonymous parties. 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’).

SUMMARY

[005] According to a first aspect of the present invention there is provided 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 exchange the second amount of second token data type with a second amount of the conversion token data type, wherein the conversion token is associated with the computer network, and wherein the amount of conversion token data type corresponds to an exchange rate between each token data type and the conversion token data type.

[006] 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. [007] The computer network may be associated with a decentralized blockchain network, and all operations of the computer network may be carried out automatically.

[008] Each conversion from a token data type to a conversion token data type may be registered on a separate blockchain network.

[009] The method may further comprise determining the exchange rate from each token data type to the conversion token data type.

[010] The exchange rate may be determined for a predetermined time period.

[011] At least some operations of the computer network may be carried out utilizing the processing power of computerized devices associated with the computer network.

[012] Each node of the computer network may be assigned to perform conversions for a specific token data type.

[013] According to a second aspect of the present invention there is provided a data conversion system, the 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: receive a second amount of second token data type from a second computerized device associated with the computer network; and exchange the second amount of second token data type with a second amount of the conversion token data type, wherein the conversion token is associated with the computer network, and wherein the amount of conversion token data type corresponds to an exchange rate from each token data type to the conversion token data type.

[014] 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.

[015] 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.

[016] 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.

[017] 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.

[018] The exchange rate may be determined for a predetermined time period.

[019] At least some operations of the computer network may be carried out utilizing the processing power of computerized devices associated with the computer network. [020] The computer network may be associated with a decentralized blockchain network, and all operations of the computer network may be carried out automatically.

BRIEF DESCRIPTION OF THE DRAWINGS

[021] The subject matter regarded as the invention is particularly pointed out and distinctly claimed in the concluding portion of the specification. The invention, however, both as to organization and method of operation, together with objects, features, and advantages thereof, may best be understood by reference to the following detailed description when read with the accompanying drawings in which:

[022] Fig. 1 shows a block diagram of an examplary computing device, according to some embodiments of the invention;

[023] Fig. 2 A shows a block diagram of a data conversion system, according to some embodiments of the invention;

[024] Fig. 2B shows a block diagram of computer network, according to some embodiments of the invention;

[025] Fig. 3A shows a block diagram of data type conversions in the computer network, according to some embodiments of the invention;

[026] Fig. 3B schematically illustrates initial data type conversions between computerized devices with the data conversion system, according to some embodiments of the invention;

[027] Fig. 3C schematically illustrates final data type conversions between computerized devices with the data conversion system, according to some embodiments of the invention; and

[028] Fig. 4 shows a flowchart for a method of data conversion in a computer network, according to some embodiments of the invention.

[029] It will be appreciated that for simplicity and clarity of illustration, elements shown in the figures have not necessarily been drawn to scale. For example, the dimensions of some of the elements may be exaggerated relative to other elements for clarity. Further, where considered appropriate, reference numerals may be repeated among the figures to indicate corresponding or analogous elements. DETAILED DESCRIPTION

[030] In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of the invention. However, it will be understood by those skilled in the art that the present invention may be practiced without these specific details. In other instances, well-known methods, procedures, and components have not been described in detail so as not to obscure the present invention.

[031] Although embodiments of the invention are not limited in this regard, discussions utilizing terms such as, for example, “processing,” “computing,” “calculating,”“determining,”“establishing”,“analyzing”,“checking”, or the like, may refer to operation(s) and/or process(es) of a computer, a computing platform, a computing system, or other electronic computing device, that manipulates and/or transforms data represented as physical (e.g., electronic) quantities within the computer’s registers and/or memories into other data similarly represented as physical quantities within the computer’s registers and/or memories or other information non- transitory storage medium that may store instructions to perform operations and/or processes. Although embodiments of the invention are not limited in this regard, 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. Unless explicitly stated, 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.

[032] Definitions:

[033] 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.

[034] Token Data Type - the type of the token data which can be different from the data itself. [035] Conversion Token - is a token that can be used for conversion between two token data types

[036] According to some embodiments, 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. In some embodiments, 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.

[037] Reference is made to Fig. 1, which shows a block diagram of an exemplary computing device, according to some embodiments of the invention. 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.

[038] 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. For example, 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.

[039] 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.

[040] 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.

[041] 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. In some embodiments, some of the components shown in Fig. 1 may be omitted. For example, memory 120 may be a non-volatile memory having the storage capacity of storage system 130. Accordingly, although shown as a separate component, storage system 130 may be embedded or included in memory 120. [042] 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. For example, a wired or wireless network interface card (NIC), a universal serial bus (USB) device or external hard drive may be included in input devices 135 and/or output devices 140. It will be recognized that any suitable number of input devices 135 and output device 140 may be operatively connected to computing device 100 as shown by blocks 135 and 140. For example, 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.

[043] 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. For example, a storage medium such as memory 120, computer-executable instructions such as executable code 125 and a controller such as controller 105.

[044] 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.

[045] 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. In some embodiments, 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.

[046] In some embodiments, 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. For example, a system as described herein may include one or more devices such as the computing device 100.

[047] Reference is made to Fig. 2A which 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.

[048] 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.

[049] According to some embodiments, conversion and/or exchange between data tokens may refer to conversion between different data types. For instance, 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). In some embodiments, 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).

[050] The various computing nodes described in the figures may include components such as shown in Fig. 1. For example, in some embodiments, 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. In some embodiments, 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.

[051] In some embodiments, 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. For example, 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.

[052] In some embodiments, 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. It should be noted that 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.

[053] In order to perform a transaction of data tokens in a single blockchain network, 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. In some embodiments, 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.

[054] According to some embodiments, 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. In some embodiments, 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. For example, the first conversion 301 may be from type‘A’ to type‘B’, the second conversion 302 may be from type‘B’ to type‘C’, and 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’. It should be noted that any other number of conversions may be determined such that a long chain of such conversions may be created to allow all parties to anonymously exchange their data tokens, as further described hereinafter. Also the decentralized computer network 210 may determine and execute partial exchange between the first, second, and third conversions 301, 302, 303.

[055] According to some embodiments, 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. In some embodiments, 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. For instance, 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). In some embodiments, 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. For example, a data token 21 lb (e.g., a token with information of internet of things, IOT, devices) may be handled by an IOT blockchain network 22 lb.

[056] It should be noted that since the majority of current blockchain networks use different technologies and/or different algorithms, formatting a conversion between different data types may be required in order to switch two data tokens.

[057] According to some embodiments, 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. For example, 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.

[058] According to some embodiments, a single computing node 20la, 20lb, 20lc may be assigned by the computer network 210 to carry out each data type conversion. For instance, 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, and second computing node 20 lb may be assigned to handle the second token data type 21 lb and carry out the second conversion 302. In some embodiments, 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. [059] Reference is made to Fig. 2B which 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.

[060] In some embodiments, 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. In some embodiments, 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. According to some embodiments, 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.

[061] Reference is made back to Fig. 2 A. According to some embodiments, 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. In some embodiments, 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). For example, 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. In some embodiments, 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.

[062] In some embodiments, 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. For example, 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.

[063] For example, a first user of first computerized device 203 associated with computer network 210 (e.g., associated with a dedicated software code embedded therein) 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. Thus, 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. In some embodiments, 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.

[064] It should be noted that using system 200 the overall processing power used for the conversion between different types of data tokens may be reduced since there is no longer a need to include third parties to calculate exchange rates, separately register on blockchain networks and validate transactions.

[065] Reference is made to Fig. 3A which 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.

[066] According to some embodiments, 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. Similarly, 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).

[067] According to some embodiments, 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.

[068] Reference is made to Figs. 3B-3C which schematically illustrate data type conversions between computerized devices 203, 204 with data conversion system 200, according to some embodiments of the invention.

[069] 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). [070] In the first conversion 301, 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. Similarly, in the second conversion 302, 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.

[071] It should be noted that at this stage, 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. For instance a transaction may be registered in a blockchain network assigning a particular amount of data token type to the corresponding computing node.

[072] At the final stage of the transaction, 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. Similarly, 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. In some embodiments, transactions of the conversion token data type 206 may be registered on a ledger of a blockchain network associated with computer network 210. [073] It should be noted that at the end of the transaction, 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. Thus, 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. Additionally, 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. In some embodiments, at least one computing node may be registered with several blockchain networks 22 la, 22 lb and handle multiple types of data tokens.

[074] In one example, 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.

[075] 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. Similarly, 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.

[076] In exchange of the“Bitcoin” 21 la and“Ripple” 21 lb tokens, the first and second users may receive conversion data tokens 206. For instance 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.

[077] At the final stage, 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. Similarly, 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. Thus, at the end of the exchange 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).

[078] Reference is made to Fig. 4 which 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. In some embodiments, 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. [079] In some embodiments, 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. In some embodiments, 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.

[080] 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.

[081] Unless explicitly stated, the method embodiments described herein are not constrained to a particular order in time or chronological sequence. Additionally, some of the described method elements may be skipped, or they may be repeated, during a sequence of operations of a method.

[082] Various embodiments have been presented. Each of these embodiments may of course include features from other embodiments presented, and embodiments not specifically described may include various features described herein.

Claims

1. 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 exchange the second amount of second token data type with a second amount of the conversion token data type,

wherein the conversion token is associated with the computer network, and wherein the amount of conversion token data type corresponds to an exchange rate between each token data type and the conversion token data type.

2. The method of claim 1, further comprising:

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.

3. The method of claim 1, wherein the computer network is associated with a decentralized blockchain network, and wherein all operations of the computer network are carried out automatically.

4. The method of claim 3, wherein each conversion from a token data type to a conversion token data type is registered on a separate blockchain network.

5. The method of claim 1, further comprising determining the exchange rate from each token data type to the conversion token data type.

6. The method of claim 5, wherein the exchange rate is determined for a predetermined time period.

7. The method of claim 1, wherein at least some operations of the computer network are carried out utilizing the processing power of computerized devices associated with the computer network.

8. The method of claim 1, wherein each node of the computer network is assigned to perform conversions for a specific token data type.

9. A data conversion system, the 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:

wherein the conversion token is associated with the computer network, and wherein the amount of conversion token data type corresponds to an exchange rate from each token data type to the conversion token data type.

10. The system of claim 9, wherein at least one of said at least first and second processor is 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.

11. The system of claim 10, wherein at least one of said at least first and second processor is 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.

12. The system of claim 9, wherein each one of said at least first and second computing node of the computer network is associated with a single blockchain, and wherein each conversion from a token data type to a conversion token data type is registered on a separate blockchain network.

13. The system of claim 9, wherein at least one of said at least first and second computing node of the computer network is configured to determine an exchange rate from each token data type to the conversion token data type.

14. The system of claim 13, wherein the exchange rate is determined for a predetermined time period.

15. The system of claim 9, wherein at least some operations of the computer network are carried out utilizing the processing power of computerized devices associated with the computer network.

16. The system of claim 9, wherein the computer network is associated with a decentralized blockchain network, and wherein all operations of the computer network are carried out automatically.

17. A non-transitory computer-readable medium storing a program causing a computer to execute the method of claim 1.