An interactive cabin management terminal testing system and testing method

Abstract

The present application relates to the field of aircraft cabin electronic system maintenance support and testing, and provides an interactive cabin management terminal testing system and testing method. A testing control terminal module generates task records, link records, comparison records, instruction records, observation records, index records, report records and evidence storage index records, performs interface self-checking, calculates device digest values based on software version identification and configuration identification set and compares them with baseline digest values, issues instructions according to use cases and collects BITE, screenshots, voltage and current measurement data and audio measurement data, obtains compliance rules by combining rule versions, generates compliance conclusions and calculates evidence storage digest values to output indexes. The present application can realize multi-source data closed loop, rule determination reviewable and result traceable evidence storage.

Description

Technical Field

[0001] This invention relates to the field of maintenance, support and testing of aircraft cabin electronic systems, specifically an interactive cabin management terminal testing system and testing method. Background Technology

[0002] The cabin management terminal is used for centralized control and status display of cabin lighting, entertainment, broadcasting, alarms, and other functions. After maintenance operations such as component replacement, software rewriting, or parameter reset, it is usually necessary to verify whether the software version and configuration are consistent with the baseline, and further verify whether the operation under conditions such as power fluctuations and video anomalies meets compliance requirements. Existing solutions often rely on manual verification of version numbers or sampling tests, which has problems such as incomplete verification evidence chains, insufficient data dimensions, and poor verifiability of conclusions. Summary of the Invention

[0003] The purpose of this invention is to provide a technical solution to address the technical problems existing in the prior art. Specifically, this invention is achieved through the following technical solution: A testing method for an interactive cabin management terminal includes the following steps: Step 1: The test control terminal module receives task configuration data and generates a task record containing the device under test identifier, baseline summary value, test case set identifier, interface mapping parameters, rule version, power supply parameters, video parameters, and session parameters. Step 2: Write power supply parameters to the power supply unit, video parameters to the video generation unit, and session parameters to the switching unit. Control the interface adapter to perform interface self-test according to the interface mapping parameters to generate link records. Write the link records to the measurement unit connection identifier and the audio test unit connection identifier. Step 3: Based on the link record, the power supply unit is triggered to supply power and the switching unit is triggered to establish a session. The software version identifier and configuration identifier set are obtained, and the device digest value is calculated based on the software version identifier and configuration identifier set. The device digest value is compared with the baseline digest value to generate a comparison record and write the comparison identifier. Step 4: Generate an instruction record containing instruction frames and instruction enable identifiers based on the use case set identifier and the comparison identifier; Step 5: Based on the instruction record, issue instruction frames according to the instruction enable flag to generate a transmission timestamp, receive BITE data from the device under test to generate a reception timestamp, collect display data output from the display interface, and receive voltage and current data output from the measurement unit and audio measurement data output from the audio test unit to generate an observation record containing comparison flag, transmission timestamp, reception timestamp, BITE data, display data, voltage and current data, and audio measurement data. Step 6: Obtain compliance rules from the compliance rule library based on the rule version; extract indicator values ​​from the observation records and compare them with the compliance rule judgment conditions to generate indicator records; generate report records containing compliance conclusions based on the indicator records; and calculate the evidence storage summary value based on the report records, observation records, and rule versions to generate evidence storage index records containing evidence storage summary values.

[0004] Furthermore, the baseline digest value, device digest value, and evidence digest value are calculated using the SHA-256 digest algorithm.

[0005] Furthermore, the control interface adapter performs interface self-test and generates link records according to the interface mapping parameters, including: Based on the interface mapping parameters, perform Ethernet link connectivity verification to obtain the network link identifier, perform RS-232 link communication verification to obtain the serial link identifier, and perform parameter write consistency verification to obtain the write verification identifier. The link record also writes the network link identifier, serial link identifier, and write verification identifier.

[0006] Furthermore, the video parameters include a fault mode identifier, which is used to indicate that the video generation unit outputs a fault video signal.

[0007] Furthermore, the power supply parameters include voltage sag parameters and voltage surge parameters, which are used to indicate the output power supply voltage waveform of the power supply unit.

[0008] Furthermore, if the device summary value is the same as the baseline summary value, the comparison is identified as passed and the instruction enable flag is identified as enabled; if the device summary value is different from the baseline summary value, the comparison is identified as failed and the instruction enable flag is identified as disabled.

[0009] Furthermore, the BITE data is the built-in test output data of the device under test.

[0010] Furthermore, the displayed data is screenshot data.

[0011] Furthermore, the audio measurement data includes spectrum data, total harmonic distortion data, and alarm frequency data.

[0012] An interactive cabin management terminal testing system is provided for executing any of the interactive cabin management terminal testing methods described above, comprising: a test control terminal module, a power supply unit, a video generation unit, a switching unit, a measurement unit, an audio testing unit, an interface adapter, a compliance rule base, and a communication unit; The power supply unit, video generation unit, switching unit, measurement unit, audio testing unit, interface adapter, and communication unit are all connected to the test control terminal module; the compliance rule base is communicatively connected to the communication unit. The power supply unit is used to supply power to the device under test and output a power supply voltage waveform; The video generation unit is used to output a video signal based on video parameters; The aforementioned switching unit is used to establish a session and carry out instruction frame transmission; The aforementioned measuring unit is used to output voltage and current data; The audio testing unit is used to output audio measurement data; The interface adapter is used to map the interfaces between the device under test and the power supply unit, video generation unit, switching unit, measurement unit, and audio testing unit according to the interface mapping parameters. The aforementioned compliance rule library is used to provide compliance rule data.

[0013] Compared with the prior art, the present invention has the following advantages and beneficial effects: By linking summary comparison with multidimensional observation in a closed loop, the reliability of post-maintenance configuration consistency verification is improved; by using rule version-bound indicator judgment and evidence summary value output, the traceability and verifiability of verification results are improved. Attached Figure Description

[0014] The accompanying drawings, which are included to provide a further understanding of embodiments of the invention and form part of this application, do not constitute a limitation thereof. In the drawings: Figure 1 This is a flowchart illustrating a testing method for an interactive cabin management terminal. Detailed Implementation

[0015] To make the objectives, technical solutions, and advantages of this invention clearer, the invention will be further described in detail below with reference to embodiments and accompanying drawings. The illustrative embodiments and descriptions of this invention are for illustrative purposes only and are not intended to limit the invention. It should be noted that this invention is already in the actual research and development stage.

[0016] Example 1 like Figure 1 As shown, a testing method for an interactive cabin management terminal includes the following steps: Step 1: The test control terminal module receives task configuration data and generates a task record containing the device under test identifier, baseline summary value, test case set identifier, interface mapping parameters, rule version, power supply parameters, video parameters, and session parameters. Step 2: Write power supply parameters to the power supply unit, video parameters to the video generation unit, and session parameters to the switching unit. Control the interface adapter to perform interface self-test according to the interface mapping parameters to generate link records. Write the link records to the measurement unit connection identifier and the audio test unit connection identifier. Step 3: Based on the link record, the power supply unit is triggered to supply power and the switching unit is triggered to establish a session. The software version identifier and configuration identifier set are obtained, and the device digest value is calculated based on the software version identifier and configuration identifier set. The device digest value is compared with the baseline digest value to generate a comparison record and write the comparison identifier. Step 4: Generate an instruction record containing instruction frames and instruction enable identifiers based on the use case set identifier and the comparison identifier; Step 5: Based on the instruction record, issue instruction frames according to the instruction enable flag to generate a transmission timestamp, receive BITE data from the device under test to generate a reception timestamp, collect display data output from the display interface, and receive voltage and current data output from the measurement unit and audio measurement data output from the audio test unit to generate an observation record containing comparison flag, transmission timestamp, reception timestamp, BITE data, display data, voltage and current data, and audio measurement data. Step 6: Obtain compliance rules from the compliance rule library based on the rule version; extract indicator values ​​from the observation records and compare them with the compliance rule judgment conditions to generate indicator records; generate report records containing compliance conclusions based on the indicator records; and calculate the evidence storage summary value based on the report records, observation records, and rule versions to generate evidence storage index records containing evidence storage summary values.

[0017] Specifically, the task configuration data should include at least: the device under test identifier, baseline summary value, test case set identifier, interface mapping parameters, rule version, power supply parameters, video parameters, and session parameters.

[0018] The test control terminal module stores structured data as records, which can be local database table entries, log entries, or message objects.

[0019] The test control terminal module receives task configuration data, generates task records, and writes the device under test identifier, baseline summary value, test case set identifier, interface mapping parameters, rule version, power supply parameters, video parameters, and session parameters.

[0020] The test control terminal module writes power supply parameters to the power supply unit, video parameters to the video generation unit, and session parameters to the switching unit.

[0021] The test control terminal module controls the interface adapter to perform interface self-test and generate link records according to the interface mapping parameters. The link records are written to the measurement unit connection identifier and the audio test unit connection identifier.

[0022] The example of determining the connection path for the measurement unit connection identifier and the audio test unit connection identifier is as follows: The interface adapter performs port enumeration and handshake requests for the ports indicated by the interface mapping parameters; receives the handshake response of the corresponding peripheral and parses it to obtain the peripheral type identifier and port status; encapsulates "peripheral type identifier + port identifier + handshake status" into a connection identifier and writes it into the link record.

[0023] Optionally, the interface self-test also includes: Ethernet link connectivity verification, RS-232 link communication verification, parameter write consistency verification, obtaining network link identifier, serial link identifier, write verification identifier and writing to the link record.

[0024] The test control terminal module triggers the power supply unit to supply power and triggers the switching unit to establish a session based on the link record, and obtains the software version identifier and configuration identifier set from the device under test. The test control terminal module calculates the device digest value based on the software version identifier and configuration identifier set, compares the device digest value with the baseline digest value, generates a comparison record, and writes it into the comparison identifier.

[0025] One executable calculation method for device summary values ​​is: Among them, the software version identifier is the version string or version code read from the device under test; the configuration identifier set is the set of configuration entry identifiers read from the device under test; Sort() means sorting in lexicographical order; Join() means concatenating according to a fixed delimiter; SHA256() means SHA-256 digest algorithm; Indicates splicing.

[0026] The test control terminal module generates instruction records based on test case set identifiers and comparison identifiers. Each instruction record contains instruction frames and instruction enable identifiers. The instruction enable identifier can be used as a field in the instruction frame. The test control terminal module assembles the frame according to this field and sends it. The enable status is reflected in the execution strategy of the device under test (DUT) for the instruction frame.

[0027] Optionally, during the framing stage, the test control terminal module enables the instruction frame based on the instruction enable flag and writes the instruction enable flag into the instruction frame to instruct the device under test to perform or disable the corresponding action of the instruction frame.

[0028] The test control terminal module issues command frames and generates a transmission timestamp based on the command record and the command enable flag; the test control terminal module receives BITE data from the device under test and generates a reception timestamp; the test control terminal module collects display data output from the display interface and receives voltage and current data output from the measurement unit and audio measurement data output from the audio test unit, generates observation records and writes comparison flags, transmission timestamps, reception timestamps, BITE data, display data, voltage and current data, and audio measurement data.

[0029] Among them: BITE data is the built-in test output data of the device under test, which may include alarm codes, fault bitmaps and key module status words; The displayed data is screenshot data. An example of the acquisition path is: the test control terminal module captures the video stream frames from the display output port through the display interface acquisition module, or captures and encapsulates the frame buffer image data of the device under test into a screenshot. Voltage and current data can be either a sampling sequence or a set of statistical values; Audio measurement data includes spectrum data, total harmonic distortion data, and alarm frequency data.

[0030] The test control terminal module retrieves compliance rules from the compliance rule library based on the rule version. An example data structure for a compliance rule is as follows: rule identifier; indicator identifier; judgment condition, which includes a comparison operator and a comparison object; the comparison object is one of a threshold, an allowed set, or a pattern matching template; and a conclusion mapping, used to map the judgment result to a compliance / non-compliance identifier.

[0031] Among them, the comparison operator is used to limit the judgment relationship between the indicator value and the comparison object. The comparison object is the threshold, interval endpoint, allowed set or template identifier that is matched with the comparison operator. When generating indicator records, the test control terminal module extracts the corresponding indicator value from the self-observation record based on the indicator identifier, and performs a comparison between the indicator value and the comparison object according to the comparison operator to obtain the judgment result identifier. Then, it generates a compliance conclusion based on the conclusion mapping. Examples of comparison operators include greater than, greater than or equal to, less than, less than or equal to, equal to, not equal to, interval fall into, set containment and template matching, so that the judgment caliber under the same rule version is reproducible and traceable.

[0032] The test control terminal module extracts indicator values ​​from observation records and generates indicator records by comparing them with compliance rules and judgment conditions. One example of the data structure for an indicator record is: indicator identifier; indicator value; judgment result identifier.

[0033] Examples of indicator value extraction include: extracting the minimum voltage, maximum voltage, and peak current from voltage and current data as indicator values; extracting total harmonic distortion data and alarm frequency data from audio measurement data as indicator values; extracting alarm codes from BITE data as indicator values; and extracting screenshot summaries or template matching results from screenshot data as indicator values.

[0034] The test control terminal module generates a report record containing compliance conclusions based on the indicator records. The report record must at least contain compliance conclusions, and may optionally include a list of non-compliant indicator identifiers and a summary of key evidence.

[0035] The test control terminal module calculates the evidence summary value based on report records, observation records, and rule versions, generates an evidence index record, and writes it into the evidence summary value. To ensure verifiability, the input objects for the evidence summary value adopt deterministic serialization rules: report records and observation records are output in a fixed field order; list fields are output according to a fixed sorting rule; UTF-8 encoding and a fixed delimiter are used uniformly; and the rule version is used as a fixed field in the concatenation.

[0036] One executable calculation method for the evidence digest value is: Where Serialize() is the deterministic serialization rule mentioned above; SHA256() is the SHA-256 digest algorithm.

[0037] Example 2 The system includes a test control terminal module, a power supply unit, a video generation unit, a switching unit, a measurement unit, an audio test unit, an interface adapter, a compliance rule base, and a communication unit.

[0038] The test control terminal module establishes interface mapping connections with the power supply unit, video generation unit, measurement unit, and audio test unit through the interface adapter, and establishes a session with the device under test through the switching unit to carry command frame transmission; the physical communication media between the interface adapter and the switching unit include Ethernet links and RS-232 links.

[0039] The test control terminal module is used to execute the functions corresponding to each step in Embodiment 1, including: generating task records, controlling the interface adapter to perform interface self-test to generate link records, establishing a session and obtaining software version identifier and configuration identifier set, calculating device summary value and comparing baseline summary value to generate comparison records, generating instruction records and issuing instruction frames and generating timestamps, receiving BITE data and collecting screenshots, receiving voltage and current data and audio measurement data to generate observation records, obtaining compliance rules and generating indicator records and report records, and calculating evidence storage summary value to generate evidence storage index records.

[0040] The aforementioned test control terminal module adopts an embedded ARM multi-core processor hardware platform, integrates a 2.5GbE Ethernet interface and an RS-232 serial interface, and runs the Ubuntu 22.04 LTS operating system and Python 3.10 test control software.

[0041] The embedded ARM multi-core processor hardware platform is ROCK5B, equipped with a Rockchip RK3588 processor, including 4 × Cortex-A76@2.4GHz and 4 × Cortex-A55@1.8GHz, 8nm process technology, and integrated Mali-G610 MP4 GPU. It features a 6TOPS NPU and supports up to 16GB of LPDDR4X / LPDDR5 memory and NVMe PCIe 3.0×4 solid-state drive expansion.

[0042] The test control terminal module uses NPU to accelerate real-time image recognition and analysis of video display data, which is used to automatically determine display anomalies in screenshots.

[0043] The remaining units are used to output power supply voltage waveforms, output video signals, carry session and command frame transmission, output voltage and current data, output audio measurement data, and provide compliance rules, respectively.

[0044] Example 3 Based on Example 1, the compliance rule base performs deterministic serialization on the rule set corresponding to the rule version and calculates the rule set fingerprint value. The test control terminal module writes the rule set fingerprint value into the report record and incorporates the rule set fingerprint value into the evidence storage digest value input object to enhance the binding strength of the evidence storage digest value to the rule content.

[0045] Example 4 Based on Example 1, the test control terminal module performs consistency verification on BITE data, screenshot data, voltage and current data, and audio measurement data before generating indicator records, and generates consistency verification results. When the consistency verification results indicate a conflict, the test control terminal module generates anomaly attribution information and writes it into the report record, so that the report record outputs the attribution information corresponding to the non-compliant items while outputting the compliance conclusion. The evidence summary value is still calculated based on the report record, observation record, and rule version.

[0046] Example 5 The test control terminal uses the ROCK5B industrial-grade development board instead of the traditional Raspberry Pi platform. This hardware platform is equipped with a Rockchip RK3588 processor, built on an 8nm advanced process, and integrates a big.LITTLE architecture with four Cortex-A76 cores (2.4GHz) and four Cortex-A55 cores (1.8GHz). Compared to the Raspberry Pi 4B's Cortex-A72 architecture, multi-core performance is improved by approximately 100%, and single-core performance by approximately 60%. The platform integrates a 6TOPS NPU, supporting real-time image recognition during testing and automatically identifying SVDU screen display anomalies (screen flickering, black screen, color distortion, etc.), replacing manual visual inspection and further improving testing efficiency.

[0047] In terms of storage, the ROCK5B supports NVMe PCIe 3.0 x4 solid-state drive expansion, with sequential read and write speeds reaching up to 3500MB / s, a 35-fold improvement over the Raspberry Pi 4B's MicroSD card (approximately 100MB / s), meeting the real-time storage needs of high-resolution video test data (4K@60fps, approximately 12Gbps bitrate). The network interface has been upgraded to 2.5GbE, with a theoretical transmission rate of 2500Mbps, 25 times that of 100Mbps Ethernet, supporting the bandwidth requirements of multi-channel parallel testing or future 8K video testing.

[0048] The operating system uses Ubuntu 22.04 LTS Long Term Support version, and the Python environment has been upgraded to version 3.10. It maintains API compatibility with the original test control software, while supporting more modern asynchronous programming features (async / await) to improve the response performance of multi-device concurrent testing.

[0049] The specific embodiments described above further illustrate the purpose, technical solution, and beneficial effects of the present invention. It should be understood that the above description is only a specific embodiment of the present invention and is not intended to limit the scope of protection of the present invention. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the scope of protection of the present invention.

Claims

1. A testing method for an interactive cabin management terminal, characterized in that, Includes the following steps: Step 1: The test control terminal module receives task configuration data and generates a task record containing the device under test identifier, baseline summary value, test case set identifier, interface mapping parameters, rule version, power supply parameters, video parameters, and session parameters. Step 2: Write power supply parameters to the power supply unit, video parameters to the video generation unit, and session parameters to the switching unit. Control the interface adapter to perform interface self-test according to the interface mapping parameters to generate link records. Write the link records to the measurement unit connection identifier and the audio test unit connection identifier. Step 3: Based on the link record, the power supply unit is triggered to supply power and the switching unit is triggered to establish a session. The software version identifier and configuration identifier set are obtained, and the device digest value is calculated based on the software version identifier and configuration identifier set. The device digest value is compared with the baseline digest value to generate a comparison record and write the comparison identifier. Step 4: Generate an instruction record containing instruction frames and instruction enable identifiers based on the use case set identifier and the comparison identifier; Step 5: Based on the instruction record, issue instruction frames according to the instruction enable flag to generate a transmission timestamp, receive BITE data from the device under test to generate a reception timestamp, collect display data output from the display interface, and receive voltage and current data output from the measurement unit and audio measurement data output from the audio test unit to generate an observation record containing comparison flag, transmission timestamp, reception timestamp, BITE data, display data, voltage and current data, and audio measurement data. Step 6: Obtain compliance rules from the compliance rule library based on the rule version; extract indicator values ​​from the observation records and compare them with the compliance rule judgment conditions to generate indicator records; generate report records containing compliance conclusions based on the indicator records; and calculate the evidence storage summary value based on the report records, observation records, and rule versions to generate evidence storage index records containing evidence storage summary values.

2. The interactive cabin management terminal testing method according to claim 1, characterized in that, The baseline digest value, device digest value, and evidence digest value are calculated using the SHA-256 digest algorithm.

3. The interactive cabin management terminal testing method according to claim 1, characterized in that, The control interface adapter performs interface self-test and generates link records according to the interface mapping parameters, including: Based on the interface mapping parameters, perform Ethernet link connectivity verification to obtain the network link identifier, perform RS-232 link communication verification to obtain the serial link identifier, and perform parameter write consistency verification to obtain the write verification identifier. The link record also writes the network link identifier, serial link identifier, and write verification identifier.

4. The interactive cabin management terminal testing method according to claim 1, characterized in that, The video parameters include a fault mode identifier, which is used to indicate that the video generation unit outputs a fault video signal.

5. The interactive cabin management terminal testing method according to claim 1, characterized in that, The power supply parameters include voltage sag parameters and voltage surge parameters, which are used to indicate the output power supply voltage waveform of the power supply unit.

6. The interactive cabin management terminal testing method according to claim 1, characterized in that, If the device summary value is the same as the baseline summary value, the comparison is marked as passed and the instruction enable value is marked as enabled. If the device summary value is different from the baseline summary value, the comparison is marked as failed and the instruction enable value is marked as disabled.

7. The interactive cabin management terminal testing method according to claim 1, characterized in that, The BITE data is the built-in test output data of the device under test.

8. The interactive cabin management terminal testing method according to claim 1, characterized in that, The displayed data is screenshot data.

9. The interactive cabin management terminal testing method according to claim 1, characterized in that, The audio measurement data includes spectrum data, total harmonic distortion data, and alarm frequency data.

10. An interactive cabin management terminal testing system, characterized in that, The method for performing an interactive cabin management terminal test according to any one of claims 1-9 includes: a test control terminal module, a power supply unit, a video generation unit, a switching unit, a measurement unit, an audio test unit, an interface adapter, a compliance rule base, and a communication unit; The power supply unit, video generation unit, switching unit, measurement unit, audio testing unit, interface adapter, and communication unit are all connected to the test control terminal module; the compliance rule base is communicatively connected to the communication unit. The power supply unit is used to supply power to the device under test and output a power supply voltage waveform; The video generation unit is used to output a video signal based on video parameters; The aforementioned switching unit is used to establish a session and carry out instruction frame transmission; The aforementioned measuring unit is used to output voltage and current data; The audio testing unit is used to output audio measurement data; The interface adapter is used to map the interfaces between the device under test and the power supply unit, video generation unit, switching unit, measurement unit, and audio testing unit according to the interface mapping parameters. The aforementioned compliance rule library is used to provide compliance rule data.

Images