Data space infrastructure-oriented data use control negotiation method

Through the data usage control negotiation method for data space infrastructure, combined with OAuth, RBAC and ABAC models, smart contracts and blockchain technology are used to solve the security, trust and efficiency problems in data sharing, and achieve fine-grained permission control and efficient data management.

CN119004427AInactive Publication Date: 2024-11-22KEY TECH & EVALUATION OF NEXT GENERATION INTERNET BEIJING ENG RES CENT CO LTD +1

Patent Information

Application Number
CN202411488679.3
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-10-24
Publication Date
2024-11-22
Estimated Expiration
Not applicable · inactive patent

AI Technical Summary

Technical Problem

During the data sharing process, data security and privacy protection, lack of trust mechanisms, inefficient negotiation, and compliance and technical issues lead to low data use efficiency, making it difficult to meet the rapidly changing market demand.

Method used

Adopt data usage control negotiation method for data space infrastructure, through identity authentication, permission evaluation and smart contract negotiation, combined with OAuth, RBAC and ABAC models, log query and audit reports are generated, and blockchain technology is used to ensure the security of data transactions. and transparency.

Benefits of technology

It improves the security and trust of data sharing, simplifies the data usage negotiation process, provides fine-grained permission control, improves the overall level of data management and negotiation efficiency, and is suitable for cross-organization and cross-regional data exchange scenarios.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119004427A_ABST
    Figure CN119004427A_ABST
Patent Text Reader

Abstract

The invention discloses a data space infrastructure-oriented data use control negotiation method, which belongs to the technical field of data management and security. The method comprises the following steps: carrying out identity authentication on a user request; performing authority evaluation and decision on the user identity information passing the verification; executing authority evaluation and decision results; according to the execution result, the data provider negotiates with the data user; and generating a log query and audit report. The method is widely applied to cross-organization and cross-region data exchange and cooperation scenes, healthy development of data sharing ecology can be effectively promoted, and the overall level of data management is improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of data management and security technology, and in particular to a data usage control negotiation method oriented to a data space infrastructure. Background Art

[0002] With the advent of the big data era, data has become an important production factor and resource. The sharing and use of data can not only promote economic development, but also enhance social governance capabilities. However, in the actual process of data sharing and use, data providers and data users still face the following challenges: 1. Data security and privacy protection: In the process of data sharing, ensuring that data is not abused or leaked is a key issue. Traditional data sharing methods often lack effective security mechanisms and cannot fully protect the rights and interests of data owners.

[0003] 2. Lack of trust mechanism: In data exchange scenarios involving multiple parties, the lack of a unified trust mechanism makes all parties concerned when conducting data transactions. In particular, trust issues are particularly prominent in cross-organizational and cross-regional data exchanges.

[0004] 3. Inefficient negotiation: Existing data usage negotiations usually rely on manual work and traditional legal agreements. The process is cumbersome and inefficient, and it is difficult to adapt to rapidly changing market demands.

[0005] 4. Compliance and technical issues: Data is vulnerable to unauthorized access and leakage during transmission and storage. The dynamic adjustment of laws, regulations and compliance requirements makes the compliant use of data complicated. There are also technical issues such as time delay and data integrity in the data transmission process, which affect the efficient use of data.

[0006] In order to meet the above challenges, a new data usage control negotiation method for data space infrastructure is urgently needed to improve the security, trust and efficiency of data sharing. Summary of the invention

[0007] The purpose of the present invention is to propose a data usage control negotiation method oriented to data space infrastructure.

[0008] A data usage control negotiation method for a data space infrastructure comprises the following steps: Authenticate user requests; Conduct authority evaluation and decision making on the verified user identity information; Executive authority assessment and decision-making outcomes; Based on the execution results, the data provider negotiates with the data user; Generate log query and audit reports.

[0009] Use the OAuth authentication protocol to authenticate user requests.

[0010] In the process of evaluating and deciding the permissions of the verified user identity information, the RBAC model and ABAC model are used to control the permissions of user roles, attributes, resource attributes, and environmental attributes.

[0011] The negotiation process between data providers and data users is as follows: Data users and data providers are initialized separately, prepare the information and resources required for negotiation, deploy their respective smart contracts, and record the initial status of both parties; The data user generates a data usage contract and initiates a negotiation request. The smart contract automatically processes the negotiation request and performs preliminary verification. The data user evaluates the contract response and confirms the contract, generating a contract acceptance agreement; The data user and data provider accept the negotiation content and reach a data use contract; Data users and data providers verify the contract through smart contracts to ensure the execution of the contract terms.

[0012] A data usage control negotiation system for data space infrastructure, comprising: Identity authentication module, used to authenticate user requests; The policy engine module is used to evaluate and make decisions on the permissions of authenticated user identity information; Data access control module, used to perform permission evaluation and decision results; A negotiation module is used for the data provider and the data user to negotiate based on the execution results; Audit module, used to generate log queries and audit reports.

[0013] The OAuth authentication protocol is used in the identity authentication module to authenticate user requests.

[0014] In the policy engine module, the RBAC model and ABAC model are used to comprehensively control the permissions of user roles, attributes, resource attributes, and environmental attributes during the process of authority evaluation and decision-making for the verified user identity information.

[0015] The negotiation process between data providers and data users in the negotiation module is as follows: Data users and data providers are initialized separately, prepare the information and resources required for negotiation, deploy their respective smart contracts, and record the initial status of both parties; The data user generates a data usage contract and initiates a negotiation request. The smart contract automatically processes the negotiation request and performs preliminary verification. The data user evaluates the contract response and confirms the contract, generating a contract acceptance agreement; The data user and data provider accept the negotiation content and reach a data use contract; Data users and data providers verify the contract through smart contracts to ensure the execution of the contract terms.

[0016] An electronic device includes a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, each step in a data usage control negotiation method for a data space infrastructure is implemented.

[0017] A storage medium stores a computer program, which, when executed by a processor, implements various steps in a data usage control negotiation method for a data space infrastructure.

[0018] The beneficial effects of the present invention are: 1. The present invention uses blockchain technology to build a secure and transparent data usage negotiation mechanism to ensure credible data transactions between data owners and data users, thereby enhancing trust.

[0019] 2. The present invention combines encryption technology to design an effective data usage control strategy to ensure the legality, privacy protection and efficiency of data during sharing and access, meet the needs of efficient data circulation and use, and provide strong support for various data-driven applications.

[0020] 3. The present invention automatically executes the terms and conditions in data usage negotiations through smart contracts, simplifies the process of data usage negotiations, reduces manual intervention and cumbersome agreement signing process, and improves negotiation efficiency.

[0021] 4. The present invention provides a fine-grained permission control and management mechanism, enabling data owners to flexibly set and adjust data usage permissions according to actual needs, ensuring flexibility and controllability of data during sharing and use.

[0022] 5. The method of the present invention is widely applicable to cross-organizational and cross-regional data exchange and collaboration scenarios, and can effectively promote the healthy development of the data sharing ecosystem and improve the overall level of data management. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] Figure 1 This is a system architecture diagram for data usage control in data space; Figure 2 It is a flow chart of the implementation of the data usage control negotiation method for data space infrastructure of the present invention; Figure 3 This is a diagram of the ABAC model implementation architecture of the present invention; Figure 4 This is a diagram of the RBAC model implementation architecture of the present invention; Figure 5 A flow chart of analyzing log data by the log analyzer of the present invention; Figure 6 Flow chart of the negotiation process of the present invention. DETAILED DESCRIPTION

[0024] The present invention proposes a data usage control negotiation method for data space infrastructure, which will be further described below in conjunction with the accompanying drawings and specific embodiments.

[0025] Figure 1 This is a system architecture diagram for data usage control in the data space. The six-dimensional data policy model is used in this architecture to restrict and control the use of data from multiple dimensions, including "who uses it", "when to use it", "how to use it", "where to use it", "number of times to use it" and "purpose of use".

[0026] 1. Who will use it? Specific users or roles can be specified.

[0027] Trust levels are divided into three levels: normal, trust, and trust+. Particularly important data can only be used by trust+ level users.

[0028] Freely define granularity in enterprise classification to increase the freedom of data use.

[0029] 2. When to use: Trigger time: The time after which the data can be used.

[0030] Time period: The specific time period during which the data is available.

[0031] Time period: The start and end dates for limiting data usage.

[0032] 3. How to use: By specifying a specific application, the data provider can request that the data be used on a certain APP.

[0033] 4. Where to use: Physical location: country, city, and region.

[0034] Server environment: operating system, cloud platform.

[0035] 5. Number of times used: Limits on the number of times a data user can use the data.

[0036] 6. Usage: View: View data online.

[0037] Download: Download to local computer.

[0038] Delete: Delete the file.

[0039] Edit: Make changes to a file.

[0040] Forward: Forward to a third party.

[0041] Usage notification: Notify the data provider each time the data is used.

[0042] This embodiment uses the role-based access control (RBAC) and attribute-based access control (ABAC) models to develop a fine-grained access control strategy. Each data object is associated with a specific access permission, and only users or systems that meet the permission requirements can access and operate the data. By dynamically evaluating information such as user roles, attributes, and access environments, the secure use of data in different scenarios is ensured. The implementation process is as follows: Figure 2 As shown, the details are as follows: The user initiates a data use request and enters the identity authentication module. This module ensures the authenticity of the user's identity. When the user issues an access request, the identity authentication module first verifies the user's identity, specifically using the OAuth authentication protocol to complete the authentication. After the identity authentication is passed, the user's identity information will be passed to the policy engine module.

[0043] In the policy engine module, two models are used to parse and execute policies, namely the RBAC and ABAC models. According to user identity information and request content, the policy engine module uses RBAC and ABAC in combination to control permissions for roles, attributes, resource attributes, and environment attributes.

[0044] RBAC is a role-based access control model that simplifies permission management and control by assigning permissions to roles and then assigning roles to users. RBAC mainly includes the following core attributes: Role: Represents a set of permissions, usually corresponding to a position or function in an organization.

[0045] User: The subject who accesses system resources, which can be an individual, device, or other system.

[0046] Permission: Access operations to system resources, such as read, write, delete, etc.

[0047] Session: An instance of a user's activity in the system. Each session can activate a portion of the user's roles.

[0048] System administrators define multiple roles based on organizational structure and business requirements, and each role corresponds to a set of permissions. Assign specific permission sets to corresponding roles. For example, the "Administrator" role may have read and write permissions for all resources, while the "Normal User" role may only have read permissions. Assign users to corresponding roles, and each user can have one or more roles. When a user tries to access a resource, the system first checks whether the user's role has the corresponding permissions. Only users who meet the permission requirements can perform the operation.

[0049] ABAC is an attribute-based access control model that determines access rights through a combination of user attributes, resource attributes, and environment attributes. ABAC mainly includes the following core attributes: User Attributes: Describes the user's characteristic information, such as position, department, qualifications, etc.

[0050] Resource Attributes: Describes the characteristic information of resources, such as resource type, data sensitivity level, etc.

[0051] Environment Attributes: Describes the characteristic information of the access environment, such as access time and access location.

[0052] Policy: Access control rules defined based on attributes that determine whether a user has access to resources.

[0053] System administrators define user attributes, resource attributes, and environment attributes. User attributes can include positions (manager, employee), departments (finance department, technical department), etc.; resource attributes can include data types (financial data, technical documents), etc.; environment attributes can include access time (working hours, non-working hours), etc. Based on the defined attributes, set access control policies. When a user issues an access request, the system dynamically evaluates the user attributes, resource attributes, and environment attributes to determine whether the set access control policies are met. Based on the evaluation results, the system makes permission decisions to determine whether to allow the user to access or operate.

[0054] like Figure 3 As shown in the figure, the ABAC model implementation architecture mainly includes the following four components: Attribute Service Interface Policy Management Module Policy Evaluation Engine Logging Module The attribute service interface provides services for obtaining user attributes, resource attributes, and environmental attributes to ensure the real-time and accuracy of attribute data. Obtain user-related attributes (including position, department, role, etc.) from the user database or identity management system. Obtain resource-related attributes (brain-wide resource type, data sensitivity level, etc.) from the resource management system. Obtain access environment-related attributes (including access time, access location, device type, etc.) from the environmental monitoring system. The attribute service interface needs to be integrated with external systems (user database, resource management system, environmental monitoring system, etc.) and provide an API interface for the policy evaluation engine to call. Attribute data is maintained by combining scheduled refresh and real-time query to ensure that the data is up-to-date and accurate.

[0055] The policy management module provides the functions of policy definition, editing, storage and management, and supports dynamic update and priority management of policies. The policy editor provides a user interface and API for administrators to define and edit ABAC policy rules. The policy storage stores defined policy rules and supports version control and history management of policies. The policy management interface provides an operation interface for adding, deleting, modifying and querying policies, which can be called by the policy engine and other systems. Policy rules are defined and stored using JSON. The policy management component needs to support dynamic loading and updating of policies to ensure that new policies can take effect in a timely manner.

[0056] The policy evaluation engine parses and executes ABAC policy rules, dynamically evaluates access requests and makes permission decisions. The rule parser is used to parse policy rules from storage format to internal data structures for easy execution by the policy evaluation engine. The attribute matcher is used to match the corresponding policy rules according to the attribute information of the access request. Finally, the decision generator generates permission decisions based on the matching results and passes the decision results to the data access control module.

[0057] The logging module records the user's access behavior and permission decision process, and provides audit and tracking functions. It includes access logger and decision logger. The logger records each user's access request, including request time, user identity, access resource, request type and other information. The decision logger records the detailed process of policy evaluation and permission decision, including the evaluated policy, matching attributes, evaluation results and other information. It supports efficient log query and audit report generation.

[0058] The RBAC model implementation architecture mainly includes the following four components: Figure 4 As shown: User Management Interface Role Management Component Policy Evaluation Engine Logging Module The user management interface provides functions such as user registration, login, and password management. Common authentication protocols (OAuth, SAML) are integrated to ensure the authenticity of the user's identity. After the authentication is passed, a user identity token is generated for subsequent access control.

[0059] The role management component defines and manages roles and their permission sets, and assigns user roles. It provides services to the outside world through different interfaces. The role definition interface provides the definition and editing functions of roles. The permission management interface manages the relationship between roles and permissions. The user role assignment interface assigns roles to users and supports multi-role assignment. Roles and their permission sets are stored in the role database in a structured format Json. It supports dynamic creation, modification, and deletion of roles.

[0060] The Policy Evaluation Engine parses and executes RBAC policies, and performs permission evaluation and decision making on user requests. The Role Parser parses role definitions and permission sets from storage formats into internal data structures. The Permission Checker checks whether the user has the corresponding permissions based on the user role and requested operation. The Decision Generator generates permission decisions based on the permission check results.

[0061] The logging module records the user's access behavior and permission decision-making process, and provides audit and tracking functions. The access log recorder records each user's access request, including request time, user identity, access resources, request type and other information. The decision log recorder records the detailed process of policy evaluation and permission decision-making, including information such as the evaluated policy, matching attributes, and evaluation results. The log storage stores access logs and decision logs, and supports efficient log query and audit report generation. The logging component provides an API interface for the policy evaluation engine to call and record the evaluation and decision-making process. It supports compressed storage and archiving management of logs to ensure efficient storage and long-term preservation of log data. Integrate anomaly detection and alarm mechanisms to identify and alarm abnormal access and permission abuse.

[0062] In the data access control module, the data access control module is responsible for executing the permission decisions generated by the policy evaluation engine and controlling the actual access of users to data. This module ensures that only authorized users can access and operate data.

[0063] It mainly includes two components: access controller and resource manager. The access controller is mainly responsible for allowing or denying user access requests based on the permission decision of the policy evaluation engine. First, it receives the permission decision generated by the policy evaluation engine, and then verifies whether the user request meets the permission decision result. If the permission verification passes, the request is allowed to enter the request processor. If the permission verification fails, the request is rejected and a corresponding rejection log is generated. The resource manager stores metadata information of all resources, provides resource query and update interfaces, and supports dynamic management of resources. It also maintains the ACL information of each resource, provides ACL query and update interfaces, and ensures the real-time and accuracy of ACL information. The process is as follows: The user sends an access request through the system interface, which contains user identity information and access resource information.

[0064] The access controller's permission validator receives the permission decision from the policy evaluation engine and verifies the legitimacy of the user's request.

[0065] If the permission verification passes, the request processor performs the corresponding read and write operations.

[0066] If permission verification fails, the access controller denies the request and logs the denial.

[0067] The resource manager maintains the metadata and ACL information of resources to ensure the real-time and accuracy of resource access control.

[0068] The audit module is responsible for recording all access behaviors and permission decision-making processes in the system, and provides detailed logging and analysis functions to facilitate auditing, tracking, and security monitoring.

[0069] The audit module mainly relies on logging. It is divided into access logging and decision logging. The access logging format is as follows: Timestamp: The time when the request is recorded.

[0070] User ID: The identity of the user making the request.

[0071] Resource ID: The resource identifier for the requested access.

[0072] Operation Type: The type of operation requested, such as read, write, delete, etc.

[0073] Request Status: The processing status of the request, such as success, failure, etc.

[0074] The decision log record format is as follows: Timestamp: The time when the evaluation is recorded.

[0075] User ID: The identity of the user making the request.

[0076] Policy ID: The policy identifier of the application.

[0077] Evaluation Result: The result of the permission evaluation, such as allow, deny, etc.

[0078] Attributes: Attribute information involved in the evaluation.

[0079] The main core point of the audit module is log analysis. This embodiment proposes a log analyzer for analyzing log data. The process includes log collection, log processing, log storage, compliance inspection, log analysis, and audit report generation. Figure 5 shown.

[0080] The log analyzer extracts the latest access logs and decision logs from the log storage through a scheduled task. The logs are then processed to remove redundant and noisy data, and the log data is converted to XML format for subsequent analysis. The data is then aggregated based on the time series, the user's access interval and resource heat are calculated, and the user role and identity are converted to numerical representation using one-hot encoding. The processed log data is stored in the analysis database to support efficient query and analysis. BigID is then used to identify personal sensitive information in the log data, and the effectiveness of data anonymization is verified, and data access policies are formulated to ensure that only authorized personnel can access the log data. In the data analysis stage, Pandas and NumPy are used to aggregate and statistically analyze the log data, and the number of visits and operation type distribution per hour are calculated. Scikit-learn is used for pattern recognition and anomaly detection to identify abnormal access behavior. Tableau is used to generate a visual chart of access frequency and operation type distribution. Finally, JasperReports is used to generate a detailed audit report containing key indicators, compliance analysis results, and anomaly detection results.

[0081] In this embodiment, smart contracts play a key role in the data usage negotiation process, ensuring the efficiency and credibility of the negotiation process through their automation, transparency, and security features.

[0082] The entire negotiation process can be divided into the initialization stage, the negotiation request stage, the contract determination and response stage, the contract achievement stage, and the contract verification stage.

[0083] In the initial stage of the data usage negotiation process, data users and data providers are initialized and prepare the information and resources required for negotiation. Data users (Data Consumer) and data providers (Data Provider) deploy their own smart contracts to record the initial status of both parties. Smart contracts include: Identity information of both parties, the identification code (ID) of the data user and the data provider; Trust level: predefined trust levels (such as normal, trust, and trust+) that indicate the credibility and trust between the two parties; Negotiation parameters include data type, data volume, purpose of use, time limit and other specific parameters required for negotiation.

[0084] In the negotiation request phase of the data usage negotiation process, the data user generates a data usage contract and initiates a negotiation request. The smart contract automatically processes these requests and performs preliminary verification. The data user generates a data usage contract (including data usage conditions, permissions, etc.) by calling the smart contract method createContractRequest and triggers the ContractRequestMessage event. The smart contract automatically records this request and stores it on the blockchain to ensure the transparency and immutability of the request. The data provider listens to and receives the data usage negotiation request, evaluates the data contract and responds. The data provider's smart contract listens to the ContractRequestMessage event and evaluates the contract request through the method evaluateContractRequest (including verifying the requester's identity, usage conditions, etc.). After confirming the contract request, the data provider calls the smart contract method createContractOffer to generate a contract response (ContractOfferMessage) and broadcasts it to the blockchain network.

[0085] In the contract confirmation and response phase, the data user evaluates the contract response, confirms the contract, and generates a contract acceptance agreement. The data user's smart contract listens to the ContractOfferMessage event and evaluates the contract response through the evaluateContractOffer method. After confirming the contract, the data user calls the smart contract method acceptContractOffer to generate a contract acceptance agreement (ContractNegotiationEventMessage) and triggers the ContractAgreementMessage event.

[0086] In the contract reaching stage, both parties accept the negotiation content and the data use contract is reached. The data provider's smart contract listens to the ContractAgreementMessage event and confirms the contract is reached through the method finalizeContract. The smart contract records the final state of the negotiation on the blockchain and marks it as an agreement (AGREED).

[0087] After the contract is reached, it enters the contract verification phase, where both parties verify the contract through the smart contract to ensure the execution of the contract terms. Both parties verify the contract by calling the smart contract method verifyContractAgreement, triggering the ContractAgreementVerificationMessage event. The smart contract records the verification results and updates the contract status on the blockchain to Verified (VERIFIED).

[0088] Negotiations are tracked through a series of states, and each state change is automatically handled by the smart contract and recorded through the blockchain. Negotiation states include INITIALIZED, REQUESTED, OFFERED, ACCEPTED, AGREED, VERIFIED, FINALIZED, and TERMINATED. The smart contract method updateNegotiationState is responsible for updating the state and triggering corresponding events (such as ContractNegotiationEventMessage). Both parties automatically track state changes through smart contracts to ensure transparency and consistency of the negotiation process. The overall process is as follows: Figure 6 shown.

[0089] The ContractRequestMessage message format is as follows:

[0090]

[0091] JSON example: { "RequestID": "REQ123456789", "ConsumerID": "CONSUMER001", "ProviderID": "PROVIDER001", "RequestTimestamp": "2024-07-04T10:00:00Z", "ContractType": "DataUsageContract", "ConsumerInfo": { "ConsumerName": "John Doe", "ConsumerRole": "Researcher", "ConsumerTrustLevel": "trust+" }, "DataUsageDetails": { "DataDescription": "Dataset on climate change research", "UsagePurpose": "Academic research", "UsageDuration": "2024-07-04 to 2024-12-31", "UsageFrequency": "multiple", "UsageLocation": "University of XYZ, Research Lab" }, "DataControlPolicy": { "WhoCanUse": "John Doe, Research Team A", "WhenToUse": { "TriggerTime": "2024-07-05T00:00:00Z", "TimeCycle": "Daily from 09:00 to 17:00", "TimeRange": "2024-07-04 to 2024-12-31" }, "HowToUse": "ClimateDataAnalysisApp", "WhereToUse": { "PhysicalLocation": "USA, New York, University of XYZ", "ServerEnvironment": "Linux, AWS Cloud" }, "UsageCount": 100, "UsageActions": ["view", "download", "edit", "notify"] }, "DataSecurityAndPrivacy": { "DataEncryption": "AES-256", "AccessControl": "Role-based access control", "AuditTrail": "Enabled" }, "ContractTerms": { "TermsAndConditions": "Data must be used strictly for academicresearch. Redistribution is prohibited.", "AdditionalNotes": "Data access is subject to periodic review andaudit." } } ContractOfferMessage

[0092]

[0093] { "OfferID": "OFF123456789", "RequestID": "REQ123456789", "ProviderID": "PROVIDER001", "ConsumerID": "CONSUMER001", "OfferTimestamp": "2024-07-04T12:00:00Z", "ContractType": "DataUsageContract", "ProviderInfo": { "ProviderName": "Data Provider Corp", "ProviderRole": "Data Provider", "ProviderTrustLevel": "trust+" }, "DataUsageConditions": { "DataDescription": "Climate change research dataset", "UsagePurpose": "Academic research only", "UsageDuration": "2024-07-04 to 2024-12-31", "UsageFrequency": "multiple", "UsageLocation": "University of XYZ, Research Lab" }, "DataControlPolicy": { "WhoCanUse": "John Doe, Research Team A", "WhenToUse": { "TriggerTime": "2024-07-05T00:00:00Z", "TimeCycle": "Daily from 09:00 to 17:00", "TimeRange": "2024-07-04 to 2024-12-31" }, "HowToUse": "ClimateDataAnalysisApp", "WhereToUse": { "PhysicalLocation": "USA, New York, University of XYZ", "ServerEnvironment": "Linux, AWS Cloud" }, "UsageCount": 100, "UsageActions": ["view", "download", "edit", "notify"] }, "DataSecurityAndPrivacy": { "DataEncryption": "AES-256", "AccessControl": "Role-based access control", "AuditTrail": "Enabled" }, "ContractTerms": { "TermsAndConditions": "Data must be used strictly for academic research. Redistribution is prohibited.", "AdditionalNotes": "Data access is subject to periodic review and audit." } } ContractNegotiationEventMessage:

[0094] The JSON format is as follows: { "EventID": "EVT123456789", "NegotiationID": "NEG123456789", "OfferID": "OFF123456789", "RequestID": "REQ123456789", "ProviderID": "PROVIDER001", "ConsumerID": "CONSUMER001", "Timestamp": "2024-07-04T16:00:00Z", "EventDetails": { "EventType": "StateChange", "CurrentState": "OFFERED", "PreviousState": "REQUESTED", "EventDescription": "The provider has offered new terms for the data usage contract.", "EventDetails": { "ProposedTerms": { "UsageDuration": "2024-07-04 to 2025-06-30", "UsageCount": 200 }, "Notes": "Provider agrees to extend the usage duration and increase usage count." } }, "Signatures": { "ProviderSignature": "0xProviderSignatureHash", "ConsumerSignature": "0xConsumerSignatureHash", "VerificationHash": "0xVerificationHash" } } ContractAgreementMessage:

[0095]

[0096] The JSON format is as follows: { "AgreementID": "AGM123456789", "NegotiationID": "NEG123456789", "OfferID": "OFF123456789", "RequestID": "REQ123456789", "ProviderID": "PROVIDER001", "ConsumerID": "CONSUMER001", "Timestamp": "2024-07-04T18:00:00Z", "AgreementTerms": { "DataDescription": "Climate change research dataset", "UsagePurpose": "Academic research only", "UsageDuration": "2024-07-04 to 2025-06-30", "UsageFrequency": "multiple", "UsageLocation": "University of XYZ, Research Lab", "UsageCount": 200, "UsageActions": ["view", "download", "edit", "notify"] }, "DataSecurityAndPrivacy": { "DataEncryption": "AES-256", "AccessControl": "Role-based access control", "AuditTrail": "Enabled" }, "AdditionalNotes": "Data access is subject to periodic review andaudit.", "Signatures": { "ProviderSignature": "0xProviderSignatureHash", "ConsumerSignature": "0xConsumerSignatureHash", "VerificationHash": "0xVerificationHash" } } ContractAgreementVerificationMessage message:

[0097]

[0098] The JSON format is as follows: { "VerificationID": "VER123456789", "AgreementID": "AGM123456789", "NegotiationID": "NEG123456789", "OfferID": "OFF123456789", "RequestID": "REQ123456789", "ProviderID": "PROVIDER001", "ConsumerID": "CONSUMER001", "Timestamp": "2024-07-04T20:00:00Z", "VerificationStatus": "Approved", "VerificationDetails": "Agreement terms have been verified and approved.", "VerificationReason": "All terms and conditions meet the specified requirements.", "VerifiedAgreementTerms": { "DataDescription": "Climate change research dataset", "UsagePurpose": "Academic research only", "UsageDuration": "2024-07-04 to 2025-06-30", "UsageFrequency": "multiple", "UsageLocation": "University of XYZ, Research Lab", "UsageCount": 200, "UsageActions": ["view", "download", "edit", "notify"] }, "Signatures": { "VerifierSignature": "0xVerifierSignatureHash", "ProviderSignature": "0xProviderSignatureHash", "ConsumerSignature": "0xConsumerSignatureHash", "VerificationHash": "0xVerificationHash" } } This embodiment also includes an electronic device and a storage medium. An electronic device includes a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, each step in the data usage control negotiation method for data space infrastructure is implemented. A storage medium stores a computer program on it. When the computer program is executed by the processor, each step in the data usage control negotiation method for data space infrastructure is implemented.

[0099] This invention uses smart contracts to automate and make data usage negotiations transparent, ensuring the security and credibility of data during sharing and usage. Through detailed technical implementation, it demonstrates the specific operation and state management of smart contracts at each negotiation stage, providing strong support for the healthy development of the data sharing ecosystem.

[0100] 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 combining 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.) containing computer-usable program codes. The schemes in the embodiments of the present application may be implemented in various computer languages, for example, object-oriented programming language Java and literal scripting language JavaScript, etc.

[0101] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes 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 generate 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.

[0102] 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.

[0103] 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 A step that specifies a function in one or more boxes.

[0104] Although the preferred embodiments of the present application have been described, those skilled in the art may make other changes and modifications to these embodiments once they have learned the basic creative concept. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and all changes and modifications falling within the scope of the present application.

[0105] Obviously, those skilled in the art can make various changes and modifications to the present application without departing from the spirit and scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to include these modifications and variations.

Claims

1. A data usage control negotiation method for data space infrastructure, characterized in that: The following steps are involved: Use the OAuth authentication protocol to authenticate user requests; Conduct authority evaluation and decision making on the verified user identity information; Executive authority assessment and decision-making outcomes; Based on the execution results, the data provider negotiates with the data user; Generate log query and audit reports.

2. The data usage control negotiation method for data space infrastructure according to claim 1, characterized in that: In the process of evaluating and deciding the permissions of the verified user identity information, the RBAC model and ABAC model are used to control the permissions of user roles, attributes, resource attributes, and environmental attributes.

3. The data usage control negotiation method for data space infrastructure according to claim 2, characterized in that: The negotiation process between data providers and data users is as follows: Data users and data providers are initialized separately, prepare the information and resources required for negotiation, deploy their respective smart contracts, and record the initial status of both parties; The data user generates a data usage contract and initiates a negotiation request. The smart contract automatically processes the negotiation request and performs preliminary verification. The data user evaluates the contract response and confirms the contract, generating a contract acceptance agreement; The data user and data provider accept the negotiation content and reach a data use contract; Data users and data providers verify the contract through smart contracts to ensure the execution of the contract terms.

4. A data usage control negotiation system for data space infrastructure, characterized in that: include: The identity authentication module is used to authenticate user requests using the OAuth authentication protocol; The policy engine module is used to evaluate and make decisions on the permissions of authenticated user identity information; Data access control module, used to perform permission evaluation and decision results; A negotiation module is used for the data provider and the data user to negotiate based on the execution results; Audit module, used to generate log queries and audit reports.

5. The data usage control negotiation system for data space infrastructure according to claim 4, characterized in that: In the process of evaluating and deciding the permissions of the verified user identity information in the policy engine module, the RBAC model and the ABAC model are comprehensively used to control the permissions of user roles, attributes, resource attributes, and environmental attributes.

6. The data usage control negotiation system for data space infrastructure according to claim 5, characterized in that: The negotiation process between the data provider and the data user in the negotiation module is as follows: Data users and data providers are initialized separately, prepare the information and resources required for negotiation, deploy their respective smart contracts, and record the initial status of both parties; The data user generates a data usage contract and initiates a negotiation request. The smart contract automatically processes the negotiation request and performs preliminary verification. The data user evaluates the contract response and confirms the contract, generating a contract acceptance agreement; The data user and data provider accept the negotiation content and reach a data use contract; Data users and data providers verify the contract through smart contracts to ensure the execution of the contract terms.

7. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, each step of the data usage control negotiation method for data space infrastructure as described in any one of claims 1 to 3 is implemented.

8. A storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, each step of the data usage control negotiation method for data space infrastructure as described in any one of claims 1 to 3 is implemented.

Citation Information

Patent Citations

  • Cross-domain access control method and system based on multi-block chain

    CN117424747A

  • Progress, quality and cost integrated management and control system based on BIM and block chain

    CN118378953A

  • Telecom node control via blockchain

    WO2019215040A1

Cited By

  • Data full life cycle use control method, system, device, medium and program

    CN121211481A

  • Data lifecycle control method, system, device, medium and program

    CN121211481B

  • Cross-industry data sharing method and system supporting dynamic policy negotiation

    CN121750666A

  • A cross-industry data sharing method and system supporting dynamic policy negotiation

    CN121750666B