A method, system, device, and medium for cross-domain dynamic trust level adjustment
By using multi-dimensional trust assessment and quantum security technology, the trust value and permissions of cross-domain nodes are dynamically calculated, which solves the problems of static level fixation and insufficient security in cross-domain node trust management, and realizes precise trust management and efficient access control.
Patent Information
- Application Number
- CN202611294997.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-08-25
- Publication Date
- 2026-11-17
AI Technical Summary
In existing technologies, cross-domain node trust management suffers from problems such as static and fixed levels, single evaluation dimensions, weak security protection, and poor scenario adaptability, which cannot meet the needs of dynamic, accurate, and highly secure trust management.
By combining multi-dimensional trust assessment data (historical behavior, real-time status, scenario risk, and cross-domain distance) with a four-dimensional assessment model, the trust value is dynamically calculated. The trust level and permissions are managed in a closed loop through smart contracts, and quantum security technology is used to ensure the security of data transmission and assessment.
It improves the accuracy and scenario adaptability of trust assessment, realizes closed-loop management of trust levels and permissions, and enhances the security and management efficiency of cross-domain collaboration.
Smart Images

Figure CN123122914A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of blockchain technology, and in particular to a method, system, device, and medium for cross-domain dynamic trust level adjustment. Background Technology
[0002] With the increasing prevalence of cross-domain collaboration in consortium blockchains (government data sharing, cross-domain financial settlement, and industrial internet collaboration), cross-domain node trust management has become a bottleneck. Traditional solutions generally adopt static trust levels: a fixed level is assigned when a node joins the network and remains unchanged for a long time, which cannot match the dynamic changes in node behavior, risk scenarios, and network environment.
[0003] Current mainstream solutions mainly fall into three categories, all of which suffer from the following technical defects: Static role assignment: Administrators preset fixed roles (ordinary / trusted / super node) without dynamic adjustment; relies on traditional encryption (TLS / ECC) without quantum security protection; permissions are simply enabled / disabled, without fine-grained control.
[0004] Single-dimensional trust assessment: Trust value is calculated only based on historical transaction compliance rate, without considering real-time status, scenario risks, or cross-domain distance; the update cycle is long (≥1 hour), resulting in delayed response; there is no anti-tampering mechanism, and the assessment data is easily tampered with.
[0005] Centralized dynamic adjustment: Relies on third-party nodes for unified calculation and distribution of trust levels, which poses a single point of failure and tampering risk; the adjustment rules are fixed and cannot adapt to different scenarios such as sensitive data sharing and ordinary queries. Data transmission uses traditional HTTPS, which is vulnerable to eavesdropping.
[0006] Meanwhile, with the rapid development of quantum computing, traditional signatures (ECC / RSA) are easily cracked, and trust credentials and evaluation data are vulnerable to quantum attacks, tampering, and forgery. In summary, existing solutions are static, limited in scope, lack security, have poor scenario adaptability, and are disconnected from trust permissions, failing to meet the dynamic, accurate, and highly secure trust management needs of cross-domain collaboration. Summary of the Invention
[0007] The technical problem to be solved by this invention is to provide a method, system, device and medium for cross-domain dynamic trust level adjustment, so as to solve the technical problems of static and fixed trust levels that cannot be dynamically adjusted, single evaluation dimension and low accuracy, weak security protection and the risk of quantum attack, fixed rules and poor adaptability to scenarios, and disconnect between trust and permissions and the lack of closed-loop management.
[0008] The technical solution of the present invention to solve the above-mentioned technical problems is as follows: In a first aspect, the present invention provides a method for cross-domain dynamic trust level adjustment, comprising: Obtain multi-dimensional trust assessment data for cross-domain nodes, wherein the multi-dimensional trust assessment data includes historical behavior data, real-time status data, scenario risk data, and cross-domain distance data; Based on the multi-dimensional trust assessment data and the preset four-dimensional assessment model, the trust value of the cross-domain node is calculated. The four-dimensional assessment model assigns corresponding weights to the historical behavior data, the real-time status data, the scenario risk data, and the cross-domain distance data, and performs a weighted summation. The trust level of the cross-domain node is determined based on the trust value and the scenario rules corresponding to the current cross-domain collaboration scenario. Different scenario rules correspond to different weight configurations, trust level thresholds, and update cycles.
[0009] Based on the above technical solution, the present invention can be further improved as follows.
[0010] Furthermore, the acquisition of multi-dimensional trust assessment data for cross-domain nodes includes: Obtain historical behavior data of the cross-domain node, wherein the historical behavior data includes at least one of transaction compliance rate, number of abnormal behaviors, trust level maintenance duration, and cross-domain collaboration completion rate; Obtain the real-time status data of the cross-domain node, wherein the real-time status data includes at least one of processor utilization, memory utilization, network latency, and online status of security modules; Obtain scenario risk data for the cross-domain nodes, wherein the scenario risk data includes at least one of the following: collaboration scenario type, data sensitivity level, and number of collaboration participating nodes; Obtain cross-domain distance data of the cross-domain node, wherein the cross-domain distance data includes at least one of geographical distance and network link type.
[0011] Furthermore, the calculation of the trust value of the cross-domain node based on the multi-dimensional trust assessment data and the preset four-dimensional assessment model includes: The historical behavior data, the real-time status data, the scenario risk data, and the cross-domain distance data are standardized respectively to obtain the standardized scores corresponding to each dimension. Based on the weights corresponding to each dimension, the standardized scores corresponding to each dimension are weighted and summed to obtain the trust value.
[0012] Furthermore, the standardization processing of the historical behavior data, the real-time status data, the scenario risk data, and the cross-domain distance data includes: For positive indicators, the standardized score of the positive indicator is determined based on the ratio of the actual value to the optimal value of the positive indicator. For negative indicators, the standardized score of the negative indicator is determined based on the ratio of the actual value of the negative indicator to the maximum allowable value.
[0013] Furthermore, determining the trust level of the cross-domain node based on the trust value and the scenario rules corresponding to the current cross-domain collaboration scenario includes: Identify the scenario type of the current cross-domain collaboration scenario; Match the scene rules corresponding to the scene type from the scene rule base, wherein the scene rules include weight configuration, trust level threshold and update cycle; The trust level of the cross-domain node is determined based on the trust value and the trust level threshold in the scenario rules.
[0014] Furthermore, the scenario rules are configured in the following way: Receive a scenario rule configuration request, wherein the scenario rule configuration request includes weight configuration information, trust level threshold information, and update cycle information; Perform integrity verification on the configured scenario rules; When the integrity verification passes, the scenario rule is stored in the scenario rule base.
[0015] Furthermore, based on the trust level, permission allocation or permission revocation operations are automatically executed via smart contracts; When the trust level is upgraded, the smart contract automatically performs a permission allocation operation to grant the cross-domain node new operation permissions corresponding to the upgraded trust level. When the trust level drops, the smart contract automatically performs a permission revocation operation to reclaim the excess operation permissions of the cross-domain node that do not correspond to the dropped trust level.
[0016] Secondly, the present invention provides a cross-domain dynamic trust level adjustment system, comprising: The multi-dimensional data acquisition module acquires multi-dimensional trust assessment data of cross-domain nodes, wherein the multi-dimensional trust assessment data includes historical behavior data, real-time status data, scenario risk data, and cross-domain distance data; The four-dimensional evaluation model module calculates the trust value of the cross-domain node based on the multi-dimensional trust evaluation data and the preset four-dimensional evaluation model. The four-dimensional evaluation model assigns corresponding weights to the historical behavior data, the real-time status data, the scenario risk data, and the cross-domain distance data, and performs a weighted summation. The trust level confirmation module determines the trust level of the cross-domain node based on the trust value and the scenario rules corresponding to the current cross-domain collaboration scenario. Different scenario rules correspond to different weight configurations, trust level thresholds, and update cycles. The permission closed-loop layer module automatically performs permission allocation or permission revocation operations through smart contracts based on the trust level.
[0017] Thirdly, the present invention provides a computer device, comprising: Memory and processor; The memory is used to store computer-executable instructions, and the processor is used to execute the computer-executable instructions, which, when executed by the processor, implement the steps of a cross-domain dynamic trust level adjustment method.
[0018] Fourthly, the present invention provides a computer-readable storage medium storing computer-executable instructions that, when executed by a processor, implement the steps of the cross-domain dynamic trust level adjustment method.
[0019] The advantages of this invention over the prior art are as follows: First, by acquiring four types of multi-dimensional trust assessment data—historical behavior data, real-time status data, scenario risk data, and cross-domain distance data—and calculating the trust value based on a weighted summation of the four-dimensional assessment model, compared to existing technologies that only assess based on a single dimension of historical transaction behavior, this approach can comprehensively consider the multi-dimensional characteristics of nodes, improve the accuracy of trust assessment, and avoid misjudgments.
[0020] Second, by determining the trust level based on the trust value and the scenario rules corresponding to the current cross-domain collaboration scenario, different scenario rules correspond to different weight configurations, trust level thresholds and update cycles. Compared with the existing technology that uses fixed adjustment rules, it can flexibly adapt to the differentiated needs of different cross-domain scenarios and improve scenario adaptability.
[0021] Third, by using smart contracts to automatically perform permission allocation or revocation operations based on trust levels, closed-loop management of trust levels and operation permissions can be achieved. Compared with existing technologies where trust levels and permissions are disconnected and permission changes require manual intervention, this can form a strongly constrained closed-loop control and improve management efficiency. Attached Figure Description
[0022] Figure 1 This is a flowchart illustrating a cross-domain dynamic trust level adjustment method. Figure 2 A flowchart illustrating the data collection process for a cross-domain dynamic trust level adjustment method; Figure 3 A flowchart of a four-dimensional dynamic evaluation model for a cross-domain dynamic trust level adjustment method; Figure 4 A flowchart for evaluating data protection in a cross-domain dynamic trust level adjustment method; Figure 5A flowchart illustrating a scenario-based dynamic adjustment strategy for a cross-domain dynamic trust level adjustment method; Figure 6 A flowchart illustrating the mapping relationship of a cross-domain dynamic trust level adjustment method; Figure 7 This is a schematic diagram of the electronic device of the present invention. Detailed Implementation
[0023] The technical solutions of the embodiments of the present invention will be described below with reference to the accompanying drawings. In the description of the present invention, unless otherwise stated, " / " indicates that the objects before and after are in an "or" relationship. For example, A / B can represent A or B. The "or" in the present invention is merely a description of the relationship between the related objects, indicating that three relationships can exist. For example, A or B can represent: A alone, A and B simultaneously, and B alone. A and B can be singular or plural. Furthermore, in the description of the present invention, unless otherwise stated, "multiple" refers to two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items.
[0024] Furthermore, to facilitate a clear description of the technical solutions of the embodiments of the present invention, the terms "first" and "second" are used in the embodiments of the present invention to distinguish identical or similar items with essentially the same function and effect. Those skilled in the art will understand that the terms "first" and "second" do not limit the quantity or execution order, and that the terms "first" and "second" are not necessarily different.
[0025] In this embodiment of the invention, the terms "exemplary" or "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design described as "exemplary" or "for example" in this embodiment of the invention should not be construed as superior or more advantageous than other embodiments or designs. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner for ease of understanding.
[0026] Example 1, an embodiment of the present invention, provides a cross-domain dynamic trust level adjustment system. This system adopts a four-layer architecture: a quantum security foundation, a dynamic evaluation core, a scenario adaptation interface, and a permission closed-loop layer. Each layer is independently decoupled and works collaboratively to achieve the core objectives of quantum security, multi-dimensional evaluation, scenario adaptation, and permission closed-loop. The architecture is as follows: Figure 1 As shown, it includes: The quantum-secure foundation layer provides underlying security support for the entire trust assessment system, employing quantum-level encryption and signature technologies to build end-to-end quantum-secure protection capabilities. Assessment data is transmitted through a quantum-secure channel, and quantum signatures are used to record trust level adjustments and assess data for tamper-proof documentation. Quantum hashing technology is used to verify data integrity, effectively resisting quantum computing attacks, data tampering, and forgery risks, ensuring the security and reliability of the entire trust assessment process.
[0027] The dynamic assessment core layer is the core execution layer, comprising four core modules: a multi-dimensional data acquisition module, a four-dimensional assessment model module, a level confirmation module, and a dynamic adjustment decision module. This enables accurate calculation and real-time adjustment of trust levels. The multi-dimensional data acquisition module collects four types of data in real time: historical node behavior, real-time status, scenario risk, and cross-domain distance, with a collection cycle of ≤1 second to ensure data timeliness. The four-dimensional assessment model module calculates trust values based on preset weights, ranging from 0 to 100 points, and supports dynamic weight configuration. The level confirmation module performs quantum hash verification and quantum signature encryption on the collected data to ensure data integrity and security. The dynamic adjustment decision module automatically adjusts the trust level (five levels: A / B / C / D / E) based on the trust value and scenario rules, triggering permission updates.
[0028] The multi-dimensional data acquisition module acquires multi-dimensional trust assessment data of cross-domain nodes, wherein the multi-dimensional trust assessment data includes historical behavior data, real-time status data, scenario risk data, and cross-domain distance data; The four-dimensional evaluation model module calculates the trust value of the cross-domain node based on the multi-dimensional trust evaluation data and the preset four-dimensional evaluation model. The four-dimensional evaluation model assigns corresponding weights to the historical behavior data, the real-time status data, the scenario risk data, and the cross-domain distance data, and performs a weighted summation. The trust level confirmation module determines the trust level of the cross-domain node based on the trust value and the scenario rules corresponding to the current cross-domain collaboration scenario. Different scenario rules correspond to different weight configurations, trust level thresholds, and update cycles. The permission closed-loop layer module automatically performs permission allocation or permission revocation operations through smart contracts based on the trust level.
[0029] The scenario adaptation interface layer provides a standardized scenario rule configuration interface, supporting alliance nodes to customize trust level adjustment rules. It includes a scenario rule management module, a rule verification module, and a rule switching module. The scenario rule management module supports creating / editing / deleting scenario rules (such as sensitive data sharing rules and ordinary data query rules); the rule verification module uses quantum hashing to verify rule integrity and prevent rule tampering. The rule switching module supports automatic / manual rule switching based on cross-domain scenarios, with a switching response time of ≤500ms.
[0030] The permission closed-loop layer implements deep binding of trust levels and permissions, including a permission mapping module, a smart contract auto-execution module, and a permission revokement module. The permission mapping module presets the mapping relationship between trust levels and operation permissions (e.g., level A nodes can read sensitive data, while level B nodes can only read ordinary data). The smart contract auto-execution module executes permission allocation / revokement in real time after the trust level is adjusted, with a response time ≤100ms. Permission revokement...
[0031] Example 2, a second embodiment of the present invention, provides a cross-domain dynamic trust level adjustment method, including: S1: Obtain multi-dimensional trust assessment data for cross-domain nodes, wherein the multi-dimensional trust assessment data includes historical behavior data, real-time status data, scenario risk data, and cross-domain distance data.
[0032] like Figure 2 As shown, in step S1, the multi-dimensional data acquisition module is responsible for collecting four types of core data in real time to provide input for the four-dimensional evaluation model. All collected data are transmitted through a quantum-secure channel to ensure timeliness and security.
[0033] Historical behavioral data (30% weight). Collected metrics include transaction compliance rate over the past 72 hours, number of abnormal behaviors, trust level maintenance duration, and cross-domain collaboration completion rate. On-chain data is synchronized in real-time via the consortium blockchain ledger API, aggregated every 10 seconds, and outliers (such as response timeouts due to network fluctuations) are removed.
[0034] Data example: Transaction compliance rate = 98.5%, number of abnormal behaviors = 1, trust level maintenance duration = 48 hours, collaboration completion rate = 99.2%.
[0035] Real-time status data (25% weight). Collected metrics include CPU utilization, memory utilization, network latency, and the online status of the quantum-safe module. A data collection agent is deployed locally on each node, collecting data every second and uploading it to the evaluation node via a QKD quantum-safe channel with encryption.
[0036] Example data: CPU utilization = 35%, memory utilization = 42%, network latency = 28ms, quantum security module online status = normal.
[0037] Scenario risk data (30% weight): The collected indicators include the type of cross-domain collaboration scenario (sensitive data sharing / ordinary data query / transaction endorsement), data sensitivity level (level 1-5), and the number of participating nodes in the collaboration; the node initiating the cross-domain collaboration uploads the scenario information through a smart contract, and the evaluation node verifies the authenticity of the information through quantum signature.
[0038] Data example: Scenario type = sensitive data sharing, data sensitivity level = level 5, number of participating nodes = 12.
[0039] Cross-domain distance data (15% weight). Collected metrics include cross-domain node geographical distance (located via IP address) and network link type (leased line / public network / 5G); node locations are obtained by calling third-party geolocation APIs, and geographical distances are calculated; link types are identified using network detection tools.
[0040] Data example: Geographical distance = 350km, Link type = Leased line.
[0041] Data preprocessing and anomaly filtering: Data standardization: Mapping data of different dimensions to a score range of 0-100, using the following formula: Positive metrics (such as compliance rate): Standardized score = (actual value / optimal value) × 100; Negative indicators (such as the number of anomalies): Standardized score = (1 - actual value / maximum allowable value) × 100; Outlier filtering: The 3σ principle is used to remove outlier data (such as a sudden increase in CPU utilization caused by a network attack), and outlier data is replaced with the average of the last 5 collections; Encrypted data storage: The preprocessed data is generated into a feature code using quantum hashing and stored in a distributed database along with the original data. The feature code is used for subsequent integrity verification.
[0042] The cross-domain collaboration scenario involves sharing sensitive government data. Node A participates in the collaboration, and the data collection and preprocessing process is as follows: Historical behavioral data collection: Transaction compliance rate = 99.1% (standardized score = 99.1), number of abnormal behaviors = 0 (score = 100), trust level maintenance duration = 72 hours (score = 100), collaboration completion rate = 99.5% (score = 99.5), average standardized score = 99.7 points; Real-time status data acquisition: CPU utilization = 28% (score = 92), memory utilization = 35% (score = 95), network latency = 22ms (score = 96), quantum module online (score = 100), average standardized score = 95.75; Scenario risk data collection: Scenario type = sensitive data sharing (score = 80), data sensitivity = level 5 (score = 70), participating nodes = 15 (score = 85), average standardized score = 78.33; Cross-domain distance data collection: Geographic distance = 280km (score = 90), Link type = Leased line (score = 100), Average standardized score = 95; Anomaly filtering: No abnormal data is found. The preprocessed data is stored using quantum hash encryption.
[0043] S2: Based on the multi-dimensional trust assessment data and the preset four-dimensional assessment model, calculate the trust value of the cross-domain node, wherein the four-dimensional assessment model assigns corresponding weights to the historical behavior data, the real-time status data, the scenario risk data and the cross-domain distance data and performs a weighted summation.
[0044] Existing technologies only employ a single dimension for evaluation, resulting in insufficient accuracy. This application's embodiments utilize a four-dimensional dynamic evaluation model, calculating trust values through weighted summation. This model supports dynamic weight configuration and adapts to different cross-domain scenario requirements, such as... Figure 3 As shown: The default weight allocation is shown in Table 1. Alliance nodes can adjust the weights through smart contract proposals (requiring the consent of ≥2 / 3 of the nodes).
[0045] Table 1 The Trust Value calculation formula is as follows: The Trust Value is calculated using a weighted summation formula, and the result is rounded to one decimal place, ranging from 0 to 100. TrustValue=(H×0.3)+(R×0.25)+(S×0.3)+(D×0.15) Where: H represents the average standardized score of historical behavior data (0-100 points); R represents the average standardized score of real-time status data (0-100 points); S represents the average standardized score of scenario risk data (0-100 points); and D represents the average standardized score of cross-domain distance data (0-100 points).
[0046] The trust level classification rules are as follows: five levels: A / B / C / D / E. The level is strongly bound to the permissions. The classification rules can be dynamically adjusted through the scenario adaptation interface, as shown in Table 2.
[0047] Table 2 The default real-time update cycle is once every 10 seconds for the trust value, and it supports scenario-based configuration (5 seconds / time for sensitive scenarios, 30 seconds / time for ordinary scenarios). When a node exhibits abnormal behavior (such as malicious proposals or data tampering), an update is triggered immediately, and the trust value is lowered in real time. The change in trust value is ≤5 points / time to avoid frequent switching of trust levels due to data fluctuations, which could affect system stability.
[0048] Based on the preprocessed scores across all dimensions, calculate the trust value and level of node A: Trust Value Calculation: TrustValue = (99.7 × 0.3) + (95.75 × 0.25) + (78.33 × 0.3) + (95 × 0.15) = 29.91 + 23.9375 + 23.499 + 14.25 = 91.5965 ≈ 91.6 points The trust level score is 91.6, which falls within the 90-100 score range, and is therefore classified as Level A. Node A has the authority to read sensitive data, initiate cross-domain collaboration, endorse transactions, and deploy smart contracts, and can participate in all cross-domain scenarios.
[0049] S3: Determine the trust level of the cross-domain node based on the trust value and the scenario rules corresponding to the current cross-domain collaboration scenario. Different scenario rules correspond to different weight configurations, trust level thresholds, and update cycles.
[0050] Current technologies lack quantum security protection, making trusted data vulnerable to tampering and eavesdropping. By employing triple protection—quantum signatures, quantum hashes, and quantum secure channels—we ensure the security of evaluation data throughout the entire process. Figure 4 As shown.
[0051] After multi-dimensional data collection is completed, the evaluation node calls the Dilithium-3 variant quantum signature algorithm to sign the original data and preprocessing results, generating a quantum signature value (size ≤ 2.5KB). The quantum signature value and the data feature code (quantum hash result) are written into the consortium blockchain ledger to form an immutable evidence record with an on-chain latency of ≤ 500ms. Other nodes can verify the signature validity through the evaluation node's public key with a verification time of ≤ 10ms, ensuring that the data has not been tampered with.
[0052] Quantum-secure channel establishment: Cross-domain nodes and evaluation nodes complete QKD key distribution through the BB84 protocol to generate a shared key pool (key length 256 bits), and the channel establishment time is ≤3 seconds; One-time encrypted transmission: Before each transmission of evaluation data, a 128-bit key is randomly selected from the key pool as the session key. The data is encrypted using AES-256-GCM. The session key is used only once and is destroyed immediately after the transmission is completed. Transmission integrity verification: A quantum hash signature is appended to the end of the transmitted data. The receiver verifies the consistency of the signature to ensure that the data has not been eavesdropped on or tampered with.
[0053] Rule Feature Code Generation: After the scenario rules are configured, the quantum feature code (256 bits) of the rule file is calculated using the quantum hash algorithm, and the feature code is stored together with the rule file; Rule call verification: Before each trust level adjustment, the quantum feature code of the rule file is recalculated and compared with the stored feature code. If they do not match, it is determined that the rule has been tampered with, the adjustment process is immediately paused and an alarm is triggered. Rule update signature: When modifying scenario rules, at least 2 / 3 of the alliance nodes must confirm the changes via quantum signature to ensure the legality of the rule adjustments.
[0054] Node B participates in a cross-domain general data query scenario; evaluate the data processing flow: Data signature: After the evaluation node collects data from node B, it generates a quantum signature value 0xqsign123... and calculates the quantum feature code 0xqhash456...; Secure transmission: Data, signatures, and feature codes are encrypted using a one-time session key via a QKD quantum secure channel and transmitted to all network nodes; Signature verification: The receiving node verifies the signature using the evaluation node's public key. After successful verification, it compares the signature with the signature code to confirm data integrity. Rule verification: Call the rules for ordinary data query scenarios, recalculate the rule feature code, and if it matches the stored value, the rule is valid and the trust level is adjusted.
[0055] Existing technologies employ fixed adjustment strategies, resulting in poor scenario adaptability. This application's embodiments design a scenario-based dynamic adjustment strategy, supporting custom rule customization and automatic switching, such as... Figure 5 As shown.
[0056] As shown in Table 3, three basic scenario rules are preset, and alliance nodes can customize and extend them (up to 10 scenarios are supported).
[0057] Table 3 Automatic rule switching mechanism: Scene recognition: The current scene is identified by parsing the scene type identifier (such as scene:sensitive_data) of the cross-domain collaboration initiator through smart contracts; Rule matching: Match the corresponding adjustment rule from the scene rule library, with a matching time of ≤100ms; Rule execution: Automatically load the matching weight configuration, level threshold, and update cycle, and perform trust level adjustment.
[0058] Trust level adjustment trigger conditions: Timed trigger: The adjustment is automatically triggered according to the preset update cycle (5 seconds / 30 seconds / 60 seconds) of the scenario rules; Event triggering: The event is triggered immediately when a specific event occurs on the node (such as abnormal behavior, quantum security module going offline, scene switching). Manual Trigger: Alliance administrators can manually trigger the trust level adjustment of a specific node through quantum signature authorization (only for emergency handling).
[0059] Trust Level Adjustment Process: Triggered Adjustment: Once the triggering conditions are met, the dynamic adjustment decision module initiates the adjustment process; Data reassessment: The four-dimensional assessment model is invoked to calculate the trust value based on the latest collected data; Trust Level Determination: Determine a new trust level based on the threshold values of the current scenario rules; Permission synchronization: Synchronize the new trust level to the permission closed-loop layer and perform permission allocation / revocation; Results announcement: The adjustment results (including changes in trust value, level, and permissions) will be announced on the blockchain after being verified by quantum signature, with a delay of ≤1 second.
[0060] Node C's initial trust level is B (82 points). Its participation in cross-domain scenarios has been switched from "normal data query" to "sensitive data sharing," and the process has been adjusted as follows: Scene recognition: The smart contract parses the scene identifier scene:sensitive_data and identifies it as a sensitive data sharing scene; Rule matching: Load rules for sensitive data sharing scenarios (weight 35% / 25% / 30% / 10%, level threshold A≥90, B≥85, C≥70, update cycle 5 seconds); Data reassessment: Node C's latest trust value is calculated to be 83 points; Level determination: 83 points < 85 points (threshold for Level B in sensitive scenarios), determined as Level C; Permission revocation: The permission closed-loop layer automatically revoks the "read sensitive data" permission, while retaining the "read ordinary data, participate in cross-domain collaboration" permissions; Results Announcement: The adjustment results will be announced on the blockchain and updated synchronously across all nodes on the network.
[0061] S4: Based on the trust level, automatically execute permission allocation or revocation operations via smart contracts to achieve closed-loop management of trust levels and operation permissions.
[0062] Existing technologies lack a clear connection between trust levels and permissions. Smart contracts can be used to automatically bind and synchronize "trust levels" and "permissions" in real time, forming a closed-loop constraint. Figure 6 As shown.
[0063] The mapping relationship between the preset trust level and operation permission is set, and the permission type can be dynamically expanded through smart contracts, as shown in Table 4.
[0064] Table 4 Smart contract automatic execution process: Permission allocation: When the trust level is upgraded (e.g., C level → B level), the smart contract automatically executes the grantPermission function to grant the new permission (e.g., endorsement transaction), with an execution time of ≤100ms; Permission revocation: When the trust level decreases (e.g., from B to C), the smart contract automatically executes the revokePermission function to revoke excess permissions (e.g., endorsement transactions), with an execution time of ≤100ms; Permission Freeze: When the trust level drops to E, the smart contract executes the freezeAccount function, freezing all node operation permissions and prohibiting the initiation / participation of cross-domain collaboration; Permission restoration: When the trust value of an E-level node is increased to D level or above, the smart contract executes the unfreezeAccount function to restore the corresponding permissions.
[0065] Permission operation auditing and traceability: Audit log generation: Every permission assignment / revocation / freeze / restore operation generates an audit log, which includes the operation time, triggering reason, execution result, and quantum signature; Log on-chain evidence storage: Audit logs are written to the consortium blockchain ledger, which is tamper-proof and traceable for ≥90 days; Abnormal permission alert: When the permission operation does not match the trust level adjustment (such as a C-level node obtaining sensitive data read permission), a quantum security alert is immediately triggered to notify the alliance administrator.
[0066] Node D's trust level is upgraded from C (75 points) to B (82 points). The permission execution process is as follows: Level update trigger: The dynamic adjustment decision module updates node D's level to level B and synchronizes it to the smart contract; Permission allocation: The smart contract executes the grantPermission function, granting node D the "endorsement transaction" permission; Log generation: Generate audit log {Time: 202X-XX X:X:X, Node DID:did:qdtl:xxx, Operation: Grant endorsement transaction permission, Trigger reason: Trust level C→B, Signature: 0xqsign...}; Logs on the blockchain: Audit logs are written to the consortium blockchain to complete the evidence storage; Permission verification: When node D initiates an endorsement transaction, the smart contract verifies its B-level permissions, and executes the transaction after successful verification.
[0067] The overall execution flow of the Cross-Domain Dynamic Trust Level (DTL) adjustment method consists of six steps: data collection, quantum-secure processing, four-dimensional assessment, dynamic adjustment, permission closure, and log storage. It provides full-link quantum-secure coverage, forming a closed loop, as detailed below: Data Acquisition: The multi-dimensional data acquisition module collects historical behavior, real-time status, scenario risks, and cross-domain distance data in real time, with an acquisition cycle of ≤1 second; Quantum-secure processing: The evaluation data is transmitted through a quantum-secure channel and securely verified using quantum signatures and quantum hashes. Four-dimensional assessment: Calculates a trust value based on preset weights, ranging from 0 to 100 points, with an update cycle of ≤30 seconds; Dynamic adjustment: Automatically match and adjust strategies according to scenario rules, determine trust level (A / B / C / D / E), and adjust response time ≤1 second; Permission closed loop: Smart contracts execute permission allocation / revocation in real time, with permission response time ≤100ms; Log storage: Adjustment results and permission operation logs are stored on the blockchain for evidence, supporting 90-day traceability.
[0068] Example 3: In some embodiments, the cross-domain dynamic trust level adjustment system of the present invention can be implemented in a combination of hardware and software. As an example, the cross-domain dynamic trust level adjustment system of the present invention can be a processor in the form of a hardware decoding processor, which is programmed to execute the cross-domain dynamic trust level adjustment method of the present invention. For example, the processor in the form of a hardware decoding processor can be one or more application-specific integrated circuits (ASICs), DSPs, programmable logic devices (PLDs), complex programmable logic devices (CPLDs), field-programmable gate arrays (FPGAs), or other electronic components.
[0069] The modules described in the embodiments of this invention can be implemented in software or hardware. The names of the modules are not, in some cases, limiting the scope of the module itself.
[0070] An electronic device according to an embodiment of the present invention 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, it implements any of the aforementioned cross-domain dynamic trust level adjustment methods. That is, an electronic device according to an embodiment of the present invention may include, but is not limited to: a processor and a memory; the memory is used to store the computer program; the processor is used to execute a cross-domain dynamic trust level adjustment method shown in any embodiment of the present invention by calling the computer program.
[0071] In one alternative embodiment, an electronic device is provided, such as Figure 7 As shown, Figure 7The illustrated electronic device 4000 includes a processor 4001 and a memory 4003. The processor 4001 and the memory 4003 are connected, for example, via a bus 4002. Optionally, the electronic device 4000 may further include a transceiver 4004, which can be used for data interaction between the electronic device and other electronic devices, such as sending and / or receiving data. It should be noted that in practical applications, the transceiver 4004 is not limited to one type, and the structure of the electronic device 4000 does not constitute a limitation on the embodiments of the present invention.
[0072] Processor 4001 may be a CPU (Central Processing Unit), a general-purpose processor, a DSP (Digital Signal Processor), an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute the various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this invention. Processor 4001 may also be a combination that implements computational functions, such as including one or more microprocessor combinations, a combination of a DSP and a microprocessor, etc.
[0073] Bus 4002 may include a path for transmitting information between the aforementioned components. Bus 4002 may be a PCI (Peripheral Component Interconnect) bus or an EISA (Extended Industry Standard Architecture) bus, etc. Bus 4002 can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 7 The bus 4002 is represented by only one thick line, but this does not mean that there is only one bus or one type of bus.
[0074] The memory 4003 may be ROM (Read Only Memory) or other types of static storage devices capable of storing static information and instructions, RAM (Random Access Memory) or other types of dynamic storage devices capable of storing information and instructions, or EEPROM (Electrically Erasable Programmable Read Only Memory), CD-ROM (Compact Disc Read Only Memory) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but not limited thereto.
[0075] The memory 4003 stores application code (computer program) for executing the present invention, and its execution is controlled by the processor 4001. The processor 4001 executes the application code stored in the memory 4003 to implement the content shown in the foregoing method embodiments.
[0076] Among them, electronic devices can also be terminal devices, which can be any device that can install applications, including at least one of smartphones, tablets, laptops, desktop computers, smart speakers, smartwatches, smart TVs, and smart in-vehicle devices.
[0077] It should be noted that, Figure 7 The electronic device shown is merely an example and should not be construed as limiting the functionality and scope of the embodiments of the present invention.
[0078] An embodiment of the present invention provides a computer-readable storage medium storing a computer program, which, when executed by a processor, implements any of the above-described cross-domain dynamic trust level adjustment methods.
[0079] Alternatively, the computer-readable storage medium may be a read-only memory (ROM), a random access memory (RAM), a compact disc read-only memory (CD-ROM), magnetic tape, a floppy disk, and an optical data storage device, etc.
[0080] In an exemplary embodiment, a computer program product or computer program is also provided, which includes computer instructions stored in a computer-readable storage medium. A processor of an electronic device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the electronic device to perform the aforementioned cross-domain dynamic trust level adjustment method.
[0081] Computer program code for performing the operations of this invention can be written in one or more programming languages or a combination thereof, including object-oriented programming languages such as Java, Smalltalk, and C++, and conventional procedural programming languages such as C or similar languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).
[0082] It should be understood that the flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of methods and computer program products according to various embodiments of the present invention. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.
[0083] The computer-readable storage medium provided in this invention can be, but is not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EEPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this invention, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device.
[0084] The aforementioned computer-readable storage medium carries one or more programs, which, when executed by the electronic device, cause the electronic device to perform the method shown in the above embodiments.
[0085] The above description is merely a preferred embodiment of the present invention and an explanation of the technical principles employed. Those skilled in the art should understand that the scope of disclosure in this invention is not limited to technical solutions formed by specific combinations of the above-described technical features, but should also cover other technical solutions formed by arbitrary combinations of the above-described technical features or their equivalents without departing from the above-disclosed concept. For example, technical solutions formed by substituting the above features with (but not limited to) technical features with similar functions disclosed in this invention.
[0086] It should be noted that the terms "first," "second," etc., used in the specification and claims of this application are used to distinguish similar objects and represent a limitation on a specific order or sequence. Where appropriate, the order of use for similar objects can be interchanged so that the embodiments of this application described herein can be implemented in an order other than that shown or described.
[0087] Those skilled in the art will recognize that this invention can be implemented as a system, method, or computer program product. Therefore, this invention can be specifically implemented in the following forms: it can be entirely hardware, entirely software (including firmware, resident software, microcode, etc.), or a combination of hardware and software, generally referred to herein as a "circuit," "module," or "system." Furthermore, in some embodiments, this invention can also be implemented as a computer program product contained in one or more computer-readable media, which includes computer-readable program code.
[0088] Although embodiments of the present invention have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting the present invention. Those skilled in the art can make changes, modifications, substitutions and variations to the above embodiments within the scope of the present invention.
Claims
1. A method for cross-domain dynamic trust level adjustment, characterized in that, include: Obtain multi-dimensional trust assessment data for cross-domain nodes, wherein the multi-dimensional trust assessment data includes historical behavior data, real-time status data, scenario risk data, and cross-domain distance data; Based on the multi-dimensional trust assessment data and the preset four-dimensional assessment model, the trust value of the cross-domain node is calculated. The four-dimensional assessment model assigns corresponding weights to the historical behavior data, the real-time status data, the scenario risk data, and the cross-domain distance data, and performs a weighted summation. The trust level of the cross-domain node is determined based on the trust value and the scenario rules corresponding to the current cross-domain collaboration scenario. Different scenario rules correspond to different weight configurations, trust level thresholds, and update cycles.
2. The method for cross-domain dynamic trust level adjustment according to claim 1, characterized in that, The acquisition of multi-dimensional trust assessment data for cross-domain nodes includes: Obtain historical behavior data of the cross-domain node, wherein the historical behavior data includes at least one of transaction compliance rate, number of abnormal behaviors, trust level maintenance duration, and cross-domain collaboration completion rate; Obtain the real-time status data of the cross-domain node, wherein the real-time status data includes at least one of processor utilization, memory utilization, network latency, and online status of security modules; Obtain scenario risk data for the cross-domain nodes, wherein the scenario risk data includes at least one of the following: collaboration scenario type, data sensitivity level, and number of collaboration participating nodes; Obtain cross-domain distance data of the cross-domain node, wherein the cross-domain distance data includes at least one of geographical distance and network link type.
3. The method for cross-domain dynamic trust level adjustment according to claim 1, characterized in that, The process of calculating the trust value of the cross-domain node based on the multi-dimensional trust assessment data and the preset four-dimensional assessment model includes: The historical behavior data, the real-time status data, the scenario risk data, and the cross-domain distance data are standardized respectively to obtain the standardized scores corresponding to each dimension. Based on the weights corresponding to each dimension, the standardized scores corresponding to each dimension are weighted and summed to obtain the trust value.
4. The method for cross-domain dynamic trust level adjustment according to claim 3, characterized in that, The standardization processing of the historical behavior data, the real-time status data, the scenario risk data, and the cross-domain distance data includes: For positive indicators, the standardized score of the positive indicator is determined based on the ratio of the actual value to the optimal value of the positive indicator. For negative indicators, the standardized score of the negative indicator is determined based on the ratio of the actual value of the negative indicator to the maximum allowable value.
5. The method for cross-domain dynamic trust level adjustment according to claim 1, characterized in that, The step of determining the trust level of the cross-domain node based on the trust value and the scenario rules corresponding to the current cross-domain collaboration scenario includes: Identify the scenario type of the current cross-domain collaboration scenario; Match the scene rules corresponding to the scene type from the scene rule base, wherein the scene rules include weight configuration, trust level threshold and update cycle; The trust level of the cross-domain node is determined based on the trust value and the trust level threshold in the scenario rules.
6. The method for cross-domain dynamic trust level adjustment according to claim 5, characterized in that, The scenario rules are configured in the following way: Receive a scenario rule configuration request, wherein the scenario rule configuration request includes weight configuration information, trust level threshold information, and update cycle information; Perform integrity verification on the configured scenario rules; When the integrity verification passes, the scenario rule is stored in the scenario rule base.
7. The method for cross-domain dynamic trust level adjustment according to claim 1, characterized in that, Based on the trust level, the smart contract automatically performs permission allocation or permission revocation operations. When the trust level is upgraded, the smart contract automatically performs a permission allocation operation to grant the cross-domain node new operation permissions corresponding to the upgraded trust level. When the trust level drops, the smart contract automatically performs a permission revocation operation to reclaim the excess operation permissions of the cross-domain node that do not correspond to the dropped trust level.
8. A cross-domain dynamic trust level adjustment system, using the method described in any one of claims 1-7, characterized in that, include: The multi-dimensional data acquisition module acquires multi-dimensional trust assessment data of cross-domain nodes, wherein the multi-dimensional trust assessment data includes historical behavior data, real-time status data, scenario risk data, and cross-domain distance data; The four-dimensional evaluation model module calculates the trust value of the cross-domain node based on the multi-dimensional trust evaluation data and the preset four-dimensional evaluation model. The four-dimensional evaluation model assigns corresponding weights to the historical behavior data, the real-time status data, the scenario risk data, and the cross-domain distance data, and performs a weighted summation. The trust level confirmation module determines the trust level of the cross-domain node based on the trust value and the scenario rules corresponding to the current cross-domain collaboration scenario. Different scenario rules correspond to different weight configurations, trust level thresholds, and update cycles. The permission closed-loop layer module automatically performs permission allocation or permission revocation operations through smart contracts based on the trust level.
9. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 7.
10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 7.
