A hierarchical encryption method and system for data sharing platforms

Abstract

This invention discloses a method and system for hierarchical encryption of data in a multi-party sharing platform, relating to the field of data processing technology. The method includes: in response to an instruction to create a temporary session, obtaining the permission laziness coefficients of each project member in the temporary session; determining the permission error degree of each project member in the temporary session based on the permission laziness coefficients and the current project permission level; determining the total adjustment weight of each project member in the temporary session based on the permission error degree and the current project permission level; and updating the current project permission level of each project member in the temporary session based on the total adjustment weight, thereby obtaining the updated project permission level of each project member in the temporary session, enabling hierarchical encryption of project data in the temporary session based on the updated project permission level. This invention can reduce the management cost of hierarchical data encryption.

Description

Technical Field

[0001] This invention relates to the field of data processing technology, specifically to a data hierarchical encryption method and system for a multi-party sharing platform. Background Technology

[0002] In enterprise operations, multi-party sharing platforms are widely used in scenarios such as project management and document sharing to meet the data interaction needs of different departments, positions, and project teams. To ensure the security of sensitive enterprise data during the collaboration process and to meet data compliance and confidentiality requirements, a multi-level data security architecture needs to be built, with data being encrypted in a graded manner and granular permissions assigned.

[0003] Currently, the multi-party sharing platform enables different users to have different permissions for the same document, such as read-only, editable, and shareable scope, through hierarchical data encryption and role-based fine-grained permission allocation.

[0004] However, in practice, due to the long project cycle, the project permission levels required by project personnel change frequently, making it difficult to quickly and reasonably adjust the project permission levels of project personnel, and the management cost of data hierarchical encryption is high. Summary of the Invention

[0005] This invention provides a data hierarchical encryption method and system for a multi-party sharing platform, which can reduce the management cost of data hierarchical encryption.

[0006] A first aspect of this invention provides a data hierarchical encryption method for a multi-party sharing platform, comprising:

[0007] In response to the instruction to create a temporary session, obtain the permission inertia coefficient of each project personnel in the temporary session; the permission inertia coefficient is used to characterize the degree of impact of changes in project permission levels on the work of project personnel;

[0008] Based on the permission inertia coefficient and current project permission level of each project personnel in the temporary session, the permission error degree of each project personnel in the temporary session is determined; the permission error degree is used to characterize the degree of deviation between the current project permission level of the project personnel and the theoretical project permission level of the project personnel in the temporary session.

[0009] Based on the permission error degree of each project personnel in the temporary session and the current project permission level, determine the total adjustment weight of each project personnel in the temporary session;

[0010] Based on the adjusted total weight of each project member in the temporary session, the current project permission level of each project member in the temporary session is updated to obtain the updated project permission level of each project member in the temporary session, so as to realize hierarchical encryption of project data in the temporary session based on the updated project permission level.

[0011] Furthermore, this invention also proposes obtaining the permission laziness coefficients of each project member in a temporary session, including:

[0012] The difference between the first timestamp of the current project permission level of the first project personnel and the second timestamp of the target historical project permission level is determined as the lazy parameter of the first project personnel; the first project personnel is any project personnel in the temporary session, and the target historical project permission level is the project permission level before the current project permission level;

[0013] Obtain the third timestamp of each project operation performed by the person in the first project under the current project permission level;

[0014] Based on the laziness parameters of the personnel in the first project and the third timestamps of their operations in each project under the current project permission level, the permission laziness coefficient of the personnel in the first project is determined.

[0015] Furthermore, the present invention also proposes obtaining a third timestamp of the operations performed by the first project personnel in each project under the current project permission level, including:

[0016] Obtain the project step sequence for the first project personnel under the current project permission level; the project step sequence includes multiple project steps processed in chronological order;

[0017] Two adjacent project steps with the same object type and a step interval shorter than the preset time are grouped into the same project operation to obtain multiple project operations corresponding to the project step sequence.

[0018] A third timestamp for the project operation is generated based on the start time of the project operation.

[0019] Furthermore, the present invention also proposes to determine the permission laziness coefficient of the first project personnel based on the laziness parameter of the first project personnel and the third timestamp of the first project personnel's operations in each project under the current project permission level, including:

[0020] Subtract the third timestamp of the (t-1)th project operation of the first project personnel from the third timestamp of the tth project operation of the first project personnel to obtain the operation time interval; t is a positive integer greater than 1.

[0021] The average operation time interval is obtained by averaging the various operation time intervals.

[0022] The permission inertia coefficient of the first project personnel is determined by using the average operation time interval and the inertia parameter of the first project personnel.

[0023] Furthermore, this invention also proposes determining the permission error degree of each project member in a temporary session based on the permission inertia coefficient of each project member and the current project permission level, including:

[0024] The first calculation result is obtained by multiplying the quotient of the current project permission level of the first project personnel and the number of first project personnel in the temporary session by the permission inertia coefficient of the first project personnel; the first project personnel is any project personnel in the temporary session, and the number of first project personnel is used to represent the total number of project personnel in the temporary session.

[0025] The second calculation result is obtained by processing the quotient of the number of personnel in the second project in the temporary session and the highest project permission level in the temporary session using a Gaussian function; the number of personnel in the second project is used to represent the number of project personnel in the temporary session who are at the current project permission level of the personnel in the first project.

[0026] The error rate of the permissions of the first project personnel in the temporary session is determined by using the difference between the first calculation result and the second calculation result.

[0027] Furthermore, this invention proposes determining the total adjustment weight of each project member in a temporary session based on the permission error degree of each project member in the temporary session and the current project permission level, including:

[0028] Select reference project personnel from the temporary session; the current project permission level of the reference project personnel is higher than the current project permission level of the first project personnel, and the first project personnel is any project personnel in the temporary session;

[0029] The total adjustment weight of the first project personnel in the temporary session is determined by using the current project permission level and permission error degree of the reference project personnel, the preset level weight corresponding to the current project permission level of the first project personnel, and the highest project permission level in the temporary session.

[0030] Furthermore, this invention also proposes updating the current project permission level of each project member in a temporary session based on the total adjustment weight of each project member in the temporary session, to obtain the updated project permission level of each project member in the temporary session, including:

[0031] Filter out personnel from temporary sessions whose total weight adjustment exceeds a preset weight threshold;

[0032] Based on the total adjustment weight of each project personnel to be adjusted, the current project permission level of each project personnel to be adjusted is updated to obtain the updated project permission level of each project personnel to be adjusted.

[0033] Furthermore, the present invention also proposes that, before obtaining the permission laziness coefficients of each project personnel in the temporary session in response to the instruction to create a temporary session, the method further includes:

[0034] Obtain the initial project permission levels of each project member in the target development project;

[0035] In response to a project member accessing target project data, determine whether the project member meets the permission update conditions; the target project data is used to represent project data that the project member does not have access to, and the permission update condition is that the project member's project role changes.

[0036] If the project personnel meet the permission update conditions, the initial project permission level of the project personnel will be updated based on their current project role to obtain the current project permission level.

[0037] Furthermore, this invention also proposes obtaining the initial project permission levels of each project member in the target development project, including:

[0038] Obtain the initial project role of the second project member in the target development project; the second project member can be any project member in the target development project.

[0039] Based on the initial project roles of the second project personnel, determine the project attributes of the second project personnel; the project attributes include at least one of role attributes, resource attributes, and environmental attributes;

[0040] Based on the project attributes of the personnel in the second project, determine the initial project permission level of the personnel in the second project.

[0041] A second aspect of this invention provides a data hierarchical encryption system for a multi-party sharing platform, comprising:

[0042] The coefficient acquisition module is used to obtain the permission inertia coefficient of each project personnel in the temporary session in response to the instruction to create a temporary session; the permission inertia coefficient is used to characterize the degree of impact of changes in project permission levels on the work of project personnel.

[0043] The error determination module is used to determine the permission error of each project personnel in a temporary session based on the permission inertia coefficient and the current project permission level. The permission error is used to characterize the degree of deviation between the current project permission level of the project personnel and the theoretical project permission level of the project personnel in the temporary session.

[0044] The weight determination module is used to determine the total adjustment weight of each project personnel in a temporary session based on the permission error degree of each project personnel in the temporary session and the current project permission level.

[0045] The permission update module is used to update the current project permission level of each project member in the temporary session based on the adjusted total weight of each project member in the temporary session, so as to obtain the updated project permission level of each project member in the temporary session, and to realize hierarchical encryption of project data in the temporary session based on the updated project permission level.

[0046] The present invention has the following beneficial effects:

[0047] The data hierarchical encryption method for a multi-party sharing platform provided in this invention firstly obtains the permission inertia coefficient of each project personnel in a temporary session. This permission inertia coefficient characterizes the impact of changes in project permission levels on personnel work, providing an important reference for subsequent adjustments. Secondly, based on the permission inertia coefficient and the current project permission level, the permission error degree is determined, which clarifies the deviation between the current permissions and theoretical permissions of each project personnel in the temporary session, accurately locating the permissions that need adjustment. Thirdly, based on the permission error degree and the current project permission level, the total adjustment weight is determined, comprehensively considering multiple factors and rationally allocating the adjustment priority. Finally, based on the total adjustment weight, the current project permission level of the project personnel is updated to obtain the updated project permission level, thus achieving data hierarchical encryption. In this way, by introducing the permission inertia coefficient, permission error degree, and total adjustment weight, this method establishes a scientific and reasonable temporary session permission adjustment mechanism, enabling rapid and reasonable adjustment of personnel permissions according to the actual situation of the project. This avoids repetitive operations and additional management costs caused by untimely or inaccurate permission adjustments, thereby effectively reducing the management cost of data hierarchical encryption. Attached Figure Description

[0048] To more clearly illustrate the technical solutions and advantages in the embodiments of the present 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 some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0049] Figure 1 This is a flowchart illustrating a data hierarchical encryption method for a multi-party sharing platform provided in an embodiment of the present invention.

[0050] Figure 2 This is a schematic flowchart of S100 provided in one embodiment of the present invention;

[0051] Figure 3 This is a schematic diagram of the structure of a data hierarchical encryption system for a multi-party sharing platform provided in an embodiment of the present invention. Detailed Implementation

[0052] To further illustrate the technical means and effects adopted by the present invention to achieve its intended purpose, the following, in conjunction with the accompanying drawings and preferred embodiments, details the specific implementation, structure, features, and effects of a data hierarchical encryption method and system for a multi-party sharing platform proposed according to the present invention. In the following description, different "one embodiment" or "another embodiment" do not necessarily refer to the same embodiment. Furthermore, specific features, structures, or characteristics in one or more embodiments can be combined in any suitable form.

[0053] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention pertains.

[0054] The following description, in conjunction with the accompanying drawings, details the specific scheme of the data hierarchical encryption method and system for a multi-party sharing platform provided by this invention.

[0055] In traditional, existing multi-party data sharing platforms with hierarchical encryption architectures, dynamic permission adjustment mechanisms suffer from response lag and inaccurate resource allocation. When project cycles are excessively long, the frequency and complexity of permission change requests increase exponentially, causing permission level updates to be delayed beyond the system's response time window. Furthermore, permission allocation algorithms fail to consider the non-linear disturbance effects of permission changes on workflows, resulting in a dynamic imbalance between permission levels and operational requirements.

[0056] For example, in collaborative development scenarios involving cross-regional R&D teams, distributed version control systems need to assign data access permissions to multiple functional groups. When agile development enters the sprint phase, the system generates more than multiple permission change requests per hour. The existing static weight model cannot effectively handle the permission change request queue, resulting in significant delays in permission synchronization. Permission allocation errors cause unauthorized access events in the core codebase, and the deployment process in the test environment is interrupted multiple times due to permission conflicts.

[0057] To address the aforementioned issues, this invention first considers the nonlinear disturbance effect of permission changes on workflows, finding that traditional static weight models cannot quickly capture the dynamic matching relationship between permission levels and operational requirements. To resolve this, this invention attempts to establish a mechanism for quantifying the impact of permission changes. By analyzing the temporal characteristics of historical permission changes and the temporal distribution patterns of operational behaviors, a permission inertia coefficient is constructed as a workflow stability indicator. Furthermore, this invention discovers that the calculation of permission error rate needs to simultaneously consider the permission distribution within the session environment. By introducing the dual constraints of the relative relationship and absolute value of permission levels within temporary sessions, a dynamic weight adjustment mechanism is established. Ultimately, a closed-loop permission level update logic chain is formed by constructing a correlation model between the permission inertia coefficient and the permission error rate, enabling rapid and reasonable adjustment of project permission levels for project personnel in temporary sessions.

[0058] In this regard, such as Figure 1 As shown, this invention provides a flowchart of a hierarchical encryption method for data on a multi-party sharing platform. This hierarchical encryption method can be applied to electronic devices that have data processing and access control functions, can access a multi-party sharing platform, and can create temporary sessions. The hierarchical encryption method for data on a multi-party sharing platform may include the following steps S100 to S400:

[0059] S100, in response to the instruction to create a temporary session, obtains the permission inertia coefficient of each project personnel in the temporary session; the permission inertia coefficient is used to characterize the degree of impact of changes in project permission levels on the work of project personnel.

[0060] In this embodiment, a temporary session refers to a communication and collaboration space established to meet the needs of a specific temporary project, characterized by a certain time limit and specific participants. It differs from long-term, fixed project teams or work groups, being characterized by temporary formation and potential disbandment upon completion of the task. Within a temporary session, project personnel can share documents, exchange information, and collaborate on tasks.

[0061] The project personnel in a temporary session refer to the various members of the project corresponding to that temporary session. They come from different departments and positions, and have different responsibilities and skills. For example, in a software development project, project personnel may include programmers, testers, project managers, etc.

[0062] The permission inertia coefficient is an indicator used to quantify the impact of changes in project permission levels on the work of project personnel. Different project personnel have varying sensitivities and adaptability to permission changes, and the permission inertia coefficient reflects this difference. For example, for project personnel who primarily rely on specific permissions to carry out core tasks, permission changes have a significant impact on their work; while for some support staff, permission changes have a smaller impact on their work.

[0063] Specifically, in the operational scenario of an enterprise multi-party sharing platform, when a specific temporary project requirement arises, relevant personnel (such as the project initiator) issue an instruction to create a temporary session. Upon receiving this instruction, the electronic device immediately initiates the permission laziness coefficient acquisition process. Based on a pre-stored project personnel information database, which includes data such as the personnel's department, position, and historical project permission usage records, and combined with a preset algorithm model, a permission laziness coefficient is calculated and assigned to each project personnel in the temporary session.

[0064] Due to differences in job nature, work habits, and individual abilities, personnel in different projects exhibit varying degrees of sensitivity and adaptability to changes in project permission levels. The permission inertia coefficient is set based on this difference, aiming to quantify the degree of impact. By collecting and analyzing historical data from personnel, and utilizing data mining and machine learning algorithms to build models, it is possible to accurately assess the extent to which each project personnel is affected by permission changes, providing a basis for subsequent permission adjustments.

[0065] S200, based on the permission inertia coefficient and current project permission level of each project personnel in the temporary session, determine the permission error degree of each project personnel in the temporary session; the permission error degree is used to characterize the degree of deviation between the current project permission level of the project personnel and the theoretical project permission level of the project personnel in the temporary session.

[0066] In this embodiment, the current project permission level refers to the level of access and operation permissions that project personnel have to project data at the current moment when a temporary session is created. For example, it may be divided into different levels such as read-only permission, editable permission, and manageable permission.

[0067] Theoretical project access levels refer to the level of project access that should theoretically be assigned to project personnel based on their actual work needs and roles in ad-hoc sessions. It is determined comprehensively based on factors such as the specific tasks and processes of the project, as well as the collaborative relationships between personnel. For example, in a collaborative document project, those responsible for writing certain content should theoretically have edit permissions, while those only needing to view and reference should theoretically have read-only permissions.

[0068] Access control error is an indicator used to measure the deviation between the current access control level of project personnel and the theoretical access control level. By calculating the access control error, it can be determined whether the current access control allocation is reasonable and whether there are any adjustments needed. If the access control error is large, it means that the current access control level deviates significantly from the theoretical access control level, and access control adjustments may be necessary; if the access control error is small, it means that the current access control level is reasonable.

[0069] Specifically, after obtaining the permission inertia coefficients of each project member in the temporary session, the current project permission level of each member is also obtained. Next, based on factors such as the specific tasks, processes, and collaborative relationships between project members, the theoretical project permission level for each member in the temporary session is determined using preset rules and algorithms. For example, in a market research project, the person responsible for data collection should theoretically have read-only and partial editing permissions on the survey questionnaire, while the project manager should have full management permissions. Then, the current project permission level of each member is compared with the theoretical project permission level, and combined with the permission inertia coefficient, the permission error rate for each member is calculated using a specific formula.

[0070] The current project permission level is the initial assignment at the start of a temporary session, and may deviate from the actual work requirements of the temporary session due to various reasons. The theoretical project permission level is the ideal permission state precisely determined based on the actual needs of the temporary session and the roles of the personnel. The calculation of permission error takes into account the permission inertia coefficient, because different personnel have different tolerances for permission deviations. By quantitatively comparing the current project permission level with the theoretical project permission level and adjusting it in conjunction with the permission inertia coefficient, the rationality of permission allocation can be accurately measured, and it can be clearly identified which project personnel's permissions need to be adjusted and the urgency of such adjustments.

[0071] S300, based on the permission error degree of each project personnel in the temporary session and the current project permission level, determines the total adjustment weight of each project personnel in the temporary session.

[0072] In this embodiment, the total adjustment weight is a comprehensive indicator used to guide permission adjustments, determined by taking into account factors such as the permission error rate of project personnel and the current project permission level. It reflects the priority and importance of adjusting project personnel permissions. A higher total adjustment weight indicates that the personnel's permissions require priority adjustment to better align with actual work needs. For example, project personnel with a high permission error rate and whose current project permission level has a critical impact on their work may have a higher total adjustment weight.

[0073] Specifically, after obtaining the permission error rate for each project member, a pre-defined weighting calculation model is used to determine the total adjustment weight, taking into account their current project permission level. This model comprehensively considers both the magnitude of the permission error rate and the importance of the current permission level. For example, a project member with a large permission error rate but whose current permission level is critical to their work will be assigned a higher total adjustment weight; while a project member with a small permission error rate and whose current permission level has little impact on their work will be assigned a lower weight. In this way, a comprehensive indicator is determined for each project member to guide permission adjustments.

[0074] The determination of the overall weight is aimed at rationally allocating the priority and importance of permission adjustments. Permission error rate reflects the degree of deviation in permission allocation, while the current permission level reflects the importance of the permission to the work. Combining these two factors allows for a more scientific assessment of which personnel's permission adjustments are more urgent and critical. Through a pre-defined weight calculation model, these two factors are quantified and integrated, enabling permission adjustments to more accurately meet actual work needs and improve the efficiency and rationality of permission management.

[0075] S400, based on the adjusted total weight of each project personnel in the temporary session, updates the current project permission level of each project personnel in the temporary session to obtain the updated project permission level of each project personnel in the temporary session, so as to realize hierarchical encryption of project data in the temporary session based on the updated project permission level.

[0076] In this embodiment, updating project permission levels refers to modifying the current project permission levels of project personnel based on the total adjustment weight of each project member in the temporary session, resulting in a new permission level. By updating project permission levels, the permissions of project personnel can be better matched to their actual work needs in the temporary session, improving collaboration efficiency and data security. For example, the permissions of personnel who were originally unable to complete their tasks due to insufficient permissions can be raised to an appropriate level, or the permissions of personnel whose excessively high permissions may pose security risks can be reduced to a reasonable range.

[0077] Tiered encryption of project data refers to applying different strengths and methods of encryption to project data in temporary sessions based on the updated permission levels of project personnel. Project personnel with different permission levels have different access and operation permissions for data. Tiered encryption ensures that data can only be accessed and processed by authorized personnel in an appropriate manner, protecting the security and confidentiality of sensitive corporate data during the collaboration process.

[0078] Specifically, based on the total adjustment weight of each project member, their current project permission levels are updated sequentially from highest to lowest. For project members with high total adjustment weights, their permissions are prioritized for adjustment to a state that better reflects actual work needs; for example, the permission levels of those with excessively low permissions are increased, while the permission levels of those with excessively high permissions are decreased. After updating the permission levels of all project members, the updated project permission levels are obtained. Then, based on the updated permission levels, different strengths and methods of encryption measures are applied to the project data in the temporary session.

[0079] The overall weight adjustment reflects the priority of personnel permission adjustments within the project. Updating permission levels according to weight ensures that those most in need of adjustments are processed first, quickly aligning permission allocation with actual work requirements and improving collaboration efficiency. The hierarchical encryption of project data, based on the updated permission levels, uses encryption technology to provide layered protection for the data. Different permission levels grant different access and operation permissions to the data. Hierarchical encryption ensures that data can only be accessed and processed by authorized personnel in an appropriate manner, preventing data leakage and misuse, and safeguarding the security and confidentiality of sensitive corporate data during collaboration.

[0080] This invention quantifies the impact of permission changes on work efficiency by introducing a permission laziness coefficient, and dynamically calculates and adjusts the total weight by combining permission error degree, ultimately realizing the automatic adaptation and update of permission levels in temporary sessions, effectively solving the problem of excessive management costs in traditional methods.

[0081] As an example, consider a short-term, temporary project for promoting a new product undertaken by an internet company. The project initiator issues a command to create a temporary session on the company's multi-party sharing platform. Upon receiving the command, the platform, based on a pre-stored database of project personnel information and a pre-defined algorithm model, calculates and assigns permission inertia coefficients to project personnel from different departments such as marketing, sales, and technology participating in the temporary session. Next, it obtains the current project permission level of each personnel and determines the theoretical project permission level based on project tasks, processes, and personnel collaboration relationships; for example, personnel responsible for writing promotional copy should theoretically have edit permissions. The current project permission level is compared with the theoretical project permission level, and the permission inertia coefficient is used to calculate the permission error. Then, using a pre-defined weight calculation model, considering both the permission error and the current project permission level, the total adjustment weight for each project personnel is determined. For example, marketing personnel with a large permission error and whose current permissions are crucial to their work will have a higher total adjustment weight. Finally, the current project permission levels of project personnel are updated sequentially according to the total adjustment weight from high to low to obtain the updated project permission levels. Based on the updated project permission levels, different strengths and methods of encryption measures are applied to the project data in the temporary session to achieve hierarchical encryption of project data.

[0082] This embodiment first obtains the permission inertia coefficient of each project personnel in the temporary session. This inertia coefficient characterizes the impact of changes in project permission levels on personnel work, providing an important reference for subsequent adjustments. Second, based on the permission inertia coefficient and the current project permission level, the permission error degree is determined, clarifying the deviation between the current and theoretical permissions of each project personnel in the temporary session, and accurately locating the permissions that need adjustment. Third, based on the permission error degree and the current project permission level, the total adjustment weight is determined, comprehensively considering multiple factors and rationally allocating the adjustment priority. Finally, based on the total adjustment weight, the current project permission level of the project personnel is updated to obtain the updated project permission level, thereby achieving hierarchical data encryption. Thus, by introducing the permission inertia coefficient, permission error degree, and total adjustment weight, this method establishes a scientific and reasonable temporary session permission adjustment mechanism. It can quickly and reasonably adjust personnel permissions according to the actual situation of the project, avoiding repetitive operations and additional management costs caused by untimely or inaccurate permission adjustments, thereby effectively reducing the management cost of hierarchical data encryption.

[0083] In some of the solutions described above in this invention, a permission inertia coefficient is proposed to characterize the degree of impact of changes in project permission levels on the work of project personnel. However, in the process of determining the permission inertia coefficient, relying solely on the time interval of changes in project permission levels is insufficient to accurately reflect the impact of permission changes on the actual work rhythm, and the operational behavior characteristics of project personnel under the current project permission level are not considered, resulting in a lack of dynamic adaptability in the calculation of the permission inertia coefficient.

[0084] In this regard, such as Figure 2 As shown, the present invention further proposes that S100 includes the following S110 to S130:

[0085] S110, the difference between the first timestamp of the current project permission level of the first project personnel and the second timestamp of the target historical project permission level is determined as the lazy parameter of the first project personnel; the first project personnel is any project personnel in the temporary session, and the target historical project permission level is the project permission level before the current project permission level;

[0086] S120, obtain the third timestamp of the first project personnel's operations in each project under the current project permission level;

[0087] S130, based on the laziness parameter of the first project personnel and the third timestamp of the first project personnel's operations in each project under the current project permission level, determine the permission laziness coefficient of the first project personnel.

[0088] In this embodiment, the first timestamp is used to mark the effective time of the current project permission level, the second timestamp is used to mark the expiration time of the target historical project permission level, and the third timestamp is used to mark the start time of the project operation. The laziness parameter is calculated by comparing the time difference between the effective time of the current project permission level and the expiration time of the target historical project permission level, which reflects the time span of the project permission level change. The third timestamp is obtained by extracting the operation time node of the project operation. The determination of the permission laziness coefficient combines the time laziness of permission changes with the density of operation behaviors. For example, it is generated by calculating the average time interval of adjacent project operations and performing a weighted operation with the laziness parameter.

[0089] Specifically, when a change in project permission level is detected, the effective time T1 of the current project permission level L1 and the expiration time T0 of the previous project permission level L0 are first extracted. The permission change interval ΔT is calculated as T1-T0 and used as a laziness parameter. Simultaneously, all operation records under the current project permission level are traversed, recording the start timestamp sequence of each project operation. The average time interval Δt between adjacent project operations is further calculated. After normalizing ΔT and Δt, a linear combination formula λ=αΔT+βΔt is used to generate the permission laziness coefficient, where α and β are preset weighting coefficients. This dual-time-dimensional calculation method captures both the impact of permission change cycles on personnel adaptability and quantifies the correlation between operation frequency and workload, making the evaluation results of the permission laziness coefficient more closely reflect actual work scenarios.

[0090] As an example, assuming the first project user's current project permission level has a first timestamp of January 1, 2023, and the target historical project permission level has a second timestamp of July 1, 2022, then the laziness parameter is 6 months. Next, the timestamps of each project operation performed by the first project user under the current project permission level are obtained, such as January 5, 2023, January 10, 2023, January 15, 2023, etc. Finally, based on these timestamp data and the laziness parameter, the permission laziness coefficient for the first project user is calculated using a preset algorithm.

[0091] This embodiment accurately obtains the permission inertia coefficient of each project member in a temporary session. This quantifies the impact of changes in project permission levels on project members' work, providing a data foundation for subsequent permission adjustments. This analysis method, based on historical data and current operations, more objectively reflects project members' adaptability to permission changes, contributing to more precise permission management.

[0092] In some of the solutions described above in this invention, when obtaining the third timestamp of each project operation performed by project personnel under the current project permission level, directly recording the timestamp separately for each step in the original project step sequence may lead to inconsistent operation granularity. Since the same operation may be split into multiple steps with short time intervals, recording them separately will introduce redundant timestamps, thereby affecting the accuracy of the permission laziness coefficient calculation.

[0093] In this regard, the present invention further proposes that S120 includes:

[0094] Obtain the project step sequence for the first project personnel under the current project permission level; the project step sequence includes multiple project steps processed in chronological order;

[0095] Two adjacent project steps with the same object type and a step interval shorter than the preset time are grouped into the same project operation to obtain multiple project operations corresponding to the project step sequence.

[0096] A third timestamp for the project operation is generated based on the start time of the project operation.

[0097] In this embodiment, the project step sequence is captured through a log system or operation recording module, and the time order is automatically arranged by the timestamp sequence of step execution. Same object type means that the operation objects involved in the steps have the same data type identifier or resource identifier, such as editing the same document or querying the same database table. The step interval is calculated by the difference between the start time of the subsequent step and the end time of the previous step. The preset duration is dynamically set according to the operation type; for example, 30 minutes for document editing operations and 5 minutes for data query operations. During the project operation division process, when two consecutive steps meet the conditions of having the same object type and a step interval less than the preset duration, they are merged into one project operation. The start time of the merged project operation is the start time of the first step.

[0098] Specifically, in the process of calculating the permission laziness coefficient, all operation steps of the first project personnel under the current project permission level are first extracted from the operation log, forming a step sequence sorted by time. For example, the step sequence includes step A (starting at 09:00, object type is document D), step B (starting at 09:25, object type is document D), and step C (starting at 09:50, object type is database T). When the preset duration is 30 minutes, steps A and B are separated by 25 minutes and are merged into operation 1, while step C forms operation 2 separately. The start time of operation 1 is taken from 09:00 of step A, and the start time of operation 2 is taken from 09:50 of step C. The resulting third timestamp avoids splitting short-interval related steps into independent operations, ensuring that each project operation represents a complete task unit. This division method allows the subsequent calculation of operation time intervals to accurately reflect the actual work rhythm, thereby improving the calculation accuracy of the permission laziness coefficient and permission error degree.

[0099] As an example, we first obtain the project step sequence for the first project personnel under their current project permission level. The project step sequence includes multiple project steps processed in chronological order. For example, for a software development project, the project step sequence might include steps such as requirements analysis, system design, coding implementation, and testing and verification.

[0100] Next, two adjacent project steps in the project step sequence with the same object type and an interval shorter than a preset time are grouped into the same project operation, resulting in multiple project operations corresponding to the project step sequence. Specifically, the preset time can be set to 30 minutes. If the interval between two consecutive coding implementation steps is less than 30 minutes, these two steps are merged into one project operation.

[0101] Finally, a third timestamp for each project operation is generated based on its start time. For example, for a merged coding implementation operation, its start time can be recorded as the third timestamp.

[0102] This embodiment achieves a reasonable merging of project steps, avoiding overly frequent timestamp recording. This method can more accurately reflect the actual work patterns of project personnel and reduce data noise caused by brief interruptions. Furthermore, by generating merged project operation timestamps, a more reliable data foundation is provided for subsequent calculation of permission laziness coefficients, which helps improve the accuracy and efficiency of permission allocation.

[0103] In some of the solutions described above in this invention, a method is proposed to calculate the permission inertia coefficient using the timestamps of project operations to reflect the degree of impact of permission changes on work. However, in the process of determining the permission inertia coefficient, since the time intervals between different project operations fluctuate greatly, directly using the time intervals of adjacent operations will lead to unstable calculation results, making it difficult to accurately characterize the actual impact of permission level changes on work rhythm.

[0104] In this regard, the present invention further proposes that S130 includes:

[0105] Subtract the third timestamp of the (t-1)th project operation of the first project personnel from the third timestamp of the tth project operation of the first project personnel to obtain the operation time interval; t is a positive integer greater than 1.

[0106] The average operation time interval is obtained by averaging the various operation time intervals.

[0107] The permission inertia coefficient of the first project personnel is determined by using the average operation time interval and the inertia parameter of the first project personnel.

[0108] In this embodiment, the operation time interval is calculated using the timestamp difference between two consecutive project operations to capture changes in the work rhythm of project personnel under the current project permission level. The mean processing uses an arithmetic mean method to smooth the data across multiple operation time intervals, eliminating the impact of random fluctuations on the calculation results. The inertia parameter is determined by the timestamp difference between the current project permission level and the target historical project permission level, reflecting the adaptation period of project personnel to permission changes. The average operation time interval and the inertia parameter are combined through linear weighting and other operations to form a comprehensive quantitative indicator reflecting the sensitivity to permission changes.

[0109] Specifically, when calculating the permission inertia coefficient, the timestamp sequence of all project operations performed by the first project personnel under the current project permission level is first extracted. An operation time interval set is generated by the difference in timestamps between adjacent operations. For example, if a project personnel performs operations at 9:00, 9:15, and 14:30 within three days, two time intervals of 15 minutes and 315 minutes are generated. The arithmetic mean of this set is calculated to obtain the average operation time interval as a typical work rhythm benchmark. Simultaneously, the time difference between the effective time of the current project permission level and the expiration time of the previous project permission level is calculated as an inertia parameter. Finally, the average operation time interval and the inertia parameter are merged according to a preset ratio to generate the permission inertia coefficient. This permission inertia coefficient reflects both the stability of the current work rhythm and the adaptation period of historical permission changes, providing a stable and reliable input parameter for subsequent permission error calculations.

[0110] The permission laziness coefficient can be determined using the following formula 1:

[0111] Formula 1

[0112] In formula 1, The permission laziness coefficient is used to characterize the permission laziness coefficient of the i-th project personnel during the j-th permission update. The third timestamp used to characterize the t-th project operation of the j-th permission update for the i-th project member. The third timestamp is used to represent the (t-1)th project operation of the j-th permission update for the i-th project member, where T represents the total number of project operations at the time of the j-th permission update. The parameter used to characterize the laziness of the i-th project personnel during the j-th permission update is norm, which is used to characterize the standardization process.

[0113] As an example, subtract the third timestamp of the (t-1)th project operation from the third timestamp of the first project operator's t-th project operation to obtain the operation time interval. Here, t is a positive integer greater than 1. For example, suppose the first project operator has 5 project operations with corresponding third timestamps of 10:00, 10:30, 11:15, 14:00, and 15:30. The time interval between the second and first project operations is calculated to be 30 minutes, the time interval between the third and second project operations is 45 minutes, the time interval between the fourth and third project operations is 165 minutes, and the time interval between the fifth and fourth project operations is 90 minutes.

[0114] The average operation time interval is obtained by averaging the various operation time intervals. Further, the calculated operation time intervals of 30 minutes, 45 minutes, 165 minutes, and 90 minutes are summed and then divided by the number of operations (4) to obtain an average operation time interval of 82.5 minutes.

[0115] The permission inertia coefficient for the personnel in the first project is determined by using the average operation time interval and the inertia parameter of the personnel in the first project. Specifically, the permission inertia coefficient can be calculated by substituting the average operation time interval and the inertia parameter into Formula 1 above.

[0116] This embodiment enables accurate calculation of the permission inertia coefficient for project personnel. This allows for a more precise reflection of the impact of changes in project permission levels on the work of project personnel. Furthermore, by introducing an average operation time interval, the time fluctuations of individual operations can be effectively smoothed, improving the stability and reliability of the permission inertia coefficient. In addition, by combining the average operation time interval with an inertia parameter, the actual work rhythm of project personnel and historical permission changes can be comprehensively considered, resulting in a more comprehensive and accurate permission inertia coefficient.

[0117] In some of the solutions described above in this invention, the determination of the permission error degree is based solely on the permission inertia coefficient and the current project permission level, without considering the impact of the distribution of the number of people with the same permission level in a temporary session on the theoretical permission level, which leads to errors in the assessment of the degree of deviation.

[0118] In this regard, the present invention further proposes S200 including:

[0119] The first calculation result is obtained by multiplying the quotient of the current project permission level of the first project personnel and the number of first project personnel in the temporary session by the permission inertia coefficient of the first project personnel; the first project personnel is any project personnel in the temporary session, and the number of first project personnel is used to represent the total number of project personnel in the temporary session.

[0120] The second calculation result is obtained by processing the quotient of the number of personnel in the second project in the temporary session and the highest project permission level in the temporary session using a Gaussian function; the number of personnel in the second project is used to represent the number of project personnel in the temporary session who are at the current project permission level of the personnel in the first project.

[0121] The error rate of the permissions of the first project personnel in the temporary session is determined by using the difference between the first calculation result and the second calculation result.

[0122] In this embodiment, the number of people in the first item represents the total number of people in the temporary session, and the number of people in the second item represents the number of people at the same permission level. Gaussian function processing eliminates the discreteness of the personnel distribution through nonlinear mapping. The difference operation between the two couples couples the group distribution characteristics with the individual inertia characteristics, forming a dynamic compensation mechanism.

[0123] Specifically, when multiple individuals with the same permission level exist in a temporary session, the ratio of the number of individuals in the second category to the highest permission level is processed using a Gaussian function to generate a smoothing parameter characterizing the group distribution density. Simultaneously, the first calculation result reflects the relative permission weight of an individual within the group by proportionally allocating individual permission levels to the total number of individuals. Calculating the difference between the smoothed group density parameter and the individual relative permission weight eliminates evaluation errors caused by the concentrated distribution of permission levels, accurately quantifying the deviation between the actual permission level and the theoretical value.

[0124] The permission error rate can be determined using the following formula 2:

[0125] Formula 2

[0126] In formula 2, Used to characterize the permission error degree of the i-th project personnel. The parameter N represents the current project permission level of the i-th project personnel, and N represents the number of personnel in the first project in the temporary session. The permission laziness coefficient is used to characterize the permission laziness coefficient of the i-th project personnel during the j-th permission update. B is used to represent the number of people in the second project in a temporary session, G is used to represent the highest project authority level in a temporary session, exp is used to represent the Gaussian function, and exp is used to represent the exponential function operation with the natural constant as the base.

[0127] in, The difference here represents the weight of the permission level of the person in the temporary session after the permission laziness coefficient is corrected. The smaller the difference is, and the less than 0 it is, the greater the permission error.

[0128] The credibility of a temporary privilege level upgrade for a single person in this temporary session depends on the structure of the participants in the temporary session. When there is no significant gap in the privilege level of the participants above their privilege level, it can be considered that their privilege to process shared data in the current temporary session is authorized hierarchically. In this case, the number of people at each of their privilege levels should follow a normal distribution, that is, the fewer people there are with higher privilege levels.

[0129] As an example, firstly, the quotient of the current project permission level of the first project member and the number of first project members in the temporary session is multiplied by the permission laziness coefficient of the first project member to obtain the first calculation result. Here, the first project member refers to any project member in the temporary session, and the number of first project members represents the total number of project members in the temporary session. For example, assuming there are 10 project members in the temporary session, the first project member's current project permission level is 3, and the permission laziness coefficient is 0.8, then the first calculation result is: 3 / 10 0.8 = 0.24.

[0130] Next, the quotient of the number of personnel in the second project within the temporary session and the highest project permission level in the temporary session is processed using a Gaussian function to obtain the second calculation result. Here, the number of personnel in the second project represents the number of personnel in the temporary session at the same project permission level as the personnel in the first project. For example, assuming the highest project permission level in the temporary session is 5, and there are 4 personnel at the current project permission level (level 3) of the personnel in the first project, then the second calculation result is: Gaussian function (4 / 5) = 0.6.

[0131] Finally, the difference between the first and second calculation results is used to determine the permission error degree of the first project personnel in the temporary session. Specifically, the first and second calculation results are substituted into Formula 2 above to calculate the permission error degree of the first project personnel in the temporary session.

[0132] This embodiment enables the accurate calculation of project personnel's permission error rate based on their permission inertia coefficient and current project permission level. This reflects the deviation between a project personnel's current permission level and their theoretical permission level in a temporary session, providing a basis for subsequent adjustments to their permission levels and achieving more precise data hierarchical encryption. This method considers the impact of permission changes on project personnel and their relative position in temporary sessions, making permission adjustments more rational and improving data security and collaboration efficiency.

[0133] In some of the solutions described above in this invention, when determining the total adjustment weight based on the permission error degree and the current project permission level, only the preset level weight corresponding to the current project permission level is considered, without introducing the influence of personnel with higher permission levels on the adjustment process, resulting in a deviation between the permission level adjustment result and the actual collaboration needs of the project.

[0134] In this regard, the present invention further proposes S300 including:

[0135] Select reference project personnel from the temporary session; the current project permission level of the reference project personnel is higher than the current project permission level of the first project personnel, and the first project personnel is any project personnel in the temporary session;

[0136] The total adjustment weight of the first project personnel in the temporary session is determined by using the current project permission level and permission error degree of the reference project personnel, the preset level weight corresponding to the current project permission level of the first project personnel, and the highest project permission level in the temporary session.

[0137] In this embodiment, when filtering reference project personnel, the current project permission level of all project personnel in the temporary session is traversed, and project personnel with permission levels higher than the first project personnel are marked as reference project personnel.

[0138] When determining the total weight for adjustment, the specific calculation is performed using the following formula 3:

[0139] Formula 3

[0140] In formula 3, B is used to represent the total adjustment weight of the i-th project personnel, and B is used to represent the highest project permission level in the temporary session. Used to characterize the current project permission level of the z-th reference project personnel. Used to characterize the permission error degree of the personnel in the z-th reference project. The preset level weight is used to represent the current project permission level of the i-th project personnel. The term "norm" is used to characterize the total number of people in the reference project, while "norm" is used to characterize the standardization process.

[0141] As an example, first, reference project personnel are selected from the temporary session. The current project permission level of the reference project personnel is higher than that of the first project personnel, who can be any project personnel in the temporary session. Further, using the current project permission level of the reference project personnel, the permission error degree, the preset level weight corresponding to the current project permission level of the first project personnel, and the highest project permission level in the temporary session, the total adjustment weight of the first project personnel in the temporary session is determined by Formula 3 above.

[0142] This embodiment enables the determination of the total adjustment weight for each project member in a temporary session based on the permission error rate of each project member and the current project permission level. This method considers the permission differences and errors among project members, making permission adjustments more precise and reasonable. Furthermore, by introducing the concept of reference project members, the relative permission relationships between project members can be better reflected, improving the accuracy of permission adjustments. This method effectively solves the problem of frequent permission changes caused by long project cycles, reduces the management cost of hierarchical data encryption, and improves the data security and efficiency of multi-party sharing platforms.

[0143] In some of the solutions described above in this invention, the project personnel permission levels are updated based on adjusting the total weight. However, in actual operation, if permission adjustments are performed on all project personnel, it will lead to a waste of system resources and a reduction in permission management efficiency.

[0144] In this regard, the present invention further proposes S400 including:

[0145] Filter out personnel from temporary sessions whose total weight adjustment exceeds a preset weight threshold;

[0146] Based on the total adjustment weight of each project personnel to be adjusted, the current project permission level of each project personnel to be adjusted is updated to obtain the updated project permission level of each project personnel to be adjusted.

[0147] In this embodiment, the preset weight threshold is determined by the median of the weight distribution of valid adjustment cases in the historical permission adjustment record. Furthermore, when screening personnel for adjustments, a dynamic threshold mechanism can be used to automatically adjust the threshold range based on the total adjustment weight distribution in temporary sessions.

[0148] Specifically, the total adjustment weight for each project's personnel is first compared to a preset weight threshold, filtering out the set of personnel whose weight exceeds the threshold. For each personnel in this set, the total adjustment weight is mapped to the permission level adjustment range; for example, an increase of 0.1 in the weight value corresponds to a one-level increase in permission level. During the update process, the current project's permission level and the adjustment range are added together. If the calculated result exceeds the set maximum permission level, the highest level is used as the update result. This method targets only personnel with significant permission deviations, avoiding computational redundancy from global permission updates, while ensuring that permission changes are concentrated on key personnel, effectively improving the adjustment efficiency of the data hierarchical encryption strategy.

[0149] As an example, select project personnel from temporary sessions whose total adjustment weight exceeds a preset weight threshold. For instance, the preset weight threshold can be set to 0.8. For each project personnel in the temporary session, calculate their total adjustment weight. If a project personnel's total adjustment weight is greater than 0.8, then select them as project personnel to be adjusted.

[0150] Based on the total adjustment weight of each project personnel to be adjusted, the current project permission level of each personnel is updated to obtain the updated project permission level for each personnel. Specifically, the current project permission level can be adjusted accordingly based on the magnitude of the total adjustment weight. For example, if the total adjustment weight of a project personnel to be adjusted is 0.85 and the current project permission level is level 3, then it can be updated to level 4. If the total adjustment weight is 0.9, then the permission level can be increased by 2 levels, updating to level 5.

[0151] This embodiment enables targeted screening and updating of permissions for personnel whose permissions need adjustment based on the overall adjustment weight of project personnel, avoiding unnecessary permission adjustments for all personnel. This improves the efficiency and accuracy of permission updates, reduces human intervention, and lowers the management costs of hierarchical data encryption. Furthermore, by setting preset weight thresholds, the frequency and magnitude of permission adjustments can be controlled, ensuring the stability and rationality of permission allocation.

[0152] In some of the solutions described above in this invention, the adjustment of project permission levels depends on the calculation of dynamic parameters in temporary sessions, but the problem of connecting the initial permission settings of project personnel with the dynamic changes in roles is not solved, resulting in a delay in permission updates after role changes and increasing the risk of data leakage.

[0153] In response, this invention further proposes that, prior to S100, the data hierarchical encryption method of this multi-party sharing platform also includes:

[0154] Obtain the initial project permission levels of each project member in the target development project;

[0155] In response to a project member accessing target project data, determine whether the project member meets the permission update conditions; the target project data is used to represent project data that the project member does not have access to, and the permission update condition is that the project member's project role changes.

[0156] If the project personnel meet the permission update conditions, the initial project permission level of the project personnel will be updated based on their current project role to obtain the current project permission level.

[0157] In this embodiment, the initial project permission level is obtained by parsing the mapping relationship between project roles and multi-dimensional attributes. Project attributes include at least one of role attributes, resource attributes, and environment attributes, where role attributes correspond to job responsibilities, resource attributes relate to data access scope, and environment attributes reflect project stage characteristics. The permission update triggering mechanism is based on cross-validation of role change events and data access requests. When a role change is detected and unauthorized data access behavior exists, the permission update process is activated.

[0158] Specifically, the initial project permission level can be established through the following steps: First, extract the job tag from the project personnel's registration information as a role attribute, and associate it with the average data access level of that role in historical projects; second, extract the data / system scope that the project personnel need to access as a resource attribute; finally, generate environment attribute parameters by combining the security level of the project stage. These three sets of attribute values ​​are weighted and mapped to a preset permission level table to generate the initial permission level. When a project personnel attempts to access data beyond their current permissions, the access request time point is compared with the most recent role change record. If the role change occurred before the access request, a permission update condition is triggered. During the update process, the permission level is recalculated using the attribute parameters after the role change, and synchronized to the data encryption module to adjust the personnel's decryption key permission range. For example, after a developer is promoted to project manager, their role attribute weight increases from 0.3 to 0.6, the resource attribute increases by 20% due to the expanded management scope, and the environment attribute increases its security level as the project enters the delivery stage. After comprehensive calculation of these three factors, the permission level increases from L2 to L4, automatically gaining access to core design documents.

[0159] As an example, in the target development project, the process of obtaining the initial project permission level includes the following steps: First, the initial project role of each member of the development team is obtained through the project management interface. This role is synchronized from the human resources management system to the multi-party shared platform. Second, based on the developer's initial project role, the role attribute analysis module is called to identify the corresponding role attributes, which include three basic categories: system architect, front-end engineer, and test engineer. Further, the access frequency and resource dependency of the member in the project resource library are calculated using a resource attribute evaluation algorithm. Simultaneously, the security level parameters of the current development stage of the project are collected using an environment attribute detection unit. Finally, the role attributes, resource attributes, and environment attributes are input into the permission level decision model to generate an initial project permission level matrix containing five permission categories. When a developer attempts to access an encrypted requirements document, the permission management system detects that the document is in an unauthorized access range, triggering a permission update condition judgment process. The permission update condition is set to a change in the developer's role field in the project management system. If it is detected that the developer's role has changed from test engineer to project manager, the role permission mapping table is called to dynamically upgrade the initial project permission level from level three to level four, while simultaneously updating the key allocation rules in the hierarchical encryption strategy.

[0160] This embodiment effectively solves the data security risk caused by the lag in adjusting the permission levels of project personnel. By establishing a real-time linkage mechanism between role changes and permission levels, it avoids the operational delays caused by manual approval of permission upgrades. At the same time, it ensures that the permission allocation results match the actual security needs of the project by comprehensively determining the initial permission level based on multi-dimensional attributes, thereby reducing the probability of unauthorized access caused by improper permission settings.

[0161] In some of the solutions described above in this invention, a method for dynamically adjusting project permission levels based on permission laziness coefficients is proposed. However, if the initial permission level cannot be accurately allocated during the project startup phase, the subsequent dynamic adjustment process may frequently trigger permission changes, leading to an increase in the computational complexity of permission error and affecting the stability of data hierarchical encryption.

[0162] In response, this invention further proposes obtaining the initial project permission levels of each project member in the target development project, including:

[0163] Obtain the initial project role of the second project member in the target development project; the second project member can be any project member in the target development project.

[0164] Based on the initial project roles of the second project personnel, determine the project attributes of the second project personnel; the project attributes include at least one of role attributes, resource attributes, and environmental attributes;

[0165] Based on the project attributes of the personnel in the second project, determine the initial project permission level of the personnel in the second project.

[0166] In this embodiment, a quantitative evaluation model for the initial project permission level is constructed using a "project attribute triple" (role attribute, resource attribute, and environment attribute). The role attribute defines a person's basic functional role within the project (e.g., development, testing, operations); the resource attribute associates the scope of data / systems they need to access (e.g., code repository, testing environment, production database); and the environment attribute reflects the characteristics of the project phase (e.g., development phase, testing phase, deployment phase). Through the combined mapping of these three types of attributes, the initial project permission level can be accurately anchored, avoiding the problems of overly lenient or overly restrictive permissions caused by traditional "one-size-fits-all" allocation.

[0167] Specifically, the initial project roles (e.g., "Front-end Development Engineer") of the second project personnel are first obtained through the project management system or role assignment interface. These roles are usually bound to the responsibility descriptions in the project task decomposition structure. Then, role attributes (e.g., "Development") are parsed based on the role definition table. Resource attributes (e.g., "Read-write code repository A, read-only design document B") are obtained through resource access logs or permission application templates. Environment attributes (e.g., "Development environment") are determined through project phase identifiers or environment configuration files. Then, a weighted scoring model is used to assign weights to the three types of attributes (e.g., role attributes 40%, resource attributes 40%, environment attributes 20%). The initial project permission level is generated through preset mapping rules and stored in the permission management system as a benchmark value for dynamic adjustment.

[0168] This embodiment implements a permission initialization mechanism based on dynamic matching of multi-dimensional attributes, effectively solving the permission deviation problem caused by the single role definition in the traditional permission allocation process. By automatically associating resource types with environmental characteristics, it avoids the operational errors of manually configuring permissions item by item, enabling newly joined project members to accurately obtain data access permissions that match the current task scenario, significantly improving the efficiency of permission configuration and the accuracy of data security management in multi-party collaboration scenarios.

[0169] This invention provides specific embodiments of a data hierarchical encryption method for a multi-party sharing platform. Correspondingly, this invention also provides specific embodiments of a data hierarchical encryption system for a multi-party sharing platform.

[0170] like Figure 3 The diagram shows a structural schematic of a hierarchical data encryption system for a multi-party sharing platform. This hierarchical data encryption system 300 includes a coefficient acquisition module 310, an error determination module 320, a weight determination module 330, and a permission update module 340.

[0171] The coefficient acquisition module 310 is used to obtain the permission inertia coefficient of each project personnel in the temporary session in response to the instruction to create a temporary session; the permission inertia coefficient is used to characterize the degree of impact of changes in project permission levels on the work of project personnel.

[0172] The error determination module 320 is used to determine the permission error of each project personnel in the temporary session based on the permission inertia coefficient and the current project permission level of each project personnel in the temporary session; the permission error is used to characterize the degree of deviation between the current project permission level of the project personnel and the theoretical project permission level of the project personnel in the temporary session.

[0173] The weight determination module 330 is used to determine the total adjustment weight of each project personnel in the temporary session based on the permission error degree of each project personnel in the temporary session and the current project permission level.

[0174] The permission update module 340 is used to update the current project permission level of each project person in the temporary session based on the adjusted total weight of each project person in the temporary session, so as to obtain the updated project permission level of each project person in the temporary session, so as to realize hierarchical encryption of project data in the temporary session based on the updated project permission level.

[0175] In the data hierarchical encryption system of the multi-party sharing platform provided in this invention embodiment, firstly, the permission inertia coefficient of each project personnel in the temporary session is obtained. This permission inertia coefficient characterizes the impact of changes in project permission levels on personnel work, providing an important reference for subsequent adjustments. Secondly, based on the permission inertia coefficient and the current project permission level, the permission error degree is determined, which clarifies the deviation between the current permissions and theoretical permissions of each project personnel in the temporary session, accurately locating the permissions that need adjustment. Thirdly, based on the permission error degree and the current project permission level, the total adjustment weight is determined, which comprehensively considers multiple factors and rationally allocates the priority of adjustments. Finally, based on the total adjustment weight, the current project permission level of the project personnel is updated to obtain the updated project permission level, thereby achieving data hierarchical encryption. Thus, by introducing the permission inertia coefficient, permission error degree, and total adjustment weight, this method establishes a scientific and reasonable temporary session permission adjustment mechanism, enabling rapid and reasonable adjustment of personnel permissions according to the actual situation of the project. This avoids repetitive operations and additional management costs caused by untimely or inaccurate permission adjustments, thereby effectively reducing the management cost of data hierarchical encryption.

[0176] It should be noted that the order of the above embodiments of the present invention is merely for descriptive purposes and does not represent the superiority or inferiority of the embodiments. The processes depicted in the accompanying drawings do not necessarily require a specific or sequential order to achieve the desired result. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0177] The various embodiments in this specification are described in a progressive manner. The same or similar parts between the various embodiments can be referred to each other. Each embodiment focuses on describing the differences from other embodiments.

Claims

1. A hierarchical encryption method for data in a multi-party sharing platform, characterized in that, The method includes: In response to an instruction to create a temporary session, the permission inertia coefficient of each project personnel in the temporary session is obtained; the permission inertia coefficient is used to characterize the degree of impact of changes in project permission levels on the work of the project personnel. Based on the permission inertia coefficient and current project permission level of each project member in the temporary session, the permission error degree of each project member in the temporary session is determined; the permission error degree is used to characterize the degree of deviation between the current project permission level of the project member and the theoretical project permission level of the project member in the temporary session. Based on the permission error degree of each project personnel in the temporary session and the current project permission level, determine the total adjustment weight of each project personnel in the temporary session; Based on the total adjusted weight of each project personnel in the temporary session, the current project permission level of each project personnel in the temporary session is updated to obtain the updated project permission level of each project personnel in the temporary session, so as to realize hierarchical encryption of project data in the temporary session based on the updated project permission level. The step of obtaining the permission inertia coefficient of each project personnel in the temporary session includes: determining the difference between the first timestamp of the current project permission level of the first project personnel and the second timestamp of the target historical project permission level as the inertia parameter of the first project personnel; the first project personnel is any one of the project personnel in the temporary session, and the target historical project permission level is the previous project permission level of the current project permission level; Obtain the third timestamp of each project operation performed by the first project personnel under the current project permission level; Based on the laziness parameter of the first project personnel and the third timestamp of the first project personnel's operations in each project under the current project permission level, the permission laziness coefficient of the first project personnel is determined. The step of determining the permission error degree of each project member in the temporary session based on the permission inertia coefficient and the current project permission level of each project member in the temporary session includes: multiplying the quotient of the current project permission level of the first project member and the number of the first project members in the temporary session by the permission inertia coefficient of the first project member to obtain a first calculation result; the first project member is any one of the project members in the temporary session, and the number of the first project members is used to represent the total number of project members in the temporary session; The quotient of the number of personnel in the second project in the temporary session and the highest project permission level in the temporary session is processed by a Gaussian function to obtain a second calculation result; the number of personnel in the second project is used to represent the number of personnel in the temporary session who are at the current project permission level of the personnel in the first project. The difference between the first calculation result and the second calculation result is used to determine the permission error degree of the first project personnel in the temporary session.

2. The data hierarchical encryption method for a multi-party sharing platform according to claim 1, characterized in that, The step of obtaining the third timestamp of the operations of the first project personnel in each project under the current project permission level includes: Obtain the project step sequence of the first project personnel under the current project permission level; the project step sequence includes multiple project steps processed in chronological order; Two adjacent project steps in the project step sequence that have the same object type and a step interval of less than a preset time are grouped into the same project operation to obtain multiple project operations corresponding to the project step sequence. A third timestamp for the project operation is generated based on the start time of the project operation.

3. The data hierarchical encryption method for a multi-party sharing platform according to claim 1, characterized in that, The determination of the permission inertia coefficient of the first project personnel based on the inertia parameter of the first project personnel and the third timestamp of the first project personnel's operations in each project under the current project permission level includes: The operation time interval is obtained by subtracting the third timestamp of the (t-1)th project operation of the first project personnel from the third timestamp of the tth project operation of the first project personnel; t is a positive integer greater than 1. The average operation time interval is obtained by averaging the various operation time intervals. The permission inertia coefficient of the first project personnel is determined by using the average operation time interval and the inertia parameter of the first project personnel.

4. The data hierarchical encryption method for a multi-party sharing platform according to claim 1, characterized in that, The determination of the total adjustment weight for each project member in the temporary session based on the permission error degree of each project member in the temporary session and the current project permission level includes: Reference project personnel are selected from the temporary session; the current project permission level of the reference project personnel is greater than the current project permission level of the first project personnel, and the first project personnel is any one of the project personnel in the temporary session; The total adjustment weight of the first project personnel in the temporary session is determined by using the current project permission level of the reference project personnel, the permission error degree, the preset level weight corresponding to the current project permission level of the first project personnel, and the highest project permission level in the temporary session.

5. The data hierarchical encryption method for a multi-party sharing platform according to claim 1, characterized in that, The step of updating the current project permission level of each project member in the temporary session based on the total adjustment weight of each project member in the temporary session, to obtain the updated project permission level of each project member in the temporary session, includes: Filter out the personnel whose total adjustment weight is greater than a preset weight threshold from the temporary sessions; Based on the total adjustment weight of each of the personnel to be adjusted, the current project permission level of each of the personnel to be adjusted is updated to obtain the updated project permission level of each of the personnel to be adjusted.

6. The data hierarchical encryption method for a multi-party sharing platform according to any one of claims 1-5, characterized in that, Before obtaining the permission laziness coefficients of each project member in the temporary session in response to the instruction to create a temporary session, the method further includes: Obtain the initial project permission level of each project member in the target development project; In response to the project personnel accessing the target project data, it is determined whether the project personnel meet the permission update conditions; the target project data is used to represent project data that the project personnel do not have access to, and the permission update condition is that the project personnel's project role changes. If the project personnel meet the permission update conditions, the initial project permission level of the project personnel is updated based on the current project role of the project personnel to obtain the current project permission level.

7. The data hierarchical encryption method for a multi-party sharing platform according to claim 6, characterized in that, The process of obtaining the initial project permission level of each project member in the target development project includes: Obtain the initial project role of the second project member in the target development project; the second project member is any one of the project members in the target development project; Based on the initial project role of the second project personnel, the project attributes of the second project personnel are determined; the project attributes include at least one of role attributes, resource attributes, and environmental attributes. Based on the project attributes of the personnel in the second project, determine the initial project permission level of the personnel in the second project.

8. A hierarchical encryption system for data on a multi-party sharing platform, characterized in that, The system includes: A coefficient acquisition module is used to acquire the permission inertia coefficient of each project personnel in the temporary session in response to an instruction to create a temporary session. The permission inertia coefficient is used to characterize the degree of impact of changes in project permission levels on the work of the project personnel. Acquiring the permission inertia coefficient of each project personnel in the temporary session includes: determining the difference between the first timestamp of the current project permission level of the first project personnel and the second timestamp of the target historical project permission level as the inertia parameter of the first project personnel; the first project personnel is any one of the project personnel in the temporary session, and the target historical project permission level is the project permission level preceding the current project permission level; acquiring the third timestamp of each project operation of the first project personnel under the current project permission level; and determining the permission inertia coefficient of the first project personnel based on the inertia parameter of the first project personnel and the third timestamp of each project operation of the first project personnel under the current project permission level. The error determination module is used to determine the permission error degree of each project member in the temporary session based on the permission inertia coefficient and the current project permission level of each project member. The permission error degree characterizes the deviation between the current project permission level of the project member and the theoretical project permission level of the project member in the temporary session. Determining the permission error degree of each project member in the temporary session based on the permission inertia coefficient and the current project permission level includes: multiplying the quotient of the current project permission level of the first project member and the number of first project members in the temporary session by the first term. The laziness coefficient of the project personnel's permissions is used to obtain a first calculation result; the first project personnel is any one of the project personnel in the temporary session, and the number of the first project personnel is used to represent the total number of project personnel in the temporary session; the quotient of the number of the second project personnel in the temporary session and the highest project permission level in the temporary session is processed by a Gaussian function to obtain a second calculation result; the number of the second project personnel is used to represent the number of project personnel in the temporary session at the current project permission level of the first project personnel; the difference between the first calculation result and the second calculation result is used to determine the permission error degree of the first project personnel in the temporary session; The weight determination module is used to determine the total adjustment weight of each project personnel in the temporary session based on the permission error degree of each project personnel in the temporary session and the current project permission level; The permission update module is used to update the current project permission level of each project member in the temporary session based on the adjusted total weight of each project member in the temporary session, so as to obtain the updated project permission level of each project member in the temporary session, so as to realize hierarchical encryption of project data in the temporary session based on the updated project permission level.

Images