A water transport engineering auxiliary design system platform and design method based on AR

Through the AR-based water transport engineering auxiliary design system platform, the design plan is combined with the on-site environment in real time, solving the problem of information island effect in traditional water transport engineering design, improving the quality and construction efficiency of the design plan, and avoiding construction caused by design errors change.

CN118153153BActive Publication Date: 2024-12-06ANHUI PROVINCIAL TRANSPORTATION SURVEY & DESIGN INST CO LTD
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202410208408.1
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2024-02-26
Publication Date
2024-12-06
Estimated Expiration
2044-02-26

AI Technical Summary

Technical Problem

There is an information island effect between the design plan and the on-site environment in traditional water transport engineering design, resulting in design errors and construction changes, resulting in economic and construction losses.

Method used

Adopt AR-based water transport engineering auxiliary design system platform, including private cloud subsystem, management subsystem, internal subsystem and field subsystem, and combine design solutions with real scenes through AR technology to achieve real-time comparison between design solutions and on-site environments. Select and review to improve the quality of design plans.

Benefits of technology

It effectively solves the information island problem between the design plan and the on-site environment, improves the correctness of the design plan review and construction efficiency, avoids plan changes during construction, and ensures the matching of the design plan and on-site conditions.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118153153B_ABST
    Figure CN118153153B_ABST
Patent Text Reader

Abstract

The present invention discloses a water transport engineering auxiliary design system platform and a design method based on AR. The system platform includes a private cloud subsystem, a management subsystem, an internal subsystem and an external subsystem. By utilizing the information integration capability of the existing AR technology and expressing the water transport engineering design scheme through BIM technology, the water transport infrastructure design scheme can be efficiently reviewed and compared at the project site, and the design errors and hidden dangers in the engineering scheme can be eliminated in the design stage.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of engineering auxiliary design and software development, and in particular to an AR-based water transport engineering auxiliary design system platform and a design method. Background Art

[0002] Water transport engineering includes coastal, offshore or inland river engineering such as ports, waterways, breakwaters (sand dikes), revetments (seawalls), ship locks (navigation structures), docks, etc., serving the water transport industry. Engineering design is an important part of the basic construction process of water transport engineering.

[0003] At present, in traditional engineering design work, it is necessary to first conduct surveying and mapping at the project site to form topographic drawings and materials. Designers design, compare and review engineering plans based on the site topographic map. Since the site conditions are easily affected by natural and human activity conditions, coupled with the subjective influence of designers and reviewers, some important topographic details in the site plan drawings are easily ignored, resulting in an information island effect between the design plan and the site environment, causing the design plan to be inconsistent with the site conditions. Design errors are brought into the construction stage, resulting in plan changes, causing economic and construction period losses. Summary of the invention

[0004] In order to overcome the shortcomings of the existing water transport engineering design stage, the present invention provides an AR-based water transport engineering auxiliary design system platform and design method, which can combine the design plan with the real scene of the engineering site, discover the conflict between the design plan and the on-site environment, solve the information island problem between the changing on-site environment and the design plan, realize efficient comparison and review of the plans in the design stage, improve the quality of the design plan, and avoid plan changes during construction.

[0005] The technical solution adopted by the present invention to solve the above technical problems is:

[0006] An AR-based water transport engineering auxiliary design system platform, including a private cloud subsystem, a management subsystem, an internal subsystem and an external subsystem;

[0007] The private cloud subsystem is the backend system of the entire platform, providing logical organization, storage, external access to engineering design solutions, and cloud processing functions related to platform design solutions;

[0008] The management subsystem is a front-end system used by system administrators, providing platform management system user login, user configuration, project organization and management, project model, and field record addition, deletion, and modification functions;

[0009] The office subsystem is a front-end system used by designers, providing user login, engineering project management, engineering model addition, deletion and modification functions, and field data management functions for the office platform system;

[0010] The field subsystem is a mobile front-end system used by designers, which provides user login to the internal platform system, GIS project navigation, AR and solution integration with real scenes, and the functions of adding, deleting and modifying data related to field records.

[0011] Further technology of the present invention: the private cloud subsystem includes a rights management module, an access control module, a data management module and a function processing module;

[0012] The authority management module provides the management function of the entire system users and user-related system permissions. The access control module provides the user's corresponding permission judgment function to access each function. The data management module provides the storage of system user-related information, the logical organization, storage, and external access functions of the engineering design plan. The function processing module provides cloud processing functions related to the platform design plan.

[0013] The access control module is the entrance to external access. It passes the permission information in the external request to the permission management module for verification. If the verification fails, an error code is returned. If the verification passes, the request is transferred to the data management module or the function processing module for processing according to the content of the external request. After the processing is completed, the result is returned and the request ends.

[0014] The management subsystem includes system login module, user management module, model metadata management module and data management module;

[0015] The system login module provides the user login function of the platform management system, the user management module provides the configuration function of system users, the model metadata management module provides the hierarchical organization and management function of engineering projects, and the data management module provides the engineering design scheme related models and field record addition, deletion and modification functions.

[0016] The system login module is the entrance for managing user access. It converts the user's login information into an external request and sends it to the private cloud subsystem. If the verification fails, an error code is returned. If the verification passes, it turns to the user management module, model metadata management module or data management module according to the user's operation to perform the corresponding functional operations of each module. The user management module, model metadata management module and data management module can be switched according to the user's operation needs. The user's operation in each module will form an external request and send it to the private cloud subsystem. If the operation is successful, the operation result will be returned. If the operation is unsuccessful, an error code will be returned.

[0017] The internal subsystem includes system login module, project management module, model management module and field processing module;

[0018] The system login module is used to provide the user login function of the internal platform system, the project management module provides the engineering project management function corresponding to the user, the model management module is responsible for the addition, deletion and modification of the models related to the engineering plan, and the field processing module provides the processing function of the data recorded in the field process;

[0019] The system login module is the entrance for general users to access. It converts the user's login information into an external request and sends it to the private cloud subsystem. If the verification fails, an error code is returned. If the verification passes, it will turn to the project management module, model management module or field processing module according to the user's operation to perform the corresponding functional operations of each module. The project management module, model management module and field processing module can be switched according to the user's operation needs. The user's operation in each module will form an external request and send it to the private cloud subsystem. If the operation is successful, the operation result will be returned. If the operation is unsuccessful, an error code will be returned.

[0020] The field subsystem includes system login module, GIS module, AR module and data management module;

[0021] The system login module provides the user login verification function of the field platform system, the GIS module provides the GIS project navigation function of the project location during field operations, the AR module provides the AR and scheme combined with the real scene related functions, and the data management module provides the design scheme data cache in the field and the addition, deletion and modification functions of the field data note records;

[0022] The system login module is the entrance for general users to access. The user's login information will be converted into an external request and sent to the private cloud subsystem. If the verification fails, an error code will be returned. If the verification passes, the module will be turned to the GIS module according to the user's operation. Under the guidance of the GIS module, the on-site engineering plan comparison and review will be carried out. If needed, the AR module can be turned to browse the combination of specific engineering plans and on-site conditions. During the real-scene comparison process, the GIS module and the AR module can record the field situation through the data management module, and save the on-site plan comparison and plan adjustment information in a timely manner. The data operation in the data management module will form an external request and be sent to the private cloud subsystem. If the operation is successful, the operation result will be returned. If the operation is unsuccessful, an error code will be returned.

[0023] The present invention also provides a design method of a water transport engineering auxiliary design system platform based on AR, comprising the following steps:

[0024] Step 1: Use the Docker engine's small private cloud architecture to install system-related components and perform initial configuration of the components;

[0025] Step 2: Log in to the management subsystem, configure the project organization hierarchy, and create general user accounts and login passwords for the internal and external systems;

[0026] Step 3: Use a general user account to log in to the office subsystem, create a field task, and fill in and upload the information related to the field task, including the model and corresponding project level for comparison and review of the plan in the field;

[0027] Step 4: Use a general user account to log in to the field subsystem to browse the field task related information, and preview and adjust the design model;

[0028] Step 5: Use a general user account to log in to the field subsystem at the project site to perform field work;

[0029] Step 6: Use a general user account to log in to the office subsystem and complete the field work report.

[0030] Preferably, step 1 is specifically:

[0031] Step 1-1, install the Docker container on the background host system;

[0032] Step 1-2, install Nginx, Apache, and MySQL components in the Docker container;

[0033] Steps 1-3, configure the storage structure of the MySQL component in the Docker container, access user and login password;

[0034] Steps 1-4: Install and configure the system site module in the Apache environment of the Docker container, including the authority management module, access control module, data management module, and function processing module, and configure the default system administrator account password of the authority management module;

[0035] Steps 1-5, configure and test the Nginx component of the Docker container;

[0036] Steps 1-6: Run the Docker container and wait for external requests.

[0037] Preferably, step 2 is specifically as follows: step 2-1, logging into the management subsystem login module with the system default administrator account and login password, forming an external system login request, and sending it to the private cloud subsystem;

[0038] Step 2-2, return success, the user uses the system login module user interface navigation function to jump to the model metadata management module user interface, create a project hierarchy organization plan, form an external metadata operation request, and send it to the private cloud subsystem;

[0039] Step 2-3, return success, the project hierarchy organization scheme is created successfully;

[0040] Step 2-4: The user uses the navigation function of the user interface of the model metadata management module to jump to the user management module user interface to add system users, form an external data operation request, and send it to the private cloud subsystem;

[0041] Step 2-5, return success, the system user is added successfully.

[0042] Preferably, step 3 is specifically as follows: Step 3-1, log in to the internal subsystem login module with a general user account and login password, form an external system login request, and send it to the private cloud subsystem

[0043] Step 3-2, return success, the user uses the user interface navigation function of the task management module to configure the field task and upload the relevant project plan, forming an external data operation request and sending it to the private cloud subsystem;

[0044] Step 3-3, return success, the field task configuration and related project plans are uploaded successfully.

[0045] Step 3-4: The user uses the navigation function of the project management module user interface to jump to the model management module user interface to perform attribute supplement, preview, anchor point calibration, and wrong model deletion. The anchor reference point position can be the model center, model corner point, or model base surface center. The anchor point coordinates are input in the form of (X, Y, Z) three-dimensional coordinates. Finally, an external data operation request is formed and sent to the private cloud subsystem;

[0046] Step 3-5, return success, the field design model related parameters are configured successfully.

[0047] Preferably, step 4 is specifically:

[0048] Step 4-1, log in to the field subsystem login module with a general user account and login password, form an external system login request, and send it to the private cloud subsystem;

[0049] Step 4-2, return success, the user uses the user interface of the GIS module to browse the projects included in the field task, and compiles a field work plan form according to the content of the field project, forms a data request through the data management module, and sends it to the private cloud subsystem;

[0050] Step 4-3, return success, the field work configuration and related work plan are uploaded successfully.

[0051] Step 4-4, the user uses the navigation function of the GIS module user interface to jump to the AR module user interface to preview the model real scene and adjust the display effect, and forms a data request through the data management module and sends it to the private cloud subsystem;

[0052] Step 4-5, return success, the model display effect adjustment record is successful.

[0053] Preferably, step 5 is specifically as follows: step 5-1, logging into the field subsystem login module with a general user account and login password at the project site, forming an external system login request, and sending it to the private cloud subsystem;

[0054] Step 5-2, returns success, the user uses the user interface of the GIS module to browse the field work plan form, and navigates in the project area according to the digital map function of the GIS module;

[0055] Step 5-3, when the digital map of the GIS module shows that the user is close to the construction site of the engineering design scheme to be reviewed, the user switches to the AR module through the navigation function of the GIS module. The AR module overlays the model of the engineering design scheme to be built with the real scene at the construction site. The user can change the observation angle to inspect the coordination between the engineering construction scheme and the actual conditions.

[0056] Step 5-4, the user inputs the record of problems existing in the review of the scheme and the on-site construction conditions through the user interface of the AR module, forms a data request through the data management module, and sends it to the private cloud subsystem;

[0057] Step 5-5 returns success and the field record is saved successfully; if the field task plan is completed, it is terminated, otherwise the next plan in the field task plan is reviewed and go to step 5-3.

[0058] Preferably, step 6 is specifically as follows: Step 6-1, log in to the internal subsystem login module with a general user account and login password, form an external system login request, and send it to the private cloud subsystem

[0059] Step 6-2, return success, the user uses the user interface function of the field processing module to read field-related information, including relevant image information, voice information and model adjustment information, form an external data operation request, and send it to the private cloud subsystem;

[0060] Step 6-3, return success, the user uses the user interface function of the field processing module to summarize all field information, compile field reports, and generate external data operation requests when temporarily storing or saving field reports, which are sent to the private cloud subsystem;

[0061] Step 6-4, returns successfully, the field report is saved successfully, and is exported as a field document file through the office subsystem, and ends.

[0062] The beneficial effects of the present invention are embodied in:

[0063] Compared with the existing foam lightweight soil technology, it has the following advantages:

[0064] The present invention adopts AR technology to combine the design scheme with the actual engineering site conditions for display, thus solving the information island problem between the two. It can intuitively judge the conflict between the design scheme and the site conditions, and compare the schemes, thus improving the accuracy of the design scheme review and solving the problems that cannot be handled in the traditional engineering design process.

[0065] The auxiliary design method process proposed by the method of the present invention effectively realizes the needs of organization, integration, application, etc. of design scheme demonstration and verification, and significantly improves the efficiency of verification, comparison and review of complex engineering schemes;

[0066] The field subsystem of the present invention is deployed on a mobile handheld terminal, which improves the flexibility and practicality of system application; the data system is deployed in a private cloud subsystem, which ensures the security of system platform data application. BRIEF DESCRIPTION OF THE DRAWINGS

[0067] Figure 1 is a structural composition diagram of a system in an embodiment of the present invention;

[0068] Figure 2 is a diagram of the interaction of the private cloud subsystem modules in an embodiment of the present invention;

[0069] Figure 3 is a diagram of the management subsystem module interaction in an embodiment of the present invention;

[0070] Figure 4 It is an interaction diagram of the internal subsystem modules in an embodiment of the present invention;

[0071] Figure 5 It is an interaction diagram of the field subsystem modules in an embodiment of the present invention;

[0072] Figure 6 is a flowchart of the method execution in an embodiment of the present invention;

[0073] Figure 7 It is a wireframe display effect diagram of the design recommendation model in an embodiment of the present invention. DETAILED DESCRIPTION

[0074] The present invention is further described below in conjunction with the accompanying drawings and embodiments to more clearly and completely describe the technical solution of the present invention. Obviously, the described embodiments are only a part of the embodiments of the present invention, rather than all of the embodiments. The following description of at least one embodiment is actually illustrative and is by no means intended to limit the present invention and its application or use. Based on the embodiments of the present invention, other embodiments obtained by ordinary technicians in this field without creative work are all within the scope of protection of the present invention. Unless otherwise specifically stated, the relative positions, quantities, and sizes of the components and steps described in these embodiments do not limit the scope of the present invention.

[0075] In order to make the purpose, technical solution and advantages of the embodiments of the present invention clearer, the technical solution in the embodiments of the present invention will be further described in detail below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention but not all. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present invention.

[0076] The features and performance of the present invention are further described in detail below in conjunction with the embodiments.

[0077] An AR-based water transport engineering auxiliary design system platform, the system structure diagram is shown in Figure 1 , specifically including the following parts:

[0078] The private cloud subsystem P1 includes a permission management module M11, an access control module M12, a data management module M13 and a function processing module M14, wherein the permission management module M11 provides the management function of the entire system users and user-related system permissions, the access control module M12 provides the user's corresponding permission judgment function for accessible functions, the data management module M13 provides the storage of system user-related information, the logical organization, storage and external access functions of the engineering design plan, and the function processing module M14 provides cloud processing functions related to the platform design plan.

[0079] The relationship between the modules of the private cloud subsystem is shown in Figure 2 The access control module M12 is the entrance to external access. M12 passes the permission information in the external request to the permission management module M11 for verification. If the verification fails, an error code is returned. If the verification passes, the request is transferred to the data management module M13 or the function processing module M14 for processing according to the content of the external request. After the processing is completed, the result is returned and the request ends.

[0080] The management subsystem P2 includes a system login module M21, a user management module M22, a model metadata management module M23 and a data management module M24. The system login module M21 provides a user login function for the platform management system, the user management module M22 provides a system user configuration function, the model metadata management module M23 provides a project hierarchical structure organization and management function, and the data management module M24 provides engineering design scheme related models and field record addition, deletion and modification functions.

[0081] The relationship between the modules of the management subsystem is shown in Figure 3. The system login module M21 is the entrance for managing user access. M21 converts the user's login information into an external request and sends it to the private cloud subsystem. If the verification fails, an error code is returned. If the verification passes, it turns to the user management module M22, the model metadata management module M23 or the data management module M24 according to the user's operation to perform the corresponding functional operations of each module. The M22, M23 and M24 modules can be switched according to the user's operation needs. The user's operations in each module will form an external request and be sent to the private cloud subsystem. If the operation is successful, the operation result will be returned. If the operation is unsuccessful, an error code will be returned.

[0082] The office subsystem P3 includes a system login module M31, a project management module M32, a model management module M33 and a field processing module M34, wherein the system login module M31 is used to provide a user login function for the office platform system, the project management module M32 provides the engineering project management function corresponding to the user, the model management module is responsible for the addition, deletion and modification of models related to the engineering plan, and the field processing module M34 provides the processing function of the data recorded during the field process.

[0083] The relationship between the modules of the internal subsystem is shown in Figure 4 . The system login module M31 is the entrance for general users to access. M31 converts the user's login information into an external request and sends it to the private cloud subsystem. If the verification fails, an error code is returned. If the verification passes, it will turn to the project management module M32, the model management module M33 or the field processing module M34 according to the user's operation to perform the corresponding functional operations of each module. The M32, M33 and M34 modules can be switched according to the user's operation needs. The user's operations in each module will form an external request and be sent to the private cloud subsystem. If the operation is successful, the operation result will be returned. If the operation is unsuccessful, an error code will be returned.

[0084] The field subsystem P4 includes a system login module M41, a GIS module M42, an AR module M43 and a data management module M44. The system login module M41 provides a user login verification function for the field platform system. The GIS module M42 provides a GIS project navigation function for the project site during field operations. The AR module M43 provides AR and scheme-based real-scene related functions. The data management module M44 provides a design scheme data cache and field data note record addition, deletion and modification functions.

[0085] The relationship between the modules of the field subsystem is shown in Figure 5The system login module M41 is the entrance for general users to access. M41 converts the user's login information into an external request and sends it to the private cloud subsystem. If the verification fails, an error code is returned. If the verification passes, it turns to the GIS module M42 according to the user's operation, and conducts field engineering plan comparison and review under the guidance of the GIS module. If needed, it can turn to the AR module M43 to browse the combination of specific engineering plans and field conditions. During the real-scene comparison process, the GIS module M42 and the AR module M43 can record the field situation through the data management module M44, and save the on-site plan comparison and plan adjustment information in time. The data operation in the data management module M44 will form an external request and send it to the private cloud subsystem. If the operation is successful, the operation result will be returned. If the operation is unsuccessful, an error code will be returned.

[0086] Based on the water transport engineering auxiliary design system platform proposed in the embodiment, an AR-based water transport engineering auxiliary design method is proposed. The flow chart is as follows: Figure 6 , specifically including the following steps:

[0087] Step 1: Use the Docker engine's small private cloud architecture to install system-related components and perform initial configuration of the components. This step includes the following steps:

[0088] Step 1-1, install the Docker container on the background host system;

[0089] Step 1-2, install Nginx, Apache, MySQL and other components in the Docker container;

[0090] Steps 1-3, configure the storage structure of the MySQL component in the Docker container, access user and login password;

[0091] Step 1-4, install and configure the system site module in the Apache environment of the Docker container, including the authority management module M11, the access control module M12, the data management module M13 and the function processing module M14, and configure the default system administrator account password of the authority management module M11;

[0092] Steps 1-5, configure and test the Nginx component of the Docker container;

[0093] Steps 1-6: Run the Docker container and wait for external requests;

[0094] Step 2: Log in to the management subsystem, configure the project organization hierarchy, and create general user accounts and login passwords for the office and field systems. This step includes the following steps:

[0095] Step 2-1, log in to the management subsystem login module M21 with the system default administrator account and login password, form an external system login request, and send it to the private cloud subsystem;

[0096] Step 2-2, returns success, the user uses the M21 user interface navigation function to jump to the M23 module user interface, creates a project hierarchy organization plan, forms an external metadata operation request, and sends it to the private cloud subsystem;

[0097] Step 2-3, return success, the project hierarchy organization scheme is created successfully;

[0098] Step 2-4, the user uses the M23 user interface navigation function to jump to the M22 user management module user interface to add system users, form an external data operation request, and send it to the private cloud subsystem;

[0099] Step 2-5, return success, the system user is added successfully;

[0100] In step 2-2, the project hierarchical organization scheme is created according to the application standard of the water transport engineering design information model, and is configured according to the project level, unit level, professional level, component and equipment level, and steel bar and part level. Multiple alternative schemes can be added to each of the above levels.

[0101] In the steps 2-4, user creation can be organized according to the settings of the unit organization department used by the system, at the company level, department level, and project level, and multiple system users can be added at each level.

[0102] Step 3: Use a general user account to log in to the office subsystem, create a field task, and fill in and upload information related to the field task, including the model and corresponding project level for comparison and review of the plan in the field. This step includes the following steps:

[0103] Step 3-1: Log in to the internal subsystem login module M31 with a general user account and login password, form an external system login request, and send it to the private cloud subsystem

[0104] Step 3-2, return success, the user uses the user interface navigation function of the task management module M32 to configure the field task and upload the relevant project plan, forming an external data operation request and sending it to the private cloud subsystem;

[0105] Step 3-3, return success, the field task configuration and related project plans are uploaded successfully.

[0106] Step 3-4, the user uses the M32 user interface navigation function to jump to the M33 model management module user interface to perform attribute supplement, preview, anchor point calibration and wrong model deletion. The anchor reference point position can be the model center, model corner point, model base surface center, and the anchor point coordinates are input in the form of (X, Y, Z) three-dimensional coordinates. Finally, an external data operation request is formed and sent to the private cloud subsystem;

[0107] Step 3-5, return success, the relevant parameters of the field design model are configured successfully;

[0108] In step 3-2, the field task configuration information includes the task name, the province, city, county (district) where the project is located, information on each level of the project hierarchy, and the scheme name, design model, and remarks of the design schemes at each level of the hierarchy. The model corresponding to the design scheme supports uploading in common file formats such as DXF, FBX, and OBJ. The field project configuration information corresponding to this embodiment is shown in the following table:

[0109]

[0110]

[0111] In the step 3-4, this embodiment adopts the field design recommendation model as Figure 7 The default length unit is metric, which can be specified in the model property table. The anchor reference point is the center of the model base surface, with coordinates of (519682, 3710102, 14.75), the plane coordinate system is the Geodetic 2000 coordinate system, and the elevation system is the 1985 National Elevation Datum.

[0112] Step 4: Use a general user account to log in to the field subsystem to browse the field task related information, and preview and adjust the design model. This step includes the following steps:

[0113] Step 4-1, log in to the field subsystem login module M41 with a general user account and login password, form an external system login request, and send it to the private cloud subsystem;

[0114] Step 4-2, return success, the user uses the user interface of the GIS module M42 to browse the projects included in the field task, and compiles a field work plan form according to the content of the field project, forms a data request through the data management module M44, and sends it to the private cloud subsystem;

[0115] Step 4-3, return success, the field work configuration and related work plan are uploaded successfully.

[0116] Step 4-4, the user uses the navigation function of the GIS module M42 user interface to jump to the AR module M43 user interface to preview the model real scene and adjust the display effect, and forms a data request through the data management module M44 and sends it to the private cloud subsystem;

[0117] Step 4-5, return success, the model display effect adjustment record is successful;

[0118] In step 4-2, the GIS module M42 displays the geographical location range of the field task and the tree structure and list of the field scheme in the form of a digital map, highlights the scheme mark at the engineering site of each design scheme, and can click to display the engineering organization information corresponding to the design scheme. The digital map supports roaming functions such as zooming and panning. Through the table function of the user interface, the field order can be planned according to the geographical distribution of the design scheme and recorded in a table form;

[0119] In step 4-4, the GIS module M42 navigation function is used to switch to the AR module. The AR module displays all design solutions in the form of a list. By selecting a design solution, the design solution model can be previewed in the AR module based on the current system position. The AR module provides translation, rotation, scaling and mapping functions for the design solution model. When the physical file of the solution model is too large, the AR module provides a pre-loading function to load the solution model in the private cloud to the local device in advance to avoid the impact of field communication conditions on system operation efficiency.

[0120] Step 5: Use a general user account to log in to the field subsystem at the project site to perform field work. This step includes the following steps:

[0121] Step 5-1, log in to the field subsystem login module M41 with a general user account and login password at the project site, form an external system login request, and send it to the private cloud subsystem;

[0122] Step 5-2, return success, the user uses the user interface of the GIS module M42 to browse the field work plan form, and navigates in the project area according to the digital map function of M42;

[0123] Step 5-3, when the digital map of the GIS module M42 shows that the user is close to the construction site of the engineering design scheme to be reviewed, the user switches to the AR module M43 through the navigation function of the GIS module M42. The AR module overlays the model of the engineering design scheme to be built with the real scene at the construction site, and the user can change the observation angle to inspect the coordination between the engineering construction scheme and the actual conditions.

[0124] Step 5-4, the user inputs the record of problems existing in the review of the scheme and the on-site construction conditions through the user interface of M43, forms a data request through the data management module M44, and sends it to the private cloud subsystem;

[0125] Step 5-5 returns success and the field record is saved successfully; if the field task plan is completed, it is terminated, otherwise the next plan in the field task plan is reviewed and go to step 5-3.

[0126] In step 5-3, if the design plan conflicts with the on-site conditions, the user can notify the model adjustment function of the AR module M43 to perform fine adjustments such as translation and rotation on the original position of the design plan. The adjusted position can be recorded, and the real-scene effect can be saved in real time through the screenshot function.

[0127] In step 5-4, the user may also input on-site voice recordings through the voice function provided by M43, and information such as design plans, observation locations, screenshots, etc. related to the voice recordings may be associated with the voice recordings and saved.

[0128] Step 6: Use a general user account to log in to the office subsystem and complete the field work report. This step includes the following steps:

[0129] Step 6-1: Log in to the internal subsystem login module M31 with a general user account and login password, form an external system login request, and send it to the private cloud subsystem

[0130] Step 6-2, return success, the user uses the user interface function of the field processing module M34 to read field-related information, including relevant image information, voice information and model adjustment information, to form an external data operation request, and send it to the private cloud subsystem;

[0131] Step 6-3, returns successfully, the user uses the user interface function of the field processing module M34 to summarize all field information, compile field reports, and generate external data operation requests when temporarily storing or saving field reports, which are sent to the private cloud subsystem.

[0132] Step 6-4, returns successfully, the field report is saved successfully, and is exported as a field document file through the office subsystem, and ends.

[0133] Obviously, the above embodiments are merely examples for the purpose of clear explanation, and are not intended to limit the implementation methods. For those skilled in the art, other different forms of changes or modifications can be made based on the above description. It is not necessary and impossible to list all implementation methods here. However, the obvious changes or modifications derived therefrom should still be considered as the protection scope of the present invention.

Claims

1. An AR-based water transport engineering auxiliary design system platform, characterized by: Including private cloud subsystem, management subsystem, internal subsystem and external subsystem; The private cloud subsystem is the backend system of the entire platform, providing logical organization, storage, external access to engineering design solutions, and cloud processing functions related to platform design solutions; The management subsystem is a front-end system used by system administrators, providing platform management system user login, user configuration, project organization and management, project model, and field record addition, deletion, and modification functions; The office subsystem is a front-end system used by designers, providing user login, engineering project management, engineering model addition, deletion and modification functions, and field data management functions for the office platform system; The field subsystem is a mobile front-end system used by designers, which provides user login, GIS project navigation, AR and solution integration, and field record-related data addition, deletion and modification functions; The private cloud subsystem includes a rights management module, an access control module, a data management module, and a function processing module; The authority management module provides the management function of the entire system users and user-related system permissions. The access control module provides the user's corresponding permission judgment function to access each function. The data management module provides the storage of system user-related information, the logical organization, storage, and external access functions of the engineering design plan. The function processing module provides cloud processing functions related to the platform design plan. The access control module is the entrance to external access. It passes the permission information in the external request to the permission management module for verification. If the verification fails, an error code is returned. If the verification passes, the request is transferred to the data management module or the function processing module for processing according to the content of the external request. After the processing is completed, the result is returned and the request ends. The management subsystem includes system login module, user management module, model metadata management module and data management module; The system login module provides the user login function of the platform management system, the user management module provides the configuration function of system users, the model metadata management module provides the hierarchical structure organization and management functions of the engineering project, and the data management module provides the related models of the engineering design scheme and the addition, deletion and modification functions of the field records; The system login module is the entrance for managing user access. It converts the user's login information into an external request and sends it to the private cloud subsystem. If the verification fails, an error code is returned. If the verification passes, it turns to the user management module, model metadata management module or data management module according to the user's operation to perform the corresponding functional operations of each module. The user management module, model metadata management module and data management module can be switched according to the user's operation needs. The user's operation in each module will form an external request and send it to the private cloud subsystem. If the operation is successful, the operation result will be returned. If the operation is unsuccessful, an error code will be returned. The internal subsystem includes system login module, project management module, model management module and field processing module; The system login module is used to provide the user login function of the internal platform system, the project management module provides the engineering project management function corresponding to the user, the model management module is responsible for the addition, deletion and modification of the models related to the engineering plan, and the field processing module provides the processing function of the data recorded in the field process; The system login module is the entrance for general users to access. It converts the user's login information into an external request and sends it to the private cloud subsystem. If the verification fails, an error code is returned. If the verification passes, it will turn to the project management module, model management module or field processing module according to the user's operation to perform the corresponding functional operations of each module. The project management module, model management module and field processing module can be switched according to the user's operation needs. The user's operation in each module will form an external request and send it to the private cloud subsystem. If the operation is successful, the operation result will be returned. If the operation is unsuccessful, an error code will be returned. The field subsystem includes system login module, GIS module, AR module and data management module; The system login module provides the user login verification function of the field platform system, the GIS module provides the GIS project navigation function of the project location during field operations, the AR module provides the AR and scheme combined with the real scene related functions, and the data management module provides the design scheme data cache in the field and the addition, deletion and modification functions of the field data note records; The system login module is the entrance for general users to access. It converts the user's login information into an external request and sends it to the private cloud subsystem. If the verification fails, an error code is returned. If the verification passes, it turns to the GIS module according to the user's operation. Under the guidance of the GIS module, the on-site engineering plan comparison and review are carried out. If needed, it can turn to the AR module to browse the combination of specific engineering plans and on-site conditions. During the real-scene comparison process, the GIS module and the AR module can record the field situation through the data management module, and save the on-site plan comparison and plan adjustment information in time. The data operation in the data management module will form an external request and send it to the private cloud subsystem. If the operation is successful, the operation result will be returned. If the operation is unsuccessful, an error code will be returned. The following steps are involved: Step 1: Use the Docker engine's small private cloud architecture to install system-related components and perform initial configuration of the components; Step 1 is as follows: Step 1-1, install the Docker container on the background host system; Step 1-2, install Nginx, Apache, and MySQL components in the Docker container; Steps 1-3, configure the storage structure of the MySQL component in the Docker container, access user and login password; Steps 1-4: Install and configure the system site module in the Apache environment of the Docker container, including the authority management module, access control module, data management module, and function processing module, and configure the default system administrator account password of the authority management module; Steps 1-5, configure and test the Nginx component of the Docker container; Steps 1-6, run the Docker container and wait for external requests; Step 2: Log in to the management subsystem, configure the project organization hierarchy, and create general user accounts and login passwords for the internal and external systems; Step 2 is specifically as follows: Step 2-1, log in to the management subsystem login module with the system default administrator account and login password, form an external system login request, and send it to the private cloud subsystem; Step 2-2, return success, the user uses the system login module user interface navigation function to jump to the model metadata management module user interface, create a project hierarchy organization plan, form an external metadata operation request, and send it to the private cloud subsystem; Step 2-3, return success, the project hierarchy organization scheme is created successfully; Step 2-4: The user uses the navigation function of the user interface of the model metadata management module to jump to the user management module user interface to add system users, form an external data operation request, and send it to the private cloud subsystem; Step 2-5, return success, the system user is added successfully; Step 3: Use a general user account to log in to the office subsystem, create a field task, and fill in and upload the information related to the field task, including the model and corresponding project level for comparison and review of the plan in the field; Step 3 is specifically as follows: Step 3-1, log in to the internal subsystem login module with a general user account and login password, form an external system login request, and send it to the private cloud subsystem; Step 3-2, return success, the user uses the user interface navigation function of the task management module to configure the field task and upload the relevant project plan, forming an external data operation request and sending it to the private cloud subsystem; Step 3-3, return success, the field task configuration and related project plans are uploaded successfully; Step 3-4: The user uses the navigation function of the project management module user interface to jump to the model management module user interface to supplement attributes, preview, calibrate anchor points, and delete incorrect models. The anchor reference point position can be the model center, model corner point, or model base surface center. The anchor point coordinates are input in the form of (X, Y, Z) three-dimensional coordinates, and finally form an external data operation request and send it to the private cloud subsystem; Step 3-5, return success, the relevant parameters of the field design model are configured successfully; Step 4: Use a general user account to log in to the field subsystem to browse the field task related information, and preview and adjust the design model; Step 4 is as follows: Step 4-1, log in to the field subsystem login module with a general user account and login password, form an external system login request, and send it to the private cloud subsystem; Step 4-2, return success, the user uses the user interface of the GIS module to browse the projects included in the field task, and compiles a field work plan form according to the content of the field project, forms a data request through the data management module, and sends it to the private cloud subsystem; Step 4-3, return success, the field operation configuration and related operation plan are uploaded successfully; Step 4-4, the user uses the navigation function of the GIS module user interface to jump to the AR module user interface to preview the model real scene and adjust the display effect, and forms a data request through the data management module and sends it to the private cloud subsystem; Step 4-5, return success, the model display effect adjustment record is successful; Step 5: Use a general user account to log in to the field subsystem at the project site to perform field work; Step 5 is specifically as follows: Step 5-1, log in to the field subsystem login module with a general user account and login password at the project site, form an external system login request, and send it to the private cloud subsystem; Step 5-2, returns success, the user uses the user interface of the GIS module to browse the field work plan form, and navigates in the project area according to the digital map function of the GIS module; Step 5-3, when the digital map of the GIS module shows that the user is close to the construction site of the engineering design scheme to be reviewed, the user switches to the AR module through the navigation function of the GIS module. The AR module overlays the model of the engineering design scheme to be built with the real scene at the construction site. The user can change the observation angle to inspect the coordination between the engineering construction scheme and the actual conditions. Step 5-4, the user inputs the record of problems existing in the review of the scheme and the on-site construction conditions through the user interface of the AR module, forms a data request through the data management module, and sends it to the private cloud subsystem; Step 5-5, return success, the field record is saved successfully; if the field task plan is completed, it is terminated, otherwise the next plan in the field task plan is reviewed and the process goes to step 5-3; Step 6: Use a general user account to log in to the office subsystem and complete the field work report; Step 6 is as follows: Step 6-1: Log in to the internal subsystem login module with a general user account and login password, form an external system login request, and send it to the private cloud subsystem Step 6-2, return success, the user uses the user interface function of the field processing module to read field-related information, including relevant image information, voice information and model adjustment information, form an external data operation request, and send it to the private cloud subsystem; Step 6-3, return success, the user uses the user interface function of the field processing module to summarize all field information, compile field reports, and generate external data operation requests when temporarily storing or saving field reports, which are sent to the private cloud subsystem; Step 6-4, returns successfully, the field report is saved successfully, and is exported as a field document file through the office subsystem, and ends.

Citation Information

Patent Citations

  • A road interactive field investigation system based on BIM and AR technologies

    CN109741010A

  • Power grid decentralized collaborative design method and system based on cloud data center

    CN110599116A