A method for transmitting WiFi wireless self-organizing networks with no bandwidth attenuation using dual network cards
By configuring STA and AP mode WiFi network cards in the tunnel construction area, generating a node topology table, and determining candidate next-hop nodes and forwarding interfaces based on link status, the data forwarding congestion problem caused by insufficient link role binding in traditional methods is solved, and stable data transmission of multiple types of services is achieved.
Patent Information
- Application Number
- CN202611361515.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-09-03
- Publication Date
- 2026-11-17
AI Technical Summary
Traditional dual-NIC WiFi wireless self-organizing network transmission methods without bandwidth attenuation lack link role binding in narrow tunnel environments during node cascading, leading to data forwarding congestion and link fluctuation delays, which affect the continuous transmission of data load.
Within the tunnel construction area, configure STA mode WiFi network cards to connect with the upper-level base station node, and AP mode WiFi network cards to register relationships with the lower-level base station node or local construction equipment. Generate a node topology table, determine candidate next-hop nodes and forwarding interfaces based on service type, destination address, and link status, and update the forwarding path under link fluctuation conditions.
It enables stable forwarding of various types of service data under link fluctuation conditions, reduces the number of service data entering non-corresponding paths, and improves the reliability and efficiency of data transmission.
Smart Images

Figure CN123124140A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of WiFi transmission technology, and in particular to a dual-NIC WiFi wireless self-organizing network transmission method without bandwidth attenuation. Background Technology
[0002] The field of WiFi transmission technology typically revolves around wireless terminals, access points, network cards, radio frequency channels, and network protocols to carry out signal transmission and reception, link establishment, data encapsulation, routing and forwarding, address allocation, and connection status maintenance. Data is carried by MAC frames, IP packets, or application layer data packets and transmitted between nodes via antennas, wireless network cards, drivers, and protocol stacks.
[0003] The traditional dual-NIC WiFi wireless self-organizing network transmission method without bandwidth attenuation refers to configuring two WiFi NICs on the self-organizing network node, establishing an adjacent node link and a local access link respectively, and selecting the interface, queuing for sending, receiving confirmation and forwarding hop by hop for the data packet to be sent based on SSID, channel, MAC address, IP address, routing table, signal strength, link status and packet destination address, and the node program records the connection status and forwarding table entries.
[0004] Traditional dual-NIC WiFi wireless self-organizing network transmission methods mainly rely on interface status and routing tables for hop-by-hop forwarding during node cascading. There is a lack of role binding between adjacent node links and local access links in narrow tunnel environments. Sensor data, video data, and control commands are mixed and enter the transmission queue, which can easily lead to forwarding congestion. Node connection status, link latency, and packet loss status are only used for routine forwarding records. When the link fluctuates, routing switching is delayed, and continuous data load transmission is affected. Summary of the Invention
[0005] The purpose of this invention is to provide a dual-NIC WiFi wireless ad hoc network transmission method without bandwidth attenuation. Focusing on the cascading transmission process of wireless ad hoc network nodes within a tunnel construction area, this method establishes a role correspondence between STA-mode WiFi network cards and upper-level base station nodes, and between AP-mode WiFi network cards and lower-level base station nodes or local construction equipment. Furthermore, it determines candidate next-hop nodes, transmission queues, and forwarding interfaces by combining service type, destination address, link latency, packet loss status, and transmission queue status. This ensures that various types of service data in the tunnel construction scenario can still be forwarded along the corresponding paths even under link fluctuation conditions.
[0006] To achieve the above objectives, the present invention adopts the following technical solution, providing a dual-NIC WiFi wireless self-organizing network transmission method without bandwidth attenuation, comprising the following steps: deploying multiple dual-NIC wireless bandwidth IoT base station nodes in a tunnel construction area, configuring each base station node with a STA mode WiFi network card and an AP mode WiFi network card; enabling the STA mode WiFi network card to connect to the upper-level base station node and obtain the upper-level base station node identifier and connection status, enabling the AP mode WiFi network card to register the lower-level base station node or local construction equipment and obtain the lower-level access object identifier and interface role; generating a node topology table based on the upper-level base station node identifier, the connection status, the lower-level access object identifier, and the interface role; receiving incoming... From the service data of the local construction equipment, extract the service type, destination address, and data payload. Verify the destination address according to the service type, and determine candidate next-hop nodes based on the node topology table and the destination address. Collect link latency, packet loss status, and sending queue status. When the connection status, link latency, packet loss status, or sending queue status meets the abnormal triggering conditions, update the candidate next-hop nodes and forwarding interfaces according to the node topology table. Determine the sending queue and the forwarding interface based on the service type, candidate next-hop nodes, link latency, packet loss status, and sending queue status, and send the data payload to the backend server or target construction equipment corresponding to the destination address.
[0007] In the progressive scheme, the step of deploying multiple dual-NIC wireless bandwidth IoT base station nodes in the tunnel construction area includes: acquiring axial segment information, construction progress position information, and connection status of already deployed base station nodes in the tunnel construction area; matching the axial segment information with the construction progress position information to obtain candidate deployment segments; when no already deployed base station node exists in the candidate deployment segment, or when the connection status of the already deployed base station node meets the abnormal triggering condition, deploying a new base station node in the candidate deployment segment, and configuring the new base station node with both STA mode WiFi NIC and AP mode WiFi NIC, thus obtaining the base station node deployment result. This progressive scheme ensures that the deployment of the base station nodes corresponds to the changes in the tunnel construction area's segments and the connection status.
[0008] In a further progressive scheme, the configuration steps for the newly added base station node include: having the STA-mode WiFi network card scan for connectable upper-level base station nodes within the candidate deployment segment, and selecting a target upper-level base station node from those meeting the connection conditions according to the connection status; having the AP-mode WiFi network card generate an access identifier for lower-level base station nodes or local construction equipment to access; and writing the target upper-level base station node, the access identifier, and the tunnel segment of the newly added base station node into the node topology table to obtain the network access configuration result for the newly added base station node. When writing to the node topology table, the target upper-level base station node is converted to the upper-level base station node identifier, the access identifier is converted to the lower-level access object identifier, and the tunnel segment of the newly added base station node is associated with the interface role; when corresponding records exist for the upper-level base station node identifier, the lower-level access object identifier, and the interface role, a node topology table record is generated to obtain the node topology table update result.
[0009] In the business data processing scheme, the steps of receiving business data from the local construction equipment and extracting the business type, destination address, and data payload include: reading the source object identifier and data packet header field of the business data; matching the source object identifier with the lower-level access object identifier in the node topology table to obtain a source verification result; when the source verification result is a successful match, extracting the business type and destination address from the data packet header field, and separating the data payload from the business data to obtain a business data parsing result. When verifying the destination address, reading the business type and destination address from the business data parsing result; when the business type is a multi-source sensor data type, a monitoring video stream type, or a risk identification result type, matching the destination address with the backend server address to obtain an uplink business verification result; when the business type is a camera control command type, matching the destination address with the target construction equipment address to obtain a downlink business verification result.
[0010] In the candidate next-hop node determination scheme, the step of determining the candidate next-hop node based on the uplink service verification result or the downlink service verification result includes: when the uplink service verification result is a successful match, determining the candidate next-hop node based on the upper-level base station node identifier in the node topology table to obtain an uplink candidate forwarding result; when the downlink service verification result is a successful match, determining the candidate next-hop node based on the lower-level access object identifier in the node topology table to obtain a downlink candidate forwarding result. Thus, a corresponding forwarding judgment relationship is formed between the service type, the destination address, and the node topology table.
[0011] In the link anomaly detection scheme, the step of determining whether the connection status, link latency, packet loss status, or transmission queue status meets the anomaly triggering condition includes: comparing the connection status with the disconnection status, comparing the link latency with a latency threshold, comparing the packet loss status with a packet loss threshold, and comparing the transmission queue status with a queue congestion threshold; when any comparison result reaches the corresponding threshold or status condition, a link anomaly detection result is generated; when none of the comparison results reach the corresponding threshold or status condition, a link normal detection result is generated. The step of updating the candidate next-hop node and the forwarding interface based on the link anomaly detection result includes: reading the available upper-level base station nodes and available lower-level access objects adjacent to the current base station node according to the node topology table, matching the available upper-level base station nodes or the available lower-level access objects with the destination address to obtain an alternative next-hop node, and determining the forwarding interface according to the interface role corresponding to the alternative next-hop node to obtain the abnormal link forwarding update result.
[0012] In the collaborative scheme of sending queue and forwarding interface, the steps of determining the sending queue and the forwarding interface based on the service type, the candidate next-hop node, the link latency, the packet loss status, and the sending queue status include: when the connection status, the link latency, the packet loss status, and the sending queue status do not meet the abnormal triggering conditions, a service priority is generated according to the service type, the candidate next-hop node is matched with the node topology table to obtain the interface role, the sending queues that have not reached the queue congestion threshold are filtered based on the link latency, the packet loss status, and the sending queue status, the forwarding interface corresponding to the interface role is bound to the sending queue, and the data payload is sent to the backend server or target construction equipment corresponding to the destination address according to the binding result to obtain the service data sending result.
[0013] Compared with the prior art, the advantages and positive effects of the present invention are as follows: In this invention, the connection relationship between STA mode WiFi network cards and upper-level base station nodes is bound, and the registration relationship between AP mode WiFi network cards and lower-level base station nodes or local construction equipment is bound. A node topology table is generated using the upper-level base station node identifier, connection status, lower-level access object identifier, and interface role, ensuring that the cascading relationship of base station nodes corresponds to the interface role. Service data is split by service type, destination address, and data load. The destination address is first verified, and then the candidate next-hop node is determined based on the node topology table, reducing the chance of service data mistakenly entering non-corresponding forwarding paths. Link latency, packet loss status, and sending queue status participate in the determination of the sending queue and forwarding interface. When abnormal triggering conditions are met, the candidate next-hop node and forwarding interface are updated, ensuring that data loads under link fluctuations have alternative forwarding paths. Attached Figure Description
[0014] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0015] Figure 1 This is the main flowchart of the dual-NIC WiFi wireless self-organizing network transmission of the present invention; Figure 2 This is a schematic diagram of the base station node deployment and dual network card configuration of the present invention; Figure 3 Generate a data relationship graph for the node topology table of this invention; Figure 4 This is a schematic diagram illustrating the business data parsing and candidate next-hop node determination of the present invention; Figure 5 This is a schematic diagram of the link anomaly detection and forwarding interface update of the present invention. Detailed Implementation
[0016] The technical solution described in this invention will be described below with reference to the accompanying drawings. In subsequent embodiments, the tunnel construction area refers to the construction space where dual-NIC wireless bandwidth IoT base station nodes are deployed and local construction equipment can access them; the dual-NIC wireless bandwidth IoT base station node refers to a node configured with both STA-mode and AP-mode WiFi network cards and participating in wireless self-organizing network cascading transmission; local construction equipment refers to sensing and acquisition devices, monitoring devices, control objects, or other construction site data sources that access the corresponding base station node via AP-mode WiFi network cards. The protection scope text does not assign numerical labels to physical components; therefore, subsequent embodiments will not supplement physical component labels. Steps S1 to S5 in the embodiments are consistent with the step numbers in the technical solution described in the application documents; the step numbers are only used to identify the process sequence.
[0017] Please see Figures 1 to 5This embodiment provides a dual-NIC WiFi wireless self-organizing network transmission method without bandwidth attenuation. This method is applied to a WiFi wireless self-organizing network composed of multiple dual-NIC wireless bandwidth IoT base station nodes within a tunnel construction area. During transmission, each base station node uses a STA-mode WiFi NIC to establish a connection with its superior base station node and an AP-mode WiFi NIC to register with its subordinate base station node or local construction equipment. This integrates the superior connection relationship, subordinate access relationship, and service data forwarding relationship into a unified node topology table. Before transmission, service data undergoes extraction of service type, destination address, and data load. After service type verification, the destination address enters the candidate next-hop node determination process. Link latency, packet loss status, and transmission queue status participate in anomaly trigger judgment and transmission queue selection, ensuring that the data load is forwarded according to the backend server or target construction equipment corresponding to the destination address.
[0018] S1: Deploy multiple dual-NIC wireless bandwidth IoT base station nodes in the tunnel construction area, and configure each base station node with a STA mode WiFi NIC and an AP mode WiFi NIC.
[0019] When executing S1, the axial segment information, construction progress position information, and connection status of the deployed base station nodes in the tunnel construction area are first obtained. The axial segment information characterizes the segment positions of the tunnel construction area along the construction direction; the construction progress position information characterizes the current construction progress position; and the connection status of the deployed base station nodes characterizes whether the base station node maintains an available connection with its superior base station node. After the axial segment information and construction progress position information are processed, candidate deployment segments are obtained. These candidate deployment segments are used to determine whether new base station nodes need to be deployed and are not included as separate final outputs.
[0020] After obtaining the candidate deployment segment, it is determined whether there are already deployed base station nodes within the candidate deployment segment, and the connection status of the already deployed base station nodes is read. If there are no already deployed base station nodes within the candidate deployment segment, a new base station node is deployed within the candidate deployment segment. If there are already deployed base station nodes within the candidate deployment segment, but the connection status of the already deployed base station nodes meets the abnormal triggering conditions, a new base station node is also deployed within the candidate deployment segment. After the new base station node is deployed, a STA mode WiFi network card and an AP mode WiFi network card are configured for the new base station node, obtaining the base station node deployment result. The base station node deployment result serves as the basis for connecting to the upper-level base station node, registering lower-level access objects, and generating the node topology table in S2.
[0021] In S1, the STA mode WiFi network card is responsible for connecting to the upstream base station node, while the AP mode WiFi network card is responsible for registering the downstream base station node or local construction equipment. The roles of the two network cards are distinguished during the base station node configuration phase, and this role relationship is referenced subsequently when generating the node topology table, determining candidate next-hop nodes, and selecting forwarding interfaces. Thus, the dual-NIC wireless bandwidth IoT base station node already has a basic division of labor between the upstream connection side and the downstream access side before entering the wireless ad hoc network.
[0022] S2: Enables the STA mode WiFi network card to connect to the upper-level base station node and obtain the upper-level base station node identifier and connection status; enables the AP mode WiFi network card to register the lower-level base station node or local construction equipment and obtain the lower-level access object identifier and interface role; generates a node topology table based on the upper-level base station node identifier, connection status, lower-level access object identifier and interface role.
[0023] During S2 execution, the STA-mode WiFi network card first scans for connectable upstream base station nodes within the candidate deployment segment. This scanning process creates a set of connectable upstream base station nodes, each with a corresponding connection status. The connection status indicates whether the connection between the STA-mode WiFi network card and the upstream base station node meets the connection conditions. Based on the connection status, a target upstream base station node is selected from those meeting the connection conditions, and the STA-mode WiFi network card connects to the target upstream base station node. The target upstream base station node is converted into an upstream base station node identifier, and the connection process yields the connection status. The upstream base station node identifier and connection status are used in the node topology table to determine the uplink connection relationship of the current base station node.
[0024] After configuration, the AP-mode WiFi network card generates an access identifier for lower-level base station nodes or local construction equipment to access. Lower-level base station nodes or local construction equipment access the corresponding base station node through the access identifier. The AP-mode WiFi network card registers the access object, obtaining a lower-level access object identifier and an interface role. The lower-level access object identifier distinguishes objects entering the lower-level side of the current base station node, and the interface role indicates that the access relationship is handled by the AP-mode WiFi network card. After the access identifier is converted into a lower-level access object identifier, it is entered into the node topology table generation process along with the interface role.
[0025] The node topology table generation process includes associating the upper-level base station node identifier and the lower-level access object identifier with their corresponding interface roles. When corresponding records exist for the upper-level base station node identifier, the lower-level access object identifier, and the interface role, a node topology table record is generated, resulting in an updated node topology table. The node topology table record includes the connection relationship between the current base station node and the upper-level base station node, the access relationship between the current base station node and the lower-level base station node or local construction equipment, and the interface role used for subsequent matching of candidate next-hop nodes. If the connection status does not meet the connection conditions, the upper-level base station node is not written into the target upper-level base station node record to prevent subsequent candidate next-hop nodes from being generated based on unavailable connections.
[0026] Through S2, a topology relationship is formed between the STA mode WiFi network card, the AP mode WiFi network card, the upper-level base station node identifier, the connection status, the lower-level access object identifier, and the interface role, which can be invoked in subsequent steps. In S3, when receiving service data, the source object identifier is matched with the lower-level access object identifier in the node topology table. In S4, when a link is abnormal, adjacent available upper-level base station nodes and available lower-level access objects are read according to the node topology table. In S5, when selecting a forwarding interface, candidate next-hop nodes are matched with the node topology table to obtain the interface role.
[0027] S3: Receive service data from local construction equipment, extract service type, destination address and data payload, verify the destination address according to the service type, and determine the candidate next-hop node according to the node topology table and the destination address.
[0028] When executing S3, the current base station node receives service data from local construction equipment via its AP-mode WiFi network card. The service data includes at least a source object identifier, a data packet header field, and a data payload. The source object identifier indicates which local construction equipment sent the service data; the data packet header field carries the service type and destination address; and the data payload is the actual data content that needs to be forwarded to the backend server or target construction equipment. After receiving the service data, the source object identifier and data packet header field are read first. The source object identifier is then matched against the lower-level access object identifier in the node topology table to obtain the source verification result.
[0029] When the source verification result is a successful match, it indicates that the service data originates from a downstream access object registered by the AP-mode WiFi network card. Subsequently, the service type and destination address are extracted from the data packet header fields, and the data payload is separated from the service data to obtain the service data parsing result. The service type, destination address, and data payload in the parsing result are used in different subsequent processing stages: the service type is used for destination address verification and service priority generation; the destination address is used for candidate next-hop node determination and final sending object confirmation; and the data payload is used to send the data to the corresponding backend server or target construction equipment via the forwarding interface.
[0030] The destination address verification process includes: reading the service type and destination address from the service data parsing results. When the service type is a multi-source sensor data type, a monitoring video stream type, or a risk identification result type, the destination address is matched with the backend server address to obtain the uplink service verification result; when the service type is a camera control command type, the destination address is matched with the target construction equipment address to obtain the downlink service verification result. The different service types correspond to different destination address directions. Multi-source sensor data types, monitoring video stream types, and risk identification result types correspond to uplink transmissions from the local construction equipment or on-site acquisition side to the backend server, while camera control command types correspond to downlink transmissions from the management side to the target construction equipment.
[0031] The process of determining candidate next-hop nodes based on uplink or downlink service verification results includes: when the uplink service verification result is a successful match, the candidate next-hop node is determined based on the identifier of the upper-level base station node in the node topology table, resulting in an uplink candidate forwarding result; when the downlink service verification result is a successful match, the candidate next-hop node is determined based on the identifier of the lower-level access object in the node topology table, resulting in a downlink candidate forwarding result. The candidate next-hop node is not the final fixed output; it needs to be updated in S4 based on link anomaly detection, and in S5 based on link latency, packet loss status, and transmission queue status to determine the corresponding transmission queue and forwarding interface.
[0032] S4: Collect link latency, packet loss status, and sending queue status. When the connection status, link latency, packet loss status, or sending queue status meets the abnormal triggering conditions, update the candidate next-hop node and forwarding interface according to the node topology table.
[0033] During S4 execution, the current base station node collects link latency, packet loss status, and transmission queue status. Link latency characterizes the delay state when the current base station node transmits service data through candidate next-hop nodes; packet loss status characterizes the packet loss status in the current transmission link; and transmission queue status characterizes the queue occupancy status for the current base station node to transmit service data. These three types of status, along with the connection status obtained in S2, enter the anomaly trigger judgment process.
[0034] The anomaly triggering process includes comparing the connection status with the disconnection status, comparing the link latency with a latency threshold, comparing the packet loss status with a packet loss threshold, and comparing the sending queue status with a queue congestion threshold. When any comparison result reaches the corresponding threshold or status condition, a link anomaly determination result is generated; when none of the comparison results reach the corresponding threshold or status condition, a link normality determination result is generated. The latency threshold, packet loss threshold, and queue congestion threshold are used to determine whether the corresponding status falls within the anomaly triggering range; their specific values can be determined by the network operation strategy.
[0035] When a link anomaly determination result is generated, the candidate next-hop node and forwarding interface are updated based on the node topology table. The update process includes: reading the available upstream base station nodes and available downstream access objects adjacent to the current base station node from the node topology table; matching the available upstream base station nodes or available downstream access objects with the destination address to obtain the alternative next-hop node; determining the forwarding interface based on the interface role corresponding to the alternative next-hop node to obtain the abnormal link forwarding update result. If the service data belongs to the uplink transmission direction, the alternative next-hop node is preferentially matched from the available upstream base station nodes in the node topology table; if the service data belongs to the downlink transmission direction, the alternative next-hop node is matched from the available downstream access objects in the node topology table. This matching process is still constrained by the destination address to avoid changing the target sending object of the service data during link anomaly handling.
[0036] When a link is deemed normal, step S4 does not change the candidate next-hop node already determined in step S3. The candidate next-hop node is then used in step S5 to determine the sending queue and forwarding interface. Therefore, link anomaly and link normal results correspond to two types of subsequent paths: for anomaly paths, the candidate next-hop node and forwarding interface are updated through the node topology table; for normal paths, the candidate next-hop node is retained and entered into the queue for filtering.
[0037] S5: Determine the sending queue and forwarding interface based on the service type, candidate next-hop node, link latency, packet loss status, and sending queue status, and send the data payload to the backend server or target construction equipment corresponding to the destination address.
[0038] When executing S5, the service type, candidate next-hop nodes, link latency, packet loss status, and sending queue status are read first. The service type is used to generate service priorities, the candidate next-hop nodes are used to match interface roles in the node topology table, and the link latency, packet loss status, and sending queue status are used to filter the sending queue. The data payload is used to be forwarded after the sending queue and forwarding interface are determined. If S4 generates a link anomaly determination result, S5 uses the updated candidate next-hop nodes and forwarding interfaces; if S4 generates a link normal determination result, S5 uses the candidate next-hop nodes determined in S3.
[0039] When the connection status, link latency, packet loss status, and transmission queue status all fail to meet the abnormal triggering conditions, a service priority is generated according to the service type. The service priority is used to determine the order in which multiple service data enters the transmission queue when they simultaneously enter the transmission process. Subsequently, candidate next-hop nodes are matched against the node topology table to obtain interface roles. Interface roles indicate whether the data payload should be transmitted via the upstream connection direction corresponding to the STA mode WiFi network card or the downstream access direction corresponding to the AP mode WiFi network card. Then, based on link latency, packet loss status, and transmission queue status, transmission queues that have not reached the queue congestion threshold are filtered. The forwarding interface corresponding to the interface role is bound to the transmission queue, and the data payload is sent to the backend server or target construction equipment corresponding to the destination address according to the binding result, thus obtaining the service data transmission result.
[0040] If S4 generates a link anomaly determination result, S5 reads the alternative next-hop node and forwarding interface from the abnormal link forwarding update result, and re-determines the sending queue based on the service type, link latency, packet loss status, and sending queue status. At this time, the data load is still sent to the backend server or target construction equipment corresponding to the destination address, and the sending path is adjusted according to the alternative next-hop node and corresponding forwarding interface. Through this process, the connection status, link latency, packet loss status, and sending queue status are not only used to record link conditions, but also participate in candidate next-hop node updates, forwarding interface determination, and sending queue filtering.
[0041] In this embodiment, the node topology table is used throughout the processing flow from S2 to S5. S2 generates the node topology table; S3 uses the node topology table to verify the source object identifier and determine candidate next-hop nodes; S4 uses the node topology table to read adjacent available upstream base station nodes and available downstream access objects; and S5 uses the node topology table to match candidate next-hop nodes as interface roles. Service type is used throughout the processing flow from S3 to S5. S3 extracts the service type and verifies the destination address accordingly; and S5 generates service priorities based on the service type. Destination address is used throughout the processing flow from S3 to S5. S3 determines candidate next-hop nodes based on the destination address; S4 matches available upstream base station nodes or available downstream access objects with the destination address in case of link anomalies; and S5 sends the data payload to the backend server or target construction equipment corresponding to the destination address.
[0042] In this embodiment, the backend server is used to receive data payloads whose destination address is the backend server address, and the target construction equipment is used to receive data payloads whose destination address is the target construction equipment address. This embodiment does not further limit the internal storage structure of the backend server, the specific mechanical structure of the target construction equipment, or the specific product type of the local construction equipment. The backend server, the target construction equipment, and the local construction equipment only participate in the transmission process as data sending objects, data receiving objects, or data source objects in this embodiment.
[0043] This embodiment focuses on the method flow as its main extension object, fully disclosing the execution link of dual-NIC wireless bandwidth IoT base station node deployment, STA mode WiFi NIC connection, AP mode WiFi NIC registration, node topology table generation, service data parsing, destination address verification, candidate next-hop node determination, anomaly trigger judgment, candidate next-hop node update, forwarding interface determination, sending queue filtering, and data payload transmission. The above processing steps have clear input-output relationships; the connection state, node topology table, service type, destination address, candidate next-hop node, link latency, packet loss status, and sending queue status formed in the previous step are all invoked in subsequent steps.
[0044] Without departing from the technical solution described in this invention, any equivalent substitutions, equivalent modifications, equivalent combinations, order adjustments, equivalent transformations of field names, equivalent succession of the executing entity, or equivalent changes in the carrier form that can be conceived by those skilled in the art should fall within the scope of protection of this patent; however, they shall not be extended to unclaimed subjects, nor shall they alter the substantive correspondence of the technical objects through name changes. Equivalent changes shall not replace, delete, or weaken the method features, control relationships, data relationships, timing relationships, parameter relationships, or network transmission relationships necessary to achieve the technical effect.
[0045] The above description is merely a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in the present invention should be included within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.
Claims
1. A method for transmitting WiFi wireless self-organizing networks with no bandwidth attenuation using dual network cards, characterized in that, Includes the following steps: S1: Deploy multiple dual-NIC wireless bandwidth IoT base station nodes in the tunnel construction area, and configure each base station node with a STA mode WiFi network card and an AP mode WiFi network card. S2: Connect the STA mode WiFi network card to the upper-level base station node and obtain the upper-level base station node identifier and connection status; register the AP mode WiFi network card with the lower-level base station node or local construction equipment and obtain the lower-level access object identifier and interface role; generate a node topology table based on the upper-level base station node identifier, the connection status, the lower-level access object identifier, and the interface role. S3: Receive service data from the local construction equipment, extract the service type, destination address and data payload, verify the destination address according to the service type, and determine the candidate next-hop node according to the node topology table and the destination address; S4: Collect link latency, packet loss status and sending queue status. When the connection status, link latency, packet loss status or sending queue status meet the abnormal triggering conditions, update the candidate next-hop node and forwarding interface according to the node topology table. S5: Determine the sending queue and the forwarding interface based on the service type, the candidate next-hop node, the link delay, the packet loss status, and the sending queue status, and send the data payload to the backend server or target construction equipment corresponding to the destination address.
2. The dual-NIC WiFi wireless self-organizing network transmission method with no bandwidth attenuation according to claim 1, characterized in that, The steps for deploying multiple dual-NIC wireless bandwidth IoT base station nodes in the tunnel construction area include: obtaining axial segment information, construction progress position information, and connection status of already deployed base station nodes in the tunnel construction area; matching the axial segment information with the construction progress position information to obtain candidate deployment segments; when there are no already deployed base station nodes in the candidate deployment segments, or when the connection status of already deployed base station nodes meets the abnormal triggering conditions, deploying new base station nodes in the candidate deployment segments, and configuring STA mode WiFi network cards and AP mode WiFi network cards for the new base station nodes to obtain the base station node deployment result.
3. The dual-NIC WiFi wireless self-organizing network transmission method with no bandwidth attenuation according to claim 2, characterized in that, The configuration steps for the newly added base station node include: enabling the STA mode WiFi network card to scan for connectable upper-level base station nodes within the candidate deployment section; selecting the target upper-level base station node from the upper-level base station nodes that meet the connection conditions according to the connection status; enabling the AP mode WiFi network card to generate an access identifier for access by lower-level base station nodes or local construction equipment; writing the target upper-level base station node, access identifier, and tunnel section of the newly added base station node into the node topology table to obtain the network access configuration result of the newly added base station node.
4. The dual-NIC WiFi wireless self-organizing network transmission method with no bandwidth attenuation according to claim 3, characterized in that, The steps of writing the target upper-level base station node, access identifier, and tunnel segment of the newly added base station node into the node topology table include: converting the target upper-level base station node into an upper-level base station node identifier, converting the access identifier into a lower-level access object identifier, associating the tunnel segment of the newly added base station node with the interface role, and generating a node topology table record when corresponding records exist for the upper-level base station node identifier, the lower-level access object identifier, and the interface role, thereby obtaining the node topology table update result.
5. The dual-NIC WiFi wireless self-organizing network transmission method with no bandwidth attenuation according to claim 1, characterized in that, The steps of receiving the service data from the local construction equipment and extracting the service type, destination address, and data payload include: reading the source object identifier and data header field of the service data; matching the source object identifier with the lower-level access object identifier in the node topology table to obtain the source verification result; when the source verification result is a successful match, extracting the service type and destination address from the data header field and separating the data payload from the service data to obtain the service data parsing result.
6. The dual-NIC WiFi wireless self-organizing network transmission method with no bandwidth attenuation according to claim 5, characterized in that, The destination address verification step of the business data parsing result includes: reading the business type and destination address in the business data parsing result; when the business type is a multi-source sensor data type, a monitoring video stream type, or a risk identification result type, matching the destination address with the backend server address to obtain the uplink business verification result; when the business type is a camera control command type, matching the destination address with the target construction equipment address to obtain the downlink business verification result.
7. The dual-NIC WiFi wireless self-organizing network transmission method with no bandwidth attenuation according to claim 6, characterized in that, The steps for determining the candidate next-hop node based on the uplink service verification result or the downlink service verification result include: when the uplink service verification result is a successful match, determining the candidate next-hop node based on the identifier of the upper-level base station node in the node topology table to obtain the uplink candidate forwarding result; when the downlink service verification result is a successful match, determining the candidate next-hop node based on the identifier of the lower-level access object in the node topology table to obtain the downlink candidate forwarding result.
8. The dual-NIC WiFi wireless self-organizing network transmission method with no bandwidth attenuation according to claim 1, characterized in that, The step of determining whether the connection status, link latency, packet loss status, or transmission queue status meets the abnormal triggering condition includes: comparing the connection status with the disconnection status, comparing the link latency with a latency threshold, comparing the packet loss status with a packet loss threshold, and comparing the transmission queue status with a queue congestion threshold. When any comparison result reaches the corresponding threshold or status condition, a link abnormality determination result is generated. When none of the comparison results reach the corresponding threshold or status condition, a link normality determination result is generated.
9. The dual-NIC WiFi wireless self-organizing network transmission method with no bandwidth attenuation according to claim 8, characterized in that, The steps of updating the candidate next-hop node and forwarding interface based on the link anomaly determination result include: reading the available upper-level base station nodes and available lower-level access objects adjacent to the current base station node according to the node topology table, matching the available upper-level base station nodes or available lower-level access objects with the destination address to obtain the alternative next-hop node, and determining the forwarding interface according to the interface role corresponding to the alternative next-hop node to obtain the abnormal link forwarding update result.
10. The dual-NIC WiFi wireless self-organizing network transmission method with no bandwidth attenuation according to claim 1, characterized in that, The steps for determining the sending queue and the forwarding interface based on the service type, the candidate next-hop node, the link latency, the packet loss status, and the sending queue status include: when the connection status, the link latency, the packet loss status, and the sending queue status all fail to meet the abnormal triggering conditions, a service priority is generated according to the service type; the candidate next-hop node is matched with the node topology table to obtain the interface role; sending queues that have not reached the queue congestion threshold are filtered based on the link latency, the packet loss status, and the sending queue status; the forwarding interface corresponding to the interface role is bound to the sending queue; and the data payload is sent to the backend server or target construction equipment corresponding to the destination address according to the binding result to obtain the service data sending result.
