A method and system for testing beyond-line-of-sight self-organizing network communication equipment

Abstract

The present invention discloses a method and system for testing beyond-line-of-sight self-organizing network communication equipment, which specifically relates to the technical field of dynamic multi-hop network performance testing. The method and system are used to solve the problem of multi-hop performance distortion caused by the inability of existing static tests to reflect topology mutations. The method comprises: constructing a dynamic topology of mobile nodes, monitoring the routing switching behavior of relay nodes, and identifying event density aggregation intervals; determining routing switching paths based on triple conditions of the number of transmission interruptions, the path switching interval, and the timing aggregation interval; generating a multi-hop signal attenuation factor through the correlation between node position data and the number of transmission interruptions, and reconstructing a discontinuous mutation link test scenario; finally, injecting traffic into the scenario and collecting end-to-end delay and throughput as performance evaluation indicators; achieving accurate laboratory reproduction of the dynamic topology and multi-hop coupling effects, and providing real-scenario equivalent testing capabilities for beyond-line-of-sight communication equipment.

Description

Technical Field

[0001] The present invention relates to the technical field of dynamic multi-hop network performance testing, and more particularly to a method and system for testing over-the-horizon self-organizing network communication equipment. Background Art

[0002] Beyond-line-of-sight (BLOS) ad hoc network communication equipment is widely used in scenarios such as emergency communications. To achieve stable transmission in non-line-of-sight (NLOS) conditions, such equipment typically relies on a multi-hop relay mechanism, where mobile nodes dynamically construct a temporary network topology. Existing testing methods typically operate within a pre-set static or semi-static topology, simulating fixed path loss and node locations to verify communication metrics (such as throughput and latency). While this model can assess basic device performance, the test environment differs structurally from actual deployment scenarios.

[0003] However, existing testing methods cannot accurately reflect the true impact of dynamic topology and multi-hop coupling on end-to-end performance. Because ad hoc network topologies constantly change in real-world scenarios (such as node movement and link switching), and multi-hop relays gradually amplify routing convergence hysteresis, this can lead to systematic deviations between static laboratory test results and actual values ​​measured in dynamic scenarios. Summary of the Invention

[0004] In order to overcome the above-mentioned defects of the prior art, the present invention provides a method and system for testing beyond-line-of-sight ad hoc network communication equipment to solve the problems raised in the above-mentioned background technology.

[0005] To achieve the above object, the present invention provides the following technical solutions:

[0006] A method for testing a beyond-line-of-sight ad hoc network communication device comprises the following steps:

[0007] S1. Build a test topology consisting of at least three mobile nodes, with the intermediate node acting as a relay node. Each node moves periodically along a preset trajectory and reports its location data in real time.

[0008] S2. Monitor the routing switching behavior of relay nodes, record the timestamp of each routing switch, and count the number of transmission interruptions and the interval between adjacent path switches for each relay node;

[0009] S3. Calculate the route switching event density per unit time according to the route switching timestamp, and mark it as a time series aggregation interval when the route switching event density exceeds a third threshold;

[0010] S4. If the number of transmission interruptions exceeds a first threshold, the interval between adjacent path switches is less than a second threshold, and the route switching event is within a timing aggregation interval, then it is determined that a route switching path exists;

[0011] S5. Generate a multi-hop signal attenuation factor based on the real-time correlation between the node location data corresponding to the routing switching path and the number of transmission interruptions, and reconstruct a discontinuous mutation link test scenario including the multi-hop signal attenuation factor;

[0012] S6. Inject test traffic into the discontinuous mutation link test scenario and collect end-to-end delay and throughput data as evaluation indicators.

[0013] Furthermore, a test topology comprising at least three mobile nodes is constructed, wherein the intermediate node serves as a relay node. Each node periodically moves along a preset trajectory and reports node location data in real time, including:

[0014] Set up an intermediate node as a relay node and two endpoint nodes, with the endpoint nodes distributed on opposite sides of the relay node;

[0015] Configure all endpoint nodes to move along a closed ring path, and the ring path size is larger than the communication radius of a single node;

[0016] Configure the relay node to move along a broken line path with directional mutation points;

[0017] During the movement, all nodes report their three-dimensional geographic location coordinates as node location data at fixed time intervals through a dedicated control channel.

[0018] Furthermore, the distance between adjacent mutation points is greater than an integer multiple of the communication radius of a single node.

[0019] Furthermore, the routing switching behavior of relay nodes is monitored, the timestamp of each routing switch is recorded, and the number of transmission interruptions and the interval between adjacent path switches of each relay node are counted, including:

[0020] Listening to the routing protocol signaling message type changes of the relay node through a dedicated control channel;

[0021] When the message type switches from route stabilization signaling to route request signaling, the corresponding moment is marked as the route switching timestamp;

[0022] The cumulative number of physical layer link interruptions between two consecutive route switching timestamps is recorded as the number of transmission interruptions;

[0023] The difference between the adjacent route switching timestamps is taken as the adjacent path switching interval.

[0024] Furthermore, the route switching event density per unit time is calculated based on the route switching timestamp, and when the route switching event density exceeds a third threshold, it is marked as a time series aggregation interval, including:

[0025] Taking the current route switching timestamp as the benchmark, a fixed time length is intercepted forward as the event density calculation window;

[0026] The number of route switching timestamps contained in the event density calculation window is counted as the route switching event density value;

[0027] Comparing the relationship between the route switching event density value and the third threshold;

[0028] If the route switching event density value exceeds the third threshold, the time interval corresponding to the current calculation window is marked as a time series aggregation interval.

[0029] Furthermore, if the number of transmission interruptions exceeds a first threshold, the adjacent path switching interval is less than a second threshold, and the route switching event is within a timing aggregation interval, then determining that a route switching path exists includes:

[0030] Parallel checking of the relationship between the current number of transmission interruptions and the first threshold;

[0031] Synchronously verifying the relationship between the current adjacent path switching interval and the second threshold;

[0032] Confirm whether the timestamp of the current route switching event falls within the time range of the marked timing aggregation interval;

[0033] When the number of transmission interruptions exceeds a first threshold, the interval between adjacent path switching is less than a second threshold, and the timestamp of the route switching event is within the timing aggregation interval, the output is a route switching path existence determination result.

[0034] Furthermore, a multi-hop signal attenuation factor is generated based on the real-time correlation between the node location data corresponding to the routing switching path and the number of transmission interruptions, and a discontinuous mutation link test scenario including the multi-hop signal attenuation factor is reconstructed, including:

[0035] Extracting the three-dimensional geographic location coordinates of the relay node corresponding to the route switching path at the route switching timestamp as the current node location data;

[0036] Read the real-time statistics of the number of transmission interruptions of the corresponding relay node within the time window of the routing switching event;

[0037] Calculate the single-hop signal attenuation factor corresponding to the relay node;

[0038] The multi-hop signal attenuation factor is obtained by multiplying the single-hop signal attenuation factors of all relay nodes on the routing switching path;

[0039] Configure RF channel attenuator parameters based on the multi-hop signal attenuation factor strength value to create a discontinuous mutation link test scenario.

[0040] Furthermore, the single-hop signal attenuation factor is calculated based on the inverse relationship between the displacement change in the current node position data and the real-time statistical value of the number of transmission interruptions.

[0041] Furthermore, test traffic is injected into the discontinuous mutation link test scenario, and end-to-end latency and throughput data are collected as evaluation indicators, including:

[0042] Inject constant bit rate test traffic data streams through a physical test port independent of the dedicated control channel;

[0043] During the test traffic transmission, the first packet sending timestamp and the last packet receiving timestamp between the endpoint nodes are synchronously recorded;

[0044] Calculate the end-to-end delay based on the difference between the first packet sending timestamp and the last packet receiving timestamp;

[0045] The amount of test traffic data that successfully reaches the target endpoint node within a unit time is counted as throughput data;

[0046] Outputs a set of evaluation metrics consisting of end-to-end latency and throughput data.

[0047] In another aspect, the present invention provides a beyond-line-of-sight ad hoc network communication equipment testing system, comprising the following modules:

[0048] A topology building module is used to build a test topology containing at least three mobile nodes, where the intermediate nodes act as relay nodes. Each node moves periodically along a preset trajectory and reports node location data in real time.

[0049] The routing monitoring module is used to monitor the routing switching behavior of relay nodes, record the timestamp of each routing switching, and count the number of transmission interruptions and the interval time between adjacent path switching of each relay node;

[0050] A density marking module is used to calculate the density of route switching events per unit time according to the route switching timestamp, and mark the route switching event as a time series aggregation interval when the route switching event density exceeds a third threshold;

[0051] a path determination module, configured to determine that a route switching path exists if the number of transmission interruptions exceeds a first threshold, the interval between adjacent path switching is less than a second threshold, and the route switching event is within a timing aggregation interval;

[0052] A scenario reconstruction module is used to generate a multi-hop signal attenuation factor based on the real-time correlation between the node location data corresponding to the routing switching path and the number of transmission interruptions, and reconstruct a discontinuous mutation link test scenario including the multi-hop signal attenuation factor;

[0053] The indicator collection module is used to inject test traffic in the discontinuous mutation link test scenario and collect end-to-end delay and throughput data as evaluation indicators.

[0054] Compared with the prior art, the present invention has the following beneficial effects:

[0055] By building a dynamic mobile topology environment and monitoring routing behavior changes in real time, the system accurately captures the timing characteristics of routing switching event aggregation, effectively reproducing the oscillation effects of topology mutations in real-world scenarios. By screening high-distortion paths based on triple constraints (frequent transmission interruptions, compressed switching intervals, and event aggregation), it accurately identifies the critical switching paths that cause multi-hop performance degradation, resolving the limitation of traditional static testing that cannot reflect dynamic routing oscillations.

[0056] By correlating node location data with the number of transmission interruptions to generate a multi-hop signal attenuation factor, and physically injecting this factor into the test environment to reconstruct a discontinuous mutation link, the multi-stage coupling attenuation effect during the routing switching process can be realistically simulated. This not only reproduces the instantaneous characteristics of path interruption, but also gradually amplifies signal distortion on multi-hop links, reducing the deviation rate between laboratory test results and performance data in actual dynamic scenarios to an acceptable range. BRIEF DESCRIPTION OF THE DRAWINGS

[0057] Figure 1 This is a flow chart of a method for testing beyond-line-of-sight ad hoc network communication equipment according to the present invention;

[0058] Figure 2 The present invention is a structural diagram of a beyond-line-of-sight ad hoc network communication equipment testing system. DETAILED DESCRIPTION

[0059] The following will provide a clear and complete description of the technical solutions in the embodiments of the present invention in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. All other embodiments obtained by ordinary technicians in this field based on the embodiments of the present invention without making any creative efforts shall fall within the scope of protection of the present invention.

[0060] Example 1: Figure 1 The present invention provides a method for testing a beyond-line-of-sight ad hoc network communication device, which comprises the following steps:

[0061] S1. Build a test topology consisting of at least three mobile nodes, with the intermediate node acting as a relay node. Each node moves periodically along a preset trajectory and reports its location data in real time.

[0062] S2. Monitor the routing switching behavior of relay nodes, record the timestamp of each routing switch, and count the number of transmission interruptions and the interval between adjacent path switches for each relay node;

[0063] S3. Calculate the route switching event density per unit time according to the route switching timestamp, and mark it as a time series aggregation interval when the route switching event density exceeds a third threshold;

[0064] S4. If the number of transmission interruptions exceeds a first threshold, the interval between adjacent path switches is less than a second threshold, and the route switching event is within a timing aggregation interval, then it is determined that a route switching path exists;

[0065] S5. Generate a multi-hop signal attenuation factor based on the real-time correlation between the node location data corresponding to the routing switching path and the number of transmission interruptions, and reconstruct a discontinuous mutation link test scenario including the multi-hop signal attenuation factor;

[0066] S6. Inject test traffic into the discontinuous mutation link test scenario and collect end-to-end delay and throughput data as evaluation indicators.

[0067] When implementing the test topology construction and location reporting process, the following operational procedures must be clearly defined. First, prepare three mobile node devices: one intermediate node device is designated as a relay node, and the other two endpoint nodes are deployed symmetrically to the left and right of the relay node. The intermediate node device is a dual-band wireless device model C, and the endpoint nodes are model D. All devices are pre-installed with the same operating system version, and the topology is configured using a configuration tool. Position initialization parameters include: With the laboratory coordinate system origin as the center point, the relay node's initial coordinates are (0, 0, 0), the left endpoint node's coordinates are (-400, 0, 0), and the right endpoint node's coordinates are (400, 0, 0). This positioning setting maintains a distance of 800 meters between the endpoint nodes, exceeding the 250-meter maximum communication radius of the model D device in the 2.4 GHz band.

[0068] Configuring all endpoint devices to move along a closed circular path is accomplished as follows: The circular path size parameter is defined as the diameter of the circular path, which must be greater than the single-node communication radius. In implementation, the single-node communication radius value is entered through the configuration interface. For example, if the communication radius is 250 meters based on the RF chip manual for model D, the system automatically sets the circular path diameter to 600 meters. Path generation uses the equal chord length segmentation method to calculate the coordinate sequence of the circular trajectory points: with the initial position of the relay node as the center, the circumferential coordinate points are calculated at 15-degree intervals. The chord lengths of adjacent points are calculated using a formula to ensure that they do not exceed the device movement error range.

[0069] The implementation of configuring the relay node to move along a broken line path with directional mutation points includes: the directional mutation point is defined as a set of coordinate turning points in the path trajectory with a turning angle greater than 60 degrees. Enter the turning point coordinate list through the path planning software, for example, set the path turning sequence to (0,0)→(300,500)→(800,300). The distance between adjacent mutation points is the straight-line distance between two consecutive points. This distance is calculated and verified by the coordinate system difference formula, for example, the first distance value is 360 meters. The aforementioned spacing must be greater than an integer multiple of the single-node communication radius value. The specific implementation takes the minimum multiple requirement of 2 times, that is, when the communication radius is measured to be 250 meters, the distance between adjacent turning points is set to be greater than 500 meters, and the system automatically verifies whether the input turning point coordinates meet this constraint.

[0070] During mobility, all node devices report real-time location information at fixed 500-millisecond intervals through a dedicated control channel at the device hardware layer. A dedicated control channel refers to an independent physical transmission channel divided according to the 802.11 protocol specification, which is spectrum-isolated from the service data channel. The fixed time interval setting is precisely triggered by the timer interrupt service routine of the device's real-time operating system. The reported data content is three-dimensional geographic location coordinates, including longitude, latitude, and altitude data. The detailed implementation process is as follows: After the device's built-in multi-mode satellite positioning module receives the global positioning system signal, it uses the Kalman filter algorithm to eliminate signal jitter errors and output three-dimensional location data that conforms to the WGS84 coordinate system; the data processing thread writes the latest location value to a specific memory address area; when the next timer interrupt is triggered, the memory data is encapsulated into a control frame format and physically sent to the monitoring host system after being scheduled by the media access control layer.

[0071] During the mobile control phase, the endpoint node device moves along a circular trajectory at a constant rate of 4 meters per second, and the coordinates of the motion trajectory are obtained by real-time calculation of the relative position of the center of the circle and the current angle value. The motion control of the relay node device includes a direction mutation processing mechanism: when approaching the 3-meter range of the path turning point coordinates, the steering control sub-process is activated, including deceleration to 0 meters per second, waiting for a 1-second direction adjustment period, realigning the direction of the next target point, and accelerating to the original rate. A 4-second timeout protection mechanism is set for the entire direction switching process to ensure the completion of the process. The three-dimensional position reporting operation runs uninterrupted throughout, and the monitoring host performs parsing and verification after receiving the data: checking whether the coordinate value is within the preset geographical range and whether the timestamp is continuously increasing. If three consecutive reporting failures are detected, the system automatically triggers an alarm and resets the node positioning module initialization process.

[0072] The implementation of the routing switching behavior of the monitoring relay node needs to be completed through the monitoring host system. The system is equipped with a dedicated network adapter to access a dedicated control channel. The channel divides independent frequency band resources at the physical layer and maintains a 50MHz spectrum interval with the service data channel. After the listening operation is started, the monitoring host network interface controller switches to the promiscuous working mode to capture all data frames transmitted in the dedicated control channel. The captured original byte stream is input into the parsing processing unit, which first identifies the type identification code located in the lower 4 bits of the second byte in the frame control field. When the identification code value is 1, it is determined to be a control frame, and the lower 4 bits of the third byte of the OLSR protocol packet header in the payload part are parsed: if the value is equal to 6, it is marked as routing stability signaling, and if it is equal to 1, it is marked as routing request signaling. This definition is implemented according to the RFC3626 protocol standard document.

[0073] The timestamp function is activated when a transition from stable to requested signaling type is detected for two consecutive frames. Timestamp acquisition uses the high-precision time interface provided by the operating system, specifically the Linux kernel function clock_gettime(), to obtain a nanosecond time value based on a monotonic clock. Within the CPU clock cycle when the message type switch is detected, the time acquisition operation is immediately executed and the result is stored in a first-in, first-out queue memory. The timestamp is stored in a 64-bit integer variable, with the upper 32 bits storing the second time and the lower 32 bits storing the nanosecond offset. Time synchronization is implemented using the PTP precision time protocol. During the test initialization phase, the node and host clocks are calibrated to a maximum deviation of ±50 microseconds. A local clock compensation table is maintained, and a linear regression algorithm is executed every 10 seconds to correct for clock drift errors.

[0074] The function of counting the number of transmission interruptions is deployed and runs locally on the relay node device. A physical layer link interruption is defined as: within a preset time window, the media access control layer confirmation frame loss events occur continuously and reach the set threshold value. In the specific implementation, the device driver maintains a status counter. When it detects that the link layer ACK response frame is not received within 500ms after data transmission, if this situation occurs three times consecutively within the 1ms event detection window, it is determined to be a single physical layer link interruption. The status counter value increment operation is executed by the hardware interrupt service program, and the counting result is uploaded to the monitoring host through the device management information library. The statistical time range is defined by two consecutive route switching timestamps. The monitoring host initializes the counter when timestamp T0 arrives, and reads the current count value when timestamp T1 arrives as the number of transmission interruptions this time. The data is stored in an unsigned 16-bit integer, and the valid value range is limited to between 0 and 65535.

[0075] The interval between adjacent path switching times is calculated through time difference processing. When the new route switching timestamp T1 is stored in the queue, the storage location of the previous record T0 is retrieved. The time difference calculation uses the formula Δt = (T1-T0) / 1000 to convert the result into milliseconds. A data validity verification mechanism is implemented: Δt ≥ 5ms is set as the minimum valid threshold to eliminate time acquisition errors, and Δt ≤ 180,000ms is set as the maximum valid threshold to avoid system anomalies. Valid results are stored in IEEE754 single-precision floating-point format, with a value range limited to 5ms to 180,000ms. The abnormal data processing process includes discarding invalid data records, triggering an abnormal event flag, and recording the timestamp and original difference information in the system log.

[0076] The data acquisition system employs a triple security mechanism. The protocol parsing layer deploys a dual-buffer storage area structure, with the buffer switching threshold set to 80% occupancy. Physical layer interrupt detection utilizes an event-driven model. Each interrupt record contains a millisecond-level event timestamp and signal strength value. Anomalies are detected by comparing the system timer reading with the timestamp sequence. Data persistence is stored in a log file format, with a disk synchronization operation performed every 100 records written. The file structure consists of a 4-byte file header identifier, an 8-byte start timestamp, a 2-byte record count, an N×8-byte data record area, and a 4-byte CRC32 checksum. The power-off protection mechanism is implemented by updating the metadata file after each synchronization operation, recording the last valid block file number and checksum.

[0077] During the process of calculating the density of routing switch events and marking time series aggregation intervals, a sliding time window analysis method is used to process the routing switch timestamp sequence. When the monitoring host system receives a new routing switch timestamp, the calculation process is immediately triggered. Using the current routing switch timestamp as the time reference point, a fixed time period is intercepted forward to serve as the event density calculation window. This fixed time length parameter is set based on the convergence characteristics of the routing protocol. For example, when using the OLSR protocol, the value is 2000 milliseconds, based on the minimum period for topology stability specified in RFC3626. During the time window determination process, the current timestamp value minus 2000000 microseconds is used as the window start time point based on the nanosecond system clock counter. The time boundary positioning accuracy is controlled within an error range of ±1 millisecond.

[0078] After determining the event density calculation window, count the number of route switching timestamps within that period. This statistics is performed by querying the timestamp sequence storage area: Enter the window start time value, T_start, and end time value, T_end, and retrieve all timestamp records greater than or equal to T_start and less than or equal to T_end. A binary search algorithm is used to quickly match valid records within the time interval, and the number of statistical items is counted as the route switching event density value. This value is stored in an unsigned 16-bit integer format and represents the frequency of events within a fixed duration. Data validation is performed after each statistical result is generated, for example, to check whether the statistical value exceeds 300% of the historical maximum density. If so, a secondary verification process is triggered.

[0079] After obtaining the route switching event density value, a threshold comparison operation is performed. The third threshold uses a dynamic configuration mechanism, and the initial value is set by analyzing the average density value of the previous five tests. The specific setting process is as follows: the arithmetic mean of the historical data set is calculated, and this value is multiplied by a coefficient of 1.3 as the initial third threshold. When the comparison operation is performed, the current density value is converted to a 32-bit floating point number and input into the comparator circuit for numerical comparison with the third threshold parameter. When the comparator outputs a result greater than zero, it is determined that the density value exceeds the threshold. The threshold dynamic update mechanism sets the detection cycle to every 20 timestamp records processed. The threshold is adjusted by calculating the sliding average of the newly collected density values, and the adjustment range is limited to ±10%.

[0080] When the route switching event density value exceeds the current third threshold, the timing aggregation interval marking operation is activated. The time range of the timing aggregation interval is defined as the start time to the end time of the event density calculation window, and the boundary value is accurate to millisecond-level time accuracy. The specific implementation of the marking operation is: extract the window start time value T_start and the end time value T_end, package and generate the time interval data structure and write it to the permanent storage area. The data structure format includes: 8-byte start timestamp, 8-byte end timestamp, 2-byte trigger density value, 4-byte version number, and 4-byte cyclic redundancy check code. At the same time, the time interval is registered to the event management queue, and the status identifier is set to a high-priority pending event.

[0081] Multiple safeguards were implemented during the implementation process. The event density calculation window length was constrained, with a minimum of 100 milliseconds to prevent statistical distortion and a maximum of 5000 milliseconds to avoid response delays. A buffering mechanism was enabled for statistical operations, automatically switching to batch mode when the query timestamp exceeded 1000 records. A soft decision mechanism was added to the threshold comparison phase: if three consecutive comparison results were within the ±10% range of the threshold, a weighted review calculation was initiated, incorporating historical variance values ​​into the evaluation. Integrated integrity verification ensured that data was read out immediately after each write for reverse verification, ensuring bit-level consistency within the time range.

[0082] During the routing switch path determination process, three verification condition checks are performed in parallel. After the transmission interruption count verification process is initiated, the monitoring host system directly reads the current transmission interruption count value from the shared memory area. This value is stored as a 32-bit unsigned integer and records the cumulative number of physical layer link interruptions that have occurred since the previous routing switch timestamp. The first threshold is set based on statistical analysis of historical test data: the maximum transmission interruption count data from at least five complete test cycles is collected, the arithmetic mean is calculated, and then multiplied by a coefficient of 1.2 to serve as the initial threshold. The comparison operation is performed by a dedicated comparator hardware circuit: the read transmission interruption count is input to port A of the comparator, the first threshold is input to port B, an A-B subtraction operation is performed, and the sign bit of the flag register is checked. If the flag bit is 0 and the result value is non-zero, a condition is satisfied signal is generated. The first threshold is updated after every 10 determinations: a sliding average is calculated for the newly collected data set, and the new threshold is adjusted within a range of ±15% of the original threshold.

[0083] The verification of the adjacent path switching interval is initiated simultaneously with the interruption detection. The system obtains the latest calculated adjacent path switching interval value from the ring buffer. This data is stored as an IEEE754 single-precision floating-point number in milliseconds. The second threshold is dynamically adjusted based on the routing protocol type: when the OLSR protocol is detected, the baseline value is 300 milliseconds, and when the AODV protocol is detected, the baseline value is 500 milliseconds. The base value is selected based on the minimum path holding time parameter defined in the reference protocol specification. The comparison operation is completed using the floating-point operation unit: the current interval time value is input to the floating-point comparator input port A, the second threshold is input to port B, and the relational operation _A_<_B_ is performed. When the output status code is true, a condition satisfaction signal is generated. The tester is allowed to perform a floating correction of the baseline value by ±20% through the configuration interface, for example, setting the OLSR environment correction value to 360 milliseconds.

[0084] The inclusion verification of the time series aggregation interval is triggered when a route switching event occurs. The system retrieves the time series aggregation interval record set stored in the non-volatile memory, which is sorted in ascending time order. The verification operation process includes: extracting the timestamp value of the current route switching event, which is a microsecond time value stored in a 64-bit integer format; traversing all time series aggregation interval record items, each record contains an 8-byte start timestamp and an 8-byte end timestamp; performing interval inclusion calculation on each record: if the current timestamp satisfies the conditions of being greater than or equal to the start timestamp and less than or equal to the end timestamp at the same time, a match success mark is generated. The optimized query mechanism is: when the number of stored records exceeds 100, the binary search algorithm is automatically enabled, and the maximum query depth is set to 15 loop protections.

[0085] The comprehensive judgment of the three verification results is achieved through digital logic circuits. Three conditional signals are connected to a three-input AND gate circuit: Signal A comes from the transmission interruption count exceeding threshold flag, Signal B comes from the interval time low threshold flag, and Signal C comes from the timestamp inclusion match flag. The output port only generates a high-level valid signal when all three input signals are simultaneously at a logic high level. The valid signal triggers the judgment result output operation: a 64-byte data structure is constructed, consisting of an 8-byte event timestamp, a 4-byte conditional status code, a 6-byte node identifier, and a 46-byte reserved field. When the data structure is written to the event log file, the version control field value 0001h is added, and the path existence flag is set in the memory mapping area.

[0086] Multiple safeguards are configured during system implementation. The data verification phase utilizes a hardware-level dual-path redundancy design: two independent circuits synchronously execute the same operation, and the results are confirmed and output by a consistency comparator. The timestamp synchronization mechanism is implemented via a phase-locked loop circuit, synchronizing read operations with the 200MHz system clock. The anomaly detection unit includes: triggering data rollback and recovery when the interval value is negative; switching to the backup storage area when the time interval query takes longer than 200 milliseconds. A self-test program is set to execute at each system startup: testing all logic gate functions, verifying the read and write integrity of the storage area, and generating a self-test report that is written to the log system.

[0087] During the implementation of the discontinuous link reconstructing test scenario, the location data of relay nodes corresponding to the route switching path is first extracted. After determining the list of relay node identifiers based on the route switching path, the three-dimensional geographic location coordinates at the route switching timestamp are retrieved from the spatiotemporal database. The spatiotemporal database uses a time series storage architecture. The specific query instruction is: SELECT longitude, latitude, altitude FROM node_position WHEREnode_id = ? AND timestamp = ?. The node identifier in the query parameters is bound to the path configuration record, and the timestamp value is an exact match to the route switching event. For example, retrieving the record with relay node ID R005 at timestamp 1690000000000 microseconds returns the coordinates [116.407528, 39.904030, 45.6]. After extracting the location data, an integrity check is performed to check whether the altitude value is within the preset physically feasible range (-100 meters to 9000 meters). For abnormal data outside the range, a temporal neighbor interpolation algorithm is automatically used to repair the abnormal data.

[0088] The real-time statistics of transmission interruptions at the corresponding relay node within the time window of the route switch event are then retrieved. The time window is defined as a symmetric time interval based on the route switch timestamp. The interval length is fixed at 1000 milliseconds based on protocol characteristics. The statistics are calculated by executing a COUNT query in the transmission interruption log database: SELECT COUNT(*) FROM link_interruption WHERE node_id = ? AND timestamp BETWEEN ? AND ?. The time boundary parameter is calculated as the route switch timestamp plus or minus 500 milliseconds. The statistical results are stored as 32-bit unsigned integer variables and written to the shared memory area. A zero-value check mechanism is simultaneously enabled: when the statistical value reaches zero, the time window range is checked to ensure that it covers the valid period and the log file checksum is verified. A minimum cardinality constraint is also set: if the final statistical value is less than 3, it is forcibly set to 3 to reduce interference from low-probability events.

[0089] An inverse relationship model is established based on the displacement change in node location data and the transmission interruption statistics. The displacement change calculation process is to take the three-dimensional Euclidean distance difference between the coordinates at the current route switch timestamp and the coordinates at the previous route switch timestamp. The specific calculation steps include: obtaining the coordinate pair [longitude1, latitude1, altitude1] corresponding to the previous recorded timestamp; calculating the three-axis differences Δx = longitude2 - longitude1, Δy = latitude2 - latitude1, and Δz = altitude2 - altitude1; and calculating the displacement change with an accuracy of 0.01 meter. The inverse relationship model is defined as: single-hop signal attenuation factor K = (1000 / D) * (10 / (N+1)), where the constant 1000 meters represents the maximum theoretical communication distance of the device (set according to the RF chip specification), the constant 10 is a normalization coefficient, and N is the real-time transmission interruption statistics. A protection mechanism is implemented for the special case where the displacement D = 0: the D value is automatically replaced with 0.01 meters to prevent division by zero errors.

[0090] The cumulative multiplication of the single-hop signal attenuation factors for all relay nodes in a routing handover path is implemented as follows: First, a list of path nodes is obtained, sorted by signal transmission direction. The accumulator variable is initialized to 1.0 (double-precision floating point). As the node list is traversed, the single-hop signal attenuation factor Ki value for each node is read from the cache. The cumulative multiplication operation is performed: result = result × Ki. A value range protection strategy is set: when the cumulative value exceeds 1000, logarithmic calculation mode is switched (multiplication is converted to ln(K) addition and then exponential reduction); when the cumulative value is less than 0.000001, the value is forced to 0.000001. Intermediate result buffering is performed after processing every three nodes to prevent data loss due to power outages.

[0091] RF channel attenuator parameters are configured based on the multi-hop signal attenuation factor strength. The floating-point attenuation factor is converted to a decibel value: Atten_dB = 10×log10(K), where log10 is the base-10 logarithm. Configuration parameters are sent to the RF instrument using standard SCPI commands: for example, the command "ATT SET " + str(Atten_dB) + "DB" is written to the instrument control port. A programmable attenuation array is used to implement discontinuous link mutation test scenarios. Upon detecting a route switch event, the instrument driver performs three steps: reads the multi-hop signal attenuation factor of the new path, calculates the required attenuation value, and then sends a tuning command to the specified attenuator port. The state switch process is controlled to a mutation time of less than 10 microseconds, simulating the effect of a momentary physical link disruption.

[0092] When implementing performance test traffic injection in a non-continuous mutation link test scenario, an independent physical test port is used to inject a constant bit rate test traffic data stream. This port is physically isolated from the dedicated control channel at the hardware level and is implemented using an independent network interface controller chip. The specific connection scheme is as follows: the traffic generator device is connected to the dedicated test port hub via the RJ-45 interface, and the hub output is connected to the physical test interface of the target endpoint node. The constant bit rate transmission mode configuration parameters include: setting the bit rate value to 10 megabits per second, the data frame length to a fixed load of 1500 bytes, and the frame interval time to a 96-bit transmission time slot. The startup process control is: after the test scenario reconstruction completion signal is triggered, the traffic data stream is sent with a delay of 50 milliseconds.

[0093] During the test traffic transmission, the first packet transmission timestamp and the last packet reception timestamp are synchronously recorded. The first packet transmission timestamp recording mechanism is as follows: when the traffic generator detects the media access control layer start sending event for the first frame of data, a high-resolution timer with nanosecond accuracy is called to capture the time value. The timestamp format is a 64-bit integer (the upper 32 bits store seconds, and the lower 32 bits store nanoseconds). The last packet reception timestamp recording mechanism is as follows: when the physical layer chip of the target endpoint node detects the frame check sequence pass signal of the last frame, it triggers a direct memory access to obtain the system time value. The time synchronization system is deployed using the IEEE1588 v2 Precision Time Protocol network. The master clock source is connected to the timestamp recorders at each node via coaxial cable, ensuring that the clock deviation between devices is within ±100 nanoseconds. Timestamp data is stored using a double-buffer alternating recording strategy: after each recording cycle, all data blocks in the buffer are written to non-volatile solid-state storage.

[0094] End-to-end delay is calculated based on the first packet send timestamp and the last packet receive timestamp. The calculation algorithm involves subtracting the first packet send timestamp (T_start) from the last packet receive timestamp (T_end). The resulting difference, Δt = (T_end - T_start), is first converted to microseconds and then divided by 1000 to obtain a millisecond precision value. An additional compensation mechanism is implemented during the calculation process: Based on the hop count H of the measured path, an additional compensation value, δt = 0.02 × H milliseconds, is added. The compensation factor of 0.02 milliseconds / hop is derived from laboratory channel propagation data. The calculated results are constrained to be within the valid range of 0 milliseconds to 10,000 milliseconds. Values ​​outside this range are marked as invalid and the data review process is initiated. The final delay value is stored in IEEE 754 single-precision floating-point format with three decimal places of precision.

[0095] Throughput data is generated by counting the amount of test traffic data that successfully reaches the target endpoint node within a unit time. Statistics are performed by setting the unit time window length to an integer value of 1000 milliseconds, with the start of the time window aligned with the rising edge of the system clock's second pulse. Data volume is calculated by deploying traffic analyzer software on the target node and filtering received valid test traffic data frames. Valid frames are determined by continuously increasing sequence numbers in the frame header and correct cyclic redundancy check (CRC). Data frames with duplicate sequence numbers, gaps, or CRC errors are discarded. The throughput calculation formula is: Throughput = (N × 1500 × 8) / t, where N is the number of valid frames in the time window, 1500 represents the number of bytes per frame, 8 represents the byte-to-bit conversion factor, and t is the time window length of 1000 milliseconds. The calculated result is converted to an integer bit-per-second value and stored in a 32-bit register.

[0096] Outputs a set of evaluation metrics consisting of end-to-end latency and throughput data. The data structure of the evaluation metric set is defined as follows: A structure member contains a 4-byte floating-point latency value, a 4-byte throughput integer value, an 8-byte test sequence number, and a 4-byte data checksum. The output process is as follows: after completing statistics for each unit time window, the data structure is encapsulated; the XOR value of all bytes except the checksum field is calculated as the checksum; and the complete structure is synchronously written to the disk log file and the network monitoring platform. The output frequency is fixed at once per second. During continuous output, when the total test duration reaches 300 seconds, the performance summary generator is automatically activated.

[0097] Example 2: Figure 2 The present invention provides a structural diagram of a beyond-line-of-sight self-organizing network communication equipment testing system, which includes the following modules:

[0098] A topology building module is used to build a test topology containing at least three mobile nodes, where the intermediate nodes act as relay nodes. Each node moves periodically along a preset trajectory and reports node location data in real time.

[0099] The routing monitoring module is used to monitor the routing switching behavior of relay nodes, record the timestamp of each routing switching, and count the number of transmission interruptions and the interval time between adjacent path switching of each relay node;

[0100] A density marking module is used to calculate the density of route switching events per unit time according to the route switching timestamp, and mark the route switching event as a time series aggregation interval when the route switching event density exceeds a third threshold;

[0101] a path determination module, configured to determine that a route switching path exists if the number of transmission interruptions exceeds a first threshold, the interval between adjacent path switching is less than a second threshold, and the route switching event is within a timing aggregation interval;

[0102] A scenario reconstruction module is used to generate a multi-hop signal attenuation factor based on the real-time correlation between the node location data corresponding to the routing switching path and the number of transmission interruptions, and reconstruct a discontinuous mutation link test scenario including the multi-hop signal attenuation factor;

[0103] The indicator collection module is used to inject test traffic in the discontinuous mutation link test scenario and collect end-to-end delay and throughput data as evaluation indicators.

[0104] The calculations involved in the embodiments are all dimensionless numerical calculations, and the preset parameters and thresholds in the calculations are set by those skilled in the art according to actual conditions.

[0105] The above embodiments may be implemented in whole or in part through software, hardware, firmware, or any other combination thereof. When implemented using software, the above embodiments may be implemented in whole or in part in the form of a computer program product.

[0106] Those skilled in the art will appreciate that the modules and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application of the technical solution and the invention constraints. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0107] In addition, each functional module in each embodiment of the present application may be integrated into one processing module, or each module may exist physically separately, or two or more modules may be integrated into one module.

[0108] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the modules is only a logical function division. In actual implementation, there may be other division methods, such as multiple modules or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or modules, which can be electrical, mechanical or other forms.

[0109] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

[0110] Finally: The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present invention should be included in the scope of protection of the present invention.

Claims

1. A method for testing a beyond-line-of-sight ad hoc network communication device, characterized in that: The steps include: S1. Build a test topology consisting of at least three mobile nodes, with the intermediate node acting as a relay node. Each node moves periodically along a preset trajectory and reports its location data in real time. S2. Monitor the routing switching behavior of relay nodes, record the timestamp of each routing switch, and count the number of transmission interruptions and the interval between adjacent path switches for each relay node; S3. Calculate the route switching event density per unit time according to the route switching timestamp, and mark it as a time series aggregation interval when the route switching event density exceeds a third threshold; S4. If the number of transmission interruptions exceeds a first threshold, the interval between adjacent path switches is less than a second threshold, and the route switching event is within a timing aggregation interval, then it is determined that a route switching path exists; S5. Generate a multi-hop signal attenuation factor based on the real-time correlation between the node location data corresponding to the routing switching path and the number of transmission interruptions, and reconstruct a discontinuous mutation link test scenario including the multi-hop signal attenuation factor; S6. Inject test traffic into the discontinuous mutation link test scenario and collect end-to-end delay and throughput data as evaluation indicators.

2. A method for testing a beyond-line-of-sight ad hoc network communication device according to claim 1, characterized in that: Construct a test topology consisting of at least three mobile nodes, with the intermediate node acting as a relay node. Each node moves periodically along a preset trajectory and reports its location data in real time, including: Set up an intermediate node as a relay node and two endpoint nodes, with the endpoint nodes distributed on opposite sides of the relay node; Configure all endpoint nodes to move along a closed ring path, and the ring path size is larger than the communication radius of a single node; Configure the relay node to move along a broken line path with directional mutation points; During the movement, all nodes report their three-dimensional geographic location coordinates as node location data at fixed time intervals through a dedicated control channel.

3. A method for testing a beyond-line-of-sight ad hoc network communication device according to claim 2, characterized in that: The distance between adjacent mutation points is greater than an integer multiple of the communication radius of a single node.

4. The method for testing a beyond-line-of-sight ad hoc network communication device according to claim 1, wherein: Monitor the routing switching behavior of relay nodes, record the timestamp of each routing switch, and count the number of transmission interruptions and the interval between adjacent path switches for each relay node, including: Listening to the routing protocol signaling message type changes of the relay node through a dedicated control channel; When the message type switches from route stabilization signaling to route request signaling, the corresponding moment is marked as the route switching timestamp; The cumulative number of physical layer link interruptions between two consecutive route switching timestamps is recorded as the number of transmission interruptions; The difference between the adjacent route switching timestamps is taken as the adjacent path switching interval.

5. The method for testing a beyond-line-of-sight ad hoc network communication device according to claim 1, wherein: The route switching event density per unit time is calculated based on the route switching timestamp. When the route switching event density exceeds the third threshold, it is marked as a time series aggregation interval, including: Taking the current route switching timestamp as the benchmark, a fixed time length is intercepted forward as the event density calculation window; The number of route switching timestamps contained in the event density calculation window is counted as the route switching event density value; Comparing the relationship between the route switching event density value and the third threshold; If the route switching event density value exceeds the third threshold, the time interval corresponding to the current calculation window is marked as a time series aggregation interval.

6. The method for testing a beyond-line-of-sight ad hoc network communication device according to claim 1, wherein: If the number of transmission interruptions exceeds a first threshold, the adjacent path switching interval is less than a second threshold, and the route switching event is within a timing aggregation interval, then it is determined that a route switching path exists, including: Parallel checking of the relationship between the current number of transmission interruptions and the first threshold; Synchronously verifying the relationship between the current adjacent path switching interval and the second threshold; Confirm whether the timestamp of the current route switching event falls within the time range of the marked timing aggregation interval; When the number of transmission interruptions exceeds a first threshold, the interval between adjacent path switching is less than a second threshold, and the timestamp of the route switching event is within the timing aggregation interval, the output is a route switching path existence determination result.

7. The method for testing a beyond-line-of-sight ad hoc network communication device according to claim 1, wherein: Based on the real-time correlation between node location data and transmission interruption times corresponding to the routing switching path, a multi-hop signal attenuation factor is generated. A discontinuous mutation link test scenario containing the multi-hop signal attenuation factor is reconstructed, including: Extracting the three-dimensional geographic location coordinates of the relay node corresponding to the route switching path at the route switching timestamp as the current node location data; Read the real-time statistics of the number of transmission interruptions of the corresponding relay node within the time window of the routing switching event; Calculate the single-hop signal attenuation factor corresponding to the relay node; The multi-hop signal attenuation factor is obtained by multiplying the single-hop signal attenuation factors of all relay nodes on the routing switching path; Configure RF channel attenuator parameters based on the multi-hop signal attenuation factor strength value to create a discontinuous mutation link test scenario.

8. A method for testing a beyond-line-of-sight ad hoc network communication device according to claim 7, characterized in that: The single-hop signal attenuation factor is calculated based on the inverse relationship between the displacement change in the current node position data and the real-time statistical value of the number of transmission interruptions.

9. The method for testing a beyond-line-of-sight ad hoc network communication device according to claim 1, wherein: Inject test traffic into a discontinuous link test scenario and collect end-to-end latency and throughput data as evaluation metrics, including: Inject constant bit rate test traffic data streams through a physical test port independent of the dedicated control channel; During the test traffic transmission, the first packet sending timestamp and the last packet receiving timestamp between the endpoint nodes are synchronously recorded; Calculate the end-to-end delay based on the difference between the first packet sending timestamp and the last packet receiving timestamp; The amount of test traffic data that successfully reaches the target endpoint node per unit time is counted as throughput data; Outputs a set of evaluation metrics consisting of end-to-end latency and throughput data.

10. A beyond-line-of-sight self-organizing network communication equipment testing system, used to implement a beyond-line-of-sight self-organizing network communication equipment testing method according to any one of claims 1 to 9, characterized in that: Includes the following modules: A topology building module is used to build a test topology containing at least three mobile nodes, where the intermediate nodes act as relay nodes. Each node moves periodically along a preset trajectory and reports node location data in real time. The routing monitoring module is used to monitor the routing switching behavior of relay nodes, record the timestamp of each routing switching, and count the number of transmission interruptions and the interval time between adjacent path switching of each relay node; A density marking module is used to calculate the density of route switching events per unit time according to the route switching timestamp, and mark the route switching event as a time series aggregation interval when the route switching event density exceeds a third threshold; a path determination module, configured to determine that a route switching path exists if the number of transmission interruptions exceeds a first threshold, the interval between adjacent path switching is less than a second threshold, and the route switching event is within a timing aggregation interval; A scenario reconstruction module is used to generate a multi-hop signal attenuation factor based on the real-time correlation between the node location data corresponding to the routing switching path and the number of transmission interruptions, and reconstruct a discontinuous mutation link test scenario including the multi-hop signal attenuation factor; The indicator collection module is used to inject test traffic in the discontinuous mutation link test scenario and collect end-to-end delay and throughput data as evaluation indicators.

Images