A data exchange method and apparatus

Abstract

The application relates to the technical field of data sharing exchange, and discloses a data exchange method and device, the device comprises a data connector, a data exchange server and a storage server; the method comprises the following steps: data / application registration, data encryption upload, data reception and storage, data exchange application, data exchange audit and data exchange application. In the data exchange process, the data exchange audit mainly comprises two types of business audit and system audit; wherein the business audit comprises but is not limited to the audit of processes such as data registration, data exchange application, data exchange audit and data application analysis; the system audit is mainly aimed at the security of the running state of the system, and all key operation records are stored through a block chain, so that the credibility of the data exchange is greatly improved, and the data exchange process is convenient to use, has the advantages of high efficiency and safety in use.

Description

Technical Field

[0001] This application relates to the field of data sharing and exchange technology, and for example to a data exchange method and apparatus. Background Technology

[0002] Data exchange refers to the process of transferring data between different systems, applications, or devices. This data can be in the form of text, images, audio, video, etc., and is transmitted and shared between different systems. Data exchange is usually carried out to achieve purposes such as information sharing, collaborative work, and system integration. With the popularization of the Internet and the acceleration of digitalization, data sharing and exchange have become key drivers of its development. However, the data exchange process faces many security risks, such as data tampering, data leakage, and illegal use of data.

[0003] Existing data exchange methods are often based on traditional encryption methods and access control technologies, such as communication encryption and RBAC models. While agencies can use these to ensure data transmission security and control access rights, data users can still obtain the original data. Even with security measures such as encryption, it is still impossible to completely eliminate security vulnerabilities, and security protection needs to be continuously strengthened.

[0004] In implementing the embodiments of this disclosure, it was found that the related technologies have at least the following problems: Existing patents disclose a data exchange method and apparatus between a main chain and a side chain, including data exchange from the main chain to the side chain. An arbitration node elected by the main chain system converts a first cross-chain data interaction request on the main chain system into a second cross-chain data interaction request. Since the second cross-chain data interaction information contains the first cross-chain data interaction information and SPV proof path information for the side chain system to verify, the side chain system does not need to pre-store all blockchain header information of the main chain system to verify transaction requests on the main chain system. It also includes data exchange from the side chain to the main chain. The arbitration node not only needs to convert a third cross-chain data interaction request into a fourth cross-chain data interaction request that can be recognized by the main chain system, but also needs to pre-set a number of arbitration nodes to perform signature verification of the fourth cross-chain data interaction request. The main chain system does not need to store the block information of the side chain system to achieve secure and reliable data exchange from the side chain system to the main chain system. However, with the increase of data volume and data source, the management and monitoring of the data exchange process becomes more complicated and inconvenient to use.

[0005] It should be noted that the information disclosed in the background section above is only used to enhance the understanding of the background of this application, and therefore may include information that does not constitute prior art known to those skilled in the art. Summary of the Invention

[0006] To provide a basic understanding of some aspects of the disclosed embodiments, a brief summary is given below. This summary is not intended as a general commentary, nor is it intended to identify key / important components or describe the scope of protection of these embodiments, but rather as a prelude to the detailed description that follows.

[0007] This disclosure provides a data exchange method and apparatus to address the problems of data leakage, tampering, and illegal use that are easily caused by existing exchange methods.

[0008] In some embodiments, the data exchange method includes:

[0009] Data connectors are used for data upload / download, data encryption / decryption, and data signing;

[0010] The data exchange server includes a data exchange service module, a data security sandbox, and a data exchange gateway module;

[0011] The evidence storage server includes a blockchain and a database, wherein the database is used for data hosting and the blockchain is used to provide trusted evidence storage for data exchange;

[0012] During data exchange, the data provider encrypts and signs the data through the data connector and sends the relevant data to the data exchange server. After successful verification, the data exchange server creates a virtual data security sandbox instance and encrypts and saves the data in the data security sandbox instance. The data user initiates a data exchange request to the data exchange server through the data connector. After successful verification, the data exchange server sends the request message to the data provider's data connector. After the data provider approves the request, the data exchange server invokes the data security sandbox to perform data exchange processing. The data user downloads or reads the data processing results through the data connector.

[0013] Optionally, when the data exchange server encrypts and stores the data in the data security sandbox instance, it can be hosted on the evidence storage server. The evidence storage server stores the encrypted hash of the data, the original data hash, and the data identifier.

[0014] After the evidence is stored, the data exchange server automatically cleans up the relevant data.

[0015] Optionally, after the data user issues a data exchange request and the data provider approves it, if the data is hosted in the evidence storage server, the data exchange server retrieves it from the evidence storage server through the data reading module.

[0016] Optionally, all data exchange transactions of the data exchange server can be stored on the blockchain.

[0017] Optionally, the underlying cryptographic algorithm SDK of the data connector is integrated. The modules of the data connector adopt event-driven connection, and the connection is achieved through the time-driven method between the modules to realize communication and collaboration between the modules.

[0018] Optionally, middleware is used to connect the modules of the data exchange server. The middleware provides common interfaces and protocols to help different modules communicate and exchange data.

[0019] Optionally, the evidence storage server has blockchain and database modules, and the modules are connected through the database and shared storage. Data is transferred and shared between multiple modules through the shared database and memory storage, thereby connecting different modules.

[0020] In some embodiments, the data exchange method includes the following steps:

[0021] S1. Data / Application Registration: At the data sending end, a unique data identifier is generated based on a random number generator, and the data identifier, data hash, and relevant information about the data description are registered.

[0022] S2. Encrypted data upload: The sending end uses a symmetric key to encrypt the data, signs the encrypted ciphertext and data identifier, and then uploads the data identifier, ciphertext, signature and hash related data to the receiving end.

[0023] S3. Data reception and storage: The data receiving end verifies the data signature. After successful verification, the data is decrypted and then hashed to verify whether the hash value matches the original hash value. After successful verification, the data is encrypted and stored using the data encryption key of the exchange service provider.

[0024] S4. Data exchange application: The data user selects the proposed exchange and the exchange method, and applies to the relevant data provider for data exchange.

[0025] S5. Data exchange review: After receiving the exchange review request, the relevant data provider reviews the exchange application and the exchange application. If the review is approved, the exchange service provider will proceed to the next step; otherwise, the exchange application will not be approved.

[0026] S6. Data exchange application: The exchange service provider will review and approve the corresponding data, process it according to the data application, and encrypt and sign the processed result before sending it to the data user; the data user will then decrypt the data to obtain the application result.

[0027] S7. Data exchange audit.

[0028] Preferably, the encryption key for step S3 can be obtained in real time from the receiving end via the Diffie-Hellman key exchange protocol, where the receiving end refers to the exchange service provider.

[0029] Preferably, the data application processing in step S6 is performed in a data security sandbox, and all data and applications in the data security sandbox have undergone security audits.

[0030] This invention provides a data exchange method and apparatus. It has the following beneficial effects:

[0031] The data exchange method and apparatus disclosed in this invention uniquely identify and register the data from the very beginning of the data sending process. The data is then encrypted before uploading, decrypted and verified upon receipt, and then encrypted again before storage. The data exchange is conducted using a method selected by the user, and the user must decrypt the data using a password. This ensures that the data is not leaked during the exchange process. This method guarantees that the data is secure and controllable during exchange and use, and the data user only obtains the necessary data results, without acquiring any additional data. Attached Figure Description

[0032] One or more embodiments are illustrated by way of example with reference to the accompanying drawings. These illustrations and drawings do not constitute a limitation on the embodiments. Elements having the same reference numerals in the drawings are considered similar elements. The drawings do not constitute a limitation of scale, and wherein:

[0033] Figure 1 This is a schematic diagram of the system structure of the data connector in this invention;

[0034] Figure 2 This is a schematic diagram of the system structure of the data exchange server in this invention;

[0035] Figure 3 This is a schematic diagram of the system structure of the evidence storage server in this invention;

[0036] Figure 4 This is a flowchart illustrating the data exchange method in this invention. Detailed Implementation

[0037] To provide a more detailed understanding of the features and technical content of the embodiments of this disclosure, the implementation of the embodiments of this disclosure will be described in detail below with reference to the accompanying drawings. The accompanying drawings are for illustrative purposes only and are not intended to limit the embodiments of this disclosure. In the following technical description, for ease of explanation, several details are used to provide a full understanding of the disclosed embodiments. However, one or more embodiments may still be implemented without these details. In other cases, well-known structures and devices may be simplified in their depiction to simplify the drawings.

[0038] The terms "first," "second," etc., used in the specification, claims, and accompanying drawings of this disclosure are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate for the embodiments of this disclosure described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion.

[0039] Unless otherwise stated, the term "multiple" means two or more.

[0040] In this embodiment of the disclosure, the character " / " indicates that the objects before and after it are in an "or" relationship. For example, A / B means: A or B.

[0041] The term "and / or" describes an association between objects, indicating that three relationships can exist. For example, A and / or B means: A or B, or A and B.

[0042] The term "correspondence" can refer to an association or binding relationship. The correspondence between A and B means that there is an association or binding relationship between A and B.

[0043] In this embodiment of the disclosure, such as Figure 1-3 As shown, an embodiment of the present invention provides a data exchange method, including:

[0044] The data connector is used for data upload / download, data encryption / decryption, and data signing. It serves as a user data exchange platform, allowing users to perform data upload / download, data application registration, data exchange requests, and other related business operations. The underlying cryptographic algorithm SDK is integrated for data encryption / decryption and data signing functions.

[0045] The data exchange business module is responsible for data exchange business processing. On the one hand, it includes service interfaces related to data exchange user registration and authentication, permission management, access control, certificate management, etc. On the other hand, it includes business service interfaces related to data upload and download, exchange application / approval, application registration, etc.

[0046] The data security sandbox is built on technologies such as TEE and secure containers, providing a secure and reliable execution environment for secure data exchange.

[0047] The data exchange gateway is a secure gateway for entering and exiting the data security sandbox. Data and applications entering and exiting the sandbox undergo strict security audits, access controls, and usage controls to ensure data security during exchange processing. At the same time, it calls the blockchain SDK to store relevant data on the blockchain for evidence.

[0048] Evidence storage servers mainly consist of databases and blockchains. Databases primarily handle data hosting, while blockchains provide trusted evidence storage for data exchange. Evidence storage servers are typically a server cluster that provides distributed and trusted storage for data.

[0049] During data exchange, the data provider encrypts and signs the data through the data connector and sends the relevant data to the data exchange server. After the data exchange server verifies the data, it creates a virtual data security sandbox instance and encrypts and saves the data in the data security sandbox instance. The data user initiates a data exchange request to the data exchange server through the data connector. After the data exchange server verifies the data, it sends the request message to the data provider's data connector. After the data provider approves the request, the data exchange server calls the data security sandbox to process the data exchange. The data user downloads or reads the data processing results through the data connector.

[0050] When a data exchange server encrypts and stores data in a data security sandbox instance, it can be hosted on an evidence storage server. The evidence storage server stores the encrypted hash of the data, the original data hash, and the data identifier.

[0051] After the evidence is stored, the data exchange server automatically cleans up the relevant data.

[0052] After the data user issues a data exchange request and the data provider approves it, if the data is hosted in a certificate storage server, the data exchange server retrieves it from the certificate storage server through the data reading module.

[0053] All data exchange transactions of the data exchange server are stored on the blockchain.

[0054] The underlying cryptographic algorithm SDK of the data connector is integrated. The modules of the data connector are connected by event-driven means, and the connection between the modules is achieved through time-driven means, so as to realize communication and collaboration between the modules.

[0055] The modules of the data exchange server are connected using middleware, which provides common interfaces and protocols to facilitate communication and data exchange between different modules.

[0056] The evidence storage server has blockchain and database modules, and the modules are connected through the database and shared storage. Data is transferred and shared between multiple modules through the shared database and memory storage, thereby connecting different modules.

[0057] like Figure 4 As shown, the main workflow of a data exchange device includes the following steps:

[0058] The data provider processes the data through the data connector's encryption and signing modules and sends the data to the data exchange server.

[0059] After the data exchange server verifies the data, it creates a virtual data security sandbox instance and encrypts and saves the data in the data security sandbox instance. The data can be hosted on the evidence storage server to store the encrypted hash, original data hash, and data identifier. After the evidence storage is completed, the data handover server automatically cleans up the relevant data.

[0060] The data user initiates a data exchange request to the data exchange server through the connector. After the data exchange server verifies the request, it sends the request message to the data provider's data connector. The data provider then reviews and approves the request before proceeding to the next step.

[0061] After the review is approved, the data exchange server calls the data security sandbox to process the data exchange. If the data is hosted in the evidence storage server, it needs to be retrieved from the evidence storage server through the data reading module. At the same time, all data exchange-related business is stored on the blockchain, such as the data upload process and the data exchange process.

[0062] Data users download or read data processing results by connecting to a machine.

[0063] This disclosure also discloses a method for data exchange, including the following steps:

[0064] S1. Data / Application Registration: At the data sending end, a unique data identifier is generated based on a random number generator, and the data identifier, data hash, and relevant information about the data description are registered.

[0065] User registration: After downloading and deploying the connector, users register using their mobile phone number and password, and complete real-name authentication according to relevant requirements. During connector registration, the connector generates public and private keys for each user and registers the public key information with the data exchange server.

[0066] Data Registration: The data provider processes the data according to the data template and generates a unique data identifier based on a random number generator. The data identifier and the data are then hashed. After successful registration, relevant users can see the corresponding data directory. It is also possible to configure the data to be visible only to certain users.

[0067] Application Registration: In addition to the data applications pre-installed on the data exchange server, data users can also register their own data applications according to their needs to perform application analysis. During application registration, the exchange server performs security scans and audits on the applications.

[0068] S2. Encrypted data upload: The sending end uses a symmetric key to encrypt the data, signs the encrypted ciphertext and data identifier, and then uploads the data identifier, ciphertext, signature, and hash data to the receiving end.

[0069] After logging into the connector, the data provider can randomly generate a data encryption key through the data connector and encrypt it based on the public key of the data exchange server before sending it to the data exchange server. Users can also obtain the encrypted data key from the data exchange server in real time through key exchange protocols such as Diffie-Hellman.

[0070] The data is encrypted using a symmetric key, and the encrypted ciphertext and data identifier are signed. Then, the data identifier, data ciphertext, data signature, data hash, etc., are uploaded to the data exchange server.

[0071] The data exchange server verifies the validity of the data signature and checks for data consistency based on hash verification. Otherwise, the upload fails; if verification is successful, proceed to the next step.

[0072] S3. Data reception and storage: The data receiving end verifies the data signature. After successful verification, it decrypts the data and then hashes it to verify whether the hash value matches the original hash value. After successful verification, the data exchange gateway encrypts the data using the data encryption key and sends the encrypted ciphertext, ciphertext hash, and data identifier to the data storage server. In particular, if on-chain storage is required, the data exchange gateway needs to call the blockchain SDK to perform data storage.

[0073] S4. Data exchange application: The data user selects the proposed exchange and the exchange method, and applies to the relevant data provider for data exchange.

[0074] After logging into the connector, the data user obtains the publicly available data catalog from the relevant data provider, selects the data to be exchanged and the data application, and submits a request to the data exchange server.

[0075] The data exchange server verifies the legitimacy of the exchange request. Once the verification is successful, the exchange request is sent to the connector of the relevant data provider.

[0076] S5. Data exchange review: After receiving the exchange review application, the relevant data provider reviews the exchange application and the exchange application. If the review is approved, the exchange service provider will proceed to the next step; otherwise, the exchange application will not be approved. In particular, if only some users from multiple data providers have passed the review, the data exchange application process needs to be re-initiated.

[0077] S6. Data exchange application: The exchange service provider will review and approve the corresponding data, process it according to the data application, and encrypt and sign the processed result before sending it to the data user; the data user will then decrypt the data to obtain the application result.

[0078] After the data exchange review is completed, the data exchange server creates a virtual data security sandbox instance, reads the corresponding data from the evidence storage server through the data exchange gateway, decrypts the evidence storage data, and then encrypts it using the sandbox key before uploading it to the data security sandbox.

[0079] The data security sandbox decrypts relevant data and processes it according to data application requirements. Within the security sandbox, all data processing records are stored and exchanged with the data exchange gateway, significantly improving the security of data processing.

[0080] After the data security sandbox processing is completed, the encrypted result and its signature are sent to the data exchange gateway, which then pushes the encrypted result to the data user connector.

[0081] Data users obtain application results through a connector and decrypt them locally. Preferably, the data security sandbox is cleaned up and the system reclaims resources after the data results have been downloaded or after a certain time period.

[0082] S7. Data exchange audit.

[0083] The encryption key for step S3 can be obtained in real time from the receiving end through the Diffie-Hellman key exchange protocol. The receiving end refers to the exchange service provider. In step S6, the data application processing is performed in a data security sandbox. All data and applications in the data security sandbox have undergone security audits.

[0084] In the data exchange process, data exchange auditing mainly includes two categories: business auditing and system auditing. Business auditing includes, but is not limited to, auditing processes such as data registration, data exchange application, data exchange review, and data application analysis; system auditing mainly focuses on the security of system operation, such as whether the system is operating normally and whether there are abnormal traffic phenomena. Meanwhile, all key operation records are stored on the blockchain, significantly improving the credibility of data exchange.

[0085] The foregoing description and accompanying drawings fully illustrate embodiments of this disclosure to enable those skilled in the art to practice them. Other embodiments may include structural, logical, electrical, procedural, and other changes. The embodiments represent only possible variations. Individual components and functions are optional unless explicitly required, and the order of operation may vary. Parts and features of some embodiments may be included in or replace parts and features of other embodiments. Moreover, the terminology used in this application is for describing embodiments only and is not intended to limit the claims. As used in the description of embodiments and claims, the singular forms “a,” “an,” and “the” are intended to equally include the plural forms unless the context clearly indicates otherwise. Similarly, the term “and / or” as used in this application refers to any and all possible combinations of one or more of the associated listed elements. Additionally, when used in this application, the term "comprise" and its variations "comprises" and / or "comprising" refer to the presence of stated features, integrals, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, integrals, steps, operations, elements, components, and / or groups thereof. Without further limitations, an element defined by the phrase "comprises a..." does not exclude the presence of other identical elements in the process, method, or apparatus that includes said element. In this document, each embodiment may focus on the differences from other embodiments, and similar or identical parts between embodiments can be referred to mutually. For methods, products, etc., disclosed in the embodiments, if they correspond to the method section disclosed in the embodiments, the relevant parts can be referred to the description of the method section.

[0086] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the embodiments of this disclosure. Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0087] The methods and products (including but not limited to devices and equipment) disclosed in the embodiments herein can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For instance, the division of units may be merely a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. In addition, the coupling or direct coupling or communication connection shown or discussed between each other may be through some interfaces, and the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms. The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to implement this embodiment according to actual needs. In addition, the functional units in the embodiments of this disclosure may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0088] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to embodiments of this disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. In some alternative implementations, the functions marked in the blocks may occur in a different order than that shown in the drawings. For example, two consecutive blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. In the descriptions corresponding to the flowcharts and block diagrams in the accompanying drawings, the operations or steps corresponding to different blocks may also occur in a different order than disclosed in the description, and sometimes there is no specific order between different operations or steps. For example, two consecutive operations or steps may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. Each block in a block diagram and / or flowchart, and combinations of blocks in a block diagram and / or flowchart, can be implemented using a dedicated hardware-based system that performs the specified function or action, or using a combination of dedicated hardware and computer instructions.

Claims

1. A data exchange device, characterized in that, include: A data connector is used for data upload / download, data encryption / decryption, and data signing. The underlying cryptographic algorithm SDK of the data connector is integrated. The data exchange server includes a data exchange business module, a data security sandbox, and a data exchange gateway module. The modules of the data exchange server are connected by middleware, which provides common interfaces and protocols to help different modules communicate and exchange data. When the data exchange server encrypts and saves data in the data security sandbox instance, it is hosted on an evidence storage server. The evidence storage server stores the encrypted hash of the data, the original hash of the data, and the data identifier. After the evidence storage is completed, the data exchange server automatically cleans up the relevant data. The evidence storage server includes a blockchain and a database, wherein the database is used for data hosting and the blockchain is used to provide trusted evidence storage for data exchange; During data exchange, the data provider encrypts and signs the data through the data connector and sends the relevant data to the data exchange server. After successful verification, the data exchange server creates a virtual data security sandbox instance and encrypts and saves the data within it. The data security sandbox is built based on TEE or secure container technology. The data user initiates a data exchange request to the data exchange server through the data connector. After successful verification, the data exchange server sends the request message to the data provider's data connector. After the data provider approves the request, the data exchange server invokes the data security sandbox to process the data exchange. The data user downloads or reads the data processing results through the data connector.

2. The data exchange device according to claim 1, characterized in that: After the data user issues a data exchange request and the data provider approves it, if the data is hosted in the evidence storage server, the data exchange server retrieves it from the evidence storage server through the data reading module.

3. The data exchange apparatus according to claim 1, characterized in that: All data exchange transactions of the data exchange server are stored on the blockchain.

4. The data exchange apparatus according to any one of claims 1 to 3, characterized in that: The modules of the data connector are connected via an event-driven mechanism, enabling communication and collaboration between modules through a time-driven approach.

5. A data exchange device according to claim 1, characterized in that: The evidence storage server has blockchain and database modules, and the modules are connected through the database and shared storage. Data is transmitted and shared between multiple modules through the shared database and memory storage, thereby connecting different modules.

6. A method for data exchange, characterized in that: Includes the following steps: S1. Data / Application Registration: At the data sending end, a unique data identifier is generated based on a random number generator, and the data identifier, data hash, and relevant information about the data description are registered. S2. Encrypted data upload: The sending end uses a symmetric key to encrypt the data, signs the encrypted ciphertext and data identifier, and then uploads the data identifier, ciphertext, signature and hash related data to the receiving end. S3. Data reception and storage: The data receiving end verifies the data signature. After successful verification, it decrypts the data and then hashes it to verify whether the hash value matches the original hash value. After successful verification, the data is encrypted and stored using the data encryption key of the exchange service provider. If the encrypted data is stored in a data security sandbox instance and then hosted on the evidence storage server, the data exchange server will automatically clean up the relevant original data after the evidence storage is completed. S4. Data exchange application: The data user selects the proposed exchange and the exchange method, and applies to the relevant data provider for data exchange. S5. Data exchange review: After receiving the exchange review request, the relevant data provider reviews the exchange application and the exchange application. If the review is approved, the exchange service provider will proceed to the next step; otherwise, the exchange application will not be approved. S6. Data exchange application: The exchange service provider will review and approve the corresponding data, and process it according to the data application. The data application processing is executed in a data security sandbox built based on TEE or secure container technology, and the processed result is encrypted and signed and sent to the data user. The data user decrypts the data to obtain the application result. S7. Data exchange audit, which includes business audit and system audit, and all key operation records and audit results are stored on the blockchain.

7. The method according to claim 6, characterized in that: The encryption key for step S3 can be obtained in real time from the receiving end through the Diffie-Hellman key exchange protocol, where the receiving end refers to the exchange service provider.

8. The method according to claim 6, characterized in that: In step S6, the data application processing is performed in a data security sandbox, and all data and applications in the data security sandbox have undergone security audits.

Images