Distributed data authorization method and system based on wearable device

Abstract

The embodiment of the invention provides a distributed data authorization method and system based on wearable equipment, and relates to the technical field of intelligent wearable equipment. According to the method, original data can be obtained through the wearable device, forced end-to-end encryption and desensitization are executed on the original data, and authorizable data are generated. And uploading the authorizable data to the decentralized storage network so as to cast an ownership certificate of the authorizable data through the decentralized storage network. When the data authorization is performed, a data authorization credential for the authorizable data may be casted based on the ownership credential, thereby transferring the data authorization credential in accordance with the authorization request. Through forced encryption and desensitization, privacy calculation is carried out on the premise that original data is not leaked, privacy security is guaranteed to the maximum extent, and it is ensured that a user has ownership to the data through an ownership certificate. Moreover, by casting a data authorization certificate, key authorization and on-chain recording of authorization are realized, and transparency and traceability of data authorization can be improved.

Description

Technical Field

[0001] This application relates to the field of smart wearable device technology, and in particular to a distributed data authorization method and system based on wearable devices. Background Technology

[0002] Data licensing refers to the process of authorizing the use of personal data, whether for a fee or free. Personal data can include physiological indicators collected through smart wearable devices. Taking health and behavioral data as an example, wearable devices such as smartwatches and fitness trackers can continuously and in real-time capture high-value physiological indicators such as heart rate, steps, sleep patterns, and blood oxygen saturation.

[0003] Wearable devices collect rich, timely, and relatable personal data that reflects an individual's real-life habits, making it highly valuable and analytically promising for industries such as insurance, healthcare, and health management. Therefore, data licensing allows users to authorize data analytics firms to access their personal data for specific purposes. Since this personal data originates from wearable devices monitoring individual behavior and may contain sensitive information, users must anonymize their data before authorizing it to remove sensitive content and minimize the risk of privacy breaches.

[0004] However, when anonymizing personal data to remove private content, it can easily reduce the connection or ownership between the anonymized data and the user, thus affecting the user's ownership and control over their personal data. Therefore, while reducing the risk of privacy breaches when authorizing personal data, ensuring that users' ownership and control over their personal data are not compromised is a pressing issue that needs to be addressed. Summary of the Invention

[0005] In view of this, embodiments of this application provide a distributed data authorization method and system based on wearable devices, which can provide a new data authorization scheme, reduce the risk of privacy leakage when authorizing personal data, and at the same time ensure that the user's ownership and control over personal data are not compromised.

[0006] According to a first aspect of this application, a distributed data authorization method based on a wearable device is provided, applied to a user terminal device, the method comprising: Obtain raw data, which includes raw health data and raw behavioral data collected by wearable devices; Authorizable data is generated based on the original data, and the authorizable data is data obtained by performing mandatory end-to-end encryption and first-layer mandatory desensitization on the original data. The authorizable data is uploaded to a decentralized storage network to obtain ownership certificates for the authorizable data; the ownership certificate is a permanent on-chain proof that represents the root ownership and authorization capability of the original data. In response to an authorization request for the authorizable data, a data authorization credential is obtained, which is used to represent the permission to use the authorizable data; Transfer the data authorization certificate according to the authorization request.

[0007] In some embodiments, generating authoritative data based on the original data includes: Obtain desensitization strategies; Set the encryption and desensitization order according to the desensitization strategy; According to the encryption and desensitization sequence, a unique decryption key is generated by performing forced end-to-end encryption on the original data, and the authorized data is generated by performing a first-level forced desensitization on the original data.

[0008] In some embodiments, generating authoritative data based on the original data includes: Identify information to be processed from the raw data. The information to be processed includes at least one of the following: user's real identity information, precise parameters, and authorization sensitive fields. The precise parameters include precise timestamps and precise numerical values. The authorization sensitive fields include personal identification information unrelated to authorization. The information to be processed is obfuscated to obtain authoritative data; Wherein, when the information to be processed includes the user's real identity information, the obfuscation process includes replacing the user's real identity information in the original data with a pseudo-anonymized data identifier; When the information to be processed includes the precise parameters, the fuzzification process includes fuzzification and intervalization of the precise parameters; When the information to be processed includes the authorization sensitive field, the obfuscation process includes deleting the authorization sensitive field from the original data.

[0009] In some embodiments, uploading the authorizable data to a decentralized storage network to obtain ownership certificates for the authorizable data includes: Obtain the authorizable data of a preset type within a preset time period; The authorizable data is sent to any working node in the decentralized storage network so that the working node can perform a hash operation on the authorizable data to generate the unique hash information. The system receives the unique hash information, runs a smart contract through the worker node, and uses the smart contract to forge the permanent on-chain proof based on the authorizable data; the permanent on-chain proof includes data time range, data type, and anonymization level information.

[0010] In some embodiments, the data authorization credential includes a general authorization credential and a higher-level authorization credential, wherein the general authorization credential includes unique hash information; in response to an authorization request for the authorizable data, obtaining the data authorization credential includes: Receive the authorization request, which is a request entered by the user holding the ownership certificate through the platform authorization interface; Read the ownership certificate from the authorization request; Based on the ownership certificate, locate the authorizable data in the decentralized storage network; The general authorization credential is cast based on the authorizable data, and the general authorization credential is used to perform conditional decryption authorization and / or analysis authorization on behalf of the authorizable data.

[0011] In some embodiments, in response to an authorization request for the authorizable data, obtaining a data authorization credential includes: The authorization platform information is read from the authorization request. The platform authorization information is used to characterize the authorization platform explicitly authorized by the user holding the ownership certificate through a smart contract, and to allow the authorization platform to perform data processing on the authorizable data. According to the authorization platform information, the authorized data is subjected to a second layer of forced desensitization through the work nodes associated with the authorization platform to generate a layer of product data; Through the working node, a first high-level authorization credential is forged based on the first-level product data. The first high-level authorization credential is used to represent access rights to the first-level product data.

[0012] In some embodiments, the method further includes: Obtain multiple product data from the first layer; Through the work node, second-level analysis is performed on multiple first-level product data according to the authorized platform information to obtain second-level product data. The second-level analysis data includes at least one of insight reports, behavioral patterns, and model parameters. The working node forges a second high-level authorization credential based on the second-level product data. The second high-level authorization credential represents the right to access the second-level product data.

[0013] According to a second aspect of this application, a distributed data authorization method based on wearable devices is provided, applied to a decentralized storage network, the method comprising: Receive authenticable data, which is data obtained by performing mandatory end-to-end encryption and first-layer mandatory desensitization on the raw data collected by the wearable device; Distributed storage is performed on the authorizable data to generate unique hash information; The unique hash information is sent to the user device, and a smart contract is used to mint an ownership certificate based on the authorizable data; the ownership certificate is a permanent on-chain proof that represents the root ownership and authorization capability of the original data. In response to an authorization request for the authorizable data, a data authorization certificate for the authorizable data is forged based on the ownership certificate; the data authorization certificate is used to represent the right to use the authorizable data; Transfer the data authorization certificate according to the authorization request.

[0014] In some embodiments, the method further includes: Obtain the requester's requirements information, which includes data analysis requirements and data acquisition requirements; The requester's demand information is parsed into executable analysis logic; According to the executable analysis logic, an authorization notification is sent to the user terminal device so that the user terminal device authorizes the data authorization certificate through the ownership certificate and submits the data authorization certificate to the smart contract; Based on the data authorization credential, the authorized data is subjected to data analysis specified by the requester's requirements in a privacy computing environment to generate analysis result data and analysis proof; The smart contract verifies the analytical proof, and based on the verification result of the analytical proof, the data used to update the authorizable data.

[0015] According to a third aspect of this application, a distributed data authorization system based on wearable devices is provided, the system comprising: a decentralized storage network and multiple user terminal devices; the multiple user terminal devices establishing a communication connection through the decentralized storage network; and at least one wearable device among the multiple user terminal devices. The user terminal device is configured to: acquire raw data, including raw health data and raw behavioral data collected by the wearable device; generate authoritable data based on the raw data, wherein the authoritable data is data obtained by performing mandatory end-to-end encryption and first-layer mandatory desensitization on the raw data; and upload the authoritable data to a decentralized storage network. The decentralized storage network includes multiple worker nodes, which are configured to: perform distributed storage on the authorizable data to generate unique hash information; send the unique hash information to the user terminal device; and use a smart contract to forge ownership certificates based on the authorizable data; the ownership certificate is a permanent on-chain proof representing root ownership and authorization capability over the original data. The working node is further configured to: in response to an authorization request for the authorizable data, forge a data authorization certificate for the authorizable data based on the ownership certificate, and transfer the data authorization certificate according to the authorization request; the data authorization certificate is used to represent the usage rights of the authorizable data.

[0016] According to a fourth aspect of this application, a computer device is provided, including a storage medium, a processor, and a computer program stored on the storage medium and executable on the processor, wherein the processor executes the program to implement the above-described distributed data authorization method based on a wearable device.

[0017] According to a fifth aspect of this application, a storage medium is provided having a computer program stored thereon, which, when executed by a processor, implements the above-described distributed data authorization method based on a wearable device.

[0018] By employing the above technical solutions, embodiments of this application provide a distributed data authorization method and system based on wearable devices. The method acquires raw data through a wearable device, performs mandatory end-to-end encryption and desensitization on the raw data, and generates authoritable data. The authoritable data is then uploaded to a decentralized storage network to forge ownership certificates for the authoritative data. During data authorization, a data authorization certificate for the authoritative data can be forged based on the ownership certificate, thereby transferring the data authorization certificate according to the authorization request. This method, through mandatory desensitization, enables privacy computation without disclosing the raw data, maximizing privacy and security, and also ensures user ownership of the data through the ownership certificate. Furthermore, by forging data authorization certificates, key authorizations and on-chain recording of authorizations are achieved, improving the transparency and traceability of data authorization.

[0019] The above description is only an overview of the technical solution of this application. In order to better understand the technical means of this application and to implement it in accordance with the contents of the specification, and to make the above and other objects, features and advantages of this application more obvious and understandable, specific embodiments of this application are given below. Attached Figure Description

[0020] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings: Figure 1 This is a schematic diagram of a distributed system architecture provided in an embodiment of this application; Figure 2 This is a schematic diagram of a distributed data authorization method based on wearable devices provided in an embodiment of this application; Figure 3 A flowchart illustrating the process of obtaining data authorization credentials provided in this application embodiment; Figure 4 A schematic diagram illustrating the process of data authorization based on universal authorization credentials provided in this application embodiment; Figure 5 A schematic diagram illustrating the process of performing data authorization based on high-level authorization credentials, provided for embodiments of this application; Figure 6 This is a schematic diagram of a decentralized storage network data authorization process provided in an embodiment of this application; Figure 7 This is a schematic diagram of the architecture of a distributed data authorization system based on wearable devices provided in an embodiment of this application. Detailed Implementation

[0021] The present application will be described in detail below with reference to the accompanying drawings and embodiments. It should be noted that, unless otherwise specified, the embodiments and features described in the embodiments of the present application can be combined with each other.

[0022] In this application embodiment, wearable device is short for smart wearable device, also known as wearable device or smart wearable device, which is a portable device that can be worn directly on the user's body or integrated into the user's clothing or accessories. For example, wearable devices include, but are not limited to, smartwatches, smart bracelets, smart rings, smart glasses, smart head-mounted devices, etc.

[0023] Wearable devices can possess data monitoring, data processing, and communication capabilities. To this end, wearable devices can integrate sensors, controllers, and communicators internally. Sensors are used to collect users' health and behavioral data. Depending on the type and function of the wearable device, multiple sensors of various types can be integrated within it, forming a sensor suite. For example, a sensor suite may include accelerometers, gyroscopes, barometers, altimeters, heart rate sensors, temperature sensors, and electroactivity sensors.

[0024] The controller is used to process data collected by various sensors, control the watch's operating status, and execute user commands. For example, the controller of a wearable device can be a microcontroller unit (MCU). The data processed by the controller can include internal data from the wearable device as well as data transmitted and received by the wearable device through a communication connection.

[0025] The communicator is used to enable data communication between wearable devices and between wearable devices and other devices. Wearable device communicators can include various types of communication modules depending on the supported communication methods, such as Bluetooth modules, GPS modules, and NFC modules. The Bluetooth module is used to connect with devices such as smartphones to achieve data synchronization, receive notifications, and control phone functions. The GPS module is used to independently achieve positioning and motion tracking. The NFC module is used to enable near-field wireless communication functions, such as payments and access cards.

[0026] A distributed system is a decentralized network system that enables data communication and distributed processing based on decentralized principles, achieving end-to-end non-repudiation and traceability in the data processing process. Taking blockchain systems as an example, blockchain systems can ensure the security, transparency, and immutability of authorization methods through distributed ledgers, encryption technology, and consensus mechanisms.

[0027] like Figure 1 As shown, in some embodiments, the distributed system may include a decentralized network, which may include multiple network nodes. Each network node can be used to perform specific data processing functions, and the data processing flow is completed jointly through communication between the multiple network nodes. For example, a blockchain network, as a decentralized network, allows multiple participants (network nodes) to jointly maintain a decentralized authorization ledger. This ledger records all verified authorizations, which are organized into a series of blocks. Each block is cryptographically linked to the previous block, forming an immutable chain. Network nodes in a blockchain network can be personal computers, servers, or other electronic devices with data processing and communication capabilities. Network nodes are responsible for verifying authorizations, generating blocks, and disseminating information.

[0028] In some embodiments, multiple network nodes in a decentralized network can also form sub-networks based on the functions to be implemented. For example, multiple network nodes used for distributed data storage can form a decentralized storage network. Network nodes participating in distributed data processing within a decentralized storage network can be referred to as worker nodes. That is, a decentralized storage network can use multiple worker nodes to distribute data for storage.

[0029] The distributed system may also include user-end devices, which are electronic devices with data processing and communication capabilities. For example, user-end devices can be computers, mobile terminals such as mobile phones, servers, etc. In some embodiments, the user-end device can access the decentralized storage network by establishing a communication connection with at least one network node in the decentralized storage network, thereby utilizing the decentralized storage network for data storage. When performing data authorization, the user-end device can be used to perform user interactions and, through the connected network node, perform data interactions with the decentralized storage network.

[0030] In some embodiments, the user terminal device can also be considered a network node in the decentralized storage network, and can communicate directly or indirectly with any node in the decentralized storage network. Therefore, during the data authorization process, the user terminal device can not only perform user interactions, but also participate in the authorization execution process, that is, participate in at least one of the following stages: authorization initiation, authorization broadcasting, authorization verification, authorization pooling, block generation, and authorization confirmation.

[0031] Data licensing refers to the process of authorizing the paid use of personal data. Personal data can include various physiological indicators and behavioral information collected through smart wearable devices. For example, wearable devices such as smartwatches and fitness trackers can continuously and in real-time capture high-value personal data such as heart rate, steps, sleep patterns, and blood oxygen saturation.

[0032] Wearable devices collect rich, timely, and relatable personal data that reflects an individual's real-life habits, making it highly valuable and analytically promising for industries such as insurance, healthcare, and health management. Therefore, data licensing allows users to authorize data analytics firms to access their personal data for specific purposes. Since this personal data originates from wearable devices monitoring individual behavior and may contain sensitive information, users must anonymize their data before authorizing it to remove sensitive content and minimize the risk of privacy breaches.

[0033] However, when anonymizing personal data to remove private content, it can easily reduce the connection or ownership between the anonymized data and the user, thus affecting the user's ownership and control over their personal data. Therefore, while reducing the risk of privacy breaches when authorizing personal data, ensuring that users' ownership and control over their personal data are not compromised is a pressing issue that needs to be addressed.

[0034] Therefore, some embodiments of this application provide a distributed data authorization method based on wearable devices. This method can be applied to user-end devices, where the user-end device, as an electronic device with data processing capabilities, may include, but is not limited to, computers, servers, mobile terminals, smart wearable devices, industrial control machines, etc. For ease of description, the user-end device is used as the execution subject of the method in this application embodiment. It should be understood that the method can also be applied to other types of execution subjects, which are not shown one by one in this application embodiment. Figure 2 As shown, the method includes: S101. Obtain the raw data.

[0035] When performing data authorization, the user device can first obtain raw data, which includes raw health data and raw behavioral data collected by the wearable device. For example, raw health data and raw behavioral data, such as heart rate, blood oxygen, and sleep data, can be obtained from the wearable device or its synchronized application through data acquisition tools provided in the authorization platform application.

[0036] Depending on the type of user terminal device, different methods can be used to acquire raw data. When the user terminal device is a wearable device, it can directly receive raw data collected by the wearable device's built-in sensors. When the user terminal device is a terminal device that establishes a communication connection with the wearable device, it can send a data acquisition request to the wearable device, so that the wearable device can respond to the data acquisition request and send raw data back to the terminal device.

[0037] S102. Generate authorizable data based on the original data.

[0038] After acquiring the raw data, the user-end device can generate authoritative data based on it. This authoritative data is obtained by performing mandatory end-to-end encryption and a first layer of mandatory desensitization on the raw data. On the user-end device, mandatory end-to-end encryption of the raw data is required, ensuring that the user possesses a unique decryption key. Mandatory end-to-end encryption ensures that the data remains encrypted throughout transmission and is decrypted only at the sending and receiving ends.

[0039] In some embodiments, end-to-end encryption can be achieved through a hybrid encryption mechanism that combines asymmetric and symmetric encryption algorithms. For example, symmetric encryption algorithms such as RSA and ECC can be used for key exchange and digital signatures, ensuring the security of key transmission; while symmetric encryption algorithms such as AES and ChaCha20 can be used to encrypt actual data, providing high-efficiency encryption performance.

[0040] Forced anonymization involves modifying, replacing, encrypting, or deleting data that raises concerns about personal privacy and data security. This ensures that the original data retains its original characteristics while preventing direct identification of specific individuals or entities. For example, the original data might include a user's movement path data. Data security-related information within this movement path data could include all geographic coordinates along the path, path change trends, and offline map data. Therefore, forced anonymization protects data privacy while ensuring data remains usable in non-production environments or shared scenarios.

[0041] In some embodiments, data masking can include static masking and dynamic masking. Static masking refers to permanently modifying a data copy, making the data obtained through static masking irreversible and impossible to restore to the original data. Dynamic masking, on the other hand, displays masked data in real time based on user permissions. It can be combined with access control processes in the data processing environment to achieve different levels of masking, thereby maintaining the usability of the original data as much as possible.

[0042] During the data anonymization process, user-side data can be processed using different anonymization strategies based on specific data analysis (authorization) requirements. Different anonymization strategies have corresponding requirements for the original data; therefore, the specific execution order of the data anonymization and encryption processes can be determined based on the specific anonymization strategy used. In some embodiments, when generating authoritative data from the original data, the anonymization strategy can be obtained first, and then the encryption and anonymization order can be set according to the anonymization strategy.

[0043] If the desensitization strategy is Type I, the encryption and desensitization order is set to encryption first, then desensitization. Type I strategy refers to a data desensitization strategy that performs desensitization on encrypted data; that is, Type I data desensitization strategy includes a built-in data decryption program. After encrypting the original data to obtain the encrypted data, the user device can invoke Type I strategy and use the data decryption program to identify sensitive information from the encrypted data and perform data desensitization on the sensitive information. If the desensitization strategy is Type II, the encryption and desensitization order is set to desensitization first, then encryption. That is, Type II data desensitization strategy does not require a built-in data decryption program; it requires directly reading the sensitive information from the original data before encryption, desensitizing the sensitive information, and then encrypting it.

[0044] Following the encryption and desensitization sequence, a unique decryption key is generated by performing mandatory end-to-end encryption on the original data, and authoritative data is generated by performing a first-level mandatory desensitization on the original data. For example, in practical applications, the corresponding desensitization strategy can be used according to the device type of the user's terminal device. That is, when the user's terminal device includes a wearable device and a terminal device that have established a communication connection, the first type of strategy can be adopted. Then, when generating authoritative data, the original data collected by the wearable device's sensors can be encrypted first using the encryption algorithm built into the wearable device, and the encrypted data can be transmitted to the terminal device. The terminal device then uses the first type of desensitization strategy to desensitize the encrypted data to generate authoritative data.

[0045] Similarly, when the user device is a wearable device, the second type of strategy can be used for data anonymization. That is, the wearable device can simultaneously incorporate encryption and anonymization algorithms. After the built-in sensors acquire the raw data, the wearable device can first activate the anonymization algorithm corresponding to the second type of strategy to anonymize the raw data, obtaining anonymized data. Then, the encryption algorithm is activated to encrypt the anonymized data, obtaining authoritative data.

[0046] To achieve anonymization of the original data, in some embodiments, when the user-end device generates authoritative data based on the original data, it can identify information to be processed from the original data. This information to be processed includes at least one of the following: the user's real identity information, precise parameters, and authorization-sensitive fields; the precise parameters include precise timestamps and precise numerical values; and the authorization-sensitive fields include personal identification information unrelated to authorization.

[0047] After identifying the information to be processed from the original data, the content of the information can be judged, i.e., the information to be processed can be obfuscated to obtain authoritative data. Specifically, when the information to be processed includes the user's real identity information, the obfuscation process includes replacing the user's real identity information in the original data with a pseudo-anonymized data identifier; when the information to be processed includes the precise parameters, the obfuscation process includes obfuscating and range-dividing the precise parameters; when the information to be processed includes the authorization-sensitive field, the obfuscation process includes deleting the authorization-sensitive field from the original data.

[0048] That is, when the information to be processed includes the user's real identity information, the user's real identity information in the original data is replaced with a pseudo-anonymized data identifier. The pseudo-anonymized data identifier includes at least one of a blockchain address and a temporary ID. A blockchain address refers to the address of a storage node in a decentralized storage network, which is a publicly available network address.

[0049] When the information to be processed includes the precise parameters, the precise parameters are fuzzed and ranged; and when the information to be processed includes the authorization sensitive fields, the authorization sensitive fields in the original data are deleted to generate authoritative data.

[0050] For example, the de-identification processing of raw data on the user's device can be called Layer 0 de-identification. Depending on the de-identification strategy, before or after local encryption, the de-identification tools provided by the data authorization platform can be used to perform a first-level mandatory de-identification of the raw data. During this first-level mandatory de-identification process, pseudo-anonymization, generalization or aggregation processing, and deletion of highly sensitive fields can be performed on the raw data. Pseudo-anonymization refers to using a blockchain address or one-time ID as the data identifier, rather than the user's real identity. Generalization or aggregation processing involves obfuscating precise timestamps, such as down to the hour, and classifying specific values ​​into ranges, such as age groups rather than specific ages. Furthermore, highly sensitive fields are deleted by removing personal identification information unrelated to authorization.

[0051] Furthermore, during the generation of authorizable data, the degree of data anonymization of the original data can be controlled by the user. That is, the data authorization platform enforces the minimum anonymization standard, while users can choose a higher level of anonymization to meet their personalized data security needs.

[0052] S103. Upload the authorizable data to a decentralized storage network to obtain ownership certificates for the authorizable data.

[0053] After generating authoritative data from the original data, the user device can upload the authoritative data to a decentralized storage network. Once uploaded, one or more worker nodes in the decentralized storage network can process the authoritative data using a distributed data storage method and generate ownership certificates based on the authorized data. These ownership certificates are permanent on-chain proofs representing root ownership and authorization capabilities over the original data. The generated ownership certificates are then fed back to the user device, enabling the user device to obtain ownership of the authoritative data.

[0054] Ownership certificates are permanent on-chain proofs forged by smart contracts based on authoritative data after it has been uploaded to a decentralized storage network and a unique hash has been obtained. For example, when the decentralized storage network is a network such as the Interplanetary File System (IPFS), file storage and retrieval can be achieved through content addressing and distributed hash tables (DHTs).

[0055] In some embodiments, when uploading authoritative data to a decentralized storage network to obtain ownership certificates for the authoritative data, the user device can first obtain authoritative data of a preset type within a preset time period, and send the authoritative data to any working node in the decentralized storage network, so that the working node can perform a hash operation on the authoritative data to generate unique hash information.

[0056] For example, after uploading the anonymized and encrypted original data packets to a decentralized storage network (DSN), the DSN can perform a hash calculation on the content of the authoritative data to obtain a Content Identifier (CID). The CID, as a hash value used to uniquely identify content, ensures the uniqueness and immutability of the authoritative data content within the DSN. After generating the CID, the centralized storage network can also feed it back to the user device, enabling the user device to locate and manage the authoritative data stored in the centralized storage network based on the CID.

[0057] The user-end device then receives unique hash information and runs a smart contract through worker nodes, using the smart contract to forge ownership certificates based on authorizable data. This ownership certificate is a permanent on-chain proof. For example, the permanent on-chain proof includes information such as the data's time range, data type, and anonymization level. When a user first uploads authorizable data of a specific time period or type, such as all sleep data from July 2024, to the IPFS network, they receive a CID from the IPFS network. Simultaneously, the IPFS network can forge a non-transferable Soul-Bound Token (SBT) for the user through a smart contract. This SBT, as permanent on-chain proof of the user's root ownership and authorization capabilities over the original data packet, can be bound to the user's wallet address. Furthermore, all subsequent authorizations or derivative product generation based on this original data require authorization through holding this SBT. Therefore, the metadata corresponding to the SBT can include information such as the data's time range, approximate type, and anonymization level.

[0058] S104. In response to an authorization request for authorizable data, obtain data authorization credentials.

[0059] After authorizable data is uploaded to the decentralized storage network, the user device can obtain an authorization request through the decentralized storage network or the data authorization platform server. In response to the authorization request for the authorizable data, it obtains a data authorization certificate. This data authorization certificate represents the user's right to use the authorizable data; the data authorization certificate is an authorization credential for authorizable data forged by the decentralized storage network based on ownership certificates.

[0060] In some embodiments, the data authorization credential includes a general authorization credential and a higher-level authorization credential. The general authorization credential includes unique hash information. That is, when executing a response to an authorization request for authorizable data and obtaining a data authorization credential, an authorization request may be received first. The authorization request is a request entered by the user holding the ownership credential through the platform authorization interface.

[0061] The system reads ownership credentials from the authorization request and, based on these credentials, locates authorizable data in a decentralized storage network. A generic authorization credential is then forged based on the authorizable data, wherein the generic authorization credential represents a conditional authorization for decryption and / or analysis of the authorizable data.

[0062] For example, such as Figure 3 As shown, users holding SBTs can generate authorization requests by performing authorization operations through the platform's authorization interface. When the authorization request is for authorizable data uploaded by the current user's device, one or more worker nodes in the decentralized storage system can mint transferable L0 data authorization certificates based on the data packets represented by SBTs. The data authorization certificate can be a non-fungible token (NFT), such as a data authorization certificate generated based on the ERC-721 non-fungible token standard on Ethereum.

[0063] In this context, an L0 Data Authorization Certificate (NFT) can represent a one-time or limited-term authorization for a specific de-identified encrypted raw data packet, such as a single-time analysis access or a three-month access right for decryption or analysis. Correspondingly, the metadata associated with an L0 Data Authorization Certificate (NFT) may include name information, description information, data hash, SBT reference, authorization type, and authorization duration.

[0064] For example, the metadata corresponding to the L0 data authorization certificate NFT includes the following information: Name: "User X July 2024 Sleep Data Authorization Certificate"; Description: User description, authorization scope, data content, authorization type (one-time / limited-term), and anonymization level; Data Hash: Points to the CID of the encrypted original data file on IPFS; Ownership Certificate: Points to the corresponding SBT, proving its legitimate origin. Authorization types include One-Time Analysis authorization and Limited-Time Access authorization; Authorization duration is a set duration, such as 3 months, etc. If it is a One-Time Analysis authorization, the authorization duration is empty.

[0065] The minting of L0 NFTs is essentially a decryption key authorization process. The SBT holder, through a smart contract, sets how the decryption key is securely transferred to the new L0 NFT holder after the L0 NFT is transferred. Therefore, the authorizing user device can list the minted L0 NFTs for sale on the platform, enabling the sale of L0 NFTs. A base price can be set to represent the value of obtaining authorization to analyze or access the original (anonymized and encrypted) data.

[0066] In some embodiments, when executing the process of obtaining a data authorization credential in response to an authorization request for authorizable data, authorization platform information can also be read from the authorization request. This platform authorization information is used to characterize the authorization of the platform by the user holding the ownership credential through a smart contract, and the data processing methods permitted to be performed by the authorization platform on the authorizable data.

[0067] Next, based on the authorization platform information, a second layer of mandatory desensitization is performed on the authorizable data through the work nodes associated with the authorization platform to generate first-layer product data. Then, through the work nodes, a first high-level authorization credential is forged based on the first-layer product data, whereby the first high-level authorization credential represents access rights to the first-layer product data.

[0068] For example, to achieve data authorization and platform collaboration, user devices holding SBTs can choose an authorization platform and authorize it through a smart contract, specifying the type of data processing the platform will perform, such as aggregation, standardization, and report generation, and agreeing on the revenue sharing ratio. This enables secure channel access or deeper processing based on authorizable data (L0 raw data) in a privacy computing environment.

[0069] The working nodes in the data authorization platform can perform structured and standardized processing on the L0 data authorized by the user, and perform a second layer of desensitization, such as aggregating into weekly averages and monthly trends, adding differential privacy noise, and removing all personally identifiable information. In this way, a layer of product data, namely L1 data product, is generated through standardized or aggregated data processing.

[0070] During the generation of the first-layer product data, L1 high-level authorization credential NFT minting can also be performed. For example, after structuring, standardizing, and performing second-layer anonymization processing through the data licensing platform's worker nodes to obtain an anonymous dataset of 1000 users' average weekly sleep duration, the generated L1 data product can be used as a new NFT to obtain a high-level authorization credential. The high-level authorization credential L1 NFT can then represent access rights to a certain type of aggregated, anonymized data. Because this data is highly anonymized, the requesting party does not need to perform complex analysis of the original data and can use it directly.

[0071] In some embodiments, the generated first-level product data can be further processed with higher-level data analysis. That is, after acquiring multiple first-level product data sets, second-level analysis can be performed on the multiple first-level product data sets through work nodes, according to the authorized platform information, to obtain second-level product data. The second-level analysis data includes at least one of insight reports, behavioral patterns, and model parameters.

[0072] For example, a working node in a data authorization platform can utilize multiple L1 data sets, or perform privacy calculations on L0 data with user authorization, to conduct deeper second-level analysis, generating advanced insight reports, behavioral patterns of specific groups, or trained model parameters to generate L2+ data products for identifying advanced analysis or insight reports.

[0073] After generating Layer 2 product data, worker nodes then forge a second-level authorization credential based on this data. This second-level authorization credential represents access to the Layer 2 product data. For example, after generating L2+ data products, worker nodes can forge L2+ NFTs. By forging these reports or model parameters as L2+ NFTs, access to specific insights or analytical results is represented. These high-value data products can meet specific industry needs, such as cardiovascular health risk assessment reports for a user group of an insurance product. Platforms or users can list and sell the forged L1 and L2+ NFTs on the data licensing platform through agreed-upon revenue sharing. These NFTs have more direct commercial value and command higher prices than L0 NFTs.

[0074] S105. Transfer the data authorization certificate according to the authorization request.

[0075] After obtaining data authorization credentials, the user device can transfer the data authorization credentials according to the authorization request. By transferring the data authorization credentials, authorization of authorizable data can be achieved, allowing the data requester to obtain partial analysis authorization or access authorization for authorizable data according to the data authorization credential transfer process, thereby meeting the requester's data usage needs.

[0076] In some embodiments, when transferring data authorization credentials based on an authorization request, the user terminal device can also obtain requester requirement information through a decentralized storage network and parse the requester requirement information into executable analysis logic. The requester requirement information includes data analysis requirements and data acquisition requirements.

[0077] The worker nodes of the decentralized storage network then obtain authorization notifications based on executable analysis logic, enabling user devices to authorize data authorization through ownership credentials and submit data authorization credentials to the smart contract. Based on the data authorization credentials, data analysis specified by the requester's requirements is performed on the authorized data in a privacy-preserving computing environment to generate analysis result data and analysis proof. The smart contract then verifies the analysis proof, and based on the verification results, the authorizable data is updated using the analysis result data.

[0078] For example, such as Figure 4 As shown, the authorization platform can first obtain data requirements. That is, the requesting user device can perform interactive operations on the platform interface, describing in natural language, such as "I need 100 anonymous heart rate and blood oxygen data of users who, in the past 3 months, had a heart rate exceeding 150 bpm for more than 15 minutes during strenuous exercise and a blood oxygen saturation below 90%", or use smart filters, such as adjusting parameters with sliders, selecting preset activity types, and submitting the required data characteristics and quantity.

[0079] The requester's needs are then analyzed by the AI ​​model in the data authorization platform's backend, transforming them into executable analysis logic within the platform. Intelligent matching and data recommendation are then used to generate or confirm authorizable data. The platform displays the matching results in real time, such as "[X] sets of raw data matching your needs have been found" or "[Y] relevant analysis reports are recommended."

[0080] Then, on-demand privacy analysis is performed to match L0 data. The platform automatically dispatches a Privacy Computing Service Provider (PCP) to perform on-demand privacy analysis on the L0 encrypted raw data that meets the basic conditions in a TEE or federated learning environment. The PCP generates a Privacy Proof (ZKP) or TEE proof, which is verified by the platform's smart contract to confirm which L0 NFTs or L0 data packets meet the requester's requirements.

[0081] The platform also automatically retrieves and recommends aggregated data or analysis reports that meet the requester's needs from the existing L1 / L2+ derivative data product library, namely L1 NFT or L2+ NFT, to realize the recommendation of L1 data products and L2+ data products.

[0082] Once the requesting user device confirms the purchase of an L0 licensed NFT or an L1 / L2+ data product NFT through interactive operations, it clicks "Pay." The payment process utilizes the licensed certificate; the platform automatically completes certificate redemption and on-chain operations, achieving purchase confirmation and automatic delivery. At this point, the platform can automatically complete the NFT ownership transfer and fund settlement using smart contracts based on on-chain atomic authorization. Furthermore, after a successful purchase, the platform automatically delivers the data decryption key for L0 data or the data download link and API key for L1 / L2+ data to the requesting user device via an encrypted channel. This allows the requesting user to directly access and download the data in the platform backend or via API, without any manual decryption or blockchain operations.

[0083] By applying the technical solutions of the above embodiments, the distributed data licensing method based on wearable devices described in the above embodiments can ensure that users have permanent and inalienable ownership of the original data through SBT, realizing true user data sovereignty. Furthermore, it enables on-demand privacy computing, overcoming the limitations of traditional tag presets, meeting the needs of arbitrarily complex and dynamic requesters, and achieving extremely flexible demand matching. The method also allows users to directly sell original data licenses (L0) or sell advanced derivative data products (L1 / L2+) through DPS cooperation, realizing multi-level data value utilization. Moreover, the same original data can be analyzed multiple times by minting different L0 NFTs (license certificates), enabling continuous data analysis and utilization, meeting the needs of data reuse and multiple analysis. The method can also enforce desensitization at the L0 layer, allowing privacy computing to perform analysis without disclosing the original data, maximizing privacy security and achieving a balance between privacy and utility. In addition, all key licenses and authorizations are recorded on the blockchain, ensuring transparency and traceability, realizing traceability and transparency of data licensing.

[0084] In some embodiments, as a refinement and extension of the specific implementation of the above embodiments, and to fully illustrate the specific implementation process of this embodiment, some embodiments of this application also provide a distributed data authorization method based on wearable devices, applied to a decentralized storage network, such as... Figure 5 As shown, the method includes: S201, Receive authorized data.

[0085] S202. Perform distributed storage on the authorizable data to generate unique hash information; S203, Send the unique hash information to the user terminal device, and use a smart contract to forge ownership certificates based on authoritative data; S204. In response to a request for authorization of authorizable data, a data authorization certificate for the authorizable data is created based on the ownership certificate; S205. Transfer data authorization credentials according to the authorization request.

[0086] In the process of data authorization, a decentralized storage network can first receive authorizable data. It then performs distributed storage on this authorizable data to generate unique hash information. This authorizable data is obtained by performing mandatory end-to-end encryption and a first layer of mandatory de-identification on the raw data collected from wearable devices.

[0087] The unique hash information is then sent to the user device, and a smart contract is used to mint an ownership certificate based on the authorizable data. This ownership certificate is a permanent on-chain proof representing root ownership and authorization capabilities over the original data. When the requesting user device sends an authorization request, it can respond to the authorization request for the authorizable data by minting a data authorization certificate based on the ownership certificate, and then transferring the data authorization certificate according to the authorization request. The data authorization certificate represents the right to use the authorizable data, and includes a general authorization certificate and a higher-level authorization certificate; the general authorization certificate includes unique hash information.

[0088] For example, requesting user devices can submit and browse data requests at different levels through multi-tiered requests. For raw data analysis of L0 NFTs, requesting user devices can propose highly customized requests, such as "abnormal blood oxygen levels during strenuous exercise," and submit their analysis logic through the platform's smart contract. For derivative data products of L1 or L2+ NFTs, users can directly search, filter, and purchase generated and listed L1 or L2+ NFTs for sale.

[0089] During the authorization process, for L0 NFT analysis needs, the decentralized storage network can extract and match features on demand. Specifically, the data authorization platform associated with the decentralized storage network can parse the analysis requirements submitted by the requester into executable analysis logic and coordinate with the PCP (Programmable Execution Platform). The L0 NFT authorizing user device then responds, notifying the authorizing user device holding the relevant L0 NFT. The authorizing user device, through its SBT (Smart Bitwise Power) authorization, submits the L0 data authorization certificate NFT to the smart contract, agreeing to allow the PCP to perform the analysis specified by the requester on its encrypted L0 data within a privacy computing environment (TEE / Federated Learning / MPC).

[0090] During the PCP execution analysis, zero-knowledge proofs (ZKPs) / TEEs can be generated to verify whether the data meets the requester's requirements without disclosing the original data, thus achieving secure computation and proof. The PCP proof is then verified using a smart contract. If valid, the L0 NFT is marked as compliant and can be verified on-chain and a data pool built. At this point, the requester can see the real-time growth in the number of compliant L0 NFTs. For L0 NFTs, once the required number is met, the requester purchases these matched L0 NFTs (data authorization certificates). For L1 or L2+ NFTs, the requester directly purchases L1 or L2+ NFTs already listed for sale on the market.

[0091] like Figure 6 As shown, in some embodiments, decentralized storage networks can also transform unmet needs into new data contribution opportunities to transparently and efficiently guide user participation. During the authorization process, if the data request from the requesting user's device is not successfully matched, a notification and customized project suggestion can be provided. For example, if the platform cannot find sufficient or fully matching data in existing minted L0 NFTs or L1 / L2+ data products, the system will prompt the requester, "We have not found data that fully meets all your conditions, but we can initiate a customized data contribution project to meet your needs." At this point, the data licensing platform can use its AI model to analyze existing data coverage and determine if new data contributions are needed. It can then initiate customized data contribution projects. For example, after the requester selects "Initiate Custom Project" and defines the compensation they are willing to pay for each eligible data set, the target data volume, and the project duration, the data licensing platform can translate the requester's needs into task instructions and lock the requester's pre-paid funds. It then targets potential data contributors with on-demand L0 NFT casting requests. Specifically, the platform uses its AI model to identify user devices whose raw data might meet the customized requirements, including those that have not yet cast L0 NFTs for this purpose.

[0092] The platform then notifies the user's device of the identification results, such as sending a message that reads, "A new data contribution task is relevant to you. You can earn [XX yuan] by sharing specific features from your data. Click to participate." Users click the "Participate" link or control to initiate the on-demand privacy analysis process on their local device. Users do not need to upload raw data or manually mint NFTs.

[0093] At this point, the platform automatically forges a customized L0 data authorization credential NFT for the user. The metadata of this NFT clearly associates with the requester's requirements and defines the scope of this authorization. Simultaneously, this L0 NFT immediately participates in privacy computation verification. The platform then automatically schedules PCP and executes the requester-defined analysis logic on the user's local encrypted raw data within a TEE or federated learning environment. If successful, PCP generates a ZKP / TEE proof, which is then verified by the platform's smart contract.

[0094] The platform then uses smart contracts to verify the ZKP / TEE proofs of all participating users, enabling batch delivery and revenue settlement. When a sufficient amount of qualifying data is collected, the platform delivers these newly minted L0 NFTs or their analysis results to the requester. The requester receives their customized data results as needed and pays a fee, making the licensing experience identical to direct purchase. Furthermore, users who contribute receive corresponding rewards.

[0095] By applying the technical solutions of the above embodiments, the distributed data authorization method based on wearable devices described in the above embodiments can achieve privacy computing without disclosing the original data through forced desensitization, maximizing privacy and security. It also ensures user ownership of the data through ownership certificates. Furthermore, by forging data authorization certificates and achieving on-chain recording of key authorizations and authorizations, the transparency and traceability of data authorization can be improved.

[0096] In some embodiments, as a specific implementation of the distributed data authorization method based on wearable devices in the above embodiments, some embodiments of this application also provide a distributed data authorization system based on wearable devices, such as... Figure 7 As shown, the system includes a decentralized storage network and multiple user terminal devices; the multiple user terminal devices establish communication connections through the decentralized storage network; and at least one wearable device is included among the multiple user terminal devices.

[0097] The user-end device is configured to: acquire raw data, including raw health data and raw behavioral data collected by the wearable device; generate authoritable data based on the raw data, wherein the authoritable data is data obtained by performing mandatory end-to-end encryption and first-layer mandatory desensitization on the raw data; and upload the authoritable data to a decentralized storage network. The decentralized storage network consists of multiple worker nodes, which are configured to: perform distributed storage on authoritative data to generate unique hash information; send the unique hash information to the user device; and use smart contracts to mint ownership certificates based on the authoritative data. The worker node is also configured to: in response to an authorization request for authorizable data, forge a data authorization credential for the authorizable data based on the ownership certificate, and transfer the data authorization credential according to the authorization request.

[0098] By applying the technical solutions of the above embodiments, the distributed data authorization system based on wearable devices described in the above embodiments can acquire raw data through wearable devices, perform mandatory end-to-end encryption and desensitization on the raw data, and generate authoritable data. The authoritable data is then uploaded to a decentralized storage network to forge ownership certificates for the authoritative data. When performing data authorization, a data authorization certificate for the authoritative data can be forged based on the ownership certificate, thereby transferring the data authorization certificate according to the authorization request. The system can achieve privacy-preserving computation without disclosing the raw data through mandatory desensitization, maximizing privacy and security, and also ensures user ownership of the data through the ownership certificate. Furthermore, by forging data authorization certificates, key authorizations and on-chain recording of authorizations can be achieved, improving the transparency and traceability of data authorization.

[0099] It should be noted that other corresponding descriptions of the functional units involved in the distributed data authorization system based on wearable devices provided in the embodiments of this application can be found in the corresponding descriptions in the distributed data authorization method based on wearable devices provided in the above embodiments, and will not be repeated here.

[0100] This application also provides a computer device, specifically a personal computer, server, network device, etc. The computer device includes a bus, processor, memory, and communication interface, and may also include input / output interfaces and a display device. The processor of the computer device provides computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and internal memory. The non-volatile storage medium stores an operating system, computer programs, and a database. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage medium. The database of the computer device stores location information. The network interface of the computer device is used for communication with external terminals via a network connection. When the computer program is executed by the processor, it implements the steps in the various method embodiments.

[0101] Those skilled in the art will understand that the structure of the computer device described above is only a partial structure related to the solution of this application, and does not constitute a limitation on the computer device to which the solution of this application is applied. A specific computer device may include more or fewer components, or combine certain components, or have different component arrangements.

[0102] In one embodiment, a computer-readable storage medium is also provided, which may be non-volatile or volatile, having stored thereon a computer program that, when executed by a processor, implements the steps in the above method embodiments.

[0103] In one embodiment, a computer program product is also provided, including a computer program that, when executed by a processor, implements the steps in the above method embodiments.

[0104] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties.

[0105] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the methods described above.

[0106] Any references to memory, database, or other media used in the embodiments provided in this application may include at least one of non-volatile and volatile memory. Non-volatile memory may include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc.

[0107] Volatile memory may include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM can take many forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM).

[0108] The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, distributed databases based on blockchain. The processors involved in the embodiments provided in this application may be, but are not limited to, general-purpose processors, graphics processors, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, etc.

[0109] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0110] The above embodiments are merely illustrative of several implementation methods of this application, and their descriptions are relatively specific and detailed. However, they should not be construed as limiting the scope of this application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

Claims

1. A distributed data authorization method based on wearable devices, characterized in that, Applied to a user terminal device, the method includes: Obtain raw data, which includes raw health data and raw behavioral data collected by wearable devices; Authorizable data is generated based on the original data, wherein the authorizable data is data obtained by performing mandatory end-to-end encryption and first-layer mandatory desensitization on the original data; The authorizable data is uploaded to a decentralized storage network to obtain ownership certificates for the authorizable data; the ownership certificate is a permanent on-chain proof that represents the root ownership and authorization capability of the original data. In response to an authorization request for the authorizable data, a data authorization credential is obtained, which is used to represent the permission to use the authorizable data; Transfer the data authorization certificate according to the authorization request.

2. The method according to claim 1, characterized in that, Generate authorizable data based on the original data, including: Obtain desensitization strategies; Set the encryption and desensitization order according to the desensitization strategy; According to the encryption and desensitization sequence, a unique decryption key is generated by performing forced end-to-end encryption on the original data, and the authorized data is generated by performing a first-level forced desensitization on the original data.

3. The method according to claim 1, characterized in that, Generate authorizable data based on the original data, including: Identify information to be processed from the raw data. The information to be processed includes at least one of the following: user's real identity information, precise parameters, and authorization sensitive fields. The precise parameters include precise timestamps and precise numerical values. The authorization sensitive fields include personal identification information unrelated to authorization. The information to be processed is obfuscated to obtain authoritative data; Wherein, when the information to be processed includes the user's real identity information, the obfuscation process includes replacing the user's real identity information in the original data with a pseudo-anonymized data identifier; When the information to be processed includes the precise parameters, the fuzzification process includes fuzzification and intervalization of the precise parameters; When the information to be processed includes the authorization sensitive field, the obfuscation process includes deleting the authorization sensitive field from the original data.

4. The method according to claim 1, characterized in that, Uploading the authorizable data to a decentralized storage network to obtain ownership certificates for the authorizable data includes: Obtain the authorizable data of a preset type within a preset time period; The authorizable data is sent to any working node in the decentralized storage network so that the working node can perform a hash operation on the authorizable data to generate the unique hash information. The system receives the unique hash information, runs a smart contract through the worker node, and uses the smart contract to forge the permanent on-chain proof based on the authorizable data; the permanent on-chain proof includes data time range, data type, and anonymization level information.

5. The method according to claim 1, characterized in that, The data authorization credentials include a general authorization credential and a higher-level authorization credential, and the general authorization credential includes unique hash information; In response to an authorization request for the authorizable data, obtaining data authorization credentials includes: Receive the authorization request, which is a request entered by the user holding the ownership certificate through the platform authorization interface; Read the ownership certificate from the authorization request; Based on the ownership certificate, locate the authorizable data in the decentralized storage network; The general authorization credential is cast based on the authorizable data, and the general authorization credential is used to perform conditional decryption authorization and / or analysis authorization on behalf of the authorizable data.

6. The method according to claim 5, characterized in that, In response to an authorization request for the authorizable data, obtaining data authorization credentials includes: The authorization platform information is read from the authorization request. The platform authorization information is used to characterize the authorization platform explicitly authorized by the user holding the ownership certificate through a smart contract, and to allow the authorization platform to perform data processing on the authorizable data. According to the authorization platform information, the authorized data is subjected to a second layer of forced desensitization through the work nodes associated with the authorization platform to generate a layer of product data; Through the working node, a first high-level authorization credential is forged based on the first-level product data. The first high-level authorization credential represents the right to access the first-level product data.

7. The method according to claim 6, characterized in that, The method further includes: Obtain multiple product data from the first layer; Through the work node, second-level analysis is performed on multiple first-level product data according to the authorized platform information to obtain second-level product data. The second-level analysis data includes at least one of insight reports, behavioral patterns, and model parameters. The working node forges a second high-level authorization credential based on the second-level product data. The second high-level authorization credential represents the right to access the second-level product data.

8. A distributed data authorization method based on wearable devices, characterized in that, Applied to decentralized storage networks, the method includes: Receive authenticable data, which is data obtained by performing mandatory end-to-end encryption and first-layer mandatory desensitization on the raw data collected by the wearable device; Distributed storage is performed on the authorizable data to generate unique hash information; The unique hash information is sent to the user device, and a smart contract is used to mint an ownership certificate based on the authorizable data; the ownership certificate is a permanent on-chain proof that represents the root ownership and authorization capability of the original data. In response to an authorization request for the authorizable data, a data authorization certificate for the authorizable data is forged based on the ownership certificate; the data authorization certificate is used to represent the right to use the authorizable data; Transfer the data authorization certificate according to the authorization request.

9. The method according to claim 8, characterized in that, The method further includes: Obtain the requester's requirements information, which includes data analysis requirements and data acquisition requirements; The requester's demand information is parsed into executable analysis logic; According to the executable analysis logic, an authorization notification is sent to the user terminal device so that the user terminal device authorizes the data authorization certificate through the ownership certificate and submits the data authorization certificate to the smart contract; Based on the data authorization credential, the authorized data is subjected to data analysis specified by the requester's requirements in a privacy computing environment to generate analysis result data and analysis proof; The smart contract verifies the analytical proof, and based on the verification result of the analytical proof, the data used to update the authorizable data.

10. A distributed data authorization system based on wearable devices, characterized in that, The system includes: a decentralized storage network and multiple user terminal devices; the multiple user terminal devices establish a communication connection through the decentralized storage network; at least one wearable device is included among the multiple user terminal devices; The user terminal device is configured to: acquire raw data, including raw health data and raw behavioral data collected by the wearable device; generate authoritable data based on the raw data, wherein the authoritable data is data obtained by performing mandatory end-to-end encryption and first-layer mandatory desensitization on the raw data; and upload the authoritable data to a decentralized storage network. The decentralized storage network includes multiple worker nodes, which are configured to: perform distributed storage on the authorizable data to generate unique hash information; send the unique hash information to the user terminal device; and use a smart contract to forge ownership certificates based on the authorizable data; the ownership certificate is a permanent on-chain proof representing root ownership and authorization capability over the original data. The working node is further configured to: in response to an authorization request for the authorizable data, forge a data authorization certificate for the authorizable data based on the ownership certificate, and transfer the data authorization certificate according to the authorization request; the data authorization certificate is used to represent the usage rights of the authorizable data.

Images