CN115827785B

CN115827785B - Data storage method, device, equipment and readable storage medium

Info

Publication number: CN115827785B
Application number: CN202211712798.3A
Authority: CN
Inventors: 陈海锋; 李朝霞; 肖征荣
Original assignee: China United Network Communications Group Co Ltd; Unicom Digital Technology Co Ltd; Unicom Cloud Data Co Ltd
Current assignee: China United Network Communications Group Co Ltd; Unicom Digital Technology Co Ltd; Unicom Cloud Data Co Ltd
Priority date: 2022-12-30
Filing date: 2022-12-30
Publication date: 2023-05-16
Anticipated expiration: 2042-12-30
Also published as: CN115827785A

Abstract

The application provides a data storage method, a data storage device, data storage equipment and a readable storage medium. The method comprises the following steps: receiving first data sent by a first client; storing the first data in an interplanetary file system IPFS server through a first application program interface API; determining first data information corresponding to the first data, wherein the first data information comprises at least one of the following: the method comprises the steps of data fingerprints corresponding to first data, IPFS storage addresses corresponding to the first data and coding information corresponding to a first client; the first data information is stored in the federated chain server through a second API. The security of data storage is improved.

Description

Data storage method, device, equipment and readable storage medium

Technical Field

The present disclosure relates to the field of computer technologies, and in particular, to a data storage method, apparatus, device, and readable storage medium.

Background

The background server may receive data from the client and store the data in the storage server.

In the related art, data is generally stored in a storage server in a centralized storage manner. However, in the above manner, when the storage server fails, data is easily lost, resulting in low security of data storage.

Disclosure of Invention

The application provides a data storage method, a data storage device and a readable storage medium, which are used for improving the security of data storage.

In a first aspect, the present application provides a data storage method, the method comprising:

receiving first data sent by a first client;

storing the first data in an interplanetary file system IPFS server through a first application program interface API;

determining first data information corresponding to the first data, wherein the first data information comprises at least one of the following: the method comprises the steps of obtaining a data fingerprint corresponding to first data, an IPFS storage address corresponding to the first data and coding information corresponding to a first client;

the first data information is stored in the federated chain server through a second API.

In one possible implementation manner, determining the coding information corresponding to the first client includes:

determining encryption information corresponding to a plurality of clients respectively, wherein the plurality of clients comprise the first client;

encrypting the plurality of encrypted information to obtain common coded information, wherein the common coded information is used for the plurality of clients;

and determining the common coding information as the coding information corresponding to the first client.

In one possible implementation manner, determining encryption information corresponding to each of the plurality of clients includes:

receiving a device identifier, a call number and a time stamp sent by each client;

and encrypting the equipment identifiers, the numbers and the time stamps to obtain encryption information corresponding to the clients respectively.

In one possible embodiment, the method further comprises:

receiving a hash value corresponding to first data information sent by a alliance chain server;

and storing the hash value in a preset database.

In one possible embodiment, the method further comprises:

and sending a storage result corresponding to the first data to the first client, wherein the storage result is successful storage or failed storage.

In one possible embodiment, the method further comprises:

receiving a data acquisition request of the first client, wherein the data acquisition request comprises coding information corresponding to the first client;

acquiring first data information corresponding to the first data from a alliance chain server according to the coding information;

determining an IPFS storage address corresponding to the first data in the first data information;

And acquiring the first data in the IPFS server according to the IPFS storage address, and sending a data acquisition result corresponding to the data acquisition request to the first client, wherein the data acquisition result comprises the first data.

In one possible implementation manner, according to the coding information, obtaining first data information corresponding to the first data in a coalition chain server includes:

encrypting the coded information to obtain encrypted coded information;

sending the encrypted coded information to a second client;

receiving a verification result of the encrypted coded information sent by the second client;

and when the verification result is that the verification is successful, acquiring first data information corresponding to the first data in a alliance chain server.

In a second aspect, the present application provides a data storage device comprising: the device comprises a receiving module, a first storage module, a first determining module and a second storage module, wherein,

the receiving module is used for receiving first data sent by the first client;

the first storage module is used for storing the first data in an IPFS server through a first application program interface API;

The first determining module is configured to determine first data information corresponding to the first data, where the first data information includes at least one of the following: the method comprises the steps of obtaining a data fingerprint corresponding to first data, an IPFS storage address corresponding to the first data and coding information corresponding to a first client;

the second storage module is used for storing the first data information in the alliance chain server through a second API.

In one possible implementation manner, the first determining module is specifically configured to:

In one possible implementation of the method according to the invention,

the receiving module is further used for receiving a hash value corresponding to the first data information sent by the alliance chain server;

in a possible embodiment, the device further comprises a third memory module,

the third storage module is used for storing the hash value in a preset database.

In one possible embodiment, the apparatus further comprises a transmitting module,

the sending module is configured to send a storage result corresponding to the first data to the first client, where the storage result is successful or failed in storage.

In one possible implementation of the method according to the invention,

the receiving module is further configured to receive a data acquisition request of a first client, where the data acquisition request includes coding information corresponding to the first client;

in one possible embodiment, the apparatus further comprises: a first acquisition module, a second determination module and a second acquisition module, wherein,

the first acquisition module is used for acquiring first data information corresponding to the first data in a alliance chain server according to the coding information;

the second determining module is used for determining an IPFS storage address corresponding to the first data in the first data information;

The second obtaining module is used for obtaining the first data in an IPFS server according to the IPFS storage address;

in one possible implementation of the method according to the invention,

the sending module is further configured to send a data acquisition result corresponding to the data acquisition request to the first client, where the data acquisition result includes the first data.

In one possible implementation manner, the first obtaining module is further configured to:

encrypting the coded information to obtain encrypted coded information;

sending the encrypted coded information to a second client;

In a third aspect, the present application provides an electronic device, comprising: a processor and a memory;

the memory stores computer-executable instructions;

the processor executing computer-executable instructions stored in the memory causing the processor to perform the data storage method of any one of the first aspects.

In a fourth aspect, the present application provides a computer-readable storage medium having stored therein computer-executable instructions for performing the data storage method of any one of the first aspects when the computer-executable instructions are executed by a processor.

In a fifth aspect, the present application provides a computer program product comprising a computer program which, when executed by a processor, implements the data storage method of any of the first aspects.

The embodiment of the application provides a data storage method, a device, equipment and a readable storage medium, wherein a background server can receive first data sent by a first client and store the first data in an IPFS server through a first API; the background server can determine first data information corresponding to the first data, and store the first data information in the alliance chain server through the second API. Because the first data can be stored in the IPFS server, the first data information can be stored in the alliance chain server, and the IPFS server and the alliance chain server can both adopt distributed storage, thereby improving the safety of data storage.

Drawings

In order to more clearly illustrate the embodiments of the present invention or the technical solutions of the prior art, the drawings that are needed in the embodiments or the description of the prior art will be briefly described below, it will be obvious that the drawings in the following description are some embodiments of the present invention, and that other drawings can be obtained according to these drawings without inventive effort to a person skilled in the art.

Fig. 1 is a schematic diagram of an application scenario provided in an embodiment of the present application;

fig. 2 is a schematic flow chart of a data storage method according to an embodiment of the present application;

FIG. 3 is a flowchart illustrating another data storage method according to an embodiment of the present disclosure;

fig. 4 is a schematic process diagram of a data storage method according to an embodiment of the present application;

fig. 5 is a flow chart of a data query method according to an embodiment of the present application;

FIG. 6 is a schematic diagram of a data storage device according to the present disclosure;

FIG. 7 is a schematic diagram of another data storage device according to an embodiment of the present disclosure;

fig. 8 is a schematic structural diagram of an electronic device according to an embodiment of the present application.

Detailed Description

Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The implementations described in the following exemplary examples are not representative of all implementations consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with some aspects of the present application as detailed in the accompanying claims.

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

Fig. 1 is a schematic diagram of an application scenario provided in an embodiment of the present application. Referring to fig. 1, the system includes a plurality of clients, a background server, an interstellar file system (InterPlanetary File System, IPFS) server, and a federated chain (Fabric) server.

The plurality of clients may be clients 1, … …, client n, respectively. The plurality of clients may share a user account, or a call number. For example, the client 1 may be a mobile phone, the client n may be a smart watch, and the mobile phone and the smart watch may share a call number.

For any one client, the client and the background server can communicate with each other. The client may send the first data to the background server. For example, the client 1 may send the first data 1 to a background server.

After the background server receives the first data, the first data may be stored in the IPFS server; the background server may determine first data information corresponding to the first data and store the first data information in the federated chain server.

In the embodiment of the application, the background server may receive the first data sent by the first client, and store the first data in the IPFS server; corresponding first data information may be determined from the first data and stored in the federated chain server. The first data and the first data information can be respectively stored in different storage servers, and the IPFS server and the alliance chain server can both adopt distributed storage, so that the safety of data storage is improved.

The technical scheme shown in the application is described in detail through specific embodiments. It should be noted that the following embodiments may exist alone or in combination with each other, and for the same or similar content, the description will not be repeated in different embodiments.

Fig. 2 is a flow chart of a data storage method according to an embodiment of the present application. Referring to fig. 2, the method may include:

s201, first data sent by a first client side are received.

The execution body of the embodiment of the application may be a background server, or may be a data storage device disposed in the background server. The data storage device may be implemented in software or a combination of software and hardware. The data storage device may be a processor in a backend server. For ease of understanding, the description will be made below taking the execution body as a background server as an example.

The first client may be a terminal device used by the user. For example, the first client may be a mobile phone, a computer, a smart watch, or the like.

The first data may be system data, application data, etc. in the first client. The amount of the first data may be at least one.

Alternatively, the first client may send a hypertext transfer protocol (Hyper Text Transfer Protocol, HTTP) POST request to the backend server, where the HTTP POST request may include the first data and an identification of the first client. The backend server may receive the HTTP POST request to obtain the first data.

For example, if the first client is the client 1, the client 1 may send an HTTP POST request 1 to the background server, where the HTTP POST request 1 may include the first data 1 and the identifier of the client 1, and the background server may receive the HTTP POST request 1 to obtain the first data 1.

Optionally, the first client may send a plurality of HTTP POST requests to the backend server to send the plurality of first data, such that the backend server may receive the plurality of first data sent by the first client.

S202, storing the first data in an interstellar file system server through a first application program interface.

The first application program interface (Application Programming Interface, API) may be an interface provided in the IPFS server.

The IPFS server may be a server in the interplanetary file system IPFS. The IPFS server can perform distributed storage on data in a point-to-point (peer-to-peer) mode, so that the safety and the storage efficiency of data storage are improved, the repeated data storage can be avoided, and the cost of data storage is reduced.

Optionally, after the background server obtains the first data, a first API in the IPFS server may be determined, and the first data is sent to the IPFS server through the first API to store the first data in the IPFS server.

Optionally, after receiving the first data, the IPFS server may perform distributed storage on the first data in a point-to-point manner, and determine an IPFS storage address corresponding to the first data. The IPFS server may send an IPFS storage address corresponding to the first data to a background server.

For example, if the background server receives the first data 1, the background server may determine a first API in the IPFS server and send the first data 1 to the IPFS server through the first API. After the IPFS server receives the first data 1, the first data 1 may be stored, and an IPFS storage address 1 corresponding to the first data 1 is determined. Assuming that IPFS store address 1 may be 001-002-003-004, the IPFS server may send the IPFS store address 1 to the background server.

Optionally, before the background server sends the first data to the IPFS server, hash operation may be further performed on the first data to determine a data fingerprint corresponding to the first data. The background server can store the identification of the first client, the identification of the first data and the data fingerprint corresponding to the first data in a preset database.

The data fingerprint may be a sequence code. The data fingerprint may be used to verify whether the first data has been tampered with. For example, the data fingerprint may be "0906b080b03ea64d0534d36b2bd9 edb".

For example, if the background server receives the first data 1, the background server may perform a hash operation on the first data 1 to determine a data fingerprint 1 corresponding to the first data 1. Suppose that data fingerprint 1 may be "0906b080b03ea64d0534d36b2bd9 edb". The background server can store the identification of the first data 1 and the correspondence of the data fingerprint 1 in a preset database.

S203, determining first data information corresponding to the first data.

The first data information may include at least one of: the method comprises the steps of data fingerprint corresponding to first data, IPFS storage address corresponding to the first data and coding information corresponding to a first client.

In an alternative embodiment, the coding information corresponding to the first client may be determined by: determining encryption information corresponding to each of a plurality of clients; encrypting the plurality of encrypted information to obtain common coded information; and determining the common coding information as the coding information corresponding to the first client.

The background server can receive the information sent by the clients respectively and determine the encryption information corresponding to the clients respectively according to the information sent by the clients respectively. The background server can encrypt the plurality of encrypted information through a homomorphic encryption algorithm to obtain common encoded information, and the common encoded information is determined to be the encoded information corresponding to the first client.

For example, if the background server receives the information 1 sent by the client 1 and the information 1 sent by the client 2, the background server may determine the encrypted information 1 corresponding to the client 1 according to the information 1; the encrypted information 2 corresponding to the client 2 may be determined from the information 2. The background server can encrypt the encrypted information 1 and the encrypted information 2 through a homomorphic encryption algorithm to obtain common encoded information 1. This common encoded information 1 may be used for both client 1 and client 2. If the first client is the client 1, the common code 1 may be determined as the code information corresponding to the client 1.

Optionally, since the common encoding information may be used for a plurality of clients, after the background server determines the common encoding information, it may determine that the encoding information corresponding to the plurality of clients is the common encoding information, and send the common encoding information to the plurality of clients respectively, so that the plurality of clients store the common encoding information.

The background server can acquire the data fingerprint corresponding to the first data from the preset database because the identifier of the first data and the data fingerprint corresponding to the first data can be correspondingly stored in the preset database; because the background server can receive the IPFS storage address corresponding to the first data sent by the IPFS server, the background server can determine the IPFS storage address corresponding to the first data.

After the background server determines the coding information corresponding to the first client, the data fingerprint corresponding to the first data and the IPFS storage address corresponding to the first data, the coding information corresponding to the first client, the data fingerprint corresponding to the first data and the IPFS storage address corresponding to the first data may be packaged to obtain the first data information.

The format of the first data information may be JavaScript object notation (JavaScript Object Notation, JSON) format.

For example, if the first client is client 1, the encoded information 1 corresponding to client 1 is 0001, the data fingerprint 1 corresponding to the first data is 0906b080b03ea64d0534d36b2bd9edb8, and the IPFS storage address 1 corresponding to the first data is 001-002-003-004, the background server may perform the packaging processing on the encoded information 1, the data fingerprint 1, and the IPFS storage address 1 to obtain the first data information. The first data information may include encoded information 1, a data fingerprint 1, and an IPFS storage address 1.

S204, storing the first data information in the alliance chain server through a second application program interface.

The second API may be an interface provided in the federated chain server.

A federated chain server is a server located in a federated chain system. The federated chain server is a node in the federated chain system that may provide storage space and computational power support for the federated chain system.

Alternatively, the background server may determine a second API in the federated chain server and send the first data information to the federated chain server through the second API. After the alliance chain server receives the first data information, the first data information can be stored in a point-to-point mode in a distributed mode.

For example, if the background server may determine the first data information 1, where the first data information 1 may include the data fingerprint 1, the IPFS storage address 1, and the encoded information 1, the background server may determine a second API in the federated chain server, and send the first data information 1 to the federated server through a second API interface. After the coalition chain server receives the first data information 1, the first data information 1 can be stored in a distributed mode in a point-to-point mode.

In the embodiment of the application, the background server may receive the first data sent by the first client, and store the first data in the IPFS server through the first API. The background server may determine a data fingerprint corresponding to the first data, an IPFS storage address corresponding to the first data, and encoding information corresponding to the first client, and further determine first data information corresponding to the first data. The background server may store the first data information in the federated chain server through the second API. Because the first data can be stored in the IPFS server, the first data information can be stored in the alliance chain server, and the IPFS server and the alliance chain server can both adopt distributed storage, thereby improving the safety of data storage.

The above data storage method will be described in further detail with reference to fig. 3 on the basis of the embodiment shown in fig. 2.

Fig. 3 is a flowchart of another data storage method according to an embodiment of the present application. Referring to fig. 3, the method may include:

s301, the first client sends first data to a background server.

Optionally, the first client may send the first data to the background server through an HTTP POST request, so that the background server receives the first data. The HTTP POST request may include first data therein. And an identification of the first client.

For example, if the first client is the client 1, the client 1 may send an HTTP POST request 1 to the background server, where the HTTP POST request 1 may include the first data 1 and the identifier of the client 1.

S302, the background server determines a data fingerprint corresponding to the first data.

After receiving the HTTP POST request, the background server may obtain the first data in the HTTP POST request and the identifier of the first client. The background server can carry out hash operation on the first data, determine a hash operation result of the first data, and determine the hash operation result as a data fingerprint corresponding to the first data. The background server can store the identification of the first client, the identification of the first data and the data fingerprint corresponding to the first data in a preset database.

For example, if the background server receives the first data 1, the background server may perform a hash operation on the first data 1 to determine a data fingerprint 1 corresponding to the first data 1. Suppose that data fingerprint 1 may be "0906b080b03ea64d0534d36b2bd9 edb". The background server can correspondingly store the identification 1 of the first data 1 and the data fingerprint 1 in a preset database.

S303, the background server sends first data to the interstellar file system server through a first application program interface.

The background server may determine a first API in the interplanetary file system IPFS server and send the first data to the IPFS server via the first API.

For example, if the background server receives the first data 1, the background server may determine a first API in the IPFS server and send the first data 1 to the IPFS server through the first API.

S304, the interstellar file system server stores the first data, and determines an interstellar file system storage address corresponding to the first data.

Optionally, after the interstellar file system IPFS server receives the first data, a plurality of storage units may be determined according to a size of the first data, the first data is stored in the plurality of storage units in a scattered manner, and an IPFS storage address corresponding to the first data may be determined according to addresses of the plurality of storage units.

For example, if the IPFS server receives the first data 1, if the size of the first data 1 is 1024KB (kilobytes), and the size of the storage unit in the IPFS server is 256KB, the IPFS server may determine 4 storage units according to the size of the first data 1, and store the first data 1 in the 4 storage units in a scattered manner. If the addresses of the 4 storage units are 001, 002, 003, and 004, respectively, the IPFS server may determine that the IPFS storage address 1 of the first data 1 is 001-002-003-004 according to the 4 addresses.

S305, the interstellar file system server transmits the interstellar file system storage address corresponding to the first data to the background server.

For example, if the interplanetary file system IPFS server determines that IPFS storage address 1 of first data 1 is 001-002-003-004, the IPFS server may send the IPFS storage address 1 to the background server.

S306, the background server determines coding information corresponding to the first client.

Optionally, the background server may determine encryption information corresponding to each of the plurality of clients, and perform encryption processing on the plurality of encryption information through a homomorphic encryption algorithm to obtain common encoding information, and determine the common encoding information as encoding information corresponding to the first client.

Alternatively, the encryption information respectively corresponding to the plurality of clients may be determined by: receiving a device identifier, a call number and a time stamp sent by each client; and carrying out encryption processing on the plurality of equipment identifiers, the numbers and the time stamps to obtain encryption information corresponding to the plurality of clients respectively.

The device identification may be used to distinguish between different clients. For example, the device identification may be a globally unique device identification (Unique Device Identifier, UDID) of the client.

The call number may be a telephone number used by the client. For example, the call number may be 131×1234.

The time stamp may be a character sequence acquired according to the current time. For example, if the current time is 2022-12-15:12, the timestamp may be determined according to the current time, assuming that the timestamp corresponding to the current time may be 445555000.

A first client may be included among the plurality of clients, which may share a call number. The background server can receive the equipment identifiers, the call numbers and the time stamps sent by the plurality of clients, and encrypt the plurality of equipment identifiers, the call numbers and the time stamps through a homomorphic encryption algorithm to obtain encryption information respectively corresponding to the plurality of clients.

For example, if there are 2 clients, client 1 and client 2, respectively. The 2 clients may share a single call number. If the background server receives the equipment identifier 1, the call number and the timestamp 1 sent by the client 1 and receives the equipment identifier 2, the call number and the timestamp 2 sent by the client 2, the background server can encrypt the equipment identifier 1, the call number and the timestamp 1 through a homomorphic encryption algorithm to obtain encrypted information 1 corresponding to the client 1; the device identifier 2, the call number and the timestamp 2 can be encrypted by a homomorphic encryption algorithm to obtain encrypted information 2 corresponding to the client 2.

After the background server determines the encryption information corresponding to each of the plurality of clients, the plurality of encryption information can be encrypted by a homomorphic encryption algorithm to obtain common coding information, and the common coding information is determined to be the coding information corresponding to the first client.

For example, if the background server determines that the encrypted information corresponding to the client 1 is the encrypted information 1 and determines that the encrypted information corresponding to the client 2 is the encrypted information 2, the background server may encrypt the encrypted information 1 and the encrypted information 2 by using a homomorphic encryption algorithm, so as to obtain the common encoded information 1. This common encoded information 1 may be used for both client 1 and client 2. If the first client is the client 1, the common code 1 may be determined as the code information corresponding to the client 1.

It should be noted that the plurality of clients may include a first client, and the plurality of clients may share a call number or an account number. The background server may use the common encoding information as encoding information corresponding to the plurality of clients, that is, encoding information corresponding to the plurality of clients sharing one call number is the same.

S307, the background server determines the first data information according to the data fingerprint corresponding to the first data, the interstellar file system storage address corresponding to the first data and the coding information corresponding to the first client.

Optionally, the background server may perform packaging processing on the data fingerprint corresponding to the first data, the IPFS storage address corresponding to the first data, and the encoded information corresponding to the first client, to obtain first data information.

For example, if the first client is client 1, the data fingerprint 1 corresponding to the first data is 0906b080b03ea64d0534d36b2bd9edb, the IPFS storage address 1 corresponding to the first data is 001-002-003-004, and the encoded information 1 corresponding to the client 1 is 0001, the background server may perform the packaging processing on the data fingerprint 1, the IPFS storage address 1 and the encoded information 1 to obtain the first data information. The first data information may include a data fingerprint 1, an IPFS memory address 1, and encoded information 1.

S308, the background server sends the first data information to the alliance chain server through the second application program interface.

Alternatively, the background server may determine a second API in the federated chain server and send the first data information to the federated chain server through the second API.

For example, if the background server may determine the first data information 1, where the first data information 1 may include the data fingerprint 1, the IPFS storage address 1, and the encoded information 1, the background server may determine a second API in the federated chain server, and send the first data information 1 to the federated server through a second API interface.

S309, the alliance chain server stores the first data information and determines a hash value corresponding to the first data information.

Optionally, a chain code and ledger may be included in the federation chain server. The chain code is a programming preset in the alliance chain server, and the first data information can be logically processed and stored through the chain code. A plurality of key-value pairs (key-value) may be included in the ledger for storing or recording the first data information.

After the federation chain server receives the first data information, the chain code may be called through the second API, and a corresponding ledger may be determined. The alliance chain server can save the first data information in an account book as a key, and can map the hash value corresponding to the first data information through a hash algorithm.

For example, if the federation chain server receives the first data information 1, the federation chain server may call the chain code through the second API and determine the corresponding ledger. The federation chain server can save the first data information 1 as a key in an account book, and can map the first data information 1 through a hash algorithm to obtain a hash value 1 corresponding to the first data information 1. For example, hash value 1 may be 56.

S310, the alliance chain server sends a hash value corresponding to the first data information to the background server.

For example, if the hash value 1 corresponding to the first data information 1 is 56, the federation chain server may send the hash value 1 to the background server.

S311, the background server stores the hash value in a preset database.

For example, if the background server receives the hash value 1 corresponding to the first data information 1, the background server stores the hash value 1 in the preset database.

Optionally, the background server may store the identifier of the first data and the hash value corresponding to the first data information in a preset database.

S312, the background server sends a storage result corresponding to the first data to the first client.

The storage result may include storage success or storage failure.

Optionally, the background server may send the storage result to the first client by using an HTTP POST method. If the background server receives the hash value corresponding to the first data information, a storage result can be sent to the first client, and the storage result can be that the storage is successful; if the background server does not receive the hash value corresponding to the first data information, a storage result may be sent to the first client, where the storage result may be a storage failure.

In this embodiment of the present application, the first client may send the first data to the background server, and after the background server receives the first data, the data fingerprint corresponding to the first data may be determined, and the first data may be sent to the IPFS server through the first API. The IPFS server may store the first data and determine an IPFS storage address corresponding to the first data. The IPFS server may send an IPFS storage address corresponding to the first data to a background server. The background server may determine the encoded information corresponding to the first client, and may determine the first data information according to the data fingerprint corresponding to the first data, the IPFS storage address corresponding to the first data, and the encoded information corresponding to the first client. The background server may send the first data information to the federated chain server via the second API. The federated chain server may store the first data information and determine a hash value corresponding to the first data information. The alliance chain server can send the hash value corresponding to the first data information to the background server, the background server can store the hash value in a preset database, and the background server can also send a storage result corresponding to the first data to the first client. Because the first data can be stored in the IPFS server and the first data information can be stored in the alliance chain server, the IPFS server and the alliance chain server can both adopt distributed storage, and the safety of data storage is improved.

The data storage method described above will be further described below with reference to fig. 4 by way of specific example on the basis of any of the above embodiments.

Fig. 4 is a schematic process diagram of a data storage method according to an embodiment of the present application. Referring to fig. 4, the client, the background server, the IPFS server, and the federation chain server are included.

The plurality of clients may be client 1, client 2, … …, client n, respectively. The plurality of clients may share one call number or one account number. Wherein the first client may be client 1.

In step (1), the client 1 may send the first data 1 to the background server through the HTTP POST request 1, and may send the first data 2 to the background server through the HTTP POST request 2.

After the background server receives the first data 1 and the first data 2, hash operation can be performed on the first data 1 to determine a corresponding data fingerprint 1; a hash operation may be performed on the first data 2 to determine a corresponding data fingerprint 2.

In step (2), the background server may send the first data 1 and the first data 2 to the IPFS server.

The IPFS server can perform distributed storage on the first data 1 and the first data 2 in a point-to-point mode, determine an IPFS storage address 1 corresponding to the first data 1 and an IPFS storage address 2 corresponding to the first data 2, and send the IPFS storage address 1 and the IPFS storage address 2 to the background server (step (3)), so that the background server can acquire the IPFS storage address 1 and the IPFS storage address 2.

Optionally, the IPFS server may include a plurality of first data and an IPFS storage address corresponding to each first data.

In step (4), the backend server may receive the device identification, the phone number, and the timestamp sent by each client. For example, the background server may receive device identification 1, phone number and timestamp 1 sent by client 1, device identification 2, phone number and timestamp 2, … … sent by client 2, device identification n sent by client n, phone number and timestamp n.

The background server can determine the encryption information corresponding to each client according to the equipment identifier, the call number and the time stamp sent by each client, and can encrypt a plurality of encryption information through a homomorphic encryption algorithm to obtain common coding information, wherein the common coding information can be used as the coding information of each client. For example, the common encoding information may be determined as the encoding information 1 corresponding to the client 1.

The background server can encrypt the data fingerprint 1 corresponding to the first data 1, the IPFS storage address 1, the data fingerprint 2 corresponding to the first data 2, the IPFS storage address 2 and the encoded information corresponding to the first client to obtain first data information 1 in JSON format. In the first data information 1, the content corresponding to the encoded information 1 may include: data fingerprint 1 and IPFS storage address 1 corresponding to first data 1, data fingerprint 2 and IPFS storage address 2 corresponding to first data 2. The background server may send the first data information 1 to the federated chain server (step (5)).

After the alliance chain server receives the first data information 1, the first data information 1 can be used as a key to be stored in an account book, and the first data information 1 is mapped through a hash algorithm to obtain a hash value 1 corresponding to the first data information 1. For example, the hash value 1 may be 23. The federated chain server may send the hash value of 1 to the background server (step (6)).

Optionally, a plurality of first data information and corresponding hash values may be included in the federated chain server.

Optionally, the background server may also send the stored results of the first data 1 and the first data 2 to the client.

In this embodiment of the present application, the first client may send the first data to the background server, and after the background server receives the first data, the data fingerprint corresponding to the first data may be determined, and the first data may be sent to the IPFS server through the first API. The IPFS server may store the first data and determine an IPFS storage address corresponding to the first data. The IPFS server may send an IPFS storage address corresponding to the first data to a background server. The background server may determine the encoding information corresponding to the first client, and determine the first data information according to the data fingerprint corresponding to the first data, the IPFS storage address corresponding to the first data, and the encoding information corresponding to the first client. The background server may send the first data information to the federated chain server via the second API. The federated chain server may store the first data information and determine a hash value corresponding to the first data information. The alliance chain server can send the hash value corresponding to the first data information to the background server, the background server can store the hash value in a preset database, and the background server can also send a storage result corresponding to the first data to the first client. Because the first data can be stored in the IPFS server and the first data information can be stored in the alliance chain server, the IPFS server and the alliance chain server can both adopt distributed storage, and the safety of data storage is improved.

Next, on the basis of any of the above embodiments, in conjunction with fig. 5, a data query method is provided.

Fig. 5 is a flow chart of a data query method according to an embodiment of the present application. Referring to fig. 5, the method may include:

s501, acquiring a data acquisition request sent by a first client.

The data acquisition request may be an HTTP GET request, and the data acquisition request may include encoding information corresponding to the first client and/or an identifier of the first client.

For example, if the first client is the client 1, the background server may acquire a data acquisition request sent by the client 1, where the data acquisition request may include the code information 1 corresponding to the client 1 and the identifier of the client 1.

S502, acquiring first data information corresponding to the first data in the alliance chain server according to the coding information.

In an alternative embodiment, the first data information corresponding to the first data may be obtained from the federated chain server according to the encoding information by: encrypting the coded information to obtain encrypted coded information; sending the encrypted coding information to a second client; receiving a verification result of the encrypted coded information sent by the second client; and when the verification result is that the verification is successful, acquiring first data information corresponding to the first data from the alliance chain server according to the coding information.

Optionally, after the second client receives the encrypted encoded information corresponding to the encoded information sent by the background server, the verification result of the encrypted encoded information may be determined by the following 2 manners:

mode 1, carrying out decryption processing on the encrypted coded information once to obtain new coded information, and determining a verification result of the encrypted coded information according to whether the new coded information is consistent with the original coded information in the second client.

Because the corresponding original code information, namely the common code information, is stored in each client, the second client performs decryption processing on the encrypted code information once, so that new code information can be obtained. If the new coded information is consistent with the original coded information, the verification result of the encrypted coded information can be determined to be successful verification; if the new encoded information is inconsistent with the original encoded information, the verification result of the encrypted encoded information can be determined to be verification failure.

For example, if the background server receives the data acquisition request 1 sent by the client 1, where the data acquisition request 1 includes the encoded information 1 corresponding to the client 1, the background server may encrypt the encoded information 1 through a preset encryption algorithm to obtain encrypted encoded information 1. The background server may send the encrypted encoded information 1 to the client 2, and after the client 2 receives the encrypted encoded information 1, the client may decrypt the encrypted encoded information 1 to obtain the encoded information 2. Since the original code information is included in the client 2, the client 2 can determine whether the original code information and the code information 2 agree. If the verification results are consistent, the verification result can be determined to be successful verification; if the verification results are inconsistent, the verification results can be determined to be verification failures.

And 2, performing decryption processing on the encrypted coded information for multiple times to obtain device identifiers, call numbers and time stamps corresponding to the multiple clients, and determining whether the device identifiers, the call numbers and the time stamps corresponding to the multiple clients comprise the device identifiers and the call numbers corresponding to the second clients or not so as to determine verification results of the encrypted coded information.

The encrypted coded information is obtained by encrypting the coded information, and the coded information is obtained according to the device identifiers, the call numbers and the time stamps corresponding to the plurality of clients, so that the second client can decrypt the encrypted coded information once to obtain new coded information, and can further decrypt the new coded information to obtain the device identifiers, the call numbers and the time stamps corresponding to the plurality of clients. If the device identifiers, the call numbers and the time stamps corresponding to the plurality of clients comprise the device identifiers and the call numbers corresponding to the second client, the verification result of the encrypted coding information can be determined to be successful verification; if the device identifier and the call number corresponding to the second client are not included, the verification result of the encrypted coding information can be determined to be verification failure.

For example, if the background server receives the data acquisition request 1 sent by the client 1, where the data acquisition request 1 includes the encoded information 1 corresponding to the client 1, the encoded information 1 may be determined according to the device identifier, the call number, and the timestamp corresponding to the client 1 and the client 2, and then the background server may encrypt the encoded information 1 through a preset encryption algorithm to obtain the encrypted encoded information 1. The background server may send the encrypted encoded information 1 to the client 2, and after the client 2 receives the encrypted encoded information 1, the client may decrypt the encrypted encoded information 1 to obtain the encoded information 2. The client 2 may further decrypt the encoded information 2 to obtain device identifiers, call numbers, and time stamps corresponding to the plurality of clients. If the device identifiers and the call numbers corresponding to the plurality of clients include the device identifier and the call number of the client 2, the verification result of the encrypted code information 1 can be determined to be successful verification; if the device identifier and the call number of the client 2 are not included, it may be determined that the verification result of the encrypted encoded information 1 is verification failure. The second client may send the verification result to the background server.

Optionally, since the identifier of the first client, the identifier of the first data, the data fingerprint corresponding to the first data, and the hash value corresponding to the first data information may be correspondingly stored in the preset database, if the verification result of the encrypted encoded information is that the verification is successful, the background server may determine the hash value corresponding to the first data information in the preset database according to the identifier of the first client, and call and execute the chain code to obtain the corresponding first data information in the alliance chain server according to the hash value.

For example, if the background server can determine 2 pieces of first data information according to the identifier of the first client, where the first data information 1 corresponds to the hash value 1 and the first data information 2 corresponds to the hash value 2, the corresponding first data information 1 may be obtained in the federated chain server according to the hash value 1, and the corresponding first data information 2 may be obtained in the federated chain server according to the hash value 2.

S503, determining an interstellar file system storage address corresponding to the first data in the first data information.

Because the first data information is obtained by encrypting the data fingerprint corresponding to the first data, the IPFS storage address corresponding to the first data and the coding information of the first client, the first data information can be decrypted to obtain the data fingerprint corresponding to the first data, the IPFS storage address corresponding to the first data and the coding information of the first client, and therefore the IPFS storage address corresponding to the first data can be determined.

For example, if the first data information 1 is acquired in the federated chain server, the data fingerprint 1, the IPFS storage address 1 and the encoded information 1 corresponding to the first client corresponding to the first data may be obtained for the first data information 1. The IPFS memory address corresponding to the first data may be determined to be IPFS memory address 1.

S504, according to the interstellar file system storage address, acquiring first data in the interstellar file system server, and sending a data acquisition result corresponding to the data acquisition request to the first client.

After the background server determines the IPFS storage address corresponding to the first data, the first data may be obtained from the IPFS server according to the IPFS storage address. The background server may send a data acquisition result corresponding to the data acquisition request to the first client. The data acquisition result includes first data.

For example, if the IPFS storage address determined in the first data information is IPFS storage address 1, the background server may obtain the first data 1 from the IPFS storage address 1 in the IPFS server. The background server may send a data acquisition result corresponding to the data acquisition request to the first client, where the data acquisition result may include the first data 1.

Optionally, since the identifier of the first data and the data fingerprint corresponding to the first data are stored in the preset database, after the background server receives the first data, hash operation can be performed on the first data to obtain a new data fingerprint, and the original data fingerprint corresponding to the first data is obtained in the preset database. The new data fingerprint and the original data fingerprint can be compared, and if the new data fingerprint and the original data fingerprint are consistent, the first data is not tampered; if the first data are inconsistent, the first data are tampered.

Optionally, after receiving the first data, the client may perform visual display according to the first data.

In this embodiment of the present application, the background server may acquire a data acquisition request sent by the first client, and acquire first data information corresponding to the first data in the coalition chain server according to the coding information. The background server can determine an IPFS storage address corresponding to the first data in the first data information, acquire the first data in the IPFS server according to the IPFS storage address, and send a data acquisition result corresponding to the data acquisition request to the first client. Because the first data information corresponding to the first data is required to be acquired in the alliance chain server, the IPFS storage address is determined in the first data information, and then the first data is acquired in the IPFS server according to the IPFS storage address, so that the safety of the data is improved.

Fig. 6 is a schematic structural diagram of a data storage device provided in the present application, referring to fig. 6, the data storage device 10 includes: a receiving module 11, a first storage module 12, a first determining module 13 and a second storage module 14, wherein,

the receiving module 11 is configured to receive first data sent by a first client;

the first storage module 12 is configured to store the first data in an interplanetary file system IPFS server through a first application program interface API;

the first determining module 13 is configured to determine first data information corresponding to the first data, where the first data information includes at least one of the following: the method comprises the steps of obtaining a data fingerprint corresponding to first data, an IPFS storage address corresponding to the first data and coding information corresponding to a first client;

the second storage module 14 is configured to store the first data information in a federated chain server through a second API.

The data storage device provided in the embodiment of the present application may execute the technical solution shown in the foregoing method embodiment, and its implementation principle and beneficial effects are similar, and will not be described herein again.

In a possible embodiment, the first determining module 13 is specifically configured to:

In a possible implementation manner, the receiving module 11 is further configured to receive a hash value corresponding to the first data information sent by the coalition chain server;

in a possible implementation manner, the receiving module 11 is further configured to receive a data acquisition request of a first client, where the data acquisition request includes coding information corresponding to the first client;

Fig. 7 is a schematic structural diagram of another data storage device according to an embodiment of the present application. On the basis of the data storage device 10 shown in fig. 6, the data storage device 10 may further include: a third storage module 15, a transmission module 16, a first acquisition module 17, a second determination module 18 and a second acquisition module 19, wherein,

the third storage module 15 is configured to store the hash value in a preset database.

The sending module 16 is configured to send a storage result corresponding to the first data to the first client, where the storage result is successful or failed in storage.

The first obtaining module 17 is configured to obtain, according to the encoding information, first data information corresponding to the first data in a federation chain server;

the second determining module 18 is configured to determine, in the first data information, an IPFS storage address corresponding to the first data;

the second obtaining module 19 is configured to obtain the first data in an IPFS server according to the IPFS storage address;

the sending module 16 is further configured to send a data acquisition result corresponding to the data acquisition request to the first client, where the data acquisition result includes the first data.

In a possible embodiment, the first acquisition module 17 is further configured to:

encrypting the coded information to obtain encrypted coded information;

sending the encrypted coded information to a second client;

An embodiment of the present application provides a schematic structural diagram of an electronic device, referring to fig. 8, the electronic device 20 may include a processor 21 and a memory 22. The processor 21, the memory 22, and the like are illustratively interconnected by a bus 23.

The memory 22 stores computer-executable instructions;

the processor 21 executes computer-executable instructions stored in the memory 22, causing the processor 21 to perform the data storage method as shown in the method embodiments described above.

The electronic device shown in fig. 8 may be a background server as described in any of the embodiments above.

All or part of the steps for implementing the method embodiments described above may be performed by hardware associated with program instructions. The foregoing program may be stored in a readable memory. The program, when executed, performs steps including the method embodiments described above; and the aforementioned memory (storage medium) includes: read-only memory (ROM), RAM, flash memory, hard disk, solid state disk, magnetic tape, floppy disk, optical disk, and any combination thereof.

Embodiments of the present application provide a computer readable storage medium having stored therein computer executable instructions for implementing the data storage method described in the above method embodiments when the computer executable instructions are executed by a processor.

Embodiments of the present application may also provide a computer program product, including a computer program, which, when executed by a processor, may implement the data storage method shown in the foregoing method embodiments.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

It will be apparent to those skilled in the art that various modifications and variations can be made to the embodiments of the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the embodiments of the present application fall within the scope of the claims and the equivalents thereof, the present application is intended to encompass such modifications and variations.

In the present application, the term "include" and variations thereof may refer to non-limiting inclusion; the term "or" and variations thereof may refer to "and/or". The terms "first," "second," and the like in this application are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. In the present application, "plurality" means two or more. "and/or", describes an association relationship of an association object, and indicates that there may be three relationships, for example, a and/or B, and may indicate: a exists alone, A and B exist together, and B exists alone. The character "/" generally indicates that the context-dependent object is an "or" relationship.

Claims

1. A method of data storage, the method comprising:

receiving an HTTP POST request sent by a first client to acquire first data and a first client identifier;

carrying out hash operation on the first data to determine a data fingerprint corresponding to the first data;

receiving an interstellar file system storage address corresponding to first data sent by an interstellar file system IPFS server;

encrypting the equipment identifiers, the numbers and the time stamps to obtain encryption information corresponding to the clients respectively;

encrypting the plurality of encrypted information through a homomorphic encryption algorithm to obtain common coded information, wherein the common coded information is used for the plurality of clients; the plurality of clients includes the first client;

determining the common coding information as coding information corresponding to the first client, so that when a data acquisition request sent by the first client is acquired, the coding information is subjected to encryption processing according to the coding information to obtain encrypted coding information; the data acquisition request comprises coding information corresponding to the first client and/or an identifier of the first client; sending the encrypted coding information to a second client so that the second client carries out decryption processing on the encrypted coding information once to obtain new coding information, and determining a verification result of the encrypted coding information according to whether the new coding information is consistent with the original coding information in the second client; or sending the encrypted coding information to the second client, so that the second client performs decryption processing on the encrypted coding information for multiple times to obtain device identifiers, call numbers and time stamps corresponding to multiple clients, and determining whether the device identifiers, the call numbers and the time stamps corresponding to the multiple clients comprise the device identifiers and the call numbers corresponding to the second client or not so as to determine the verification result of the encrypted coding information; receiving a verification result of the encrypted coding information sent by the second client, and acquiring first data information corresponding to the first data from a alliance chain server according to the coding information when the verification result is that verification is successful;

Determining first data information according to the data fingerprint corresponding to the first data, the interstellar file system storage address corresponding to the first data and the coding information corresponding to the first client;

2. The method according to claim 1, wherein the method further comprises:

and storing the hash value in a preset database.

3. The method according to claim 1, wherein the method further comprises:

4. A method according to any one of claims 1-3, wherein the method further comprises:

5. The method of claim 4, wherein obtaining first data information corresponding to the first data in a federated chain server based on the encoded information comprises:

encrypting the coded information to obtain encrypted coded information;

sending the encrypted coded information to a second client;

6. A data storage device, comprising: the device comprises a receiving module, a first storage module, a first determining module and a second storage module, wherein,

the receiving module is used for receiving an HTTP POST request sent by the first client to obtain first data and a first client identifier;

The first determining module is used for determining first data information according to the data fingerprint corresponding to the first data, the interstellar file system storage address corresponding to the first data and the coding information corresponding to the first client;

the second storage module is used for storing the first data information in the alliance chain server through a second API;

the first determining module is specifically configured to receive a device identifier, a call number and a timestamp sent by each client;

determining the common coding information as coding information corresponding to the first client, so that when a data acquisition request sent by the first client is acquired, the coding information is subjected to encryption processing according to the coding information to obtain encrypted coding information; the data acquisition request comprises coding information corresponding to the first client and/or an identifier of the first client; sending the encrypted coding information to a second client so that the second client carries out decryption processing on the encrypted coding information once to obtain new coding information, and determining a verification result of the encrypted coding information according to whether the new coding information is consistent with the original coding information in the second client; or sending the encrypted coding information to the second client, so that the second client performs decryption processing on the encrypted coding information for multiple times to obtain device identifiers, call numbers and time stamps corresponding to multiple clients, and determining whether the device identifiers, the call numbers and the time stamps corresponding to the multiple clients comprise the device identifiers and the call numbers corresponding to the second client or not so as to determine the verification result of the encrypted coding information; and receiving a verification result of the encrypted coding information sent by the second client, and acquiring first data information corresponding to the first data from a alliance chain server according to the coding information when the verification result is verification success.

7. An electronic device, comprising: a processor and a memory;

the memory stores computer-executable instructions;

the processor executing computer-executable instructions stored in the memory, causing the processor to perform the data storage method of any one of claims 1 to 5.

8. A computer readable storage medium having stored therein computer executable instructions for implementing the data storage method of any one of claims 1 to 5 when the computer executable instructions are executed by a processor.