Data asset life cycle driven archiving control method in combination with ownership

Abstract

The invention relates to the technical field of data asset management, in particular to an ownership-combined data asset life cycle driven filing control method, which comprises the following steps of: extracting ownership entities of target data assets and a dependency relationship between the entities from a distributed permission log, generating a topological ownership relation chain comprising ownership hierarchy depth and a comprehensive authority attenuation coefficient; calculating a dynamic archiving weight value based on the ownership level depth and the authority attenuation coefficient in combination with the current life cycle stage of the data assets; and migrating the data assets to a low-cost storage domain meeting compliance requirements of most ownership entities according to entity regional distribution characteristics in the ownership relation chain. Compared with a traditional scheme that filing judgment is carried out only according to the static permission state of the current owner, the method can recognize potential risks in historical chains such as multi-layer transfer authorization, permission shrinkage and timeliness weakening.

Description

Technical Field

[0001] This invention relates to the field of data asset management technology, and in particular to a data asset lifecycle-driven archiving control method that combines ownership relationships. Background Technology

[0002] With the widespread deployment of big data, cloud computing, and multi-organizational collaborative business, the lifecycle management of data assets in distributed systems has gradually become a core issue in information governance. This is particularly true in industries with high data compliance requirements, such as finance, energy, and manufacturing. Ensuring business continuity while achieving on-demand archiving, compliant migration, and low-cost storage has become a key challenge for data operations and maintenance. Existing data archiving solutions primarily rely on lifecycle stage identifiers (such as active / inactive) or access frequency statistics to determine whether data has entered the archiving period.

[0003] However, this static determination method has the following technical limitations: It is impossible to capture the evolution of ownership under complex organizational structures. Data assets are often authorized and re-authorized at multiple levels between headquarters, subsidiaries, and partners. Existing solutions only record the current owner's permission status, making it difficult to identify compliance risks and weakened control issues hidden in historical authorization paths.

[0004] Ignoring the dynamic changes in the validity of the access control chain, in practical applications, permissions may be reduced, revoked, or expire, but the system cannot detect whether the permissions are still valid. This causes some invalid but not updated control chains to continue to affect the data, creating archiving blind spots.

[0005] Poor handling of geographic compliance can easily lead to invalidation of archiving compliance or increased storage costs. Data sovereignty regulations require data storage to comply with the relevant regulations of the geographic regions where the majority of ownership entities reside. Existing solutions often store all data in a single, highly compliant geographic region, neglecting fine-grained aggregation judgments and cost optimization strategies for geographic compliance, resulting in unnecessary waste of resources. Summary of the Invention

[0006] This invention provides a data asset lifecycle-driven archiving control method that combines ownership relationships with dynamic archiving control methods that integrate ownership relationship topology, permission evolution rules and lifecycle driving factors, so as to achieve intelligent archiving judgment and risk-controlled migration throughout the entire data lifecycle.

[0007] The data asset lifecycle-driven archiving control method, which combines ownership relationships, includes the following steps: S1, extract the ownership entities and inter-entity dependencies of the target data asset from the distributed permission log, and generate a topological ownership relationship chain including ownership hierarchy depth and comprehensive permission decay coefficient; S2, Based on the ownership hierarchy depth and permission decay coefficient, and combined with the current lifecycle stage of the data asset, calculate the dynamic archiving weight value; S3, when the dynamic archiving weight value exceeds the preset weight threshold, the data assets are migrated to a low-cost storage domain that meets the compliance requirements of most ownership entities, based on the geographical distribution characteristics of the entities in the ownership relationship chain.

[0008] Optionally, the extraction of the ownership entities and inter-entity dependencies of the target data asset from the distributed permission log specifically includes: S11, Extract the original ownership record of the target data asset from the permission logs of the blockchain evidence storage node or RBAC permission management system: The identity and registered region of the data creator; The digital certificates of the initiator and recipient of the authorization operation, and the authorization timestamp; The transaction hash value for privilege revoke or transfer; S12: Using the data creator as the root node and the authorization operation as the directed edge, construct the dependency path of the ownership entity, that is, the dependency relationship between entities; calculate the length of the longest path from the root node to the last-level ownership entity as the ownership hierarchy depth.

[0009] Optionally, the generation of the comprehensive privilege attenuation coefficient includes: Parse the permission scope description field of each authorized operation and calculate the basic decay factor; calculate the time decay factor based on the difference between the authorized timestamp and the current time. The combined attenuation values ​​are used to obtain the comprehensive authority attenuation coefficient, which is expressed as: Comprehensive authority attenuation coefficient = basic attenuation factor × fa + time attenuation factor × fb, where fa and fb are weighting factors; The basic attenuation factor is calculated as follows: ;in, Indicates the basic attenuation factor. This represents the set of permissions currently held by the entity. It represents the set of permissions possessed by its superior entity; The time decay factor is calculated as follows: ;in, Indicates the time decay factor. This represents the difference between the current time and the authorized timestamp. This indicates the maximum preset validity period of the authorization.

[0010] Optionally, S1 further includes topological ownership relationship chain encapsulation, specifically including encapsulating ownership hierarchy depth, permission decay coefficient and entity geographic attributes into structured data objects for output.

[0011] Optionally, the dynamic archiving weight value is calculated as follows: ; in, For dynamic archiving weight values, The hierarchy depth factor reflects the complexity of the organizational structure. This is the privilege decay factor, reflecting the degree of privilege invalidation. The lifecycle stages are coded to reflect the urgency of archiving at each stage. The lifecycle stages include the active stage, the archiving stage, and the destruction stage, and each stage is pre-coded. These are the weighting coefficients; The dynamic archiving weight value is used to determine whether to trigger an archiving operation, so as to achieve data migration control driven by multi-dimensional risk factors.

[0012] Optionally, the hierarchy depth factor is obtained by ownership hierarchy depth conversion. The hierarchy depth factor is used to reflect the nesting complexity of the target data asset in the organizational structure and is normalized by the ratio with a preset depth threshold to prevent extreme structures from causing weight distortion in archiving decisions.

[0013] Optionally, the permission decay factor is obtained by converting the comprehensive permission decay coefficient. The permission decay factor is adjusted in the dynamic archiving weight value in combination with the timeliness compensation coefficient determined by the time of the most recent permission change in the permission path. The timeliness compensation coefficient is used to enhance the response sensitivity to the historical change status of permissions.

[0014] Optionally, the lifecycle stage coding quantitatively characterizes the urgency of archiving the target data asset at its current stage. The coding value of the lifecycle stage has a gradient difference between the active period, the archiving period and the destruction period, and participates in the generation of dynamic archiving weight value as one of the weight factors to reflect the impact of phased compliance requirements on archiving control.

[0015] Optionally, S3 includes a weight threshold determination, monitoring whether the dynamic archiving weight value exceeds a preset weight threshold; if it does, archiving is triggered, specifically including: S31. Based on the geographical distribution characteristics of entities in the ownership relationship chain, select the storage domain that meets the compliance requirements of the majority of ownership entities. Extract the registration region code of all ownership entities in the ownership relationship chain, use the region code as the clustering region unit, count the proportion of ownership entities in each region unit, and merge the geographically adjacent and compliant regions. S32, calculate the lowest-cost compliant region that meets both conditions, including the region compliance condition and the region storage cost condition. If no single region meets the conditions, select the hybrid cloud region with the highest entity ratio that supports data sovereignty partitioned storage. S33, Migration Execution, migrates data assets to a low-cost storage partition in the selected storage domain.

[0016] Optionally, the migration execution includes: Pre-register data sovereignty credentials with the target storage domain; Data blocks are transmitted in segments with increasing depth of ownership hierarchy; Write access circuit breaker rules based on permission decay coefficients into the target domain.

[0017] The beneficial effects of this invention are: This invention, by constructing a topological ownership relationship chain and introducing two dimensions—ownership hierarchy depth and permission decay coefficient—comprehensively characterizes the control complexity and permission evolution path of data assets in a multi-level organizational authorization structure. Compared to traditional schemes that rely solely on the static permission status of the current owner for archiving decisions, this invention can identify potential risks in historical chains such as multi-level sub-authorization, permission reduction, and weakened timeliness.

[0018] This invention designs a dynamic archiving weight value model composed of a hierarchical depth factor, a permission decay factor, and a lifecycle stage encoding weight, and sets a preset weight threshold as an archiving judgment threshold, realizing a shift from a "rule-triggered" to a "risk quantification" driven archiving strategy. This mechanism introduces a timeliness compensation coefficient to identify implicit archiving risks in the permission chain where "changes have been made for a long time but permissions have become inactive," enhancing the system's adaptability and precision control capabilities.

[0019] This invention introduces a regional clustering compliance analysis mechanism during the archiving execution phase, supporting the merging and judgment of regional units compatible with the compliance system. It achieves parallel judgment of sovereign majority decision and cost constraints, resolving the conflict between multi-sovereign data ambiguity and high-cost compliance in traditional solutions. Simultaneously, it maps the permission decay coefficient to a multi-level access control policy and deploys an automatic circuit breaker mechanism in the target storage domain to proactively block access in abnormal, expired, or interrupted permission states. This forms a closed-loop control path from "archiving judgment → migration execution → access control," significantly improving compliance and security throughout the data lifecycle. Attached Figure Description

[0020] To more clearly illustrate the technical solutions in this invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only for this invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0021] Figure 1 This is a schematic diagram of the archiving control method according to an embodiment of the present invention; Figure 2 This is a schematic diagram illustrating data asset migration decision-making in an embodiment of the present invention. Detailed Implementation

[0022] The present invention will now be described in detail with reference to the accompanying drawings and specific embodiments. For some well-known technologies, those skilled in the art may also use other alternative methods to implement the invention. Moreover, the accompanying drawings are only for more specific description of the embodiments and are not intended to specifically limit the present invention.

[0023] like Figures 1-2 As shown, the data asset lifecycle-driven archiving control method, which combines ownership relationships, includes the following steps: S1 extracts the ownership entities and inter-entity dependencies of the target data asset from the distributed permission log, and generates a topological ownership relationship chain including ownership hierarchy depth and comprehensive permission decay coefficient.

[0024] S1 specifically includes the following steps: S11, Distributed Log Targeted Collection: Extracting the original ownership records of target data assets from the following two types of log systems: The blockchain evidence storage node logs collect the following fields: Txn hash: Represents an immutable transaction hash for permission transfer; Timestamp: Operation timestamp; Region info: The region where the creator registered.

[0025] The logs from the RBAC (Role-Based Access Control) permission management system include the following fields: Issuer ID and Receiver ID: Authorize the issuer and receiver identities; Perm range: Description of the permission range; Cert ID: Digital certificate identifier.

[0026] By integrating heterogeneous logs from multiple sources for targeted collection, the integrity and traceability of ownership chain data are ensured.

[0027] S12, Entity Dependency Modeling: The data asset creator is the root node. Each authorization operation is modeled as a directed edge. Construct a directed graph G=(V,E), where V is the set of ownership entities and E is the set of authorized operation paths.

[0028] Define the depth of ownership hierarchy: ;in, This represents the set of all authorized paths originating from the root node. Representing a path The number of edges (i.e., the number of authorization layers).

[0029] Example: A (Creator) The path length is 2, therefore .

[0030] Ownership level depth Defined as "the longest authorized path length from the data creator (root node) to the lowest-level ownership entity," its calculation method is based on graph structure modeling of the authorization operation chain. The right to use data assets is often transferred multiple times within an organization (e.g., headquarters → subsidiary → outsourcing provider) or externally (e.g., platform → third-party service provider). Each authorization forms a directed edge, constituting a true "authority inheritance chain." Path length represents the "depth of authorization transmission." In graph theory, the longest path length can be used to measure the maximum dependency depth between a node and other nodes. In this scenario, the path length naturally maps to the number of authorization "hops" experienced during the layer-by-layer transmission of permissions from the creator. The larger this number of hops, the more complex the ownership relationship of the data asset and the deeper the control chain. Unlike existing solutions that only count the number of entities with permissions, the longest path length reflects the vertical complexity of the permission transmission process, i.e., the "degree of nesting of the ownership chain," which better reflects the actual complexity of data ownership management.

[0031] The deeper the ownership hierarchy, the more likely the data has been used by multiple levels of authorization, and its ownership is no longer centralized. Archiving should be handled with care to avoid disrupting downstream authorization dependencies that have not yet expired. Therefore, the archiving threshold for this data should be increased in the archiving strategy. Multi-layered nested ownership structures are more prone to problems such as legacy permissions and ambiguous responsibilities in actual management, especially during organizational changes or compliance reviews. Therefore, High-value data should be considered priority for review or archiving. The deeper the ownership chain, the more geographical regions are involved. Determining the deepest level of dependencies through the longest path helps identify compliant geographical overlap areas for most ownership entities in S3, guiding storage location selection. This invention, by modeling ownership hierarchy depth as "longest path length," not only provides a quantifiable complexity metric but also introduces this metric into data archiving control scenarios for the first time, providing crucial support for dynamic archiving decisions and filling the gap in existing technologies regarding the lack of modeling for "ownership depth."

[0032] S13, Generation of permission decay coefficient: (1) Base attenuation factor (measures the degree of reduction in the scope of permissions): ; in, This represents the set of permissions currently possessed by the entity. It represents the set of permissions possessed by its parent entity.

[0033] (2) Time decay factor (measures the reduction in the validity of permissions): ;in, This represents the difference between the current time and the authorized timestamp. This indicates the maximum preset validity period of the authorization.

[0034] (3) Overall Permission Attenuation Coefficient : Example as follows: Superior permissions: {read, write, delete}, Current authorization: {read}, therefore ; The license is valid for 2 years, and has been used for 1.5 years, therefore... ; Overall attenuation coefficient: .

[0035] A base decay factor weight of 0.7 indicates that the reduction in the scope of permissions dominates the overall permission decay assessment. In other words, if an entity inherits only a small portion of the permissions from its parent, this "permission reduction" plays a decisive role in determining the entity's actual control over the data.

[0036] A weight of 0.3 (time decay factor) indicates that the "authorization duration" has a relatively small impact on the validity of permissions. However, it is still necessary to consider whether the authorization is close to expiration in order to prevent the appearance of false valid permissions that are actually about to expire.

[0037] In data asset lifecycle management, the scope of control is a more direct indicator of an entity's actual ability to manipulate data than the time factor. For example, if an entity inherits only "read-only" permissions, even if the authorization time is recent, its risk to the data is far less than that of an entity with "read, write, and delete" permissions whose authorization is nearing expiration. Therefore, the "width" of permissions is considered more valuable for archiving decisions than the "duration" of permissions.

[0038] If a high weight is given to the time decay factor, it may lead to a situation where "even if there is only one month left on the validity period, as long as the scope of permissions is complete, it is considered a strong dependency," which poses a risk in actual compliance operations. Setting it to 0.3 makes the time effect only an auxiliary decision-making factor.

[0039] S14, Topological Ownership Relationship Chain Encapsulation: Encapsulate the following three types of indicators into structured objects for direct use in subsequent steps: Depth of ownership hierarchy: ; Permission decay coefficient: ; Entity geographic attributes: ,in .

[0040] S2 calculates the dynamic archiving weight value based on the ownership hierarchy depth and permission decay coefficient, combined with the current lifecycle stage of the data asset.

[0041] S2 specifically includes the following steps: S21, Lifecycle Stage Coding: Mapping the current lifecycle stage of a data asset to a digital coded value. : The active period is encoded as 0.3; The archiving period code is 0.7; The destruction period code is 0.9; It has achieved a quantitative impact of "stage urgency" on archiving decisions.

[0042] This invention employs quantitative stage coding values ​​to reflect the urgency of data archiving at different lifecycle stages. The coding values ​​are set according to the following logic: Table 1. Coding Value Setting Comparison Table The above setting does not adopt the traditional "stage identifier = active / inactive (Boolean)" method, but reflects the stage urgency level through the gradient difference of the encoded value, thereby improving the sensitivity of the system's archiving decision.

[0043] The differences in coding values ​​at different stages reflect the business implications of the "lifecycle evolution" of data assets. For example, during the active period, data is used frequently, and erroneous archiving will affect business continuity, so the weight is low; during the destruction period, there is no need for access, and failure to archive or transfer data in a timely manner will violate regulatory requirements, so the weight is high.

[0044] This invention employs a "0.3–0.7–0.9" encoding mechanism, designed based on the differences in the driving forces for archiving at different stages of the data lifecycle. Compared to the Boolean state judgment of traditional solutions, it introduces continuous gradient features, integrating lifecycle urgency as a quantitative indicator into the archiving weight model, thereby improving the dynamic response capability to timeliness risks and compliance priorities. A coupled judgment mechanism with ownership information is formed: lifecycle factors are no longer treated in isolation, but participate in archiving judgment together with ownership hierarchy and permission decay coefficient, forming an archiving model that is more business-sensitive and compliance-flexible.

[0045] S22, Calculation of ownership impact factor: S221, Hierarchical depth factor calculation: ; It is the ownership hierarchy depth output by S1. It is a preset depth threshold used to limit the excessive impact caused by ultra-deep dependency chains.

[0046] For example: like ,but ; like ,but ; This invention is a graph-based ownership path modeling system. The ownership relationship chain is rooted at the data creator. Each authorization action constructs a directed edge, forming an authorization transfer graph with varying ownership hierarchy depth. The natural value is defined as the longest path length from the root node to the last node in the graph, reflecting the "maximum authorization nesting level". Since real-world systems may have complex authorization structures with multiple levels of subsidiaries, outsourcing companies, and partners, the path length varies greatly across different organizations. Directly using the original value would lead to an imbalance in the weighted model. Therefore, the depth value is normalized as described above: This can limit the maximum weight value to 1, ensuring the controllability of the subsequent weighted model; using a threshold Controlling the "maximum risk perception depth" prevents misjudgments in archiving due to excessively long chains. In most cross-organizational systems, the influence tends to become marginal after the ownership chain exceeds 5 levels (e.g., headquarters → region → branch → subsidiary → partner → end user). Therefore, setting... It is an empirical balance between compliance complexity and archiving requirements.

[0047] In this invention, the hierarchical depth factor The calculation reflects the "risk intensity" of the ownership structure complexity. The deeper the ownership structure, the more data controllers there are, and the higher the potential compliance risk. The hierarchy depth factor serves as a weight input, ensuring that the archiving system maintains high attention to data in deep authorization chains, effectively capturing compliance gaps in "redundant authorization" and "implicit inheritance." Without normalization, extremely nested structures (such as subsidiaries with more than 8 levels in a large group) can lead to abnormally high archiving weights, affecting stability. The above formula limits the maximum value using min(), ensuring the stability and fairness of the judgment. In scenarios such as group acquisitions, mergers, and splits, ownership levels change frequently; this hierarchy depth factor can quickly detect the restructuring of the authorization chain brought about by "deep expansion" and adjust the archiving strategy in a timely manner.

[0048] S222, Calculation of privilege attenuation factor: ;in, This is the privilege decay coefficient. It is the timeliness compensation coefficient, defined as: ; For the current time, The time of the most recent permission change. The preset monitoring period is 180 days.

[0049] Permission decay is multi-dimensional, not a single static value. Traditionally, the validity of permissions is judged solely by the "reduction of permission scope," such as whether it has been reduced from {read, write, delete} to {read}. However, this ignores another crucial dimension: the corrosive effect of time. For example, although a permission may not appear to have changed, its last authorization may have occurred many years ago. Such "long-unmaintained permissions" are actually weakened in terms of security and compliance. Therefore, this invention proposes combining the degree of permission reduction with the timeliness of permission changes to derive a "decay factor" that more closely reflects actual control.

[0050] The linear amplification mechanism reflects the concentration of risk in the "most recent change," when If the change in permissions is relatively large, it is considered a stable state and only a slight increase is given. If the permissions have just been revoked or downgraded (i.e. the change time is very close to the current time), it means that it is still in the "permission reconstruction period" and the potential conflict risk is the highest. Therefore, this time-sensitive impact is quantified by a linear compensation formula and an adjustment weight of 0.2 is set to ensure that it plays an auxiliary and enhancing role in the total weight and avoids the dominant imbalance.

[0051] This invention addresses the issue of "unpopular risks" in existing archiving strategies. A common problem is that "permissions may have been revoked, but the archiving system still perceives them as having strong control, leading to a lag in the archiving strategy." By using a time-based compensation factor, this invention identifies dependencies that are "although permissions exist, they are actually static," and promptly weakens their support for data retention, avoiding misjudgments. When permissions are recently contracted, transferred, or revoked, this permission decay factor immediately increases the archiving weight, facilitating the rapid archiving of data that is no longer under control, freeing up high-cost storage resources, and meeting the compliance requirement of "archiving immediately after permission revocation." Most traditional archiving systems lack a response mechanism for "historical permission events." This invention provides a lightweight, time-driven compensation method, which not only improves the accuracy of judgments but also achieves more sensitive archiving responses over time.

[0052] This forms a complementary protection mechanism with the hierarchical factor. 1. Hierarchical depth captures structural complexity risks; 2. The authority decay factor detects the risk of weakened control; 3. The collaboration of the two can establish a more granular basis for archiving judgments across multiple dimensions.

[0053] S23, Dynamic Archiving Weight Value The archive weight value is calculated by weighting three factors: ; in, The hierarchy depth factor reflects the complexity of the organizational structure. This is the privilege decay factor, reflecting the degree of privilege invalidation. The lifecycle stages are coded to reflect the urgency of archiving at each stage. Based on the above, the codes are: active stage is 0.3, archiving stage is 0.7, and destruction stage is 0.9.

[0054] The value varies between 0 and 1; the higher the value, the more likely the data should be included in the archiving process.

[0055] S3, when the dynamic archiving weight value exceeds the preset weight threshold, the data assets are migrated to a low-cost storage domain that meets the compliance requirements of most ownership entities, based on the geographical distribution characteristics of entities in the ownership relationship chain.

[0056] The preset weight threshold in S3 is 0.6, which is equivalent to about 60% of the total archive risk score, representing a medium to high risk level. This means that it will not easily trigger archives and can also identify potential risks in a timely manner.

[0057] If the setting is too low (such as 0.4), a large amount of data that "does not yet pose a substantial risk" will be archived, increasing storage and migration costs. If the setting is too high (such as 0.8), it will delay the archiving response of high-risk data, resulting in compliance delays and access risks. 0.6 serves as an empirical safety threshold, balancing timeliness and cost control. The dynamic archiving weight value is a weighted composite of the following three core factors: Hierarchy depth factor: Reflects the complexity of the data ownership structure. The deeper the hierarchy, the longer the data dependency path, the more entities involved, and the higher the compliance risk.

[0058] Permission decay factor: Reflects the degree of ineffectiveness of data control permissions. The more "reduced" the permissions or the closer they are to expiration, the more likely the data is no longer effectively controlled and is suitable for archiving.

[0059] Lifecycle stage coding: reflects the position of data in its lifecycle. Data in the archiving or destruction phase has a higher necessity for archiving.

[0060] Setting a preset weight threshold for archiving avoids the accidental archiving of active or sensitive data. Without threshold control, forcing the archiving process whenever the ownership chain becomes slightly complex or permissions are slightly weakened could lead to the erroneous archiving of active data, impacting business continuity, and premature archiving of data with valid but underestimated permissions, resulting in decreased data availability. By setting a preset weight threshold, the S3 archiving process is ensured to start only when multiple risk factors converge to a significant level. Therefore, S3 specifically includes the following steps: S31, Entity-based regional clustering analysis: S311, Extract the regional codes of each entity in the ownership relationship chain: ;in, Indicates the first The registered region of an entity.

[0061] S312, Statistical distribution ratio of entities by geographical code: ;in, Regional Unit The number of ownership entities within, This represents the total number of entities in the ownership relationship chain. Regional Unit The proportion of entities.

[0062] S313, Perform regional unit merging: Merge adjacent regions that meet the relevant regulatory system requirements; The merged regional cluster set is obtained .

[0063] S32, the majority decision-making process for selecting the storage domain is as follows: S321, for each merged region Determine whether the following conditions are met: Compliance majority vote conditions: That is, a geographical unit covering more than 60% of the ownership entities; Cost constraints: , Indicates the region Unit data storage cost To preset the cost threshold, the average unit cost curves formed by region and storage type (cold storage, warm storage, hybrid cloud) in the past archiving operations of enterprises or platforms are summarized, and the 70-80th percentile is extracted as the maximum acceptable cost threshold. This avoids extremely high-priced regions from entering the candidate set. Therefore, the value range is set to: 0.01 yuan / GB / day to 0.05 yuan / GB / day (or converted into monthly / annual storage fees). For high-density cold data archiving scenarios, the threshold is generally taken as the lower limit; for sensitive data or medium-temperature storage scenarios that require compliance protection, the threshold can be appropriately relaxed.

[0064] If at least one region meets both of the above conditions, select the region with the lowest storage cost as the archiving target region: , The final target archiving region.

[0065] S322, If the majority decision condition is not met in all regions, the hybrid cloud sovereignty partitioning strategy will be activated: Sensitive data is archived to the region with the highest proportion of entities. ; Non-sensitive data should be archived in the least costly and compliant region.

[0066] S33, Secure migration execution mechanism: Pre-registering data sovereignty credentials with the target domain, i.e., data sovereignty credential pre-registration: generating zero-knowledge proofs based on the ownership relationship chain to form an immutable data passport; registering sovereignty credentials with the target storage domain to ensure the legality and effectiveness of the migration.

[0067] Data blocks are encrypted in segments according to the increasing depth of the ownership hierarchy, i.e., segmented encryption transmission control: data is segmented according to the depth of the ownership hierarchy from shallow to deep; each segment is encrypted and transmitted in sequence to ensure path integrity and access security.

[0068] Inject access control rules triggered by permission decay coefficients: Map the permission decay coefficients to access control policies; deploy a circuit breaker mechanism in the target domain to immediately freeze access requests when the permission control chain abnormally decays or expires. (The permission decay coefficient is then used to...) The mapping is used to define multi-level access control states, as shown in the table below: Table 2 Multilevel Access Control Mapping Table The permission decay coefficient (S1 calculation) measures the degree to which the current data access permission is less effective than the original creator's authorization. The larger the value, the weaker the permission, the closer it is to expiration, or the more severely it is reduced. This invention uses it as a dynamic risk assessment indicator and introduces it into the access control logic to form a policy linkage.

[0069] This invention encompasses any substitutions, modifications, equivalent methods, and solutions made within the spirit and scope of this invention. To provide the public with a thorough understanding of this invention, specific details are described in detail in the following preferred embodiments; however, those skilled in the art will fully understand the invention even without these details. Furthermore, to avoid unnecessary misunderstanding of the essence of this invention, well-known methods, processes, procedures, components, and circuits are not described in detail.

[0070] The above description is only a preferred embodiment of the present invention. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the principle of the present invention, and these improvements and modifications should also be considered within the scope of protection of the present invention.

Claims

1. A data asset lifecycle-driven archiving control method that combines ownership relationships, characterized in that: Includes the following steps: S1, extract the ownership entities and inter-entity dependencies of the target data asset from the distributed permission log, and generate a topological ownership relationship chain including ownership hierarchy depth and comprehensive permission decay coefficient; S2, Based on the ownership hierarchy depth and permission decay coefficient, and combined with the current lifecycle stage of the data asset, calculate the dynamic archiving weight value; S3, when the dynamic archiving weight value exceeds the preset weight threshold, the data assets are migrated to a low-cost storage domain that meets the compliance requirements of most ownership entities, based on the geographical distribution characteristics of the entities in the ownership relationship chain.

2. The data asset lifecycle-driven archiving control method based on ownership relationships as described in claim 1, characterized in that, The extraction of the ownership entities and inter-entity dependencies of the target data assets from the distributed permission log specifically includes: S11, Extract the original ownership record of the target data asset from the permission logs of the blockchain evidence storage node or RBAC permission management system: The identity and registered region of the data creator; The digital certificates of the initiator and recipient of the authorization operation, and the authorization timestamp; The transaction hash value for privilege revoke or transfer; S12: Using the data creator as the root node and the authorization operation as the directed edge, construct the dependency path of the ownership entity, that is, the dependency relationship between entities; calculate the length of the longest path from the root node to the last-level ownership entity as the ownership hierarchy depth.

3. The data asset lifecycle-driven archiving control method based on ownership relationships as described in claim 2, characterized in that, The generation of the comprehensive privilege attenuation coefficient includes: Parse the permission scope description field of each authorized operation and calculate the basic decay factor; calculate the time decay factor based on the difference between the authorized timestamp and the current time. The combined attenuation values ​​are used to obtain the comprehensive authority attenuation coefficient, which is expressed as: Comprehensive authority attenuation coefficient = basic attenuation factor × fa + time attenuation factor × fb, where fa and fb are weighting factors; The basic attenuation factor is calculated as follows: ;in, Indicates the basic attenuation factor. This represents the set of permissions currently held by the entity. It represents the set of permissions possessed by its superior entity; The time decay factor is calculated as follows: ;in, Indicates the time decay factor. This represents the difference between the current time and the authorized timestamp. This indicates the maximum preset validity period of the authorization.

4. The data asset lifecycle-driven archiving control method based on ownership relationships as described in claim 3, characterized in that, S1 also includes topological ownership relationship chain encapsulation, specifically including encapsulating ownership hierarchy depth, permission decay coefficient and entity geographic attributes into structured data objects for output.

5. The data asset lifecycle-driven archiving control method based on ownership relationships according to claim 1, characterized in that, The dynamic archiving weight value is calculated as follows: ； in, For dynamic archiving weight values, The hierarchy depth factor reflects the complexity of the organizational structure. This is the privilege decay factor, reflecting the degree of privilege invalidation. The lifecycle stages are coded to reflect the urgency of archiving at each stage. The lifecycle stages include the active stage, the archiving stage, and the destruction stage, and each stage is pre-coded. These are the weighting coefficients; The dynamic archiving weight value is used to determine whether to trigger an archiving operation, so as to achieve data migration control driven by multi-dimensional risk factors.

6. The data asset lifecycle-driven archiving control method based on ownership relationships as described in claim 5, characterized in that, The hierarchical depth factor is obtained by ownership hierarchy depth conversion. The hierarchical depth factor is used to reflect the nesting complexity of the target data asset in the organizational structure. It is normalized by the ratio with the preset depth threshold to prevent extreme structures from causing weight distortion in archiving decisions.

7. The data asset lifecycle-driven archiving control method based on ownership relationships as described in claim 5, characterized in that, The permission decay factor is obtained by converting the comprehensive permission decay coefficient. The permission decay factor is adjusted in the dynamic archiving weight value by combining the timeliness compensation coefficient determined by the time of the most recent permission change in the permission path. The timeliness compensation coefficient is used to enhance the responsiveness to the historical change status of permissions.

8. The data asset lifecycle-driven archiving control method based on ownership relationships as described in claim 5, characterized in that, The lifecycle stage coding quantitatively characterizes the urgency of archiving the target data asset at its current stage. The coding value of the lifecycle stage has a gradient difference between the active period, the archiving period and the destruction period, and participates as one of the weight factors in the generation of dynamic archiving weight value, so as to reflect the impact of phased compliance requirements on archiving control.

9. The data asset lifecycle-driven archiving control method based on ownership relationships according to claim 1, characterized in that, S3 includes weight threshold determination, which monitors whether the dynamic archiving weight value exceeds a preset weight threshold. If it does, archiving is triggered, specifically including: S31. Based on the geographical distribution characteristics of entities in the ownership relationship chain, select the storage domain that meets the compliance requirements of the majority of ownership entities. Extract the registration region code of all ownership entities in the ownership relationship chain, use the region code as the clustering region unit, count the proportion of ownership entities in each region unit, and merge the geographically adjacent and compliant regions. S32, calculate the lowest-cost compliant region that meets both conditions, including the region compliance condition and the region storage cost condition. If no single region meets the conditions, select the hybrid cloud region with the highest entity ratio that supports data sovereignty partitioned storage. S33, Migration Execution, migrates data assets to a low-cost storage partition in the selected storage domain.

10. The data asset lifecycle-driven archiving control method based on ownership relationships according to claim 9, characterized in that, The migration execution includes: Pre-register data sovereignty credentials with the target storage domain; Data blocks are transmitted in segments with increasing depth of ownership hierarchy; Write access circuit breaker rules based on permission decay coefficients into the target domain.

Images