Cloud disk menu authority control method and device and storage medium

Abstract

The embodiment of the invention provides a cloud disk menu authority control method and device and a storage medium. The method comprises the following steps: setting an operation authority corresponding to a cloud disk menu; determining all leaf node menus visible to the target user according to the post attributes of the target user and a post menu mapping rule; based on the hierarchical relationship of the cloud disk menu and leaf node menus, a menu tree is constructed for the target user, and each leaf node menu in the menu tree is provided with a unique binary permission code; establishing an association mapping table of the operation authority and the binary authority code, wherein the association mapping table comprises an operation authority combination corresponding to each leaf node menu; determining a target menu and an operation type according to a cloud disk operation request of a target user; and on the basis of the target menu, the binary permission code and the association mapping table, verifying the user visible permission and the user operation permission of the target user for operating the cloud disk menu. According to the method, the efficiency of cloud disk menu management and control is improved.

Description

Technical Field

[0001] This application relates to the fields of interface menu management and computer technology, specifically to a method, apparatus and storage medium for cloud disk menu permission control. Background Technology

[0002] As enterprises accelerate their digital transformation, online storage, interaction, and management of office documents have become core needs. As a crucial office tool, enterprise cloud storage's comprehensive service capabilities directly impact enterprise office efficiency. However, existing enterprise cloud storage systems suffer from numerous pain points in practical applications, failing to meet the refined usage needs of enterprise customers.

[0003] First, enterprise customers lack centralized storage and management tools for downloadable files. The scattered storage of files leads to low efficiency in searching and retrieving them. Furthermore, there is a lack of convenient and secure online means for file exchange between enterprises, making it impossible to efficiently achieve closed-loop management of the entire process of receiving, forwarding, storing, and using office documents, which hinders the online transformation of office operations.

[0004] Secondly, existing enterprise cloud storage systems have significant deficiencies in menu display and access control. The system uses a fixed menu display mode, where all users can see the entire menu, without differentiated configuration based on the business functions of different positions within the enterprise, resulting in insufficient data security and isolation.

[0005] Furthermore, the menu loading and query mechanism is unreasonable. The existing system queries menus and submenus recursively, requiring users to navigate through directories level by level to view files. This cumbersome and repetitive recursive query increases server request pressure, easily leading to system response delays and hindering stable system operation. This problem is particularly pronounced in scenarios with a large number of enterprise files and frequent user access.

[0006] In addition, the existing menu creation process lacks flexibility, requiring manual entry into the database based on menu information provided by business personnel. Menu structure adjustments and permission updates are complex and cannot dynamically adapt to permission configuration requirements arising from changes in enterprise positions, further reducing the system's usability and adaptability.

[0007] In summary, existing enterprise cloud storage services have significant shortcomings in centralized file management, cross-enterprise interaction, differentiated permission control for different job roles, and menu loading efficiency. There is an urgent need for a technical solution that can optimize the menu structure and achieve refined permission control to improve the comprehensive service capabilities of enterprise cloud storage services, meet the full-process needs of enterprises for receiving, transferring, storing, and using office documents, and ensure data security and stable system operation. Summary of the Invention

[0008] The purpose of this application is to provide a method, apparatus, and storage medium for cloud drive menu permission management, which improves the efficiency of cloud drive menu management.

[0009] To achieve the above objectives, the first aspect of this application provides a method for controlling menu permissions on a cloud drive, the method comprising: Configure the operation permissions corresponding to the cloud drive menu, which includes share, preview, upload, download, edit, and delete; Determine all leaf node menus visible to the target user based on the target user's job attributes and job menu mapping rules; Based on the hierarchical relationship and leaf node menus of the cloud disk menu, a menu tree is constructed for the target user, and each leaf node menu in the menu tree is assigned a unique binary permission code; Establish an association mapping table between the operation permissions and binary permission codes, wherein the association mapping table includes the operation permission combination corresponding to each leaf node menu; Determine the target menu and operation type based on the target user's cloud drive operation request; Based on the target menu, binary permission code, and associated mapping table, the user's visibility and operation permissions are verified to operate the cloud drive menu.

[0010] Optionally, each leaf node menu in the menu tree has a unique binary permission code, including: Generate corresponding binary permission codes based on the visibility of the leaf node menus in the menu tree; Each binary digit in the binary permission code corresponds to the visibility permission status of a leaf node menu, with 1 indicating visibility and 0 indicating invisibility.

[0011] Optionally, the method further includes: Monitor the target user's operational behavior. When the operational behavior does not meet the permission control dimensions, activate the temporary permission freeze mechanism and generate a permission warning notification. The access control dimensions include the scope of the operation object, the operation time limit, and the operation frequency threshold.

[0012] Optionally, the step of verifying the target user's visibility and operation permissions based on the target menu, binary permission code, and associated mapping table, for operating the cloud drive menu, includes: Verify the target user's user visibility permission for the target menu based on the target menu and the binary permission code; Verify the target user's user operation permissions for the target menu based on the operation type and the associated mapping table; The user operates on the cloud drive menu according to the user's visibility permissions and user operation permissions.

[0013] Optionally, operating the cloud drive menu based on the user's visibility permissions and user operation permissions includes: If both the user's visibility permission and user's operation permission are verified, then the target user is allowed to operate the target menu.

[0014] Optionally, the job attributes include job level, department affiliation, and business functions; Menu visibility priority is set based on the job level and department affiliation, and menu visibility filtering conditions are set based on the business function to retain leaf node menus related to the target user's business function.

[0015] Optionally, the leaf node menu is the smallest indivisible functional menu unit.

[0016] A second aspect of this application provides a device for managing cloud drive menu permissions, the device comprising: The first processing module is used to set the operation permissions corresponding to the cloud drive menu, which includes share, preview, upload, download, edit, and delete. The second processing module is used to determine all leaf node menus visible to the target user based on the target user's job attributes and job menu mapping rules. The third processing module is used to construct a menu tree for the target user based on the hierarchical relationship and leaf node menus of the cloud disk menu. Each leaf node menu in the menu tree has a unique binary permission code. The fourth processing module is used to establish an association mapping table between the operation permissions and binary permission codes, wherein the association mapping table includes the operation permission combination corresponding to each leaf node menu. The fifth processing module is used to determine the target menu and operation type based on the target user's cloud drive operation request; The sixth processing module is used to verify the target user's visibility permissions and operation permissions based on the target menu, binary permission code, and associated mapping table, and is used to operate the cloud disk menu.

[0017] Optionally, each leaf node menu in the menu tree has a unique binary permission code, including: Generate corresponding binary permission codes based on the visibility of the leaf node menus in the menu tree; Each binary digit in the binary permission code corresponds to the visibility permission status of a leaf node menu, with 1 indicating visibility and 0 indicating invisibility.

[0018] A third aspect of this application provides a processor configured to execute the cloud disk menu permission control method described above.

[0019] A fourth aspect of this application provides a machine-readable storage medium storing instructions that, when executed by a processor, configure the processor to perform the cloud disk menu permission control method described above.

[0020] The fifth aspect of this application provides a computer program product, including a computer program that, when executed by a processor, implements the cloud disk menu permission control method described above.

[0021] This application discloses a method for controlling cloud drive menu permissions, comprising: setting operation permissions corresponding to cloud drive menus, wherein the cloud drive menus include sharing, previewing, uploading, downloading, editing, and deleting; determining all leaf node menus visible to the target user based on the target user's job attributes and job menu mapping rules; constructing a menu tree for the target user based on the hierarchical relationship of the cloud drive menus and the leaf node menus, wherein each leaf node menu in the menu tree has a unique binary permission code; establishing an association mapping table between the operation permissions and the binary permission codes, wherein the association mapping table includes the combination of operation permissions corresponding to each leaf node menu; determining the target menu and operation type based on the target user's cloud drive operation request; and verifying the target user's user visibility permissions and user operation permissions based on the target menu, the binary permission code, and the association mapping table, for operating the cloud drive menus. This application is based on the improved method of menu permissions for enterprise cloud disks using small-rooted trees. It adopts a tree structure to construct menus and combines them with a custom authentication model to solve the problems of insufficient recursive query loading of directory points and authentication of directory corresponding positions. The permissions are stored in binary code, which optimizes the permission storage method. At the same time, it meets the needs of enterprise cloud disk customers to display different menus and have different permissions for different positions, improves menu management efficiency, reduces the number of requests, and increases system stability.

[0022] Other features and advantages of the embodiments of this application will be described in detail in the following detailed description section. Attached Figure Description

[0023] The accompanying drawings are provided to further illustrate the embodiments of this application and form part of the specification. They are used together with the following detailed description to explain the embodiments of this application, but do not constitute a limitation on the embodiments of this application. In the drawings: Figure 1 The illustration shows a flowchart of a method for controlling menu permissions in a cloud drive according to an embodiment of this application; Figure 2 A flowchart illustrating an embodiment of this application is shown schematically; Figure 3 This schematic diagram illustrates a structural block diagram of a cloud drive menu permission control device according to an embodiment of this application; Figure 4 The diagram illustrates the internal structure of a computer device according to an embodiment of this application.

[0024] Explanation of reference numerals in the attached figures 100-Cloud Drive menu permission control device; 200 - First Processing Module; 300 - Second processing module; 400 - Third Processing Module; 500 - Fourth Processing Module; 600 - Fifth Processing Module; 700 - Sixth Processing Module. Detailed Implementation

[0025] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. It should be understood that the specific embodiments described herein are only for illustration and explanation of the embodiments of this application and are not intended to limit the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application without creative effort are within the scope of protection of this application.

[0026] It should be noted that if the embodiments of this application involve directional indicators (such as up, down, left, right, front, back, etc.), the directional indicators are only used to explain the relative positional relationship and movement of each component in a certain specific posture (as shown in the figure). If the specific posture changes, the directional indicators will also change accordingly.

[0027] Furthermore, if the embodiments of this application involve descriptions such as "first" or "second," these descriptions are for descriptive purposes only and should not be construed as indicating or implying their relative importance or implicitly specifying the number of technical features indicated. Therefore, features defined with "first" or "second" may explicitly or implicitly include at least one of those features. Additionally, the technical solutions of various embodiments can be combined with each other, but this must be based on the ability of those skilled in the art to implement them. If the combination of technical solutions is contradictory or impossible to implement, it should be considered that such a combination of technical solutions does not exist and is not within the scope of protection claimed in this application.

[0028] The acquisition, transmission, storage, use, and processing of data in this application comply with relevant laws and regulations. Furthermore, it should be noted that certain software, components, models, and other existing industry solutions may be mentioned in the embodiments of this application. These should be considered exemplary, intended only to illustrate the feasibility of implementing the technical solution of this application, and do not imply that the applicant has already used or necessarily used such solutions.

[0029] Figure 1 The illustration shows a flowchart of a method for controlling menu permissions in a cloud drive according to an embodiment of this application. Figure 1 As shown in one embodiment of this application, a method for controlling cloud drive menu permissions is provided, including the following steps: Step S101 involves setting the operation permissions corresponding to the cloud drive menu, which includes sharing, previewing, uploading, downloading, editing, and deleting.

[0030] In one specific implementation, the cloud drive menu is broken down into different atomic operation permissions such as share, preview, upload, download, edit, and delete, and user permissions are stored in binary format. For example, share 1, preview 10, upload 100, download 1000, edit 10000, and delete 100000 correspond to decimal 1, 2, 4, 8, 16, and 32, respectively.

[0031] Specifically, to create operation permissions: Enter the cloud storage platform's backend management system and create permission information, as shown in Table 1.

[0032] Table 1:

[0033] Where id represents a unique identifier, ahr_code represents the English name, ahr_name represents the Chinese name, ahr_mask represents the permission binary value, and status indicates the status: 1 for available and 0 for unavailable.

[0034] Step S102 involves determining all leaf node menus visible to the target user based on the target user's job attributes and job menu mapping rules. Each leaf node menu is the smallest indivisible functional menu unit.

[0035] Specifically, the job attributes include job level, department affiliation, and business function. Menu visibility priority is set based on the job level and department affiliation, and menu visibility filtering conditions are set based on the business function to retain leaf node menus related to the target user's business function. The job menu has a tree-like hierarchical structure, divided into root node, intermediate nodes, and leaf nodes, containing attributes such as menu ID and parent menu ID. Mapping rules include three categories: basic permissions, superimposed permissions, and exclusion permissions, supporting multi-rule combination calculations. First, job attributes are parsed and standardized. After verifying field validity, unstructured function descriptions are mapped to standard codes, and the parsing results are stored in a Redis cache. The mapping rules adopt a four-dimensional structure of rule ID + triggering condition + permission action + priority. The triggering condition is converted into an abstract syntax tree by a syntax parser, executed in descending order of priority, and supports dynamic updates without system restart. Leaf node menu calculation first loads basic permissions, then adds menus according to superimposed rules and removes menus according to exclusion rules, recursively verifies leaf node attributes, and removes duplicates based on menu ID hashing.

[0036] In one specific implementation, a unique identifier ID is assigned to each leaf node menu, and the identifier ID of the non-leaf node menu contains the identifier information of its parent node, forming a hierarchical relationship; visual editing of the menu tree is supported, including adding, deleting, and adjusting the hierarchy of nodes, and the editing operations are synchronized to the permission configuration of the associated users in real time; a menu tree version management mechanism is established to record the content and time of each change to the menu tree, and version rollback operations are supported.

[0037] Specifically, menus are created and values ​​are assigned. Once the entire system menu is created, clicking "Submit" will allow the backend to assign values ​​to each menu item using a tree-structured algorithm and store them in a database table, as shown in Table 2.

[0038] Table 2:

[0039] Menus and job permissions are configured and different menus are assigned to each job through the backend management system to meet the scenario where different jobs can see different menus, as shown in Table 3.

[0040] Table 3:

[0041] Create job permissions: Through the backend management configuration, assign different permission codes to each job to meet the different permission scenarios of different jobs, as shown in Table 4.

[0042] Table 4:

[0043] This method sets menu visibility priority based on job level. Higher-level jobs inherit all visible menus from lower-level jobs by default and can additionally configure their own leaf node menus. It also sets menu visibility filtering conditions based on business functions, retaining only leaf node menus related to the target user's business functions and filtering out irrelevant function menus. It supports batch importing of job-menu mapping relationships, and automatically updates the visible leaf node menus of all associated users when the mapping relationship changes.

[0044] Step S103 involves constructing a menu tree for the target user based on the hierarchical relationship and leaf node menus of the cloud disk menu. Each leaf node menu in the menu tree has a unique binary permission code.

[0045] A tree structure is a hierarchical nested structure. The outer and inner layers of a tree structure have similar structures, so this structure can often be represented recursively. Various tree diagrams in classic data structures are typical tree structures: a tree can be simply represented as a root, left subtree, and right subtree. The left and right subtrees also have their own subtrees. A node represents a data element in the tree, consisting of data items and the relationships between them. In a min-rooted tree, the value of each node is less than or equal to the values ​​of its child nodes.

[0046] According to one specific implementation, each leaf node menu in the menu tree is provided with a unique binary permission code, including: generating a corresponding binary permission code based on the visibility of the leaf node menu in the menu tree; each binary number in the binary permission code corresponds to the visibility permission status of a leaf node menu, 1 for visible and 0 for invisible.

[0047] Specifically, this application uses a tree structure combined with a custom node value algorithm to construct a menu tree. The formula for filling node values ​​is: v= Where v represents the node value, N represents the node level, M represents the radix, and P represents the node position, i.e., the order from left to right. The radix value is the maximum number of child nodes + 1. The leftmost node's sequence number is 0 by default. The system satisfies the condition that the value of the same parent node is less than the value of its child node, and the value of the left node is less than the value of the right node, making the node values ​​of the entire menu tree unique.

[0048] This method employs a variable-length binary encoding method, dynamically adjusting the length of the binary permission code based on the total number of leaf node menus in the menu tree; it adds a check bit to the binary permission code, which is generated based on the XOR operation of all permission bits and is used to verify the integrity of the permission code during transmission or storage; it supports bidirectional conversion between binary permission codes and decimal permission values, facilitating the visualization of permission configuration and storage optimization.

[0049] Step S104 is to establish an association mapping table between the operation permissions and binary permission codes, wherein the association mapping table includes the operation permission combination corresponding to each leaf node menu.

[0050] In one specific implementation, the association mapping table uses leaf node menus as the core association unit, establishing a three-dimensional mapping relationship of menu ID, operation permission combination, and binary permission code to achieve permission digitization and efficient verification. Each leaf node menu is bound to a unique operation permission combination (such as view, add, edit, delete), and a unique binary permission code is assigned to the combination. Bitwise operation logic is used to achieve fast permission calculation and verification.

[0051] Binary permission codes occupy little storage space and have a fast processing speed, making them suitable for high-concurrency scenarios; standardized operation permission combinations ensure mapping consistency; the dynamic maintenance mechanism supports flexible adjustment of menus and permissions, is deeply compatible with the overall permission calculation scheme, and realizes a digital closed loop for the entire process of permission configuration, calculation, and verification.

[0052] Step S105 is to determine the target menu and operation type based on the target user's cloud disk operation request.

[0053] In one specific implementation, user cloud drive requests are first standardized and parsed to extract core fields, including: request path, request method, operation object, and operation behavior description. Abnormal paths directly return an illegal request message. Based on the menu structure and mapping table described earlier, an association index between cloud drive request paths and menu IDs is established and stored in a Redis cache. During matching, a combination of prefix matching and exact matching strategies is used. The menu path is matched precisely using the request path first to obtain the corresponding leaf node menu ID; if no exact match is found, prefix matching is recursively performed according to the path hierarchy. If a match fails, it is determined that there is no corresponding target menu, and the operation request is intercepted. A cloud drive operation type enumeration set is defined, and mapping rules for request methods, behavior descriptions, and operation types are established. During parsing, both request method and behavior description keywords are used for dual judgment to ensure accurate type identification. This method supports expanding the operation type enumeration and path matching rules through the management backend. When adding new cloud drive functions, the corresponding menu and operation type can be quickly associated without modifying the core code. Abnormal scenario handling: Log alarms when the request path is invalid; when the target menu is matched but there is no corresponding operation type, it is mapped to the view type by default; when the menu has been excluded by permissions, return an insufficient permissions prompt directly to improve request processing efficiency.

[0054] Step S106 verifies the target user's visibility and operation permissions based on the target menu, binary permission code, and associated mapping table, for use in operating the cloud drive menu.

[0055] According to one specific implementation, the step of verifying the target user's visibility permissions and operation permissions based on the target menu, binary permission code, and association mapping table, for operating the cloud drive menu, includes: verifying the target user's visibility permissions for the target menu based on the target menu and binary permission code; verifying the target user's operation permissions for the target menu based on the operation type and the association mapping table; and operating the cloud drive menu according to the visibility permissions and operation permissions.

[0056] The step of operating the cloud drive menu based on the user's visibility permissions and user's operation permissions includes: if both the user's visibility permissions and user's operation permissions are verified, then the target user is allowed to operate the target menu.

[0057] For example, after assigning permissions, a bitwise AND operation is performed to determine if the user has permission. For instance, if a user has upload and edit permissions (10100), when a certain atomic permission is needed, the bitwise AND operation is performed between the atomic permission and the user's existing permissions. A result of 0 indicates no permission, while a result greater than 0 indicates the user has the corresponding atomic permission. Share (1): 10100&1=0, then no share permission; Preview (10): 10100&10=0, then no preview permission; Upload (100): 10100&100>0, then upload permission is granted.

[0058] Specifically, such as Figure 2 The method described above stores menu information in a database based on the calculation rules of a min-rooted tree. Atomic permissions are stored in binary format, and different visible menus and atomic operation permissions are set according to different job roles. The backend generates corresponding binary permission codes and stores them in the database. When an enterprise cloud storage customer logs in, the method retrieves the leaf node menu under that user's job role information. The entire min-rooted menu tree is constructed based on the menu values. During construction, the parent node is obtained when the first child node is retrieved; sibling nodes do not require recalculation of the parent node value. Sibling nodes are determined by the range MN to MN+PM. The atomic permission combination code corresponding to the user's job role is retrieved. A return message is then sent to the frontend for processing. The frontend displays the corresponding operation buttons using a binary bitwise AND operation. Finally, the frontend-rendered result is displayed to the enterprise cloud storage customer.

[0059] A database is a repository for data, with a large storage capacity, capable of holding millions, tens of millions, or even hundreds of millions of data entries. Databases don't store data arbitrarily; they follow certain rules, otherwise query efficiency would be very low. A database is a computer software system that stores and manages data according to a data structure. It encompasses two meanings: First, a database is an entity—a repository that can reasonably store data, where users store the transactional data they want to manage. The concepts of data and repository combine to form a database. Second, a database represents a new method and technology for data management, enabling more appropriate organization, more rigorous control, and more efficient utilization of data.

[0060] When a target user belongs to multiple user groups, if there is a conflict between the binary permission codes corresponding to different user groups, the permission configuration of the user group with the higher priority shall be taken according to the user group priority order. If the target user has a personal permission configuration, the personal permission configuration has higher priority than the user group permission configuration, and the personal permission shall prevail in case of conflict. The permission conflict resolution process is automatically logged, including the conflicting permission item, the source of the conflict, and the resolution result, which facilitates permission auditing and traceability.

[0061] The method further includes: monitoring the operation behavior of the target user; when the operation behavior does not meet the permission control dimensions, activating a temporary permission freeze mechanism and generating a permission warning notification; the permission control dimensions include the scope of the operation object, the operation time limit, and the operation frequency threshold.

[0062] Freezing based on operation time limit: When the time of the operation request exceeds the preset valid time period of the atomic operation permission, the corresponding operation permission of the menu is frozen until the next valid time period; Freezing based on operation frequency threshold: When the number of times the same operation is executed within a unit of time reaches or exceeds the preset threshold, the operation permission is frozen for a preset duration, and the freeze duration increases with the number of triggers; The permission freeze status is synchronized to the user operation interface in real time, clearly indicating the reason for the freeze and the unfreezing time.

[0063] This application enables silent login to enterprise cloud storage; it parses user-related information based on the token; if authentication is successful, it parses the user's job title and enterprise cloud storage channel number based on the authentication information; it queries all leaf node menus visible to the customer based on their job title, constructs a menu tree, and adds it to the returned information message; it queries the atomic operation combination permissions the customer possesses based on their job title and adds it to the returned information message; and it displays the menu to the enterprise cloud storage customer after front-end processing based on the permission code and the menu tree. This method is more efficient than the original recursive query for menu construction, reduces the number of requests, and increases system stability. It uses binary codes for permissions, optimizing permission storage and simultaneously meeting the needs of enterprise cloud storage customers to display different menus and have different permissions for different job titles.

[0064] Figure 3 This schematically illustrates a structural block diagram of a cloud drive menu permission control device according to an embodiment of this application, such as... Figure 3 As shown, this application also provides a cloud drive menu permission control device 100, which includes: a first processing module 200, used to set operation permissions corresponding to cloud drive menus, the cloud drive menus including share, preview, upload, download, edit, and delete; a second processing module 300, used to determine all leaf node menus visible to the target user according to the target user's job attributes and job menu mapping rules; a third processing module 400, used to construct a menu tree for the target user based on the hierarchical relationship of the cloud drive menus and the leaf node menus, each leaf node menu in the menu tree having a unique binary permission code; a fourth processing module 500, used to establish an association mapping table of the operation permissions and binary permission codes, the association mapping table including operation permission combinations corresponding to each leaf node menu; a fifth processing module 600, used to determine the target menu and operation type according to the target user's cloud drive operation request; and a sixth processing module 700, used to verify the target user's user visibility permissions and user operation permissions based on the target menu, binary permission code, and association mapping table, and to perform operations on the cloud drive menu.

[0065] Specifically, each leaf node menu in the menu tree has a unique binary permission code, including: generating a corresponding binary permission code based on the visibility of the leaf node menu in the menu tree; each binary digit in the binary permission code corresponds to the visibility permission status of a leaf node menu, with 1 for visible and 0 for invisible.

[0066] This application discloses a method for controlling cloud drive menu permissions, comprising: setting operation permissions corresponding to cloud drive menus, wherein the cloud drive menus include sharing, previewing, uploading, downloading, editing, and deleting; determining all leaf node menus visible to the target user based on the target user's job attributes and job menu mapping rules; constructing a menu tree for the target user based on the hierarchical relationship of the cloud drive menus and the leaf node menus, wherein each leaf node menu in the menu tree has a unique binary permission code; establishing an association mapping table between the operation permissions and the binary permission codes, wherein the association mapping table includes the combination of operation permissions corresponding to each leaf node menu; determining the target menu and operation type based on the target user's cloud drive operation request; and verifying the target user's user visibility permissions and user operation permissions based on the target menu, the binary permission code, and the association mapping table, for operating the cloud drive menus. This application is based on the improved method of menu permissions for enterprise cloud disks using small-rooted trees. It adopts a tree structure to construct menus and combines them with a custom authentication model to solve the problems of insufficient recursive query loading of directory points and authentication of directory corresponding positions. The permissions are stored in binary code, which optimizes the permission storage method. At the same time, it meets the needs of enterprise cloud disk customers to display different menus and have different permissions for different positions, improves menu management efficiency, reduces the number of requests, and increases system stability.

[0067] The cloud disk menu permission control device 100 includes a processor and a memory. The first processing module 200, the second processing module 300, the third processing module 400, the fourth processing module 500, and the fifth processing module 600 are all stored in the memory as program units. The processor executes the program modules stored in the memory to implement the corresponding functions.

[0068] The processor contains a kernel, which retrieves the corresponding program units from memory. One or more kernels can be configured, and methods for controlling cloud drive menu permissions can be implemented by adjusting kernel parameters.

[0069] The memory may include non-permanent memory in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM, and the memory includes at least one memory chip.

[0070] This application provides a storage medium on which a program is stored, which, when executed by a processor, implements the above-described method for controlling cloud disk menu permissions.

[0071] This application provides a processor for running a program, wherein the program executes the above-described cloud disk menu permission control method during runtime.

[0072] In one embodiment, a computer device is provided, which may be a terminal, and its internal structure diagram may be as follows: Figure 4 As shown in the figure, the computer device includes a processor A01, a network interface A02, a display screen A04, an input device A05, and a memory (not shown) connected via a system bus. The processor A01 provides computing and control capabilities. The memory includes internal memory A03 and a non-volatile storage medium A06. The non-volatile storage medium A06 stores an operating system B01 and a computer program B02. The internal memory A03 provides an environment for the operation of the operating system B01 and the computer program B02 stored in the non-volatile storage medium A06. The network interface A02 is used for communication with external terminals via a network connection. When the computer program is executed by the processor A01, it implements a method for managing cloud drive menu permissions. The display screen A04 can be an LCD screen or an e-ink display screen. The input device A05 can be a touch layer covering the display screen, buttons, a trackball, or a touchpad mounted on the computer device casing, or an external keyboard, touchpad, or mouse.

[0073] Those skilled in the art will understand that Figure 4 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0074] In one embodiment, the cloud drive menu permission control device provided in this application can be implemented as a computer program, and the computer program can be implemented in the form of, for example, Figure 4 The cloud drive menu permission control device is run on the computer device shown. The memory of the computer device can store various program modules that constitute the cloud drive menu permission control apparatus. The computer program composed of the various program modules causes the processor to execute the steps of the cloud drive menu permission control method described in the various embodiments of this application.

[0075] This application provides a device including a processor, a memory, and a program stored in the memory and executable on the processor. When the processor executes the program, it performs the following steps: setting operation permissions corresponding to a cloud drive menu, the cloud drive menu including share, preview, upload, download, edit, and delete; determining all leaf node menus visible to the target user based on the target user's job attributes and job menu mapping rules; constructing a menu tree for the target user based on the hierarchical relationship of the cloud drive menu and the leaf node menus, each leaf node menu in the menu tree having a unique binary permission code; establishing an association mapping table between the operation permissions and the binary permission codes, the association mapping table including combinations of operation permissions corresponding to each leaf node menu; determining the target menu and operation type based on the target user's cloud drive operation request; and verifying the target user's visibility permissions and operation permissions based on the target menu, the binary permission code, and the association mapping table, for operating the cloud drive menu.

[0076] This application also provides a computer program product, which, when executed on a data processing device, is suitable for executing an initialization program with the following method steps: setting operation permissions corresponding to a cloud drive menu, wherein the cloud drive menu includes share, preview, upload, download, edit, and delete; determining all leaf node menus visible to the target user based on the target user's job attributes and job menu mapping rules; constructing a menu tree for the target user based on the hierarchical relationship of the cloud drive menu and the leaf node menus, wherein each leaf node menu in the menu tree has a unique binary permission code; establishing an association mapping table between the operation permissions and the binary permission codes, wherein the association mapping table includes the operation permission combination corresponding to each leaf node menu; determining the target menu and operation type based on the target user's cloud drive operation request; and verifying the target user's user visibility permissions and user operation permissions based on the target menu, the binary permission code, and the association mapping table, for operating the cloud drive menu.

[0077] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0078] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0079] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0080] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0081] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0082] Memory may include non-persistent memory in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0083] Computer-readable media include both permanent and non-permanent, removable and non-removable media, which can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0084] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

[0085] The above are merely embodiments of this application and are not intended to limit the scope of this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of the claims of this application.

Claims

1. A method for controlling menu permissions in a cloud drive, characterized in that, The method includes: Configure the operation permissions corresponding to the cloud drive menu, which includes share, preview, upload, download, edit, and delete; Determine all leaf node menus visible to the target user based on the target user's job attributes and job menu mapping rules; Based on the hierarchical relationship and leaf node menus of the cloud disk menu, a menu tree is constructed for the target user, and each leaf node menu in the menu tree is assigned a unique binary permission code; Establish an association mapping table between the operation permissions and binary permission codes, wherein the association mapping table includes the operation permission combination corresponding to each leaf node menu; Determine the target menu and operation type based on the target user's cloud drive operation request; Based on the target menu, binary permission code, and associated mapping table, the user's visibility and operation permissions are verified to operate the cloud drive menu.

2. The method according to claim 1, characterized in that, Each leaf node menu in the menu tree has a unique binary permission code, including: Generate corresponding binary permission codes based on the visibility of the leaf node menus in the menu tree; Each binary digit in the binary permission code corresponds to the visibility permission status of a leaf node menu, with 1 indicating visibility and 0 indicating invisibility.

3. The method according to claim 1, characterized in that, The method also includes: Monitor the target user's operational behavior. When the operational behavior does not meet the permission control dimensions, activate the temporary permission freeze mechanism and generate a permission warning notification. The access control dimensions include the scope of the operation object, the operation time limit, and the operation frequency threshold.

4. The method according to claim 1, characterized in that, The step of verifying the target user's visibility and operation permissions based on the target menu, binary permission code, and associated mapping table, for operating the cloud drive menu, includes: Verify the target user's user visibility permission for the target menu based on the target menu and the binary permission code; Verify the target user's user operation permissions for the target menu based on the operation type and the associated mapping table; The user operates on the cloud drive menu according to the user's visibility and operation permissions.

5. The method according to claim 4, characterized in that, The step of operating the cloud drive menu according to the user's visibility permissions and user operation permissions includes: If both the user's visibility permission and user's operation permission are verified, then the target user is allowed to operate the target menu.

6. The method according to claim 1, characterized in that, The job attributes include job level, department affiliation, and business functions; Menu visibility priority is set based on the job level and department affiliation, and menu visibility filtering conditions are set based on the business function to retain leaf node menus related to the target user's business function.

7. The method according to claim 1, characterized in that, The leaf node menu is the smallest, indivisible functional menu unit.

8. A device for controlling menu permissions in a cloud drive, characterized in that, The device includes: The first processing module is used to set the operation permissions corresponding to the cloud drive menu, which includes share, preview, upload, download, edit, and delete. The second processing module is used to determine all leaf node menus visible to the target user based on the target user's job attributes and job menu mapping rules. The third processing module is used to construct a menu tree for the target user based on the hierarchical relationship and leaf node menus of the cloud disk menu. Each leaf node menu in the menu tree has a unique binary permission code. The fourth processing module is used to establish an association mapping table between the operation permissions and binary permission codes, wherein the association mapping table includes the operation permission combination corresponding to each leaf node menu. The fifth processing module is used to determine the target menu and operation type based on the target user's cloud drive operation request; The sixth processing module is used to verify the target user's visibility permissions and operation permissions based on the target menu, binary permission code, and associated mapping table, and is used to operate the cloud disk menu.

9. The apparatus according to claim 8, characterized in that, Each leaf node menu in the menu tree has a unique binary permission code, including: Generate corresponding binary permission codes based on the visibility of the leaf node menus in the menu tree; Each binary digit in the binary permission code corresponds to the visibility permission status of a leaf node menu, with 1 indicating visibility and 0 indicating invisibility.

10. A processor, characterized in that, Configured to perform the cloud disk menu permission control method according to any one of claims 1 to 7.

11. A machine-readable storage medium storing instructions thereon, characterized in that, When executed by the processor, the instruction causes the processor to be configured to perform the method for controlling cloud disk menu permissions according to any one of claims 1 to 7.

12. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by the processor, it implements the cloud disk menu permission control method as described in any one of claims 1 to 7.

Images