WO2018223777A1 - 数据交换系统、方法和装置 - Google Patents
数据交换系统、方法和装置 Download PDFInfo
- Publication number
- WO2018223777A1 WO2018223777A1 PCT/CN2018/083375 CN2018083375W WO2018223777A1 WO 2018223777 A1 WO2018223777 A1 WO 2018223777A1 CN 2018083375 W CN2018083375 W CN 2018083375W WO 2018223777 A1 WO2018223777 A1 WO 2018223777A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- data
- exchanged
- server
- storage address
- identifier
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/04—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
- H04L63/0428—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload
- H04L63/0435—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload wherein the sending and receiving network entities apply symmetric encryption, i.e. same key used for encryption and decryption
-
- 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/14—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols using a plurality of keys or algorithms
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/602—Providing cryptographic facilities or services
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
- G06F21/6209—Protecting access to data via a platform, e.g. using keys or access control rules to a single file or object, e.g. in a secure envelope, encrypted and accessed using a key, or with access control rules appended to the object itself
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/04—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
- H04L63/0428—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload
- H04L63/0442—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload wherein the sending and receiving network entities apply asymmetric encryption, i.e. different keys for encryption and decryption
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/104—Peer-to-peer [P2P] networks
- H04L67/1074—Peer-to-peer [P2P] networks for supporting data block transmission mechanisms
- H04L67/1078—Resource delivery mechanisms
-
- 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/06—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols the encryption apparatus using shift registers or memories for block-wise or stream coding, e.g. DES systems or RC4; Hash functions; Pseudorandom sequence generators
- H04L9/0618—Block ciphers, i.e. encrypting groups of characters of a plain text message using fixed encryption transformation
-
- 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/08—Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
- H04L9/0816—Key establishment, i.e. cryptographic processes or cryptographic protocols whereby a shared secret becomes available to two or more parties, for subsequent use
- H04L9/0819—Key transport or distribution, i.e. key establishment techniques where one party creates or otherwise obtains a secret value, and securely transfers it to the other(s)
-
- 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/08—Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
- H04L9/0816—Key establishment, i.e. cryptographic processes or cryptographic protocols whereby a shared secret becomes available to two or more parties, for subsequent use
- H04L9/0819—Key transport or distribution, i.e. key establishment techniques where one party creates or otherwise obtains a secret value, and securely transfers it to the other(s)
- H04L9/0825—Key transport or distribution, i.e. key establishment techniques where one party creates or otherwise obtains a secret value, and securely transfers it to the other(s) using asymmetric-key encryption or public key infrastructure [PKI], e.g. key signature or public key certificates
-
- 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/08—Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
- H04L9/0861—Generation of secret information including derivation or calculation of cryptographic keys or passwords
-
- 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/14—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols using a plurality of keys or algorithms
- H04L9/16—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols using a plurality of keys or algorithms the keys or algorithms being changed during operation
-
- 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/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
- H04L9/3236—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials using cryptographic hash functions
- H04L9/3239—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials using cryptographic hash functions involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD
-
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L2463/00—Additional details relating to network architectures or network communication protocols for network security covered by H04L63/00
- H04L2463/062—Additional details relating to network architectures or network communication protocols for network security covered by H04L63/00 applying encryption of the keys
Definitions
- the present application relates to the field of computer technologies, and in particular, to the field of Internet technologies, and in particular, to a data exchange system, method and apparatus.
- Data exchange centers are usually established in existing data exchange systems. When the data exchange system performs data exchange, the data exchange center records and maintains the exchange process.
- the data exchange system is set up in the data exchange system, and all data exchange processes require the support of the data exchange center, which results in high construction and maintenance costs of the data exchange system.
- the purpose of the present application is to propose an improved data exchange system, method and apparatus to solve the technical problems mentioned in the background section above.
- the embodiment of the present application provides a data exchange system, where the system includes a first server and a second server, and the first server is configured to acquire a data identifier to be exchanged according to the requirement information, and store the data identifier to be exchanged; Obtaining a storage address of the data identifier to be exchanged; encrypting the storage address of the data to be exchanged to generate a first encrypted storage address; and second server for obtaining the first encrypted storage address from the first server; and performing the first encrypted storage address Decrypting, obtaining a storage address of the data identifier to be exchanged; obtaining a data identifier to be exchanged based on the storage address of the data to be exchanged; and searching for the to-be-exchanged data identifier to be exchanged from the pre-stored data set based on the data identifier to be exchanged Data, such that the first server obtains data to be exchanged from the second server, wherein the data set includes data and data identification.
- the second server is further configured to: store the data to be exchanged; obtain a storage address of the data to be exchanged; encrypt the storage address of the data to be exchanged, and generate a second encrypted storage address;
- the second encrypted storage address is obtained from the second server; the second encrypted storage address is decrypted, the storage address of the data to be exchanged is obtained, and the data to be exchanged is obtained based on the storage address of the data to be exchanged.
- the first server is further configured to: generate a symmetric key; encrypt the storage address of the data identifier to be exchanged by using the symmetric key, generate a first ciphertext; and set the first ciphertext based on the preset correspondence relationship Map to the first encrypted storage address.
- the first server is further configured to: encrypt the symmetric key by using a public key acquired in advance from the second server, to generate an encrypted symmetric key, where the second server stores the public key and the public The private key corresponding to the key.
- the second server is further configured to: obtain an encrypted symmetric key and a first encrypted storage address from the first server; decrypt the encrypted symmetric key by using a private key corresponding to the public key, to obtain a symmetric key Key: decrypting the first encrypted storage address by using the symmetric key and the preset correspondence, and obtaining the storage address of the data identifier to be exchanged.
- the second server is further configured to: encrypt the storage address of the data to be exchanged by using the symmetric key to generate a second ciphertext; and map the second ciphertext to the second encrypted storage based on the preset correspondence relationship address.
- the first server is further configured to: obtain a second encrypted storage address from the second server; decrypt the second encrypted storage address by using the symmetric key and the preset correspondence, and obtain a storage address of the data to be exchanged.
- the data to be exchanged is obtained based on the storage address of the data to be exchanged.
- the first server is further configured to: seal the resources corresponding to the data to be exchanged; after receiving the data to be exchanged sent by the second server, release the resources corresponding to the data to be exchanged, The second server is caused to acquire resources corresponding to the data to be exchanged.
- the embodiment of the present application provides a data exchange method for a first server, where the method includes: acquiring, according to the requirement information, the identifier of the data to be exchanged; storing the identifier of the data to be exchanged; and acquiring the identifier of the data to be exchanged.
- the address is encrypted by the storage address of the data to be exchanged, and the first encrypted storage address is generated, so that the second server obtains the first encrypted storage address from the first server, decrypts the first encrypted storage address, and obtains the identifier of the data to be exchanged.
- the storage address based on the storage address of the data to be exchanged, obtains the data identifier to be exchanged, and searches for data to be exchanged, which is indicated by the data identifier to be exchanged, from the pre-stored data set, based on the data identifier to be exchanged, wherein the data set includes data And data identification; obtaining data to be exchanged from the second server.
- the embodiment of the present application provides a data exchange device for a first server, where the device includes: a first acquiring unit, configured to acquire a data identifier to be exchanged based on the requirement information; and a storage unit configured to be configured to use The storage unit identifier is stored; the second obtaining unit is configured to obtain a storage address of the data identifier to be exchanged; the encryption unit is configured to encrypt the storage address of the data identifier to be exchanged, and generate a first encrypted storage address, so that the first The second server obtains the first encrypted storage address from the first server, decrypts the first encrypted storage address, obtains the storage address of the data identifier to be exchanged, and obtains the data identifier to be exchanged based on the storage address of the data to be exchanged, based on the data to be exchanged. And the third obtaining unit configured to obtain the data to be exchanged from the second server. The data is collected from the data set to be exchanged.
- an embodiment of the present application provides a server, where the server includes: one or more processors; a storage device for storing one or more programs; and one or more programs when one or more programs are used by one or more processors Executing, causing one or more processors to implement the methods as described in the implementations of the second aspect.
- an embodiment of the present application provides a computer readable storage medium, where a computer program is stored thereon, and when the computer program is executed by a processor, the method described in the implementation manner of the second aspect is implemented.
- the data exchange system, method and device provided by the embodiment of the present application, firstly, the first server acquires the data identifier to be exchanged based on the requirement information, and stores the data identifier to be exchanged; after that, the first server encrypts the storage address of the exchange data identifier. Generating a first encrypted storage address; then, the second server obtains the first encrypted storage address from the first server, and decrypts it to obtain a storage address of the data identifier to be exchanged; and then, the second server identifies the data to be exchanged based on The storage address is used to obtain the data identifier to be exchanged.
- the second server searches for the data to be exchanged indicated by the data identifier to be exchanged from the pre-stored data set based on the data identifier to be exchanged, so that the first server obtains the data to be exchanged from the second server.
- Exchange data In the data exchange system, the data exchange center is omitted, and the point-to-point data exchange is directly performed between the first server and the second server, thereby saving the construction and maintenance cost of the data exchange system.
- FIG. 1 is a diagram of an exemplary system architecture of a data exchange system in accordance with an embodiment of the present application
- FIG. 2 is a timing diagram of one embodiment of a data exchange system in accordance with the present application.
- FIG. 3 is a timing diagram of still another embodiment of a data exchange system in accordance with the present application.
- FIG. 4 is a flow diagram of one embodiment of a data exchange method for a first server in accordance with the present application
- FIG. 5 is a schematic structural diagram of an embodiment of a data exchange device for a first server according to the present application.
- FIG. 6 is a block diagram showing the structure of a computer system suitable for implementing the server of the embodiment of the present application.
- FIG. 1 illustrates an exemplary system architecture 100 of a data exchange system in accordance with an embodiment of the present application.
- the system architecture 100 can include a terminal device 101, a first server 102, a second server 103, and networks 104, 105.
- the network 104 is used to provide a medium for the communication link between the terminal device 101 and the first server 102.
- the network 105 is used to provide a medium for the communication link between the first server 102 and the second server 103.
- the networks 104, 105 can include various types of connections, such as wired, wireless communication links, fiber optic cables, and the like.
- the terminal device 101 can interact with the first server 102 via the network 104 to receive or transmit a message or the like. For example, the terminal device 101 can transmit the demand information to the first server 102 via the network 104.
- the terminal device 101 may be various electronic devices including, but not limited to, a smart phone, a tablet computer, a laptop portable computer, a desktop computer, and the like.
- the first server 102 can interact with the second server 103 over the network 105 to receive or send messages and the like.
- the first server 102 may store the data identifier to be exchanged, and send the first encrypted storage address (the storage address of the encrypted data identifier to be exchanged) to the second server 103 through the network 105; the second server 103 may first The first encrypted storage address is subjected to analysis and the like to obtain the data identifier to be exchanged; then, the data to be exchanged is searched from the pre-stored data set based on the data identifier to be exchanged, and the data to be exchanged is sent to the first server through the network 105. 102.
- the data exchange method for the first server provided by the embodiment of the present application is generally performed by the first server 102. Accordingly, the data exchange device for the first server is generally disposed in the first server 102.
- terminal devices first server, second server, and network in FIG. 1 is merely illustrative. Depending on the implementation needs, there may be any number of terminal devices, first servers, second servers, and networks.
- timing 200 of one embodiment of a data exchange system in accordance with the present application is illustrated.
- the data exchange system in this embodiment may include a first server (such as the first server 102 shown in FIG. 1) and a second server (such as the second server 103 shown in FIG. 1).
- the first server is configured to obtain a data identifier to be exchanged based on the requirement information, store the identifier of the data to be exchanged, obtain a storage address of the data identifier to be exchanged, and encrypt the storage address of the data identifier to be exchanged to generate a first encrypted storage address. .
- a second server configured to obtain a first encrypted storage address from the first server, decrypt the first encrypted storage address, obtain a storage address of the data identifier to be exchanged, and obtain a data identifier to be exchanged based on the storage address of the data identifier to be exchanged;
- the data to be exchanged indicated by the data identifier to be exchanged is searched from the pre-stored data set, so that the first server obtains data to be exchanged from the second server, where the data set includes data and data identifiers.
- step 201 the first server acquires the data identifier to be exchanged based on the demand information.
- the first server (for example, the first server 102 shown in FIG. 1) can obtain the demand information from the client (for example, the terminal device 101 shown in FIG. 1) by using a wired connection manner or a wireless connection manner, and
- the data identifier to be exchanged is extracted from the demand information.
- the requirement information may include a data identifier to be exchanged.
- the data identifier can be composed of words, letters, numbers, symbols, etc., to uniquely identify the data.
- the data identifier to be exchanged can be used to uniquely identify the data to be exchanged.
- the data identification can include a data name and/or a data index.
- the second server (such as the second server 103 shown in FIG. 1) may pre-publish the data identifier of the exchangeable data stored in the second server. Users can view these data identifiers and find out the data identifiers to be exchanged from the data identifiers according to their own needs. Then, the user can send the demand information including the data identifier to be exchanged to the first server. Finally, the first server can analyze the demand information and extract the data identifier to be exchanged.
- the second server can issue data identifiers in various ways.
- the second server can write the data identification into the smart contract and issue the smart contract.
- the user can view the smart contract and find the data identifier to be exchanged from the smart contract according to his own needs.
- a smart contract is a set of promises defined in digital form, including agreements on which contract participants (such as the first server and the second server) can execute these commitments.
- a smart contract is essentially an executable computer code that works like an if-then statement for other computer programs. Smart contracts only interact with real-world assets in this way. When a pre-programmed condition is triggered, the smart contract enforces the corresponding contract terms.
- the requirement information may further include a resource value corresponding to the data to be exchanged
- the first server may seal the resource corresponding to the data to be exchanged.
- the resource may be a virtual currency, that is, a digital currency in the form of P2P (peer-to-peer).
- Peer-to-peer transmission means a decentralized payment system.
- the resource value can be the amount of the virtual currency.
- the second server may also issue a resource value corresponding to the data while publishing the data identifier. The user can obtain the resource value corresponding to the data to be exchanged while obtaining the identifier of the data to be exchanged.
- the user can then send demand information including the data identifier to be exchanged and the resource value corresponding to the data to be exchanged to the first server.
- the first server may analyze the demand information, extract the resource values corresponding to the data to be exchanged, and seal the resources corresponding to the data to be exchanged.
- the first server may encapsulate the resource corresponding to the data to be exchanged in the smart contract acquired from the second server. It should be noted that, before the first server releases the sealed resources, neither the first server nor the second server can operate on the sealed resources.
- step 202 the first server stores the exchanged data identifier.
- the first server may store the data identifier to be exchanged.
- the first server may store the data identifier to be exchanged in a local or third party server.
- the first server may store the data identifier to be exchanged locally.
- the data identifier to be exchanged may be stored locally in the form of a text file at the first server.
- step 203 the first server acquires a storage address of the data identifier to be exchanged.
- the first server may obtain the storage address of the data identifier to be exchanged.
- the storage address may be a specific storage path of the data to be exchanged identifier in the first server.
- step 204 the first server encrypts the storage address of the exchanged data identifier to generate a first encrypted storage address.
- the first server may encrypt the storage address of the data identifier to be exchanged to generate a first encrypted storage address.
- the first server may use various reversible encryption algorithms to encrypt the storage address of the data to be exchanged.
- the reversible encryption algorithm is a well-known technology widely studied and applied at present, and details are not described herein again.
- step 205 the second server obtains the first encrypted storage address from the first server.
- the second server may acquire the first encrypted storage address from the first server.
- the first server may directly send the first encrypted storage address to the second server.
- the first server may store the first encrypted storage address, and send the storage address of the first encrypted storage address to the second server. So that the second server obtains the first encrypted storage address according to the storage address of the first encrypted storage address.
- the first server may write the first encrypted storage address into the smart contract acquired from the second server, and store the smart contract locally. The first server can then send the storage address of the smart contract to the second server.
- the second server may acquire the smart contract from the first server according to the storage address of the smart contract, and extract the first encrypted storage address from the smart contract.
- step 206 the second server decrypts the first encrypted storage address to obtain a storage address of the data identifier to be exchanged.
- the second server may decrypt the first encrypted storage address to obtain a storage address of the data identifier to be exchanged.
- the second server may decrypt the first encrypted storage address by using a decryption algorithm corresponding to the encryption algorithm for encrypting the storage address of the first server to exchange the data identifier, thereby obtaining the storage address of the data identifier to be exchanged.
- step 207 the second server acquires the data identifier to be exchanged based on the storage address of the data identifier to be exchanged.
- the second server may obtain the data identifier to be exchanged from the first server.
- step 208 the second server searches for data to be exchanged indicated by the data identifier to be exchanged from the pre-stored data set based on the data identifier to be exchanged.
- the second server may search for data to be exchanged indicated by the data identifier to be exchanged from the pre-stored data set.
- the data set can include data and data identification.
- the data set can be stored locally in the second server in various ways.
- the data collection can be stored in the second server in the form of a text file.
- the data set can be stored in the second server in the form of a data table.
- Each row in the data table has a different data index, and each column of the data table has a different data name.
- the data identifier to be exchanged may be the data index to be exchanged and the data name to be exchanged
- the second server may first find the row of the data to be exchanged in the data table of the stored data set according to the data index to be exchanged; The name finds the data to be exchanged in the row where the data to be exchanged is located.
- step 209 the first server acquires data to be exchanged from the second server.
- the first server may acquire data to be exchanged from the second server.
- the second server may directly send the data to be exchanged to the first server.
- the second server may store the data to be exchanged; afterwards, the second server may obtain the storage address of the data to be exchanged, and exchange the The storage address of the data is encrypted to generate a second encrypted storage address; then, the first server may obtain the second encrypted storage address from the second server, and decrypt the second encrypted storage address to obtain the storage address of the data to be exchanged; The first server may acquire data to be exchanged from the second server based on the storage address of the data to be exchanged.
- the second server may write the second encrypted storage address into the smart contract acquired from the first server, and store the smart contract locally.
- the second server can then send the storage address of the smart contract to the first server.
- the first server can obtain the smart contract from the second server and extract the second encrypted storage address from the smart contract.
- the first server may seal the resources corresponding to the data to be exchanged, and release the data to be exchanged after receiving the data to be exchanged sent by the second server.
- Resources to enable the second server to acquire resources corresponding to the data to be exchanged may be encapsulate the resource corresponding to the data to be exchanged in the smart contract acquired by the second server, and after receiving the data to be exchanged sent by the second server, may trigger the first server to perform the storage.
- a smart contract having resources corresponding to the data to be exchanged to enable transmission of resources corresponding to the data to be exchanged to the second server.
- the first server acquires the to-be-exchanged data identifier based on the requirement information, and stores the exchanged data identifier; after that, the first server encrypts the storage address of the exchanged data identifier to generate the first Encrypting the storage address; then, the second server obtains the first encrypted storage address from the first server, and decrypts it to obtain the storage address of the data identifier to be exchanged; and then, the second server obtains the storage address based on the data identifier to be exchanged
- the second server searches for data to be exchanged indicated by the data identifier to be exchanged from the pre-stored data set based on the data identifier to be exchanged, so that the first server acquires data to be exchanged from the second server.
- the data exchange center is omitted, and the point-to-point data exchange is directly performed between the first server and the second server, thereby saving the construction and maintenance cost of the data exchange system.
- timing 300 of yet another embodiment of a data exchange system in accordance with the present application is shown.
- the data exchange system in this embodiment may include a first server (such as the first server 102 shown in FIG. 1) and a second server (such as the second server 103 shown in FIG. 1).
- the first server is configured to obtain the data identifier to be exchanged based on the requirement information, store the identifier of the data to be exchanged, obtain a storage address of the data identifier to be exchanged, generate a symmetric key, and use the symmetric key to treat the storage address of the data identifier.
- the second server stores a public key and a private key corresponding to the public key.
- a second server configured to obtain an encrypted symmetric key and a first encrypted storage address from the first server; decrypt the encrypted symmetric key by using a private key corresponding to the public key to obtain a symmetric key; and use the symmetric key and the pre- The corresponding relationship is used to decrypt the first encrypted storage address, obtain the storage address of the data identifier to be exchanged, obtain the data identifier to be exchanged based on the storage address of the data identifier to be exchanged, and search for the data set to be exchanged based on the data identifier to be exchanged.
- the first server is further configured to: obtain a second encrypted storage address from the second server; decrypt the second encrypted storage address by using the symmetric key and the preset correspondence, and obtain a storage address of the data to be exchanged; Store the address and obtain the data to be exchanged.
- step 301 the first server acquires the data identifier to be exchanged based on the demand information.
- the first server (for example, the first server 102 shown in FIG. 1) can obtain the demand information from the client (for example, the terminal device 101 shown in FIG. 1) by using a wired connection manner or a wireless connection manner, and
- the data identifier to be exchanged is extracted from the demand information.
- the requirement information may include a data identifier to be exchanged.
- the data identifier can be composed of words, letters, numbers, symbols, etc., to uniquely identify the data.
- the data identifier to be exchanged can be used to uniquely identify the data to be exchanged.
- the data identification can include a data name and/or a data index.
- step 302 the first server stores the exchanged data identifier.
- the first server may store the data identifier to be exchanged.
- the first server may store the data identifier to be exchanged in a local or third party server.
- the first server may store the data identifier to be exchanged locally.
- the data identifier to be exchanged may be stored locally in the form of a text file at the first server.
- step 303 the first server acquires a storage address of the data identifier to be exchanged.
- the first server may obtain the storage address of the data identifier to be exchanged.
- the storage address may be a specific storage path of the data to be exchanged identified in the first server.
- step 304 the first server generates a symmetric key.
- the first server can generate a symmetric key.
- the symmetric key may be used to encrypt the storage address of the data to be exchanged or the storage address of the data to be exchanged.
- Symmetric key encryption is also called private key encryption, that is, both parties that send and receive data must use the same key to encrypt and decrypt the plaintext.
- Symmetric key encryption algorithms may include, but are not limited to, DES (Data Encryption Standard), 3DES (Triple DES, Triple Data Encryption Standard), IDEA (International Data Encryption Algorithm), and FEAL (Fast Data Encipherment). Algorithm, packet encryption algorithm, etc.
- step 305 the first server encrypts the storage address of the data to be exchanged by using the symmetric key to generate a first ciphertext.
- the storage address of the data identifier to be exchanged may be encrypted by the first symmetric key to generate a first ciphertext.
- step 306 the first server maps the first ciphertext to the first encrypted storage address based on the preset correspondence.
- the first server may map the first ciphertext to the first encrypted storage address based on the preset correspondence.
- the distributed hash table may be pre-stored in the first server, and the distributed hash is used when the first server inputs the first ciphertext to the distributed hash table.
- the table may map the first ciphertext to the first encrypted storage address according to the corresponding mapping relationship.
- the distributed hash table is a data structure that associates a key (key) and a value (value) in some way.
- the hash function is also called a hash function, which can convert an input of arbitrary length (also called pre-map) into a fixed-length output through a hash algorithm, and the output is a hash value.
- step 307 the first server encrypts the symmetric key with a public key previously acquired from the second server to generate an encrypted symmetric key.
- the first server may use the public key to encrypt the symmetric key to generate an encryption.
- Symmetric key obtained in advance from a second server (for example, the second server 103 shown in FIG. 1)
- the first server may use the public key to encrypt the symmetric key to generate an encryption.
- Symmetric key The second server stores a public key and a private key corresponding to the public key, and issues a public key while publishing the data identifier.
- the public key and the private key are a key pair obtained by an algorithm (ie, a public key and a private key), the public key is a part of the key pair, and the private key is a non-public part.
- Public keys are typically used to encrypt session keys, verify digital signatures, or encrypt data that can be decrypted with the corresponding private key.
- the key pair obtained by this algorithm is guaranteed to be unique worldwide.
- this key pair if one piece of data is used to encrypt a piece of data, it must be decrypted with another key. For example, encrypting data with a public key must be decrypted with a private key. If it is encrypted with a private key, it must be decrypted with a public key, otherwise the decryption will not succeed.
- step 308 the second server obtains the encrypted symmetric key and the first encrypted storage address from the first server.
- the second server may acquire the first encrypted storage address and the encrypted symmetric key from the first server.
- the first server may directly send the first encrypted storage address and the encrypted symmetric key to the second server.
- the first server may store the first encrypted storage address and the encrypted symmetric key, and the first encryption is performed.
- the storage address and the storage address of the encrypted symmetric key are sent to the second server, so that the second server acquires the first encrypted storage address and the encrypted symmetric key according to the first encrypted storage address and the storage address of the encrypted symmetric key.
- the first server may write the first encrypted storage address and the encrypted symmetric key into the smart contract acquired from the second server, and The smart contract is stored locally.
- the first server can then send the storage address of the smart contract to the second server.
- the second server may acquire the smart contract from the first server according to the storage address of the smart contract, and extract the first encrypted storage address and the encrypted symmetric key from the smart contract.
- step 309 the second server decrypts the encrypted symmetric key by using the private key corresponding to the public key to obtain a symmetric key.
- the second server may decrypt the encrypted symmetric key by using the private key corresponding to the public key to obtain a symmetric key.
- step 310 the second server decrypts the first encrypted storage address by using the symmetric key and the preset correspondence, and obtains the storage address of the data identifier to be exchanged.
- the second server may decrypt the first encrypted storage address by using the symmetric key and the preset correspondence to obtain the storage address of the data identifier to be exchanged.
- the distributed hash table may also be pre-stored in the second server.
- the distributed hash table may map the first encrypted storage address to the first ciphertext according to the corresponding mapping relationship. Then, the second server may decrypt the first ciphertext by using the symmetric key to obtain a storage address of the data identifier to be exchanged.
- step 311 the second server acquires the data identifier to be exchanged based on the storage address of the data identifier to be exchanged.
- the second server may obtain the data identifier to be exchanged from the first server.
- step 312 the second server searches for data to be exchanged indicated by the data identifier to be exchanged from the pre-stored data set based on the data identifier to be exchanged.
- the second server may search for data to be exchanged indicated by the data identifier to be exchanged from the pre-stored data set.
- the data set can include data and data identification.
- step 313 the second server stores the exchanged data.
- the second server may store the data to be exchanged.
- the second server may store the data to be exchanged in a local or third party server.
- the second server can store the data to be exchanged locally.
- the data to be exchanged may be stored locally in the form of a text file on the second server.
- step 314 the second server obtains a storage address of the data to be exchanged.
- the second server may acquire the storage address of the data to be exchanged.
- the storage address may be a specific storage path of the data to be exchanged in the second server.
- step 315 the second server encrypts the storage address of the data to be exchanged using the symmetric key to generate a second ciphertext.
- the second server may encrypt the storage address of the data to be exchanged by using the symmetric key to generate a second ciphertext.
- step 316 the second server maps the second ciphertext to the second encrypted storage address based on the preset correspondence.
- the second server may map the second ciphertext to the second encrypted storage address based on the preset correspondence.
- step 317 the first server obtains a second encrypted storage address from the second server.
- the first server may acquire the second encrypted storage address from the second server.
- step 318 the first server decrypts the second encrypted storage address by using the symmetric key and the preset correspondence, and obtains the storage address of the data to be exchanged.
- the first server may decrypt the second encrypted storage address by using the symmetric key and the preset correspondence to obtain the storage address of the data to be exchanged.
- the first server may first input the second encrypted storage address into the distributed hash table to obtain the second ciphertext; and then decrypt the second ciphertext by using the symmetric key to obtain the storage of the data to be exchanged. address.
- step 319 the first server acquires data to be exchanged based on the storage address of the data to be exchanged.
- the first server may acquire data to be exchanged from the second server.
- the sequence 300 of the data exchange system in the present embodiment highlights the steps of encrypting and decrypting using the public key, the private key, and the symmetric key as compared with the embodiment corresponding to Fig. 2. Thereby the data exchange system can exchange data more safely and reliably.
- the process 400 for the data exchange method of the first server includes the following steps:
- Step 401 Acquire a data identifier to be exchanged based on the requirement information.
- the first server (for example, the first server 102 shown in FIG. 1) can obtain the demand information from the client (for example, the terminal device 101 shown in FIG. 1) by using a wired connection manner or a wireless connection manner, and
- the data identifier to be exchanged is extracted from the demand information.
- the requirement information may include a data identifier to be exchanged.
- the data identifier can be composed of words, letters, numbers, symbols, etc., to uniquely identify the data.
- the data identifier to be exchanged can be used to uniquely identify the data to be exchanged.
- the data identification can include a data name and/or a data index.
- step 402 the data identifier to be exchanged is stored.
- the first server may store the data identifier to be exchanged.
- the first server may store the data identifier to be exchanged in a local or third party server.
- the first server may store the data identifier to be exchanged locally.
- the data identifier to be exchanged may be stored locally in the form of a text file at the first server.
- Step 403 Acquire a storage address of the data identifier to be exchanged.
- the first server may obtain the storage address of the data identifier to be exchanged.
- the storage address may be a specific storage path of the data to be exchanged identifier in the first server.
- Step 404 Encrypt the storage address of the data to be exchanged to generate a first encrypted storage address.
- the first server may encrypt the storage address of the data identifier to be exchanged, and generate a first encrypted storage address to enable the second server (for example, The second server 103) shown in FIG. 1 acquires the first encrypted storage address from the first server, decrypts the first encrypted storage address, obtains the storage address of the data identifier to be exchanged, and acquires the storage address based on the data identifier to be exchanged.
- the data identifier is exchanged, and the data to be exchanged, which is indicated by the data identifier to be exchanged, is searched from the pre-stored data set, where the data set may include data and data identifiers.
- Step 405 Acquire data to be exchanged from the second server.
- the first server may obtain the data to be exchanged from the second server.
- the data exchange method for the first server provided by the embodiment of the present application firstly obtains the data identifier to be exchanged based on the requirement information, and stores the identifier of the exchanged data; and then encrypts the storage address of the data identifier to be exchanged to generate the first Encrypting the storage address, so that the second server obtains the first encrypted storage address from the first server, and decrypts the storage address to obtain the storage address of the data identifier to be exchanged, and obtains the data identifier to be exchanged based on the storage address of the data identifier to be exchanged.
- the data to be exchanged indicated by the data identifier to be exchanged is searched from the pre-stored data set based on the data identifier to be exchanged.
- the data to be exchanged is obtained from the second server.
- the entire data exchange process does not require the participation of the data exchange center, and the point-to-point data exchange is directly performed between the first server and the second server, thereby saving the construction and maintenance cost of the data exchange system.
- the present application provides an embodiment of a data exchange device for a first server, the device embodiment being the same as the method embodiment shown in FIG.
- the device can be specifically applied to various electronic devices.
- the data switching apparatus 500 for the first server shown in this embodiment may include: a first obtaining unit 501, a storage unit 502, a second obtaining unit 503, an encrypting unit 504, and a third obtaining unit 505. .
- the first obtaining unit 501 is configured to obtain the data identifier to be exchanged based on the requirement information
- the storage unit 502 is configured to store the data identifier to be exchanged.
- the second obtaining unit 503 is configured to obtain the data identifier to be exchanged.
- the storage unit 502 is configured to encrypt the storage address of the data identifier to be exchanged, and generate a first encrypted storage address, so that the second server obtains the first encrypted storage address from the first server, and performs the first encrypted storage address.
- Decrypting obtaining the storage address of the data identifier to be exchanged, obtaining the data identifier to be exchanged based on the storage address of the data to be exchanged, and searching for the to-be-exchanged data identifier to be exchanged from the pre-stored data set Data, wherein the data set includes data and data identifiers; and the third obtaining unit 505 is configured to obtain data to be exchanged from the second server.
- the data processing device 500 for the first server the specific processing of the first obtaining unit 501, the storage unit 502, the second obtaining unit 503, the encrypting unit 504, and the third obtaining unit 505
- the data processing device 500 for the first server the specific processing of the first obtaining unit 501, the storage unit 502, the second obtaining unit 503, the encrypting unit 504, and the third obtaining unit 505
- FIG. 6 a block diagram of a computer system 600 suitable for use in implementing a server of an embodiment of the present application is shown.
- the server shown in FIG. 6 is merely an example, and should not impose any limitation on the function and scope of use of the embodiments of the present application.
- computer system 600 includes a central processing unit (CPU) 601 that can be loaded into a program in random access memory (RAM) 603 according to a program stored in read only memory (ROM) 602 or from storage portion 608. And perform various appropriate actions and processes.
- RAM random access memory
- ROM read only memory
- RAM random access memory
- various programs and data required for the operation of the system 600 are also stored.
- the CPU 601, the ROM 602, and the RAM 603 are connected to each other through a bus 604.
- An input/output (I/O) interface 605 is also coupled to bus 604.
- the following components are connected to the I/O interface 605: an input portion 606 including a keyboard, a mouse, etc.; an output portion 607 including, for example, a cathode ray tube (CRT), a liquid crystal display (LCD), and the like, and a storage portion 608 including a hard disk or the like. And a communication portion 609 including a network interface card such as a LAN card, a modem, or the like. The communication section 609 performs communication processing via a network such as the Internet.
- Driver 610 is also coupled to I/O interface 605 as needed.
- a removable medium 611 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory or the like, is mounted on the drive 610 as needed so that a computer program read therefrom is installed into the storage portion 608 as needed.
- an embodiment of the present disclosure includes a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for executing the method illustrated in the flowchart.
- the computer program can be downloaded and installed from the network via communication portion 609, and/or installed from removable media 611.
- the central processing unit (CPU) 601 the above-described functions defined in the method of the present application are performed.
- the computer readable medium described above may be a computer readable signal medium or a computer readable storage medium or any combination of the two.
- the computer readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the above. More specific examples of computer readable storage media may include, but are not limited to, electrical connections having one or more wires, portable computer disks, hard disks, random access memory (RAM), read only memory (ROM), erasable Programmable read only memory (EPROM or flash memory), optical fiber, portable compact disk read only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination of the foregoing.
- a computer readable storage medium may be any tangible medium that can contain or store a program, which can be used by or in connection with an instruction execution system, apparatus or device.
- a computer readable signal medium may include a data signal that is propagated in the baseband or as part of a carrier, carrying computer readable program code. Such propagated data signals can take a variety of forms including, but not limited to, electromagnetic signals, optical signals, or any suitable combination of the foregoing.
- the computer readable signal medium can also be any computer readable medium other than a computer readable storage medium, which can transmit, propagate, or transport a program for use by or in connection with the instruction execution system, apparatus, or device.
- Program code embodied on a computer readable medium can be transmitted by any suitable medium, including but not limited to wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.
- each block of the flowchart or block diagram can represent a module, a program segment, or a portion of code that includes one or more of the logic functions for implementing the specified.
- Executable instructions can also occur in a different order than that illustrated in the drawings. For example, two successively represented blocks may in fact be executed substantially in parallel, and they may sometimes be executed in the reverse order, depending upon the functionality involved.
- each block of the block diagrams and/or flowcharts, and combinations of blocks in the block diagrams and/or flowcharts can be implemented in a dedicated hardware-based system that performs the specified function or operation. Or it can be implemented by a combination of dedicated hardware and computer instructions.
- the units involved in the embodiments of the present application may be implemented by software or by hardware.
- the described unit may also be disposed in the processor, for example, as a processor including a first acquisition unit, a storage unit, a second acquisition unit, an encryption unit, and a third acquisition unit.
- the name of these units does not constitute a limitation on the unit itself in some cases.
- the first obtaining unit may also be described as “a unit for obtaining data identifiers to be exchanged based on the demand information”.
- the present application further provides a computer readable medium, which may be included in a server described in the above embodiments; or may exist separately and not installed in the server.
- the computer readable medium carries one or more programs, and when the one or more programs are executed by the server, the server: obtains the data identifier to be exchanged based on the requirement information; stores the data identifier to be exchanged; and acquires the to be exchanged
- the storage address of the data identifier is encrypted; the storage address of the data to be exchanged is encrypted, and the first encrypted storage address is generated, so that the second server obtains the first encrypted storage address from the first server, and decrypts the first encrypted storage address to obtain the
- the storage address of the data identifier is exchanged, and the data identifier to be exchanged is obtained based on the storage address of the data to be exchanged, and the data to be exchanged is searched for, according to the data identifier to be exchanged, the data to be exchanged indicated by the data identifier to be exchanged is searched from
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- General Engineering & Computer Science (AREA)
- Computer Hardware Design (AREA)
- Theoretical Computer Science (AREA)
- Computing Systems (AREA)
- Health & Medical Sciences (AREA)
- Physics & Mathematics (AREA)
- Software Systems (AREA)
- General Physics & Mathematics (AREA)
- General Health & Medical Sciences (AREA)
- Bioethics (AREA)
- Storage Device Security (AREA)
- Information Transfer Between Computers (AREA)
Abstract
本申请公开了数据交换系统、方法和装置。该系统的一具体实施方式包括:第一服务器,用于基于需求信息,获取待交换数据标识;对待交换数据标识进行存储;获取待交换数据标识的存储地址;对待交换数据标识的存储地址进行加密,生成第一加密存储地址;第二服务器,用于从第一服务器获取第一加密存储地址;对第一加密存储地址进行解密,获取待交换数据标识的存储地址;基于待交换数据标识的存储地址,获取待交换数据标识;基于待交换数据标识,从预先存储的数据集合中查找出待交换数据标识所指示的待交换数据,以使第一服务器从第二服务器获取待交换数据。该实施方式节省了数据交换系统的建设与维护成本。
Description
相关申请的交叉引用
本专利申请要求于2017年6月6日提交的、申请号为201710418271.2、申请人为北京京东世纪贸易有限公司和北京京东尚科信息技术有限公司、发明名称为“数据交换系统、方法和装置”的中国专利申请的优先权,该申请的全文以引用的方式并入本申请中。
本申请涉及计算机技术领域,具体涉及互联网技术领域,尤其涉及数据交换系统、方法和装置。
随着大数据时代的到来,数据的交换与共享也变得越来越重要。现有的数据交换系统中通常会设立数据交换中心。在数据交换系统进行数据交换时,数据交换中心对交换过程进行记录、维护等操作。
然而,数据交换系统中设立数据交换中心,并且所有的数据交换过程均需要数据交换中心提供支持,这样就导致数据交换系统的建设与维护成本较高。
发明内容
本申请的目的在于提出一种改进的数据交换系统、方法和装置,来解决以上背景技术部分提到的技术问题。
第一方面,本申请实施例提供了一种数据交换系统,该系统包括第一服务器和第二服务器;第一服务器,用于基于需求信息,获取待交换数据标识;对待交换数据标识进行存储;获取待交换数据标识的存储地址;对待交换数据标识的存储地址进行加密,生成第一加密存储地址;第二服务器,用于从第一服务器获取第一加密存储地址;对 第一加密存储地址进行解密,获取待交换数据标识的存储地址;基于待交换数据标识的存储地址,获取待交换数据标识;基于待交换数据标识,从预先存储的数据集合中查找出待交换数据标识所指示的待交换数据,以使第一服务器从第二服务器获取待交换数据,其中,数据集合包括数据和数据标识。
在一些实施例中,第二服务器,还用于:对待交换数据进行存储;获取待交换数据的存储地址;对待交换数据的存储地址进行加密,生成第二加密存储地址;第一服务器,还用于:从第二服务器获取第二加密存储地址;对第二加密存储地址进行解密,获取待交换数据的存储地址;基于待交换数据的存储地址,获取待交换数据。
在一些实施例中,第一服务器,还用于:生成对称密钥;利用对称密钥对待交换数据标识的存储地址进行加密,生成第一密文;基于预设对应关系,将第一密文映射成第一加密存储地址。
在一些实施例中,第一服务器,还用于:利用从第二服务器预先获取的公钥对对称密钥进行加密,生成加密对称密钥,其中,第二服务器中存储有公钥和与公钥相对应的私钥。
在一些实施例中,第二服务器,还用于:从第一服务器获取加密对称密钥和第一加密存储地址;利用与公钥相对应的私钥对加密对称密钥进行解密,获取对称密钥;利用对称密钥和预设对应关系对第一加密存储地址进行解密,获取待交换数据标识的存储地址。
在一些实施例中,第二服务器,还用于:利用对称密钥对待交换数据的存储地址进行加密,生成第二密文;基于预设对应关系,将第二密文映射成第二加密存储地址。
在一些实施例中,第一服务器,还用于:从第二服务器获取第二加密存储地址;利用对称密钥和预设对应关系对第二加密存储地址进行解密,获取待交换数据的存储地址;基于待交换数据的存储地址,获取待交换数据。
在一些实施例中,第一服务器,还用于:对与待交换数据相对应的资源进行封存;在接收到第二服务器发送的待交换数据之后,释放与待交换数据相对应的资源,以使第二服务器获取与待交换数据相对 应的资源。
第二方面,本申请实施例提供了一种用于第一服务器的数据交换方法,该方法包括:基于需求信息,获取待交换数据标识;对待交换数据标识进行存储;获取待交换数据标识的存储地址;对待交换数据标识的存储地址进行加密,生成第一加密存储地址,以使第二服务器从第一服务器获取第一加密存储地址,对第一加密存储地址进行解密,获取待交换数据标识的存储地址,基于待交换数据标识的存储地址,获取待交换数据标识,基于待交换数据标识,从预先存储的数据集合中查找出待交换数据标识所指示的待交换数据,其中,数据集合包括数据和数据标识;从第二服务器获取待交换数据。
第三方面,本申请实施例提供了一种用于第一服务器的数据交换装置,该装置包括:第一获取单元,配置用于基于需求信息,获取待交换数据标识;存储单元,配置用于对待交换数据标识进行存储;第二获取单元,配置用于获取待交换数据标识的存储地址;加密单元,配置用于对待交换数据标识的存储地址进行加密,生成第一加密存储地址,以使第二服务器从第一服务器获取第一加密存储地址,对第一加密存储地址进行解密,获取待交换数据标识的存储地址,基于待交换数据标识的存储地址,获取待交换数据标识,基于待交换数据标识,从预先存储的数据集合中查找出待交换数据标识所指示的待交换数据,其中,数据集合包括数据和数据标识;第三获取单元,配置用于从第二服务器获取待交换数据。
第四方面,本申请实施例提供了一种服务器,该服务器包括:一个或多个处理器;存储装置,用于存储一个或多个程序;当一个或多个程序被一个或多个处理器执行,使得一个或多个处理器实现如第二方面中实现方式描述的方法。
第五方面,本申请实施例提供了一种计算机可读存储介质,其上存储有计算机程序,该计算机程序被处理器执行时实现如第二方面中实现方式描述的方法。
本申请实施例提供的数据交换系统、方法和装置,首先,第一服务器基于需求信息获取待交换数据标识,并对待交换数据标识进行存 储;之后,第一服务器对待交换数据标识的存储地址进行加密,生成第一加密存储地址;而后,第二服务器从第一服务器获取第一加密存储地址,并对其进行解密以获取待交换数据标识的存储地址;然后,第二服务器基于待交换数据标识的存储地址,获取待交换数据标识;最后,第二服务器基于待交换数据标识从预先存储的数据集合中查找出待交换数据标识所指示的待交换数据,以使第一服务器从第二服务器获取待交换数据。数据交换系统中省去数据交换中心,第一服务器与第二服务器之间直接进行点对点的数据交换,从而节省了数据交换系统的建设与维护成本。
通过阅读参照以下附图所作的对非限制性实施例所作的详细描述,本申请的其它特征、目的和优点将会变得更明显:
图1是根据本申请实施例的数据交换系统的示例性系统架构图;
图2是根据本申请的数据交换系统的一个实施例的时序图;
图3是根据本申请的数据交换系统的又一个实施例的时序图;
图4是根据本申请的用于第一服务器的数据交换方法的一个实施例的流程图;
图5是根据本申请的用于第一服务器的数据交换装置的一个实施例的结构示意图;
图6是适于用来实现本申请实施例的服务器的计算机系统的结构示意图。
下面结合附图和实施例对本申请作进一步的详细说明。可以理解的是,此处所描述的具体实施例仅仅用于解释相关发明,而非对该发明的限定。另外还需要说明的是,为了便于描述,附图中仅示出了与有关发明相关的部分。
需要说明的是,在不冲突的情况下,本申请中的实施例及实施例中的特征可以相互组合。下面将参考附图并结合实施例来详细说明本 申请。
图1示出了根据本申请实施例的数据交换系统的示例性系统架构100。
如图1所示,系统架构100可以包括终端设备101,第一服务器102,第二服务器103和网络104、105。网络104用以在终端设备101和第一服务器102之间提供通信链路的介质。网络105用以在第一服务器102和第二服务器103之间提供通信链路的介质。网络104、105可以包括各种连接类型,例如有线、无线通信链路或者光纤电缆等等。
终端设备101可以通过网络104与第一服务器102交互,以接收或发送消息等。例如终端设备101可以通过网络104向第一服务器102发送需求信息。其中,终端设备101可以是各种电子设备,包括但不限于智能手机、平板电脑、膝上型便携计算机和台式计算机等等。
第一服务器102可以通过网络105与第二服务器103交互,以接收或发送消息等。例如,第一服务器102可以对待交换数据标识进行存储,并通过网络105将第一加密存储地址(加密后的待交换数据标识的存储地址)发送至第二服务器103;第二服务器103可以首先对第一加密存储地址进行分析等处理,以获取待交换数据标识;然后,基于待交换数据标识从预先存储的数据集合中查找出待交换数据,并通过网络105将待交换数据发送至第一服务器102。
需要说明的是,本申请实施例所提供的用于第一服务器的数据交换方法一般由第一服务器102执行,相应地,用于第一服务器的数据交换装置一般设置于第一服务器102中。
应该理解,图1中的终端设备、第一服务器、第二服务器和网络的数目仅仅是示意性的。根据实现需要,可以具有任意数目的终端设备、第一服务器、第二服务器和网络。
继续参考图2,其示出了根据本申请的数据交换系统的一个实施例的时序200。
本实施例中的数据交换系统可以包括第一服务器(例如图1所示的第一服务器102)和第二服务器(例如图1所示的第二服务器103)。其中,第一服务器,用于基于需求信息,获取待交换数据标识;对待 交换数据标识进行存储;获取待交换数据标识的存储地址;对待交换数据标识的存储地址进行加密,生成第一加密存储地址。第二服务器,用于从第一服务器获取第一加密存储地址;对第一加密存储地址进行解密,获取待交换数据标识的存储地址;基于待交换数据标识的存储地址,获取待交换数据标识;基于待交换数据标识,从预先存储的数据集合中查找出待交换数据标识所指示的待交换数据,以使第一服务器从第二服务器获取待交换数据,其中,数据集合包括数据和数据标识。
如图2所示,在步骤201中,第一服务器基于需求信息,获取待交换数据标识。
在本实施例中,第一服务器(例如图1所示的第一服务器102)可以通过有线连接方式或者无线连接方式从客户端(例如图1所示的终端设备101)获取需求信息,并从需求信息中提取出待交换数据标识。其中,需求信息可以包括待交换数据标识。数据标识可以由文字、字母、数字、符号等组成,用来唯一识别数据。待交换数据标识可以用来唯一标识待交换数据。作为示例,数据标识可以包括数据名和/或数据索引。
在本实施例中,第二服务器(例如图1所示的第二服务器103)可以预先发布第二服务器中存储的、可交换的数据的数据标识。用户可以查看这些数据标识,并根据自己的需求,从数据标识中查找出待交换数据标识。然后,用户可以向第一服务器发送包括待交换数据标识的需求信息。最后,第一服务器可以对需求信息进行分析,从中提取出待交换数据标识。
在这里,第二服务器可以通过各种方式发布数据标识。例如,第二服务器可以将数据标识写入智能合约中,并发布该智能合约。这样,用户可以查看该智能合约,并根据自己的需求,从该智能合约中查找出待交换数据标识。其中,智能合约是一套以数字形式定义的承诺(promises),包括合约参与方(例如第一服务器和第二服务器)可以在上面执行这些承诺的协议。智能合约本质上是可执行的计算机代码,其工作原理类似于其它计算机程序的if-then(如果-则)语句。智能合 约只是以这种方式与真实世界的资产进行交互。当一个预先编好的条件被触发时,智能合约执行相应的合同条款。
在本实施例的一些可选的实现方式中,需求信息中还可以包括与待交换数据相对应的资源值,第一服务器可以对与待交换数据相对应的资源进行封存。其中,资源可以是虚拟货币,即一种P2P(点对点)形式的数字货币。点对点的传输意味着一个去中心化的支付系统。资源值可以是虚拟货币的金额。具体地,第二服务器在发布数据标识的同时,还可以发布与数据相对应的资源值。用户可以在获取待交换数据标识的同时,获取与待交换数据相对应的资源值。然后用户可以将向第一服务器发送包括待交换数据标识和与待交换数据相对应的资源值的需求信息。最后,第一服务器可以对需求信息进行分析,从中提取出与待交换数据相对应的资源值,并对与待交换数据相对应的资源进行封存。作为示例,第一服务器可以将与待交换数据相对应的资源封存在从第二服务器所获取到的智能合约中。需要说明的是,在第一服务器对封存的资源释放之前,第一服务器与第二服务器均不能对封存的资源进行操作。
在步骤202中,第一服务器对待交换数据标识进行存储。
在本实施例中,基于步骤201中所获取到的待交换数据标识,第一服务器可以对待交换数据标识进行存储。这里,第一服务器可以将待交换数据标识存储在本地或者第三方服务器中。通常情况下,为了减少数据交换系统的建设与维护成本,第一服务器可以将待交换数据标识存储在本地。作为示例,待交换数据标识可以以文本文件的形式存储在第一服务器本地。
在步骤203中,第一服务器获取待交换数据标识的存储地址。
在本实施例中,在第一服务器对待交换数据标识进行存储之后,第一服务器可以获取待交换数据标识的存储地址。其中,存储地址可以是待交换数据标识在第一服务器中的具体存储路径。
在步骤204中,第一服务器对待交换数据标识的存储地址进行加密,生成第一加密存储地址。
在本实施例中,基于步骤203中所获取到的待交换数据标识的存 储地址,第一服务器可以对待交换数据标识的存储地址进行加密,生成第一加密存储地址。
需要说明的是,第一服务器可以采用各种可逆加密算法对待交换数据标识的存储地址进行加密,可逆加密算法是目前广泛研究和应用的公知技术,在此不再赘述。
在步骤205中,第二服务器从第一服务器获取第一加密存储地址。
在本实施例中,基于步骤204中所生成的第一加密存储地址,第二服务器可以从第一服务器获取第一加密存储地址。
在本实施例的一些可选的实现方式中,在生成第一加密存储地址之后,第一服务器可以直接将第一加密存储地址发送至第二服务器。
在本实施例的一些可选的实现方式中,在生成第一加密存储地址之后,第一服务器可以对第一加密存储地址进行存储,并将第一加密存储地址的存储地址发送至第二服务器,以使第二服务器根据第一加密存储地址的存储地址获取第一加密存储地址。作为示例,在生成第一加密存储地址之后,第一服务器可以将第一加密存储地址写入从第二服务器所获取到的智能合约中,并对该智能合约进行本地存储。然后,第一服务器可以将该智能合约的存储地址发送至第二服务器。最后,第二服务器可以根据该智能合约的存储地址从第一服务器获取该智能合约,并从该智能合约中提取出第一加密存储地址。
在步骤206中,第二服务器对第一加密存储地址进行解密,获取待交换数据标识的存储地址。
在本实施例中,基于步骤205中所获取到的第一加密存储地址,第二服务器可以对第一加密存储地址进行解密,以获取待交换数据标识的存储地址。这里,第二服务器可以采用与第一服务器对待交换数据标识的存储地址进行加密的加密算法相对应的解密算法对第一加密存储地址进行解密,即可获得待交换数据标识的存储地址。
在步骤207中,第二服务器基于待交换数据标识的存储地址,获取待交换数据标识。
在本实施例中,基于步骤206中所获取到的待交换数据标识的存储地址,第二服务器可以从第一服务器获取待交换数据标识。
在步骤208中,第二服务器基于待交换数据标识,从预先存储的数据集合中查找出待交换数据标识所指示的待交换数据。
在本实施例中,基于步骤207中所获取到的待交换数据标识,第二服务器可以从预先存储的数据集合中查找出待交换数据标识所指示的待交换数据。其中,数据集合可以包括数据和数据标识。
在本实施例中,数据集合可以以各种方式存储在第二服务器本地。例如,数据集合可以以文本文件的形式存储在第二服务器中。作为示例,数据集合可以以数据表的形式存储在第二服务器中。其中,数据表中的每行都有不同的数据索引,数据表的每列都有不同的数据名。这里,待交换数据标识可以是待交换数据索引和待交换数据名,第二服务器可以首先根据待交换数据索引在存储数据集合的数据表中查找到待交换数据所在的行;然后根据待交换数据名在待交换数据所在的行中查找到待交换数据。
在步骤209中,第一服务器从第二服务器获取待交换数据。
在本实施例中,基于步骤208中所获取到的待交换数据,第一服务器可以从第二服务器获取待交换数据。
在本实施例的一些可选的实现方式中,在获取到待交换数据之后,第二服务器可以直接将待交换数据发送至第一服务器。
在本实施例的一些可选的实现方式中,在获取到待交换数据之后,首先,第二服务器可以对待交换数据进行存储;之后,第二服务器可以获取待交换数据的存储地址,并对待交换数据的存储地址进行加密,生成第二加密存储地址;然后,第一服务器可以从第二服务器获取第二加密存储地址,并对第二加密存储地址进行解密,获取待交换数据的存储地址;最后,第一服务器可以基于待交换数据的存储地址,从第二服务器获取待交换数据。作为示例,在生成第二加密存储地址之后,首先,第二服务器可以将第二加密存储地址写入从第一服务器所获取到的智能合约中,并对该智能合约进行本地存储。然后,第二服务器可以将智能合约的存储地址发送至第一服务器。最后,第一服务器可以从第二服务器获取该智能合约,并从该智能合约中提取出第二加密存储地址。
在本实施例的一些可选的实现方式中,第一服务器可以对与待交换数据相对应的资源进行封存,并在接收到第二服务器发送的待交换数据之后,释放与待交换数据相对应的资源,以使第二服务器获取与待交换数据相对应的资源。作为示例,第一服务器可以将与待交换数据相对应的资源封存在从第二服务器所获取到的智能合约中,在接收到第二服务器发送的待交换数据之后,可以触发第一服务器执行封存有与待交换数据相对应的资源的智能合约,以实现将与待交换数据相对应的资源发送至第二服务器。
本申请实施例提供的数据交换系统,首先,第一服务器基于需求信息获取待交换数据标识,并对待交换数据标识进行存储;之后,第一服务器对待交换数据标识的存储地址进行加密,生成第一加密存储地址;而后,第二服务器从第一服务器获取第一加密存储地址,并对其进行解密以获取待交换数据标识的存储地址;然后,第二服务器基于待交换数据标识的存储地址,获取待交换数据标识;最后,第二服务器基于待交换数据标识从预先存储的数据集合中查找出待交换数据标识所指示的待交换数据,以使第一服务器从第二服务器获取待交换数据。数据交换系统中省去数据交换中心,第一服务器与第二服务器之间直接进行点对点的数据交换,从而节省了数据交换系统的建设与维护成本。
进一步参考图3,其示出了根据本申请的数据交换系统的又一个实施例的时序300。
本实施例中的数据交换系统可以包括第一服务器(例如图1所示的第一服务器102)和第二服务器(例如图1所示的第二服务器103)。其中,第一服务器,用于基于需求信息,获取待交换数据标识;对待交换数据标识进行存储;获取待交换数据标识的存储地址;生成对称密钥;利用对称密钥对待交换数据标识的存储地址进行加密,生成第一密文;基于预设对应关系,将第一密文映射成第一加密存储地址;利用从第二服务器预先获取的公钥对对称密钥进行加密,生成加密对称密钥,其中,第二服务器中存储有公钥和与公钥相对应的私钥。第二服务器,用于从第一服务器获取加密对称密钥和第一加密存储地址; 利用与公钥相对应的私钥对加密对称密钥进行解密,获取对称密钥;利用对称密钥和预设对应关系对第一加密存储地址进行解密,获取待交换数据标识的存储地址;基于待交换数据标识的存储地址,获取待交换数据标识;基于待交换数据标识,从预先存储的数据集合中查找出待交换数据标识所指示的待交换数据;对待交换数据进行存储;获取待交换数据的存储地址;利用对称密钥对待交换数据的存储地址进行加密,生成第二密文;基于预设对应关系,将第二密文映射成第二加密存储地址。第一服务器,还用于:从第二服务器获取第二加密存储地址;利用对称密钥和预设对应关系对第二加密存储地址进行解密,获取待交换数据的存储地址;基于待交换数据的存储地址,获取待交换数据。
如图3所示,在步骤301中,第一服务器基于需求信息,获取待交换数据标识。
在本实施例中,第一服务器(例如图1所示的第一服务器102)可以通过有线连接方式或者无线连接方式从客户端(例如图1所示的终端设备101)获取需求信息,并从需求信息中提取出待交换数据标识。其中,需求信息可以包括待交换数据标识。数据标识可以由文字、字母、数字、符号等组成,用来唯一识别数据。待交换数据标识可以用来唯一标识待交换数据。作为示例,数据标识可以包括数据名和/或数据索引。
在步骤302中,第一服务器对待交换数据标识进行存储。
在本实施例中,基于步骤301中所获取到的待交换数据标识,第一服务器可以对待交换数据标识进行存储。这里,第一服务器可以将待交换数据标识存储在本地或者第三方服务器中。通常情况下,为了减少数据交换系统的建设与维护成本,第一服务器可以将待交换数据标识存储在本地。作为示例,待交换数据标识可以以文本文件的形式存储在第一服务器本地。
在步骤303中,第一服务器获取待交换数据标识的存储地址。
在本实施例中,在第一服务器对待交换数据标识进行存储之后,第一服务器可以获取待交换数据标识的存储地址。其中,存储地址可 以是待交换数据标识在第一服务器中的具体存储路径。
在步骤304中,第一服务器生成对称密钥。
在本实施例中,第一服务器可以生成对称密钥。其中,对称密钥可以用于对待交换数据标识的存储地址或待交换数据的存储地址进行加密。对称密钥加密又叫专用密钥加密,即发送和接收数据的双方必使用相同的密钥对明文进行加密和解密运算。对称密钥加密算法可以包括但不限于DES(Data Encryption Standard,数据加密标准)、3DES(Triple DES,三重数据加密标准)、IDEA(International Data Encryption Algorithm,国际数据加密算法)、FEAL(Fast Data Encipherment Algorithm,分组加密算法)等。
在步骤305中,第一服务器利用对称密钥对待交换数据标识的存储地址进行加密,生成第一密文。
在本实施例中,基于步骤304中所生成的对称密钥,第一可以利用对称密钥对待交换数据标识的存储地址进行加密,以生成第一密文。
在步骤306中,第一服务器基于预设对应关系,将第一密文映射成第一加密存储地址。
在本实施例中,第一服务器可以基于预设对应关系,将第一密文映射成第一加密存储地址。
在本实施例的一些可选的实现方式中,第一服务器中可以预先存储分布式哈希表,当第一服务器将第一密文输入至该分布式哈希表时,该分布式哈希表可以根据对应的映射关系,将第一密文映射成第一加密存储地址。其中,分布式哈希表是一种数据结构,它把key(键)和value(值)用某种方式对应起来。具体地,分布式哈希表可以使用函数(例如hash函数)把一个key值映射到一个value上,即hash(key)=value。这样就可以把一个key值同某个value对应起来。其中,hash函数又叫做散列函数,其可以把任意长度的输入(又叫做预映射,pre-image),通过散列算法,变换成固定长度的输出,该输出就是散列值。
在步骤307中,第一服务器利用从第二服务器预先获取的公钥对对称密钥进行加密,生成加密对称密钥。
在本实施例中,基于从第二服务器(例如图1所示的第二服务器103)预先获取的公钥(Public Key),第一服务器可以利用该公钥对对称密钥进行加密,生成加密对称密钥。其中,第二服务器中存储有公钥和与公钥相对应的私钥(Private Key),并在发布数据标识的同时,发布公钥。具体地,公钥与私钥是通过一种算法得到的一个密钥对(即一个公钥和一个私钥),公钥是密钥对中公开的部分,私钥则是非公开的部分。公钥通常用于加密会话密钥、验证数字签名,或加密可以用相应的私钥解密的数据。通过这种算法得到的密钥对能保证在世界范围内是唯一的。使用这个密钥对的时候,如果用其中一个密钥加密一段数据,必须用另一个密钥解密。比如用公钥加密数据就必须用私钥解密,如果用私钥加密也必须用公钥解密,否则解密将不会成功。
在步骤308中,第二服务器从第一服务器获取加密对称密钥和第一加密存储地址。
在本实施例中,基于步骤306中所生成的第一加密存储地址和步骤307中所生成的加密对称密钥,第二服务器可以从第一服务器获取第一加密存储地址和加密对称密钥。
在本实施例的一些可选的实现方式中,在生成第一加密存储地址和加密对称密钥之后,第一服务器可以直接将第一加密存储地址和加密对称密钥发送至第二服务器。
在本实施例的一些可选的实现方式中,在生成第一加密存储地址和加密对称密钥之后,第一服务器可以对第一加密存储地址和加密对称密钥进行存储,并将第一加密存储地址和加密对称密钥的存储地址发送至第二服务器,以使第二服务器根据第一加密存储地址和加密对称密钥的存储地址获取第一加密存储地址和加密对称密钥。作为示例,在生成第一加密存储地址和加密对称密钥之后,首先,第一服务器可以将第一加密存储地址和加密对称密钥写入从第二服务器所获取到的智能合约中,并对该智能合约进行本地存储。然后,第一服务器可以将该智能合约的存储地址发送至第二服务器。最后,第二服务器可以根据该智能合约的存储地址从第一服务器获取该智能合约,并从该智能合约中提取出第一加密存储地址和加密对称密钥。
在步骤309中,第二服务器利用与公钥相对应的私钥对加密对称密钥进行解密,获取对称密钥。
在本实施例中,基于步骤308中所获取到的加密对称密钥,第二服务器可以利用与公钥相对应的私钥对加密对称密钥进行解密,以获取对称密钥。
在步骤310中,第二服务器利用对称密钥和预设对应关系对第一加密存储地址进行解密,获取待交换数据标识的存储地址。
在本实施例中,基于步骤309中所获取到的对称密钥,第二服务器可以利用对称密钥和预设对应关系对第一加密存储地址进行解密,以获取待交换数据标识的存储地址。
在本实施的一些可选的实现方式中,第二服务器中也可以预先存储分布式哈希表。这里,当第二服务器将第一加密存储地址输入至该分布式哈希表时,该分布式哈希表可以根据对应的映射关系,将第一加密存储地址映射成第一密文。然后,第二服务器可以利用对称密钥对第一密文进行解密,获取待交换数据标识的存储地址。
在步骤311中,第二服务器基于待交换数据标识的存储地址,获取待交换数据标识。
在本实施例中,基于步骤310中所获取到的待交换数据标识的存储地址,第二服务器可以从第一服务器获取待交换数据标识。
在步骤312中,第二服务器基于待交换数据标识,从预先存储的数据集合中查找出待交换数据标识所指示的待交换数据。
在本实施例中,基于步骤311中所获取到的待交换数据标识,第二服务器可以从预先存储的数据集合中查找出待交换数据标识所指示的待交换数据。其中,数据集合可以包括数据和数据标识。
在步骤313中,第二服务器对待交换数据进行存储。
在本实施例中,基于步骤312中所获取到的待交换数据,第二服务器可以对待交换数据进行存储。这里,第二服务器可以将待交换数据存储在本地或者第三方服务器中。通常情况下,为了减少数据交换系统的建设与维护成本,第二服务器可以将待交换数据存储在本地。作为示例,待交换数据可以以文本文件的形式存储在第二服务器本地。
在步骤314中,第二服务器获取待交换数据的存储地址。
在本实施例中,在第二服务器对待交换数据进行存储之后,第二服务器可以获取待交换数据的存储地址。其中,存储地址可以是待交换数据在第二服务器中的具体存储路径。
在步骤315中,第二服务器利用对称密钥对待交换数据的存储地址进行加密,生成第二密文。
在本实施例中,基于步骤309中所获取到的对称密钥,第二服务器可以利用对称密钥对待交换数据的存储地址进行加密,生成第二密文。
在步骤316中,第二服务器基于预设对应关系,将第二密文映射成第二加密存储地址。
在本实施例中,第二服务器可以基于预设的对应关系,将第二密文映射成第二加密存储地址。
在步骤317中,第一服务器从第二服务器获取第二加密存储地址。
在本实施例中,基于步骤316中所生成的第二加密存储地址,第一服务器可以从第二服务器获取第二加密存储地址。
在步骤318中,第一服务器利用对称密钥和预设对应关系对第二加密存储地址进行解密,获取待交换数据的存储地址。
在本实施例中,基于步骤317中所获取到的第二加密存储地址,第一服务器可以利用对称密钥和预设对应关系对第二加密存储地址进行解密,以获取待交换数据的存储地址。作为示例,第一服务器可以首先将第二加密存储地址输入到分布式哈希表中,以获取第二密文;然后利用对称密钥对第二密文进行解密,以获取待交换数据的存储地址。
在步骤319中,第一服务器基于待交换数据的存储地址,获取待交换数据。
在本实施例中,基于步骤318中所获取到的待交换数据,第一服务器可以从第二服务器获取待交换数据。
从图3中可以看出,与图2对应的实施例相比,本实施例中的数据交换系统的时序300突出了利用公钥、私钥和对称密钥进行加密和 解密的步骤。从而数据交换系统能够更加安全地、可靠地进行数据交换。
进一步参考图4,其示出了根据本申请的用于第一服务器的数据交换方法的一个实施例的流程400。该用于第一服务器的数据交换方法的流程400,包括以下步骤:
步骤401,基于需求信息,获取待交换数据标识。
在本实施例中,第一服务器(例如图1所示的第一服务器102)可以通过有线连接方式或者无线连接方式从客户端(例如图1所示的终端设备101)获取需求信息,并从需求信息中提取出待交换数据标识。其中,需求信息可以包括待交换数据标识。数据标识可以由文字、字母、数字、符号等组成,用来唯一识别数据。待交换数据标识可以用来唯一标识待交换数据。作为示例,数据标识可以包括数据名和/或数据索引。
步骤402,对待交换数据标识进行存储。
在本实施例中,基于步骤401中所获取到的待交换数据标识,第一服务器可以对待交换数据标识进行存储。这里,第一服务器可以将待交换数据标识存储在本地或者第三方服务器中。通常情况下,为了减少数据交换系统的建设与维护成本,第一服务器可以将待交换数据标识存储在本地。作为示例,待交换数据标识可以以文本文件的形式存储在第一服务器本地。
步骤403,获取待交换数据标识的存储地址。
在本实施例中,在第一服务器对待交换数据标识进行存储之后,第一服务器可以获取待交换数据标识的存储地址。其中,存储地址可以是待交换数据标识在第一服务器中的具体存储路径。
步骤404,对待交换数据标识的存储地址进行加密,生成第一加密存储地址。
在本实施例中,基于步骤403中所获取到的待交换数据标识的存储地址,第一服务器可以对待交换数据标识的存储地址进行加密,生成第一加密存储地址,以使第二服务器(例如图1所示的第二服务器103)从第一服务器获取第一加密存储地址,对第一加密存储地址进行 解密,获取待交换数据标识的存储地址,基于待交换数据标识的存储地址,获取待交换数据标识,基于待交换数据标识,从预先存储的数据集合中查找出待交换数据标识所指示的待交换数据,其中,数据集合可以包括数据和数据标识。
步骤405,从第二服务器获取待交换数据。
在本实施例中,在第二服务器从预先存储的数据集合中查找出待交换数据标识所指示的待交换数据之后,第一服务器可以从第二服务器获取待交换数据。
本申请实施例提供的用于第一服务器的数据交换方法,首先,基于需求信息获取待交换数据标识,并对待交换数据标识进行存储;然后,对待交换数据标识的存储地址进行加密,生成第一加密存储地址,以使第二服务器从第一服务器获取第一加密存储地址,并对其进行解密以获取待交换数据标识的存储地址,基于待交换数据标识的存储地址,获取待交换数据标识,基于待交换数据标识从预先存储的数据集合中查找出待交换数据标识所指示的待交换数据;最后,在第二服务器查找出待交换数据之后,从第二服务器获取待交换数据。整个数据交换过程不需要数据交换中心的参与,第一服务器与第二服务器之间直接进行点对点的数据交换,从而节省了数据交换系统的建设与维护成本。
进一步参考图5,作为对上述图4所示方法的实现,本申请提供了一种用于第一服务器的数据交换装置的一个实施例,该装置实施例与图4所示的方法实施例相对应,该装置具体可以应用于各种电子设备中。
如图5所示,本实施例所示的用于第一服务器的数据交换装置500可以包括:第一获取单元501、存储单元502、第二获取单元503、加密单元504和第三获取单元505。其中,第一获取单元501,配置用于基于需求信息,获取待交换数据标识;存储单元502,配置用于对待交换数据标识进行存储;第二获取单元503,配置用于获取待交换数据标识的存储地址;加密单元504,配置用于对待交换数据标识的存储地址进行加密,生成第一加密存储地址,以使第二服务器从第一服 务器获取第一加密存储地址,对第一加密存储地址进行解密,获取待交换数据标识的存储地址,基于待交换数据标识的存储地址,获取待交换数据标识,基于待交换数据标识,从预先存储的数据集合中查找出待交换数据标识所指示的待交换数据,其中,数据集合包括数据和数据标识;第三获取单元505,配置用于从第二服务器获取待交换数据。
在本实施例中,用于第一服务器的数据交换装置500中:第一获取单元501、存储单元502、第二获取单元503、加密单元504和第三获取单元505的具体处理及其所带来的技术效果可分别参考图4对应实施例中的步骤401、步骤402、步骤403、步骤404和步骤405的相关说明,在此不再赘述。
下面参考图6,其示出了适于用来实现本申请实施例的服务器的计算机系统600的结构示意图。图6示出的服务器仅仅是一个示例,不应对本申请实施例的功能和使用范围带来任何限制。
如图6所示,计算机系统600包括中央处理单元(CPU)601,其可以根据存储在只读存储器(ROM)602中的程序或者从存储部分608加载到随机访问存储器(RAM)603中的程序而执行各种适当的动作和处理。在RAM 603中,还存储有系统600操作所需的各种程序和数据。CPU 601、ROM 602以及RAM 603通过总线604彼此相连。输入/输出(I/O)接口605也连接至总线604。
以下部件连接至I/O接口605:包括键盘、鼠标等的输入部分606;包括诸如阴极射线管(CRT)、液晶显示器(LCD)等以及扬声器等的输出部分607;包括硬盘等的存储部分608;以及包括诸如LAN卡、调制解调器等的网络接口卡的通信部分609。通信部分609经由诸如因特网的网络执行通信处理。驱动器610也根据需要连接至I/O接口605。可拆卸介质611,诸如磁盘、光盘、磁光盘、半导体存储器等等,根据需要安装在驱动器610上,以便于从其上读出的计算机程序根据需要被安装入存储部分608。
特别地,根据本公开的实施例,上文参考流程图描述的过程可以被实现为计算机软件程序。例如,本公开的实施例包括一种计算机程 序产品,其包括承载在计算机可读介质上的计算机程序,该计算机程序包含用于执行流程图所示的方法的程序代码。在这样的实施例中,该计算机程序可以通过通信部分609从网络上被下载和安装,和/或从可拆卸介质611被安装。在该计算机程序被中央处理单元(CPU)601执行时,执行本申请的方法中限定的上述功能。
需要说明的是,本申请上述的计算机可读介质可以是计算机可读信号介质或者计算机可读存储介质或者是上述两者的任意组合。计算机可读存储介质例如可以是——但不限于——电、磁、光、电磁、红外线、或半导体的系统、装置或器件,或者任意以上的组合。计算机可读存储介质的更具体的例子可以包括但不限于:具有一个或多个导线的电连接、便携式计算机磁盘、硬盘、随机访问存储器(RAM)、只读存储器(ROM)、可擦式可编程只读存储器(EPROM或闪存)、光纤、便携式紧凑磁盘只读存储器(CD-ROM)、光存储器件、磁存储器件、或者上述的任意合适的组合。在本申请中,计算机可读存储介质可以是任何包含或存储程序的有形介质,该程序可以被指令执行系统、装置或者器件使用或者与其结合使用。而在本申请中,计算机可读的信号介质可以包括在基带中或者作为载波一部分传播的数据信号,其中承载了计算机可读的程序代码。这种传播的数据信号可以采用多种形式,包括但不限于电磁信号、光信号或上述的任意合适的组合。计算机可读的信号介质还可以是计算机可读存储介质以外的任何计算机可读介质,该计算机可读介质可以发送、传播或者传输用于由指令执行系统、装置或者器件使用或者与其结合使用的程序。计算机可读介质上包含的程序代码可以用任何适当的介质传输,包括但不限于:无线、电线、光缆、RF等等,或者上述的任意合适的组合。
附图中的流程图和框图,图示了按照本申请各种实施例的系统、方法和计算机程序产品的可能实现的体系架构、功能和操作。在这点上,流程图或框图中的每个方框可以代表一个模块、程序段、或代码的一部分,该模块、程序段、或代码的一部分包含一个或多个用于实现规定的逻辑功能的可执行指令。也应当注意,在有些作为替换的实现中,方框中所标注的功能也可以以不同于附图中所标注的顺序发生。 例如,两个接连地表示的方框实际上可以基本并行地执行,它们有时也可以按相反的顺序执行,这依所涉及的功能而定。也要注意的是,框图和/或流程图中的每个方框、以及框图和/或流程图中的方框的组合,可以用执行规定的功能或操作的专用的基于硬件的系统来实现,或者可以用专用硬件与计算机指令的组合来实现。
描述于本申请实施例中所涉及到的单元可以通过软件的方式实现,也可以通过硬件的方式来实现。所描述的单元也可以设置在处理器中,例如,可以描述为:一种处理器包括第一获取单元、存储单元、第二获取单元、加密单元和第三获取单元。其中,这些单元的名称在某种情况下并不构成对该单元本身的限定,例如,第一获取单元还可以被描述为“基于需求信息,获取待交换数据标识的单元”。
作为另一方面,本申请还提供了一种计算机可读介质,该计算机可读介质可以是上述实施例中描述的服务器中所包含的;也可以是单独存在,而未装配入该服务器中。上述计算机可读介质承载有一个或者多个程序,当上述一个或者多个程序被该服务器执行时,使得该服务器:基于需求信息,获取待交换数据标识;对待交换数据标识进行存储;获取待交换数据标识的存储地址;对待交换数据标识的存储地址进行加密,生成第一加密存储地址,以使第二服务器从第一服务器获取第一加密存储地址,对第一加密存储地址进行解密,获取待交换数据标识的存储地址,基于待交换数据标识的存储地址,获取待交换数据标识,基于待交换数据标识,从预先存储的数据集合中查找出待交换数据标识所指示的待交换数据,其中,数据集合包括数据和数据标识;从第二服务器获取待交换数据。
以上描述仅为本申请的较佳实施例以及对所运用技术原理的说明。本领域技术人员应当理解,本申请中所涉及的发明范围,并不限于上述技术特征的特定组合而成的技术方案,同时也应涵盖在不脱离上述发明构思的情况下,由上述技术特征或其等同特征进行任意组合而形成的其它技术方案。例如上述特征与本申请中公开的(但不限于)具有类似功能的技术特征进行互相替换而形成的技术方案。
Claims (12)
- 一种数据交换系统,其特征在于,所述系统包括:第一服务器和第二服务器;所述第一服务器,用于基于需求信息,获取待交换数据标识;对所述待交换数据标识进行存储;获取所述待交换数据标识的存储地址;对所述待交换数据标识的存储地址进行加密,生成第一加密存储地址;所述第二服务器,用于从所述第一服务器获取所述第一加密存储地址;对所述第一加密存储地址进行解密,获取所述待交换数据标识的存储地址;基于所述待交换数据标识的存储地址,获取所述待交换数据标识;基于所述待交换数据标识,从预先存储的数据集合中查找出所述待交换数据标识所指示的待交换数据,以使所述第一服务器从所述第二服务器获取所述待交换数据,其中,所述数据集合包括数据和数据标识。
- 根据权利要求1所述的系统,其特征在于,所述第二服务器,还用于:对所述待交换数据进行存储;获取所述待交换数据的存储地址;对所述待交换数据的存储地址进行加密,生成第二加密存储地址;所述第一服务器,还用于:从所述第二服务器获取所述第二加密存储地址;对所述第二加密存储地址进行解密,获取所述待交换数据的存储地址;基于所述待交换数据的存储地址,获取所述待交换数据。
- 根据权利要求2所述的系统,其特征在于,所述第一服务器,还用于:生成对称密钥;利用所述对称密钥对所述待交换数据标识的存储地址进行加密, 生成第一密文;基于预设对应关系,将所述第一密文映射成第一加密存储地址。
- 根据权利要求3所述的系统,其特征在于,所述第一服务器,还用于:利用从所述第二服务器预先获取的公钥对所述对称密钥进行加密,生成加密对称密钥,其中,所述第二服务器中存储有所述公钥和与所述公钥相对应的私钥。
- 根据权利要求4所述的系统,其特征在于,所述第二服务器,还用于:从所述第一服务器获取所述加密对称密钥和所述第一加密存储地址;利用与所述公钥相对应的私钥对所述加密对称密钥进行解密,获取所述对称密钥;利用所述对称密钥和所述预设对应关系对所述第一加密存储地址进行解密,获取所述待交换数据标识的存储地址。
- 根据权利要求5所述的系统,其特征在于,所述第二服务器,还用于:利用所述对称密钥对所述待交换数据的存储地址进行加密,生成第二密文;基于所述预设对应关系,将所述第二密文映射成第二加密存储地址。
- 根据权利要求6所述的系统,其特征在于,所述第一服务器,还用于:从所述第二服务器获取所述第二加密存储地址;利用所述对称密钥和所述预设对应关系对所述第二加密存储地址进行解密,获取所述待交换数据的存储地址;基于所述待交换数据的存储地址,获取所述待交换数据。
- 根据权利要求1-7之一所述的系统,其特征在于,所述第一服务器,还用于:对与所述待交换数据相对应的资源进行封存;在接收到所述第二服务器发送的所述待交换数据之后,释放与所述待交换数据相对应的资源,以使所述第二服务器获取与所述待交换数据相对应的资源。
- 一种用于第一服务器的数据交换方法,其特征在于,所述方法包括:基于需求信息,获取待交换数据标识;对所述待交换数据标识进行存储;获取所述待交换数据标识的存储地址;对所述待交换数据标识的存储地址进行加密,生成第一加密存储地址,以使第二服务器从所述第一服务器获取所述第一加密存储地址,对所述第一加密存储地址进行解密,获取所述待交换数据标识的存储地址,基于所述待交换数据标识的存储地址,获取所述待交换数据标识,基于所述待交换数据标识,从预先存储的数据集合中查找出所述待交换数据标识所指示的待交换数据,其中,所述数据集合包括数据和数据标识;从所述第二服务器获取所述待交换数据。
- 一种用于第一服务器的数据交换装置,其特征在于,所述装置包括:第一获取单元,配置用于基于需求信息,获取待交换数据标识;存储单元,配置用于对所述待交换数据标识进行存储;第二获取单元,配置用于获取所述待交换数据标识的存储地址;加密单元,配置用于对所述待交换数据标识的存储地址进行加密,生成第一加密存储地址,以使第二服务器从所述第一服务器获取所述 第一加密存储地址,对所述第一加密存储地址进行解密,获取所述待交换数据标识的存储地址,基于所述待交换数据标识的存储地址,获取所述待交换数据标识,基于所述待交换数据标识,从预先存储的数据集合中查找出所述待交换数据标识所指示的待交换数据,其中,所述数据集合包括数据和数据标识;第三获取单元,配置用于从所述第二服务器获取所述待交换数据。
- 一种服务器,其特征在于,所述服务器包括:一个或多个处理器;存储装置,用于存储一个或多个程序;当所述一个或多个程序被所述一个或多个处理器执行,使得所述一个或多个处理器实现如权利要求9中所述的方法。
- 一种计算机可读存储介质,其上存储有计算机程序,其特征在于,所述计算机程序被处理器执行时实现如权利要求9中所述的方法。
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US16/603,232 US11283778B2 (en) | 2017-06-06 | 2018-04-17 | Data exchange system, method and device |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201710418271.2A CN107248984B (zh) | 2017-06-06 | 2017-06-06 | 数据交换系统、方法和装置 |
CN201710418271.2 | 2017-06-06 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2018223777A1 true WO2018223777A1 (zh) | 2018-12-13 |
Family
ID=60019055
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2018/083375 WO2018223777A1 (zh) | 2017-06-06 | 2018-04-17 | 数据交换系统、方法和装置 |
Country Status (3)
Country | Link |
---|---|
US (1) | US11283778B2 (zh) |
CN (1) | CN107248984B (zh) |
WO (1) | WO2018223777A1 (zh) |
Families Citing this family (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN107248984B (zh) * | 2017-06-06 | 2020-06-05 | 北京京东尚科信息技术有限公司 | 数据交换系统、方法和装置 |
WO2019098895A1 (en) * | 2017-11-17 | 2019-05-23 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and arrangement for detecting digital content tampering |
CN109981551A (zh) * | 2017-12-28 | 2019-07-05 | 航天信息股份有限公司 | 一种基于区块链的数据传输系统、方法及相关设备 |
DE102019000023A1 (de) * | 2019-01-07 | 2020-07-09 | Holger Geissler | Verfahren und System zur Informationsübermittlung |
US11295024B2 (en) | 2019-01-18 | 2022-04-05 | Red Hat, Inc. | Providing smart contracts including secrets encrypted with oracle-provided encryption keys using threshold cryptosystems |
US11593493B2 (en) * | 2019-01-18 | 2023-02-28 | Red Hat, Inc. | Providing smart contracts including secrets encrypted with oracle-provided encryption keys |
CN109740027B (zh) * | 2019-01-28 | 2020-01-10 | 上海达梦数据库有限公司 | 数据交换方法、装置、服务器和存储介质 |
US11316660B2 (en) | 2019-02-21 | 2022-04-26 | Red Hat, Inc. | Multi-stage secure smart contracts |
CN110298661B (zh) * | 2019-07-01 | 2023-06-23 | 贵州大学 | 基于智能合约的大数据安全公平交换方法 |
US11451380B2 (en) | 2019-07-12 | 2022-09-20 | Red Hat, Inc. | Message decryption dependent on third-party confirmation of a condition precedent |
CN111221903B (zh) * | 2019-12-18 | 2023-11-28 | 中思博安科技(北京)有限公司 | 数据追责方法、系统和计算机存储介质 |
CN112861037B (zh) * | 2021-02-10 | 2023-12-12 | 北京百度网讯科技有限公司 | 数据标注方法、装置、系统、电子设备以及存储介质 |
Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5884325A (en) * | 1996-10-09 | 1999-03-16 | Oracle Corporation | System for synchronizing shared data between computers |
CN101047610A (zh) * | 2007-04-30 | 2007-10-03 | 华为技术有限公司 | 数据存储、读取、传输方法和管理服务器及网络节点 |
CN102111411A (zh) * | 2011-01-21 | 2011-06-29 | 南京信息工程大学 | P2p网络中对等用户结点间的加密安全数据交换方法 |
CN103107889A (zh) * | 2013-02-06 | 2013-05-15 | 中电长城网际系统应用有限公司 | 一种可搜索的云计算环境数据加密存储系统和方法 |
CN103810197A (zh) * | 2012-11-09 | 2014-05-21 | 北京亿赞普网络技术有限公司 | 一种基于Hadoop的数据处理方法及其系统 |
CN107248984A (zh) * | 2017-06-06 | 2017-10-13 | 北京京东尚科信息技术有限公司 | 数据交换系统、方法和装置 |
Family Cites Families (18)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6092196A (en) * | 1997-11-25 | 2000-07-18 | Nortel Networks Limited | HTTP distributed remote user authentication system |
US7089214B2 (en) * | 1998-04-27 | 2006-08-08 | Esignx Corporation | Method for utilizing a portable electronic authorization device to approve transactions between a user and an electronic transaction system |
US9311499B2 (en) * | 2000-11-13 | 2016-04-12 | Ron M. Redlich | Data security system and with territorial, geographic and triggering event protocol |
US7610627B1 (en) * | 2004-01-23 | 2009-10-27 | Acxiom Corporation | Secure data exchange technique |
CN101272523A (zh) * | 2007-03-22 | 2008-09-24 | 华源润通(北京)科技有限公司 | 一种移动查询系统及其查询方法 |
US8756673B2 (en) * | 2007-03-30 | 2014-06-17 | Ricoh Company, Ltd. | Techniques for sharing data |
US8555089B2 (en) * | 2009-01-08 | 2013-10-08 | Panasonic Corporation | Program execution apparatus, control method, control program, and integrated circuit |
FR2951842B1 (fr) * | 2009-10-28 | 2011-12-30 | Sagem Securite | Identification par controle de donnees d'utilisateur |
US8799677B2 (en) * | 2011-12-09 | 2014-08-05 | Nec Corporation | Encrypted search database device, encrypted search data adding/deleting method and adding/deleting program |
US20140052989A1 (en) * | 2012-08-15 | 2014-02-20 | Ultra Electronics, ProLogic | Secure data exchange using messaging service |
KR101416541B1 (ko) * | 2012-12-27 | 2014-07-09 | 주식회사 로웸 | 안전 로그인 시스템과 방법 및 이를 위한 장치 |
JP6048710B2 (ja) * | 2013-02-28 | 2016-12-21 | パナソニックIpマネジメント株式会社 | 暗号化記録装置、および暗号化記録方法 |
US20170149748A1 (en) * | 2015-11-25 | 2017-05-25 | Ty Lindteigen | Secure Group Messaging and Data Steaming |
US9432341B2 (en) * | 2013-05-30 | 2016-08-30 | International Business Machines Corporation | Securing data in a dispersed storage network |
US9100175B2 (en) * | 2013-11-19 | 2015-08-04 | M2M And Iot Technologies, Llc | Embedded universal integrated circuit card supporting two-factor authentication |
US10992649B2 (en) * | 2016-04-01 | 2021-04-27 | Consensys Software Inc. | Systems and methods for privacy in distributed ledger transactions |
US10579952B2 (en) * | 2016-05-11 | 2020-03-03 | International Business Machines Corporation | Tracking shipment container |
SG11202101028TA (en) * | 2018-08-03 | 2021-02-25 | Abaxx Tech Inc | Computer method and apparatus for administering a commodity material transaction via a distributed ledger |
-
2017
- 2017-06-06 CN CN201710418271.2A patent/CN107248984B/zh active Active
-
2018
- 2018-04-17 WO PCT/CN2018/083375 patent/WO2018223777A1/zh active Application Filing
- 2018-04-17 US US16/603,232 patent/US11283778B2/en active Active
Patent Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5884325A (en) * | 1996-10-09 | 1999-03-16 | Oracle Corporation | System for synchronizing shared data between computers |
CN101047610A (zh) * | 2007-04-30 | 2007-10-03 | 华为技术有限公司 | 数据存储、读取、传输方法和管理服务器及网络节点 |
CN102111411A (zh) * | 2011-01-21 | 2011-06-29 | 南京信息工程大学 | P2p网络中对等用户结点间的加密安全数据交换方法 |
CN103810197A (zh) * | 2012-11-09 | 2014-05-21 | 北京亿赞普网络技术有限公司 | 一种基于Hadoop的数据处理方法及其系统 |
CN103107889A (zh) * | 2013-02-06 | 2013-05-15 | 中电长城网际系统应用有限公司 | 一种可搜索的云计算环境数据加密存储系统和方法 |
CN107248984A (zh) * | 2017-06-06 | 2017-10-13 | 北京京东尚科信息技术有限公司 | 数据交换系统、方法和装置 |
Also Published As
Publication number | Publication date |
---|---|
US11283778B2 (en) | 2022-03-22 |
CN107248984B (zh) | 2020-06-05 |
CN107248984A (zh) | 2017-10-13 |
US20200374272A1 (en) | 2020-11-26 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2018223777A1 (zh) | 数据交换系统、方法和装置 | |
US10903976B2 (en) | End-to-end secure operations using a query matrix | |
US10880732B2 (en) | Authentication of phone caller identity | |
US11706026B2 (en) | Location aware cryptography | |
US20180212753A1 (en) | End-To-End Secure Operations Using a Query Vector | |
EP3075098B1 (en) | Server-aided private set intersection (psi) with data transfer | |
US10951595B2 (en) | Method, system and apparatus for storing website private key plaintext | |
Kumar et al. | A new approach for security in cloud data storage for IOT applications using hybrid cryptography technique | |
CN113162752B (zh) | 基于混合同态加密的数据处理方法和装置 | |
US20140095881A1 (en) | File sharing with client side encryption | |
US9344410B1 (en) | Telecommunication method for securely exchanging data | |
US10250596B2 (en) | Monitoring encrypted communication sessions | |
US10291600B2 (en) | Synchronizing secure session keys | |
CN107634946A (zh) | 一种微服务节点合法性验证方法和装置 | |
CN114500093B (zh) | 报文信息的安全交互方法及系统 | |
US10530581B2 (en) | Authenticated broadcast encryption | |
CN113595722B (zh) | 量子安全密钥同步方法、装置、电子设备和存储介质 | |
CN114173328A (zh) | 密钥交换方法、装置、电子设备 | |
CN111131270B (zh) | 数据加密和解密方法、装置、电子设备及存储介质 | |
CN111865761B (zh) | 一种基于区块链智能合约的社交聊天信息存证方法 | |
CN111798236B (zh) | 交易数据加、解密方法、装置及设备 | |
CN111010283B (zh) | 用于生成信息的方法和装置 | |
CN115296807B (zh) | 用于预防工控网络病毒的密钥生成方法、装置、设备 | |
CN111767550B (zh) | 数据存储方法和装置 | |
CN114615087B (zh) | 数据共享方法、装置、设备及介质 |
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: 18813163 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
32PN | Ep: public notification in the ep bulletin as address of the adressee cannot be established |
Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 05/03/2020) |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 18813163 Country of ref document: EP Kind code of ref document: A1 |