A data management method, device and equipment based on trusted hardware

Abstract

The embodiments of this specification disclose a data management method, device and equipment based on trusted hardware. The scheme includes: the data owner can register a personal distributed digital identity based on blockchain technology, and establish a binding relationship between the distributed digital identity of the data owner and the trusted hardware, so that after the trusted hardware obtains the data description information used to describe the target data of the data owner that can be provided by the trusted institution, the trusted institution can be requested to verify whether the user business data required to generate the target data is stored; if the user business data required to generate the target data is stored at the trusted institution, the data owner can publish the data description information through the trusted hardware, so that the data owner can conveniently manage the data assets through the trusted hardware.

Description

Technical Field

[0001] The present application relates to the field of Internet technology, and in particular to a data management method, device and equipment based on trusted hardware. Background Art

[0002] With the development and progress of science and technology, we have entered the digital age. Through computer storage, processing and dissemination technologies, our information has been promoted and disseminated at a very fast speed. Digital technology has also become the core technology and common technology of various contemporary media. As a result, data resources owned or controlled by individuals and enterprises have gradually begun to bring more and more benefits to individuals and enterprises. Therefore, data assets are also considered to be one of the most important forms of assets in the digital age.

[0003] Based on this, how to provide a more convenient and reliable method for managing user data has become an issue that needs to be addressed urgently. Summary of the invention

[0004] The embodiments of this specification provide a data management method, device and equipment based on trusted hardware to improve the convenience and reliability of users in managing personal data.

[0005] To solve the above technical problems, the embodiments of this specification are implemented as follows:

[0006] The embodiment of this specification provides a data management method based on trusted hardware, including:

[0007] The trusted hardware obtains data description information to be released; the data description information is used to describe the target data of the data owner that can be provided by the trusted institution; the trusted hardware has a binding relationship with the distributed digital identity of the data owner;

[0008] Requesting the trusted institution to verify whether the trusted institution stores the user service data required to generate the target data;

[0009] Receiving the verification result fed back by the trusted institution;

[0010] If the verification result indicates that the trusted institution stores the user service data required to generate the target data, the data description information is published.

[0011] A data acquisition method provided in an embodiment of this specification includes:

[0012] Acquire data description information published by a data owner; the data description information is used to describe the target data of the data owner that can be provided by a trusted institution;

[0013] Generate an acquisition request for the target data according to the data description information;

[0014] Sending the acquisition request to the trusted hardware of the data owner; the trusted hardware has a binding relationship with the distributed digital identity of the data owner;

[0015] The target data is received.

[0016] The embodiment of this specification provides a data management device based on trusted hardware, including:

[0017] A first acquisition module is used for the trusted hardware to acquire the data description information to be released; the data description information is used to describe the target data of the data owner that can be provided by the trusted institution; the trusted hardware has a binding relationship with the distributed digital identity of the data owner;

[0018] A request verification module, used for requesting the trusted institution to verify whether the trusted institution stores the user service data required to generate the target data;

[0019] A first receiving module, used to receive the verification result fed back by the trusted institution;

[0020] A publishing module is used to publish the data description information if the verification result indicates that the trusted institution stores the user business data required to generate the target data.

[0021] A data acquisition device provided in an embodiment of the present specification includes:

[0022] A first acquisition module is used to acquire data description information published by a data owner; the data description information is used to describe the target data of the data owner that can be provided by a trusted institution;

[0023] An acquisition request generation module, used to generate an acquisition request for the target data according to the data description information;

[0024] A sending module, used for sending the acquisition request to the trusted hardware of the data owner; the trusted hardware has a binding relationship with the distributed digital identity of the data owner;

[0025] A receiving module is used to receive the target data.

[0026] The embodiment of this specification provides a data management device based on trusted hardware, including:

[0027] at least one processor; and,

[0028] a memory communicatively connected to the at least one processor; wherein,

[0029] The memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to:

[0030] Acquire data description information to be published; the data description information is used to describe the target data of the data owner that can be provided by the trusted institution; the distributed digital identity of the data owner has a binding relationship with the trusted hardware;

[0031] Requesting the trusted institution to verify whether the trusted institution stores the user service data required to generate the target data;

[0032] Receiving the verification result fed back by the trusted institution;

[0033] If the verification result indicates that the trusted institution stores the user service data required to generate the target data, the data description information is published.

[0034] A data acquisition device provided in an embodiment of the present specification includes:

[0035] at least one processor; and,

[0036] a memory communicatively connected to the at least one processor; wherein,

[0037] The memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to:

[0038] Acquire data description information published by a data owner; the data description information is used to describe the target data of the data owner that can be provided by a trusted institution;

[0039] Generate an acquisition request for the target data according to the data description information;

[0040] Sending the acquisition request to the trusted hardware of the data owner; the trusted hardware has a binding relationship with the distributed digital identity of the data owner;

[0041] The target data is received.

[0042] At least one embodiment provided in this specification can achieve the following beneficial effects:

[0043] After obtaining the data description information describing the target data of the data owner that can be provided by the trusted institution, the trusted hardware that has a binding relationship with the distributed digital identity of the data owner can request the trusted institution to verify whether the user business data required to generate the target data is stored; if so, the data description information can be considered to be true and valid, so that the data description information can be published through the trusted hardware. This solution not only allows the data owner to conveniently manage personal data assets through trusted hardware, but also prevents the data owner from publishing false data description information, thereby facilitating the data owner to reliably and effectively manage personal data assets. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] In order to more clearly illustrate the embodiments of this specification or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.

[0045] Figure 1 A flowchart of a data management method based on trusted hardware provided in an embodiment of this specification;

[0046] Figure 2 A flowchart of a data acquisition method provided in an embodiment of this specification;

[0047] Figure 3 The embodiments of this specification provide corresponding to Figure 1 A structural diagram of a data management device based on trusted hardware;

[0048] Figure 4 The embodiments of this specification provide corresponding to Figure 2 A structural schematic diagram of a data acquisition device;

[0049] Figure 5 The embodiments of this specification provide corresponding to Figure 1 A structural diagram of a data management device based on trusted hardware;

[0050] Figure 6 The embodiments of this specification provide corresponding to Figure 2 A structural schematic diagram of a data acquisition device. DETAILED DESCRIPTION

[0051] In order to make the purpose, technical solutions and advantages of one or more embodiments of this specification clearer, the technical solutions of one or more embodiments of this specification will be clearly and completely described below in combination with the specific embodiments of this specification and the corresponding drawings. Obviously, the described embodiments are only part of the embodiments of this specification, not all of the embodiments. Based on the embodiments in this description, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of one or more embodiments of this specification.

[0052] The technical solutions provided by the embodiments of this specification are described in detail below in conjunction with the accompanying drawings.

[0053] In the prior art, data assets can refer to data resources that are owned or controlled by individuals or enterprises and can bring future economic benefits to individuals or enterprises, and are recorded in physical or electronic form. For example, photos, documents, drawings, videos, digital copyrights, and other data in the form of files of individuals or enterprises; data assets are a type of asset that exists in the form of data relative to physical assets. Data assets are considered to be one of the most important forms of assets in the digital age. However, there is currently no method to manage the data assets of individuals or enterprises safely, conveniently, and effectively.

[0054] In order to solve the defects in the prior art, this solution provides the following embodiments:

[0055] Figure 1 The following is a flowchart of a data management method based on trusted hardware provided in the embodiments of this specification. From the program perspective, the execution subject of the process can be trusted hardware, or it can also be an application client or application server for managing user data assets that communicates with trusted hardware. Figure 1 As shown, the process may include the following steps:

[0056] Step 102: The trusted hardware obtains data description information to be released; the data description information is used to describe the target data of the data owner that can be provided by the trusted institution; the trusted hardware has a binding relationship with the distributed digital identity of the data owner.

[0057] In the embodiments of this specification, trusted hardware is one of the important foundations of trusted computing. Based on trusted hardware, a trusted execution environment (TEE) can be built on the hardware device to protect the program code and data in the trusted hardware from being disclosed and modified, thereby protecting the privacy and security of the data in the trusted hardware. In practical applications, there are many types of trusted hardware, for example, Intel's SGX, ARM TrustZone and other trusted chips. In the embodiments of this specification, the specific model of the trusted hardware is not specifically limited. The trusted hardware may also include a terminal device or server equipped with a trusted chip.

[0058] In the embodiments of this specification, the blockchain can be understood as a data chain composed of multiple blocks stored sequentially. The block header of each block contains the timestamp of the block, the hash value of the previous block information and the hash value of the block information, thereby realizing mutual verification between blocks and blocks, and forming an unalterable blockchain. Each block can be understood as a data block (a unit for storing data). As a decentralized database, the blockchain is a string of data blocks generated by using cryptographic methods to be interrelated. Each data block contains information about a network transaction, which is used to verify the validity of its information (anti-counterfeiting) and generate the next block. The chain formed by the end-to-end connection of blocks is the blockchain. If the data in the block needs to be modified, the content of all blocks after this block needs to be modified, and the data backed up by all nodes in the blockchain network needs to be modified. Therefore, the blockchain has the characteristics of being difficult to tamper with and delete. After the data has been saved to the blockchain, it is reliable as a method to maintain the integrity of the content.

[0059] In the embodiments of this specification, a distributed digital identity service can be provided through a blockchain platform. Specifically, the data owner can request a distributed identity server (DIS) to create a personal distributed digital identity (DID) and a distributed digital identity document (DID Doc) through an application for managing user data assets. In actual applications, the data owner's DID and DID Doc can be stored in the blockchain platform.

[0060] Among them, DIS is a blockchain-based identity management solution. The DIS server can be connected to the blockchain platform and provide functions such as digital identity creation, verification and management, so as to achieve standardized management and protection of entity data, while ensuring the authenticity and efficiency of information flow, and can solve problems such as cross-institutional identity authentication and data cooperation.

[0061] In the embodiments of the present specification, the data owner may also utilize trusted hardware or an application for managing user data assets that is in communication with the trusted hardware to request the establishment of a binding relationship between the trusted hardware and the data owner's DID, thereby facilitating the data owner to utilize the trusted hardware to manage personal data assets.

[0062] Specifically, before step 102: obtaining the data description information to be published, the following may also be included:

[0063] Obtain the identity information of the data owner.

[0064] Get the hardware identification information of the trusted hardware.

[0065] A distributed digital identity binding request is generated according to the identity identification information and the hardware identification information; the distributed digital identity binding request is used to request to establish a corresponding relationship between the distributed digital identity of the data owner and the trusted hardware.

[0066] Send the distributed digital identity binding request to a distributed identity server.

[0067] The distributed identity server responds to the distributed digital identity binding request and stores the correspondence information between the DID of the data owner and the hardware identification information of the trusted hardware in the DID Doc of the data owner, thereby completing the establishment of the binding relationship between the trusted hardware and the DID of the data owner.

[0068] In actual applications, the distributed identity server can also generate a set of key pairs for the trusted hardware bound to the data owner's DID. The private key in the key pair can be stored in the trusted hardware, and the public key corresponding to the private key can be stored in the data owner's DID Doc.

[0069] The data owner can use the private key stored in the trusted hardware to digitally sign the operation instructions or personal data, and other users can use the public key in the data owner's DID Doc to verify the signature of the data owner's operation instructions or personal data, so as to enable other users to verify the identity of the data owner. This also allows the data owner to effectively control personal data assets and personal identity through trusted hardware.

[0070] In the embodiments of this specification, the data owner's identity information may include information that can determine the identity of the data owner. The data owner may be either a corporate user or an individual user. The personal user's identity information may include ID card number information, contact information, etc. The corporate user's identity information may include the corporate business license number, the corporate unified social credit code, the corporate taxpayer identification number, etc., without specific limitation.

[0071] In actual applications, users can enter identity information in the application interface of the application used to manage user data assets; or users can use image acquisition devices to capture personal ID images; or users can use audio acquisition devices to capture audio containing identity information, etc., so that Figure 1 The executing subject of the method can obtain the identity information of the user. No specific limitation is given to this.

[0072] The hardware identification information of the trusted hardware may refer to the information used to identify the trusted hardware, and the hardware identification information of the trusted hardware is usually required to be unique and unchanged compared with other trusted hardware. In practical applications, the hardware identification information of the trusted hardware can be the unique identification information generated for the trusted hardware by the provider of the trusted hardware, or it can be the unique identification information generated for the trusted hardware by the application used to manage user data assets, and there is no specific limitation on this.

[0073] In practical applications, since the information stored in the trusted hardware cannot be tampered with, the credibility of the data stored in the trusted hardware can be guaranteed. Therefore, the hardware identification information of the trusted hardware can be stored in the trusted hardware. When the data owner needs to use the trusted hardware to manage personal data assets, Figure 1 The execution subject of the method can automatically request to obtain the hardware identification information stored in the trusted hardware, which is convenient and quick, and can ensure the credibility of the hardware identification information of the trusted hardware obtained. Alternatively, the data owner can also enter the hardware identification information of the trusted hardware in the application interface of the application used to manage user data assets, which is not specifically limited.

[0074] Step 104: Request the trusted institution to verify whether the trusted institution stores the user service data required to generate the target data.

[0075] In the embodiments of this specification, the data description information to be released by the data owner may refer to the description information of the data assets that the data owner needs to manage using trusted hardware. Specifically, the data description information can be used to reflect the source, type, content overview, etc. of the target data owned by the data owner, and there is no specific limitation on this. For example, the data asset description information for the target data of the data owner can be expressed as: data source-XX Bank; type-quarterly total flow; content overview-data range-August 1, 2019 to July 31, 2020. The data asset description information can reflect that the data owner has the data of the personal quarterly total wage flow from August 1, 2019 to July 31, 2020 obtained by processing the personal wage flow data at XX Bank.

[0076] In practical applications, in order to prevent users from publishing false data description information, a trusted institution can be used to verify whether the trusted institution stores the user business data required to generate the target data. If so, it means that the data owner does have the data assets indicated by the data description information; if not, it means that the data owner does not have the data assets indicated by the data description information.

[0077] There are many types of trusted institutions, and the types of data that different trusted institutions can provide are usually not completely consistent. For example, trusted institutions can include banks, tax bureaus, authoritative credit reporting agencies, business platforms and other authorized data holders. Among them, banks can provide reliable salary flow data, tax bureaus can provide reliable tax payment records, authoritative credit reporting agencies can provide reliable credit reports, and business platforms can provide reliable merchant transaction flow data, etc., without specific limitations.

[0078] In the embodiment of this specification, since the private key of the data owner is stored in the trusted hardware, and the public key corresponding to the private key is stored in the DID Doc of the data owner, therefore, step 104: the data owner can use the trusted hardware to send a data description information verification request to the trusted institution, and the data description information may include: the identity information of the data owner, the DID identifier of the data owner, and the data description information digitally signed by the private key in the trusted hardware.

[0079] Correspondingly, the trusted institution can determine the identity of the data owner based on the data owner's identification information or DID identifier, and use the public key corresponding to the private key obtained from the data owner's DID Doc to verify the signature of the digitally signed data description information. If the signature verification passes, it can be said that the data description information verification request is indeed sent by the data owner, so the data description information verification request can be responded to. If the signature verification fails, it can be said that the data description information verification request is not sent by the data owner, so the data description information verification request can be refused to respond to prevent criminals from obtaining information about whether others have specified data assets, which is conducive to improving the security and privacy of the data assets of the data owner.

[0080] Step 106: Receive the verification result fed back by the trusted institution.

[0081] Step 108: If the verification result indicates that the trusted institution stores the user service data required to generate the target data, the data description information is published.

[0082] In an embodiment of the present specification, if the verification result indicates that the trusted institution stores the user business data required to generate the target data, it can be determined that the data owner can obtain the target data indicated by the data description information, that is, the data owner has the data assets indicated by the data description information, and therefore, the data description information can be published.

[0083] In the embodiments of this specification, the data description information can be published to the data circulation application so that other registered users at the data circulation application can be informed that the data owner has the data assets indicated by the data description information, thereby facilitating other registered users to trade data assets with the data owner. The data circulation application can provide services such as publishing, transferring, and trading data assets. The data circulation application and the application for managing user data assets mentioned in the embodiments of this specification can be the same application or different applications, and there is no specific limitation on this.

[0084] It should be understood that the order of some steps in the methods described in one or more embodiments of this specification can be interchanged according to actual needs, or some steps can be omitted or deleted.

[0085] Figure 1In the method, after obtaining the data description information used to describe the target data of the data owner that can be provided by the trusted institution, the trusted hardware that has a binding relationship with the distributed digital identity of the data owner can request the trusted institution to verify whether the user business data required to generate the target data is stored; if so, the data description information can be considered to be true and valid, so that the data description information can be published through the trusted hardware. This solution not only allows the data owner to conveniently manage personal data assets through trusted hardware, but also prevents the data owner from publishing false data description information, thereby facilitating the data owner to reliably and effectively manage personal data assets.

[0086] based on Figure 1 The method, the examples of this specification also provide some specific implementation plans of the method, which are described below.

[0087] In the embodiments of this specification, there are multiple ways to obtain the data description information to be published.

[0088] Method 1

[0089] The target data of the data owner can be generated by devices other than trusted hardware. The data owner can use trusted hardware to publish data description information for the target data before storing the target data generated by other devices in the personal trusted hardware. At this time, step 102: trusted hardware obtains the data description information to be published, which may specifically include:

[0090] The trusted hardware identifies the data owner's selection operation for the program identifier of the target security application displayed in the target application interface; the selection operation is used to indicate the use of the target security application to process the user business data of the data owner at the trusted institution to obtain the target data; the target security application is deployed in the trusted application environment of the target server.

[0091] According to the selection operation, data description information to be published for the target data is generated.

[0092] In this implementation, the target application interface may refer to the application interface of an application for managing user data assets. The target application interface may display program identifiers of multiple security application programs supported by the application for managing user data assets, thereby facilitating the data owner to select the security application program that it allows to generate the target data.

[0093] Among them, a secure application (Trusted Application, TAPP) can refer to an application running in a trusted execution environment (Trusted Execution Environment, TEE), which can process data obtained from a trusted data source according to specified computing rules to generate target data. In actual applications, secure applications can be deployed in the trusted application environment of an application server for managing user data assets, or in the trusted application environment of other servers that communicate with the application server for managing user data assets, without specific limitation.

[0094] In actual applications, the data source of the input data of the security application can be pre-set as a trusted organization, and the data processing rules that the security application needs to execute can be pre-set, so that the security application can obtain the user business data of the specified type of the data owner from the trusted organization, and execute the preset data processing rules to generate the target data.

[0095] In the embodiments of this specification, there are no specific restrictions on the data source of the security application, the data processing rules to be executed, and the type of target data generated, and the user can set them according to actual needs. For example, the security application can generate the user's quarterly salary flow total based on the user's monthly salary flow data at Bank A, and the quarterly salary flow total can be the target data generated by the security application. Based on this, after the data owner selects the program identifier of the target security application, he can automatically generate the data description information to be published for the target data according to the setting information of the target security application.

[0096] In the embodiment of this specification, the correspondence information between the target security application and the target data can be stored in the distributed digital identity document DID Doc of the data owner. This facilitates the subsequent determination of the security application used to generate the target data of the data owner based on the DID Doc information of the data owner, which will not be described in detail.

[0097] In the embodiment of the present specification, after the data owner publishes the data description information for the target data to the data circulation application, the data user can request the data owner to obtain the target data based on the information published by the data owner.

[0098] Therefore, after publishing the data description information, it may also include:

[0099] An acquisition request for the target data generated by the data user according to the data description information; the acquisition request may be generated by the data user according to the data description information for the target data published by the data owner obtained from the data circulation application.

[0100] In response to the acquisition request, a generation request for the target data is sent to a target server equipped with the target security application.

[0101] Receive the processing result fed back by the target server.

[0102] In the embodiments of this specification, after the data owner obtains the acquisition request for the target data from the data user, the target security application used to generate the target data can be determined based on the DID Doc information of the data owner. If the data owner allows the data user to obtain the target data, the data owner can send a generation request for the target data to the target server equipped with the target security application through a trusted application, so that the target server runs the target security application to generate the target data.

[0103] The target server can also feedback the processing results to the data owner. If the processing result indicates that the target data has been generated, the data owner and the data user can go to the target server to obtain the target data, allowing the data owner to manage personal data assets through trusted hardware.

[0104] At the same time, since the target security application runs in a trusted execution environment, the target data generated by the target security application has the characteristic of being tamper-proof, and since the target security application is used to process the user business data obtained from the trusted data source, the credibility of the target data generated by the target security application can be guaranteed. In addition, since the target data generated by the security application is obtained by processing the user's original business data, the data user can only obtain the target data, but cannot obtain the user's original data involved in generating the target data, so as to improve the security and privacy of the original business data of the data owner.

[0105] In the embodiment of the present specification, the data owner may also set up an authorization approval process for the use of the target data, so that the data user is allowed to obtain the target data after the approval is passed.

[0106] Specifically, before sending the generation request for the target data to the target server equipped with the target security application, the following may also be included:

[0107] Obtaining a use authorization instruction of a use authorization approver of the target data in response to the acquisition request; wherein the use authorization approver may include a data owner of the target data.

[0108] Generate usage authorization information according to the usage authorization instruction.

[0109] The use authorization information is digitally signed using the private key of the data owner in the trusted hardware, and the authorization information is used after obtaining the digital signature. The public key corresponding to the private key is stored in the document of the distributed digital identity of the data owner.

[0110] The digitally signed authorization information is sent to a target server equipped with the target security application.

[0111] The target server can obtain the public key corresponding to the private key stored in the trusted hardware from the DID Doc of the data owner, and use the public key to verify the digitally signed authorization information. If the verification is successful, it can be determined that the digitally signed authorization information is authorized by the data owner, so the target security application can be run to generate the target data. If the target data use authorization approver does not approve it, or the target server does not pass the signature verification of the signed authorization information, the security application can be prohibited from generating the target data, so that the data user cannot obtain the target data, so as to ensure the security of the data assets of the data owner.

[0112] Method 2

[0113] The target data of the data owner needs to be generated by trusted hardware. After the target data is generated by trusted hardware, the data owner can publish the data description information for the target data. At this time, step 102: the trusted hardware obtains the data description information to be published, which may specifically include:

[0114] Trusted hardware obtains user business data of the data owner from the trusted organization.

[0115] The user business data is processed using a target security application program installed in the trusted hardware to obtain target data.

[0116] According to the target data, data description information to be published for the target data is generated.

[0117] The implementation principle of the target security application mentioned in this implementation method may be the same as that of the target security application mentioned in implementation method one, but in this implementation method, the target security application may be deployed in trusted hardware.

[0118] Specifically, the target security application may be installed in a trusted execution environment in the trusted hardware, and the trusted execution environment is isolated from the operating system of the trusted hardware.

[0119] Correspondingly, the trusted hardware obtains the user business data of the data owner from the trusted organization, which may specifically include: the trusted hardware obtains the user business data of the data owner from the trusted organization through an interface predefined in the code in the trusted execution environment.

[0120] In the embodiments of this specification, the trusted execution environment (TEE) is a trusted execution environment based on the security extension of CPU hardware and completely isolated from the outside. At present, the industry pays great attention to the TEE solution. Almost all mainstream chips and software alliances have their own TEE solutions, such as TPM (Trusted Platform Module) in software and Intel SGX (Software Guard Extensions) in hardware, ARM Trustzone (Trust Zone) and AMD PSP (Platform Security Processor) etc. TEE can play the role of hardware black box. The code and data executed in TEE cannot be peeped even at the operating system layer, and can only be operated through the pre-defined interface in the code. In terms of efficiency, due to the black box nature of TEE, what is calculated in TEE is plain text data, rather than the complex cryptographic operations in homomorphic encryption, and the efficiency of the calculation process is almost lost. Therefore, by obtaining the user business data of the data owner from the trusted organization through the program deployed in the TEE environment and processing the obtained user business data, the data privacy requirements can be met to a large extent under the premise of relatively small performance loss. And because the programs and data within the trusted execution environment are tamper-proof, the credibility of the target data generated by the programs deployed in the TEE can be improved.

[0121] Of course, when the target security application is deployed at the target server, the target security application can also be deployed in a trusted execution environment in the target server. The trusted execution environment is isolated from the operating system of the target server. The target security application can obtain the user business data of the data owner from the trusted organization through the interface pre-defined in the code in the trusted execution environment to process the user business data and obtain the target data, thereby improving the credibility of the target data generated by the program deployed in the TEE.

[0122] When the data user needs to obtain the target data, since the target data has been stored in the trusted hardware, after step 108: publishing the data description information, the following may also be included:

[0123] An acquisition request for the target data generated by the data user according to the data description information; the acquisition request may be generated by the data user according to the data description information for the target data published by the data owner obtained from the data circulation application.

[0124] Obtain the use authorization instruction of the target data use authorization approver for the acquisition request.

[0125] In response to the acquisition request, the target data stored in the trusted hardware is digitally signed using the private key of the data owner stored in the trusted hardware to obtain digitally signed data. The public key corresponding to the private key is stored in the document of the distributed digital identity of the data owner.

[0126] Send the digitally signed data to the data user.

[0127] The data user can obtain the public key corresponding to the private key stored in the trusted hardware from the data owner's DID Doc, and use the public key to verify the digitally signed data. If the verification passes, it can be determined that the digitally signed data is the target data authorized for use by the data owner. If the verification fails, it can be determined that the digitally signed data is not the target data authorized for use by the data owner, that is, the obtained data is untrustworthy.

[0128] In the embodiment of the present specification, before publishing the data description information for the target data, the user may also specify the use authorization approval process for the target data to ensure the security of the data assets of the data owner.

[0129] Therefore, step 108: before publishing the data description information, the following may also be included:

[0130] Obtain the use authorization approval process information set by the data owner for the target data.

[0131] A correspondence between the use authorization approval process information and the data description information is established.

[0132] Based on the same idea, Figure 2 A flowchart of a data acquisition method provided in an embodiment of this specification. From a program perspective, the execution subject of the process can be the device of the data user, or an application for managing user data assets installed on the device of the data user.

[0133] like Figure 2 As shown, the process may include the following steps:

[0134] Step 202: Acquire data description information published by the data owner; the data description information is used to describe the target data of the data owner that can be provided by a trusted institution.

[0135] In the embodiment of the present specification, since the data owner can publish the data description information to the data circulation application, the data user can obtain the data description information published by the data owner from the data circulation application in step 202. The data circulation application and the application for managing user data assets can be the same application or different applications, which is not specifically limited.

[0136] Step 204: Generate an acquisition request for the target data according to the data description information.

[0137] Step 206: Send the acquisition request to the trusted hardware of the data owner; the trusted hardware has a binding relationship with the distributed digital identity of the data owner.

[0138] Step 208: Receive the target data.

[0139] It should be understood that the order of some steps in the methods described in one or more embodiments of this specification can be interchanged according to actual needs, or some steps can be omitted or deleted.

[0140] Figure 2 According to the method in the embodiment, the data user can request the data owner's trusted hardware to obtain the target data based on the data description information for the target data published by the data owner using the trusted hardware, and receive the target data. This allows the data user to easily obtain the data assets of the data owner, which is conducive to improving the convenience of data asset management and transmission.

[0141] based on Figure 2 The method, the examples of this specification also provide some specific implementation plans of the method, which are described below.

[0142] In the embodiment of this specification, step 208: receiving the target data may specifically include:

[0143] The target data fed back by the target server is received; the target data is obtained by processing the user business data of the data owner stored in the trusted institution using the target security application installed in the target server.

[0144] Alternatively, the target data fed back by the trusted hardware is received; the target data is obtained by processing the user business data of the data owner stored in a trusted institution using a target security application installed in the trusted hardware.

[0145] In the embodiment of this specification, if the target security application is installed in the target server, the target security application is installed in the trusted execution environment of the target server, and the trusted execution environment is isolated from the operating system of the target server. And because the programs and data in the trusted execution environment are tamper-proof, the credibility of the target data generated by the program deployed in the TEE can be improved.

[0146] If the target security application is installed in the trusted hardware, the target security application is installed in the trusted execution environment of the trusted hardware, and the trusted execution environment is isolated from the operating system of the trusted hardware. And because the programs and data in the trusted execution environment are tamper-proof, the credibility of the target data generated by the program deployed in the TEE can be improved.

[0147] Since the private key of the data owner may be stored in the trusted hardware of the data owner, the public key corresponding to the private key is stored in the document of the distributed digital identity of the data owner.

[0148] Therefore, step 208: receiving the target data may specifically include:

[0149] The target data digitally signed by the private key is received.

[0150] After receiving the target data digitally signed by the private key, the method may further include:

[0151] The public key in the document of the distributed digital identity of the data owner is obtained.

[0152] The public key is used to perform signature verification on the digitally signed target data.

[0153] Based on the same idea, the embodiments of this specification also provide a device corresponding to the above method. Figure 3 The embodiments of this specification provide corresponding to Figure 1 A structural diagram of a data management device based on trusted hardware. Figure 3 As shown, the device may include:

[0154] The first acquisition module 302 is used for the trusted hardware to acquire the data description information to be released; the data description information is used to describe the target data of the data owner that can be provided by the trusted organization; the trusted hardware has a binding relationship with the distributed digital identity of the data owner.

[0155] The request verification module 304 is used to request the trusted institution to verify whether the trusted institution stores the user service data required to generate the target data.

[0156] The first receiving module 306 is configured to receive the verification result fed back by the trusted institution.

[0157] The publishing module 308 is configured to publish the data description information if the verification result indicates that the trusted institution stores the user service data required to generate the target data.

[0158] Optional, Figure 3 The device may also include:

[0159] The identity information acquisition module is used to obtain the identity information of the data owner.

[0160] The hardware identification information acquisition module is used to obtain the hardware identification information of the trusted hardware.

[0161] The binding request module is used to generate a distributed digital identity binding request based on the identity identification information and the hardware identification information; the distributed digital identity binding request is used to request to establish a corresponding relationship between the distributed digital identity of the data owner and the trusted hardware.

[0162] The binding request sending module is used to send the distributed digital identity binding request to the distributed identity server.

[0163] Optionally, the first acquisition module 302 may be specifically used to:

[0164] The trusted hardware identifies the data owner's selection operation for the program identifier of the target security application displayed in the target application interface; the selection operation is used to indicate the use of the target security application to process the user business data of the data owner at the trusted institution to obtain the target data; the target security application is deployed in the trusted application environment of the target server.

[0165] According to the selection operation, data description information to be published for the target data is generated.

[0166] Optional, Figure 3 The device may further include:

[0167] The corresponding relationship information storage module is used to store the corresponding relationship information between the target security application and the target data in the document of the distributed digital identity of the data owner.

[0168] Optional, Figure 3 The device may further include:

[0169] The second acquisition module is used to acquire an acquisition request for the target data generated by the data user according to the data description information.

[0170] The sending module is used to send a generation request for the target data to a target server equipped with the target security application in response to the acquisition request.

[0171] The second receiving module is used to receive the processing result fed back by the target server.

[0172] Optionally, the private key of the data owner is stored in the trusted hardware; the public key corresponding to the private key is stored in a document of the distributed digital identity of the data owner; Figure 3 The device may further include:

[0173] The third acquisition module is used to obtain the use authorization instruction of the target data use authorization approver in response to the acquisition request.

[0174] The use authorization information generation module is used to generate the use authorization information according to the use authorization instruction.

[0175] The first digital signature module is used to digitally sign the use authorization information using the private key, and use the authorization information after obtaining the digital signature.

[0176] The sending module can be specifically used for:

[0177] The digitally signed authorization information is sent to a target server equipped with the target security application.

[0178] Optionally, the first acquisition module 302 may be specifically used to:

[0179] Trusted hardware obtains user business data of the data owner from the trusted organization.

[0180] The user business data is processed using a target security application program installed in the trusted hardware to obtain target data.

[0181] Generate data description information to be published for the target data.

[0182] Optionally, the target security application is installed in a trusted execution environment in the trusted hardware, and the trusted execution environment is isolated from the operating system of the trusted hardware.

[0183] Correspondingly, the trusted hardware obtains the user business data of the data owner from the trusted institution, specifically including:

[0184] The trusted hardware obtains the user business data of the data owner from the trusted institution through an interface predefined in the code in the trusted execution environment.

[0185] Optionally, the private key of the data owner is stored in the trusted hardware; the public key corresponding to the private key is stored in a document of the distributed digital identity of the data owner; Figure 3 The device may further include:

[0186] The fourth acquisition module is used to obtain an acquisition request for the target data generated by the data user according to the data description information.

[0187] The second digital signature module is used to respond to the acquisition request and use the private key to digitally sign the target data stored in the trusted hardware to obtain digitally signed data.

[0188] The use authorization instruction acquisition module is used to obtain the use authorization instruction of the use authorization approver of the target data in response to the acquisition request.

[0189] The target data sending module is used to send the digitally signed data to the data user if the use authorization instruction is obtained.

[0190] Optional, Figure 3 The device may further include:

[0191] An approval process information acquisition module is used to acquire the use authorization approval process information set by the data owner for the target data;

[0192] The corresponding relationship establishing module is used to establish the corresponding relationship between the use authorization approval process information and the data description information.

[0193] Optionally, the publishing module 308 may be specifically used to: publish the data description information to a data circulation application.

[0194] The second acquisition module or the fourth acquisition module may be specifically used to obtain an acquisition request from a data user for the target data, wherein the acquisition request is generated based on the data description information obtained from the data circulation application.

[0195] Based on the same idea, the embodiments of this specification also provide a device corresponding to the above method. Figure 4 The embodiments of this specification provide corresponding to Figure 2 A structural diagram of a data acquisition device. Figure 4 As shown, the device may include:

[0196] The first acquisition module 402 is used to acquire data description information published by the data owner; the data description information is used to describe the target data of the data owner that can be provided by the trusted institution;

[0197] An acquisition request generating module 404, configured to generate an acquisition request for the target data according to the data description information;

[0198] The sending module 406 is used to send the acquisition request to the trusted hardware of the data owner; the trusted hardware has a binding relationship with the distributed digital identity of the data owner;

[0199] The receiving module 408 is configured to receive the target data.

[0200] Optional, Figure 4 In the device, the receiving module 408 can be specifically used for:

[0201] The target data fed back by the target server is received; the target data is obtained by processing the user business data of the data owner stored in the trusted institution using the target security application installed in the target server.

[0202] Alternatively, the target data fed back by the trusted hardware is received; the target data is obtained by processing the user business data of the data owner stored in a trusted institution using a target security application installed in the trusted hardware.

[0203] Optionally, if the target security application is installed in the target server, the target security application is installed in a trusted execution environment at the target server, and the trusted execution environment is isolated from the operating system of the target server.

[0204] If the target security application is installed in the trusted hardware, then the target security application is installed in a trusted execution environment of the trusted hardware, and the trusted execution environment is isolated from the operating system of the trusted hardware.

[0205] Optionally, the trusted hardware stores the private key of the data owner; the public key corresponding to the private key is stored in the document of the distributed digital identity of the data owner; the receiving module 408 can be specifically used to: receive the target data digitally signed with the private key.

[0206] Optional, Figure 4 The device may further include:

[0207] The second acquisition module is used to acquire the public key in the document of the distributed digital identity of the data owner.

[0208] The signature verification module is used to use the public key to perform signature verification on the target data after the digital signature.

[0209] Based on the same idea, the embodiments of this specification also provide a device corresponding to the above method.

[0210] Figure 5 The embodiments of this specification provide corresponding to Figure 1 A structural diagram of a data management device based on trusted hardware. Figure 5 As shown, the device 500 may include:

[0211] at least one processor 510; and,

[0212] A memory 530 in communication with the at least one processor; wherein,

[0213] The memory 530 stores instructions 520 executable by the at least one processor 510. The instructions are executed by the at least one processor 510 to enable the at least one processor 510 to:

[0214] Acquire data description information to be released; the data description information is used to describe the target data of the data owner that can be provided by the trusted institution; the distributed digital identity of the data owner has a binding relationship with the trusted hardware.

[0215] The trusted institution is requested to verify whether the trusted institution stores the user service data required to generate the target data.

[0216] Receive the verification result fed back by the trusted institution.

[0217] If the verification result indicates that the trusted institution stores the user service data required to generate the target data, the data description information is published.

[0218] Based on the same idea, the embodiments of this specification also provide a device corresponding to the above method.

[0219] Figure 6 The embodiments of this specification provide corresponding to Figure 2 A structural diagram of a data acquisition device. Figure 6 As shown, the device 600 may include:

[0220] at least one processor 610; and,

[0221] A memory 630 is communicatively connected to the at least one processor; wherein,

[0222] The memory 630 stores instructions 620 executable by the at least one processor 610. The instructions are executed by the at least one processor 610 to enable the at least one processor 610 to:

[0223] Acquire data description information published by a data owner; the data description information is used to describe the target data of the data owner that can be provided by a trusted institution.

[0224] A request for obtaining the target data is generated according to the data description information.

[0225] The acquisition request is sent to the trusted hardware of the data owner; the trusted hardware has a binding relationship with the distributed digital identity of the data owner.

[0226] The target data is received.

[0227] Each embodiment in this specification is described in a progressive manner. The same or similar parts between the embodiments can be referred to each other. Each embodiment focuses on the differences from other embodiments. Figure 5 and Figure 6 As for the device shown, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0228] In the 1990s, improvements to a technology could be clearly distinguished as hardware improvements (for example, improvements to the circuit structure of diodes, transistors, switches, etc.) or software improvements (improvements to the method flow). However, with the development of technology, many improvements to the method flow today can be regarded as direct improvements to the hardware circuit structure. Designers almost always obtain the corresponding hardware circuit structure by programming the improved method flow into the hardware circuit. Therefore, it cannot be said that an improvement in a method flow cannot be implemented using a hardware entity module. For example, a programmable logic device (PLD) (such as a field programmable gate array (FPGA)) is such an integrated circuit whose logical function is determined by the user's programming of the device. Designers can "integrate" a digital system on a PLD by programming it themselves, without having to ask a chip manufacturer to design and produce a dedicated integrated circuit chip. Moreover, nowadays, instead of manually making integrated circuit chips, this kind of programming is mostly implemented by "logic compiler" software, which is similar to the software compiler used when developing and writing programs, and the original code before compilation must also be written in a specific programming language, which is called hardware description language (HDL). There is not only one HDL, but many kinds, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, RHDL (Ruby Hardware Description Language), etc. The most commonly used ones are VHDL (Very-High-Speed ​​Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should also know that it is only necessary to program the method flow slightly in the above-mentioned hardware description languages ​​and program it into the integrated circuit, and then it is easy to obtain the hardware circuit that implements the logic method flow.

[0229] The controller can be implemented in any appropriate manner, for example, the controller can take the form of a microprocessor or processor and a computer-readable medium storing a computer-readable program code (such as software or firmware) that can be executed by the (micro)processor, a logic gate, a switch, an application-specific integrated circuit (ASIC), a programmable logic controller, and an embedded microcontroller. Examples of controllers include, but are not limited to, the following microcontrollers: ARC625D, AtmelAT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320. The memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art also know that in addition to implementing the controller in a purely computer-readable program code manner, the controller can be implemented in the form of a logic gate, a switch, an application-specific integrated circuit, a programmable logic controller, and an embedded microcontroller by logically programming the method steps. Therefore, this controller can be considered as a hardware component, and the devices included therein for implementing various functions can also be regarded as structures within the hardware component. Or even, the devices for implementing various functions can be regarded as both software modules for implementing the method and structures within the hardware component.

[0230] The systems, devices, modules or units described in the above embodiments may be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, the computer may be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

[0231] For the convenience of description, the above device is described in various units according to their functions. Of course, when implementing the present application, the functions of each unit can be implemented in the same or multiple software and / or hardware.

[0232] Those skilled in the art will appreciate that embodiments of the present invention may be provided as methods, systems, or computer program products. Therefore, the present invention may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0233] The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0234] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0235] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0236] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0237] The memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0238] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0239] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0240] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that contain computer-usable program code.

[0241] The present application may be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. The present application may also be practiced in distributed computing environments where tasks are performed by remote processing devices connected through a communication network. In a distributed computing environment, program modules may be located in local and remote computer storage media, including storage devices.

[0242] The above is only an embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.

Claims

1. A data management method based on trusted hardware, comprising: The trusted hardware obtains the data description information to be released; The data description information is used to describe the target data of the data owner; The trusted hardware has a binding relationship with the distributed digital identity of the data owner; Requesting a trusted institution to verify whether the trusted institution stores the user service data required to generate the target data; If the trusted institution stores the user business data required to generate the target data, the data description information is published through the trusted hardware, and the data description information is used for other users to know that the data owner has the data assets indicated by the data description information.

2. According to the method of claim 1, the verifying whether the trusted institution stores the user service data required to generate the target data specifically comprises: Requesting a trusted institution to verify whether the trusted institution stores the user service data required to generate the target data; Receive the verification result fed back by the trusted institution.

3. The method according to claim 1, before obtaining the data description information to be published, further comprising: Obtaining the identity information of the data owner; Obtain hardware identification information of trusted hardware; Generate a distributed digital identity binding request according to the identity identification information and the hardware identification information; the distributed digital identity binding request is used to request to establish a corresponding relationship between the distributed digital identity of the data owner and the trusted hardware; Send the distributed digital identity binding request to a distributed identity server.

4. According to the method of claim 1, the trusted hardware obtains the data description information to be released, specifically comprising: The trusted hardware identification data owner performs a selection operation on the program identifier of the target security application displayed in the target application interface; The selection operation is used to instruct to use the target security application to process the user business data of the data owner at the trusted institution to obtain the target data; The target security application is deployed in a trusted application environment of the target server; According to the selection operation, data description information to be published for the target data is generated.

5. The method according to claim 4, after publishing the data description information, further comprising: The correspondence information between the target security application and the target data is stored in the document of the distributed digital identity of the data owner.

6. The method according to claim 4, after publishing the data description information, further comprising: Obtaining a request for obtaining the target data generated by the data user according to the data description information; In response to the acquisition request, sending a generation request for the target data to a target server equipped with the target security application; Receive the processing result fed back by the target server.

7. According to the method of claim 6, the private key of the data owner is stored in the trusted hardware; the public key corresponding to the private key is stored in the document of the distributed digital identity of the data owner; Before sending the generation request for the target data to the target server equipped with the target security application, the method further includes: Obtaining the use authorization instruction of the target data use authorization approver for the acquisition request; Generate use authorization information according to the use authorization instruction; The authorization information is digitally signed using the private key, and the authorization information is used after obtaining the digital signature; The sending of the generation request for the target data to a target server equipped with the target security application specifically includes: The digitally signed authorization information is sent to a target server equipped with the target security application.

8. According to the method of claim 1, the trusted hardware obtains the data description information to be released, specifically comprising: Trusted hardware obtains user business data from the data owner from the trusted organization; Processing the user service data using a target security application program installed in the trusted hardware to obtain target data; Generate data description information to be published for the target data.

9. The method according to claim 8, wherein the private key of the data owner is stored in the trusted hardware; the public key corresponding to the private key is stored in the document of the distributed digital identity of the data owner; After publishing the data description information, the method further includes: Obtaining a request for obtaining the target data generated by the data user according to the data description information; In response to the acquisition request, digitally sign the target data stored in the trusted hardware using the private key to obtain digitally signed data; Send the digitally signed data to the data user.

10. The method according to claim 9, before sending the digitally signed data to the data user, further comprising: Obtaining a use authorization instruction of the target data use authorization approver for the acquisition request.

11. The method according to claim 7 or 10, before publishing the data description information, further comprising: Obtaining the use authorization approval process information set by the data owner for the target data; A correspondence between the use authorization approval process information and the data description information is established.

12. The method according to claim 6 or 9, wherein publishing the data description information specifically comprises: Publishing the data description information to the data circulation application; The acquisition request for the target data generated by the data user according to the data description information specifically includes: A request for obtaining the target data from a data user is obtained, wherein the request is generated based on the data description information obtained from the data circulation application.

13. The method according to claim 8, wherein the target security application is installed in a trusted execution environment in the trusted hardware, and the trusted execution environment is isolated from an operating system of the trusted hardware.

14. The method according to claim 13, wherein the trusted hardware obtains the user service data of the data owner from the trusted institution, specifically comprising: The trusted hardware obtains the user business data of the data owner from the trusted institution through an interface predefined in the code in the trusted execution environment.

15. A data acquisition method, comprising: Acquire data description information published by a data owner through trusted hardware to learn that the data owner has data assets indicated by the data description information; The data description information is used to describe the target data of the data owner; the data description information is issued by the trusted hardware after requesting the trusted institution to verify that the trusted institution stores the user service data required to generate the target data; Generate an acquisition request for the target data according to the data description information; Sending the acquisition request to the trusted hardware of the data owner; the trusted hardware has a binding relationship with the distributed digital identity of the data owner; The target data is received.

16. The method according to claim 15, wherein receiving the target data comprises: Receiving the target data fed back by the target server; The target data is obtained by processing the user business data of the data owner stored in the trusted institution using the target security application installed in the target server; Alternatively, receiving the target data fed back by the trusted hardware; The target data is obtained by processing the user business data of the data owner stored in a trusted institution using a target security application installed in the trusted hardware.

17. The method according to claim 16, if the target security application is installed in the target server, the target security application is installed in a trusted execution environment at the target server, and the trusted execution environment is isolated from the operating system of the target server; If the target security application is installed in the trusted hardware, then the target security application is installed in a trusted execution environment of the trusted hardware, and the trusted execution environment is isolated from the operating system of the trusted hardware.

18. The method according to claim 15, wherein the private key of the data owner is stored in the trusted hardware; the public key corresponding to the private key is stored in the document of the distributed digital identity of the data owner; The receiving the target data specifically includes: Receiving the target data digitally signed by the private key; After receiving the target data digitally signed by the private key, the method further includes: Obtaining the public key in the document of the distributed digital identity of the data owner; The public key is used to perform signature verification on the digitally signed target data.

19. A data management device based on trusted hardware, comprising: A first acquisition module, used for trusted hardware to acquire data description information to be published; The data description information is used to describe the target data of the data owner; The trusted hardware has a binding relationship with the distributed digital identity of the data owner; A request verification module, used for requesting a trusted institution to verify whether the trusted institution stores the user service data required to generate the target data; A publishing module is used to publish the data description information through the trusted hardware if the trusted institution stores the user business data required to generate the target data. The data description information is used for other users to know that the data owner has the data assets indicated by the data description information.

20. The device according to claim 19, wherein the first acquisition module is specifically configured to: The trusted hardware identifies the selection operation of the data owner for the program identifier of the target security application displayed in the target application interface; the selection operation is used to indicate that the user business data of the data owner at the trusted institution is processed using the target security application to obtain the target data; The target security application is deployed in a trusted application environment of the target server; According to the selection operation, data description information to be published for the target data is generated.

21. The apparatus according to claim 20, further comprising: A second acquisition module, used to acquire an acquisition request for the target data generated by a data user according to the data description information; A sending module, configured to send, in response to the acquisition request, a generation request for the target data to a target server equipped with the target security application; The second receiving module is used to receive the processing result fed back by the target server.

22. The device according to claim 19, wherein the first acquisition module is specifically configured to: Trusted hardware obtains user business data from the data owner from the trusted organization; Processing the user service data using a target security application program installed in the trusted hardware to obtain target data; Generate data description information to be published for the target data.

23. A data acquisition device, comprising: A first acquisition module is used to acquire data description information published by a data owner through trusted hardware to learn that the data owner has data assets indicated by the data description information; the data description information is used to describe the target data of the data owner; the data description information is published by the trusted hardware after requesting a trusted institution to verify that the trusted institution stores user service data required to generate the target data; An acquisition request generation module, used to generate an acquisition request for the target data according to the data description information; A sending module, used for sending the acquisition request to the trusted hardware of the data owner; the trusted hardware has a binding relationship with the distributed digital identity of the data owner; A receiving module is used to receive the target data.

24. A data management device based on trusted hardware, comprising: at least one processor; as well as, a memory communicatively connected to the at least one processor; wherein, The memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to: Acquire data description information to be published; the data description information is used to describe the target data of the data owner; the distributed digital identity of the data owner is bound to the trusted hardware; Requesting a trusted institution to verify whether the trusted institution stores the user service data required to generate the target data; If the trusted institution stores the user business data required to generate the target data, the data description information is published through the trusted hardware, and the data description information is used by other users to know that the data owner has the data assets indicated by the data description information.

25. A data acquisition device, comprising: at least one processor; as well as, a memory communicatively connected to the at least one processor; wherein, The memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to: Acquire data description information published by a data owner through trusted hardware to learn that the data owner has data assets indicated by the data description information; the data description information is used to describe the target data of the data owner; the data description information is published by the trusted hardware after the trusted institution requests verification that the trusted institution stores user service data required to generate the target data; Generate an acquisition request for the target data according to the data description information; Sending the acquisition request to the trusted hardware of the data owner; the trusted hardware has a binding relationship with the distributed digital identity of the data owner; The target data is received.

Images