Distributed integrated test system, method, apparatus and device

By building a data sharing domain through a distributed integration testing system, the problem of low efficiency in multi-device collaborative debugging in complex systems is solved, and automated integration testing and collaborative performance evaluation are realized, thereby improving testing efficiency and result management capabilities.

CN123114975APending Publication Date: 2026-11-17INFLYNC AVIATION TECHNOLOGY (SHANGHAI) CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202611426237.5
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2026-09-15
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

In existing technologies, the testing efficiency of multi-device collaborative debugging in complex systems is low, and the test tasks of different devices are distributed on different test hosts, making it inconvenient to manage the test content and results, and failing to reflect the functional performance of the integrated devices.

Method used

A distributed integration testing system is adopted, which constructs a data sharing domain through a distributed data communication service module between the integration testing center equipment and multiple test execution devices. Based on cross-device collaborative test case scheduling, test tasks are scheduled to realize the correlation analysis of test data and performance evaluation.

Benefits of technology

It enables automated integrated testing of multiple test execution devices, improves testing efficiency, unifies the management of test content and results, and reflects the collaborative performance of the integrated devices.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123114975A_ABST
    Figure CN123114975A_ABST
Patent Text Reader

Abstract

The application provides a distributed integrated test system, method, device and equipment, and relates to the technical field of distributed system integrated test. The system comprises: an integrated test center device; a plurality of test execution devices, each test execution device being used for corresponding connection with a measured object; the integrated test center device and each test execution device being in communication connection; a distributed data communication service module, which is deployed on the integrated test center device and each test execution device, and is used for constructing a data sharing domain in the system; the integrated test center device is used for scheduling at least two test execution devices to synchronously execute a test task through the data sharing domain according to a preset cross-device cooperative test case; receiving test data reported by each test execution device through the data sharing domain; and performing correlation analysis on the test data to obtain integrated cooperative performance indexes between the measured objects. The method is used to improve the efficiency of integrated test.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the field of distributed system integration testing technology, and more specifically, to a distributed integration testing system, method, apparatus, and equipment. Background Technology

[0002] Currently, complex systems such as aerospace vehicles and electric vehicles contain a wide variety of integrated test center equipment. During the system design and integration process, it is necessary to test each subsystem and equipment component.

[0003] In existing technologies, different devices are tested independently, and the tests between different devices or subsystems are unrelated. After the tests are passed, the devices are connected together for integration, manual debugging, or joint testing.

[0004] However, in existing technologies, for multi-device collaborative debugging in complex systems, the efficiency of manual testing is low because the devices work together through signal cross-linking, data dependence, and timing coordination. Summary of the Invention

[0005] The purpose of this application is to provide a distributed integration testing system, method, apparatus, and device to solve the above-mentioned problems existing in the prior art, and to realize automated integration testing of multiple test execution devices, thereby greatly improving the efficiency of integration testing.

[0006] Firstly, a distributed integration testing system is provided, including: Integrated testing center equipment; Multiple test execution devices are provided, each of which is connected to the object under test; the integrated test center device is communicatively connected to each of the test execution devices. A distributed data communication service module is deployed on the integrated test center equipment and each of the test execution equipment, and is used to build a data sharing domain in the system; The integrated testing center equipment is used to schedule at least two test execution devices to synchronously execute test tasks through the data sharing domain according to preset cross-device collaborative test cases; receive test data reported by each test execution device through the data sharing domain; and perform correlation analysis on the test data to obtain the integrated collaborative performance indicators between the tested objects.

[0007] Secondly, a distributed integration testing method is provided, applied to an integration testing center device, wherein the integration testing center device is communicatively connected to multiple test execution devices, and each of the test execution devices is signal-connected to a corresponding object under test; the method includes: Based on the acquired test instructions, load the preset cross-device collaborative test cases; and generate test control instructions corresponding to each test execution device according to the cross-device collaborative test cases. Through the data sharing domain, corresponding test control commands are issued to each of the test execution devices; the data sharing domain is established based on the distributed data communication service module deployed on the integration test center device and each of the test execution devices; Through the data sharing domain, test data reported by each of the test execution devices is received; correlation analysis is performed on the test data to obtain the integration and collaboration performance indicators between the tested objects.

[0008] Thirdly, a distributed integration testing device is provided, applied to an integration testing center device, wherein the integration testing center device and multiple test execution devices are communicatively connected, and each of the test execution devices is signal-connected to a corresponding object under test; the device includes: The generation module is used to load preset cross-device collaborative test cases based on the acquired test instructions; and generate test control instructions corresponding to each test execution device according to the cross-device collaborative test cases. The distribution module is used to distribute the corresponding test control commands to each of the test execution devices through the data sharing domain; the data sharing domain is established based on the distributed data communication service module deployed on the integration test center device and each of the test execution devices. The analysis module is used to receive test data reported by each of the test execution devices through the data sharing domain; and to perform correlation analysis on the test data to obtain the integration and collaboration performance indicators between the tested objects.

[0009] Fourthly, an integrated test center device is provided, which includes a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory communicate with each other through the communication bus. Memory, used to store computer programs; When a processor executes a program stored in memory, it implements any of the steps described in the first aspect above.

[0010] Fifthly, a computer-readable storage medium is provided, wherein a computer program is stored therein, and when executed by a processor, the computer program implements the steps of any of the methods described in the first aspect above.

[0011] This application provides a distributed integration testing system, method, apparatus, and device. The system includes: an integration testing center device; multiple test execution devices, each connected to a corresponding object under test (DUT); a communication connection between the integration testing center device and each test execution device; a distributed data communication service module deployed on the integration testing center device and each test execution device, used to build a data sharing domain within the system; the integration testing center device, used to schedule at least two test execution devices to synchronously execute test tasks according to preset cross-device collaborative test cases via the data sharing domain; receive test data reported by each test execution device through the data sharing domain; and perform correlation analysis on the test data to obtain integration and collaborative performance indicators between the DUTs. In this solution, based on complex, interconnected cross-device collaborative test cases, automated integration testing of multiple test execution devices is achieved; the integration testing center device can manipulate multiple device test hosts to implement device testing functions; the test process and test result recording can be uniformly completed on the integration testing center device; and the distributed integration testing system uniformly schedules test device resources to realize multi-device functional integration testing tasks, suitable for real-time synchronous integration testing of complex testing systems. Therefore, by integrating the test systems of various devices under test (i.e., objects under test) in a complex system, and connecting all test execution devices of these devices through a distributed communication network, test data can be shared among these devices. The test content for different devices under test is uniformly managed by the integration test center. During testing, the test content only needs to be distributed to the relevant devices under test, which then complete the test tasks and report the results. This achieves automated integrated testing across multiple test execution devices, greatly improving the efficiency of integration testing. Attached Figure Description

[0012] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments of this application will be briefly introduced below. It should be understood that the following drawings only show some embodiments of this application and should not be regarded as a limitation of the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0013] Figure 1 A schematic diagram of a distributed integration testing system provided in an embodiment of this application; Figure 2 This application provides a schematic diagram of the architecture of a distributed integration testing system. Figure 3 A schematic diagram illustrating the integration test of an altimeter, flight control computer, and landing gear, provided for an embodiment of this application; Figure 4 A schematic diagram illustrating a dynamic characteristic test of a control surface provided in an embodiment of this application; Figure 5 A flowchart illustrating a distributed integration testing method provided in an embodiment of this application; Figure 6 This is a schematic diagram of the structure of a distributed integration testing device provided in an embodiment of this application; Figure 7 This is a schematic diagram of the structure of an integrated testing center device provided in an embodiment of this application. Detailed Implementation

[0014] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of the embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application. Unless otherwise defined, the technical or scientific terms used in this application should have the ordinary meaning understood by those skilled in the art. The words "first," "second," and similar terms used in this application do not indicate any order, quantity, or importance, but are only used to distinguish different components. The words "comprising" or "including," etc., mean that the element or object preceding the word covers the element or object listed after the word and its equivalents, but do not exclude other elements or objects. The words "connected," "coupled," or "connected," etc., are not limited to physical or mechanical connections, but can include electrical connections, whether direct or indirect. "Up," "down," "left," "right," etc., are only used to indicate relative positional relationships. When the absolute position of the described object changes, the relative positional relationship may also change accordingly.

[0015] Currently, complex systems such as aerospace vehicles and electric vehicles contain a wide variety of integrated test center equipment. During the system design and integration process, it is necessary to test each subsystem and equipment component.

[0016] In existing technologies, testing is primarily conducted independently on different devices, with tests between different devices or subsystems being unrelated. After passing the tests, the devices are then connected together for integration and manual debugging or joint testing. However, in existing technologies, for collaborative debugging of multiple devices in complex systems, manual testing is inefficient due to the collaborative work between devices through signal cross-linking, data dependence, and timing coordination.

[0017] Furthermore, existing technologies suffer from the following technical problems: For different device testing tasks, these tasks are distributed across different test hosts, making it inconvenient to track and manage the test content and results. In complex systems, devices are interdependent; test content and results for a single device cannot reflect its functional performance when integrated with other devices.

[0018] The preferred embodiments of this application are described below with reference to the accompanying drawings. It should be understood that the preferred embodiments described herein are for illustration and explanation only and are not intended to limit this application. Furthermore, the embodiments and features in the embodiments of this application can be combined with each other without conflict.

[0019] Figure 1 This is a schematic diagram of a distributed integration testing system provided in an embodiment of this application. Figure 1 As shown, the system includes: Integrated testing center equipment; Multiple test execution devices, each connected to the object under test; communication connections between the integrated test center equipment and each test execution device; The distributed data communication service module is deployed on the integration test center equipment and various test execution equipment to build a data sharing domain in the system. The integrated test center equipment is used to schedule at least two test execution devices to synchronously execute test tasks according to preset cross-device collaborative test cases through a data sharing domain; receive test data reported by each test execution device through the data sharing domain; and perform correlation analysis on the test data to obtain the integration and collaboration performance indicators between the tested objects.

[0020] For example, the system includes an integration test center device and multiple test execution devices, each test execution device being connected to its corresponding object under test; the integration test center device and each test execution device are connected via a communication network. A distributed data communication service module is deployed on both the integration test center device and each test execution device, and is used to build a data sharing domain within the system. Specifically, the integration test center device and each test execution device uniformly activate their respective deployed distributed data communication service modules to build and join the same data sharing domain; the data sharing domain is a DDS domain.

[0021] Because communication within this distributed integration testing system is based on a data distribution service and is data-oriented, any device can access all data within the data communication domain without relying on any data relay or central device. For ease of use, an integration testing center device is added to the data communication domain to centrally manage all integration test data. Within the data sharing domain, the integration testing center device interacts with each test execution device, and with each test execution device itself, through a publish / subscribe model of the DDS (Distributed Data System). Any device joined to this DDS domain acts as a data publisher, publishing data to the DDS domain, while other devices act as data subscribers, obtaining the required data from the DDS domain.

[0022] The integration test center equipment stores multiple preset cross-device collaborative test cases, which include trigger conditions, action dependencies, and expected response results. Based on these preset cross-device collaborative test cases, the integration test center equipment schedules at least two test execution devices to synchronously execute test tasks via a data sharing domain. After each of the at least two test execution devices executes its test task, it generates test data and sends it to the integration test center equipment via the data sharing domain. The integration test center equipment receives the test data reported by each test execution device through the data sharing domain, then performs correlation analysis on the test data to obtain integration and collaborative performance indicators between the tested objects.

[0023] Therefore, by utilizing a Data Distribution Service (DDS), control commands or acquired data from numerous test devices (including test computers and test modules) of a complex system are centralized to form an interconnected data sharing domain. Modules within this domain can subscribe to relevant data as needed, enabling distributed data communication services. This distributed data communication service is then integrated with various test execution devices for complex systems such as UAVs and eVTOL (electric vertical takeoff and landing) aircraft to form a distributed integrated test system.

[0024] Optionally, the test execution equipment includes two types: test host and test module. The test host is a test computer that establishes a signal connection with the corresponding object under test (DUT) via a dedicated test cable. Based on the test control commands issued by the integrated test center equipment, the test host outputs excitation signals to the corresponding DUT via the dedicated test cable and collects feedback signals from the corresponding DUT via the same dedicated test cable. The test module is a data acquisition device that integrates a distributed data communication service module and includes wired and wireless communication modules. The wired communication module connects to a network switch via a network cable to access the communication network, while the wireless communication module connects to a wireless access point (AP) via Wi-Fi protocol to access the network switch. Therefore, the test module establishes a signal connection with the corresponding DUT via wired or wireless means, collects the DUT's operational status data, and publishes it to the data sharing domain through the distributed data communication service module. Therefore, each test host achieves physical connection between devices through a network switch. The test module includes a wired communication module and a wireless communication module: the wired communication module, like the test computer, is physically connected to the network switch via a network cable; the wireless communication module supports Wi-Fi and connects to the network switch via a wireless access point (AP).

[0025] Optionally, the communication network includes a network switch; the integration test center equipment and each test host are respectively configured with wired network interfaces, and each wired network interface is connected to the corresponding port of the network switch via a network cable; the network switch is used to establish physical layer data links between the devices, so that the integration test center equipment and each test execution device, as well as the test execution devices, form wired communication connections, providing a reliable data transmission channel at the underlying level for the distributed data communication service module.

[0026] The system provided in this application includes: an integrated testing center device; multiple test execution devices, each connected to a corresponding object under test; a communication connection between the integrated testing center device and each test execution device; a distributed data communication service module deployed on the integrated testing center device and each test execution device, used to build a data sharing domain in the system; the integrated testing center device is used to schedule at least two test execution devices to synchronously execute test tasks according to preset cross-device collaborative test cases through the data sharing domain; receive test data reported by each test execution device through the data sharing domain; and perform correlation analysis on the test data to obtain the integrated collaborative performance indicators between the objects under test. In this solution, based on complex, interconnected cross-device collaborative test cases, automated integrated testing of multiple test execution devices is achieved; the integrated testing center device can manipulate multiple device test hosts to realize device testing functions; the test process and test result recording can be uniformly completed on the integrated testing center device; and the distributed integrated testing system uniformly schedules test device resources to realize multi-device functional integrated testing tasks, suitable for real-time synchronous integrated testing of complex testing systems. Therefore, by integrating the test systems of various devices under test (i.e., objects under test) in a complex system, and connecting all test execution devices of these devices through a distributed communication network, test data can be shared among these devices. The test content for different devices under test is uniformly managed by the integration test center. During testing, the test content only needs to be distributed to the relevant devices under test, which then complete the test tasks and report the results. This achieves automated integrated testing across multiple test execution devices, greatly improving the efficiency of integration testing.

[0027] In one example, the Distributed Data Communication Service module is used to build a data sharing domain in the system based on the Data Distribution Service (DDS); the data sharing domain is the DDS domain; within the DDS domain, the integration test center device and each test execution device, as well as the test execution devices themselves, interact with each other through a publish / subscribe model.

[0028] For example, the distributed data communication service module is implemented based on the Data Distribution Service (DDS); the data sharing domain is the DDS domain; the integrated test center device and each test execution device uniformly start their respective deployed distributed data communication service modules and join the same DDS domain; within the DDS domain, the integrated test center device and each test execution device, as well as each test execution device, interact with each other through the DDS publish / subscribe model. Any device that joins the DDS domain acts as a data publisher and publishes data to the DDS domain, while other devices act as data subscribers and obtain the required data from the DDS domain.

[0029] In one example, the pre-defined cross-device collaborative test cases include triggering conditions and action dependencies. The integration test center device is used to generate control instructions to start the cross-device collaborative test cases according to the triggering conditions, issue control instructions to each relevant test execution device according to the action dependencies, and receive test data reported by each relevant test execution device.

[0030] For example, the preset cross-device collaborative test cases include triggering conditions, action dependencies, and expected response results. Triggering conditions represent the initial conditions that trigger collaborative test actions, including data threshold triggering conditions; action dependencies represent the temporal and logical dependencies between at least two tested objects, including sequential and / or synchronous execution; expected response results represent the response actions that each tested object should complete under the action dependencies.

[0031] The integrated test center equipment initiates the execution of cross-device collaborative test cases based on trigger conditions, issues control commands to each relevant test execution device according to action dependencies, and receives test data reported by each relevant test execution device.

[0032] In one example, the test data includes timestamp information marked by a preset global time base; an integrated test center device is used to extract the trigger time and completion time from the test data; the trigger time is the moment when the first test execution device performs the first action, or the moment when the state of the first tested object reaches a predetermined threshold; the completion time is the moment when the second test execution device completes the response action, or the moment when the state of the second tested object reaches a predetermined target value; the integrated test center device is used to perform time delay analysis on the completion time and the trigger time to obtain the time interval between the completion time and the trigger time, and uses this time interval as the response delay performance index of the integrated collaboration between the first tested object and the second tested object.

[0033] For example, the correlation analysis includes time delay analysis. The integration test center equipment obtains test data reported by each test execution device through a data sharing domain. The test data contains timestamp information marked by a uniformly preset global time base. The integration test center equipment extracts the trigger time and completion time from the test data; the trigger time is the moment when the first test execution device performs a first action, or the moment when the state of the first tested object reaches a predetermined threshold; the completion time is the moment when the second test execution device completes a response action, or the moment when the state of the second tested object reaches a predetermined target value. The integration test center equipment calculates the time interval between the completion time and the trigger time, and uses this time interval as a performance indicator of the response delay between the first and second tested objects in their integrated collaboration.

[0034] In one example, the integrated test center device sends frequency sweep control commands to the test execution device via a data sharing domain; the test execution device drives the corresponding connected object under test to perform frequency sweeping actions and generate response signal data according to the received frequency sweep control commands; the integrated test center device receives response signal data reported by each test execution device via the data sharing domain; the response signal data and the frequency sweep control commands are synchronized under a preset global time base; frequency domain dynamic characteristic analysis is performed on the command signal and response signal data of the frequency sweep control commands to obtain the dynamic response characteristics of the object under test.

[0035] For example, the correlation analysis includes frequency domain dynamic characteristic analysis. The integration test center equipment sends a frequency sweep control command to the test execution equipment via a data sharing domain. The test execution equipment drives the corresponding object under test (DUT) to perform a frequency sweep action according to the received frequency sweep control command, generating response signal data, and sends the response signal data to the integration test center equipment via the data sharing domain. The integration test center equipment receives the response signal data reported by each test execution equipment via the data sharing domain; the response signal data and the frequency sweep control command are synchronized under a unified global time base. The integration test center equipment performs frequency domain analysis on the command signal and response signal data of the frequency sweep control command to obtain the dynamic response characteristics of the DUT.

[0036] Optionally, after the integration test center equipment and each test execution equipment join the same data sharing domain through the distributed data communication service module, the data sharing domain adopts a peer-to-peer network architecture. Within the data sharing domain, any device can obtain all published data within the data sharing domain without needing to forward data through any dedicated data relay equipment or central equipment. The integration test center equipment is used to store preset cross-device collaborative test cases, issue test control commands, receive test data reported by each test execution equipment, and perform correlation analysis, without participating in data routing or data relay within the data sharing domain.

[0037] In one example, the integration test center device stores preset fault injection test cases; the integration test center device is also used to send fault injection instructions to the specified test execution device through the data sharing domain according to the fault injection test cases; the test execution device is used to apply simulated faults to the corresponding connected object under test according to the received fault injection instructions; the integration test center device is used to receive the test data reported by each test execution device under the simulated fault through the data sharing domain, and perform correlation analysis on the test data based on the preset global time base to obtain the integration and collaboration performance index of the object under test under fault conditions.

[0038] For example, the integration test center device stores preset fault injection test cases, which include fault type, fault injection time, fault target, and expected system response. The integration test center device is also used to send fault injection instructions to designated test execution devices through a data sharing domain, based on the fault injection test cases. Upon receiving the fault injection instruction, the test execution device applies a simulated fault to the corresponding connected object under test, including at least one of the following: signal interruption, data anomaly, response delay, and output deviation. The integration test center device receives test data reported by each test execution device under simulated fault conditions through the data sharing domain, and performs correlation analysis on the test data based on a unified global time benchmark to obtain the integration and collaboration performance indicators of the object under test under fault conditions.

[0039] Therefore, in addition to normal operating conditions, this application can also inject faults uniformly through the DDS data domain and synchronously collect the responses of each node under abnormal / fault conditions. That is, based on injecting a fault into one device, other devices synchronously observe the response, evaluate the collaborative performance of the system under fault conditions, and realize cross-device fault collaborative testing.

[0040] Optionally, for the global time base, the integration test center equipment also periodically sends synchronization probe messages to each test execution device through the data sharing domain and receives synchronization response messages returned by each test execution device. The integration test center equipment calculates the communication transmission delay between each test execution device and the integration test center equipment based on the sending time of the synchronization probe messages and the receiving time of the synchronization response messages. Finally, the integration test center equipment performs delay compensation correction on the test data reported by each test execution device based on the communication transmission delay of each test execution device, aligning the corrected test data to the same base time on the time axis; the integration test center equipment then performs correlation analysis based on the delay-compensated test data. Therefore, by introducing an active probe-response mechanism to dynamically sense the delay of each node and perform delay compensation correction on this basis, the time synchronization accuracy is improved from "logical alignment" to the "physical correction" level, ensuring the accuracy of the global time base.

[0041] Optionally, the system also includes a simulation host, on which a digital twin simulation module and a distributed data communication service module run. The simulation host joins the data sharing domain through the distributed data communication service module, and the digital twin simulation module interacts with other devices within the data sharing domain through the distributed data communication service module. The digital twin simulation module is used to construct a digital twin model of the first object under test, which simulates the input-output characteristics and dynamic behavior of the first object under test.

[0042] The integrated test center equipment sends test control commands to the digital twin simulation module through the data sharing domain. The digital twin simulation module drives the digital twin model to run according to the test control commands, outputting the first simulated response data of the first tested object under the first operating condition. The simulation host publishes the first simulated response data to the data sharing domain through the distributed data communication service module. The integrated test center equipment also sends the same test control commands to the actual test execution device connected to the second tested object through the data sharing domain. The test execution device drives the second tested object to run under the first operating condition, outputting the first measured response data of the second tested object under the first operating condition. The test execution device publishes the first measured response data to the data sharing domain through the distributed data communication service module.

[0043] The integrated test center equipment receives the first simulation response data and the first measured response data through the data sharing domain. Based on a unified global time reference, it performs correlation analysis on the first simulation response data and the first measured response data to obtain the integrated collaborative performance index of the first test object and the second test object under the first working condition.

[0044] Alternatively, the digital twin simulation module is used to construct a digital twin model of the first object under test, and then outputs the simulation response data of the first object under test under the first operating condition; at the same time, the integrated test center equipment also sends the same test control commands to the test execution equipment connected to the first object under test through the data sharing domain, and then outputs the actual test response data of the first object under test under the first operating condition, without limitation.

[0045] Therefore, the concept of digital twins is introduced, allowing virtual simulation models to participate in integration testing as devices within the data domain, enabling hybrid testing of real devices and virtual models. When certain physical devices are not yet ready or testing costs are too high, digital twin models can be used as substitutes, significantly expanding the scope and flexibility of testing. This achieves collaborative testing and correlation analysis of virtual and physical devices within the same data domain and on the same time benchmark.

[0046] Optionally, the integration test center equipment maintains available resource status information for each test execution device. This available resource status information includes at least one of the following: computational resource utilization, communication bandwidth occupancy, and current task queue length. The integration test center equipment is also used to dynamically select test execution devices to participate in the current test task based on the test requirements of cross-device collaborative test cases and the available resource status information of each test execution device. When the available resource status information of the selected test execution device does not meet a preset resource threshold, the integration test center equipment sends a task migration instruction to other test execution devices through the data sharing domain, migrating part or all of the current test task to other test execution devices for execution, resulting in a migrated task allocation scheme. Based on the migrated task allocation scheme, the integration test center equipment schedules each test execution device to synchronously execute the test task through the data sharing domain.

[0047] Therefore, based on dynamic resource awareness and task migration mechanisms, the system can dynamically adjust task allocation according to the real-time load status of each node, achieving load balancing and optimized resource utilization. Existing distributed testing systems mostly rely on static configuration for scheduling. This step introduces resource status awareness and task migration into the DDS collaborative testing architecture, enabling the system to have adaptive scheduling capabilities and demonstrating significant technical effectiveness in large-scale, long-term integration testing scenarios.

[0048] Optionally, the integration test center equipment monitors the test data streams reported by each test execution device in real time through a data sharing domain, and maintains the expected data pattern for each test data stream. The expected data pattern includes at least one of the following: data update frequency, data value range, and data change rate. When the integration test center equipment detects that the test data stream reported by any test execution device deviates from the expected data pattern, it determines that the test execution device or the corresponding test object has experienced a data anomaly. The expected data pattern refers to the regular characteristics that the test data stream of each test object should exhibit in terms of time and numerical characteristics under normal operating conditions. The expected data pattern includes the following three types: Data update frequency: refers to the time interval at which the test execution device reports test data, which depends on the sampling rate configuration of the data acquisition module and the data release cycle of the communication protocol; Data range: refers to the minimum and maximum values ​​that a physical quantity of the measured object can reach within the normal operating range, which depends on the design parameters and physical limits of the measured object; Data change rate: refers to the magnitude of change of a certain physical quantity of the measured object per unit time. It depends on the dynamic response characteristics of the measured object, including the upper limit of the speed of mechanical structure movement, the conversion rate of electrical signals, etc.

[0049] Before executing the current test task, the parameters of the aforementioned expected data pattern are configured by the test personnel according to the design parameters, physical characteristics, and test task requirements of the object under test, and stored in the integrated test center equipment. Determining whether there is a deviation can be done by setting the time interval between two adjacent sampled test data streams as Δt, the corresponding data change as ΔV, and the preset maximum allowable change rate as R_max. If |ΔV| / Δt > R_max, then a deviation is determined.

[0050] Based on the type of data anomaly, the integration test center equipment sends a self-healing command to the test execution device experiencing the anomaly via the data sharing domain. This self-healing command includes at least one of the following: restarting the test task, recalibrating the sensors, or switching to a backup test channel. After sending the self-healing command, the integration test center equipment continuously monitors the subsequent test data streams reported by the test execution device. If the data stream returns to normal, the current test task continues. If the data stream does not recover, the self-healing is deemed a failure, the test execution device is marked as faulty, the current test task is paused, an anomaly report is generated, and the test personnel are notified.

[0051] Therefore, the closed-loop mechanism of real-time data stream monitoring, expected pattern matching, and automatic self-healing enables anomaly detection and automatic recovery during the testing process. In long-term unattended integration testing scenarios, this mechanism can significantly improve the reliability and continuity of testing, achieving real-time anomaly detection and automatic recovery during the testing process.

[0052] Optionally, the integrated test center equipment, as a member of the data sharing domain, continuously records the following information during the execution of test tasks through the data sharing domain: test control instructions and timestamps issued to each test execution device at each time; test data and timestamps reported by each test execution device at each time; and data interaction events and their timestamps within the data sharing domain.

[0053] The integrated test center equipment organizes the recorded information into a replayable test sequence in chronological order. The replayable test sequence includes a complete timeline, command stream, and data stream. The integrated test center equipment is also used to reproduce any time segment in the replayable test sequence according to user instructions, and to synchronously replay the test control commands, test data, and data interaction events within any time segment on the user interface in their original time sequence.

[0054] The integrated test center equipment also supports time-axis scaling and event marking of replayable test sequences during playback to assist users in fault location and test result analysis.

[0055] Therefore, the recording method is upgraded from "result recording" to holographic process recording with replayability, recording complete information in three dimensions: instruction flow, data flow, and interaction events, and supporting synchronous playback in the original time sequence. This makes the testing process completely traceable, which is of great effect on fault location and cause analysis in complex system integration testing.

[0056] In one example Figure 2 This application provides an architectural diagram of a distributed integration testing system, as shown below. Figure 2 As shown, it includes: integrated test center equipment, distributed data communication service, test host of device A, test host of device B, test host of device C, test module of device D, dedicated test cable, device A, device B, device C and device D.

[0057] The integrated test center equipment and various test execution devices (including test hosts and / or test modules) are connected to the communication network via wired or wireless connections to form a data communication network. The integrated test center equipment, test hosts, and test modules uniformly initiate a distributed data communication service (equivalent to a distributed data communication service module). This service is a data-centric communication middleware standard that enables efficient, flexible, and secure data communication between different parts of the system.

[0058] The integration test center equipment, through distributed data communication services, can communicate with all test hosts and test modules, enabling unified management of all test hosts and control of the test hosts to execute relevant device testing functions. Furthermore, for complex systems where device A and device B have connections or dependencies, the data communication service can be used to achieve synchronous testing or integration testing between device A and device B.

[0059] In one example Figure 3 This application provides a schematic diagram of an integrated test of an altimeter, flight control computer, and landing gear, as shown in the image. Figure 3 As shown, a distributed integrated test system is used to connect the altimeter test host, altimeter, flight control test host, flight control computer, landing gear test host, and landing gear test bench.

[0060] For unmanned aerial vehicles (UAVs), radio altimeter data is typically used as the input to the automatic control logic during landing gear retraction and extension tests. For example, during takeoff, when the altimeter height is greater than 200 meters, the flight controller automatically controls the landing gear to retract; during approach and landing, when the altimeter height is less than 300 meters, the flight controller automatically controls the landing gear to extend.

[0061] Traditionally, altimeter testing equipment independently performs altimeter testing, while landing gear testing equipment independently performs landing gear retraction and extension testing. During integrated testing, integration testers control the altimeter testing unit to output altitude data across 200 meters (low to high) and 300 meters (high to low) altitude lines. The data is then processed by the flight control system to control the landing gear retraction and extension, and the landing gear retraction and extension actions are observed and the test results are recorded.

[0062] The altimeter test host, flight control test host, and landing gear test host are improved and connected via a wired network, enabling all three test hosts to support all distributed data communication services of this application. Simultaneously, each test host is improved to respond to control commands from the integrated test center, allowing for unified scheduling and management by the integrated test center equipment, and enabling rapid integration testing of the altimeter, flight control computer, and landing gear system according to the test scenario.

[0063] During testing, the integrated test center equipment sends altitude crossing commands to the altimeter test host via a distributed data communication service. The altimeter test host responds to these commands, outputting altitude data for crossing 200 meters from low to high and 300 meters from high to low. The flight control computer responds to the changes in altimeter altitude data and sends flight control status monitoring data to the flight control test host. Simultaneously, the flight control computer outputs landing gear control commands to the landing gear test bench. The landing gear test bench responds to these control commands and reports the landing gear extension and retraction status back to the landing gear test host. All status and monitoring data are transmitted to the integrated test center equipment via the distributed data communication network.

[0064] By utilizing a distributed integrated testing system, the integrated testing functions of the altimeter, flight control system, and landing gear can be realized. Simultaneously, the time interval from the altitude reading to the moment of altitude change to the moment the landing gear completes its retraction and extension maneuvers can be statistically analyzed, thus clarifying the performance indicators of the UAV's automatic landing gear retraction and extension.

[0065] In one example Figure 4 A schematic diagram of a control surface dynamic characteristic test provided in this application is shown below. Figure 4 As shown, in the dynamic characteristic testing of aircraft control surfaces, the traditional testing method involves installing angular position sensors on each control surface of the aircraft and transmitting the angular position signals via cables connected to the test host. Since the control surfaces are installed at the trailing edges of the left and right wings and the tail, sufficiently long cables are required, and the signal transmission cables need to be arranged appropriately during the test.

[0066] The integrated test center equipment includes a tilt acquisition module, an integrated test host, and a DDS data communication service. The tilt acquisition module is improved to support wireless data transmission, and a wired connection is used to connect the control surface controller test host and the integrated test host. Simultaneously, the distributed data communication service described in this application is integrated into the control surface controller test host and all tilt sensors. This enables data communication between the control surface controller test host, all tilt sensors, and the integrated test center equipment. The integrated test center equipment can synchronously acquire test command data from the control surface controller and angle data acquired by all tilt sensors.

[0067] During the dynamic test of the control surfaces, the control surface controller test host sends control commands from each servo to the control surface controller, and simultaneously publishes the command data to the distributed data communication service. The control surface controller drives each control surface servo, which in turn drives the mechanical linkage to achieve the deflection of each control surface of the aircraft. The deflection of the control surfaces causes each tilt sensor to move. The tilt sensor publishes the control surface tilt angle it has collected to the distributed data communication service.

[0068] The integrated test host connects to the distributed data communication service to synchronously acquire test command data from all control surface controllers and angle data collected by each tilt sensor, thereby enabling analysis of the dynamic response characteristics of the aircraft control surfaces.

[0069] Figure 5 A flowchart illustrating a distributed integration testing method provided in this application is shown below. Figure 5 As shown, this application is applied to an integration test center device, which communicates with multiple test execution devices, and each test execution device is signal-connected to its corresponding object under test; the method includes: Step S101: Based on the acquired test instructions, load the preset cross-device collaborative test cases; generate test control instructions corresponding to each test execution device according to the cross-device collaborative test cases.

[0070] The executing entity in this embodiment can be an integration test center device, a terminal device, a distributed integration test system device or equipment, or other devices or equipment capable of executing this embodiment; there are no limitations on this. This embodiment describes the executing entity as an integration test center device.

[0071] Step S102: Through the data sharing domain, corresponding test control commands are issued to each test execution device. The data sharing domain is established based on the distributed data communication service module deployed on the integration test center device and each test execution device.

[0072] Step S103: Receive test data reported by each test execution device through the data sharing domain; perform correlation analysis on the test data to obtain the integration and collaboration performance indicators between the tested objects.

[0073] Corresponding to the above method, embodiments of this application also provide a distributed integration testing device, such as... Figure 6 As shown, this device is applied to an integration test center, and there is a communication connection between the integration test center and multiple test execution devices. Each test execution device is connected to a corresponding object under test (DUT) via a signal connection. The device includes: The generation module 41 is used to load preset cross-device collaborative test cases based on the acquired test instructions; and generate test control instructions corresponding to each test execution device according to the cross-device collaborative test cases. The distribution module 42 is used to distribute corresponding test control commands to each test execution device through the data sharing domain; the data sharing domain is established based on the distributed data communication service module deployed on the integration test center device and each test execution device. Analysis module 43 is used to receive test data reported by each test execution device through the data sharing domain; perform correlation analysis on the test data to obtain the integration and collaboration performance indicators between the tested objects.

[0074] The functions of each functional unit of the distributed integration testing device provided in the above embodiments of this application can be implemented through the above methods and steps. Therefore, the specific working process and beneficial effects of each unit in the distributed integration testing device provided in the embodiments of this application will not be repeated here.

[0075] This application also provides an integrated testing center device, such as... Figure 7 As shown, it includes a processor 510, a communication interface 520, a memory 530, and a communication bus 540, wherein the processor 510, the communication interface 520, and the memory 530 communicate with each other through the communication bus 540.

[0076] Memory 530 is used to store computer programs; The processor 510 performs the above steps when executing the program stored in the memory 530.

[0077] The communication bus mentioned above can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. This communication bus can be divided into address bus, data bus, control bus, etc. For ease of illustration, only one thick line is used to represent it in the diagram, but this does not mean that there is only one bus or one type of bus.

[0078] The communication interface is used for communication between the aforementioned integrated test center equipment and other equipment.

[0079] The memory may include random access memory (RAM) or non-volatile memory (NVM), such as at least one disk storage device. Optionally, the memory may also be at least one storage device located remotely from the aforementioned processor.

[0080] The processors mentioned above can be general-purpose processors, including central processing units (CPUs), network processors (NPs), etc.; they can also be digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components.

[0081] The implementation methods and beneficial effects of the integrated test center equipment in the above embodiments for solving problems can be found in [reference needed]. Figure 5 The steps in the illustrated embodiments are used to implement the process. Therefore, the specific working process and beneficial effects of the integrated testing center equipment provided in this application will not be repeated here.

[0082] In another embodiment provided in this application, a computer-readable storage medium is also provided, which stores instructions that, when executed on a computer, cause the computer to perform any of the distributed integration testing methods described in the above embodiments.

[0083] In another embodiment provided in this application, a computer program product containing instructions is also provided, which, when run on a computer, causes the computer to execute any of the distributed integration testing methods described in the above embodiments.

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

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

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

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

[0088] Although preferred embodiments have been described in this application, those skilled in the art, upon learning the basic inventive concept, can make other changes and modifications to these embodiments. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments as well as all changes and modifications falling within the scope of the embodiments of this application.

[0089] Obviously, those skilled in the art can make various modifications and variations to the embodiments of this application without departing from the spirit and scope of the embodiments of this application. Therefore, if these modifications and variations to the embodiments of this application fall within the scope of the claims in this application and their equivalents, then this application also intends to include these modifications and variations.

Claims

1. A distributed integration testing system, characterized in that, include: Integrated testing center equipment; Multiple test execution devices are provided, each of which is connected to the object under test; the integrated test center device is communicatively connected to each of the test execution devices. A distributed data communication service module is deployed on the integration test center equipment and each of the test execution equipment, and is used to build a data sharing domain in the system; The integrated testing center equipment is used to schedule at least two test execution devices to synchronously execute test tasks through the data sharing domain according to preset cross-device collaborative test cases; receive test data reported by each test execution device through the data sharing domain; and perform correlation analysis on the test data to obtain the integrated collaborative performance indicators between the tested objects.

2. The system as described in claim 1, characterized in that, The distributed data communication service module is used to construct a data sharing domain in the system based on the data distribution service (DDS); the data sharing domain is a DDS domain. Within the DDS domain, the integrated test center device and each of the test execution devices, as well as the test execution devices themselves, interact with each other through a publish / subscribe model.

3. The system as described in claim 1, characterized in that, The preset cross-device collaborative test cases include triggering conditions and action dependencies; The integrated test center device is used to generate control instructions for starting the cross-device collaborative test cases according to the triggering conditions, issue the control instructions to each relevant test execution device according to the action dependency relationship, and receive test data reported by each relevant test execution device.

4. The system as described in claim 1, characterized in that, The test data includes timestamp information marked by a preset global time base; The integrated test center equipment is used to extract the trigger time and completion time from the test data; the trigger time is the time when the first test execution device performs the first action, or the time when the state of the first tested object reaches a predetermined threshold; the completion time is the time when the second test execution device completes the response action, or the time when the state of the second tested object reaches a predetermined target value. The integrated testing center equipment is used to perform time delay analysis on the completion time and the trigger time to obtain the time interval between the completion time and the trigger time, and use the time interval as the response delay performance index of the integration and collaboration between the first tested object and the second tested object.

5. The system as described in claim 1, characterized in that, The integrated test center equipment is used to send frequency sweep control commands to the test execution equipment through the data sharing domain; The test execution device is used to drive the corresponding connected test object to perform a frequency sweeping action and generate response signal data according to the received frequency sweeping control command; The integrated test center equipment is used to receive response signal data reported by each test execution device through the data sharing domain; the response signal data and the frequency sweep control command are kept synchronized under a preset global time reference; frequency domain dynamic characteristic analysis is performed on the command signal of the frequency sweep control command and the response signal data to obtain the dynamic response characteristics of the object under test.

6. The system as described in claim 1, characterized in that, The integrated test center device stores preset fault injection test cases; the integrated test center device is also used to send fault injection instructions to a designated test execution device through the data sharing domain according to the fault injection test cases; The test execution device is used to apply simulated faults to the corresponding connected object under test according to the received fault injection instruction; The integrated test center equipment is used to receive test data reported by each test execution device under the simulated fault through the data sharing domain, and to perform correlation analysis on the test data based on a preset global time benchmark to obtain the integrated collaborative performance index of the tested object under fault conditions.

7. A distributed integration testing method, characterized in that, The method is applied to an integrated test center device, wherein the integrated test center device and multiple test execution devices are communicatively connected, and each of the test execution devices is signal-connected to a corresponding object under test; the method includes: Based on the acquired test instructions, load the preset cross-device collaborative test cases; and generate test control instructions corresponding to each test execution device according to the cross-device collaborative test cases. Through the data sharing domain, corresponding test control commands are issued to each of the test execution devices; the data sharing domain is established based on the distributed data communication service module deployed on the integration test center device and each of the test execution devices; The test data reported by each of the test execution devices is received through the data sharing domain; the test data is then analyzed to obtain the integration and collaboration performance indicators between the tested objects.

8. A distributed integration testing device, characterized in that, An integrated test center device is used, wherein the integrated test center device and multiple test execution devices are communicatively connected, and each test execution device is signal-connected to a corresponding object under test; the device includes: The generation module is used to load preset cross-device collaborative test cases based on the acquired test instructions; and generate test control instructions corresponding to each test execution device according to the cross-device collaborative test cases. The distribution module is used to distribute the corresponding test control commands to each of the test execution devices through the data sharing domain; the data sharing domain is established based on the distributed data communication service module deployed on the integration test center device and each of the test execution devices. The analysis module is used to receive test data reported by each of the test execution devices through the data sharing domain; and to perform correlation analysis on the test data to obtain the integration and collaboration performance indicators between the tested objects.

9. An integrated testing center device, characterized in that, The integrated testing center equipment includes a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory communicate with each other through the communication bus; Memory, used to store computer programs; A processor, when executing a program stored in memory, implements the method of claim 7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the method of claim 7.