A method and system for proactively pushing GIS environment specification clauses based on a rule engine

By proactively pushing out applicable standard clauses based on a rule engine-based GIS environment, the system automatically generates and displays applicable standard clauses, solving the time-consuming problem in traditional bridge design and improving design quality and efficiency.

CN117669367BActive Publication Date: 2026-11-17CHINA RAILWAY SIYUAN SURVEY & DESIGN GRP CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202311597334.7
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2023-11-24
Publication Date
2026-11-17
Estimated Expiration
2043-11-24

AI Technical Summary

Technical Problem

In the bridge design process, traditional methods of consulting guidelines for span layout are time-consuming and incomplete, affecting the quality and efficiency of the design scheme.

Method used

A proactive push method for standard clauses based on a rule engine GIS environment is adopted. By obtaining bridge standard database information, business rules of the rule engine are generated, standard request information is generated based on the design scheme of the GIS environment, reasoning is performed in the rule engine, and after classification, the applicable standard clauses are displayed in the GIS environment.

Benefits of technology

It has enabled the automation and acceleration of bridge span design, improved design quality and efficiency, and lowered the professional threshold for engineers.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN117669367B_ABST
    Figure CN117669367B_ABST
Patent Text Reader

Abstract

This invention belongs to the field of intelligent bridge design technology, and discloses a method and system for proactively pushing standard clauses based on a rule engine in a GIS environment. The method includes: acquiring design standard information from a bridge standard database; generating business rules for a rule engine based on the design standard information; selecting target entity objects based on the current design scheme in the GIS environment and generating standard request information; sending the standard request information to a rule engine with the business rules for reasoning to obtain standard reasoning results; classifying the standard reasoning results based on execution level to generate applicable standard clause information; and pushing and displaying the applicable standard clause information in the GIS environment. Through this method, applicable standard clauses can be automatically pushed, transforming the traditional passive knowledge retrieval into knowledge adaptive matching and proactive pushing, achieving comprehensive and rapid pushing, and improving the quality and efficiency of design scheme review.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention relates to the field of intelligent design technology for bridge schemes, and in particular to a method and system for proactively pushing specification clauses based on a rule engine-based GIS environment. Background Technology

[0002] The core of bridge design is the span layout, which aims to employ a rational span arrangement to overcome obstacles beneath the bridge, forming an underground engineering structure together with the roadbed and tunnels to support the smooth flow of traffic along the route. During the span layout process, the bridge needs to rationally cross obstacle control points on the route while minimizing economic costs and construction difficulty, all while meeting design requirements. To ensure the rationality and feasibility of the span layout, certain rules are needed to guide the decision-making process. These rules primarily come from industry standards, classic cases, and expert experience. However, the abundance of standards and experience, coupled with the complex construction environment, means that bridge design engineers must spend a significant amount of time selecting and determining applicable rules, and even then, it is difficult to consider all possibilities, impacting the quality and efficiency of the design. Therefore, a solution is needed that can automatically and efficiently select empirical rules to improve the quality and efficiency of the design process.

[0003] The above content is only used to help understand the technical solution of the present invention and does not represent an admission that the above content is prior art. Summary of the Invention

[0004] The main objective of this invention is to provide a method and system for proactively pushing GIS environment specification clauses based on a rule engine. This aims to solve the technical problem in the prior art where, when designing bridge span layout, the traditional method of obtaining span layout guidance rules is used, which is time-consuming and difficult to fully consider, thus affecting the quality and efficiency of the design scheme.

[0005] To achieve the above objectives, this invention provides a method for proactively pushing GIS environment specification clauses based on a rule engine, the method comprising the following steps:

[0006] Obtain design specification information from the bridge specification database, and generate business rules for the rule engine based on the design specification information;

[0007] Based on the current design scheme in the GIS environment, select the target entity object and generate specification request information;

[0008] The specification request information is sent to a rule engine containing the business rules for inference to obtain the specification inference result;

[0009] Based on the execution level, the normative reasoning results are classified to generate information on applicable normative clauses;

[0010] The applicable standard clauses information will be pushed and displayed in the GIS environment.

[0011] Optionally, the step of obtaining design specification information from the bridge specification database and generating business rules for the rule engine based on the design specification information includes:

[0012] The design specification information is obtained from the bridge specification database, and the condition information in the design specification information is transformed into constraint condition rule information according to the preset lexical rules and preset grammatical structure rules.

[0013] Based on the syntax parser, the constraint rule information is transformed into the condition part of the business rules in the rule engine;

[0014] The action information in the design specification information is transformed into the action part of the business rules in the rule engine.

[0015] Optionally, the specification request information includes at least control point information and target entity object information. The control point information includes at least the control point name, control point type, control point angle, and height limit. Sending the specification request information to a rule engine with the business rules for reasoning to obtain the specification reasoning result includes:

[0016] Based on the retrieval type, the standardized request information is matched with the condition part of the business rule to determine the matching condition part;

[0017] The canonical reasoning result is obtained based on the action part corresponding to the matching condition part.

[0018] Optionally, the step of matching the standardized request information with the conditional portion of the business rule based on the retrieval type to determine the matching conditional portion includes:

[0019] Based on the retrieval type of the design specification information, the retrieval type of the condition part of the business rule is determined. The retrieval type includes at least a general retrieval type, a control point retrieval type, a business entity retrieval type, and a complex retrieval type.

[0020] Based on the control point information, a first matching condition portion is determined in the condition portion of the control point retrieval type;

[0021] Based on the target entity object information, a second matching condition part is determined in the condition part of the business entity retrieval type;

[0022] In the condition sections of the general search type and the complex search type, the third matching condition section and the fourth matching condition section are determined respectively.

[0023] Optionally, the step of converting the constraint rule information into the condition part of the business rule in the rule engine based on the syntax parser includes:

[0024] The syntax parser is generated based on the preset lexical rules and the preset syntax structure rules. The preset lexical rules include at least conditional connector rules, comparison rules, operator rules, literal rules, identifier rules, class variable rules, class rules, and reference rules. The preset syntax structure rules include at least class constraint structure rules and condition structure rules. The condition structure rules include at least object condition structure rules, compound condition structure rules, and comparison expression structure rules.

[0025] Based on the syntax parser, the constraint rule information is lexically analyzed to obtain keywords;

[0026] Syntax parsing is performed based on the grammatical structure corresponding to the keywords to obtain a syntax tree;

[0027] Based on the syntax tree, the condition part of the business rules in the rule engine is generated.

[0028] Optionally, the method for proactively pushing GIS environment specification clauses based on a rule engine further includes:

[0029] Obtain bridge specification document information, and based on the bridge specification document information, determine design specification information, which includes general attribute information and measure information;

[0030] The measure information in the design specification information is split according to the preset segmentation elements to obtain a set of conditional action pairs;

[0031] Based on the set of conditional action pairs, determine the conditional information and action information corresponding to the design specification information respectively;

[0032] Based on the general attribute information, measure information, condition information, and action information of the design specification information, a specification knowledge graph is constructed.

[0033] Optionally, the method for proactively pushing GIS environment specification clauses based on a rule engine further includes:

[0034] Based on preset fields, knowledge is extracted from the design specification information to generate a specification knowledge table. The preset fields include at least clause measures, execution level, condition classification, standard basis, clause number, clause content, event classification, engineering stage, bridge grade, bridge and culvert classification, structural system, constraint object, construction method, line relationship, geological classification, topographic classification, hydrological classification, control point classification, interface constraint, and keyword list.

[0035] Based on the retrieval type of the design specification information, set the trigger conditions for the design specification information, and add the trigger conditions to the specification knowledge table;

[0036] Based on the semantics of the design specification information, determine the functional classification and attributes of the condition information and the action information. The functional classification of the condition information includes at least empty constraints, control point constraints, and beam type constraints. The functional classification of the action information includes at least beam type query, prompt items, and beam type filtering.

[0037] Based on the functional classification and attributes of the design specification information, determine the structural type of the design specification information, and based on the structural type, determine the database structure of the design specification information;

[0038] The standard knowledge table is mapped to the database structure of the design standard information so that the standard knowledge graph is stored in the bridge standard database.

[0039] Optionally, the structure type includes object constraint type and fixed structure type. The database structure corresponding to the object constraint type includes at least object type and constraint condition. The constraint condition includes at least comparison expression, combined constraint condition and sub-object constraint. The comparison expression includes at least attribute name, constant and operator. The combined constraint condition includes at least condition combiner and sub-constraint condition.

[0040] Optionally, the method for proactively pushing GIS environment specification clauses based on a rule engine further includes:

[0041] The business rules are grouped according to the condition information and logical priority information of the design specification information to obtain agenda rule group and activation rule group, and the intra-group priority attribute and inter-group priority attribute of the agenda rule group and activation rule group are set.

[0042] Furthermore, to achieve the above objectives, this invention also proposes a proactive push system for GIS environment specification clauses based on a rule engine, the proactive push system for GIS environment specification clauses based on a rule engine comprising:

[0043] The rule generation module is used to obtain design specification information from the bridge specification database and generate business rules for the rule engine based on the design specification information.

[0044] The specification request module is used to select target entity objects based on the current design scheme in the GIS environment and generate specification request information.

[0045] The normative reasoning module is used to send the normative request information to a rule engine with the business rules for reasoning and to obtain the normative reasoning result.

[0046] The normative reasoning module is also used to classify the normative reasoning results based on the execution level and generate information on applicable normative clauses;

[0047] The specification push module is used to push and display the applicable specification clauses in the GIS environment.

[0048] Furthermore, to achieve the above objectives, the present invention also proposes a rule engine-based GIS environment specification clause proactive push device, the rule engine-based GIS environment specification clause proactive push device comprising: a memory, a processor, and a rule engine-based GIS environment specification clause proactive push program stored on the memory and executable on the processor, the rule engine-based GIS environment specification clause proactive push program being configured to implement the steps of the rule engine-based GIS environment specification clause proactive push method described above.

[0049] Furthermore, to achieve the above objectives, the present invention also proposes a storage medium storing a proactive push program for GIS environment specification clauses based on a rule engine. When the proactive push program for GIS environment specification clauses based on a rule engine is executed by a processor, it implements the steps of the proactive push method for GIS environment specification clauses based on a rule engine as described above.

[0050] In this invention, design specification information is obtained from a bridge specification database. Based on this information, business rules for a rule engine are generated. Target entity objects are selected based on the current design scheme in the GIS environment, and specification request information is generated. This request information is sent to the rule engine with business rules for reasoning, yielding specification reasoning results. These results are then categorized based on execution level, generating applicable specification clause information, which is then pushed and displayed in the GIS environment. When designing bridge span layouts, compared to traditional methods of obtaining span layout guidelines, which are time-consuming and difficult to fully consider, affecting the quality and efficiency of the design, this invention can automatically push applicable specification clauses. It shifts from traditional passive knowledge retrieval to adaptive knowledge matching and proactive pushing, achieving comprehensive and rapid push notifications, improving the quality and efficiency of the design, and lowering the professional threshold for bridge engineers. Attached Figure Description

[0051] Figure 1 This is a schematic diagram of the structure of the hardware operating environment based on the rule engine GIS environment specification clause proactive push device involved in the embodiment of the present invention;

[0052] Figure 2 This is a flowchart illustrating the first embodiment of the method for proactively pushing GIS environment specification clauses based on a rule engine according to the present invention.

[0053] Figure 3 This is an entity relationship diagram of an embodiment of the method for proactively pushing GIS environment specification clauses based on a rule engine according to the present invention;

[0054] Figure 4 This is a functional classification diagram of an embodiment of the method for proactively pushing GIS environment specification clauses based on a rule engine according to the present invention;

[0055] Figure 5 This is another functional classification diagram of an embodiment of the method for proactively pushing GIS environment specification clauses based on a rule engine according to the present invention;

[0056] Figure 6 This is a schematic diagram of the database structure of an embodiment of the method for proactively pushing GIS environment specification clauses based on a rule engine according to the present invention;

[0057] Figure 7 This is a schematic diagram of design specification information in a bridge specification database, representing an embodiment of the proactive push method for specification clauses in a rule engine-based GIS environment according to the present invention.

[0058] Figure 8 This is a schematic diagram of specification request information from an embodiment of the method for proactively pushing specification clauses of a GIS environment based on a rule engine according to the present invention.

[0059] Figure 9 This is a schematic diagram illustrating applicable regulatory clause information in an embodiment of the method for proactively pushing regulatory clauses to GIS environments based on a rule engine, according to the present invention.

[0060] Figure 10 This is a flowchart illustrating the second embodiment of the method for proactively pushing GIS environment specification clauses based on a rule engine according to the present invention.

[0061] Figure 11 This is a schematic diagram of the CJSON data format of an embodiment of the method for proactively pushing GIS environment specification clauses based on a rule engine according to the present invention;

[0062] Figure 12 This is a flowchart illustrating the third embodiment of the method for proactively pushing GIS environment specification clauses based on a rule engine according to the present invention.

[0063] Figure 13 This is a structural block diagram of the first embodiment of the rule engine-based GIS environment specification clause proactive push system of the present invention.

[0064] The realization of the objective, functional features and advantages of the present invention will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

[0065] It should be understood that the specific embodiments described herein are for illustrative purposes only and are not intended to limit the scope of the invention.

[0066] Reference Figure 1 , Figure 1This is a schematic diagram of the hardware operating environment based on the rule engine GIS environment specification clause actively pushed device structure involved in the embodiment of the present invention.

[0067] like Figure 1 As shown, the device for proactively pushing GIS environment specification clauses based on a rules engine may include: a processor 1001, such as a central processing unit (CPU), a communication bus 1002, a user interface 1003, a network interface 1004, and a memory 1005. The communication bus 1002 is used to enable communication between these components. The user interface 1003 may include a display screen or an input unit such as a keyboard; optionally, the user interface 1003 may also include a standard wired interface or a wireless interface. The network interface 1004 may optionally include a standard wired interface or a wireless interface (such as a Wireless-Fidelity (Wi-Fi) interface). The memory 1005 may be a high-speed random access memory (RAM) or a stable non-volatile memory (NVM), such as a disk drive. The memory 1005 may also optionally be a storage device independent of the aforementioned processor 1001.

[0068] Those skilled in the art will understand that Figure 1 The structure shown does not constitute a limitation on the proactive push device based on the rules engine GIS environment specification clauses. It may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0069] like Figure 1 As shown, the memory 1005, which serves as a storage medium, may include an operating system, a network communication module, a user interface module, and a proactive push program for GIS environment specification clauses based on a rule engine.

[0070] exist Figure 1 In the rule engine-based GIS environment specification clause proactive push device shown, the network interface 1004 is mainly used for data communication with the network server; the user interface 1003 is mainly used for data interaction with the user; the processor 1001 and memory 1005 in the rule engine-based GIS environment specification clause proactive push device of the present invention can be set in the rule engine-based GIS environment specification clause proactive push device, the rule engine-based GIS environment specification clause proactive push device calls the rule engine-based GIS environment specification clause proactive push program stored in memory 1005 through processor 1001, and executes the rule engine-based GIS environment specification clause proactive push method provided in the embodiment of the present invention.

[0071] This invention provides a method for proactively pushing GIS environment specification clauses based on a rule engine, referring to... Figure 2 , Figure 2 This is a flowchart illustrating the first embodiment of a method for proactively pushing GIS environment specification clauses based on a rule engine according to the present invention.

[0072] In this embodiment, the method for proactively pushing GIS environment specification clauses based on a rule engine includes the following steps:

[0073] Step S10: Obtain design specification information from the bridge specification database, and generate business rules for the rule engine based on the design specification information.

[0074] It should be noted that the execution entity in this embodiment can be a device that actively pushes GIS environment specification clauses based on a rule engine. The computer is equipped with a program that actively pushes GIS environment specification clauses based on a rule engine. By running the program, the active push of specification clauses can be achieved. It can also be other terminal devices with computing capabilities. This embodiment does not limit this. The device that actively pushes GIS environment specification clauses based on a rule engine is used as an example for explanation.

[0075] It is understandable that a bridge code database refers to a graph database that stores a code knowledge graph, which is a constructed knowledge graph about bridge design codes. Design code information refers to the relevant information for each bridge design code in the bridge code database.

[0076] It should be noted that the bridge specification database can be a graph database, which is a superior solution for storing rule information, such as GalaxyBase graph database. Other relational or non-relational databases can also be selected, and this embodiment does not impose any restrictions on this.

[0077] It should be understood that rule engines evolved from rule-based expert systems. Essentially, they are reasoning systems that match rules with corresponding data to make business decisions. Rule engines model, define, and manage rules, decoupling rules from business logic. This allows rules to be modified, adjusted, and extended at any time. Users can directly write rules corresponding to specific business needs, submitting the rules and data to the rule engine, which then automatically completes the processes of rule definition, rule management, and rule execution.

[0078] In this embodiment, the business rules used by the rule engine are generated based on the design specification information. The rule engine used is the Drools rule engine, but other suitable rule engines can also be used. This embodiment does not limit this.

[0079] Furthermore, before step S10, the method further includes: obtaining bridge specification document information; determining design specification information based on the bridge specification document information, wherein the design specification information includes general attribute information and measure information; splitting the measure information in the design specification information according to preset segmentation elements to obtain a set of condition-action pairs; determining the condition information and action information corresponding to the design specification information based on the set of condition-action pairs; and constructing a specification knowledge graph based on the general attribute information, measure information, condition information, and action information of the design specification information.

[0080] It should be noted that the bridge specification knowledge graph involves three main entities: bridge standard parameter components, control points, and bridge design specifications. Bridge standard parameter components represent the final output of bridge design, specifically the beam type. Control points are the starting point for bridge scheme design. Bridge design specifications are the actual rules referenced in bridge scheme design, including both actual bridge design specifications and bridge engineering case studies, both serving as recommended references for bridges. The schema layer of the specification knowledge graph should primarily consist of bridge standard parameter components and bridge design specifications. In this embodiment, bridge specification document information refers to textual information related to design specifications in the field of bridge design, including at least bridge design specifications, bridge specification manuals, literature monographs, engineering drawings, and bridge standard parameter component information. Bridge specification document information can be broken down into individual bridge design specifications, as shown in Table 1.

[0081] Understandably, as shown in Table 1, specifications are generally unstructured data. Each specification can be decomposed into some common attributes (specification name, implementation nature, number, and measures, etc.), but the measures portion is difficult to store using fixed attributes and structures. Therefore, specifications are divided into four entities: Specification Information, the general attribute portion of the specification, including specification name, implementation nature (mainly "mandatory" and "recommended"), priority (used to determine the application priority between different specifications), etc.; Measures Information, the measures in the specification, including branch priority (used to determine the matching priority of different measures / branches within the same specification), which will be converted into business rules; Condition Information, the condition portion of the measures, including condition behavior and condition content, etc.; and Action Information, the action portion of the measures in the specification, including action behavior and action content, etc. Figure 3 To standardize the entity-relationship diagram (ER diagram) between information, measures, conditions, and actions.

[0082] Table 1

[0083]

[0084] It should be understood that the preset segmentation elements refer to the elements set for splitting bridge design specifications, such as semicolons, periods, and phrases like "...or...", which can be determined according to actual needs. This embodiment does not impose any restrictions on this. The measure information consists of conditions and actions. After marking the possible conditional branches and their corresponding different results, the information is segmented according to the conditional branches to construct condition-action pairs. Each condition-action pair contains 0 to n conditions and 1 to n actions. A condition-action pair may have no conditions; the absence of conditions indicates default fulfillment. However, a condition-action pair must have at least one action. When a condition is met, the corresponding action is triggered. The set of condition-action pairs is the condition-action pair set. Each bridge design specification can be converted into one or more sets of condition-action pairs, providing decision-making for different branches. Each condition-action pair can be considered a rule split from a specification. Based on the semantics of the specification and its associated design task, the functional classification of the rule is determined. Then, the conditions and actions are extracted into the corresponding functional rule-related condition and action forms, obtaining the condition information and action information for each rule.

[0085] Furthermore, prior to step S10, the method further includes: extracting knowledge from the design specification information based on preset fields to generate a specification knowledge table; setting trigger conditions for the design specification information based on the retrieval type of the design specification information, and adding the trigger conditions to the specification knowledge table; determining the functional classification and attributes of the condition information and the action information based on the semantics of the design specification information; determining the structure type of the design specification information based on the functional classification and attributes of the design specification information, and determining the database structure of the design specification information based on the structure type; and mapping the specification knowledge table to the database structure of the design specification information so that the specification knowledge graph is stored in the bridge specification database.

[0086] It should be noted that the preset fields are fields set for splitting / extracting, and at least include clause measures, execution level, condition classification, standard reference, clause number, clause content, event classification, project stage, bridge grade, bridge and culvert classification, structural system, constraint object, construction method, alignment relationship, geological classification, topographic classification, hydrological classification, control point classification, interface constraints, and keyword list. Using the preset fields as the table header, relevant content is extracted from the design specification information and populated to obtain a two-dimensional table, namely the specification knowledge table. The relevant content extracted from each piece of design specification information constitutes one row of the specification knowledge table. Considering that the specifications in the field of bridge design have high requirements for the accuracy of knowledge extraction results, and the results of current machine-automated knowledge extraction cannot meet the requirements in practice, this embodiment adopts a manual knowledge extraction method.

[0087] It is understandable that, due to the large number of business entities involved in the span arrangement field, and the fact that different business entities can form new business entities through different positional or geometric relationships, it is difficult to provide a complete description directly. Therefore, this embodiment further classifies these design specification information based on existing business entities. The retrieval type is the classification of these design specification information, which includes at least control point retrieval type, business entity retrieval type, general retrieval type, and complex retrieval type. This includes relevant specifications for retrieval based on control point information, design specifications that can be retrieved after considering the introduction of relevant business entities, general design specifications without triggering conditions, and other design specifications that are difficult to describe in a structured way. For design specifications of the control point retrieval type, the fields of the control point business entities already defined in the span inference part can be used to describe the control point information involved in the condition part of this type of specification. For specifications of the business entity retrieval type, an incremental design is adopted, that is, adding the data structure of new business entities, and then using the fields of the newly added business entities to describe the relevant entity information involved in the condition part of this type of specification. For specifications of the general retrieval type, since this type of specification itself does not have specific conditions, it should be considered or applied in any situation, that is, it is a general trigger, so the description of its condition part will match any fact object. Triggering conditions are the conditions that can match design specification information. According to different retrieval types of design specification information, set the triggering conditions corresponding to each specification and add them to the specification knowledge table.

[0088] It should be understood that specifications have multiple functions. The functional classification of design specification information refers to the functional types corresponding to each specification. For conditional information, it includes at least empty constraints, control point constraints, and beam type constraints. For action information, it includes at least beam type query, prompts, and beam type filtering. Attributes are the main content of the conditional / action information. For example, if a specification is in the form of "If a control point satisfies a certain constraint, then a beam type under a certain condition should be selected" or "If a control point satisfies a certain constraint, then a certain situation should be considered," for the former, the conditional information is the constraint on the control point, or it may be empty (indicating any triggering condition), which can be used to define the scope of control points applicable to this specification. The action information is a beam type query, which includes the beam type traversal algorithm and the constraints on the beam type. For the latter, the action part is a prompt, indicating the existence of some unquantifiable data constraints, provided to the designer as a reminder. Figure 4As shown, the standard's measure section states, "The width-to-span ratio of a simply supported truss should not be less than 1 / 20, and the width-to-span ratio of the middle span of a continuous truss should not be less than 1 / 25." The extracted condition information is an empty constraint, and the action information is a beam type query, specifically stating "The width-to-span ratio of a simply supported truss is less than 1 / 20, and the width-to-span ratio of the middle span of a continuous truss is less than 1 / 25." If the standard is in the form of "If the beam type should satisfy a certain constraint" or "If the control point satisfies a certain constraint, the beam type should satisfy a certain constraint," this type of standard is generally mandatory and used to filter beam types obtained from other standards. Its condition information is a constraint on the beam type or a constraint on both the beam type and the control point, and the action information is beam type filtering, indicating pass or fail. For example... Figure 5 As shown, the standard's measures section states, "Bridges with large spans, such as steel beams and continuous beams, should preferably be located on straight lines. If they must be located on curves, a larger curve radius should be adopted. For open-deck bridges with spans greater than 40m or lengths greater than 100m, the curve radius should preferably be no less than 1000m." This is broken down into the following conditions: "Control points are curves with a curve radius less than 1000m" and "The beam type is an open-deck bridge with a span greater than 40m or a length greater than 100m."

[0089] It should be noted that the structure type refers to the type of standardized structure. In this embodiment, the structure types are divided into two categories: fixed structure types, whose attributes, content, and structure are generally fixed, and object constraint types, whose content is a set of constraints on the attributes of a certain class, and the relevant content is strongly related to the attributes of the constrained class. For fixed attribute types, they can be divided into one type of entity, and the relevant attributes are stored through the entities connected to them. In this embodiment, the database structure defined for object constraint types is as follows: Figure 6 As shown, object constraints consist of an object type and multiple constraint conditions. Constraint conditions are divided into comparison expressions (actually providing attribute constraints), composite constraints (providing logical combinations of constraints), and sub-object constraints (used to provide constraints for attributes of non-basic types). Comparison expressions have a "comparison expression" structure, consisting of object attributes, constants, operators, etc. Comparison operators include common basic comparison operators such as greater than, equal to, and less than, as well as regular expression validation and list queries. Composite constraints consist of condition combiners (AND, OR, etc.) and a series of constraint conditions. Sub-object constraints are similar in structure to object constraints, but with the addition of an attribute name field. The database structure in this embodiment is a graph database structure. If the bridge specification database uses other database forms, other suitable database structures can be defined to store the specification knowledge graph in the database.

[0090] In practical implementation, knowledge extraction is performed based on existing textual information in the field of bridge design, such as specifications, manuals, literature, and engineering drawings. Unstructured information, primarily text and images, is extracted into structured information for bridge design professionals to use in scheme decision-making. This structured information is then organized using a graph data structure and stored in a bridge specification database. Figure 7 As shown.

[0091] Step S20: Based on the current design scheme in the GIS environment, select the target entity object and generate specification request information.

[0092] It is understood that the current design scheme refers to the 3D design scheme generated in a GIS (Geographic Information System) environment. The target entity object is the currently selected entity object, which can be a control point, abutment, steel bridge, etc., and this embodiment does not impose any restrictions on this. The target entity object can be determined by the area where the mouse cursor is located, or by double-clicking / singling the object. This embodiment does not impose any restrictions on this, and appropriate methods can be flexibly selected.

[0093] It should be understood that the specification request information, i.e., the generated file used to request the push of specifications, typically includes control point information and target entity object information. That is, it includes information related to the control points and information related to the currently selected entity object. Control point information at least includes the control point name, control point type, control point angle, and height limit, such as... Figure 8 As shown.

[0094] Step S30: Send the specification request information to the rule engine with the business rules for reasoning to obtain the specification reasoning result.

[0095] It should be understood that the canonical reasoning result refers to the canonical clauses that need to be pushed out, which are inferred by the reasoning engine.

[0096] It should be noted that, since this embodiment uses the Drools rule engine, the generated business rules are Drools rules. The generated Drools rules are inserted into the Drools rule engine. When the Drools rule engine receives the specification request information, it performs rule matching in the working memory of the Drools rule engine. After a successful match, the inference result is obtained from the global buffer queue.

[0097] It is understood that the method for proactively pushing GIS environment specification clauses based on the rule engine also includes: grouping the business rules according to the condition information and logical priority information of the design specification information to obtain agenda rule groups and activation rule groups, and setting the intra-group priority attributes and inter-group priority attributes of the agenda rule groups and activation rule groups.

[0098] It should be understood that logical priority information refers to the logical implication relationships among various specification conditions determined by domain experts during the knowledge extraction process. Specifications with more general conditions have higher priority, while those with more specific conditions have lower priority. The priority attribute is the method for determining priority and can be set according to actual needs.

[0099] It should be noted that this embodiment divides rules into different agenda groups and activation groups based on logical priority information, and sets priority attributes for rules within and between groups. Some complex specifications may not be mappable to a single rule engine rule; in such cases, they need to be mapped to multiple rules. However, conflicts between general and specific conditions inevitably arise among these multiple rules. Therefore, this embodiment uses agenda groups, activation groups, and setting intra-group priorities to ensure the correct execution of rule reasoning.

[0100] Understandably, within the same agenda group, priorities are set based on the relationship between general and specific conditions of rules. Rules with general conditions (wider constraint ranges) have higher priority and are executed before rules with specific conditions (narrower constraint ranges). In actual reasoning, situations inevitably arise where key control points match multiple rules, but only one rule needs to be executed. This embodiment employs an activation grouping mechanism, grouping rules with the same conditions into the same activation group. These activation groups are mutually exclusive, with only one rule executed within each group, adapting to different reasoning scenarios. Within the same activation group, rules have their priorities set based on the content of three enumerated fields: "scope of application," "execution nature," and "maturity level" of their specification class object. Rules with broader scope of application, stronger execution nature, and higher maturity level are executed first. Priority is an attribute of a rule; the higher the attribute value, the higher the priority of the matching and execution.

[0101] Step S40: Based on the execution level, classify the normative reasoning results and generate applicable normative clause information.

[0102] It should be understood that the enforcement level refers to the degree of enforcement of the regulatory provisions, and includes at least four levels: should, should not, appropriate, and inappropriate. Applicable regulatory provision information refers to the document returned by the rules engine containing the regulatory provisions that need to be pushed.

[0103] It should be noted that this embodiment needs to classify the results of canonical inference according to different categories, such as... Figure 9 As shown, based on the categorized specifications, the final returned information on applicable specification clauses is generated.

[0104] Step S50: Push and display the applicable standard clauses information in the GIS environment.

[0105] It should be noted that bridge span design is only one type of software program interaction behavior. Any other type of business action interaction based on the software program, and the formulation of rules related to the business, can be achieved by actively pushing business rules through the rule engine provided in this embodiment. This embodiment provides a general business rule triggering event mechanism based on software program construction.

[0106] In this embodiment, design specification information is obtained from the bridge specification database. Based on this information, business rules for a rule engine are generated. Target entity objects are selected based on the current design scheme in the GIS environment, and specification request information is generated. This request information is sent to the rule engine with business rules for reasoning, yielding specification reasoning results. Based on execution level, the reasoning results are categorized, and applicable specification clause information is generated and displayed in the GIS environment. When designing bridge span layout, compared to traditional methods of obtaining span layout guidelines, which are time-consuming and difficult to fully consider, affecting the quality and efficiency of the design, this embodiment can automatically push applicable specification clauses. It shifts from traditional passive knowledge retrieval to adaptive knowledge matching and proactive pushing, achieving comprehensive and rapid push, improving the quality and efficiency of the design, and lowering the business threshold for bridge engineers.

[0107] Reference Figure 10 , Figure 10 This is a flowchart illustrating the second embodiment of a method for proactively pushing GIS environment specification clauses based on a rule engine according to the present invention.

[0108] Based on the above embodiments, in this embodiment, step S10 includes:

[0109] Step S101: Obtain design specification information from the bridge specification database, and convert the condition information in the design specification information into constraint rule information according to the preset lexical rules and preset grammatical structure rules.

[0110] It should be noted that this embodiment designs a syntax called CJSON (full name ConditionJSON), which can use a concise and hierarchical syntax to describe the attribute constraints of a class. The preset lexical rules and the preset syntax structure rules refer to the lexical design and syntax structure design in CJSON.

[0111] Understandably, the predefined lexical rules include at least conditional connector rules, comparison rules, operator rules, literal rules, identifier rules, class variable rules, class rules, and reference rules. Conditional connector rules: Constraints on a class are actually logical combinations of multiple constraints. To satisfy the logical relationships between conditions, the "and" and "or" keywords provide conditional logical combination functionality. Comparison symbol rules: Comparison symbols provide value-to-value validation functionality, possessing actual constraint functions. They include basic comparison symbols such as ">", "<", "==", ">=", "<=", and "!=", as well as advanced comparison symbols such as "matches" (regular expression validation), "memberOf" (whether an element is contained in a list), and "contains" (whether a list contains elements). Operator rules: Operators are used to perform operations on numerical values, and are categorized based on precedence as follows: addition / subtraction operators (AddSubSymbol), multiplication / division operators (MulDivSymbol), unary operators (UnarySymbol), and bracket operators. Literal rules: Literals represent fixed values ​​of basic data types, including NullLiteral, BooleanLiteral, NumberLiteral, and StringLiteral. Numeric types can be expressed using integers, floating-point numbers, and scientific notation, while character types can be represented using basic characters, escape characters ("\", etc.), and UNICODE. Identifier rules: Identifiers are used to represent method names and property names, etc. They begin with a lowercase letter, followed by uppercase letters, lowercase letters, numbers, underscores, etc. Class variable symbol rules: Class variable symbols are used to represent class variable names, etc. They begin with an uppercase letter, followed by uppercase letters, numbers, underscores, etc. Class rules: Class names are used to represent class names, beginning with an uppercase letter, followed by uppercase letters, lowercase letters, numbers, underscores, etc. Reference rules: A reference is used to indicate a class other than the current class. It is identified by adding a dollar sign "$" to the class name.

[0112] It should be noted that the preset syntax structure rules include at least class constraint structure rules and condition structure rules. Condition structure rules include at least object condition structure rules, compound condition structure rules, and comparison expression structure rules. The overall syntax structure of CJSON adopts a class constraint structure, meaning that a class constraint structure rule consists of a class name and a set of conditions. A class constraint (topCondition) is an unordered set of conditions, serving as the top-level syntax element, representing a constraint on a specific class. A class constraint begins with the name of the class to which the constraint belongs, followed by a set of conditions enclosed in "{" and "}", with each condition separated by a comma. The class name is represented using a class identifier (class). Conditions can be object conditions (structuralCondition), compound conditions (compoundCondition), or comparison expressions (comparison), with corresponding structure types of object condition structure, compound condition structure, and comparison expression structure, determined by the object condition structure rules, compound condition structure rules, and comparison expression structure rules, respectively. Structural Conditions: Structural conditions constrain non-primitive type attributes of a class. An object condition is structurally similar to a class constraint, but it uses an identifier to represent the name of the constrained attribute, i.e., the attribute name. Compound Conditions: Compound conditions are combinations of conditions obtained by using logical operators. Their structure is also similar to class constraints, but their identifier is a condition connector ("&&", or "‖‖", etc.).

[0113] Understandably, the structure of comparison expressions follows these rules: A comparison expression is a specific constraint on the attributes of a class's basic types. Its structure is either a binary comparison expression like "'expression A'' comparison operator OP1'' expression B'" or a chained comparison expression like "'expression A'' comparison operator OP1'' expression B'' comparison operator OP2'' expression C'...". Chained comparison expressions mimic the chained comparison mechanism in Python syntax and are equivalent to multiple binary comparison expressions like "'expression A'' comparison operator OP1'' expression B'", "'expression B'' comparison operator OP2'' expression C'", and so on. Comparison operators include basic operators like greater than, equal to, less than, and their combinations, as well as advanced comparison operators such as regular expression string matching (matches), list retrieval (contains, memberOf), etc. Operation expressions (expressions) combine variables using operators (including parentheses). Operators are decomposed into levels based on operator precedence, such as parentheses, unary operators, multiplication and division operators, addition and subtraction operators, etc. Variables include literal variables, basic type attributes of a class (class attribute variables), basic type attributes of other classes (reference attribute variables), and method call variables. Literals can be null, boolean values ​​(true and false), numbers, and strings, corresponding to the empty type, boolean type, numeric type, and character type, respectively. Basic type attributes of a class (identifier) ​​are references to attributes of the current class's basic type. Their structure is "hierarchy symbol * attribute name," where the hierarchy defaults to the class and progresses to attributes within the object's condition. Attribute names without hierarchy symbols represent attributes within the current hierarchy. Hierarchy symbols provide location information about the hierarchy, including relative addressing such as `this`, `super`, and `top`, which respectively provide the option to remain unchanged, move up one level, or move to the highest level. Absolute addressing, such as attribute names, also provides progression through the hierarchy. Basic type attributes of other classes (references) are similar to basic type attributes of a class, except that they include a prefix of the class name to provide references to other classes. A method call consists of two parts: the method itself and a parameter list. The structure of a method is similar to that of basic type attributes of a class and other classes. The attribute name is interpreted as the method name, thus providing a reference to methods in the current class and other classes. The parameter list uses parentheses "(" and ")" to enclose a set of operands, with each operand separated by a comma.

[0114] It should be understood that the constraint rule information is the condition information described using CJSON. In this embodiment, the condition information in the design specification information is converted into constraint rule information.

[0115] Step S102: Based on the syntax parser, the constraint rule information is transformed into the condition part of the business rule in the rule engine.

[0116] Further, step S102 includes: generating the syntax parser according to the preset lexical rules and the preset syntax structure rules; performing lexical parsing on the constraint rule information based on the syntax parser to obtain keywords; performing syntax parsing on the syntax structure corresponding to the keywords to obtain a syntax tree; and generating the condition part of the business rules in the rule engine based on the syntax tree.

[0117] It should be noted that the parser used in this embodiment is the Antlr4 parser, but other parsers can also be used; this embodiment does not impose any restrictions on this. Keywords are tokens obtained through lexical analysis, and at least include conditional connectors, comparison operators, operators, literals, identifiers, class variable operators, classes, and reference operators. Conditional connectors at least include the "AND" and "OR" conditional connectors; the AND conditional connector is usually "&&", and the OR conditional connector is usually "||". Comparison operators include basic comparison operators and advanced comparison operators. Basic comparison operators at least include the greater than (">"), less than (<), equal to (=="), and combined comparison operators (">=", "<=", "!="). Advanced comparison operators at least include the regular expression comparison operator (matches) and the list search comparison operators (contains, memberOf). Operators at least include parenthesis operators (() and ")"), addition and subtraction operators (+ and -), multiplication and division operators (* and / ), and unary operators. Literals include at least empty type literals, logical type literals, numeric type literals, and character type literals, that is, empty type literals, logical type literals, numeric type literals, and character type literals. The reference symbol is "$".

[0118] Understandably, ANTLR4 divides language parsing into lexical and syntactic stages. First, it lexically decomposes the source content (conditional rule data) into keywords. Then, it uses the syntactic structure formed by these keywords to parse the corresponding syntax tree. ANTLR4 also provides pre-defined classes `CJSONBaseVisitor` and `CJSONBaseListener` for these syntactic classes, representing visitor and listener design patterns. Users can encapsulate code based on these classes to implement custom processing for different syntaxes. For example... Figure 11 The image shows a schematic diagram of the CJSON data format.

[0119] In its implementation, ANTLR4 divides language parsing into lexical and syntactic stages. First, the source content (conditional rule data) is lexically decomposed into keywords. Then, the corresponding syntax tree is parsed using the keywords, and finally, the condition part of the business rule is generated.

[0120] Step S103: Convert the action information in the design specification information into the action part of the business rules in the rule engine.

[0121] In the specific implementation, the bridge specification database is accessed to read the design specification information. Each field of the design specification information is parsed, and its structure is converted into conditional and action structure information. The conditional information is the CJSON description of the current specification clause, and the action information is a hint from the original specification text. ANTLR4 is used to parse the CJSON description of the conditional information in the design specification information, converting it into the conditional part of a Drools rule to match business entities. The action information in the design specification information, i.e., the original specification text, is used as the action part of the Drools rule to construct the output result.

[0122] It should be understood that the triggering conditions are also described using CJSON, and the database structure is constructed according to CJSON.

[0123] In this embodiment, design specification information is retrieved from a bridge specification database. Based on preset lexical and grammatical structure rules, the conditional information in the design specification information is transformed into constraint rule information. Using a syntax parser, the constraint rule information is then transformed into the conditional part of business rules in a rule engine, and the action information in the design specification information is transformed into the action part of business rules in the rule engine. This embodiment can automatically push applicable specification clauses, shifting from traditional passive knowledge retrieval to adaptive knowledge matching and proactive push, achieving comprehensive and rapid push, and improving the quality and efficiency of scheme design.

[0124] Reference Figure 12 , Figure 12 This is a flowchart illustrating the second embodiment of a method for proactively pushing GIS environment specification clauses based on a rule engine according to the present invention.

[0125] Based on the above embodiments, in this embodiment, step S30 includes:

[0126] Step S301: Based on the retrieval type, match the standardized request information with the condition part of the business rule to determine the matching condition part.

[0127] Further, step S301 includes: determining the retrieval type of the condition part of the business rule based on the retrieval type of the design specification information; determining a first matching condition part in the condition part of the control point retrieval type based on the control point information; determining a second matching condition part in the condition part of the business entity retrieval type based on the target entity object information; and determining a third matching condition part and a fourth matching condition part in the condition parts of the general retrieval type and the complex retrieval type, respectively.

[0128] It should be noted that the matching condition part is the portion of the business rule's condition part that can match the specification request information. In this embodiment, since the design specification information can be divided into multiple retrieval types, matching is also performed according to each retrieval type to obtain the matching part corresponding to each retrieval type. For control point retrieval type, business entity retrieval type, general retrieval type, and complex retrieval type, the corresponding parts are the first matching condition part, the second matching condition part, the third matching condition part, and the fourth matching condition part, respectively.

[0129] It is understandable that control point information can usually be used to match the specification clauses of the control point retrieval type, target entity object information can usually be used to match the specification clauses of the business entity retrieval type, all specification request information can match the specification clauses of the general retrieval type, and the matching of specification clauses of the complex retrieval type needs to be determined according to the actual needs.

[0130] It should be understood that any type of retrieval specification can have multiple levels of enforcement.

[0131] Step S302: Obtain the canonical reasoning result based on the action part corresponding to the matching condition part.

[0132] In its implementation, for the input specification request information, the Drools rule engine matches the values ​​of its relevant attribute fields with the constraints described in the business rule condition section. If a match is found, the action section of the rule will be activated, and the specification clause corresponding to that action section will be returned as the currently applicable specification clause.

[0133] In this embodiment, based on the retrieval type, the specification request information is matched with the conditional parts of the business rules to determine the matching conditional parts. Based on the action parts corresponding to the matching conditional parts, the specification inference result is obtained. This embodiment categorizes specification clauses into general retrieval types, control point retrieval types, business entity retrieval types, and complex retrieval types. Each type automatically matches and pushes applicable specification clauses, shifting from traditional passive knowledge retrieval to adaptive knowledge matching and proactive push, achieving comprehensive and rapid push, and improving the quality and efficiency of solution design.

[0134] Furthermore, this embodiment of the invention also proposes a storage medium storing a proactive push program for GIS environment specification clauses based on a rule engine. When the proactive push program for GIS environment specification clauses based on a rule engine is executed by a processor, it implements the steps of the proactive push method for GIS environment specification clauses based on a rule engine as described above.

[0135] Reference Figure 13 , Figure 13 This is a structural block diagram of the first embodiment of the rule engine-based GIS environment specification clause proactive push system of the present invention.

[0136] like Figure 13 As shown, the proactive push system for GIS environment specification clauses based on a rule engine proposed in this embodiment of the invention includes:

[0137] The rule generation module 10 is used to obtain design specification information from the bridge specification database and generate business rules for the rule engine based on the design specification information.

[0138] The specification request module 20 is used to select target entity objects and generate specification request information based on the current design scheme in the GIS environment.

[0139] The normative reasoning module 30 is used to send the normative request information to the rule engine with the business rules for reasoning and to obtain the normative reasoning result.

[0140] The normative reasoning module 30 is also used to classify the normative reasoning results based on the execution level and generate applicable normative clause information.

[0141] The specification push module 40 is used to push and display the applicable specification clauses in the GIS environment.

[0142] The specification request module 40 uses the event mechanism of the GIS environment to realize the specification request information corresponding to the target entity object. The event can be a regular event such as double-clicking, single-clicking, or hovering, which needs to be provided by the GIS environment or the operating system it depends on.

[0143] In this embodiment, design specification information is obtained from the bridge specification database. Based on this information, business rules for a rule engine are generated. Target entity objects are selected based on the current design scheme in the GIS environment, and specification request information is generated. This request information is sent to the rule engine with business rules for reasoning, yielding specification reasoning results. Based on execution level, the reasoning results are categorized, and applicable specification clause information is generated and displayed in the GIS environment. When designing bridge span layout, compared to traditional methods of obtaining span layout guidelines, which are time-consuming and difficult to fully consider, affecting the quality and efficiency of the design, this embodiment can automatically push applicable specification clauses. It shifts from traditional passive knowledge retrieval to adaptive knowledge matching and proactive pushing, achieving comprehensive and rapid push, improving the quality and efficiency of the design, and lowering the business threshold for bridge engineers.

[0144] In one embodiment, the rule generation module 10 is further configured to obtain design specification information from the bridge specification database, and convert the condition information in the design specification information into constraint condition rule information according to preset lexical rules and preset grammatical structure rules;

[0145] Based on the syntax parser, the constraint rule information is transformed into the condition part of the business rules in the rule engine;

[0146] The action information in the design specification information is transformed into the action part of the business rules in the rule engine.

[0147] In one embodiment, the specification request module 20 is further configured to match the specification request information with the condition portion of the business rule based on the retrieval type to determine the matching condition portion;

[0148] The canonical reasoning result is obtained based on the action part corresponding to the matching condition part.

[0149] In one embodiment, the specification request module 20 is further configured to determine the retrieval type of the condition part of the business rule based on the retrieval type of the design specification information, wherein the retrieval type includes at least a general retrieval type, a control point retrieval type, a business entity retrieval type, and a complex retrieval type;

[0150] Based on the control point information, a first matching condition portion is determined in the condition portion of the control point retrieval type;

[0151] Based on the target entity object information, a second matching condition part is determined in the condition part of the business entity retrieval type;

[0152] In the condition sections of the general search type and the complex search type, the third matching condition section and the fourth matching condition section are determined respectively.

[0153] In one embodiment, the rule generation module 10 is further configured to generate the syntax parser based on the preset lexical rules and the preset syntax structure rules. The preset lexical rules include at least conditional connector rules, comparison operator rules, operator rules, literal rules, identifier rules, class variable rules, class rules, and reference rules. The preset syntax structure rules include at least class constraint structure rules and condition structure rules. The condition structure rules include at least object condition structure rules, compound condition structure rules, and comparison expression structure rules.

[0154] Based on the syntax parser, the constraint rule information is lexically analyzed to obtain keywords;

[0155] Syntax parsing is performed based on the grammatical structure corresponding to the keywords to obtain a syntax tree;

[0156] Based on the syntax tree, the condition part of the business rules in the rule engine is generated.

[0157] In one embodiment, the rule generation module 10 is further configured to acquire bridge specification document information, and determine design specification information based on the bridge specification document information, wherein the design specification information includes general attribute information and measure information;

[0158] The measure information in the design specification information is split according to the preset segmentation elements to obtain a set of conditional action pairs;

[0159] Based on the set of conditional action pairs, determine the conditional information and action information corresponding to the design specification information respectively;

[0160] Based on the general attribute information, measure information, condition information, and action information of the design specification information, a specification knowledge graph is constructed.

[0161] In one embodiment, the rule generation module 10 is further configured to extract knowledge from the design specification information based on preset fields to generate a specification knowledge table. The preset fields include at least clause measures, execution level, condition classification, standard basis, clause number, clause content, event classification, engineering stage, bridge grade, bridge and culvert classification, structural system, constraint object, construction method, line relationship, geological classification, topographic classification, hydrological classification, control point classification, interface constraint, and keyword list.

[0162] Based on the retrieval type of the design specification information, set the trigger conditions for the design specification information, and add the trigger conditions to the specification knowledge table;

[0163] Based on the semantics of the design specification information, determine the functional classification and attributes of the condition information and the action information. The functional classification of the condition information includes at least empty constraints, control point constraints, and beam type constraints. The functional classification of the action information includes at least beam type query, prompt items, and beam type filtering.

[0164] Based on the functional classification and attributes of the design specification information, determine the structural type of the design specification information, and based on the structural type, determine the database structure of the design specification information;

[0165] The standard knowledge table is mapped to the database structure of the design standard information so that the standard knowledge graph is stored in the bridge standard database.

[0166] In one embodiment, the structure type includes object constraint type and fixed structure type. The database structure corresponding to the object constraint type includes at least object type and constraint condition. The constraint condition includes at least comparison expression, combined constraint condition and sub-object constraint. The comparison expression includes at least attribute name, constant and operator. The combined constraint condition includes at least condition combiner and sub-constraint condition.

[0167] In one embodiment, the rule generation module 10 is further configured to group the business rules according to the condition information and logical priority information of the design specification information to obtain an agenda rule group and an activation rule group, and set the intra-group priority attribute and inter-group priority attribute of the agenda rule group and the activation rule group.

[0168] It should be understood that the above are merely illustrative examples and do not constitute any limitation on the technical solutions of the present invention. In specific applications, those skilled in the art can make settings as needed, and the present invention does not impose any restrictions on this.

[0169] It should be noted that the workflow described above is merely illustrative and does not limit the scope of protection of this invention. In practical applications, those skilled in the art can select some or all of the workflow to achieve the purpose of this embodiment according to actual needs, and no restrictions are imposed here.

[0170] In addition, for technical details not described in detail in this embodiment, please refer to the method for actively pushing GIS environment specification clauses based on rule engine provided in any embodiment of the present invention, which will not be repeated here.

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

[0172] The sequence numbers of the above embodiments of the present invention are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0173] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as read-only memory (ROM) / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal device (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods described in the various embodiments of the present invention.

[0174] The above are merely preferred embodiments of the present invention and do not limit the scope of the patent. Any equivalent structural or procedural transformations made based on the description and drawings of the present invention, or direct or indirect applications in other related technical fields, are similarly included within the scope of patent protection of the present invention.

Claims

1. A rule engine-based GIS environment specification clause proactive push method, characterized in that, The method for proactively pushing GIS environment specification clauses based on rule engines includes: Obtain design specification information from the bridge specification database, and generate business rules for the rule engine based on the design specification information; Based on the current design scheme in the GIS environment, select the target entity object and generate specification request information; The specification request information is sent to a rule engine containing the business rules for inference to obtain the specification inference result; Based on the execution level, the normative reasoning results are classified to generate information on applicable normative clauses; The applicable standard clauses information will be pushed and displayed in the GIS environment; The method for proactively pushing GIS environment specification clauses based on a rule engine also includes: Obtain bridge specification document information, and based on the bridge specification document information, determine design specification information, which includes general attribute information and measure information; The measure information in the design specification information is split according to the preset segmentation elements to obtain a set of conditional action pairs; Based on the set of conditional action pairs, determine the conditional information and action information corresponding to the design specification information respectively; Based on the general attribute information, measure information, condition information, and action information of the design specification information, a specification knowledge graph is constructed. The method for proactively pushing GIS environment specification clauses based on a rule engine also includes: Based on preset fields, knowledge is extracted from the design specification information to generate a specification knowledge table. The preset fields include at least clause measures, execution level, condition classification, standard basis, clause number, clause content, event classification, engineering stage, bridge grade, bridge and culvert classification, structural system, constraint object, construction method, line relationship, geological classification, topographic classification, hydrological classification, control point classification, interface constraint, and keyword list. Based on the retrieval type of the design specification information, set the trigger conditions for the design specification information, and add the trigger conditions to the specification knowledge table; Based on the semantics of the design specification information, determine the functional classification and attributes of the condition information and the action information. The functional classification of the condition information includes at least empty constraints, control point constraints, and beam type constraints. The functional classification of the action information includes at least beam type query, prompt items, and beam type filtering. Based on the functional classification and attributes of the design specification information, determine the structural type of the design specification information, and based on the structural type, determine the database structure of the design specification information; The standard knowledge table is mapped to the database structure of the design standard information so that the standard knowledge graph is stored in the bridge standard database.

2. The method of claim 1, wherein, The process of obtaining design specification information from the bridge specification database and generating business rules for the rule engine based on that design specification information includes: The design specification information is obtained from the bridge specification database, and the condition information in the design specification information is transformed into constraint condition rule information according to the preset lexical rules and preset grammatical structure rules. Based on the syntax parser, the constraint rule information is transformed into the condition part of the business rules in the rule engine; The action information in the design specification information is transformed into the action part of the business rules in the rule engine.

3. The method as described in claim 2, characterized in that, The specification request information includes at least control point information and target entity object information. The control point information includes at least the control point name, control point type, control point angle, and height limit. Sending the specification request information to a rule engine with the business rules for reasoning to obtain the specification reasoning result includes: Based on the retrieval type, the standardized request information is matched with the condition part of the business rule to determine the matching condition part; The canonical reasoning result is obtained based on the action part corresponding to the matching condition part.

4. The method as described in claim 3, characterized in that, The step of matching the standardized request information with the conditional portion of the business rule based on the retrieval type to determine the matching conditional portion includes: Based on the retrieval type of the design specification information, the retrieval type of the condition part of the business rule is determined. The retrieval type includes at least a general retrieval type, a control point retrieval type, a business entity retrieval type, and a complex retrieval type. Based on the control point information, a first matching condition portion is determined in the condition portion of the control point retrieval type; Based on the target entity object information, a second matching condition part is determined in the condition part of the business entity retrieval type; In the condition sections of the general search type and the complex search type, the third matching condition section and the fourth matching condition section are determined respectively.

5. The method as described in claim 2, characterized in that, The process of converting the constraint rule information into the condition part of the business rules in the rule engine based on the syntax parser includes: The syntax parser is generated based on the preset lexical rules and the preset syntax structure rules. The preset lexical rules include at least conditional connector rules, comparison rules, operator rules, literal rules, identifier rules, class variable rules, class rules, and reference rules. The preset syntax structure rules include at least class constraint structure rules and condition structure rules. The condition structure rules include at least object condition structure rules, compound condition structure rules, and comparison expression structure rules. Based on the syntax parser, the constraint rule information is lexically analyzed to obtain keywords; Syntax parsing is performed based on the grammatical structure corresponding to the keywords to obtain a syntax tree; Based on the syntax tree, the condition part of the business rules in the rule engine is generated.

6. The method as described in claim 1, characterized in that, The structure type includes object constraint type and fixed structure type. The database structure corresponding to the object constraint type includes at least object type and constraint condition. The constraint condition includes at least comparison expression, combined constraint condition and sub-object constraint. The comparison expression includes at least attribute name, constant and operator. The combined constraint condition includes at least condition combiner and sub-constraint condition.

7. The method according to any one of claims 1 to 6, characterized in that, The method for proactively pushing GIS environment specification clauses based on rule engines also includes: The business rules are grouped according to the condition information and logical priority information of the design specification information to obtain agenda rule group and activation rule group, and the intra-group priority attribute and inter-group priority attribute of the agenda rule group and activation rule group are set.

8. A system for proactively pushing GIS environment specification clauses based on a rule engine, used to execute the method as described in any one of claims 1-7, characterized in that, The rule engine-based GIS environment specification clause proactive push system includes: The rule generation module is used to obtain design specification information from the bridge specification database and generate business rules for the rule engine based on the design specification information. The specification request module is used to select target entity objects based on the current design scheme in the GIS environment and generate specification request information. The normative reasoning module is used to send the normative request information to a rule engine with the business rules for reasoning and to obtain the normative reasoning result. The normative reasoning module is also used to classify the normative reasoning results based on the execution level and generate information on applicable normative clauses; The specification push module is used to push and display the applicable specification clauses in the GIS environment.