An assembled water conservancy ring geological information system architecture

Abstract

The application discloses an assembled hydraulic engineering geological information system architecture, and aims to solve the technical problems of high coupling degree, poor expansibility and long function expansion period of the existing hydraulic engineering geological information system. The architecture adopts three-layer decoupling design and is divided into a business definition layer HeegBD, a business implementation layer HeegBI and a business application layer HeegBA from top to bottom. The business definition layer constructs a standardized business definition model with business processes, business elements, data management, model management and system tools as core dimensions, and provides stable service interfaces; the business implementation layer encapsulates independent standardized service modules according to three-dimensional combination; and the business application layer dynamically establishes the mapping relationship between interfaces and implementations through an XML configuration file and a Java reflection mechanism, and realizes the rapid plug-in assembly of business functions. The application significantly improves the flexibility, expandability and maintainability of the system, and can be widely applied to the development and deployment of hydraulic engineering geological business digital information systems in the fields of hydrogeology, geological disasters and ecological restoration.

Description

Technical Field

[0001] This invention relates to the field of computer software architecture technology, specifically to a prefabricated hydrogeological information system architecture. Background Technology

[0002] Hydrogeology and environmental geology are fundamental geological works supporting national economic development and ecological civilization construction. They encompass numerous industrial fields, including hydrogeology, geothermal and mineral spring geology, mine hydrogeology and environmental geology, geological engineering, geological disaster prevention and control, and ecological environment restoration. These fields involve dozens of technical methods, such as data collection, remote sensing interpretation, topographic surveying, geological mapping, physical exploration, chemical exploration, mountain engineering, drilling engineering, field testing, sampling and testing, dynamic monitoring, numerical simulation, and comprehensive research. Each technical method can be further subdivided into various sub-methods, generating massive amounts of multi-source heterogeneous data. Simultaneously, hydrogeology and environmental geology services are highly correlated with the needs of social development. With the deepening of ecological civilization construction and the rapid development of the digital economy, the content, standards, and technical means of hydrogeology and environmental geology services are constantly being updated and iterated, placing extremely high demands on the flexibility, scalability, and rapid response capabilities of information systems.

[0003] In recent years, the hydrogeology and environmental geology industry has made significant progress in digital transformation, with various information systems gradually replacing traditional manual work methods and improving operational efficiency. Currently, the invention patent CN120259023B discloses a "Hydrogeology and Environmental Geology Information System Based on Full Lifecycle Digitalization of Business Operations." This technology achieves integrated digitalization of business operations and management throughout the entire lifecycle of hydrogeology and environmental geology, providing the industry with an industrial-grade digitalization foundation. However, this technology still does not solve the core problems of flexible combination of business dimensions and rapid assembly of business functions. System function expansion and updates still require modification of core code, resulting in slow response times and an inability to achieve plug-and-play functionality, making it difficult to adapt to the rapid iterative development trend of hydrogeology and environmental geology operations.

[0004] Therefore, there is an urgent need to develop a prefabricated hydrogeological information system architecture that can rapidly expand business functions, flexibly combine and plug and play while maintaining the stability of the core system architecture, so as to fundamentally solve the problems of poor scalability, difficult maintenance and long development cycle of existing technologies. Summary of the Invention

[0005] This invention provides a prefabricated hydrogeological information system architecture, aiming to solve the technical defects of existing hydrogeological information systems, such as high system coupling, poor scalability, difficult maintenance, long development cycle, and low function reuse rate. In particular, it addresses the core pain point that existing technologies cannot achieve flexible combination of business dimensions and rapid assembly of business functions. While maintaining the long-term stability of the core system architecture, it enables rapid expansion, flexible combination, and plug-and-play of hydrogeological business functions, significantly improving the system's adaptability to new fields, new business models, and new technologies.

[0006] To achieve the above objectives, the technical solution provided by the present invention is as follows: A prefabricated hydrogeological information system architecture includes a business process management module, a business element management module, a data management module, a model management module, and a system tool management module for realizing a digital and intelligent information system for hydrogeological business. The architecture is characterized by adopting a three-layer decoupled design, consisting of a business definition layer (HeegBD), a business implementation layer (HeegBI), and a business application layer (HeegBA) from top to bottom. The HeegBD (Business Definition Layer) is used to define hydrogeological and environmental geology business and provide standardized service interfaces, which are independently encapsulated in corresponding functional modules. The HeegBD layer constructs a hydrogeological and environmental geology business definition model, which uses business process (BP), business elements (E), data management (D), model management (M), and system tools (T) as independent dimension variables. The business process (BP), business element (E), data management (D), model management (M), and system tool (T) are each built with standardized sub-models and corresponding service interfaces. The service interfaces of the business definition layer (HeegBD) remain stable and are closed to modification. The business implementation layer HeegBI is used to provide polymorphic specific implementations of each service interface of the business definition layer HeegBD. The service implementations corresponding to different hydrogeological and environmental geological businesses are encapsulated into mutually independent standardized service modules. The standardized service modules can be added, modified, deleted or replaced according to business needs, thereby achieving decoupling between business definition and business implementation, separation between different business implementations, and openness to extension. The business application layer HeegBA is programmed to the service interface of the business definition layer HeegBD. It is used to establish a mapping relationship between the standardized service modules of the business implementation layer HeegBI and the corresponding service interfaces of the business definition layer HeegBD according to business requirements through configuration files, complete the assembly of service modules, and implement the corresponding hydrogeological and environmental business services through interface calls, thereby decoupling business applications from business implementation.

[0007] As a further aspect of the present invention, the business process BP sub-model is constructed using business deployment (P), business execution (D), business inspection (C), and business analysis (A) as independent and fixed basic process dimension variables. This forms a closed-loop management model based on the PDCA cycle, covering the entire lifecycle of hydrogeological and environmental geological business, and sets up standardized service interfaces for business deployment, business execution, business inspection, and business analysis.

[0008] As a further aspect of the present invention, the business element E sub-model is constructed using m dynamically configurable business element dimensions and four independent and fixed basic process dimensions—element deployment (EP), element execution (ED), element inspection (EC), and element analysis (EA)—as variables. The business element dimensions include at least work tasks, work requirements, work location, work methods, work processes, work results, staff, work time, work materials, and work expenses. Furthermore, business element dimensions can be added, modified, or deleted according to business requirements, and standardized service interfaces are set accordingly.

[0009] As a further embodiment of the present invention, the data management D sub-model is constructed with n dynamically configurable data dimensions and five independent and fixed basic process dimensions: structure maintenance, data storage, data retrieval, data governance, and data analysis. The model management M sub-model is constructed with t dynamically configurable model dimensions and five independent and fixed basic process dimensions: model structure maintenance, model creation, model invocation, model management, and model analysis. The system tool T sub-model is constructed with d dynamically configurable system tool dimensions and four independent and fixed basic process dimensions: tool creation, tool configuration, tool maintenance, and tool invocation. The dimensions of each sub-model can be added, modified, or deleted according to business needs, and standardized service interfaces are set accordingly.

[0010] As a further aspect of this invention, the standardized service module implementing the HeegBI layer is constructed based on a three-dimensional combination of the industrial field, business type, and technical method of hydrogeology and environmental geology. For the combination of the i-th industrial field, j-th business type, and k-th technical method, a specific implementation is provided for the service interface of the corresponding sub-model of the HeegBD layer defining the business, thus constructing the standardized service module. Where i represents the number of industry sectors, j represents the number of business types, and k represents the number of technical methods. Each standardized service module is independent and uncoupled.

[0011] As a further aspect of the present invention, the business application HeegBA layer defines assembly rules through an XML-formatted configuration file. This configuration file contains nodes for configuring hydrogeological and environmental geology business modules. Each node includes a module ID, activation status, industry sector, business type, technical method, business definition module address, business implementation module address, and corresponding configuration information for business processes, business elements, data management, model management, and system tool modules. The business application HeegBA layer parses the configuration file using JAXB annotations, establishes a mapping relationship between business definition interfaces and business implementation modules, and dynamically loads and instantiates corresponding standardized service modules based on Java reflection to complete the assembly of business functions.

[0012] As a further aspect of the present invention, the business module node of the configuration file is set with an enable status control attribute. By modifying the parameter value of the enable status control attribute, the enable and disable of the corresponding standardized service module can be controlled without modifying the original system code, thus realizing the rapid plug-and-play assembly of hydrogeological and environmental geological business functions. When adding new business functions, it is only necessary to develop the corresponding standardized service module and supplement the configuration file content. When iterating existing functions, it is only necessary to replace the corresponding standardized service module.

[0013] Explanation of beneficial effects: This invention addresses the technical shortcomings of existing hydrogeological and environmental geological information systems by proposing a prefabricated hydrogeological and environmental geological information system architecture based on three-layer decoupling and standardized interfaces, which has the following significant advantages: 1. Achieved complete decoupling of business definition, implementation, and application: By constructing a three-layer architecture of HeegBD business definition layer, HeegBI business implementation layer, and HeegBA business application layer, it strictly adheres to the open / closed principle, dependency inversion principle, and Liskov substitution principle of software design. The business definition layer interface remains stable and closed to modification; the business implementation layer provides polymorphic concrete implementations and is open to extension; the business application layer programs to interfaces and completes service assembly through configuration files, completely solving the problem of high coupling in traditional monolithic architectures.

[0014] 2. Supports flexible combinations of business dimensions: A standardized business definition model has been constructed with business processes, business elements, data management, model management, and system tools as core dimensions. Each sub-model adopts a design pattern of "fixed process dimension + configurable business dimension". Business elements, data, models, and tool dimensions can be flexibly configured according to the needs of different industry sectors, business types, and technical methods, enabling personalized customization of hydrogeological and environmental geology businesses and adapting to differentiated business needs in multiple fields such as hydrogeology, geological hazards, and ecological restoration.

[0015] 3. Enables rapid plug-and-play assembly of business functions: Standardized service modules in the business implementation layer are independently encapsulated according to a three-dimensional combination of "industry sector - business type - technical method," with no coupling between modules. The business application layer establishes the mapping relationship between interfaces and implementations through XML configuration files, and dynamically loads and instantiates service modules based on JAXB annotation parsing and Java reflection mechanisms. Enabling or disabling business functions can be achieved by modifying the enable / disable attribute of the configuration file, without modifying the original system code, significantly improving system response speed. Attached Figure Description

[0016] Figure 1 This invention provides a schematic diagram of the architecture of a prefabricated hydrogeological information system. Figure 2 This invention provides a schematic diagram of the deployment architecture of a prefabricated hydrogeological information system. Figure 3 This invention provides a flowchart for the construction of a prefabricated hydrogeological and environmental information system architecture. Detailed Implementation

[0017] The preferred embodiments of the present invention will be described below with reference to the accompanying drawings. It should be understood that the preferred embodiments described herein are for illustration and explanation only and are not intended to limit the present invention. Example

[0018] The prefabricated hydrogeological information system architecture described in this invention adopts a three-layer decoupled design, consisting of a business definition layer (HeegBD), a business implementation layer (HeegBI), and a business application layer (HeegBA) from top to bottom. This architecture strictly adheres to the open / closed principle, dependency inversion principle, and Liskov substitution principle in software design, achieving decoupling between business definition and business implementation, decoupling between business application and business implementation, and separation between different business implementations.

[0019] The core logic of the overall system architecture can be expressed by the following mathematical model: ; in: This represents the overall architecture of the prefabricated hydrogeological and environmental information system. This represents the business definition layer, which is responsible for defining hydrogeological and environmental geological business and providing standardized service interfaces. This represents the business implementation layer, which is responsible for providing polymorphic implementations of the various service interfaces of the business definition layer. This represents the business application layer, which is responsible for assembling standardized service modules from the business implementation layer according to business requirements and calling the corresponding services.

[0020] The three-layer decoupled structure of this system and the composition of the core modules of each layer are as follows: Figure 1 As shown.

[0021] After receiving a user request, the business application layer HeegBA looks up the mapping relationship between the corresponding service interface in the business definition layer HeegBD and the specific implementation module in the business implementation layer HeegBI through the configuration file, and forwards the request to the business implementation layer HeegBI. The business implementation layer HeegBI executes the specific business logic, and in the process, calls the standardized interface defined by the business definition layer HeegBD for data interaction and function calls. The processing result is returned to the business application layer HeegBA along the original path and finally presented to the user.

[0022] Preferably, the business definition layer is implemented using HeegBD.

[0023] The Business Definition Layer (HeegBD) is the core abstraction layer of the entire system. Its core responsibility is to define unified standards and service interfaces for hydrogeological and environmental geology business operations. These service interfaces remain stable and are closed to modification. The HeegBD layer constructs a hydrogeological and environmental geology business definition model. This model uses business process (BP), business elements (E), data management (D), model management (M), and system tools (T) as independent dimension variables. Its mathematical expression is: ; in: (Business Process) refers to the business process dimension, corresponding to the full lifecycle management process of hydrogeological and environmental geology business; (Element) represents the business element dimension, corresponding to the various basic components involved in hydrogeological and environmental geology business; (Data) represents the data management dimension, corresponding to the management of various types of data generated and used in hydrogeological and environmental geology operations; (Model) represents the model management dimension, corresponding to the management of various algorithm models used in hydrogeological and environmental geology operations; (Tool) represents the system tool dimension, which corresponds to the management of various basic tools that support the operation of the system.

[0024] Business Process (BP), Business Elements (E), Data Management (D), Model Management (M), and System Tools (T) are each built with standardized sub-models and corresponding service interfaces. Each sub-model adopts a design pattern of "fixed process dimension + configurable business dimension," where the fixed process dimension ensures the consistency and standardization of business management logic, while the configurable business dimension ensures the flexibility and scalability of the system.

[0025] Furthermore, the business process BP sub-model is implemented.

[0026] The Business Process (BP) sub-model uses Business Deployment (P), Business Execution (D), Business Inspection (C), and Business Analysis (A) as independent and fixed basic process dimension variables. It is constructed as a closed-loop management model based on the PDCA cycle, covering the entire lifecycle of hydrogeological and environmental geology business. Its mathematical expression is: ; in: (Plan) represents the business deployment dimension, responsible for the planning, allocation, and resource configuration of business tasks; (Do) represents the business execution dimension, responsible for the specific execution of business tasks and data collection; (Check) represents the business inspection dimension, responsible for the quality inspection and verification of the business execution process and results; (Analysis) represents the business analysis dimension, which is responsible for the analysis, summarization, and improvement of business execution results.

[0027] The full lifecycle management of hydrogeological and environmental geology operations is essentially a continuous improvement cycle. Through abstraction and summarization of numerous hydrogeological and environmental geology business processes, it has been found that any hydrogeological and environmental geology business can be decomposed into four basic stages: "deployment-execution-inspection-analysis". These four stages proceed sequentially, forming a closed loop. The analysis results of the previous cycle serve as the basis for deployment in the next cycle, thereby achieving continuous optimization of business management. Therefore, the business process BP sub-model can be represented as a function of these four basic process dimensions.

[0028] The business process (BP) sub-model has standardized service interfaces for business deployment, business execution, business inspection, and business analysis. The functional definitions of each service interface are as follows: Business deployment interface: Receives business requirements information, generates a business execution plan, allocates human, material, and financial resources, and determines the time nodes and quality requirements for business execution. Business execution interface: Based on the business execution plan, it carries out specific business tasks, collects business data, and records the business execution process. Business Inspection Interface: This interface checks the business execution process and results according to preset quality standards and inspection rules, identifies problems, and proposes corrective action requirements. Business analytics interface: Performs statistical analysis on business execution data and inspection results, evaluates business completion, summarizes lessons learned, and proposes business improvement suggestions. The data flow in the business process BP sub-model is as follows: the business execution plan data generated by the business deployment interface is passed to the business execution interface; the business execution data generated by the business execution interface is passed to the business inspection interface; the inspection result data generated by the business inspection interface is passed to the business analysis interface; and the analysis result data generated by the business analysis interface is fed back to the business deployment interface as the basis for the next round of business deployment.

[0029] Furthermore, the business element E sub-model is implemented.

[0030] The Business Element E sub-model is constructed using m dynamically configurable business element dimensions and four independent, fixed basic process dimensions: Element Deployment (EP), Element Execution (ED), Element Inspection (EC), and Element Analysis (EA). Its mathematical expression is: in: This represents m dynamically configurable business element dimensions, with m ranging from [5, 20]. Too few business element dimensions cannot fully cover the basic components of hydrogeological and environmental geology business, while too many business element dimensions will increase the complexity and maintenance cost of the system. The optimal value is 10, which can fully cover the core elements of hydrogeological and environmental geology business while maintaining the simplicity and efficiency of the system.

[0031] (Element Plan) represents the element deployment dimension, responsible for the definition, configuration, and initialization of business elements; (Element Do) represents the element execution dimension, responsible for the invocation and use of business elements; (Element Check) represents the element check dimension, responsible for checking the completeness, accuracy, and validity of business elements; (Element Analysis) represents the element analysis dimension, responsible for analyzing the usage of business elements and providing optimization suggestions.

[0032] Business elements are the basic units constituting hydrogeological and environmental geological operations. Different hydrogeological and environmental geological operations involve different business elements, but the management process of all business elements follows the basic pattern of "deployment-execution-inspection-analysis". Therefore, the business element E sub-model can be represented as a function of dynamically configurable business element dimensions and fixed element management process dimensions.

[0033] Business element dimensions can be added, modified, or deleted according to business needs, and standardized service interfaces can be set accordingly. For example, when adding a "device management" business element, you only need to add the device management dimension to the business element E sub-model and define standardized service interfaces for device deployment, device execution, device inspection, and device analysis, without modifying the code of other parts of the system.

[0034] The data flow in the business element E sub-model is as follows: the business element configuration data generated by the element deployment interface is transferred to the element execution interface; the element usage data generated by the element execution interface is transferred to the element inspection interface; the element inspection result data generated by the element inspection interface is transferred to the element analysis interface; and the element analysis result data generated by the element analysis interface is fed back to the element deployment interface to optimize the configuration of business elements.

[0035] Furthermore, the D sub-model for data management is implemented.

[0036] The data management D sub-model is constructed using n dynamically configurable data dimensions and five independent, fixed basic process dimensions: structure maintenance, data storage, data retrieval, data governance, and data analysis. Its mathematical expression is: ; in: This represents n dynamically configurable data dimensions, where n ranges from [3, 15]. Too few data dimensions cannot fully cover the various types of data generated by hydrogeological and environmental geological operations, while too many data dimensions increase the complexity of data management. The optimal value is 5, at which point the data classification is clear and the management efficiency is the highest.

[0037] (Structure Maintenance) refers to the structural maintenance dimension, which is responsible for maintaining the database table structure and data model; (Data Storage) represents the data storage dimension, responsible for the storage management of various types of data; (Data Read) represents the data reading dimension, responsible for querying and reading various types of data; (Data Governance) refers to the data governance dimension, which is responsible for data cleaning, transformation, integration, and quality control; (Data Analysis) refers to the data analysis dimension, which is responsible for the statistical analysis and mining of various types of data.

[0038] Data is the core asset of hydrogeological and environmental geology operations. Different hydrogeological and environmental geology operations generate and use different types of data, but the management process of all data follows the basic pattern of "structure maintenance-storage-retrieval-governance-analysis". Therefore, the data management D sub-model can be represented as a function of dynamically configurable data dimensions and fixed data management process dimensions.

[0039] The data dimensions include at least knowledge data, thematic data, model data, project data, and system data. Each data dimension employs a hybrid storage approach combining relational and non-relational databases. Structured data (such as basic project information and personnel information) is stored in the relational database, while unstructured data (such as geological reports, remote sensing images, and borehole data) is stored in the non-relational database. The data storage backup strategy combines full backups and incremental backups. Full backups are performed weekly, and incremental backups are performed daily. Full backups ensure data integrity, while incremental backups reduce backup time and storage space usage. This combination ensures both data security and improved backup efficiency.

[0040] The Data Management D sub-model includes standardized service interfaces for structure maintenance, data storage, data retrieval, data governance, and data analysis. The data governance interface employs rule-based data cleaning algorithms and machine learning-based data quality assessment algorithms. The rule-based data cleaning algorithm handles obvious errors and duplicate data, while the machine learning-based data quality assessment algorithm evaluates the completeness, accuracy, and consistency of the data.

[0041] The data flow in the Data Management D sub-model is as follows: the database table structure and data model data generated by the structure maintenance interface are transferred to the data storage interface; the data storage interface receives and stores the raw data generated by business execution; the data reading interface reads data from the data storage and transfers it to the data governance interface; the data governance interface cleans, transforms, and integrates the data before transferring it to the data analysis interface; and the analysis results generated by the data analysis interface are fed back to the data storage interface for storage.

[0042] Furthermore, the model management M sub-model is implemented.

[0043] The model management M sub-model is constructed using t dynamically configurable model dimensions and five independent, fixed basic process dimensions: model structure maintenance, model creation, model invocation, model management, and model analysis. Its mathematical expression is: ; in: This represents t dynamically configurable model dimensions, with t ranging from [3, 12]. Too few model dimensions cannot cover the various models commonly used in hydrogeological and environmental geology operations, while too many model dimensions will increase the complexity of model management. The optimal value is 7, which can fully cover the core model types in hydrogeological and environmental geology operations.

[0044] (Model Structure) represents the model structure maintenance dimension, responsible for maintaining the model structure and parameters; (Model Create) represents the model creation dimension, responsible for the training and creation of various models; (Model Load) represents the model invocation dimension, responsible for loading and invoking various types of models; (Model Management) refers to the model management dimension, which is responsible for model version management, permission management, and lifecycle management; (Model Analysis) represents the model analysis dimension, which is responsible for the performance evaluation and effect analysis of the model.

[0045] Models are crucial tools for data analysis and forecasting in hydrogeological and environmental geology operations. Different hydrogeological and environmental geology operations use different types of models, but the management process for all models follows the basic pattern of "structure maintenance - creation - invocation - management - analysis". Therefore, the model management M sub-model can be represented as a function of dynamically configurable model dimensions and fixed model management process dimensions.

[0046] The model dimensions include at least geological entity models, geological calculation models, map rendering models, process management models, data management models, model management models, and general calculation models. The model creation interface supports various machine learning and numerical computation algorithms, including linear regression, logistic regression, decision trees, random forests, support vector machines, neural networks, finite element methods, and finite difference methods. Model version management adopts a semantic versioning standard, with the version number format "major version number.minor version number.revision number," where the major version number indicates incompatible API modifications, the minor version number indicates backward-compatible functional additions, and the revision number indicates backward-compatible bug fixes.

[0047] The Model Management M sub-model has standardized service interfaces for model structure maintenance, model creation, model invocation, model management, and model analysis. The model invocation interface uses a lazy loading mechanism, meaning the model is only loaded into memory the first time it is invoked, and automatically unloaded from memory if it hasn't been invoked for a long time. Models used in hydrogeological and environmental geological projects are typically large, and the lazy loading mechanism effectively reduces system memory usage and improves system efficiency.

[0048] The data flow in the Model Management M sub-model is as follows: the model structure and parameter data generated by the model structure maintenance interface are passed to the model creation interface; the model creation interface uses the training data to train the model and passes the trained model data to the model management interface; the model call interface loads the model from the model management interface and uses the input data for calculation; the model calculation result data is passed to the model analysis interface; and the model performance evaluation data generated by the model analysis interface is fed back to the model management interface for storage.

[0049] Furthermore, the system tool T sub-model is implemented.

[0050] The system tool T sub-model is constructed using d dynamically configurable system tool dimensions and four independent, fixed basic process dimensions: tool creation, tool configuration, tool maintenance, and tool invocation. Its mathematical expression is: ; in: Let d represent the number of dynamically configurable system tool dimensions, where d ranges from [5, 15]. Too few system tool dimensions will not meet the basic requirements for system operation, while too many system tool dimensions will increase the complexity of the system. The optimal value is 8, which can comprehensively cover all kinds of basic tools required for system operation.

[0051] (Tool Create) represents the tool creation dimension, responsible for the development and creation of various system tools; (Tool Setup) represents the tool configuration dimension, responsible for configuring the parameters of various system tools; (Tool Maintenance) refers to the tool maintenance dimension, which is responsible for the upgrade and maintenance of various system tools; (Tool Load) represents the tool invocation dimension, which is responsible for the invocation and use of various system tools.

[0052] System tools are fundamental components that support system operation. Different system functions require different system tools, but the management process of all system tools follows the basic pattern of "creation-configuration-maintenance-invocation". Therefore, the system tool T sub-model can be represented as a function of a dynamically configurable system tool dimension and a fixed system tool management process dimension.

[0053] The system tools dimension includes at least navigation, authorization, services, logging, help, interface, security, and configuration. The authorization management tool uses a role-based access control (RBAC) model, assigning system permissions to different roles, with users gaining corresponding permissions through their assigned roles. The logging management tool records system operation logs, management logs, and error logs, with a retention period of 6 months to 2 years, configurable according to business needs. The security management tool provides security functions such as user authentication, data encryption, access control, and firewall. User authentication uses a username + password + verification code method, and data encryption uses the AES-256 encryption algorithm.

[0054] The system tool T sub-model has standardized service interfaces for tool creation, configuration, maintenance, and invocation. Each system tool operates independently, interacting through these standardized interfaces, ensuring system stability and maintainability.

[0055] The data flow in the system tool T sub-model is as follows: the system tool data generated by the tool creation interface is passed to the tool configuration interface; the tool configuration data generated by the tool configuration interface is passed to the tool maintenance interface; after upgrading and maintaining the system tool, the tool maintenance interface passes the updated tool data to the tool call interface; the tool call interface receives the business request and calls the corresponding system tool to complete the business operation; the tool execution result data is fed back to the tool call interface and returned to the business requester.

[0056] Preferably, the business implementation layer is implemented using HeegBI.

[0057] The business implementation layer, HeegBI, provides polymorphic implementations of the service interfaces of the business definition layer, HeegBD. Service implementations corresponding to different hydrogeological and environmental geological businesses are encapsulated as independent standardized service modules. This layer is open for extension, allowing the addition, modification, deletion, or replacement of standardized service modules according to business needs, thus decoupling business definition from business implementation and separating different business implementations.

[0058] The standardized service module of HeegBI in the business implementation layer is constructed based on a three-dimensional combination of the industrial field, business type, and technical method of hydrogeology and environmental geology. For the combination of the i-th industrial field, j-th business type, and k-th technical method, a specific implementation is provided for the service interface of the corresponding sub-model in the HeegBD business definition layer, thus constructing the standardized service module. Its mathematical expression is: ; in: The value of i represents the number of industry sectors, and the range of i is [1, 10]. Industry sectors include, but are not limited to, hydrogeology, mineral geology, geological engineering, geological disasters, and ecological restoration. This indicates the number of business types, with j ranging from [1, 15]. Business types include, but are not limited to, survey and evaluation, engineering exploration, engineering consulting, engineering design, engineering implementation, engineering supervision, dynamic monitoring, and scientific research. The number of technical methods is represented by k, which ranges from [1, 20]. The technical methods include, but are not limited to, data collection, remote sensing interpretation, topographic surveying, geological mapping, physical exploration, chemical exploration, mountain engineering, drilling engineering, field testing, sampling and testing, dynamic monitoring, digital simulation, and special studies. This represents the specific implementation of the business process sub-model corresponding to the i-th industry sector, j-th business type, and k-th technical method; This represents the specific implementation of the business element sub-model corresponding to the i-th industry sector, j-th business type, and k-th technical method; This represents the specific implementation of the data management sub-model corresponding to the i-th industry sector, j-th business type, and k-th technical method; This represents the specific implementation of the model management sub-model corresponding to the i-th industry sector, j-th business type, and k-th technical method; This represents the specific implementation of the system tool sub-model corresponding to the i-th industry sector, j-th business type, and k-th technical method.

[0059] The specific implementations of business processes, business elements, data management, model management, and system tools vary across different industry sectors, business types, and technical methods in hydrogeological and environmental geology. Therefore, standardized service modules can be represented as functions that specifically implement each sub-model in the business definition layer under a three-dimensional combination of industry sector, business type, and technical method.

[0060] Each standardized service module is independent and decoupled from the others, and each standardized service module implements the complete service interface defined by the HeegBD business definition layer. When a new business function needs to be added, only the standardized service module corresponding to the industry field, business type, and technical method combination needs to be developed; when an existing business function needs to be modified or iterated, only the corresponding standardized service module needs to be replaced, without affecting the normal operation of other business functions.

[0061] The data flow in the business implementation layer HeegBI is as follows: After receiving the service request forwarded by the business application layer HeegBA, the business implementation layer HeegBI calls the corresponding business process implementation module; the business process implementation module sequentially calls the business element implementation module, data management implementation module, model management implementation module and system tool implementation module to complete the business logic processing; the processing result is returned to the business application layer HeegBA along the original path.

[0062] The hierarchical deployment and modular service node distribution of this system are as follows: Figure 2 As shown, each standardized service module can be deployed independently on different physical servers or container nodes, supporting horizontal scaling and load balancing.

[0063] Preferably, the business application layer is implemented using HeegBA.

[0064] The business application layer HeegBA programs against the service interfaces of the business definition layer HeegBD. Based on business requirements, it establishes a mapping relationship between the standardized service modules of the business implementation layer HeegBI and the corresponding service interfaces of the business definition layer HeegBD through configuration files, completes the assembly of service modules, and implements the corresponding hydrogeological and environmental business services through interface calls, thereby decoupling business applications from business implementation.

[0065] The business application layer HeegBA defines assembly rules through XML-formatted configuration files. These configuration files contain nodes for configuring hydrogeological and environmental geology business modules. These nodes include the module ID, activation status, industry sector, business type, technical method, business definition module address, business implementation module address, and corresponding configuration information for business processes, business elements, data management, model management, and system tools modules.

[0066] The XML Schema definition of the configuration file is as follows: In the business application layer, HeegBA parses configuration files using JAXB annotations to establish a mapping between business definition interfaces and business implementation modules. JAXB (Java Architecture for XML Binding) is a technology that converts XML documents to and from Java objects. By adding JAXB annotations to Java classes, automatic mapping between XML elements and Java object properties can be achieved.

[0067] After establishing the mapping relationship, the business application layer HeegBA dynamically loads and instantiates the corresponding standardized service modules based on the Java reflection mechanism, completing the assembly of business functions. The Java reflection mechanism allows the program to obtain class information and create class instances at runtime, thereby realizing the function of dynamically assembling different business modules without modifying the code.

[0068] The configuration file's business module nodes have an enable / disable attribute. By modifying the parameter value of this attribute (true for enabled, false for disabled), the enabling and disabling of the corresponding standardized service module can be controlled without modifying the original system code, enabling rapid plug-and-play assembly of hydrogeological and environmental geological business functions. When adding new business functions, only the corresponding standardized service module needs to be developed and the configuration file content supplemented; when iterating on existing functions, only the corresponding standardized service module needs to be replaced.

[0069] The data flow in the HeegBA business application layer is as follows: the user submits a business request through the HeegBA user interface; the HeegBA business application layer parses the configuration file and finds the mapping relationship between the corresponding business definition interface and the business implementation module; the business implementation module is instantiated through the Java reflection mechanism and the corresponding service interface is called; the business implementation module processes the request and returns the result; the HeegBA business application layer presents the result to the user.

[0070] The complete construction process of this system is as follows: Figure 3 As shown, following the core principle of "defining first, then implementing, and then assembling", the business definition layer, business implementation layer and business application layer are constructed in sequence, and finally the rapid pluggable assembly of hydrogeological and environmental geological business functions is realized.

[0071] Finally, it should be noted that the above descriptions are merely preferred embodiments of the present invention and are not intended to limit the present invention. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art can still modify the technical solutions described in the foregoing embodiments or make equivalent substitutions for some of the technical features. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the protection scope of the present invention.

Claims

1. A prefabricated hydrogeological and environmental geological information system architecture, comprising a business process management module, a business element management module, a data management module, a model management module, and a system tool management module for realizing a digital and intelligent information system for hydrogeological and environmental geological operations, characterized in that, The architecture adopts a three-layer decoupled design, which is divided into the business definition layer HeegBD, the business implementation layer HeegBI, and the business application layer HeegBA from top to bottom. The HeegBD (Business Definition Layer) is used to define hydrogeological and environmental geology business and provide standardized service interfaces, which are independently encapsulated in corresponding functional modules. The HeegBD layer constructs a hydrogeological and environmental geology business definition model, which uses business process (BP), business elements (E), data management (D), model management (M), and system tools (T) as independent dimension variables. The business process (BP), business element (E), data management (D), model management (M), and system tool (T) are each built with standardized sub-models and corresponding service interfaces. The service interfaces of the business definition layer (HeegBD) remain stable and are closed to modification. The business implementation layer HeegBI provides polymorphic implementations of the service interfaces of the business definition layer HeegBD. Service implementations corresponding to different hydrogeological and environmental geology businesses are encapsulated into independent standardized service modules. These standardized service modules of the business implementation layer HeegBI are constructed based on a three-dimensional combination of the industry sector, business type, and technical method of hydrogeology and environmental geology. For the combination of the i-th industry sector, j-th business type, and k-th technical method, specific implementations are provided for the service interfaces of the corresponding sub-models in the business definition layer HeegBD, thus constructing the standardized service modules. Each standardized service module is independent and decoupled from the others. The standardized service modules can be added, modified, deleted or replaced according to business needs, so as to achieve decoupling of business definition and business implementation, separation between different business implementations, and openness to extension. The business application layer, HeegBA, is programmed to the service interface of the business definition layer, HeegBD. It defines assembly rules based on business requirements using an XML-formatted configuration file. This configuration file contains nodes for configuring hydrogeological and environmental geology business modules. These nodes include module ID, activation status, industry sector, business type, technical method, business definition module address, business implementation module address, and corresponding configuration information for business processes, business elements, data management, model management, and system tool modules. HeegBA parses the configuration file using JAXB annotations, establishing a mapping between the business definition interface and the business implementation module. It then dynamically loads and instantiates the corresponding standardized service modules based on Java reflection, completing the assembly of the service modules. Finally, it implements the corresponding hydrogeological and environmental geology business services through interface calls, thus decoupling the business application from the business implementation.

2. The prefabricated hydrogeological and environmental information system architecture according to claim 1, characterized in that, The business process BP sub-model is constructed using business deployment (P), business execution (D), business inspection (C), and business analysis (A) as independent and fixed basic process dimension variables. This forms a closed-loop management model based on the PDCA cycle, covering the entire lifecycle of hydrogeological and environmental geological business, and sets up standardized service interfaces for business deployment, business execution, business inspection, and business analysis.

3. The prefabricated hydrogeological and environmental information system architecture according to claim 1, characterized in that, The business element E sub-model is constructed using m dynamically configurable business element dimensions and four independent, fixed basic process dimensions—Element Deployment (EP), Element Execution (ED), Element Inspection (EC), and Element Analysis (EA)—as variables. The business element dimensions include at least work tasks, work requirements, work location, work methods, work processes, work results, staff, work time, work materials, and work expenses. Furthermore, business element dimensions can be added, modified, or deleted according to business requirements, and standardized service interfaces are set accordingly.

4. The prefabricated hydrogeological and environmental information system architecture according to claim 1, characterized in that, The data management sub-model D is constructed using n dynamically configurable data dimensions and five independent, fixed basic process dimensions: structure maintenance, data storage, data retrieval, data governance, and data analysis. The model management sub-model M is constructed using t dynamically configurable model dimensions and five independent, fixed basic process dimensions: model structure maintenance, model creation, model invocation, model management, and model analysis. The system tool sub-model T is constructed using d dynamically configurable system tool dimensions and four independent, fixed basic process dimensions: tool creation, tool configuration, tool maintenance, and tool invocation. The dimensions of each sub-model can be added, modified, or deleted according to business needs, and standardized service interfaces are set accordingly.

5. The prefabricated hydrogeological and environmental information system architecture according to claim 1, characterized in that, The business module nodes in the configuration file are set with an enable status control attribute. By modifying the parameter value of the enable status control attribute, the enable and disable of the corresponding standardized service module can be controlled without modifying the original system code, thus realizing the rapid plug-and-play assembly of hydrogeological and environmental geological business functions. When adding new business functions, only the corresponding standardized service module needs to be developed and the configuration file content needs to be supplemented. When iterating existing functions, only the corresponding standardized service module needs to be replaced.

Images