Information processing method and device for three-dimensional design software

By obtaining and monitoring project and domain user information, creating rules to match target permissions, and using domain user identity to manage user login, the timeliness and correctness of permission management in three-dimensional design software is solved, and more efficient permission management is achieved, avoiding Data is corrupted.

CN118259953BActive Publication Date: 2024-11-26INNER MONGOLIA ELECTRIC POWER SURVEY & DESIGN INST
View PDF 9 Cites 0 Cited by

Patent Information

Application Number
CN202410330989.6
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2024-03-22
Publication Date
2024-11-26
Estimated Expiration
2044-03-22

AI Technical Summary

Technical Problem

The permission management of existing three-dimensional design software has timeliness and correctness issues, which are prone to impacting project efficiency and progress due to human misoperation. It also allows multiple machines to log in to the same account at the same time, and log in to the same user with multiple machines, etc., resulting in data corruption.

Method used

By obtaining project information and domain user information, monitoring design task allocation information, creating rules to match target design permissions, using domain user identity to manage user login, eliminating the situation of multi-user login and multi-machine login for the same user, and using ACR rules to manage permissions .

Benefits of technology

It improves the accuracy and timeliness of permission management, avoids artificial misoperation, reduces the requirements for three-dimensional management personnel, and reduces the occurrence of data corruption.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118259953B_ABST
    Figure CN118259953B_ABST
Patent Text Reader

Abstract

The present invention provides an information processing method and device for 3D design software, the method comprising: obtaining engineering project information and domain user information of the 3D design software; obtaining volume information according to the engineering project information; obtaining design task allocation information according to the volume information and domain user information; monitoring the design task allocation information to obtain event type information; creating rules according to the event type information to obtain target design permissions that match the corresponding domain user. The solution of the present invention solves the user identity consistency and user login permission management of the 3D design software; improves the accuracy and timeliness of the permission management of the 3D design software, can effectively avoid the occurrence of human error operation, and reduces the requirements for 3D management personnel.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the technical field of three-dimensional design software authority management, and in particular to an information processing method and device for three-dimensional design software. Background Art

[0002] PDMS (Plant 3D Layout Design Management System) is a powerful 3D layout design software, which is widely used in the engineering design industry. In PDMS, the completion of a 3D design of a project requires the cooperation of dozens of professionals, nearly a hundred 3D volumes, and requires dozens to hundreds of designers. In addition, a project is usually divided into initial design, construction, completion and other stages, and each stage includes planning, modeling, drawing, coordination, review, modification, optimization and other links. For a medium or above project, the PDMS background will form hundreds of user information and nearly a thousand 3D volumes, so PDMS permission management is a very heavy task, and there are often multiple projects advancing at the same time. The workload and importance of PDMS background permission management are self-evident.

[0003] At present, the timeliness and correctness of PDMS permission management completely rely on the administrator. Coupled with the discrete nature of permission management, any negligence may affect the efficiency and progress of the project. At the same time, the default management mechanism of PDMS allows multiple machines to log in to the same account at the same time, and one machine to log in to multiple accounts at the same time. Coupled with abnormal exits, etc., it often leads to project data corruption and affects the progress of the project. Summary of the invention

[0004] The present invention provides an information processing method and device for three-dimensional design software, which solves the consistency of user identities and user login authority management of the three-dimensional design software; improves the accuracy and timeliness of authority management of the three-dimensional design software, can effectively avoid the occurrence of human error operations, and reduces the requirements for three-dimensional management personnel.

[0005] In order to solve the above technical problems, the technical solution of the present invention is as follows:

[0006] An information processing method for three-dimensional design software, comprising:

[0007] Obtain engineering project information and domain user information of 3D design software;

[0008] According to the engineering project information, volume information is obtained;

[0009] According to the volume information and domain user information, design task allocation information is obtained;

[0010] Monitor the design task allocation information to obtain event type information;

[0011] According to the event type information, create rules to obtain the target design permissions that match the corresponding domain users.

[0012] Optionally, obtain domain user information of the 3D design software, including:

[0013] Obtain the domain user identification number of the 3D design software;

[0014] Authenticating the domain user identification number to obtain authentication information;

[0015] A domain user and a software operation user corresponding to the domain user are created according to the authentication information, and the domain user information is obtained.

[0016] Optionally, volume information is obtained according to the engineering project information, including:

[0017] Decomposing the engineering project information into a plurality of design task information;

[0018] Each design task information is encoded to obtain volume information corresponding to each design task information.

[0019] Optionally, obtaining design task allocation information according to the volume information and domain user information includes:

[0020] According to the volume information, the domain user information of the engineering designer required by the design task information corresponding to each volume information is matched and associated to obtain the design task allocation information corresponding to each volume information.

[0021] Optionally, the design task allocation information is monitored to obtain event type information, including:

[0022] The design task allocation information is monitored, and event type information is obtained according to change information of the design task allocation information.

[0023] Optionally, create rules based on event type information to obtain target design permissions that match the corresponding domain user, including:

[0024] The event type information is a permission opening event, and the relationship between the domain user and the volume information is established by configuring permission rules to obtain the target design permission matching the corresponding domain user.

[0025] Optionally, the information processing method further includes:

[0026] Performing judgment processing on the design task allocation information to obtain judgment information;

[0027] According to the judgment information, a path corresponding to the volume information is created or an operation user is created.

[0028] The present invention also provides an information processing device for three-dimensional design software, comprising:

[0029] An acquisition module is used to acquire engineering project information and domain user information of the 3D design software;

[0030] A processing module is used to obtain volume information based on the engineering project information; obtain design task allocation information based on the volume information and domain user information; monitor the design task allocation information to obtain event type information; create rules based on the event type information to obtain target design permissions that match the corresponding domain user.

[0031] The present invention also provides a computing device, comprising: a processor and a memory storing a computer program, wherein when the computer program is executed by the processor, the method described above is executed.

[0032] The present invention also provides a computer-readable storage medium storing instructions, which, when executed on a computer, enable the computer to execute the method described above.

[0033] The above solution of the present invention includes at least the following beneficial effects:

[0034] The above scheme of the present invention obtains project information and domain user information; obtains volume information according to the project information; obtains design task allocation information according to the volume information and domain user information; monitors the design task allocation information to obtain event type information; creates rules according to the event type information to obtain target design permissions that match the corresponding domain user. This solves the user identity consistency and user login permission management of 3D design software; improves the accuracy and timeliness of permission management of 3D design software, can effectively avoid the occurrence of human error operations, and reduces the requirements for 3D management personnel. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] Figure 1 is a flow chart of an information processing method of three-dimensional design software provided by an embodiment of the present invention;

[0036] Figure 2 is a flow chart of an information processing process of an information processing method for three-dimensional design software provided by an embodiment of the present invention;

[0037] Figure 3 is a flow chart of domain user creation and login provided by an embodiment of the present invention;

[0038] Figure 4 is a flowchart of a rights allocation sub-process provided by an embodiment of the present invention;

[0039] Figure 5A module diagram of an information processing device for three-dimensional design software provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0040] The exemplary embodiments of the present invention will be described in more detail below with reference to the accompanying drawings. Although the exemplary embodiments of the present invention are shown in the accompanying drawings, it should be understood that the present invention can be implemented in various forms and should not be limited by the embodiments set forth herein. On the contrary, these embodiments are provided in order to enable a more thorough understanding of the present invention and to enable the scope of the present invention to be fully communicated to those skilled in the art.

[0041] like Figure 1 As shown, an embodiment of the present invention provides an information processing method for three-dimensional design software, comprising:

[0042] Step 11, obtaining engineering project information and domain user information of the 3D design software;

[0043] Step 12, obtaining volume information according to the engineering project information;

[0044] Step 13, obtaining design task allocation information according to the volume information and domain user information;

[0045] Step 14, monitoring the design task allocation information to obtain event type information;

[0046] Step 15: Create a rule based on the event type information to obtain the target design authority that matches the corresponding domain user.

[0047] In this embodiment, the project information and domain user information are obtained; volume information is obtained based on the project information; design task assignment information is obtained based on the volume information and domain user information; the design task assignment information is monitored to obtain event type information; rules are created based on the event type information to obtain target design permissions that match the corresponding domain user; the consistency of user identities and user login permission management of the three-dimensional design software are solved; the accuracy and timeliness of permission management of the three-dimensional design software are improved, the occurrence of human errors can be effectively avoided, and the requirements for three-dimensional management personnel are reduced.

[0048] In an optional embodiment of the present invention, step 11 includes:

[0049] Step 111, obtaining the domain user identification number of the 3D design software;

[0050] Step 112, authenticating the domain user identification number to obtain authentication information;

[0051] Step 113: Create a domain user and a software operation user corresponding to the domain user according to the authentication information, and obtain the domain user information.

[0052] In this embodiment, the domain user information is used as the login identity information of the three-dimensional software PDMS, thereby shielding the original login method of the PDMS software, and managing each user through the domain user account. The user must log in to the computer with the domain user account, and the PDMS software and the project management system both use the domain user identity as the unique identity identifier, which fundamentally prevents the occurrence of multiple users logging in to one PDMS software machine and the same user logging in to a project on multiple machines at the same time, greatly reducing the frequency of data corruption.

[0053] In an optional embodiment of the present invention, step 12 includes:

[0054] Step 121, decomposing the engineering project information into a plurality of design task information;

[0055] Step 122: Encode each design task information to obtain volume information corresponding to each design task information.

[0056] In this embodiment, the engineering project information is decomposed into multiple design task information, and the multiple design task information is encoded using the engineering coding specifications of the survey and design industry to obtain a unique code corresponding to each design task information. In the PDMS software, one Site (path) corresponds to one volume, and the Site is named in the format of "engineering code-volume code-volume name" to achieve mapping between engineering projects and volumes, thereby obtaining the volume information corresponding to each design task information.

[0057] In an optional embodiment of the present invention, step 13 includes:

[0058] Step 131 : According to the volume information, domain user information of the engineering designer required by the design task information corresponding to each volume information is matched and associated to obtain the design task allocation information corresponding to each volume information.

[0059] In this embodiment, the domain user information of the required engineering designers for the design task information corresponding to each volume information is associated to obtain the design task allocation information corresponding to each volume information. Through the above association, the domain user corresponding to each design task is determined, and only the corresponding domain user can log in to the PDMS software to perform the design work of the corresponding design task, which fundamentally prevents the occurrence of multiple users logging in to one PDMS software machine and the same user logging in to a project on multiple machines at the same time.

[0060] In an optional embodiment of the present invention, step 14 includes:

[0061] Step 141, monitoring the design task allocation information, and obtaining event type information according to change information of the design task allocation information.

[0062] In this embodiment, the event type information is obtained by monitoring the change information of the design task allocation information, wherein the event type information includes an authority-on event and an authority-off event.

[0063] In an optional embodiment of the present invention, step 15 includes:

[0064] Step 151, the event type information is a permission opening event, and the relationship between the domain user and the volume information is established by configuring permission rules to obtain the target design permission matching the corresponding domain user.

[0065] In this embodiment, ACR (Access control rule) is used to manage the PDMS software permissions; Figure 2 As shown, when the event type information is a permission opening event, the relationship between the domain user and the volume information is established by configuring the ACR rule, so that the domain user obtains the corresponding target design permission;

[0066] When the event type information is a permission-related event, the design authority of the domain user is revoked by deleting the corresponding ACR rule.

[0067] In an optional embodiment of the present invention, the above method further includes:

[0068] Performing judgment processing on the design task allocation information to obtain judgment information;

[0069] According to the judgment information, a path corresponding to the volume information is created or an operation user is created.

[0070] In this embodiment, if Figure 4 As shown, the design task allocation information is judged and processed to obtain judgment information, wherein the judgment information includes a created Site (path), an uncreated Site (path), a created operating user, and an uncreated operating user;

[0071] The operating user has the identification information of the domain user, and the identification information of the domain user is used to achieve the identity consistency between the operating user and the domain user;

[0072] When the judgment information indicates that the Site (path) has been created and the operating user has been created, ACR rule creation is performed;

[0073] When the judgment information is that the Site (path) has not been created and the operating user has not been created, the Site (path) creation and the operating user creation are performed first, and then the ACR rule creation is performed.

[0074] like Figure 2As shown, in this application, the information processing method of the three-dimensional design software involves a project management system, a domain user login, and a rights management service system, and the specific functions are as follows:

[0075] Project management system: decompose the complete project into multiple sub-projects, encode the design tasks using the engineering coding specifications of the survey and design industry, and name them in the format of "engineering code-volume code-volume name" to achieve mapping between engineering projects and volumes, so as to obtain the volume information corresponding to each design task information; match and associate the domain user information of the required engineering designers with the design task information corresponding to each volume information, and obtain the design task allocation information corresponding to each volume information.

[0076] Domain user login: Shields the native login of PDMS software (PDMS software can only be used through the domain user login); the domain user login enables users to log in to PDMS software as the domain user of the current operating system, fundamentally eliminating the situation where multiple users log in to one PDMS software machine and the same user logs into a project on multiple machines at the same time.

[0077] Permission management service system: real-time monitoring of design task changes in the project management system, automatic synchronization of PDMS software design permissions; users in the project management system are created based on domain user accounts. After design tasks are assigned to designers, the permission management service detects permission changes and automatically assigns design permissions to the designer user in the corresponding project. If the operation user does not exist, you need to create an operation user first. The created operation user is consistent with the domain user account ID; PDMS software permission management mainly manages the relationship between users and volumes. Volumes and the Site structure of PDMS software correspond through volume codes; if the site corresponding to the volume to which permissions are assigned is not created, the site is automatically created and named in the format of "project code-volume code-volume name"; permission management is performed with ACR, and the relationship between domain users and volumes is established by configuring ACR rules to achieve the management of volume design permissions for specific domain users; when assigning permissions, configure an ACR rule to allow the specified domain user to have design permissions for a specific volume. When revoking design permissions, just delete the corresponding ACR rule; the permission management service automatically synchronizes the designer's design permissions for volumes in PDMS software based on the task assignment results of the project management system.

[0078] The information processing process of the information processing method of the three-dimensional design software:

[0079] Create project: project information;

[0080] Volume management: decompose the engineering project information into multiple design task information; encode each design task information to obtain the volume information corresponding to each design task information;

[0081] User management: obtain domain user information;

[0082] Allocating design tasks: According to the volume information, matching and associating the domain user information of the engineering designers required for the design task information corresponding to each volume information, and obtaining the design task allocation information corresponding to each volume information;

[0083] Monitoring task allocation events: monitoring the design task allocation information, and obtaining event type information according to change information of the design task allocation information, wherein the event type information includes an opening authority event and a closing authority event;

[0084] When the event type information is a permission opening event, a relationship between the domain user and the volume information is established by configuring the ACR rule, so that the domain user obtains the corresponding target design permission;

[0085] When the event type information is a permission-related event, the design authority of the domain user is revoked by deleting the corresponding ACR rule.

[0086] like Figure 3 As shown, the user management process:

[0087] Creation of domain user: obtaining a domain user identification number; authenticating the domain user identification number to obtain authentication information; wherein the authentication information is the validity authentication of the domain user identification, and the authentication information includes valid and invalid; when the domain user identification number is invalid, the process ends in failure; when the domain user identification number is valid, the domain user is created;

[0088] Domain user login: read the domain user identification number; authenticate the domain user identification number to obtain authentication information; wherein, the authentication information is the legitimacy of the domain user identification, and the authentication information includes legal and illegal; when the domain user identification number is illegal, the process fails; when the domain user identification number is legal, log in to the project management system or PDMS software.

[0089] Through the above process, the domain user account is used as a unique identity for the PDMS software and project management system: in the LAN environment, each user is managed through the domain user account. The user must log in to the computer with the domain user account. The PDMS software and project management system both use the domain user identity as a unique identity. The user can directly log in to the PDMS software and project management system without entering a user name or password.

[0090] The native login program of PDMS software is blocked, and a domain user login program is developed for PDMS software. PDMS software can only be logged in through the domain user login program. The domain user login program enables users to log in to PDMS software as domain users of the current operating system, which fundamentally prevents the occurrence of multiple users logging in to one PDMS software machine and the same user logging in to one project on multiple machines at the same time.

[0091] Develop permission management services, monitor design task changes in the project management system in real time, and automatically synchronize PDMS software design permissions; conduct secondary development through the Standalone application of PDMS software. The developed application does not need to rely on the main process of PDMS software, and the management of PDMS software 3D design permissions is realized in the periphery;

[0092] The mapping between the project management system and the PDMS software projects and volumes is achieved through globally unique coding. The projects and volumes of the engineering project are coded using the engineering coding specifications of the survey and design industry, which can ensure the uniqueness of the project code. The volume code within the project is unique. When creating a project in the PDMS software, the project code is consistent with the project code in the project management system. One site in the project corresponds to one volume, and the site is named in the format of "project code-volume code-volume name" to achieve the mapping between the project and the volume.

[0093] By configuring ACR rules, the relationship between users and volumes is established to manage volume design permissions for specific users. When assigning permissions, configure an ACR rule to allow a specified user to have design permissions for a specific volume. When revoking design permissions, just delete the corresponding ACR rule. The permission management service automatically synchronizes the design permissions of designers to volumes in the PDMS software based on the task allocation results of the project management system.

[0094] By adopting the information processing method of the present application, automatic permission allocation of PDMS software can be realized, and there is no need for manual permission allocation by personnel, which improves the accuracy and timeliness of three-dimensional software permission management, can effectively avoid the occurrence of human error, and reduces the requirements for three-dimensional management personnel; by configuring ACR rules, a relationship between domain users and volume information is established, so that domain users obtain corresponding target design permissions and log in to PDMS software as domain users, fundamentally eliminating the occurrence of multiple users logging in to one PDMS software machine and the same user logging in to a project on multiple machines at the same time, greatly reducing the frequency of data corruption.

[0095] like Figure 5 As shown, an embodiment of the present invention further provides an information processing device 50 for three-dimensional design software, comprising:

[0096] The acquisition module 51 is used to acquire the engineering project information and domain user information of the three-dimensional design software;

[0097] The processing module 52 is used to obtain volume information based on the engineering project information; obtain design task allocation information based on the volume information and domain user information; monitor the design task allocation information to obtain event type information; create rules based on the event type information to obtain target design permissions that match the corresponding domain user.

[0098] Optionally, obtain domain user information of the 3D design software, including:

[0099] Obtain the domain user identification number of the 3D design software;

[0100] Authenticating the domain user identification number to obtain authentication information;

[0101] A domain user and a software operation user corresponding to the domain user are created according to the authentication information, and the domain user information is obtained.

[0102] Optionally, volume information is obtained according to the engineering project information, including:

[0103] Decomposing the engineering project information into a plurality of design task information;

[0104] Each design task information is encoded to obtain volume information corresponding to each design task information.

[0105] Optionally, obtaining design task allocation information according to the volume information and domain user information includes:

[0106] According to the volume information, the domain user information of the engineering designer required by the design task information corresponding to each volume information is matched and associated to obtain the design task allocation information corresponding to each volume information.

[0107] Optionally, the design task allocation information is monitored to obtain event type information, including:

[0108] The design task allocation information is monitored, and event type information is obtained according to change information of the design task allocation information.

[0109] Optionally, create rules based on event type information to obtain target design permissions that match the corresponding domain user, including:

[0110] The event type information is a permission opening event, and the relationship between the domain user and the volume information is established by configuring permission rules to obtain the target design permission matching the corresponding domain user.

[0111] Optionally, the processing module 52 is further configured to perform judgment processing on the design task allocation information to obtain judgment information; and create a path corresponding to the volume information or create an operation user according to the judgment information.

[0112] It should be noted that the device is a device corresponding to the above method, and all implementation methods in the above method embodiments are applicable to the embodiments of the device and can achieve the same technical effects.

[0113] The embodiment of the present invention further provides a computing device, including: a processor, a memory storing a computer program, and when the computer program is executed by the processor, the method described in the above embodiment is executed. All implementations in the above method embodiment are applicable to this embodiment and can achieve the same technical effect.

[0114] In an embodiment of the present invention, a computer-readable storage medium is further provided, which stores instructions, and when the instructions are executed on a computer, the computer executes the method described in the above embodiment. All implementations in the above method embodiment are applicable to this embodiment, and can also achieve the same technical effect.

[0115] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the present invention.

[0116] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0117] In the embodiments provided by the present invention, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0118] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0119] In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0120] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium, including several instructions for a computer device (which can be a personal computer, server, or network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present invention. The aforementioned storage medium includes: various media that can store program codes, such as USB flash drives, mobile hard disks, ROM, RAM, magnetic disks, or optical disks.

[0121] In addition, it should be noted that in the apparatus and method of the present invention, it is obvious that each component or each step can be decomposed and / or recombined. These decompositions and / or recombinations should be regarded as equivalent schemes of the present invention. Moreover, the steps of performing the above-mentioned series of processing can naturally be performed in chronological order according to the order of description, but it is not necessary to perform them in chronological order, and some steps can be performed in parallel or independently of each other. For those of ordinary skill in the art, it is understood that all or any steps or components of the method and apparatus of the present invention can be implemented in any computing device (including processors, storage media, etc.) or a network of computing devices in hardware, firmware, software or a combination thereof, which can be achieved by those of ordinary skill in the art using their basic programming skills after reading the description of the present invention.

[0122] Therefore, the purpose of the present invention can also be achieved by running a program or a group of programs on any computing device. The computing device can be a well-known general device. Therefore, the purpose of the present invention can also be achieved by simply providing a program product containing a program code that implements the method or device. That is to say, such a program product also constitutes the present invention, and the storage medium storing such a program product also constitutes the present invention. Obviously, the storage medium can be any well-known storage medium or any storage medium developed in the future. It should also be pointed out that in the device and method of the present invention, it is obvious that each component or each step can be decomposed and / or recombined. These decompositions and / or recombinations should be regarded as equivalent schemes of the present invention. In addition, the steps of performing the above-mentioned series of processing can naturally be performed in chronological order according to the order of description, but it is not necessary to perform them in chronological order. Some steps can be performed in parallel or independently of each other.

[0123] The above is a preferred embodiment of the present invention. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present invention. These improvements and modifications should also be regarded as the scope of protection of the present invention.

Claims

1. An information processing method for three-dimensional design software, characterized in that: include: Obtain engineering project information and domain user information of 3D design software; According to the engineering project information, volume information is obtained; According to the volume information and domain user information, design task allocation information is obtained; Monitor the design task allocation information to obtain event type information; According to the event type information, create rules to obtain the target design permissions that match the corresponding domain users; Among them, obtaining domain user information of 3D design software includes: Obtain the domain user identification number of the 3D design software; Authenticating the domain user identification number to obtain authentication information; Creating a domain user and a software operation user corresponding to the domain user according to the authentication information, and obtaining domain user information; Wherein, according to the engineering project information, volume information is obtained, including: Decomposing the engineering project information into a plurality of design task information; Encode each design task information to obtain volume information corresponding to each design task information; Among them, the engineering coding specifications of the survey and design industry are used to encode multiple design task information to obtain a unique code corresponding to each design task information. One site corresponds to one volume, and the site is named in the format of "engineering code-volume code-volume name" to achieve the mapping between engineering projects and volumes, and obtain the volume information corresponding to each design task information; Wherein, obtaining design task allocation information according to the volume information and domain user information includes: According to the volume information, matching and associating the domain user information of the engineering designer required by the design task information corresponding to each volume information, to obtain the design task allocation information corresponding to each volume information; Among them, according to the event type information, create rules to obtain the target design permissions that match the corresponding domain user, including: The event type information is a permission opening event, and the relationship between the domain user and the volume information is established by configuring the permission rules to obtain the target design permission matching the corresponding domain user; The event type information is a permission-related event, and the design permission of the domain user is revoked by deleting the corresponding permission rule.

2. The information processing method of three-dimensional design software according to claim 1, characterized in that: The design task allocation information is monitored to obtain event type information, including: The design task allocation information is monitored, and event type information is obtained according to change information of the design task allocation information.

3. The information processing method of three-dimensional design software according to claim 1, characterized in that: Also includes: Performing judgment processing on the design task allocation information to obtain judgment information; According to the judgment information, a path corresponding to the volume information is created or an operation user is created.

4. An information processing device for three-dimensional design software, characterized in that: include: An acquisition module is used to acquire engineering project information and domain user information of the 3D design software; A processing module, used for obtaining volume information according to the engineering project information; According to the volume information and domain user information, design task allocation information is obtained; Monitor the design task allocation information to obtain event type information; According to the event type information, create rules to obtain the target design permissions that match the corresponding domain users; Among them, obtaining domain user information of 3D design software includes: Obtain the domain user identification number of the 3D design software; Authenticating the domain user identification number to obtain authentication information; Creating a domain user and a software operation user corresponding to the domain user according to the authentication information, and obtaining domain user information; Wherein, according to the engineering project information, volume information is obtained, including: Decomposing the engineering project information into a plurality of design task information; Encode each design task information to obtain volume information corresponding to each design task information; Among them, the engineering coding specifications of the survey and design industry are used to encode multiple design task information to obtain a unique code corresponding to each design task information. One site corresponds to one volume, and the site is named in the format of "engineering code-volume code-volume name" to achieve the mapping between engineering projects and volumes, and obtain the volume information corresponding to each design task information; Wherein, obtaining design task allocation information according to the volume information and domain user information includes: According to the volume information, matching and associating the domain user information of the engineering designer required by the design task information corresponding to each volume information, to obtain the design task allocation information corresponding to each volume information; Among them, according to the event type information, create rules to obtain the target design permissions that match the corresponding domain user, including: The event type information is a permission opening event, and the relationship between the domain user and the volume information is established by configuring the permission rules to obtain the target design permission matching the corresponding domain user; The event type information is a permission-related event, and the design permission of the domain user is revoked by deleting the corresponding permission rule.

5. A computing device, characterized in that: include: A processor and a memory storing a computer program, wherein when the computer program is executed by the processor, the method according to any one of claims 1 to 3 is performed.

6. A computer-readable storage medium, characterized in that: Instructions are stored, and when the instructions are executed on a computer, the computer is caused to execute the method according to any one of claims 1 to 3.

Citation Information

Patent Citations

  • Method for carrying out domain user verification by enterprise software management tool

    CN109309669A

  • Collaborative system application design method, system and device, server and storage medium

    CN111080270A

  • Engineering data management method and device, computer equipment and storage medium

    CN111899000A

  • SonarQube project operation authority configuration method and device

    CN113190861A

  • GIS-based low-altitude airspace collaborative management system

    CN114708751A