Automatic crossing method and device for collision of multiple professional pipelines and medium

Abstract

The invention discloses an automatic crossing method and device for collision of multiple professional pipelines and a medium, and the method comprises the steps: recognizing all pipeline collision points with overlapped volumes and different directions based on the pipeline space data of a basement region in a three-dimensional building information model, generating a collision point data set and dividing a plurality of quadrilateral grid regions based on the collision data set; identifying pipelines which have the same trend and have collision points to generate a pipeline group data set, analyzing the pipeline group data set based on a preset crossing priority rule to screen pipeline groups which need to be crossed, determining target crossing pipelines based on the pipeline group groups which need to be crossed, and outputting a crossing pipeline identifier set of the target crossing pipelines in the corresponding grid region; and according to the crossing pipeline identifier set, on the basis of a preset pipeline crossing principle and a pipeline crossing detailed rule, calculating an optimal crossing path geometric parameter of each target crossing pipeline, and generating a three-dimensional space path of the target crossing pipeline after crossing in the three-dimensional building information model.

Description

Technical Field

[0001] This application relates to the field of architectural design technology, and in particular to an automatic overcoming method, equipment and medium for collisions of multiple professional pipelines. Background Technology

[0002] In modern architecture, especially in the basement spaces of large buildings, mechanical and electrical (MEP) piping systems typically involve multiple disciplines such as water supply and drainage, HVAC, and electrical systems, resulting in a wide variety of pipe types and a dense layout. During the 3D design process, because designers from each discipline create their drawings separately, numerous pipe collisions are easily generated when the drawings are superimposed. If these collisions are not effectively addressed, they will directly lead to construction halts, frequent rework and changes, and severely impact project efficiency and quality. Therefore, the detection and handling of pipe collisions has become a crucial aspect of Building Information Modeling (BIM) applications.

[0003] Currently, handling pipeline collision issues mainly relies on manual methods or semi-automated tools. Designers typically need to first use software to perform collision detection, obtain a list of collision points, and then manually adjust the pipeline routing at each collision point, for example, by adding bends or adjusting elevations to achieve crossing. However, this approach is essentially reactive patching and localized optimization. When dealing with individual collision points, designers find it difficult to consider the global optimality of the overall pipeline routing, easily leading to new conflicts arising after resolving one collision, resulting in iterative design processes and high coordination costs. Summary of the Invention

[0004] This application provides an automatic overpass method, device, and medium for multi-disciplinary pipeline collisions to solve the aforementioned technical problems.

[0005] On the one hand, embodiments of this application provide an automatic overpass method for collisions involving multiple professional pipelines, including: Based on the pipeline space data of the basement area in the 3D building information model, all pipeline collision points with overlapping volumes and different directions are identified, a collision point dataset is generated, and multiple quadrilateral grid areas are divided based on the collision dataset; the collision point dataset includes the spatial coordinate information of the collision points, the collision entity type and size information. In each grid region, pipelines with the same direction and collision points are identified, generating a pipeline group dataset. The pipeline group dataset is analyzed based on a preset crossing priority rule to filter pipeline groups that need to be crossed. Based on the set of pipeline groups that need to be crossed, the target pipelines to be crossed are determined, and a set of pipeline crossing identifiers for the target pipelines to be crossed in the corresponding grid region is output. Based on the set of pipeline crossing identifiers, and based on the preset pipeline crossing principles and detailed rules, the optimal crossing path geometric parameters for each target pipeline are calculated, and the three-dimensional spatial path of the target pipeline after crossing is generated in the three-dimensional building information model to eliminate collision points; the geometric parameters include at least the crossing point location and crossing height.

[0006] In one implementation of this application, in each grid region, pipelines with the same direction and collision points are identified to generate a pipeline group dataset, specifically including: Within each grid area, all pipeline entity data are identified, and based on the pipeline orientation information in the pipeline entity data, a vector comparison algorithm is used to group pipeline entities with the same orientation into pipeline groups. Detect whether there are collision points in each pipeline group, and for pipeline groups with collision points, count the pipeline information in the pipeline group; the pipeline information includes the total number of pipelines, the number of heating pipes, the number of pipes other than heating pipes, and the number of cable trays.

[0007] In one implementation of this application, the pipeline group dataset is analyzed based on a preset traversal priority rule to filter pipeline groups that need to be traversed, specifically including: Based on the preset pipeline group crossing priority rules, the pipeline group dataset within the grid area is traversed, and pipeline groups containing air ducts, unpressurized pipes, or heating pipes that are in collision are selected to generate a first priority pipeline group candidate set. For pipeline groups not selected by the first priority pipeline group candidate set, when two or more pipeline groups collide within the same grid area, the total number of pipelines in the colliding pipeline groups is compared, and the pipeline group with the fewest total number of pipelines is selected. If the total number of pipelines is the same, the number of cable trays in the colliding pipeline groups is compared, and the pipeline group with the fewest number of cable trays is selected. If the number of cable trays is also the same, one pipeline group is randomly selected from the colliding pipeline groups to generate the second priority pipeline group candidate set. The candidate sets of the first priority pipeline group and the candidate sets of the second priority pipeline group are merged to form the final set of pipeline groups to be traversed.

[0008] In one implementation of this application, the target pipeline to be traversed is determined based on the set of pipeline groups to be traversed, and a set of pipeline traversal identifiers for the target pipeline to be traversed in the corresponding grid area is output, specifically including: Based on the set of pipeline groups to be crossed, the number of pipeline groups in the grid area where the pipeline groups to be crossed are located is determined. For a grid area containing only one of the pipeline groups to be crossed, all pipelines in the corresponding pipeline group to be crossed are identified as target pipelines to be crossed, and the corresponding pipeline identification is included in the pipeline identification set. For a grid area containing two or more of the aforementioned pipeline groups that need to be crossed, based on collision relationship data, all non-duct pipeline identifiers that collide with the duct are included in the pipeline crossing identifier set, and pipeline identifiers that collide with unpressurized pipes or heating pipes and have different system types are included in the pipeline crossing identifier set. For collisions between unpressurized pipes or between heated pipes, based on the total number of pipes in the group to be crossed, the pipe identifiers of the unpressurized pipes or heated pipes with the smaller total number of pipes in the group to be crossed are included in the crossed pipe identifier set.

[0009] In one implementation of this application, based on the set of pipeline crossing identifiers and a preset pipeline crossing principle and detailed rules, the optimal crossing path geometric parameters for each target pipeline are calculated, specifically including: Based on the set of pipeline crossing identifiers and the number of cable trays and pipe types of the corresponding pipeline groups to be crossed, the order of crossing each pipeline in the current grid is determined according to the preset pipeline crossing principle, and a pipeline crossing order queue is generated. For each target pipeline to be crossed in the pipeline crossing sequence queue, the upward crossing strategy is used first to calculate the crossing height. When the upward crossing path collides with the building structure model or fails to meet the preset space clearance constraints, the strategy is switched to downward crossing and the clearance compliance check is performed. Based on the pipe types at both ends of the target pipeline and the relative position of the target pipeline to be crossed with the colliding entity, predefined crossing point positioning rules are applied to calculate the coordinates of the crossing point and the crossing height value, forming the optimal crossing path geometric parameters.

[0010] In one implementation of this application, based on the pipe types at both ends of the target pipeline and the relative position of the target pipeline to be climbed and the colliding entity, a predefined climbing point positioning rule is applied to calculate the coordinates of the climbing point, specifically including: For pipeline targets that need to be crossed, when one end of the pipeline is not connected to any fittings, the coordinates of the crossing point of the current pipeline port are calculated based on the position of the outermost entity boundary that collides with the current pipeline port and the pipe diameter data, according to a preset first distance offset formula. When one end of the pipe is connected to an elbow fitting, the geometric center position of the elbow fitting is obtained, and the coordinates of the overturning point are determined at the elbow based on the preset second distance offset rule. When one end of the pipe is connected to a tee or cross fitting, the geometric boundary position of the fitting and the pipe diameter data are obtained, the coordinates of the overturning point are calculated according to the preset third distance offset formula, and the height of the branch pipeline of the fitting remains unchanged. The coordinates of the crossing points calculated at both ends of the pipeline are used as the starting and ending points of the horizontal projection of the pipeline crossing path.

[0011] In one implementation of this application, based on the pipe types at both ends of the target pipeline and the relative position of the target pipeline to be climbed and the colliding entity, a predefined climbing point positioning rule is applied to calculate the coordinates of the climbing point, specifically including: For cable tray targets that need to be crossed over pipelines, when one end of the cable tray is not connected to any cable tray accessories, the coordinates of the crossing point of the current cable tray port are calculated based on the position of the outermost entity boundary that collides with the current cable tray port, according to the preset fourth distance offset rule. When the cable tray has a T-shaped fitting and the vertical section needs to be crossed, the horizontal distance between the T-shaped edge and the object being collided with is determined. If the preset minimum spacing threshold is met, the calculation is performed according to the rule for the end without fitting. If not, the horizontal section where the T-shaped fitting is located is regarded as a whole, and the coordinates of the crossing point are uniformly calculated at the boundary of the fitting or the object being collided at the outermost end of the horizontal section according to the preset fifth distance offset rule. When multiple cable trays with fittings need to be crossed within the same pipeline group, the cable trays are sorted based on the collision point location and the number of fittings, and a different crossing height value is assigned to each cable tray according to a preset height increment rule. When the cable tray ends involve elbows, tees, or no fittings, based on the preset fitting processing priority order, the corresponding cable trays are processed in the order of elbows, tees, and no fittings, and a preset height difference is added to the cable trays with lower priority when calculating the crossing height.

[0012] In one implementation of this application, based on the pipeline space data of the basement area in a 3D building information model, all pipeline collision points with overlapping volumes and different orientations are identified, and a collision point dataset is generated, specifically including: Traverse the 3D building information model, extract all pipeline entities belonging to the preset pipeline type, and generate a set of pipeline entities to be detected; the preset pipeline professional type includes at least pipes, cable trays, and air ducts. Traverse the set of pipeline entities to be detected, detect whether there is spatial volume overlap between any two pipeline entities, and for two pipeline entities with spatial volume overlap, calculate the direction difference based on the axial direction vector of the two pipeline entities. When the direction difference is greater than a preset angle threshold, it is determined as a valid collision point. For each valid collision point, the spatial coordinate information of the valid collision point is recorded, and the collision entity type and size information of the two pipeline entities that collide are associated and stored to form a structured collision point record. All collision point records are summarized to generate a collision point dataset.

[0013] On the other hand, embodiments of this application also provide an automatic overpass device for collisions involving multiple professional pipelines, the device comprising: At least one processor; And, a memory communicatively connected to the at least one processor; The memory stores instructions that can be executed by the at least one processor, which enable the at least one processor to perform an automatic bypass method for multi-discipline pipeline collisions as described above.

[0014] On the other hand, this application embodiment also provides a non-volatile computer storage medium storing computer-executable instructions, which, when executed, implement an automatic overcoming method for multi-disciplinary pipeline collisions as described above.

[0015] This application provides an automatic overpass method, device, and medium for multi-disciplinary pipeline collisions, which has at least the following beneficial effects: By identifying collision points from 3D building information models and generating datasets, this method replaces the traditional, tedious, and easily overlooked manual collision detection and recording. Furthermore, through automated mesh generation and intelligent decision-making based on preset rules, it replaces the process of developing overpass solutions that relies entirely on the designer's personal experience and repeated trial and error. By dividing the mesh area and determining pipeline groups, and making decisions based on preset overpass priority rules, the processing perspective is elevated from a single collision point to a global level encompassing the entire mesh area and even the entire basement space. By analyzing the distribution, type, and quantity relationships of all pipelines within the entire mesh, and applying priority rules, the optimal overpass targets and order are scientifically determined, avoiding new chain collision problems caused by local adjustments in traditional methods. By automatically calculating overpass path parameters and modifying the model, it replaces manual modeling operations such as adjusting pipeline elevations, shortening the cycle of integrated pipeline design. Attached Figure Description

[0016] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings: Figure 1 A flowchart illustrating an automatic overcoming method for multi-disciplinary pipeline collisions provided in this application embodiment; Figure 2 This is a schematic diagram of a pipeline group acquisition method provided in an embodiment of this application; Figure 3 This is a schematic diagram of a method for determining a target pipeline to be traversed, provided in an embodiment of this application. Figure 4 A schematic diagram of another target pipeline crossing determination method provided in this application embodiment; Figure 5 This is a schematic diagram of pipeline crossing provided in an embodiment of this application; Figure 6 This is a schematic diagram of a pipe tee crossing provided in an embodiment of this application; Figure 7 This is a schematic diagram of a cable tray crossing provided in an embodiment of this application; Figure 8 This is a schematic diagram of the internal structure of an automatic overpass device for collisions between multiple professional pipelines, provided as an embodiment of this application. Detailed Implementation

[0017] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions of this application will be clearly and completely described below in conjunction with specific embodiments and corresponding drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. Based on the embodiments in this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0018] The technical solutions provided by the various embodiments of this application are described in detail below with reference to the accompanying drawings.

[0019] Figure 1 This is a flowchart illustrating an automatic overcoming method for multi-disciplinary pipeline collisions provided in an embodiment of this application.

[0020] The analysis method involved in the embodiments of this application can be implemented by a terminal device or a server, and this application does not impose any special limitations on it. For ease of understanding and description, the following embodiments are all described in detail using a server as an example.

[0021] It should be noted that the server can be a single device or a system composed of multiple devices, i.e., a distributed server. This application does not make any specific limitations on this.

[0022] like Figure 1 As shown in the embodiment of this application, an automatic overpass method for multi-disciplinary pipeline collisions is provided, including: Step 101: Based on the pipeline space data of the basement area in the 3D building information model, identify all pipeline collision points with overlapping volumes and different directions, generate a collision point dataset, and divide multiple quadrilateral grid areas based on the collision dataset.

[0023] It should be noted that the collision point dataset in this application embodiment includes collision point spatial coordinate information, collision entity type and size information.

[0024] A 3D building information model is a digital model that contains precise location and attribute information of buildings, structures, and mechanical and electrical pipelines. It can be understood that pipeline spatial data is extracted from this model and is used to describe the geometric characteristics of the pipelines, mainly including the 3D coordinates of the pipeline's centerline, cross-sectional shape, dimensions, and elevation.

[0025] In this embodiment, when identifying collision points, firstly, the 3D building information model is traversed, and entities with preset pipe types, such as pipes, cable trays, air ducts, and sprinkler pipes, are selected. All target pipes requiring collision detection are extracted, forming a set of pipe entities to be detected. Next, the pipes in the set are checked pairwise. The existence of volume overlap is determined by calculating whether their spatial bounding boxes intersect. For pipe pairs with volume overlap, the angle between the axial direction vectors of the two pipes is further calculated. For example, when this angle is greater than a preset angle threshold, their directions are considered different, thus determining a valid collision point. Finally, for each valid collision point, its spatial coordinates are recorded, and the collision entity type and size information of the two colliding pipes are associated and stored, forming a structured collision point record. The set of all records constitutes the collision point dataset. It should be noted that collision entity types include fire hydrants and cable trays, and size information includes pipe diameter DN150 and cable tray specifications 200x100.

[0026] Understandably, after generating the collision point dataset, the spatial distribution of collision points reflected in this dataset, combined with building structure data, is used to divide the space into grid regions. Specifically, the division is based on the layout of major structural components such as columns and walls in the model, with the aim of dividing the complex basement space into multiple regular, continuous quadrilateral regions. Each grid serves as an independent analysis unit, and subsequent collision processing is performed independently or in conjunction within each grid. This decomposes the global problem into multiple local problems for processing, helping to simplify computational complexity and better reflect the actual building structure.

[0027] Step 102: In each grid area, identify pipelines with the same direction and collision points, generate a pipeline group dataset, and analyze the pipeline group dataset based on the preset crossing priority rules to filter the pipeline groups to be crossed. Based on the set of pipeline groups to be crossed, determine the target pipeline to be crossed and output the set of pipeline crossing identifiers for the target pipeline to be crossed in the corresponding grid area.

[0028] In this embodiment, firstly, pipelines are grouped within each grid area. Specifically, the program identifies all pipelines within the grid and, by calculating the direction vector of the pipeline centerline, uses a vector comparison algorithm, such as calculating the cosine of the vector angle, groups pipelines with essentially the same direction into the same pipeline group. Then, it detects whether there are collision points within each pipeline group and, for pipeline groups with collisions, statistically analyzes their key information to generate a pipeline group dataset. For example, the pipeline group dataset includes the total number of pipelines z in the current pipeline group, the number of heating pipes p, the number of pipes other than heating pipes n, and the number of cable trays m. It should be noted that, due to the special nature of ducts, they are usually not included in the quantity statistics, but their existence is marked.

[0029] like Figure 2 As shown in the left-middle figure, for the current grid region, pipelines with the same direction and collision points are identified and grouped into the same pipeline group. Then, as... Figure 2 As shown in the middle right figure, the pipeline group is expanded to match the width of the current grid area by selecting areas where pipelines with the same direction and collision points are circled.

[0030] In this embodiment, the system traverses the pipeline group dataset within the current grid area based on a preset pipeline group crossing priority rule. First, if a pipeline group contains at least one of three specific types of pipelines—air ducts, unpressurized pipes, or heating pipes—and there are collision points within the group (i.e., volume overlap and intersection between pipelines within the group), then the pipeline group is included in the first priority pipeline group candidate set. For example, air ducts typically have large cross-sectional dimensions, high modification costs, and significant impact on airflow organization; unpressurized pipes (such as gravity drainage pipes) must maintain a certain drainage slope, and their elevation is not easily changed; heating pipes may have special requirements such as thermal expansion compensation. Therefore, in the pipeline integration avoidance principle, other specialized pipelines usually need to actively avoid these special pipelines.

[0031] Next, for pipeline groups not selected by the first-level rules, such as collision groups containing only pressurized pipes and cable trays, if two or more pipeline groups exist within the same grid area and they collide with each other or internally, the total number of pipelines in these colliding pipeline groups is compared, and the pipeline group with the fewest total pipelines is prioritized as the pipeline group to be crossed. This is because crossing and adjusting a pipeline group with fewer pipelines results in relatively minimal engineering work, material changes, and impacts on other related systems, which aligns better with the basic principle of controlling the scope of changes in engineering optimization.

[0032] It should be noted that when the total number of pipes in the colliding pipe groups is exactly the same, the system will further compare their cable tray counts and select the pipe group with fewer cable trays as the pipe group to be crossed. This is because cable trays typically carry multiple or even dozens of cables, and crossing them may involve re-laying cables or adjusting reserved lengths, which is more complex and carries greater potential risks than crossing a single pipe. Therefore, the pipe group with fewer cable trays is given priority for adjustment. For example, if one pipe group has 2 pipes and 3 rows of cable trays, and another pipe group has 4 pipes and 1 row of cable trays, although the total number of pipes in both groups is 5 (here, cable trays are counted as 1 pipe entity per "row"), the system will select the latter pipe group with fewer cable trays (1 row) as the candidate pipe group to be crossed.

[0033] If two pipeline groups have the same number of cable trays, it means that the current rules cannot further differentiate the degree of optimization. In this case, any pipeline group can be selected as the pipeline group to be traversed, and the decision result is acceptable from an engineering perspective. Finally, merging the first priority candidate set and the second priority candidate set yields the final set of pipeline groups to be traversed within the current grid that needs to be addressed.

[0034] In this embodiment, after determining the pipeline group to be traversed, it is necessary to further identify, based on more specific collision relationships, the target pipelines that actually need to change their spatial paths from the pipeline group to be traversed, and generate an identifier set for them. Specifically, when determining the target pipelines to be traversed within the pipeline group to be traversed, the system first analyzes the distribution of the pipeline group to be traversed within the current grid, that is, determines the number of pipeline groups contained in the set. This number is a key branch condition for determining which refinement rules to use subsequently.

[0035] In the simplest case, where the grid area contains only one group of pipelines to be traversed, the system will identify all pipeline entities recorded in the dataset of that pipeline group as the target pipeline to be traversed. This is because, given that collisions already exist within the group, uniformly traversing the entire group is the most thorough and efficient way to resolve all cross-collisions within the group and ensure route consistency. These identified pipeline IDs will be collected and included in the pipeline traversal identifier set corresponding to that grid.

[0036] For more complex scenarios, where the grid area contains two or more groups of pipelines that need to be traversed, the system needs to analyze the specific collision relationship data in depth, such as recording which two specific pipeline entities collided. First, in any collision relationship, as long as one of them is a duct, then the identifiers of all non-duct pipelines that collide with the duct, whether pipes or cable trays, will be included in the pipeline traversal identifier set.

[0037] Secondly, for collisions involving unpressurized or heated pipes (and not falling under the aforementioned duct collision scenarios), the system checks whether the colliding parties are of different system types. For example, system type can refer to broad professional categories such as water supply and drainage systems, electrical systems, and air conditioning water systems. If the collision occurs between pipes of different system types, such as an electrical cable tray colliding with an unpressurized drainage pipe, the non-unpressurized / non-heated pipe (i.e., the cable tray in this example) will be identified as the target crossing pipe. This rule reflects the avoidance and coordination logic between pipes of different professional categories.

[0038] Finally, for collisions of the same type of pipe occurring between unpressurized pipes or between heated pipes, the decision-making basis returns to the principle of minimizing impact, but this time it's based on the size of the pipe group. The system queries the total number of pipes in each of the two colliding unpressurized (or heated) pipes belonging to the pipe groups that need to be traversed. The pipe with the smaller total number of pipes in its group is selected as the target traversed pipe. For example, assuming the colliding heated pipes A and B, where A belongs to a pipe group with 3 pipes and B belongs to a pipe group with 5 pipes, heated pipe A is selected as the target traversed pipe. This is because having the smaller group handle the traversal of one of its internal pipes may cause less disturbance to the overall layout than having the larger group handle it.

[0039] Through the above three-layer progressive rule filtering, the system can accurately isolate the individual pipelines that actually need to be acted upon from multiple pipeline groups that need to be traversed, and finally output an unambiguous and operable set of pipeline traversal identifiers, providing a clear input target for the final geometric path calculation.

[0040] like Figure 3 As shown, when there are two or more pipeline groups within a grid area, case a is to mark all pipes colliding with the duct as target bypass pipelines, and case b is to mark pipelines of different system types colliding with unpressurized pipes or heating pipes as target bypass pipelines. It should be noted that different system types include water supply pipes and fire hydrant pipes.

[0041] like Figure 4 As shown, case c is a collision that occurs between unpressurized pipes or thermal pipes when there are two or more pipe groups in the grid area. Based on the total number of pipes in the pipe group to be crossed, the pipe identifiers of the unpressurized pipes or thermal pipes with the smaller total number of pipes in the pipe group to be crossed are selected and included in the pipe crossing identifier set.

[0042] Step 103: Based on the set of pipeline crossing identifiers, and the preset pipeline crossing principles and rules, calculate the optimal crossing path geometric parameters for each target pipeline crossing, and generate the three-dimensional spatial path of the target pipeline crossing after crossing in the three-dimensional building information model to eliminate collision points.

[0043] It should be noted that the geometric parameters in the embodiments of this application include at least the location of the crossing point and the crossing height.

[0044] In this embodiment, the system first determines the order of operations among all pipelines to be processed within the current grid based on the set of pipeline identification identifiers and by querying the detailed information of the pipeline groups to which these pipelines belong, especially the number of cable trays and pipe types within the group. This is done according to a preset pipeline crossing principle, and a pipeline crossing order queue is generated. It should be noted that this principle is typically based on common practices for multi-disciplinary coordination. When there is only one pipeline group to be crossed within the grid area, the crossing order is: cable tray, pipe (excluding unpressurized pipes or heating pipes), unpressurized pipe or heating pipe.

[0045] When there are two pipeline groups that need to be crossed within a grid area, priority is given to crossing the cable trays in the group with more cable trays. Next, the ordinary pipes in the same group (excluding unpressurized or heating pipes) are crossed. Then, the cable trays in the group with fewer cable trays are addressed. Following this, the ordinary pipes in the group with fewer cable trays (excluding unpressurized or heating pipes) are crossed. Finally, the unpressurized or heating pipes that may exist in the group with more cable trays, and the unpressurized or heating pipes that may exist in the group with fewer cable trays, are addressed sequentially. This prioritization aims to address the parts that may have the greatest impact on the spatial layout or impose the most constraints, reserving clear adjustment space for subsequent pipelines and avoiding new conflicts or wasted space due to improper processing order.

[0046] After generating the pipeline crossing sequence queue, the system begins individualized path calculation for each target pipeline in the queue. For each pipeline, the algorithm prioritizes an upward crossing strategy by default, i.e., it first attempts to calculate an upward crossing trajectory so that the pipeline bypasses the collided entity. This is because in most basement scenarios, seeking space upwards is usually more feasible and has less impact on functionality than encroaching on the building's clearance height downwards. For example, the algorithm will initially calculate the required upward crossing height based on the height of the collision point and the preset crossing slope. However, this strategy is not always feasible. Therefore, the system performs collision detection and spatial verification in real time to determine whether the virtual upward crossing path will cause new interference with the building structure model (such as concrete beams and floor slabs), or whether the required upward crossing space cannot be satisfied by other existing pipelines.

[0047] Once any infeasibility is detected in the upward path, the system will automatically switch to the downward strategy. Switching to downward means that the pipeline needs to pass under the colliding entity, at which point a strict clearance compliance check must be performed. This check is based on the minimum clearance code value corresponding to the structural bottom elevation, building foundation thickness, and usage attributes of the grid area obtained from the BIM model (such as whether it is a driveway, which has higher clearance requirements). The theoretical bottom elevation of the pipeline after downward is calculated, and it is determined whether it still meets the code requirements. Only when the check passes is the downward solution considered feasible; otherwise, the pipeline may need to be marked as an exception requiring special handling, or feedback may be given to the designer for manual intervention.

[0048] After determining the crossing direction (upward or downward) and the corresponding crossing height baseline, the system needs to accurately calculate the coordinates of the crossing point, another crucial element of the path. This calculation strictly depends on the pipe fitting types at both ends of the target pipeline and the relative position of the pipeline to the colliding entity, applying a series of predefined crossing point positioning rules. For pipelines, pipe fitting types may include flanges, elbows, tees, and crosses; for cable trays, they include horizontal bends, tees, and crosses. The relative position indicates from which section of the pipeline the crossing should begin. Due to significant differences in physical form, connection method, and construction technology between pipelines and cable trays, their crossing point positioning rules are defined separately.

[0049] like Figure 5 As shown, when flipping down, you can disregard the fact that you are only flipping within this grid. If you cannot find a flipping point, you can find the flipping point by combining the positions of the pipelines in the adjacent grids on both sides.

[0050] In this embodiment, the calculation of the crossing point for pipeline targets is a highly refined and case-specific process. The algorithm first identifies the connection status of each end of the pipeline. When one end of the pipeline is not connected to any fittings, i.e., the end of a straight pipe section, the location of the crossing point needs to balance the effectiveness of obstacle avoidance and the convenience of construction. The calculation is based on the position of the outermost physical boundary that collides with the current pipeline port and the pipe diameter data of the pipeline itself. For example, the outermost physical boundary refers to the outermost boundary position among all obstacles that collide with the port along the pipeline direction. The system offsets the boundary position outward along the pipeline axis by a specific distance according to a preset first distance offset formula. This distance is usually proportional to a certain proportion of the pipe diameter and includes a fixed installation operation space margin, thereby calculating the precise coordinates of the crossing point position of the port. This ensures that the crossing starting point is located outside the collision area and leaves space for subsequent connections.

[0051] The situation is different when one end of the pipe is connected to an elbow fitting. The elbow itself is a component that changes direction. Therefore, after obtaining the geometric center position of the elbow fitting, the system, based on a preset second distance offset rule, directly determines the coordinates of the overpass point at or very close to the elbow. This is to combine the change in direction with the change in elevation (overpass) at or immediately after the elbow, making the pipeline path more compact and reducing unnecessary straight pipe sections.

[0052] For more complex connection scenarios, such as when one end of a pipe connects to a tee or cross fitting, the rules need to additionally consider the stability of the branch pipeline. In this case, the system obtains the geometric boundary position of the fitting and the pipe diameter, and calculates the coordinates of the overpass point according to a preset third distance offset formula. This formula typically ensures that the overpass point is set at a certain distance from the connection point with the main pipe to avoid direct involvement of the branch pipeline. A crucial parallel operation is that the system maintains the height of the branch pipeline unchanged throughout the entire calculation and subsequent path generation process. This means that only the main pipe involved in the collision is overpassed and raised or lowered, while the original elevation of other branch pipes connected to the tee or cross remains unchanged, thereby minimizing the impact on non-collision related systems and reflecting the principle of localization of change. Finally, after calculating the coordinates of the overpass points at both ends of the pipe, these two coordinates together define the start and end points of the overpass path on the horizontal plane. Combined with the previously determined overpass height, a complete three-dimensional spatial polyline or curved path can be described.

[0053] like Figure 6 As shown, when the pipe is connected to a tee or cross at both ends, it is turned over at d / 2+50 on the edge of the fitting at both ends, and the pipe at the branch point remains at its original height. When there is a branch (tee or cross) at the turning point, it is turned over at d / 2+50 on the edge of the fitting (if the value is less than 200, take 200), and the pipe at the branch point remains at its original height.

[0054] In this embodiment, the calculation rules for the crossing point of cable trays are more complex due to the integration of the cable tray system and the diversity of its components. In the simplest case, where one end of the cable tray is not connected to any cable tray components, the calculation method is similar to that for pipelines, but the parameters are different. The system calculates the coordinates of the crossing point at that port based on the outermost entity boundary of the collision, according to a preset fourth distance offset rule (usually a fixed safety distance to accommodate the ramp section and installation space required for the cable tray to cross).

[0055] However, cable tray systems extensively use T-joints for line branching, which introduces special scenarios. When a T-joint is detected on a cable tray, and its vertical segment (i.e., the part of the branch pointing upwards or downwards) also needs to be traversed to avoid collision, the algorithm cannot simply handle it alone. It first determines the horizontal distance between the T-joint edge and the object being collided with. If this distance meets a preset minimum spacing threshold, it means there is enough space for the vertical segment to independently complete the traversal. In this case, the traversal point of the vertical segment can be calculated by referring to the rules for the end without the T-joint (i.e., the fourth offset rule). Conversely, if the spacing is insufficient, forcibly traversing independently may result in an overly steep path or interference with nearby structures. In this case, the system treats the horizontal segment containing the T-joint as a whole. The algorithm treats the entire horizontal cable tray containing the T-joint (which may also include other components on the horizontal segment) as a logical unit. At the outermost component or the outermost collision entity boundary of the horizontal segment, it calculates a unified traversal point coordinate according to another set of preset fifth distance offset rules, and uniformly raises or lowers the entire horizontal segment. This ensures the neatness of the cable tray layout and the smoothness of cable laying.

[0056] When multiple cable trays with fittings need to be traversed within the same pipeline group, the system needs to intelligently coordinate their spatial relationships to prevent new spatial conflicts from arising after traversal. Specifically, it sorts the cable trays based on information such as the location of their collision points and the number of fittings, and assigns each cable tray a different, progressively increasing traversal height value according to a preset height increment rule. For example, the first cable tray is traversed at the lowest height, the second is traversed at a fixed height difference, and so on, thus forming a clear, layered, stepped layout in the air.

[0057] Finally, for complex situations involving a mix of elbows, tees, or no fittings at the cable tray ends, the system processes them sequentially according to a preset priority order. Typically, this order is: elbows, tees, no fittings; that is, the system first calculates and determines the crossing path for cable trays with elbows, then processes those with tees, and finally processes those without fittings. During the calculation process, when calculating the crossing height for low-priority cable trays (such as those with tees or no fittings to be processed later), the system adds a preset height difference to their baseline height. This ensures that the later-processed cable trays can smoothly cross the pre-arranged crossing paths, maintaining a clear spatial hierarchy and avoiding intersections. Through this series of detailed and targeted rules, the system can generate reasonable, orderly, and constructible automatic crossing schemes for cable tray systems with varying shapes and connection methods, ultimately forming a coordinated three-dimensional pipeline layout together with the pipeline crossing scheme.

[0058] like Figure 7As shown, when there is a branch (tee or cross) at the crossing point, the crossing should be performed at 350mm from the branch edge, and the vertical section should also be crossed. When there are bends, no fittings, and tees, the crossing should be performed in the order of cable tray with bend, cable tray with tee, and cable tray without fittings, and the crossing height should be 200mm higher than that of the cable tray without fittings (or tee).

[0059] The above are embodiments of the method proposed in this application. Based on the same inventive concept, embodiments of this application also provide an automatic overpass device for multi-disciplinary pipeline collisions, the structure of which is as follows: Figure 8 As shown.

[0060] Figure 8 This is a schematic diagram of the internal structure of an automatic overpass device for multi-disciplinary pipeline collisions provided in an embodiment of this application. Figure 8 As shown, the device includes: At least one processor; And, a memory that is communicatively connected to at least one processor; The memory stores instructions that can be executed by at least one processor, and the instructions, when executed by at least one processor, enable at least one processor to: Based on the pipeline space data of the basement area in the 3D building information model, all pipeline collision points with overlapping volumes and different directions are identified, a collision point dataset is generated, and multiple quadrilateral grid areas are divided based on the collision dataset; the collision point dataset contains the spatial coordinate information of the collision points, the type and size information of the collision entities; In each grid region, pipelines with the same direction and collision points are identified, generating a pipeline group dataset. The pipeline group dataset is analyzed based on a preset crossing priority rule to filter pipeline groups that need to be crossed. Based on the set of pipeline groups that need to be crossed, the target pipelines to be crossed are determined, and the set of pipeline crossing identifiers for the target pipelines to be crossed in the corresponding grid region is output. Based on the set of pipeline crossing identifiers, and based on the preset pipeline crossing principles and detailed rules, the optimal crossing path geometric parameters for each target pipeline are calculated, and the three-dimensional spatial path of the target pipeline after crossing is generated in the three-dimensional building information model to eliminate collision points; the geometric parameters include at least the crossing point location and crossing height.

[0061] This application also provides a non-volatile computer storage medium storing computer-executable instructions, which, when executed, can: Based on the pipeline space data of the basement area in the 3D building information model, all pipeline collision points with overlapping volumes and different directions are identified, a collision point dataset is generated, and multiple quadrilateral grid areas are divided based on the collision dataset; the collision point dataset contains the spatial coordinate information of the collision points, the type and size information of the collision entities; In each grid region, pipelines with the same direction and collision points are identified, generating a pipeline group dataset. The pipeline group dataset is analyzed based on a preset crossing priority rule to filter pipeline groups that need to be crossed. Based on the set of pipeline groups that need to be crossed, the target pipelines to be crossed are determined, and the set of pipeline crossing identifiers for the target pipelines to be crossed in the corresponding grid region is output. Based on the set of pipeline crossing identifiers, and based on the preset pipeline crossing principles and detailed rules, the optimal crossing path geometric parameters for each target pipeline are calculated, and the three-dimensional spatial path of the target pipeline after crossing is generated in the three-dimensional building information model to eliminate collision points; the geometric parameters include at least the crossing point location and crossing height.

[0062] The various embodiments in this application are described in a progressive manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, the device and medium embodiments are basically similar to the method embodiments, so the description is relatively simple; relevant parts can be referred to the description of the method embodiments.

[0063] The devices and media provided in this application are one-to-one with the methods. Therefore, the devices and media also have similar beneficial technical effects as their corresponding methods. Since the beneficial technical effects of the methods have been described in detail above, the beneficial technical effects of the devices and media will not be repeated here.

[0064] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0065] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0066] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0067] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0068] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0069] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0070] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0071] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, article, or apparatus. 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 apparatus that includes that element.

[0072] The above are merely embodiments of this application and are not intended to limit the scope of this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of the claims of this application.

Claims

1. A method for automatic traversal of multi-specialty pipeline collisions, the method comprising: The method comprises: Based on the pipeline space data of the basement area in the three-dimensional building information model, identify all the collision points of the pipelines with different directions and volume overlap, generate a collision point data set, and divide a plurality of quadrilateral grid areas based on the collision data set; the collision point data set contains collision point space coordinate information, collision entity type and size information; In each grid area, identify the pipelines with the same direction and collision points, generate a pipeline group data set, and analyze the pipeline group data set based on the preset crossing priority rules to screen the pipeline groups that need to be crossed, so as to determine the target crossing pipeline based on the pipeline group set that needs to be crossed, and output the crossing pipeline identifier set of the target crossing pipeline in the corresponding grid area; According to the crossing pipeline identifier set, based on the preset pipeline crossing principle and pipeline crossing details, calculate the best crossing path geometric parameters of each target crossing pipeline, and generate the three-dimensional space path of the target crossing pipeline after crossing in the three-dimensional building information model to eliminate the collision points; the geometric parameters at least include the crossing point position and the crossing height.

2. A method of automatic roll-over of multi-specialty pipeline collisions as claimed in claim 1, wherein, In each grid area, identify the pipelines with the same direction and collision points, generate a pipeline group data set, and analyze the pipeline group data set based on the preset crossing priority rules to screen the pipeline groups that need to be crossed, so as to determine the target crossing pipeline based on the pipeline group set that needs to be crossed, and output the crossing pipeline identifier set of the target crossing pipeline in the corresponding grid area; In each grid area, identify all pipeline entity data, and use a vector comparison algorithm to group the pipelines with the same direction into a pipeline group according to the pipeline direction information in the pipeline entity data; Detect whether there is a collision point in each pipeline group, and count the pipeline information in the pipeline group for the pipeline group with the collision point; the pipeline information includes the total number of pipelines, the number of heat pipes, the number of pipes other than heat pipes, and the number of bridge frames.

3. A method of automatic roll-over of a multi-specialty pipeline collision as claimed in claim 2, wherein, Based on the preset crossing priority rules, analyze the pipeline group data set, and screen the pipeline groups that need to be crossed, which specifically comprises: Based on the preset pipeline group crossing priority rules, traverse the pipeline group data set in the grid area, select the pipeline groups in the pipeline group data set that contain air pipes, non-pressure pipes or heat pipe type pipelines and have collisions, and generate a first priority pipeline group candidate set; For the pipeline groups not selected by the first priority pipeline group candidate set, when there are two or more pipeline groups colliding in the same grid area, compare the total number of pipelines of the colliding pipeline groups, select the pipeline group with the least total number of pipelines, if the total number of pipelines is the same, compare the bridge frame quantity data of the colliding pipeline groups, select the pipeline group with the least bridge frame quantity, if the bridge frame quantity is also the same, select one of the colliding pipeline groups to generate a second priority pipeline group candidate set; Merge the first priority pipeline group candidate set and the second priority pipeline group candidate set to form the final pipeline group set that needs to be crossed.

4. A method of automatic roll-over of a multi-specialty pipeline collision as claimed in claim 3, wherein, Based on the pipeline group set that needs to be crossed, determine the target crossing pipeline, and output the crossing pipeline identifier set of the target crossing pipeline in the corresponding grid area, which specifically comprises: determining the number of pipeline groups in the grid region where the pipeline group to be crossed is located, and identifying all pipelines in the corresponding pipeline group to be crossed as target crossing pipelines and including the corresponding pipeline identifiers in the crossing pipeline identifier set for a grid region containing only one pipeline group to be crossed; for a grid region containing two or more pipeline groups to be crossed, based on the collision relationship data, including all non-air pipe pipeline identifiers that collide with the air pipe in the crossing pipeline identifier set, and including pipeline identifiers that collide with non-pressure pipes or heating pipes and have different system types in the crossing pipeline identifier set; for collisions between non-pressure pipes or heating pipes, based on the total number of pipelines in the corresponding pipeline group to be crossed, selecting the pipeline identifiers of the non-pressure pipes or heating pipes with fewer pipelines in the pipeline group to be crossed and including them in the crossing pipeline identifier set.

5. The method of claim 1, wherein, According to the crossing pipeline identifier set, based on the preset pipeline crossing principles and pipeline crossing rules, the optimal crossing path geometric parameters of each target crossing pipeline are calculated, specifically including: Based on the crossing pipeline identifier set and the number of bridge frames and pipe types of the corresponding pipeline group to be crossed, the crossing order of each pipeline in the current grid is determined according to the preset pipeline crossing principles, and a pipeline crossing order queue is generated; For each target crossing pipeline in the pipeline crossing order queue, the up strategy is used to calculate the crossing height first, and when the up path collides with the building structure model or cannot meet the preset space net height constraint, the down strategy is switched to and net height compliance verification is performed; According to the pipe type of the two ends of the target crossing pipeline and the relative position of the target crossing pipeline and the collision entity, the pre-defined crossing point positioning rule is applied to calculate the crossing point position coordinates and the crossing height value, and the optimal crossing path geometric parameters are formed.

6. A method of automatic roll-over of a multi-specialty pipeline collision as claimed in claim 5, wherein, According to the pipe type of the two ends of the target crossing pipeline and the relative position of the target crossing pipeline and the collision entity, the pre-defined crossing point positioning rule is applied to calculate the crossing point position coordinates, specifically including: For a pipeline target crossing pipeline, when one end of the pipeline is not connected to any pipe fitting, based on the outermost entity boundary position colliding with the current pipeline port and the pipe diameter data of the pipeline, the crossing point position coordinates of the current pipeline port are calculated according to a preset first distance offset formula; When one end of the pipeline is connected to an elbow pipe fitting, the geometric center position of the elbow pipe fitting is obtained, and the crossing point position coordinates are determined at the elbow based on a preset second distance offset rule; When one end of the pipeline is connected to a tee or cross pipe fitting, the geometric boundary position of the pipe fitting and the pipe diameter data of the pipeline are obtained, the crossing point position coordinates are calculated according to a preset third distance offset formula, and the height of the branch pipeline of the pipe fitting is kept unchanged; Integrate the crossing point position coordinates calculated at both ends of the pipeline as the horizontal projection starting point and endpoint of the pipeline crossing path.

7. A method of automatic roll-over of multi-specialty pipeline collisions as claimed in claim 5 wherein, According to the pipe type of the two ends of the target crossing pipeline and the relative position of the target crossing pipeline and the collision entity, the pre-defined crossing point positioning rule is applied to calculate the crossing point position coordinates, specifically including: When the bridge crosses the pipeline, based on the outermost entity boundary position colliding with the current bridge port, the preset fourth distance offset rule is used to calculate the crossing point position coordinates of the current bridge port when the bridge is not connected with any bridge accessory at one end; When the bridge has a tee accessory and the vertical section needs to cross, the horizontal distance of the tee edge from the collided entity is determined. If the preset minimum distance threshold is met, the no accessory end rule is used for calculation. If not, the horizontal section where the tee is located is regarded as a whole, and the crossing point position coordinates are uniformly calculated according to the preset fifth distance offset rule at the outermost end accessory or the boundary of the collided entity; When there are multiple bridges with accessories in the same pipeline group that need to cross, the bridges are sorted based on the collision point position and the number of accessories, and different crossing height values are assigned to each bridge according to the preset height increasing rule; When the end of the bridge involves a bend, a tee, or no accessory, the accessory processing priority order is based on the preset accessory processing priority order, and the corresponding bridge is processed in the order of bend, tee, and no accessory. The height difference is increased when calculating the crossing height of the bridge with low priority.

8. The method of claim 1, wherein, Based on the pipeline space data of the basement area in the three-dimensional building information model, all pipeline collision points with volume overlap and different directions are identified, and a collision point dataset is generated, including: Traverse the three-dimensional building information model to extract all pipeline entities belonging to the preset pipe type, and generate a set of pipeline entities to be detected. The preset pipeline professional type at least includes pipe, bridge, and air pipe; Traverse the set of pipeline entities to be detected to detect whether there is spatial volume overlap between any two pipeline entities. For two pipeline entities with spatial volume overlap, the direction vector of the axis of the two pipeline entities is calculated based on the direction vector of the axis of the two pipeline entities. When the direction difference is greater than the preset angle threshold, it is determined as an effective collision point. For each effective collision point, record the spatial coordinate information of the effective collision point, and associate and store the collision entity type and size information of the two pipeline entities that collide to form a structured collision point record. All collision point records are collected to generate a collision point dataset.

9. An automated roll-over apparatus for multi-discipline pipeline collisions, characterized by, The device comprises: at least one processor; and a memory connected in communication with the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform the automatic crossing method of the multi-specialty pipeline collision according to any one of claims 1-8.

10. A non-transitory computer storage medium storing computer-executable instructions that, when executed, cause a computer to perform: The computer executable instructions are executed to implement the automatic crossing method of the multi-specialty pipeline collision according to any one of claims 1-8.

Images