Data transmission real-time reachability indexing method, device and equipment based on 5G communication and dynamic topology awareness and storage medium

Abstract

The invention provides a data transmission real-time reachability indexing method and device based on 5G communication and dynamic topology awareness, equipment and a storage medium. Relates to the technical field of intelligent mine data transmission optimization. The method comprises the following steps: establishing a double-layer dividing and conquering architecture to realize hierarchical management of network topology, triggering index updating based on an event-driven mechanism, and realizing reachability verification through capacity injection judgment. According to the method, aiming at the characteristics of an intelligent mine underground dynamic transportation network, through the technical means of double-layer division architecture + event-driven updating + capacity injection judgment, the problems of response delay, capacity non-perception, heavy edge node burden and the like of the existing static index in underground environment application are effectively solved.

Description

Technical Field

[0001] This application relates to the field of intelligent mine data transmission optimization technology, and in particular to a method, apparatus, device and storage medium for real-time reachability indexing of data transmission based on 5G communication and dynamic topology awareness. Background Technology

[0002] Data transmission network nodes, such as mining trucks, conveyor belts, and intersections, are highly dynamic in their states, such as failures, landslides, and load changes. This creates three major bottlenecks in traditional data query indexing methods for determining reachability.

[0003] 1. Response delay: Static indexes often use R-trees, path labels, and other technologies to achieve full graph reconstruction, which takes up to minutes and cannot meet the requirements of second-level or sub-second-level emergency response.

[0004] 2. Lack of capacity awareness: Existing methods only determine "whether it is reachable", ignoring real-time capacity constraints such as mine car load and conveyor belt load, which can easily lead to path planning failure.

[0005] 3. Heavy burden on edge nodes: Centralized index maintenance requires global data transmission, putting significant pressure on the computing power and bandwidth of edge nodes.

[0006] In summary, static indexes are suitable for low-frequency change scenarios such as above-ground road networks and power grids, but when facing underground environments, the following situations may be encountered.

[0007] (1) Delayed disaster response: Accidents such as landslides / failures can cause the entire index to become invalid; (2) Uncontrolled resource consumption: The data storage of a large number of nodes has exceeded the actual capacity of the edge gateway; (3) Missing node label attribute data: The inability to integrate attribute data such as mine car load and conveyor belt speed results in a lack of real-time constraints, affecting the indexing results.

[0008] Therefore, how to achieve accurate and rapid response to dynamic data transmission networks is a technical problem that urgently needs to be solved. Summary of the Invention

[0009] This application provides a method, apparatus, device, and storage medium for real-time reachability indexing of data transmission based on 5G communication and dynamic topology awareness. It aims to achieve accurate and rapid response to dynamic data transmission networks through a two-layer divide-and-conquer architecture, event-driven updates, and capacity injection determination.

[0010] In a first aspect, this application provides a method for real-time reachability indexing of data transmission based on 5G communication and dynamic topology awareness, comprising: A two-layer divide-and-conquer architecture is established to achieve hierarchical management of network topology. This architecture includes a global management layer and a local execution layer. The global management layer uses a central server as a lightweight coordination center. This central server manages the macro-level topology and partitions, storing the mapping from node locations to edge nodes, the three-dimensional coordinate boundaries of partition spaces, the gateway addresses of partition edge computing nodes, the adjacency relationships of each partition, the total number of nodes within each partition, load levels, and key health indicators, but does not process specific real-time data. The local execution layer includes at least two distributed edge nodes deployed in underground tunnels, managed by the edge gateways of each partition, and responsible for storing detailed topology, real-time status, and local index information within each partition. The index update is triggered based on an event-driven mechanism, including: when a sudden change in the state of a node in the transportation network, such as excessive displacement, fault signal, or sudden load change, a response action is triggered to generate a path; wherein, the response action includes locating the abnormal node, determining the range of the affected subgraph, and performing the corresponding subgraph update according to the level of the node state change. Reachability verification is achieved through capacity injection determination, including: establishing a capacity constraint model that includes node ID, maximum capacity, real-time load and load weight; during the path reachability verification process, the capacity constraint model is used to check whether the path exists; and through the collaboration of the scheduling center, indexing system, sensor network and capacity decision-maker, the path carrying capacity is dynamically evaluated; and the path is determined to be available only when the real-time load of the node meets the capacity constraint.

[0011] In one possible design, the global management layer adopts a hash partitioning management method, partitioning nodes according to their spatial location, dividing nodes in the same alley or adjacent areas into the same partition, and the global management layer contains a global partition table, which records the edge gateway IP address corresponding to each partition ID and the relationship between adjacent partitions, for cross-partition path lookup. The local index information of the local execution layer is a quadtree index. The quadtree is based on the 2.5-dimensional environmental characteristics of the underground roadway and divides the XY plane to achieve spatial partition management.

[0012] In one possible design, the triggering methods for state mutation events in the event-driven index update step include: When UWB detects that the displacement of the mining truck exceeds a preset threshold within a set time, it triggers a sudden event indicating that the displacement has exceeded the limit. When the device's heartbeat signal disappears, a sudden status event of device failure is triggered; When the real-time load change of a node exceeds the set range, a sudden load change event is triggered.

[0013] In one possible design, determining the scope of the affected subgraph includes: Determine the subgraph containing the affected nodes within a specified radius, and then update the subgraph. When determining the affected nodes, the following conditions must be met: Spatial proximity: The distance between a node in the subgraph and a node with a state change ≤ a set threshold; Topological dependence: There is a direct or indirect path connection between a node in the subgraph and a node whose state has changed. Functional criticality: The sub-graph includes critical functional nodes, such as path control nodes, conveyor belts and / or material transfer nodes.

[0014] In one possible design, performing the corresponding subgraph update based on the level of node state mutation includes: Determine the displacement level based on the displacement setting; Different subgraph update schemes are selected based on different displacement levels; wherein, the subgraph update scheme includes local update, cooperative network update and global verification, and spatial index update, topology relationship reconstruction and path replanning are completed during the update process.

[0015] In one possible design, the load weight in the capacity constraint model is calculated as the ratio of real-time load to maximum capacity.

[0016] In one possible design, during path reachability verification, the capacity constraint model is used to check if a path exists. Through the collaboration of a scheduling center, indexing system, sensor network, and capacity decision-maker, the path's carrying capacity is dynamically evaluated. The path is determined to be available only when the real-time load of a node meets the capacity constraint, including: The existence of candidate paths is confirmed through topology verification; If the candidate path is determined to exist, the load weights of the key nodes in the candidate path are obtained; If the remaining capacity of a critical node is below a threshold, access to the candidate path is rejected and the system automatically switches to a backup path; wherein, the critical node is a node determined from the candidate paths.

[0017] Secondly, this application provides a data transmission real-time reachability indexing device based on 5G communication and dynamic topology awareness, the device comprising: The architecture building module is configured to establish a two-layer divide-and-conquer architecture to achieve hierarchical management of network topology. This two-layer architecture includes a global management layer and a local execution layer. The global management layer uses a central server as a lightweight coordination center. This central server is used for macro-level topology and partition management, storing the mapping from node locations to edge nodes, the three-dimensional coordinate boundaries of partition spaces, the gateway addresses of partition edge computing nodes, the adjacency relationships of each partition, the total number of nodes within each partition, load levels, and key health indicators, but does not process specific real-time data. The local execution layer includes at least two distributed edge nodes deployed in underground tunnels, managed by the edge gateways of each partition, and responsible for storing detailed topology, real-time status, and local index information within each partition. The index update module is configured to trigger index updates based on an event-driven mechanism, including: when a sudden change in the state of a node in the transportation network, such as excessive displacement, fault signal, or sudden load change, is detected, a response action is triggered to generate a path; wherein, the response action includes locating the abnormal node, determining the range of the affected subgraph, and performing the corresponding subgraph update according to the level of the node state change. The reachability verification module is configured to perform reachability verification through capacity injection, including: establishing a capacity constraint model containing node ID, maximum capacity, real-time load and load weight; during the path reachability verification process, using the capacity constraint model to check if the path exists; and through the collaboration of the scheduling center, indexing system, sensor network and capacity decision-maker, dynamically evaluating the path carrying capacity; and determining that the path is available only when the real-time load of the node meets the capacity constraint.

[0018] Thirdly, embodiments of this application provide an electronic device, including: at least one processor and a memory; the memory stores computer-executable instructions; the at least one processor executes the computer-executable instructions stored in the memory, causing the at least one processor to perform the real-time reachability indexing method for data transmission based on 5G communication and dynamic topology awareness as described in the first aspect and various possible designs of the first aspect.

[0019] Fourthly, embodiments of this application provide a computer-readable storage medium storing computer-executable instructions. When a processor executes the computer-executable instructions, it implements the real-time reachability indexing method for data transmission based on 5G communication and dynamic topology awareness as described in the first aspect and various possible designs of the first aspect.

[0020] Fifthly, embodiments of this application provide a computer program product, including a computer program that, when executed by a processor, implements the real-time reachability indexing method for data transmission based on 5G communication and dynamic topology awareness as described in the first aspect and various possible designs of the first aspect.

[0021] The data transmission real-time reachability indexing method, apparatus, device, and storage medium based on 5G communication and dynamic topology awareness provided in this application have at least the following beneficial effects: 1) This application adopts an event-driven update mechanism to replace the traditional periodic polling or full graph reconstruction method. Local subgraph updates are triggered only when node states undergo sudden changes (such as failures, excessive displacement, or sudden load changes), avoiding the time-consuming reconstruction after the global index becomes completely invalid. This reduces response time from minutes to seconds or sub-seconds, enabling rapid generation of emergency navigation solutions and significantly improving disaster response capabilities for sudden incidents such as landslides and equipment failures. The local execution layer uses a quadtree index to implement topology management within partitions. The time complexity of node splitting and merging is O(logn), balancing storage efficiency and query speed, further ensuring real-time response performance.

[0022] 2) This application innovatively introduces a capacity injection determination mechanism, establishing a constraint model that includes node ID, maximum capacity, real-time load, and load weight. In reachability verification, it not only checks path existence but also dynamically evaluates real-time carrying capacity such as mine car load and conveyor belt load, avoiding path planning failures caused by ignoring capacity constraints and making the indexing results more closely match actual underground transportation scenarios. Through the collaboration of the scheduling center, indexing system, sensor network, and capacity decision-maker, real-time load data of key nodes can be obtained and backup paths can be automatically switched, ensuring the feasibility and optimization of the planning scheme.

[0023] 3) This application adopts a two-layer divide-and-conquer architecture. The global management layer only serves as a lightweight coordination center to maintain macro-level topology and key partition information, without processing specific real-time data. The local execution layer is managed by distributed edge nodes, which are responsible for detailed topology and real-time status management within each partition. This layered design reduces the global data transmission required for centralized index maintenance, lowers the computing power and bandwidth pressure on edge nodes, avoids the problem of uncontrolled resource consumption due to large amounts of node data storage exceeding the actual capacity of the edge gateway, and improves the stability and scalability of the system.

[0024] 4) This application addresses the 2.5-dimensional spatial characteristics of underground mining by employing a quadtree for planar partitioning and combining it with hash partitioning to group nodes in the same tunnel or adjacent areas into the same partition, reducing cross-partition queries and enhancing adaptability to complex underground topologies. Event-driven updates only perform local reconstruction on affected subgraphs (satisfying spatial proximity, topological relevance, and functional criticality), avoiding global index invalidation. Furthermore, by integrating real-time attribute data such as mine car load and conveyor belt speed, it solves the problem of missing node label attribute data, improving the accuracy and reliability of the index results. Attached Figure Description

[0025] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0026] Figure 1 A flowchart illustrating a real-time reachability indexing method for data transmission based on 5G communication and dynamic topology awareness, provided in an embodiment of this application; Figure 2 A global management layer structure diagram provided for embodiments of this application; Figure 3 This is a diagram of the edge gateway structure provided in an embodiment of this application; Figure 4 A schematic diagram of the spatial partitioning of a quadtree structure in an underground roadway provided in this application embodiment; Figure 5 This application provides a mine car displacement event-driven subgraph update path graph in its embodiments. Figure 6 This application provides a mine car transportation route diagram for an embodiment of the invention. Figure 7 A flowchart illustrating the dynamic path determination process provided in this application embodiment; Figure 8 This is a structural diagram of a data transmission real-time reachability indexing device based on 5G communication and dynamic topology awareness, provided in an embodiment of this application.

[0027] The accompanying drawings illustrate specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to particular embodiments. Detailed Implementation

[0028] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0029] The collection, storage, use, processing, transmission, provision, and disclosure of financial data or user data involved in the technical solution of this application all comply with the provisions of relevant laws and regulations and do not violate public order and good morals.

[0030] It should be noted that in the embodiments of this application, certain software, components, models and other existing solutions in the industry may be mentioned. These should be regarded as exemplary and are only intended to illustrate the feasibility of implementing the technical solution of this application. However, it does not mean that the applicant has used or necessarily used the solution.

[0031] The technical solution of this application and how the technical solution of this application solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will now be described with reference to the accompanying drawings.

[0032] This application provides a real-time reachability indexing method for data transmission based on 5G communication and dynamic topology sensing. This method is used in dynamic transportation networks composed of underground mine cars, conveyor belts, and transfer nodes to process real-time status data changes reflecting equipment failures, path congestion, etc., and quickly generate emergency navigation plans. 5G communication technology provides a highly reliable, low-latency transmission channel for real-time data interaction in the underground dynamic transportation network, and its application spans the entire process of data acquisition, topology sensing, index updating, and emergency plan generation. In practical applications, such as data acquisition, underground mining trucks, conveyor belts, and transfer nodes are all equipped with 5G industrial modules. These modules can collect real-time data on equipment operation status, such as truck speed, location, and fault codes; conveyor belt motor temperature and speed; and material accumulation at transfer nodes. 5G's massive connectivity supports hundreds or thousands of devices accessing the network simultaneously, with a single cell supporting up to 100,000 connections, ensuring no data loss. Peak speeds exceeding 100Mbps can meet the concurrent transmission needs of high-definition video streams and high-frequency sensor data. At the dynamic topology sensing level, 5G's ultra-low latency becomes crucial. When device status data is transmitted to edge computing nodes via the 5G network, the end-to-end latency is controlled within 20ms, ensuring that the topology sensing module can acquire real-time changes in the connection relationships of network nodes. For example, when a section of conveyor belt stops due to a fault, its status data, after being transmitted via 5G, can be identified by the edge node within 30ms as a connection interruption between the node and upstream and downstream mining trucks and transfer nodes, thereby triggering dynamic reconstruction of the topology map. Simultaneously, 5G's mobility management function supports seamless switching when mining trucks are moving at high speeds, avoiding the loss of topology information caused by switching between different 5G cells, thus ensuring the continuity of topology sensing. For real-time reachability index updates, 5G communication provides high-frequency data interaction capabilities supported by high speed. The index module is deployed on the underground edge cloud platform, exclusively occupying a portion of network resources through 5G slicing technology to establish dedicated data links with each device. When device status changes, such as a sudden malfunction of a mining truck or a path blockage due to a landslide, the 5G network can push the changed data to the edge cloud within 10ms. Based on the dynamic topology awareness results, the index module quickly updates the node reachability weights using a predefined hash algorithm and generates a new index table. Due to the transmission stability of 5G, the probability of data error during index updates is extremely low, eliminating the need for additional redundant verification and significantly improving index update efficiency. During the emergency navigation plan generation phase, 5G's highly reliable transmission capabilities ensure rapid implementation. When the index module determines that a path is unreachable, the edge cloud platform initiates an emergency algorithm based on the real-time reachability index to calculate the optimal detour route. After the plan is generated, navigation commands can be simultaneously pushed to multiple affected mining trucks and transfer node control systems via 5G's multicast function, with a command transmission latency of no more than 50ms, ensuring that mining trucks can complete turning, deceleration, and other operations within a short time. Furthermore, 5G's network slicing technology can establish the highest-priority transmission channel for emergency navigation commands, ensuring priority delivery of commands even during underground network congestion, thus preventing secondary accidents caused by transmission delays.

[0033] Specifically, such as Figure 1 The diagram shows a flowchart of a real-time reachability indexing method for data transmission based on 5G communication and dynamic topology awareness, provided in an embodiment of this application. The method includes the following steps S10-S30.

[0034] S10. Establish a two-layer divide-and-conquer architecture to achieve hierarchical management of network topology.

[0035] In this embodiment, the core of the two-layer divide-and-conquer architecture is spatial layering. Considering the dynamic characteristics of the mining equipment data transmission network, the entire network is decomposed into: (1) Global Management Layer: The central server acts as a lightweight coordination center, responsible for macro-level topology and partition management. It does not process specific real-time data, but only maintains key control information. For example, the mapping from storage node locations to edge nodes (lane coordinates → gateway ID).

[0036] (2) Local Execution Layer: Distributed edge nodes, deployed in underground tunnels, managed by the edge gateway of each partition, responsible for the detailed topology and real-time status within the partition. For example, tree index information is distributed and stored on each edge node.

[0037] This layered design enables dynamic response capabilities that allow for both overall control and local autonomy.

[0038] Specifically, the data stored by the global management layer includes: three-dimensional coordinate boundaries representing the spatial range of partitions, gateway addresses of nodes responsible for edge computing of partitions, adjacency relationships of each partition, and key indicators within each partition. These key indicators include, but are not limited to, the total number of nodes, load level, and health status.

[0039] The partitioning method uses hash partitioning management, partitioning nodes according to their spatial location. Nodes in the same lane or adjacent areas should be assigned to the same partition to reduce cross-partition queries. For example, lane + coordinates, edge nodes only store the hash mapping of the associated subgraph. Figure 2 The diagram shown is a global management layer structure diagram provided in this application embodiment. The central server, as the core hub of the global management layer, coordinates and manages hash partitioning, cross-region routing, status monitoring, and data from each partition. Hash partitioning constructs a mapping relationship between nodes and partitions, clearly defining the three-dimensional coordinate boundaries of the partition space, recording the gateway addresses of the edge computing nodes of the partitions, and anchoring transit stations for cross-region data flow. Cross-region routing, based on the adjacency relationships of each partition, sorts out the data interaction paths between partitions, ensuring the smoothness of cross-partition queries and topology information transmission. Status monitoring collects key indicators such as the total number of nodes, load level, and health status of each partition in real time, providing data support for global topology management and emergency decision-making. Partition 1 data, Partition 2 data, etc., are centralized storage of detailed topology and real-time status of each partition, forming global-local data collaboration with the hash mapping of edge nodes. This allows the global management layer to accurately control the macro-architecture of the underground transportation network without getting bogged down in specific real-time data details, laying a solid foundation for global management of real-time reachability indexing of data transmission based on 5G communication and dynamic topology awareness, adapting to the complex dynamic environment underground, and improving the overall efficiency of indexing and topology management.

[0040] Therefore, the required data structures in the global management layer structure of this embodiment include a global partition table and edge nodes. The global partition table records the edge gateway IP address corresponding to each partition ID, as well as the relationship between adjacent partitions for cross-partition path queries. Each edge node is responsible for several partitions, storing local indexes of all nodes within these partitions, such as quadtree indexes, and also storing the gateway addresses of adjacent partitions for cross-partition queries.

[0041] For the local execution layer, considering that the underground space in a mine is a typical 2.5-dimensional environment, with changes in height but primarily planar movement, a quadtree is chosen to handle the two-dimensional planar partitioning. In the roadway environment, equipment mainly moves in the XY plane, with limited changes in the Z-axis; therefore, a quadtree can more accurately partition the space, and the time complexity of node splitting and merging is O(logn), achieving a balance between storage and query efficiency. Figure 3 and Figure 4The figures shown are an edge gateway structure diagram and a spatial partitioning diagram of a quadtree structure for underground tunnels, respectively, provided in the embodiments of this application.

[0042] As the core management unit of the local execution layer, the edge gateway integrates a tree index, a UWB listener, and a load status table. The tree index organizes the device connection relationships within the partition by constructing an optimal spanning tree and accurately depicts the node interaction paths through forward and reverse topology calculations; the UWB listener captures the displacement of devices such as mining trucks in real time, providing data support for monitoring state change events; and the load status table dynamically records the node load, assisting in capacity constraint model determination.

[0043] The underground roadway spatial partitioning uses a quadtree structure, with the mine boundary of 500m*500m as the initial unit. It is first divided into NW, SW, and other regions based on orientation (e.g., the NW region's coordinate range is 0-250m, 250m-500m), and then further subdivided into NW1-NW4, SW1-SW4, and other sub-regions. This spatial partitioning based on a 2.5D environment aligns with the predominantly planar movement of underground equipment, allowing the local execution layer to precisely manage the topology based on partitions. Combined with the functional modules of the edge gateway, it efficiently handles topology updates, status monitoring, and index maintenance within each partition. While ensuring a balance between storage and query efficiency, it lays a solid foundation for dynamic topology awareness and real-time reachability indexing, adapting to the needs of complex underground spatial scenarios.

[0044] S20, triggering index updates based on an event-driven mechanism.

[0045] It should be noted that event-driven refers to an innovative mechanism in network systems that, instead of periodic polling or fixed-interval updates, immediately triggers a response action when a specific state change occurs. When a sudden change in the state of a node in the transportation network is detected, such as excessive displacement, fault signals, or sudden load changes, the system automatically and accurately initiates index updates within the corresponding range.

[0046] In this embodiment, the method of triggering index updates based on the event-driven mechanism specifically includes: when a state change event such as excessive displacement, fault signal, or sudden load change of a node in the transportation network is detected, a response action is triggered to generate a path; wherein, the response action includes locating the abnormal node, determining the range of the affected subgraph, and performing the corresponding subgraph update according to the level of the node state change.

[0047] In some embodiments, an unexpected displacement event of a mining truck is used as an example of an event scenario. The event triggering conditions include: the edge gateway monitors displacement, equipment, and load in real time, and the event is triggered when the obtained mining truck position data exceeds a threshold. The event parameters involved include: vehicle ID, new coordinates, direction angle, speed, etc.

[0048] For the unexpected displacement event of the mining truck, the event-driven response process includes the following steps S201-S202.

[0049] S201, Location Anomaly: Assuming the displacement threshold S = 2 meters, when UWB detects that the displacement of mine car A is greater than 2 meters within 3 seconds, a displacement exceeding the threshold event is triggered.

[0050] S202. Determine the scope of influence: Determine the subgraph of affected nodes within a specified radius, and then update the subgraph accordingly. For example... Figure 4 If the specified radius is 30 meters, and the unloading point E is outside this range, then the information for that point will not be updated, and local reconstruction will be completed. When selecting nodes, the following conditions should be considered: ① Spatial proximity: Distance from the displacement point ≤ set threshold; ②Topological dependence: There is a direct or indirect path connection with the displacement mine car A; ③ Functional criticality: Path control node B, conveyor belt C, material transfer node D.

[0051] Similarly, in the case of equipment failure, if the heartbeat signal of the equipment is detected to have disappeared through real-time monitoring, path planning within the subgraph is performed to skip the failed path nodes. If it is a sudden change in load, the load value needs to be calculated and dynamically adjusted. That is, monitoring and judgment conditions are used, and when the conditions change, a response event is triggered.

[0052] In some embodiments, different strategies are selected for subgraph updates to improve indexing efficiency: (1) Determine the displacement level based on the displacement setting. For example: displacement exceeding the specified value by less than 1 meter is level 1, 1 meter to 3 meters is level 2, and more than 3 meters is level 3, etc. The specific values ​​should be set according to the actual example of the tunnel.

[0053] (2) Different subgraph update schemes are selected for different displacement levels, such as Figure 5 As shown.

[0054] Impact of the update: Path calculation skips fault points: If point A fails, the original path X→A→B→Y will be updated to X→B→Y; Reduced topology depth: Reduced response latency.

[0055] S30. Reachability verification is achieved through capacity injection determination.

[0056] It should be noted that capacity injection determination incorporates real-time load status into topology analysis. During reachability verification, it not only checks whether a path exists but also dynamically evaluates the path's carrying capacity. A path is only considered usable when the real-time load of a node meets the capacity constraints.

[0057] In this embodiment, the method of achieving reachability verification through capacity injection judgment specifically includes: establishing a capacity constraint model that includes node ID, maximum capacity, real-time load and load weight; during the path reachability verification process, using the capacity constraint model to check whether the path exists; and through the collaboration of the scheduling center, indexing system, sensor network and capacity decision-maker, dynamically evaluating the path carrying capacity; and determining that the path is available only when the real-time load of the node meets the capacity constraint.

[0058] In some embodiments, with Figure 6 For example, the dynamic decision-making process is executed through the capacity constraint model as follows: Figure 7 As shown in the diagram. The scheduling center initiates path query requests; the indexing system verifies topology reachability; the sensor network provides real-time load data; and the capacity decision-maker performs the final capacity determination when load data is transmitted back to the indexing system.

[0059] The two routes for mine car A to unloading point 1 are: Path 1: Mine car A → Conveyor belt B → Transfer point C → Unloading point 1; Path 2: Mine car A → Node D → Node E → Unloading point 1.

[0060] The dynamic determination is performed according to the following steps: (1) Prove the existence of path 1 through topological verification; (2) Obtain the load weight w_load (real-time load / maximum capacity) of key nodes B and C; (3) Perform path evaluation: When it is determined that the remaining capacity of the conveyor belt is lower than the threshold, path access is rejected and backup path 2 is automatically switched.

[0061] This application also provides a data transmission real-time reachability indexing device based on 5G communication and dynamic topology awareness, such as... Figure 8 As shown, the data transmission real-time reachability indexing device based on 5G communication and dynamic topology awareness includes: Architecture establishment module 801 is configured to establish a two-layer divide-and-conquer architecture to achieve hierarchical management of network topology. The two-layer divide-and-conquer architecture includes a global management layer and a local execution layer. The global management layer uses a central server as a lightweight coordination center. The central server is used for macro-level topology and partition management, storing the mapping from node locations to edge nodes, the three-dimensional coordinate boundaries of partition spatial ranges, the gateway addresses of partition edge computing nodes, the adjacency relationships of each partition, the total number of nodes within each partition, load levels, and key health indicators, but does not process specific real-time data. The local execution layer includes at least two distributed edge nodes deployed in underground tunnels, managed by the edge gateways of each partition, and responsible for storing detailed topology, real-time status, and local index information within each partition. The index update module 802 is configured to trigger index updates based on an event-driven mechanism, including: when a state change event such as excessive displacement, fault signal, or sudden load change of a node in the transportation network is detected, a response action is triggered to generate a path; wherein, the response action includes locating the abnormal node, determining the range of the affected subgraph, and performing the corresponding subgraph update according to the level of the node state change. The reachability verification module 803 is configured to perform reachability verification through capacity injection determination, including: establishing a capacity constraint model containing node ID, maximum capacity, real-time load and load weight; during the path reachability verification process, using the capacity constraint model to check whether the path exists; and through the collaboration of the scheduling center, indexing system, sensor network and capacity decision-maker, dynamically evaluating the path carrying capacity; and determining that the path is available only when the real-time load of the node meets the capacity constraint.

[0062] In some embodiments, the global management layer adopts a hash partitioning management method, partitioning nodes according to their spatial location, dividing nodes in the same alley or adjacent areas into the same partition, and the global management layer includes a global partition table, which records the edge gateway IP address corresponding to each partition ID and the relationship between adjacent partitions, for cross-partition path lookup. The local index information of the local execution layer is a quadtree index. The quadtree is based on the 2.5-dimensional environmental characteristics of the underground roadway and divides the XY plane to achieve spatial partition management.

[0063] In some embodiments, the index update module is further configured to: When UWB detects that the displacement of the mining truck exceeds a preset threshold within a set time, it triggers a sudden event indicating that the displacement has exceeded the limit. When the device's heartbeat signal disappears, a sudden status event of device failure is triggered; When the real-time load change of a node exceeds the set range, a sudden load change event is triggered.

[0064] In some embodiments, the index update module is further configured to: Determine the subgraph containing the affected nodes within a specified radius, and then update the subgraph. When determining the affected nodes, the following conditions must be met: Spatial proximity: The distance between a node in the subgraph and a node with a state change ≤ a set threshold; Topological dependence: There is a direct or indirect path connection between a node in the subgraph and a node whose state has changed. Functional criticality: The sub-graph includes critical functional nodes, such as path control nodes, conveyor belts and / or material transfer nodes.

[0065] In some embodiments, the index update module is further configured to: Determine the displacement level based on the displacement setting; Different subgraph update schemes are selected based on different displacement levels; wherein, the subgraph update scheme includes local update, cooperative network update and global verification, and spatial index update, topology relationship reconstruction and path replanning are completed during the update process.

[0066] In some embodiments, the load weight in the capacity constraint model is calculated as the ratio of real-time load to maximum capacity.

[0067] In some embodiments, the reachability verification module is further configured to: The existence of candidate paths is confirmed through topology verification; If the candidate path is determined to exist, the load weights of the key nodes in the candidate path are obtained; If the remaining capacity of a critical node is below a threshold, access to the candidate path is rejected and the system automatically switches to a backup path; wherein, the critical node is a node determined from the candidate paths.

[0068] This application provides an electronic device. The electronic device may include a processor and a memory, wherein the processor and the memory can communicate; exemplarily, the processor and the memory communicate via a communication bus.

[0069] The processor executes computer execution instructions stored in memory, causing the processor to perform the scheme in the above embodiments. The processor can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components.

[0070] The communication bus can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. The system bus can be divided into address bus, data bus, control bus, etc. Transceivers are used to enable communication between database access devices and other computers (e.g., clients, read-write libraries, and read-only libraries). Memory may include random access memory (RAM) and may also include non-volatile memory.

[0071] The electronic device provided in this application embodiment can be the terminal device described in the above embodiments.

[0072] This application also provides a computer-readable storage medium storing computer instructions. When the computer instructions are executed on a computer, the computer performs the technical solution of the data transmission real-time reachability indexing method based on 5G communication and dynamic topology awareness described in the above embodiment.

[0073] This application also provides a computer program product, which includes a computer program stored in a computer-readable storage medium. At least one processor can read the computer program from the computer-readable storage medium. When the at least one processor executes the computer program, it can implement the technical solution of the real-time reachability indexing method for data transmission based on 5G communication and dynamic topology awareness in the above embodiments.

[0074] In the several embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative; for instance, the division of modules is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple modules may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be indirect coupling or communication connection through some interfaces, devices, or modules, and may be electrical, mechanical, or other forms.

[0075] The modules described as separate components may or may not be physically separate. The components shown as modules may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to implement the solution of this embodiment according to actual needs.

[0076] Furthermore, the functional modules in the various embodiments of this application can be integrated into one processing unit, or each module can exist physically separately, or two or more modules can be integrated into one unit. The unit composed of the above modules can be implemented in hardware or in the form of hardware plus software functional units.

[0077] The integrated modules described above, implemented as software functional modules, can be stored in a computer-readable storage medium. These software functional modules, stored in a storage medium, include several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute some steps of the methods of the various embodiments of this application.

[0078] It should be understood that the aforementioned processor can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), etc. A general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in this invention can be directly manifested as execution by a hardware processor, or execution by a combination of hardware and software modules within the processor.

[0079] The memory may include high-speed RAM, and may also include non-volatile storage (NVM), such as at least one disk storage device, and may also be a USB flash drive, external hard drive, read-only memory, disk or optical disc, etc.

[0080] Buses can be Industry Standard Architecture (ISA) buses, Peripheral Component Interconnect (PCI) buses, or Extended Industry Standard Architecture (EISA) buses, etc. Buses can be categorized into address buses, data buses, control buses, etc.

[0081] The aforementioned storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk. The storage medium can be any available medium that can be accessed by a general-purpose or special-purpose computer.

[0082] An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. Alternatively, the storage medium can be an integral part of the processor. The processor and storage medium can reside in an Application-Specific Integrated Circuit (ASIC). Alternatively, the processor and storage medium can exist as discrete components in an electronic control unit or main control device.

[0083] Those skilled in the art will understand that all or part of the steps of the above-described method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When executed, the program performs the steps of the above-described method embodiments; and the aforementioned storage medium includes various media capable of storing program code, such as ROM, RAM, magnetic disks, or optical disks.

[0084] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features therein. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of this application.

Claims

1. A method for real-time reachability indexing of data transmission based on 5G communication and dynamic topology awareness, characterized in that, The method includes: A two-layer divide-and-conquer architecture is established to achieve hierarchical management of network topology. This architecture includes a global management layer and a local execution layer. The global management layer uses a central server as a lightweight coordination center. This central server manages the macro-level topology and partitions, storing the mapping from node locations to edge nodes, the three-dimensional coordinate boundaries of partition spaces, the gateway addresses of partition edge computing nodes, the adjacency relationships of each partition, the total number of nodes within each partition, load levels, and key health indicators, but does not process specific real-time data. The local execution layer includes at least two distributed edge nodes deployed in underground tunnels, managed by the edge gateways of each partition, and responsible for storing detailed topology, real-time status, and local index information within each partition. The index update is triggered based on an event-driven mechanism, including: when a sudden change in the state of a node in the transportation network, such as excessive displacement, fault signal, or sudden load change, a response action is triggered to generate a path; wherein, the response action includes locating the abnormal node, determining the range of the affected subgraph, and performing the corresponding subgraph update according to the level of the node state change. Reachability verification is achieved through capacity injection determination, including: establishing a capacity constraint model that includes node ID, maximum capacity, real-time load and load weight; during the path reachability verification process, the capacity constraint model is used to check whether the path exists; and through the collaboration of the scheduling center, indexing system, sensor network and capacity decision-maker, the path carrying capacity is dynamically evaluated; and the path is determined to be available only when the real-time load of the node meets the capacity constraint.

2. The real-time reachability indexing method for data transmission based on 5G communication and dynamic topology awareness according to claim 1, characterized in that, The global management layer adopts a hash partitioning management method, which partitions nodes according to their spatial location. Nodes in the same alley or adjacent areas are assigned to the same partition. The global management layer contains a global partition table, which records the edge gateway IP address corresponding to each partition ID and the relationship between adjacent partitions, for cross-partition path lookup. The local index information of the local execution layer is a quadtree index. The quadtree is based on the 2.5-dimensional environmental characteristics of the underground roadway and divides the XY plane to achieve spatial partition management.

3. The real-time reachability indexing method for data transmission based on 5G communication and dynamic topology awareness according to claim 1, characterized in that, In the event-driven index update process, the triggering methods for state mutation events include: When UWB detects that the displacement of the mining truck exceeds a preset threshold within a set time, it triggers a sudden event indicating that the displacement has exceeded the limit. When the device's heartbeat signal disappears, a sudden status event of device failure is triggered; When the real-time load change of a node exceeds the set range, a sudden load change event is triggered.

4. The real-time reachability indexing method for data transmission based on 5G communication and dynamic topology awareness according to claim 1, characterized in that, The scope of determining the affected subgraph includes: Determine the subgraph containing the affected nodes within a specified radius, and then update the subgraph. When determining the affected nodes, the following conditions must be met: Spatial proximity: The distance between a node in the subgraph and a node with a state change ≤ a set threshold; Topological dependence: There is a direct or indirect path connection between a node in the subgraph and a node whose state has changed. Functional criticality: The sub-graph includes critical functional nodes, such as path control nodes, conveyor belts and / or material transfer nodes.

5. The real-time reachability indexing method for data transmission based on 5G communication and dynamic topology awareness according to claim 1, characterized in that, The step of performing corresponding subgraph updates based on the level of node state mutation includes: Determine the displacement level based on the displacement setting; Different subgraph update schemes are selected based on different displacement levels; wherein, the subgraph update scheme includes local update, cooperative network update and global verification, and spatial index update, topology relationship reconstruction and path replanning are completed during the update process.

6. The real-time reachability indexing method for data transmission based on 5G communication and dynamic topology awareness according to claim 1, characterized in that, In the capacity constraint model, the load weight is calculated as the ratio of real-time load to maximum capacity.

7. The real-time reachability indexing method for data transmission based on 5G communication and dynamic topology awareness according to claim 1, characterized in that, During path reachability verification, the capacity constraint model is used to check if a path exists. Through the collaboration of the scheduling center, indexing system, sensor network, and capacity decision-maker, the path's carrying capacity is dynamically evaluated. A path is determined to be available only when the real-time load of a node meets the capacity constraint, including: The existence of candidate paths is confirmed through topology verification; If the candidate path is determined to exist, the load weights of the key nodes in the candidate path are obtained; If the remaining capacity of a critical node is below a threshold, access to the candidate path is rejected and the system automatically switches to a backup path; wherein, the critical node is a node determined from the candidate paths.

8. A real-time reachability indexing device for data transmission based on 5G communication and dynamic topology awareness, characterized in that, The device includes: The architecture building module is configured to establish a two-layer divide-and-conquer architecture to achieve hierarchical management of network topology. This two-layer architecture includes a global management layer and a local execution layer. The global management layer uses a central server as a lightweight coordination center. This central server is used for macro-level topology and partition management, storing the mapping from node locations to edge nodes, the three-dimensional coordinate boundaries of partition spaces, the gateway addresses of partition edge computing nodes, the adjacency relationships of each partition, the total number of nodes within each partition, load levels, and key health indicators, but does not process specific real-time data. The local execution layer includes at least two distributed edge nodes deployed in underground tunnels, managed by the edge gateways of each partition, and responsible for storing detailed topology, real-time status, and local index information within each partition. The index update module is configured to trigger index updates based on an event-driven mechanism, including: when a sudden change in the state of a node in the transportation network, such as excessive displacement, fault signal, or sudden load change, is detected, a response action is triggered to generate a path; wherein, the response action includes locating the abnormal node, determining the range of the affected subgraph, and performing the corresponding subgraph update according to the level of the node state change. The reachability verification module is configured to perform reachability verification through capacity injection, including: establishing a capacity constraint model containing node ID, maximum capacity, real-time load and load weight; during the path reachability verification process, using the capacity constraint model to check if the path exists; and through the collaboration of the scheduling center, indexing system, sensor network and capacity decision-maker, dynamically evaluating the path carrying capacity; and determining that the path is available only when the real-time load of the node meets the capacity constraint.

9. An electronic device, characterized in that, include: A processor, and a memory communicatively connected to the processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory to implement the real-time reachability indexing method for data transmission based on 5G communication and dynamic topology awareness as described in any one of claims 1-7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the real-time reachability indexing method for data transmission based on 5G communication and dynamic topology awareness as described in any one of claims 1-7.

Images