Security implementation method, device, equipment and storage medium for collaborative design software
By introducing a load balancing access whitelist mechanism in the collaborative design software, we ensure that only clients with permissions can connect to the application server, solving the security risks of client-to-application server connections, and improving the security and scalability of the system .
Patent Information
- Application Number
- CN202210247320.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2022-03-14
- Publication Date
- 2024-11-12
- Estimated Expiration
- 2042-03-14
AI Technical Summary
The connection between the client and the application server in the collaborative design software lacks protection measures, which poses a major security risk, hinders the scale and data security of BIM collaborative design.
By receiving the client's address query request in the application server gateway, judging user permissions and adding them to the load balancing access whitelist, the client establishes a connection with the load balancing device based on the load balancing information, ensuring that only clients with operational permissions can get the same The application server establishes a connection.
Improves the security performance of collaborative design applications, prevents unauthorized data access, and ensures data security and system scalability.
Smart Images

Figure CN114629704B_ABST
Abstract
Description
Background Art
[0002] With the development of BIM (Building Information Modeling) technology, the application scope of BIM technology is constantly expanding. Due to its characteristics, BIM design can also carry out a series of collaborative designs through the data information in the BIM model. The emergence of collaborative design software has brought new design methods and means to engineering design, especially digital factory design, and also provided basic conditions for realizing the intelligentization of buildings. In the collaborative design software, multiple clients participating in collaborative design can be connected to the application server. There is a lack of protection measures in the connection process between the client and the application server, which poses a great security risk.
[0003] It should be noted that the information disclosed in the above background technology section is only used to enhance the understanding of the background of the present disclosure, and therefore may include information that does not constitute the prior art known to ordinary technicians in the field. Summary of the invention
[0004] The present disclosure provides a method, apparatus, device and storage medium for securely implementing collaborative design software, which at least to a certain extent overcomes the problem in the related art of lack of protective measures during the connection process between the client and the application server, and the existence of significant security risks.
[0005] Other features and advantages of the present disclosure will become apparent from the following detailed description, or may be learned in part by the practice of the present disclosure.
[0006] According to one aspect of the present disclosure, a method for securely implementing collaborative design software is provided, which is applied to an application server gateway, and the method includes:
[0007] Receive an application server address query request sent by a client, where the application server address query request carries a project identifier and a user identifier;
[0008] If the user ID has the operation authority for the design project corresponding to the project ID, the client is added to the load balancing access whitelist;
[0009] The load balancing information corresponding to the application server is sent to the client, so that the client sends a connection request to the load balancing device based on the load balancing information, and the load balancing device determines whether to allow the client to establish a connection with the application server based on the load balancing access whitelist.
[0010] In one embodiment of the present disclosure, if the user identifier has the operation authority of the design project corresponding to the project identifier, adding the client to the load balancing access whitelist includes:
[0011] If the user ID has the operation authority for the design project corresponding to the project ID, obtain the load balancing information corresponding to the application server;
[0012] Add the client to the load balancing access whitelist in the load balancing information.
[0013] In one embodiment of the present disclosure, obtaining load balancing information corresponding to an application server includes:
[0014] According to the project identifier, the load balancing information of the application server corresponding to the project identifier is obtained in a preset project and load balancing configuration table; the project and load balancing configuration table includes multiple projects and the load balancing information corresponding to each project.
[0015] In one embodiment of the present disclosure, the collaborative design software is Revi, the application server is a Revit server, and the application server gateway is a Revit server gateway;
[0016] The client includes a Revit plug-in; the application server address query request is sent by the user to the Revit server gateway through the Revit plug-in.
[0017] According to another aspect of the present disclosure, a method for securely implementing a collaborative design application is provided, which is applied to a client and includes:
[0018] Sending an application server address query request to an application server gateway, the application server address query request carrying a project identifier and a user identifier, so that the application server gateway adds the client to a load balancing access whitelist when the user identifier has operation authority for the design project corresponding to the project identifier;
[0019] Receive the load balancing information corresponding to the application server returned by the application server gateway;
[0020] Based on the load balancing information corresponding to the application server, a connection request for establishing a connection with the application server is generated;
[0021] The connection request is sent to the load balancing device, so that the load balancing device determines whether to allow the client to establish a connection with the application server based on the load balancing access whitelist.
[0022] In one embodiment of the present disclosure, the method further includes:
[0023] The identity information is sent to the identity authentication and permission server. The identity information is used to apply for logging into the collaborative design software.
[0024] In one embodiment of the present disclosure, after logging into the collaborative design software, the method further includes:
[0025] Sending a central file request to the application server, wherein the central file request includes a user identifier;
[0026] The collaborative design software is Revit, the application server is Revit server, and the system where the collaborative design software is located also has Revit server middleware; the Revit server middleware is used to intercept the user ID in the central file request, and obtain the user's permission information from the authentication and permission server based on the user ID, and when the Revit server transmits data to the client, intercept the data that the user does not have the right to access based on the user's permission information.
[0027] According to another aspect of the present disclosure, a collaborative design software system is provided, the system comprising:
[0028] Application server;
[0029] Multiple clients, multiple clients communicate with the application server through the application server gateway;
[0030] The application server gateway is used to execute the above-mentioned secure implementation method of the collaborative design application.
[0031] In one embodiment of the present disclosure, the deployment mode of the application server is cluster deployment.
[0032] In one embodiment of the present disclosure, the system further includes an acceleration server;
[0033] The acceleration server is set between the application server and the client, and is used to synchronize the files of the client to the application server.
[0034] In one embodiment of the present disclosure, the acceleration server is deployed in a cluster.
[0035] In one embodiment of the present disclosure, the system further includes an identity authentication and authorization server; the identity authentication and authorization server is communicatively connected with the application server and the client.
[0036] According to another aspect of the present disclosure, a device for implementing the security of collaborative design software is provided, which is applied to an application server gateway, and the device includes:
[0037] A query request receiving module, used to receive an application server address query request sent by a client, wherein the application server address query request carries a project identifier and a user identifier;
[0038] A whitelist module, used to add the client to the load balancing access whitelist if the user identifier has the operation authority of the design project corresponding to the project identifier;
[0039] The judgment module is used to send the load balancing information corresponding to the application server to the client, so that the client sends a connection request to the load balancing device based on the load balancing information, and the load balancing device judges whether to allow the client to establish a connection with the application server based on the load balancing access whitelist.
[0040] According to another aspect of the present disclosure, a device for securely implementing a collaborative design application is provided, which is applied to a client and includes:
[0041] A query request sending module is used to send an application server address query request to an application server gateway, wherein the application server address query request carries a project identifier and a user identifier, so that the application server gateway adds the client to a load balancing access whitelist when the user identifier has operation authority for the design project corresponding to the project identifier;
[0042] An information receiving module is used to receive the load balancing information corresponding to the application server returned by the application server gateway;
[0043] A connection request generation module, used to generate a connection request for establishing a connection with the application server based on the load balancing information corresponding to the application server;
[0044] The connection request sending module is used to send the connection request to the load balancing device, so that the load balancing device determines whether to allow the client to establish a connection with the application server based on the load balancing access white list.
[0045] According to another aspect of the present disclosure, there is provided an electronic device, comprising: a processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to execute the above-mentioned method for securely implementing a collaborative design application by executing the executable instructions.
[0046] According to another aspect of the present disclosure, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the method for securely implementing the collaborative design application described above is implemented.
[0047] The embodiment of the present disclosure provides a method for implementing the security of collaborative design applications. After receiving an application server address query request, if the user identifier in the request has the operation authority of the design project corresponding to the project identifier, the application server gateway adds the client to the load balancing access whitelist and sends the load balancing information corresponding to the application server to the client. In this way, the client can send a connection request to the load balancing device based on the load balancing information, and the load balancing device can determine whether to allow the client to establish a connection with the application server based on the load balancing access whitelist. When the client is in the load balancing access whitelist, the client is allowed to establish a connection with the application server, thereby improving the security performance of the collaborative design application.
[0048] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS
[0049] The accompanying drawings herein are incorporated into the specification and constitute a part of the specification, illustrate embodiments consistent with the present disclosure, and together with the specification are used to explain the principles of the present disclosure. Obviously, the accompanying drawings described below are only some embodiments of the present disclosure, and for ordinary technicians in this field, other accompanying drawings can be obtained based on these accompanying drawings without creative work.
[0050] Figure 1 A schematic diagram of a collaborative design software working scenario in an embodiment of the present disclosure is shown;
[0051] Figure 2 A schematic diagram showing the structure of a collaborative design software system in an embodiment of the present disclosure is shown;
[0052] Figure 3 A schematic diagram showing the structure of another collaborative design software system in an embodiment of the present disclosure is shown;
[0053] Figure 4 A schematic diagram of a process flow of a method for safely implementing collaborative design software in an embodiment of the present disclosure is shown;
[0054] Figure 5 A schematic diagram of a whitelist generation process in an embodiment of the present disclosure is shown;
[0055] Figure 6 A schematic flow chart of another method for safely implementing collaborative design software in an embodiment of the present disclosure is shown;
[0056] Figure 7 A schematic flow chart of another method for safely implementing collaborative design software in an embodiment of the present disclosure is shown;
[0057] Figure 8A schematic flow chart of a method for safely implementing collaborative design software according to another embodiment of the present disclosure is shown;
[0058] Fig. 9 A schematic diagram of a device for safely implementing collaborative design software in an embodiment of the present disclosure is shown;
[0059] Fig.10 A schematic diagram of another device for safely implementing collaborative design software in an embodiment of the present disclosure is shown;
[0060] Fig.11 A structural block diagram of a computer device in an embodiment of the present disclosure is shown. DETAILED DESCRIPTION
[0061] Example embodiments will now be described more fully with reference to the accompanying drawings. However, example embodiments can be implemented in a variety of forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that the disclosure will be more comprehensive and complete and to fully convey the concepts of the example embodiments to those skilled in the art. The described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.
[0062] In addition, the accompanying drawings are only schematic illustrations of the present disclosure and are not necessarily drawn to scale. The same reference numerals in the figures represent the same or similar parts, and their repeated description will be omitted. Some of the block diagrams shown in the accompanying drawings are functional entities and do not necessarily correspond to physically or logically independent entities. These functional entities can be implemented in software form, or implemented in one or more hardware modules or integrated circuits, or implemented in different networks and / or processor devices and / or microcontroller devices.
[0063] Based on the background technology, it can be known that in the related technology, multiple clients participating in collaborative design in the collaborative design software can be connected to the application server. There is a lack of protection measures during the connection process between the client and the application server, which poses a great security risk.
[0064] The collaborative design software may be BIM design software, such as Revit or CAD, etc. The following description will be made by taking the collaborative design software as Revit software as an example.
[0065] like Figure 1 As shown, using Revit software for work sharing can allow multiple team members 110 to simultaneously process different parts in the same project model 120. However, the inventors found that the design software has the following problems:
[0066] 1. RevitServer is a stateful service and cannot be horizontally expanded;
[0067] 2. The client and RevitServer communicate using TCP protocol, a four-layer network with low operating space;
[0068] 3. The client and RevitServer protocols are not open and cannot be expanded;
[0069] 4. If the number of connections to a single RevitServer exceeds 300, a significant performance bottleneck will occur;
[0070] 5. Whether it is a local area network or an external network, you can connect as long as you know the Revit Server address. There is no identity authentication and data security is not guaranteed.
[0071] The above problems seriously hinder the scale of BIM collaboration. The disclosed embodiment realizes large-scale collaboration based on Revit Server on the basis of data security, which can at least solve the problem of lack of protective measures and major security risks in related technologies.
[0072] The present exemplary implementation is described in detail below with reference to the accompanying drawings and embodiments.
[0073] Figure 2 A collaborative design software system 200 is shown. The collaborative design software system 200 includes an application server 202 and a plurality of clients 204 .
[0074] The deployment mode of the application server 202 is cluster deployment. The application server 202 may be a server cluster or a distributed system composed of multiple servers.
[0075] The plurality of clients 204 are connected to the application server for communication via the application server gateway.
[0076] In some embodiments, the collaborative design software may be Revit software. The client 204 in the foregoing may be a Revit client. The application server 202 may be a Revit server (Revit Server).
[0077] The collaborative design software system provided by the embodiment of the present disclosure implements cluster-like deployment of Revit Server, realizes collaborative load, and improves collaborative scale. The number of clients connected to the Revit server gateway can be greater than 300.
[0078] The application server gateway is located at the network layer, and the network layer may also include a routing management module, a terminal management module, and a security authentication module. The entity structure corresponding to these functional modules may be a proxy server.
[0079] In some embodiments, the collaborative design software system 200 may further include an identity authentication and authority server; the identity authentication and authority server is communicatively connected with the application server and the client.
[0080] The user permission server mainly collects user IDs, sends access tokens according to permission configuration, and provides the ability to determine whether a specified central file can be accessed by a specified user based on the user ID.
[0081] RevitSever permission verification service is a data middle layer, which mainly accepts user ID and token, and accesses the user permission server to obtain permissions, and identifies and controls the data sent by RevitServer to Revit client according to the permissions to achieve the purpose of permission control.
[0082] In order to implement the permission control of the central file, the main work of the Revit client mentioned above is to report the current user identity ID to the permission server and obtain the access token. And send the access token to the RevitServer data interception end.
[0083] Figure 3 Another collaborative design software system provided by the embodiment of the present disclosure is shown. The collaborative design software system 300 is Figure 2 The system shown is similar, wherein the application server 302 and the client 304 correspond to the application server 202 and the client 204 respectively.
[0084] exist Figure 3 The illustrated collaborative design software system 300 also includes an acceleration server 306;
[0085] The acceleration server 306 is disposed between the application server 302 and the client 304 , and the acceleration server 306 can be used to synchronize files of the client 304 to the application server 302 .
[0086] In some embodiments, the acceleration server 306 may be deployed in a cluster.
[0087] The acceleration server 306 is an optional service in the present embodiment. If the collaboration mostly occurs in a local area network, an acceleration server 306 can be added between the application server 302 and the client 304: the system between users in the local area network is faster, and the acceleration server 306 then synchronizes the files to the application server 302, which can also support Internet collaboration.
[0088] exist Figure 3 In the system shown, the client 304 is connected to the application server 302 via a network layer device.
[0089] The network side device may include the application server gateway described above. The entity corresponding to the network side device may be a proxy server.
[0090] The network layer may also include a routing management module, a terminal management module, and a security authentication module.
[0091] The security authentication performed by the security authentication module can be divided into client authentication and server authentication.
[0092] The client completes the user's login. The server implements connection legitimacy verification and data security verification through the network layer. The user needs to log in to the client first and carry the credentials after successful login in the collaborative request. The server verifies the identity and data permissions based on the credentials.
[0093] The application server gateway in the above embodiment can be used to execute the secure implementation method of the collaborative design software provided in the embodiment of the present disclosure.
[0094] Figure 4 A flowchart of a method for safely implementing collaborative design software in an embodiment of the present disclosure is shown. Figure 4 As shown, the method for safely implementing collaborative design software provided in the embodiment of the present disclosure includes the following steps:
[0095] S402, receiving an application server address query request sent by a client, the application server address query request carrying a project identifier and a user identifier;
[0096] S404, if the user identifier has the operation authority for the design project corresponding to the project identifier, adding the client to the load balancing access whitelist;
[0097] S406, sending the load balancing information corresponding to the application server to the client, so that the client sends a connection request to the load balancing device based on the load balancing information, and the load balancing device determines whether to allow the client to establish a connection with the application server based on the load balancing access whitelist.
[0098] The above steps are described in detail below:
[0099] In the above S402, the client needs to obtain corresponding address information before connecting to the application server. In the embodiment of the present disclosure, a load balancing device is provided between the client and the application server, and the client can connect to the application server through the load balancing device.
[0100] Here, the load balancing device can be set in the proxy server mentioned above.
[0101] The project identifier is the identification information of the design project, which is also the identification information of the project model introduced in the previous article.
[0102] The user identification may be identification information of a user who logs into the client.
[0103] In the above S404, it can be determined whether the user identifier has the operation authority of the design project corresponding to the project identifier according to the preset user-project association relationship table.
[0104] In the case of multiple servers providing the same service, there is a VIP on the load balancing device. When a large number of clients access the VIP address from the outside, the load balancing device will distribute these message requests to the background servers according to the load balancing algorithm to balance the load pressure of each server, so as to avoid other services reaching the performance critical point and running slowly or even crashing when there are still servers with less pressure, thereby improving service efficiency and quality. Therefore, for the client, the IP address of the application server can be the VIP address of the load balancing device.
[0105] The load balancing information in S406 includes the address of the load balancing device corresponding to the application server, and the client needs to connect to the application server through the load balancing device.
[0106] The load balancing device can determine whether the client sending the connection request is in the load balancing access whitelist. If the client is in the load balancing access whitelist, the client is allowed to establish a connection with the application server; if the client is not in the load balancing access whitelist, the client is not allowed to establish a connection with the application server.
[0107] The embodiment of the present disclosure provides a method for securely implementing collaborative design software. The load balancing device can determine whether to allow the client to establish a connection with the application server through a load balancing access whitelist, thereby improving the security performance of the collaborative design application.
[0108] In some embodiments, Figure 5 As shown, the above S404 may include:
[0109] S4041, if the user identifier has the operation authority of the design project corresponding to the project identifier, obtain the load balancing information corresponding to the application server;
[0110] S4042, adding the client to the load balancing access whitelist in the load balancing information.
[0111] The load balancing information may be obtained from a preset project and load balancing configuration table according to the project identifier. The load balancing information is the load balancing information of the application server corresponding to the project identifier.
[0112] The project and load balancing configuration table may include multiple projects and the load balancing information corresponding to each project. The load balancing information here may include the address information of the load balancing device. The client may request to establish a connection with the load balancing device, and then establish a connection with the corresponding application server. The load balancing device may then determine whether to allow it to establish a connection relationship based on the load balancing access whitelist.
[0113] The method for securely implementing collaborative design software provided by the embodiment of the present disclosure establishes a security mechanism at the network layer, and ensures a secure connection between the client and the application server through the network layer device application server gateway and load balancing device.
[0114] In some embodiments, the collaborative design software in the above steps may be the Revit software introduced above. Accordingly, the client may be a Revit client, and the application server may be a Revit server (RevitSever). The client may include a Revit plug-in, and the application server address query request may be sent by the user to the Revit server gateway (RS gateway) through the Revit plug-in.
[0115] The following is combined with Figure 6 The following describes a method for implementing the collaborative design software security in an embodiment of the present disclosure. Figure 6 As shown, the method comprises the following steps:
[0116] S601, query RS address according to project ID;
[0117] The user can send an RS address query request to the RS gateway through the Revit plug-in, which is the application server address query request in S402 above. The specific implementation method of this step refers to the introduction of the application server address query request above, which will not be repeated here.
[0118] S602, RS gateway determines the user's project operation authority;
[0119] After receiving the query request, the RS gateway can determine whether the user sending the request has the authority for the project based on the association relationship between the user and the project.
[0120] S603, after the permission is granted, the corresponding SLB information (load balancing information) is obtained according to the configuration table;
[0121] The configuration table is the project and load balancing configuration table mentioned above, which may include multiple projects and the load balancing information corresponding to each project.
[0122] S604, adding the user client to the whitelist;
[0123] S605, adding the client information to the SLB access whitelist;
[0124] S606, maintaining the association information between the client and the RS;
[0125] The above steps are used to maintain and build the SLB access whitelist, which provides reliable information for security verification in the following steps.
[0126] S607, returning the SLB connection information corresponding to the connected RS;
[0127] The SLB connection information returned here may include the address information of the load balancing device. For the client, the IP address of the application server may be the VIP address of the load balancing device.
[0128] S608, Revit plug-in initiates a connection request;
[0129] The client can request to establish a connection with the load balancing device, and then establish a connection with the corresponding application server.
[0130] S609, SLB verification whitelist;
[0131] The load balancing device can determine whether to allow it to establish a connection relationship based on the load balancing access whitelist.
[0132] S610, RevitSever establishes connection.
[0133] It should be noted that the number of clients connected to the Revit server gateway in the embodiment of the present disclosure can be greater than 300.
[0134] The disclosed embodiment implements the collaborative capability of Revit Server through network layer extension and implements data security through network layer proxy authentication.
[0135] Based on the same inventive concept, the embodiment of the present disclosure also provides a method for safely implementing a collaborative design application, which is applied to a client, such as Figure 7 As shown, the method includes:
[0136] S702, sending an application server address query request to the application server gateway, the application server address query request carrying a project identifier and a user identifier, so that the application server gateway adds the client to the load balancing access whitelist when the user identifier has the operation authority of the design project corresponding to the project identifier;
[0137] S704, receiving load balancing information corresponding to the application server returned by the application server gateway;
[0138] S706, generating a connection request for establishing a connection with the application server based on the load balancing information corresponding to the application server;
[0139] S708: Send the connection request to the load balancing device, so that the load balancing device determines whether to allow the client to establish a connection with the application server based on the load balancing access whitelist.
[0140] In some embodiments, the method may further include:
[0141] The identity information is sent to the identity authentication and permission server. The identity information is used to apply for logging into the collaborative design software.
[0142] After the authentication and authorization server passes the verification, the user is allowed to log in to the client, and then the user can communicate with the proxy server through the client, that is, it can communicate with the application server gateway mentioned above. Figure 8 The collaborative design process of the embodiment of the present disclosure is described after the user logs in to the client.
[0143] like Figure 8 As shown, the method may include the following steps:
[0144] S801, sending user ID;
[0145] The Revit client submits user identity information to the authentication and authorization server and applies for login.
[0146] S802, application center file;
[0147] S803, read the application and user ID;
[0148] After logging into the Revit client, a central file request is sent to the application server, and the central file request includes a user ID;
[0149] When a user needs to access the central file of a model, the Revit client sends a central file request to the Revit Server. At this time, the Revit Server middleware intercepts the file read application request and obtains the user information, that is, the user ID.
[0150] S804, obtaining central file access rights;
[0151] S805, intercepting data according to authority;
[0152] RevitServer is ready to return all model information to the user. At this time, the RevitServer middleware requests the corresponding user's permission information from the authentication and permission server based on the user ID obtained in the previous step. And based on the permission information, it intercepts the model data that the user does not have access to. When the Revit server transmits data to the client, it intercepts the data that the user does not have access to based on the user's permission information.
[0153] S806, the central file data after permission filtering is sent to the client.
[0154] Users can only obtain information about models that they have permission to access.
[0155] Based on the same inventive concept, the embodiments of the present disclosure also provide a device for safely implementing collaborative design software, as described in the following embodiments. Since the principle of solving the problem in the device embodiment is similar to that in the above method embodiment, the implementation of the device embodiment can refer to the implementation of the above method embodiment, and the repeated parts will not be repeated.
[0156] Fig. 9 A schematic diagram of a device for implementing a collaborative design software security in an embodiment of the present disclosure is shown. The device is applied to an application server gateway. Fig. 9 As shown, the collaborative design software security implementation device 900 includes:
[0157] The query request receiving module 902 is used to receive an application server address query request sent by a client, wherein the application server address query request carries a project identifier and a user identifier;
[0158] A whitelist module 904, for adding the client to a load balancing access whitelist if the user identifier has operation authority for the design project corresponding to the project identifier;
[0159] The judgment module 906 is used to send the load balancing information corresponding to the application server to the client, so that the client sends a connection request to the load balancing device based on the load balancing information, and the load balancing device determines whether to allow the client to establish a connection with the application server based on the load balancing access whitelist.
[0160] In some embodiments, the whitelist module 904 may be specifically used to:
[0161] If the user ID has the operation authority for the design project corresponding to the project ID, obtain the load balancing information corresponding to the application server;
[0162] Add the client to the load balancing access whitelist in the load balancing information.
[0163] In some embodiments, obtaining load balancing information corresponding to an application server may include:
[0164] According to the project identifier, the load balancing information of the application server corresponding to the project identifier is obtained in a preset project and load balancing configuration table; the project and load balancing configuration table includes multiple projects and the load balancing information corresponding to each project.
[0165] In some embodiments, the collaborative design software may be Revi, the application server may be a Revit server, and the application server gateway may be a Revit server gateway;
[0166] The client includes a Revit plug-in; the application server address query request is sent by the user to the Revit server gateway through the Revit plug-in.
[0167] The secure implementation device for collaborative design applications provided in the embodiments of the present application can be used to execute the secure implementation methods for collaborative design applications provided in the above-mentioned method embodiments. The implementation principles and technical effects are similar and will not be described in detail here for the sake of simplicity.
[0168] Based on the same inventive concept, the embodiment of the present disclosure also provides a secure implementation device for collaborative design application, which is applied to a client, such as Fig.10 As shown, the collaborative design software security implementation device 1000 includes:
[0169] The query request sending module 1002 is used to send an application server address query request to the application server gateway, wherein the application server address query request carries a project identifier and a user identifier, so that the application server gateway adds the client to the load balancing access whitelist when the user identifier has the operation authority of the design project corresponding to the project identifier;
[0170] The information receiving module 1004 is used to receive the load balancing information corresponding to the application server returned by the application server gateway;
[0171] A connection request generating module 1006, configured to generate a connection request for establishing a connection with the application server based on the load balancing information corresponding to the application server;
[0172] The connection request sending module 1008 is used to send the connection request to the load balancing device, so that the load balancing device determines whether to allow the client to establish a connection with the application server based on the load balancing access whitelist.
[0173] In some embodiments, the collaborative design software security implementation device 1000 may further include:
[0174] The identity information sending module is used to send identity information to the identity authentication and authority server, and the identity information is used to apply for logging into the collaborative design software.
[0175] In some embodiments, the collaborative design software security implementation device 1000 may further include:
[0176] A file request module, used to send a central file request to the application server after logging into the collaborative design software, wherein the central file request includes a user identifier;
[0177] The collaborative design software may be Revit, the application server may be a Revit server, and the system where the collaborative design software is located may also be provided with a Revit server middleware;
[0178] The Revit server middleware is used to intercept the user ID in the central file request and obtain the user's permission information from the authentication and permission server based on the user ID. When the Revit server transmits data to the client, it intercepts data that the user does not have access to based on the user's permission information.
[0179] The secure implementation device for collaborative design applications provided in the embodiments of the present application can be used to execute the secure implementation methods for collaborative design applications provided in the above-mentioned method embodiments. The implementation principles and technical effects are similar and will not be described in detail here for the sake of simplicity.
[0180] Those skilled in the art will appreciate that various aspects of the present disclosure may be implemented as systems, methods or program products. Therefore, various aspects of the present disclosure may be specifically implemented in the following forms, namely: complete hardware implementation, complete software implementation (including firmware, microcode, etc.), or a combination of hardware and software, which may be collectively referred to herein as "circuits", "modules" or "systems".
[0181] Refer to the following Fig.11 1100 according to this embodiment of the present disclosure is described. Fig.11 The electronic device 1100 shown is merely an example and should not bring any limitation to the functions and scope of use of the embodiments of the present disclosure.
[0182] like Fig.11 As shown, the electronic device 1100 is in the form of a general computing device. The components of the electronic device 1100 may include but are not limited to: at least one processing unit 1110, at least one storage unit 1120, and a bus 1130 connecting different system components (including the storage unit 1120 and the processing unit 1110).
[0183] The storage unit stores program codes, which can be executed by the processing unit 1110, so that the processing unit 1110 executes the steps described in the above “exemplary method” section of this specification according to various exemplary embodiments of the present disclosure.
[0184] In some embodiments, the processing unit 1110 may be applied to an application server gateway to perform the following steps of the above method embodiment:
[0185] Receive an application server address query request sent by a client, where the application server address query request carries a project identifier and a user identifier;
[0186] If the user ID has the operation authority for the design project corresponding to the project ID, the client is added to the load balancing access whitelist;
[0187] The load balancing information corresponding to the application server is sent to the client, so that the client sends a connection request to the load balancing device based on the load balancing information, and the load balancing device determines whether to allow the client to establish a connection with the application server based on the load balancing access whitelist.
[0188] In some embodiments, the processing unit 1110 may be applied to a client to perform the following steps of the above method embodiment:
[0189] Sending an application server address query request to an application server gateway, the application server address query request carrying a project identifier and a user identifier, so that the application server gateway adds the client to a load balancing access whitelist when the user identifier has operation authority for the design project corresponding to the project identifier;
[0190] Receive the load balancing information corresponding to the application server returned by the application server gateway;
[0191] Based on the load balancing information corresponding to the application server, a connection request for establishing a connection with the application server is generated;
[0192] The connection request is sent to the load balancing device, so that the load balancing device determines whether to allow the client to establish a connection with the application server based on the load balancing access whitelist.
[0193] The storage unit 1120 may include a readable medium in the form of a volatile storage unit, such as a random access storage unit (RAM) 11201 and / or a cache storage unit 11202 , and may further include a read-only storage unit (ROM) 11203 .
[0194] The storage unit 1120 may also include a program / utility 11204 having a set (at least one) of program modules 11205, such program modules 11205 including but not limited to: an operating system, one or more application programs, other program modules, and program data, each of which or some combination may include an implementation of a network environment.
[0195] Bus 1130 may represent one or more of several types of bus structures, including a memory unit bus or memory unit controller, a peripheral bus, an accelerated graphics port, a processing unit, or a local bus using any of a variety of bus architectures.
[0196] The electronic device 1100 may also communicate with one or more external devices 1140 (e.g., keyboards, pointing devices, Bluetooth devices, etc.), one or more devices that enable a user to interact with the electronic device 1100, and / or any device that enables the electronic device 1100 to communicate with one or more other computing devices (e.g., routers, modems, etc.). Such communication may be performed through an input / output (I / O) interface 1150.
[0197] Furthermore, the electronic device 1100 can also communicate with one or more networks (eg, a local area network (LAN), a wide area network (WAN) and / or a public network, such as the Internet) through the network adapter 1160 .
[0198] like Fig.11 As shown, the network adapter 1160 communicates with other modules of the electronic device 1100 via the bus 1130 .
[0199] It should be understood that although not shown in the figures, other hardware and / or software modules may be used in conjunction with the electronic device 1100, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.
[0200] Through the description of the above implementation, it is easy for those skilled in the art to understand that the example implementation described here can be implemented by software, or by software combined with necessary hardware. Therefore, the technical solution according to the implementation of the present disclosure can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a USB flash drive, a mobile hard disk, etc.) or on a network, including several instructions to enable a computing device (which can be a personal computer, a server, a terminal device, or a network device, etc.) to execute the method according to the implementation of the present disclosure.
[0201] In an exemplary embodiment of the present disclosure, a computer-readable storage medium is further provided, which may be a readable signal medium or a readable storage medium, on which a program product capable of implementing the above method of the present disclosure is stored.
[0202] In some possible implementations, various aspects of the present disclosure may also be implemented in the form of a program product, which includes program code. When the program product is run on a terminal device, the program code is used to enable the terminal device to execute the steps of various exemplary implementations of the present disclosure described in the above “Exemplary Method” section of this specification.
[0203] More specific examples of computer-readable storage media in the present disclosure may include, but are not limited to, an electrical connection having one or more conductors, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
[0204] In the present disclosure, the computer-readable storage medium may include a propagated data signal in baseband or as part of a carrier wave, with the readable program code carried therein.
[0205] Such a propagated data signal may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the foregoing.
[0206] Readable signal media may also be any readable media other than readable storage media that can send, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
[0207] In some examples, the program code contained on a computer-readable storage medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
[0208] In a specific implementation, the program code for performing the operations of the present disclosure may be written in any combination of one or more programming languages, including object-oriented programming languages such as Java, C++, etc., and conventional procedural programming languages such as "C" language or similar programming languages.
[0209] The program code may execute entirely on the user's computing device, partly on the user's computing device, as a stand-alone software package, partly on the user's computing device and partly on a remote computing device or entirely on the remote computing device or server.
[0210] Where a remote computing device is involved, the remote computing device may be connected to the user computing device through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computing device (e.g., through the Internet using an Internet service provider).
[0211] It should be noted that, although several modules or units of the device for action execution are mentioned in the above detailed description, such division is not mandatory.
[0212] In fact, according to the embodiments of the present disclosure, the features and functions of two or more modules or units described above can be embodied in one module or unit. Conversely, the features and functions of one module or unit described above can be further divided into multiple modules or units to be embodied.
[0213] In addition, although the steps of the method in the present disclosure are described in a specific order in the drawings, this does not require or imply that the steps must be performed in this specific order, or that all the steps shown must be performed to achieve the desired results. Additionally or alternatively, some steps may be omitted, multiple steps may be combined into one step, and / or one step may be decomposed into multiple steps, etc.
[0214] Through the description of the above implementation modes, it is easy for those skilled in the art to understand that the example implementation modes described here can be implemented by software, or by combining software with necessary hardware.
[0215] Therefore, the technical solution according to the embodiment of the present disclosure can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a USB flash drive, a mobile hard disk, etc.) or on a network, and includes a number of instructions to enable a computing device (which can be a personal computer, a server, a mobile terminal, or a network device, etc.) to execute the method according to the embodiment of the present disclosure.
[0216] Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein.
[0217] The present disclosure is intended to cover any variation, use or adaptation of the present disclosure, which follows the general principles of the present disclosure and includes common knowledge or customary technical means in the technical field not disclosed in the present disclosure. The description and examples are to be regarded as exemplary only, and the true scope and spirit of the present disclosure are indicated by the appended claims.
Claims
1. A method for safely implementing collaborative design software, characterized in that: Applied to an application server gateway, the method comprises: Receive an application server address query request sent by a client, wherein the application server address query request carries a project identifier and a user identifier; If the user identifier has the operation authority for the design project corresponding to the project identifier, adding the client to the load balancing access whitelist; Sending the load balancing information corresponding to the application server to the client, so that the client sends a connection request to the load balancing device based on the load balancing information, and the load balancing device determines whether to allow the client to establish a connection with the application server based on the load balancing access whitelist; The load balancing information includes the address of the load balancing device corresponding to the application server.
2. The method according to claim 1, characterized in that If the user identifier has the operation authority of the design project corresponding to the project identifier, adding the client to the load balancing access whitelist includes: If the user identifier has the operation authority for the design project corresponding to the project identifier, obtaining the load balancing information corresponding to the application server; The client is added to the load balancing access whitelist in the load balancing information.
3. The method according to claim 2, characterized in that The obtaining of load balancing information corresponding to the application server includes: According to the project identifier, the load balancing information of the application server corresponding to the project identifier is obtained in a preset project and load balancing configuration table; the project and load balancing configuration table includes multiple projects and the load balancing information corresponding to each project.
4. The method according to any one of claims 1 to 3, characterized in that: The collaborative design software is Revit, the application server is a Revit server, and the application server gateway is a Revit server gateway; The client includes a Revit plug-in; the application server address query request is sent by the user to the Revit server gateway through the Revit plug-in.
5. A method for securely implementing collaborative design applications, characterized in that: Applied to a client, the method comprises: Sending an application server address query request to an application server gateway, wherein the application server address query request carries a project identifier and a user identifier, so that the application server gateway adds the client to a load balancing access whitelist when the user identifier has operation authority for the design project corresponding to the project identifier; Receive load balancing information corresponding to the application server returned by the application server gateway; Based on the load balancing information corresponding to the application server, generating a connection request for establishing a connection with the application server; Sending the connection request to a load balancing device, so that the load balancing device determines whether to allow the client to establish a connection with the application server based on the load balancing access whitelist; The load balancing information includes the address of the load balancing device corresponding to the application server.
6. The method according to claim 5, characterized in that The method further comprises: The identity information is sent to the identity authentication and authority server, and the identity information is used to apply for logging into the collaborative design software.
7. The method according to claim 6, characterized in that After logging into the collaborative design software, the method further includes: Sending a central file request to an application server, wherein the central file request includes a user identifier; The collaborative design software is Revit, the application server is a Revit server, and the system where the collaborative design software is located is also equipped with a Revit server middleware; the Revit server middleware is used to intercept the user identifier in the central file request, and obtain the user's permission information from the identity authentication and permission server according to the user identifier, and when the Revit server transmits data to the client, intercept the data that the user does not have the right to access according to the user's permission information.
8. A collaborative design software system, characterized in that: The system comprises: Application server; A plurality of clients, wherein the plurality of clients are communicatively connected with the application server via an application server gateway; The application server gateway is used to execute the method described in any one of claims 1-4.
9. The system according to claim 8, characterized in that The deployment mode of the application server is cluster deployment.
10. The system according to claim 8, characterized in that The system also includes an acceleration server; The acceleration server is arranged between the application server and the client, and is used to synchronize the files of the client to the application server.
11. The system according to claim 10, characterized in that The acceleration server is deployed in a cluster.
12. The system according to claim 8, characterized in that The system further comprises an identity authentication and authorization server; the identity authentication and authorization server is communicatively connected with the application server and the client.
13. A device for implementing the security of collaborative design software, characterized in that: Applied to an application server gateway, the device comprises: A query request receiving module, used to receive an application server address query request sent by a client, wherein the application server address query request carries a project identifier and a user identifier; A whitelist module, configured to add the client to a load balancing access whitelist if the user identifier has operation authority for the design project corresponding to the project identifier; A judgment module, used to send the load balancing information corresponding to the application server to the client, so that the client sends a connection request to the load balancing device based on the load balancing information, and the load balancing device judges whether to allow the client to establish a connection with the application server based on the load balancing access whitelist; The load balancing information includes the address of the load balancing device corresponding to the application server.
14. A secure implementation device for collaborative design application, characterized in that: Applied to a client, the device comprises: A query request sending module, used to send an application server address query request to an application server gateway, wherein the application server address query request carries a project identifier and a user identifier, so that the application server gateway adds the client to a load balancing access whitelist when the user identifier has operation authority for the design project corresponding to the project identifier; An information receiving module, used to receive the load balancing information corresponding to the application server returned by the application server gateway; A connection request generation module, used to generate a connection request for establishing a connection with an application server based on the load balancing information corresponding to the application server; A connection request sending module, used to send the connection request to the load balancing device, so that the load balancing device determines whether to allow the client to establish a connection with the application server based on the load balancing access whitelist; The load balancing information includes the address of the load balancing device corresponding to the application server.
15. An electronic device, characterized in that: include: processor; as well as A memory, configured to store executable instructions of the processor; Wherein, the processor is configured to execute the method for securely implementing collaborative design software as described in any one of claims 1-7 by executing the executable instructions.
16. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the method for securely implementing collaborative design software described in any one of claims 1 to 7 is implemented.
Citation Information
Patent Citations
Allopatry collaborative design informatization platform based on Web
CN101794314A
Remote collaborative design method and system based on BIM cloud collaborative platform
CN109087057A
Collaborative system application design method, system and device, server and storage medium
CN111080270A
Cross-domain collaborative interaction method based on collaborative gateway
CN111083177A
Multi-user real-time synchronous collaborative map editing method and system considering geographic features
CN112070861A
