Data transaction system, method and device, storage medium and product
By using data sandboxes and asymmetric encryption technology in data transactions, the problem of data leakage caused by unauthorized sales of data by data operators is solved, and secure encrypted transmission and sharing of data is achieved.
Patent Information
- Application Number
- CN202511674354.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-11-14
- Publication Date
- 2026-03-06
AI Technical Summary
In traditional data transactions, data operators sell data to data users without authorization, leading to the exposure of sensitive information in the original data provided by the data provider, causing data security issues and hindering data circulation and sharing.
The raw data is processed using data sandbox technology, and the data key is encrypted using the data provider's public key. Encryption is performed only before the data is stored on disk. Combined with asymmetric encryption algorithms, the privacy of the data key is protected, ensuring that the data is encrypted before transmission. Data users need to decrypt the data using the data provider's private key.
It effectively avoids the risk of leakage from persistent storage of plaintext data, protects the privacy of data keys, ensures the data security of data providers, and promotes data circulation and sharing.
Smart Images

Figure CN121614550A_ABST
Abstract
Description
Technical Field
[0001] This disclosure relates to the field of data management technology, and in particular to a data trading system, method, device, storage medium and product. Background Technology
[0002] Currently, my country's data infrastructure construction, including trusted data spaces, is booming. Data management is the primary core function of data infrastructure, and the sharing and circulation of data from data providers under trusted control is a key path to achieving sound data management. The participants in data transactions include data providers, data users, and data operators. Data operators rely on data trading platforms to match the supply and demand of data users and data providers. Traditional data trading processes suffer from trust barriers, such as data operators selling data to data users without authorization, or data operators or data users exposing sensitive information from the original data. These factors, detrimental to data providers, harm their rights and interests, hindering data circulation and sharing.
[0003] In related technologies, data operators can often sell data to data users without the data provider's consent, leading to the exposure of sensitive information such as the data provider's original data, causing data security issues, and hindering data circulation and sharing. Summary of the Invention
[0004] To address the aforementioned technical issues, this disclosure provides a data trading system, method, device, storage medium, and product to resolve the problem of sensitive information such as raw data from the first device belonging to the data provider being exposed.
[0005] In a first aspect, this disclosure provides a data trading system, comprising a first device, a second device, and a data trading apparatus. The data trading apparatus is configured to receive an acquisition request from the second device when the second device and the first device are trading target data, and based on the acquisition request, send the encrypted data and encrypted data key corresponding to the target data to the second device. The target data is obtained by processing the original data of the first device through a sandbox belonging to the first device, and the encrypted data key is obtained by encrypting the plaintext data key of the encrypted data through the sandbox using the public key generated by the first device. The second device is configured to send the received encrypted data key to the first device. The first device is configured to decrypt the encrypted data key using a locally stored private key to obtain a plaintext data key, and send the plaintext data key to the second device, with a one-to-one correspondence between the public and private keys. The second device is further configured to decrypt the encrypted data using the received plaintext data key to obtain the target data.
[0006] Secondly, the present invention provides a data transaction method, the method comprising: when a second device and a first device conduct a transaction of target data, receiving an acquisition request sent from the second device, the acquisition request being used to acquire ciphertext data and a ciphertext data key corresponding to the target data, the target data being obtained by processing the original data of the first device through a sandbox belonging to the first device, and the ciphertext data key being a key obtained by encrypting the plaintext data key of the ciphertext data through the sandbox and using a public key generated by the first device; based on the acquisition request, sending the ciphertext data and the ciphertext data key to the second device, so that the second device sends the ciphertext data key to the first device to obtain the plaintext data key after decrypting the ciphertext data key, and using the plaintext data key to decrypt the ciphertext data to obtain the target data.
[0007] Thirdly, the present invention provides a data transaction device, which includes: a receiving module, configured to receive an acquisition request sent by the second device when the second device and the first device conduct a transaction of target data, the acquisition request being used to acquire the ciphertext data and the ciphertext data key corresponding to the target data, wherein the target data is obtained by processing the original data of the first device through a sandbox belonging to the first device, and the ciphertext data key is a key obtained by encrypting the plaintext data key of the ciphertext data through the sandbox and using the public key generated by the first device.
[0008] The sending module is also used to send ciphertext data and a ciphertext data key to a second device based on an acquisition request, so that the second device sends the ciphertext data key to the first device to obtain the plaintext data key after decrypting the ciphertext data key, and uses the plaintext data key to decrypt the ciphertext data to obtain the target data.
[0009] Fourthly, the present invention provides a computer device, comprising: a memory and a processor, wherein the memory and the processor are communicatively connected to each other, the memory stores computer instructions, and the processor executes the computer instructions to perform the data transaction method described in the second aspect or any corresponding embodiment thereof.
[0010] Fifthly, the present invention provides a computer-readable storage medium storing computer instructions for causing a computer to perform the data transaction method described in the second aspect or any of its corresponding embodiments.
[0011] In a sixth aspect, the present invention provides a computer program product, including computer instructions for causing a computer to execute the data transaction method described in the second aspect or any corresponding embodiment thereof. Attached Figure Description
[0012] The accompanying drawings, which are incorporated in and form a part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure.
[0013] To more clearly illustrate the technical solutions in the embodiments of this disclosure or the prior art, the accompanying drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0014] Figure 1 A topology diagram of a data transaction system provided in this application embodiment; Figure 2 A schematic diagram illustrating a data encryption process provided in an embodiment of this application; Figure 3 A flowchart of a data transaction method provided in an embodiment of the present invention; Figure 4 A flowchart illustrating yet another data transaction method provided in this application embodiment; Figure 5 A device structure block diagram of a data transaction apparatus provided in an embodiment of this application; Figure 6 This is a schematic diagram of the structure of a computer device provided in an optional embodiment of this application. Detailed Implementation
[0015] To better understand the above-mentioned objectives, features, and advantages of this disclosure, the solutions disclosed herein will be further described below. It should be noted that, unless otherwise specified, the embodiments and features described herein can be combined with each other.
[0016] Numerous specific details are set forth in the following description in order to provide a full understanding of this disclosure, but this disclosure may also be implemented in other ways different from those described herein; obviously, the embodiments in the specification are only some, and not all, of the embodiments of this disclosure.
[0017] This application embodiment applies to a scenario where a second device belonging to the data user and a first device belonging to the data provider conduct data transactions.
[0018] In related technologies, a third-party device belonging to a data operator, after acquiring data from a first-party device, directly trades the data to a second-party device belonging to the data user without the permission of the first-party device, which is the data provider. Since data transactions typically require processing of the raw data before entering the transaction process, traditional data processing and encrypted storage schemes require that the plaintext data be persisted to disk before encryption and transmission. This persistent storage of plaintext data poses a risk of data leakage. Furthermore, in traditional data encryption methods, the encryption key is retained by the data encryption executor. If this centralized service is compromised, there is a significant risk of large-scale data leakage. This exposes sensitive information such as the raw data of the first-party device, causing data security issues and hindering data flow and sharing.
[0019] To address the aforementioned technical problems, this application provides a data trading system. In this system, when a second device and a first device trade target data, the data provider processes the original data using a data sandbox and creates a corresponding data key for the processed data. The processed data is encrypted using the data key, and the data key itself is encrypted using a public key provided by the data provider. After the data operator sells the data to the data user, both the encrypted data and the encrypted data key are distributed. Before using the data, the second device of the data user needs authorization from the first device of the data provider and decrypts the encrypted data key using the private key from the asymmetric key locally managed by the first device of the data provider. Only then can the second device decrypt the data using the plaintext data key and access the data. In this approach, by combining data encryption with data sandboxing technology, the data processed in the data sandbox resides only in the sandbox memory. Encryption is performed before the data is stored on disk, effectively avoiding the risk of data leakage that may exist from persistent storage of plaintext data. At the same time, the data encryption key only resides temporarily in the data sandbox memory during data processing and encryption. The plaintext data key is immediately cleared after data encryption is completed. The ciphertext data key obtained by using the user's public key and an asymmetric encryption algorithm can only be decrypted using the private key that is privately stored locally on the data provider's first device. This effectively protects the privacy of the data key and the data security of the data provider.
[0020] This application provides a data trading system, such as Figure 1 As shown, Figure 1 This is a topology diagram of a data transaction system provided in an embodiment of this application. Figure 1In the data trading system 100, there are data trading devices 101, a first device 102, and a second device 103. Data trading devices 101 are connected to the second device 103; the second device 103 is connected to the first device 102; and the first device 102 is connected to the data trading devices 101.
[0021] The data trading device 101 can be any device with communication and computing functions. For example, the data trading device 101 can be a server or a cloud server. The data trading device 101 includes a sandbox module and an encryption module. The sandbox module runs the sandbox of the first device. The sandbox is also called a data sandbox.
[0022] The first device 102 can be any device belonging to the data provider. The first device 102 stores the raw data.
[0023] The second device 103 can be any device belonging to the data user.
[0024] Based on the above data transaction system, the data transaction device 101 is used to receive an acquisition request sent by the second device 103 when the second device 103 and the first device 102 conduct a transaction of target data, and based on the acquisition request, send the encrypted data and the encrypted data key corresponding to the target data to the second device 103.
[0025] The second device 103 is used to send the received encrypted data key to the first device 102.
[0026] The first device 102 is used to decrypt the ciphertext data key using a locally stored private key to obtain the plaintext data key, and then send the plaintext data key to the second device 103.
[0027] The second device 103 is also used to decrypt the ciphertext data using the received plaintext data key to obtain the target data.
[0028] The retrieval request is used to request the retrieval of target data.
[0029] The target data is obtained by processing the raw data of the first device 102 through the sandbox of the first device 102.
[0030] The encrypted data corresponding to the target data is obtained by encrypting the target data through the sandbox of the first device 102.
[0031] The plaintext data key is randomly generated through the sandbox of the first device 102.
[0032] The ciphertext data key is obtained by encrypting the plaintext data key of the ciphertext data through a sandbox and using the public key generated by the first device 102.
[0033] There is a one-to-one correspondence between public and private keys.
[0034] Specifically, after receiving the acquisition request, the data transaction device parses the acquisition request to obtain the first storage address of the encrypted data and the second storage address of the encrypted data key; it retrieves the encrypted data stored at the first storage address and the encrypted data key at the second storage address from its own persistent storage medium, and sends the encrypted data and encrypted data key to the second device.
[0035] In one example, before receiving an acquisition request from a second device, the data transaction device receives raw data and a public key from a first device through a sandbox, processes the raw data to obtain target data, randomly generates a plaintext data key, encrypts the target data using the plaintext data key to obtain ciphertext data, and encrypts the plaintext data key using the public key to obtain the ciphertext data key; and stores the ciphertext data and the ciphertext data key in its own persistent storage medium.
[0036] Specifically, such as Figure 2 As shown, Figure 2 This is a schematic diagram illustrating a data encryption process provided in an embodiment of this application. Figure 2 In this process, the first device sends the raw data to a data sandbox, where it processes the data to obtain the plaintext data processing result (i.e., the target data). The target data is then encrypted using the plaintext data key (symmetric encryption) to obtain the ciphertext data processing result (ciphertext data). Simultaneously, the plaintext data key is encrypted using the public key generated by the first device of the data provider (asymmetric encryption) to obtain the ciphertext data key. The ciphertext data key and the ciphertext data processing result are then persistently stored.
[0037] Optionally, after processing the raw data, the data transaction device temporarily stores the target data and plaintext data key in the sandbox memory, and after storing the ciphertext data and ciphertext data key in its own persistent storage medium, erases the target data and plaintext data key residing in the sandbox memory.
[0038] Understandably, the target data (plaintext) processed through the sandbox resides only in the sandbox memory. Encryption is performed before the data is written to disk, effectively avoiding the risk of data leakage that may exist if plaintext data is stored on persistent storage media. Furthermore, the plaintext data key only resides temporarily in the data sandbox memory during data processing and encryption. The plaintext data key is immediately cleared after data encryption is completed, effectively protecting the privacy of the data key.
[0039] In one example, the first device is also used to locally generate public and private keys using an asymmetric algorithm, store the private key locally, and send the public key to a sandbox running on the data transaction device.
[0040] Furthermore, after the second device sends the received encrypted data key to the first device, the first device receives the encrypted data key sent by the second device; based on the preset identifier and preset mapping relationship of the public key carried in the encrypted data key, it retrieves the private key corresponding to the preset identifier from the local storage, and uses the private key to decrypt the encrypted data key to obtain the plaintext data key.
[0041] Understandably, even if the second device of the data user obtains the encrypted data and its key, it still cannot directly use the target data. It needs authorization from the first device of the data provider. The first device must decrypt the encrypted data key using its local private key before the second device can decrypt the encrypted data using the plaintext key and obtain the target data. This method, which uses an asymmetric encryption algorithm to encrypt the encrypted data with the public key generated by the data provider, and requires a private key secretly stored locally by the data provider for decryption, effectively protects the privacy of the data key, prevents the leakage of the original data, and ensures the security of the original data.
[0042] This embodiment provides a data transaction method that can be used in the aforementioned data transaction system. Figure 3 A flowchart of a data transaction method provided in this application embodiment is shown below. Figure 3 As shown, the process includes the following steps: S301, when the second device and the first device are trading target data, the data transaction device receives an acquisition request sent by the second device, and based on the acquisition request, sends the encrypted data and the encrypted data key corresponding to the target data to the second device.
[0043] S302, the second device sends the received encrypted data key to the first device.
[0044] S303, the first device uses the locally stored private key to decrypt the encrypted data key to obtain the plaintext data key, and then sends the plaintext data key to the second device.
[0045] S304, the second device uses the received plaintext data key to decrypt the ciphertext data and obtain the target data.
[0046] This embodiment provides yet another data transaction method, which can be used in the aforementioned data transaction device. Figure 4 A flowchart of another data transaction method provided in the embodiments of this application is shown below. Figure 4 As shown, the process includes the following steps: S401, when the second device and the first device are trading target data, a request for acquisition is received from the second device.
[0047] S402, based on the acquisition request, the encrypted data and the encrypted data key are sent to the second device, so that the second device sends the encrypted data key to the first device to obtain the plaintext data key after decrypting the encrypted data key, and uses the plaintext data key to decrypt the encrypted data to obtain the target data.
[0048] In some optional implementations, the sandbox receives the raw data and public key sent by the first device, processes the raw data to obtain the target data, randomly generates a plaintext data key through the sandbox, encrypts the target data using the plaintext data key to obtain ciphertext data, encrypts the plaintext data key using the public key through the sandbox to obtain the ciphertext data key, and stores the ciphertext data and the ciphertext data key in its own persistent storage medium.
[0049] based on Figure 4 This method combines data encryption with data sandboxing technology. Data processed in the sandbox resides only in the sandbox memory and is encrypted before being stored on disk, effectively avoiding the risk of data leakage that may exist from persistent storage of plaintext data. At the same time, the data encryption key only resides temporarily in the data sandbox memory during data processing and encryption. The plaintext data key is immediately cleared after data encryption is completed. The ciphertext data key obtained by using the user's public key and an asymmetric encryption algorithm can only be decrypted using the private key that is privately stored locally on the data provider's first device, effectively protecting the privacy of the data key and the data security of the data provider.
[0050] This embodiment also provides a data transaction apparatus for implementing the above embodiments and preferred embodiments; details already described will not be repeated. As used below, the term "module" can refer to a combination of software and / or hardware that performs a predetermined function. Although the apparatus described in the following embodiments is preferably implemented in software, hardware implementation, or a combination of software and hardware, is also possible and contemplated.
[0051] This embodiment provides a data transaction device, such as... Figure 5 As shown, Figure 5 A device structure block diagram of a data trading apparatus provided in this application embodiment; the data trading apparatus includes: The receiving module 501 is used to receive an acquisition request sent by the second device when the second device and the first device are trading target data. The acquisition request is used to acquire the ciphertext data and ciphertext data key corresponding to the target data. The target data is obtained by processing the original data of the first device through the sandbox of the first device. The ciphertext data key is obtained by encrypting the plaintext data key of the ciphertext data through the sandbox and using the public key generated by the first device.
[0052] The sending module 502 is also used to send ciphertext data and ciphertext data key to a second device based on an acquisition request, so that the second device sends the ciphertext data key to the first device to obtain the plaintext data key after decrypting the ciphertext data key, and uses the plaintext data key to decrypt the ciphertext data to obtain the target data.
[0053] In some optional implementations, the processing module 503 is configured to receive raw data and a public key sent by the first device through a sandbox, process the raw data to obtain target data, randomly generate a plaintext data key through the sandbox, encrypt the target data using the plaintext data key to obtain ciphertext data, encrypt the plaintext data key using the public key through the sandbox to obtain ciphertext data key, and store the ciphertext data and ciphertext data key in its own persistent storage medium.
[0054] Further functional descriptions of the above modules and units are the same as those in the corresponding embodiments described above, and will not be repeated here.
[0055] In this embodiment, the data transaction device is presented in the form of a functional unit. Here, a unit refers to an ASIC (Application Specific Integrated Circuit) circuit, a processor and memory that execute one or more software or fixed programs, and / or other devices that can provide the above functions.
[0056] This invention also provides a computer device having the above-described features. Figure 5 The data transaction device shown.
[0057] Please see Figure 6 , Figure 6 This is a schematic diagram of the structure of a computer device provided in an optional embodiment of this application, such as... Figure 6As shown, the computer device includes one or more processors 10, memory 20, and interfaces for connecting the components, including high-speed interfaces and low-speed interfaces. The components communicate with each other via different buses and can be mounted on a common motherboard or otherwise installed as needed. The processors can process instructions executed within the computer device, including instructions stored in or on memory to display graphical information of a GUI on external input / output devices (such as display devices coupled to the interfaces). In some alternative implementations, multiple processors and / or multiple buses can be used with multiple memories and multiple memory modules, if desired. Similarly, multiple computer devices can be connected, each providing some of the necessary operations (e.g., as a server array, a group of blade servers, or a multiprocessor system). Figure 6 Take a processor 10 as an example.
[0058] Processor 10 may be a central processing unit, a network processor, or a combination thereof. Processor 10 may further include a hardware chip. The hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof. The programmable logic device may be a complex programmable logic device (CAMP), a field-programmable gate array (FPGA), a general-purpose array logic (GDA), or any combination thereof.
[0059] The memory 20 stores instructions executable by at least one processor 10 to cause the at least one processor 10 to perform the method shown in the above embodiments.
[0060] The memory 20 may include a program storage area and a data storage area. The program storage area may store the operating system and applications required for at least one function; the data storage area may store data created based on the use of the computer device. Furthermore, the memory 20 may include high-speed random access memory and may also include non-transitory memory, such as at least one disk storage device, flash memory device, or other non-transitory solid-state storage device. In some alternative embodiments, the memory 20 may optionally include memory remotely located relative to the processor 10, and these remote memories may be connected to the computer device via a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.
[0061] The memory 20 may include volatile memory, such as random access memory; the memory may also include non-volatile memory, such as flash memory, hard disk or solid-state drive; the memory 20 may also include a combination of the above types of memory.
[0062] The computer device also includes a communication interface 30 for communicating with other devices or communication networks.
[0063] This invention also provides a computer-readable storage medium. The methods described above according to embodiments of the invention can be implemented in hardware or firmware, or implemented as computer code that can be recorded on a storage medium, or implemented as computer code downloaded via a network and originally stored on a remote storage medium or a non-transitory machine-readable storage medium and then stored on a local storage medium. Thus, the methods described herein can be processed by software stored on a storage medium using a general-purpose computer, a dedicated processor, or programmable or dedicated hardware. The storage medium can be a magnetic disk, optical disk, read-only memory, random access memory, flash memory, hard disk, or solid-state drive, etc.; further, the storage medium can also include combinations of the above types of memory. It is understood that computers, processors, microprocessor controllers, or programmable hardware include storage components capable of storing or receiving software or computer code, which, when accessed and executed by the computer, processor, or hardware, implements the methods shown in the above embodiments.
[0064] This invention provides a computer program product, which includes computer instructions for causing a computer to execute the method of any embodiment of this invention.
[0065] It should be noted that, in this document, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.
[0066] The above description is merely a specific embodiment of this disclosure, enabling those skilled in the art to understand or implement it. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of this disclosure. Therefore, this disclosure is not to be limited to the embodiments described herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims
1. A data transaction system, characterized by, The data transaction system comprises a first device, a second device and a data transaction device; The data transaction device is configured to receive an acquisition request sent by the second device when the second device performs a transaction of target data with the first device, and send, based on the acquisition request, ciphertext data corresponding to the target data and a ciphertext data key to the second device, the target data being obtained by processing original data of the first device through a sandbox of the first device, and the ciphertext data key being a key obtained by encrypting a plaintext data key of the ciphertext data using a public key generated by the sandbox and the first device; The second device is configured to send the received ciphertext data key to the first device; The first device is configured to decrypt the ciphertext data key using a locally stored private key to obtain the plaintext data key, and send the plaintext data key to the second device, the public key and the private key corresponding to each other; The second device is further configured to decrypt the ciphertext data using the received plaintext data key to obtain the target data.
2. The data transaction system of claim 1, wherein, The data transaction device is further configured to: receive the original data and the public key sent by the first device through the sandbox, process the original data to obtain the target data, randomly generate the plaintext data key, encrypt the target data using the plaintext data key to obtain the ciphertext data, and encrypt the plaintext data key using the public key to obtain the ciphertext data key; store the ciphertext data and the ciphertext data key in a self-persistent storage medium.
3. The data transaction system of claim 1, wherein, The data transaction device is specifically configured to: parse the acquisition request to obtain a first storage address of the ciphertext data and a second storage address of the ciphertext data key; obtain the ciphertext data stored in the first storage address and the ciphertext data key stored in the second storage address from the self-persistent storage medium, and send the ciphertext data and the ciphertext data key to the second device.
4. The data transaction system of claim 1, wherein, The first device is further configured to locally generate the public key and the private key through an asymmetric algorithm, store the private key locally, and send the public key to the sandbox running on the data transaction device.
5. The data transaction system of claim 1, wherein, The first device is specifically configured to receive the ciphertext data key sent by the second device, obtain the private key corresponding to a preset identifier of the public key according to a preset mapping relationship from the local storage, and decrypt the ciphertext data key using the private key to obtain the plaintext data key.
6. A data transaction method, characterized by, The method is applied to a data transaction device, and the method comprises: When the second device transacts with the first device for target data, an acquisition request is received from the second device, the acquisition request being used to acquire ciphertext data corresponding to the target data and a ciphertext data key, the target data being obtained by processing original data of the first device through a sandbox of the first device, and the ciphertext data key being a key obtained by encrypting a plaintext data key of the ciphertext data through the sandbox and using a public key of the first device to encrypt the plaintext data key; Based on the acquisition request, the ciphertext data and the ciphertext data key are sent to the second device, so that the second device sends the ciphertext data key to the first device to obtain a plaintext data key decrypted from the ciphertext data key, and decrypts the ciphertext data using the plaintext data key to obtain the target data.
7. The method of claim 6, wherein, The method further comprises: Receiving the original data and the public key sent by the first device through the sandbox, processing the original data to obtain the target data; Randomly generating the plaintext data key through the sandbox, encrypting the target data using the plaintext data key to obtain the ciphertext data; Encrypting the plaintext data key using the public key through the sandbox to obtain the ciphertext data key; Storing the ciphertext data and the ciphertext data key in a persistent storage medium.
8. A computer device, comprising: Comprises: A memory and a processor, which are in communication connection with each other, the memory stores computer instructions, and the processor executes the computer instructions to perform the data transaction method of claim 6 or 7.
9. A computer-readable storage medium, characterized in that, The computer readable storage medium stores computer instructions, and the computer instructions are used to make the computer execute the data transaction method of claim 6 or 7.
10. A computer program product, characterised in that, Comprise computer instructions, the computer instructions are used to make the computer execute the data transaction method of claim 6 or 7.