Automatic bus data interface simulation method and system, equipment and storage medium
By generating standardized interface files and running bus data interface simulation software on the partitioned operating system, the time-consuming and labor-intensive problem of traditional testing methods is solved, and the rapid and accurate simulation of the bus data interface of the onboard equipment is achieved, which improves the testing efficiency and reduces the cost.
Patent Information
- Application Number
- CN202411467520.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-10-21
- Publication Date
- 2025-01-07
AI Technical Summary
Traditional airborne equipment testing methods require manual development of bus data interface simulation software, which leads to time-consuming, labor-intensive, and waste of resources, reducing development efficiency.
By generating standardized interface files, automatically compiling and linking, and running bus data interface simulation software on the partitioned operating system, fast and accurate simulation of the bus data interface of the onboard equipment can be achieved.
Improves testing efficiency, reduces testing costs, reduces errors caused by manual encoding, and ensures consistency and accuracy of interface implementation.
Smart Images

Figure CN119271581A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the technical field of embedded operating systems, and in particular to an automatic bus data interface simulation method and system, device, and storage medium. Background Art
[0002] In the field of airborne equipment testing, traditional testing methods often require manual development of a large amount of bus data interface simulation software based on different design requirement documents. However, this testing method is not only time-consuming and labor-intensive, but also easily leads to duplication of work and waste of resources, reducing development efficiency. Summary of the invention
[0003] In view of this, the present application proposes an automatic bus data interface simulation method and system, equipment, and storage medium, which realizes fast and accurate simulation of the bus data interface of airborne equipment through standardized interface files, automatic compilation and linking, and partitioned operating system operation, which not only improves test efficiency but also reduces test costs.
[0004] In a first aspect, the present application provides an automatic bus data interface simulation method, comprising:
[0005] Generate several standard interface files based on the standard interface abstracted from the common test requirements of the airborne equipment;
[0006] Compile and generate corresponding source code files and header files according to the standard interface files, and generate bus data interface simulation software by linking the source code files and header files;
[0007] The bus data interface simulation software is run on the partition operating system, and the corresponding bus data interface simulation test is performed according to the configuration and rules in the standard interface file.
[0008] From the above, the automatic bus data interface simulation method provided by the present application performs abstract processing based on the common interface requirements commonly existing in the test process of airborne equipment, and generates several standard interface files. The generated standard interface files are compiled into corresponding source code files and header files using a compiler tool, and are linked into a complete executable program, namely, bus data interface simulation software, through a linker. By deploying the bus data interface simulation software to the partition operating system and executing the corresponding bus data interface simulation test according to the configuration and rules in the standard interface file, the bus data interface of the airborne equipment can be simulated quickly and accurately, thereby improving the test efficiency and reducing the test cost.
[0009] Optionally, compiling and generating corresponding source code files and header files according to the standard interface file includes:
[0010] The automation script is called through the integrated development environment, the definition in the standard interface file is parsed by the automation script, and the source code file and header file of the C language are automatically generated according to the parsed definition.
[0011] From the above, by calling the automation script in the integrated development environment (IDE), the automation script parses the definition in the standard interface file (such as data type, function prototype, interface rules, etc.), and automatically generates C language source code file (.c) and header file (.h) according to the definition, which not only improves the development efficiency, but also reduces the errors caused by manual coding, ensuring the consistency and accuracy of the interface implementation.
[0012] Optionally, the standard interface file includes at least one of the following:
[0013] Message subscription attribute interface file, data forwarding attribute interface file, verification data forwarding attribute interface file, control command attribute interface file and message publishing attribute interface file.
[0014] Optionally, the bus data interface simulation test includes at least one of the following:
[0015] Message subscription, control command parsing, data forwarding, verification data forwarding, message publishing.
[0016] From the above, the common interface requirements existing in the test process of airborne equipment are abstracted to form a set of standard interface specifications, such as message input / output type, data format, message rate group, data processing mechanism, etc. According to the interface specifications, several standard interface files can be generated, such as message subscription attribute interface file, data forwarding attribute interface file, verification data forwarding attribute interface file, control command attribute interface file and message publishing attribute interface file, etc. Through these several standard interface files, the bus data interface of the airborne equipment can be ensured to be consistent and comparable during testing, thereby reducing the test complexity and error rate caused by interface differences.
[0017] Optionally, the simulation test of the message subscription includes:
[0018] According to the configuration information in the message subscription attribute interface file, the subscribed message is registered in the internal message registration table according to the configuration information, and automatically identified and processed when the matching message arrives; the configuration information includes the channel ID, message type and message format.
[0019] From the above, when executing the message subscription simulation test of the bus data interface in the partition operating system, it is first necessary to parse the configuration information in the message subscription attribute interface file, such as channel ID, message type and message format, etc., and register the subscribed message in the internal message registry according to the parsed configuration information. When a new message is received, it will match the information in the internal message registry according to the attributes such as the channel ID and message type of the message. For messages that are successfully matched, the callback function provided by the subscriber will be called or the corresponding processing logic will be executed, thereby realizing the message subscription simulation test of the bus data interface.
[0020] Optionally, the simulation test of data forwarding includes:
[0021] According to the forwarding rules in the data forwarding attribute interface file, data is read from the source address according to the forwarding rules, and the data is filled in the data packet according to the target address and format requirements, and the generated data packet is sent to the target address; the forwarding rules include the source address, the target address, the data format requirements and the forwarding logic.
[0022] From the above, when executing the data forwarding simulation test of the bus data interface in the partition operating system, it is first necessary to read the data forwarding rules in the data forwarding attribute interface file, and read the data to be forwarded according to the source address in the forwarding rule, and fill in these data in the data packet according to the target address and format requirements, and send the encapsulated data packet to the target address, thereby realizing the data forwarding simulation test of the bus data interface.
[0023] Optionally, the simulation test of the message release includes:
[0024] According to the configuration information in the message publishing attribute interface file, the published message is registered in the internal message publishing table according to the configuration information, and the corresponding message is generated according to the publishing requirements and sent to the designated bus; the configuration information includes the channel ID, message type and message format.
[0025] From the above, when executing the message publishing simulation test of the bus data interface in the partition operating system, it is first necessary to parse the configuration information in the message publishing attribute interface file, and register the published message in the internal message publishing table according to the parsed configuration information. When the publishing demand arrives, the corresponding message can be generated according to the registration information in the internal message publishing table, and the encapsulated message can be sent to the specified bus so that the receiver can receive and process it, thereby realizing the message publishing simulation test of the bus data interface.
[0026] In a second aspect, the present application provides an automatic bus data interface simulation system, comprising:
[0027] The standard interface layer is used to abstract the standard interface based on the common test requirements of the airborne equipment and generate several standard interface files;
[0028] An automated generation tool, used to compile and generate corresponding source code files and header files according to the standard interface files, and to generate bus data interface simulation software by linking the source code files and header files;
[0029] The simulation device is used to run the bus data interface simulation software on the partition operating system and perform the corresponding bus data interface simulation test according to the configuration and rules in the standard interface file.
[0030] In a third aspect, the present application provides a computing device, the computing device comprising:
[0031] processor;
[0032] A memory for storing one or more programs;
[0033] When the one or more programs are executed by the processor, the processor implements the above-mentioned automatic bus data interface simulation method.
[0034] In a fourth aspect, the present application provides a computer-readable storage medium having a computer program stored thereon, which implements the above-mentioned automatic bus data interface simulation method when executed by a computer.
[0035] These and other aspects of the present application will become more apparent from the following description of the embodiment(s). BRIEF DESCRIPTION OF THE DRAWINGS
[0036] Figure 1 A flowchart of a first automatic bus data interface simulation method provided in an embodiment of the present application;
[0037] Figure 2 A flowchart of a second automatic bus data interface simulation method provided in an embodiment of the present application;
[0038] Figure 3 A flowchart of a message subscription initialization process provided in an embodiment of the present application;
[0039] Figure 4 A flowchart of an initialization process for message publishing provided in an embodiment of the present application;
[0040] Figure 5 A flowchart of a data forwarding process provided in an embodiment of the present application;
[0041] Figure 6 A structural diagram of an automatic bus data interface simulation system provided in an embodiment of the present application;
[0042] Figure 7 A structural diagram of a computing device provided in an embodiment of the present application.
[0043] It should be understood that the size and shape of each block diagram in the above structural diagram are for reference only and should not constitute an exclusive interpretation of the embodiments of the present application. The relative positions and inclusion relationships between the blocks presented in the structural diagram are only schematic representations of the structural associations between the blocks, and do not limit the physical connection methods of the embodiments of the present application. DETAILED DESCRIPTION
[0044] The technical solution provided by the present application is further described below with reference to the accompanying drawings and examples. It should be understood that the system structure and business scenarios provided in the examples of the present application are mainly to illustrate the possible implementation methods of the technical solution of the present application and should not be interpreted as the only limitation on the technical solution of the present application. It is known to those of ordinary skill in the art that with the evolution of the system structure and the emergence of new business scenarios, the technical solution provided by the present application is also applicable to similar technical problems.
[0045] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as those commonly understood by those skilled in the art of the present application. In case of any inconsistency, the meaning described in this specification or the meaning derived from the contents recorded in this specification shall prevail. In addition, the terms used herein are only for the purpose of describing the embodiments of the present application and are not intended to limit the present application.
[0046] The embodiment of the present application proposes an automatic bus data interface simulation method and system, which realizes fast and accurate simulation of the bus data interface of airborne equipment through standardized interface files, automatic compilation and linking, and partitioned operating system operation, which not only improves test efficiency but also reduces test costs.
[0047] like Figure 1 As shown, the first automatic bus data interface simulation method proposed in the embodiment of the present application includes:
[0048] S110: Generate a plurality of standard interface files based on the standard interface abstracted from the commonality of the test requirements of the airborne equipment.
[0049] S120: Compile and generate corresponding source code files and header files according to the standard interface files, and generate bus data interface simulation software by linking the source code files and header files.
[0050] S130: running the bus data interface simulation software on the partition operating system, and performing corresponding bus data interface simulation tests according to the configuration and rules in the standard interface file.
[0051] The automatic bus data interface simulation method provided in the embodiment of the present application performs abstract processing based on the common interface requirements commonly existing in the test process of airborne equipment, and generates a number of standard interface files. The generated standard interface files are compiled into corresponding source code files and header files using a compiler tool, and are linked into a complete executable program, namely, bus data interface simulation software, through a linker. The bus data interface simulation software is deployed to a partitioned operating system, and the corresponding bus data interface simulation test is performed according to the configuration and rules in the standard interface file, thereby achieving fast and accurate simulation of the bus data interface of the airborne equipment, improving test efficiency, and reducing test costs.
[0052] like Figure 2 As shown, the second automatic bus data interface simulation method proposed in the embodiment of the present application includes:
[0053] S210: The user modifies the message configuration.
[0054] In this step, the user can modify the message configuration in the configuration table according to the simulation test requirements of the bus data interface of the airborne device, and save the configuration table after the modification is completed. When executing the generation of the standard interface file, the common interface requirements in the configuration table can be abstracted to form a set of standard interface specifications, which include but are not limited to message input / output type, data format, message rate group, data processing mechanism, etc. Based on these specifications, several standard interface files are generated, such as message subscription attribute interface file, data forwarding attribute interface file, verification data forwarding attribute interface file, control command attribute interface file and message publishing attribute interface file.
[0055] The message subscription attribute interface file defines the interface attributes related to message subscription, including the name of the subscription message, the data migration partition of the subscription message, the transmission rate group of the message, the message length, etc. These attributes ensure that the subscriber can receive and process the message from the message publisher according to the predetermined rules.
[0056] The data forwarding attribute interface file defines the interface attributes of data forwarding, including the source address, destination address, forwarding method, data format, and error handling and verification mechanism during the forwarding process. These attributes ensure that data can be transmitted safely and reliably between different systems or modules in a predetermined manner.
[0057] The verification data forwarding attribute interface file defines the interface attributes related to the forwarding of verification data (including heartbeat bit and SVPC check bit), which is mainly used to monitor the heartbeat of the specified message data packet and the complete validity of the message data packet, which helps the tester to view the continuity and correctness of the message data packet on the external device.
[0058] The control command attribute interface file defines the interface attributes of the control command, including the command name, parameter list, execution result feedback mechanism, and command security and effective control authority and management control. These attributes ensure that the control command can be executed in the predetermined command mode.
[0059] The message publishing attribute interface file defines the interface attributes of message publishing, including the published message name, message length, transmission partition number of the published message, transmission rate group of the published message, etc. These attributes ensure that the message can be published to the corresponding receiver in the predetermined manner and time.
[0060] S220: Open the compilation IDE.
[0061] Before executing the generation of source code files and header files, you first need an integrated development environment (IDE) that supports automated script execution and C language development, and the IDE needs to provide sufficient flexibility to integrate custom scripts or plug-ins.
[0062] By writing an automation script, the automation script can parse the definitions in the standard interface file (such as data types, function prototypes, interface rules, etc.), and automatically generate C language source code files and header files according to these definitions. For example, the automation script can be written in Python, Perl, Shell, etc. The written automation script is integrated into the IDE so that the automation script can be called when needed.
[0063] S230: Calling an automated script to generate a source code file (.c) and a header file (.h).
[0064] According to the automation script integrated in the above IDE, when the standard interface file is created or updated, the execution of the automation script is triggered by the graphical interface or shortcut keys of the IDE, and the automation script will read and parse the definition in the standard interface file, and generate the corresponding C language source code file (.c) and header file (.h) according to the definition. Exemplarily, the source code file contains the code logic for implementing the standard interface function, such as the implementation of the interface function, the initialization of the data structure, error handling, etc., and the header file defines the data structure, function prototype, macro definition, etc. of the interface for reference by other modules.
[0065] This embodiment converts the interface specification into executable code, thereby providing a basis for subsequent software simulation, and at the same time improves the readability and maintainability of the code by separating the source code and the header file.
[0066] S240: Link to generate bus data interface simulation software.
[0067] The compiled source code files and header files, as well as other library files that may be required, are linked into a complete executable file, namely the bus data interface simulation software, through a linker to simulate the bus data interface behavior of the airborne device. The linking process resolves the dependencies between code modules to ensure that the software can run normally.
[0068] S250: Fix the bus data interface simulation software into the simulation device.
[0069] The compiled and linked bus data interface simulation software is deployed to the simulation device, in which several partitions can be arranged. The generated several bus data interface simulation software are respectively deployed to different partitions and scheduled and run through the partition operating system.
[0070] S260: The simulation device is reset and running.
[0071] After the deployment of the above bus data interface simulation software is completed, the simulation device can be reset and run, so that the simulation device can run the above bus data interface simulation software deployed in the partition on its partition operating system.
[0072] S270: Execute initialization such as message registration.
[0073] The partition operating system performs the initialization of the bus data interface simulation software according to the configuration and rules in the above standard interface file, and registers the relevant information in the internal registry to facilitate the execution of data subscription, forwarding, publishing and other operations during the simulation test.
[0074] S280: Execute bus data interface simulation test in sequence.
[0075] After completing the above initialization, the bus data interface simulation software deployed in each partition can be run through the partition operating system to perform bus data interface simulation tests, such as message subscription, control command parsing, data forwarding, heartbeat and SVPC forwarding, heartbeat and SVPC filling and message publishing, etc., to achieve various simulation tests on the bus data interface and verify the correctness and stability of the bus data interface.
[0076] Refer to the following Figure 3-Figure 4 , the initialization process such as executing message registration in the above step S270 is described in detail.
[0077] like Figure 3As shown, the initialization process of message subscription in the embodiment of the present application includes: parsing the configuration information in the message subscription attribute interface file, the configuration information including the channel ID, message type and message format, etc., registering the subscribed message type and message format in the internal message registration table according to the channel ID to complete the initialization of the message subscription.
[0078] When a new message is received, it will match the information in the internal message registry based on the message's channel ID, message type and other attributes. For messages that are successfully matched, it will call the callback function provided by the subscriber or execute the corresponding processing logic, thereby realizing the message subscription simulation test of the bus data interface.
[0079] like Figure 4 As shown, the initialization process of message publishing in the embodiment of the present application includes: parsing the configuration information in the message publishing attribute interface file, the configuration information including the channel ID, message type and message format, etc., registering the published message type and message format in the internal message publishing table according to the channel ID to complete the initialization of message publishing.
[0080] When a publishing demand arrives, a corresponding message can be generated according to the registration information in the internal message publishing table, and the encapsulated message can be sent to the specified bus so that the receiver can receive and process it, thereby realizing the message publishing simulation test of the bus data interface.
[0081] like Figure 5 As shown, the data forwarding process of the embodiment of the present application includes: parsing the forwarding rules in the data forwarding attribute interface file, the forwarding rules including the source address, the target address, the data format requirements and the forwarding logic, etc., reading data from the source address according to the forwarding rules, and performing validity calculation and judgment on the verification information in the data (such as pkimFlag). When the validity judgment is passed, the data is filled in the data packet according to the target address and format requirements in the forwarding rules, and the encapsulated data packet is sent to the target address, thereby realizing the data forwarding simulation test of the bus data interface.
[0082] In summary, the automatic bus data interface simulation method provided in the embodiment of the present application performs abstract processing according to the common interface requirements commonly present in the test process of airborne equipment, and generates several standard interface files, and uses a compiler tool to compile the generated standard interface files into corresponding source code files and header files, and links them into a complete executable program, namely, bus data interface simulation software, through a linker, and deploys the bus data interface simulation software to a partition operating system, and performs the corresponding bus data interface simulation test according to the configuration and rules in the standard interface file. The embodiment of the present application reduces the manual coding work of developers and shortens the software development cycle through the automated generation tool, and adopts standardized interface files and configuration files to make the software structure clear, easy to maintain and expand. In addition, the generated simulation software can meet the needs of multiple test scenarios at the same time, improves the flexibility and accuracy of the test, and is of great significance for ensuring the quality and reliability of airborne equipment.
[0083] like Figure 6 As shown, the embodiment of the present application provides an automatic bus data interface simulation system, which can be used to implement the above Figure 1-Figure 5 Any step of an automatic bus data interface simulation method shown and its optional embodiments. Figure 6 As shown, the system includes a standard interface layer 310 , an automatic generation tool 320 and a simulation device 330 .
[0084] The standard interface layer 310 is used to generate several standard interface files based on the standard interface abstracted from the common test requirements of the airborne equipment, including a message subscription attribute interface file, a data forwarding attribute interface file, a verification data forwarding attribute interface file, a control command attribute interface file, and a message publishing attribute interface file.
[0085] The automated generation tool 320 may be an integrated development environment that supports automated script execution and C language development. The integrated development environment is integrated with an automated script that can parse definitions in standard interface files and automatically generate C language source code files and header files based on these definitions. The integrated development environment is also integrated with a linker that links the generated source code files and header files into a complete executable file, namely, bus data interface simulation software, for simulating the bus data interface behavior of airborne equipment.
[0086] The simulation device 330 may include multiple partitions, which are uniformly managed through the partition operating system. By deploying several generated bus data interface simulation software to different partitions respectively and running the bus data interface simulation software through the partition operating system, the bus data interface simulation test of the airborne device can be realized.
[0087] It should be understood that the system or tool in the embodiment of the present application can be implemented by software, for example, it can be implemented by a computer program or instruction having the above functions, and the corresponding computer program or instruction can be stored in a memory inside the terminal, and the processor reads the corresponding computer program or instruction inside the memory to implement the above functions. Alternatively, the system or tool in the embodiment of the present application can also be implemented by hardware. Alternatively, the system or tool in the embodiment of the present application can also be implemented by a combination of a processor and a software module.
[0088] It should be understood that the processing details of the system or tool in the embodiments of the present application can be referred to Figure 1-Figure 5 The related descriptions of the illustrated embodiment and related extended embodiments will not be repeated in the embodiments of the present application.
[0089] Figure 7 5 is a structural diagram of a computing device 500 provided in an embodiment of the present application. The computing device 500 includes: a processor 510 , a memory 520 , a communication interface 530 , and a bus 540 .
[0090] It should be understood that Figure 7 The communication interface 530 in the computing device 500 shown may be used to communicate with other devices.
[0091] The processor 510 may be connected to a memory 520. The memory 520 may be used to store the program code and data. Therefore, the memory 520 may be a storage unit inside the processor 510, or an external storage unit independent of the processor 510, or a component including a storage unit inside the processor 510 and an external storage unit independent of the processor 510.
[0092] Optionally, the computing device 500 may further include a bus 540. The memory 520 and the communication interface 530 may be connected to the processor 510 via the bus 540. The bus 540 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus. The bus 540 may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 7 The fact that only one line is used in the diagram does not mean that there is only one bus or only one type of bus.
[0093] It should be understood that in the embodiment of the present application, the processor 510 may adopt a central processing unit (CPU). The processor may also be other general-purpose processors, digital signal processors (DSP), application specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc. Alternatively, the processor 510 may adopt one or more integrated circuits to execute relevant programs to implement the technical solutions provided in the embodiment of the present application.
[0094] The memory 520 may include a read-only memory and a random access memory, and provides instructions and data to the processor 510. A portion of the processor 510 may also include a nonvolatile random access memory. For example, the processor 510 may also store information on the device type.
[0095] When the computing device 500 is running, the processor 510 executes the computer-executable instructions in the memory 520 to perform the operating steps of the above method.
[0096] It should be understood that the computing device 500 according to the embodiment of the present application can correspond to the corresponding subjects in the methods according to the embodiments of the present application, and the above-mentioned other operations and / or functions of each module in the computing device 500 are respectively for realizing the corresponding processes of each method of the present embodiment. For the sake of brevity, they will not be repeated here.
[0097] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.
[0098] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.
[0099] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.
[0100] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
[0101] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
[0102] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application can be essentially or partly embodied in the form of a software product that contributes to the prior art. The computer software product is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.
[0103] An embodiment of the present application also provides a computer-readable storage medium on which a computer program is stored. When the program is executed by a processor, it is used to execute the above method, which includes at least one of the solutions described in the above embodiments.
[0104] The computer storage medium of the embodiment of the present application can adopt any combination of one or more computer-readable media. Computer-readable media can be computer-readable signal media or computer-readable storage media. Computer-readable storage media can be, for example, but not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices or devices, or any combination of the above. More specific examples (non-exhaustive lists) of computer-readable storage media include: electrical connections with one or more wires, portable computer disks, hard disks, random access memories (RAM), read-only memories (ROM), erasable programmable read-only memories (EPROM or flash memory), optical fibers, portable compact disk read-only memories (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the above. In this document, computer-readable storage media can be any tangible medium containing or storing programs, which can be used by instruction execution systems, devices or devices or used in combination with them.
[0105] Computer-readable signal media may include data signals propagated in baseband or as part of a carrier wave, which carry computer-readable program code. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Computer-readable signal media may also be any computer-readable medium other than a computer-readable storage medium, which may send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device.
[0106] The program code embodied on the computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
[0107] Computer program code for performing the operation of the present application can be written in one or more programming languages or a combination thereof, including object-oriented programming languages, such as Java, Smalltalk, C++, and conventional procedural programming languages, such as "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as an independent software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer can be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computer (e.g., using an Internet service provider to connect through the Internet).
[0108] It should be noted that the embodiments described in the present application are only a part of the embodiments of the present application, rather than all the embodiments. The components of the embodiments of the present application usually described and shown in the drawings can be arranged and designed in various different configurations. Therefore, the above detailed description of the embodiments of the present application provided in the drawings is not intended to limit the scope of the application claimed for protection, but merely represents the selected embodiments of the present application. Based on the embodiments of the present application, all other embodiments obtained by those skilled in the art without making creative work belong to the scope of protection of the present application.
[0109] The words "first, second, third, etc." or module A, module B, module C and other similar terms in the specification and claims are only used to distinguish similar objects and do not represent a specific ordering of the objects. It is understandable that the specific order or sequence can be interchanged where permitted so that the embodiments of the present application described herein can be implemented in an order other than that illustrated or described herein.
[0110] In the above description, the numbers representing the steps involved do not necessarily mean that the steps will be executed. Intermediate steps may be included or replaced by other steps. The order of the previous and next steps may be interchanged or executed simultaneously if permitted.
[0111] The term "comprising" as used in the description and claims should not be interpreted as being limited to what is listed thereafter; it does not exclude other elements or steps. Therefore, it should be interpreted as specifying the presence of the features, integers, steps or components mentioned, but does not exclude the presence or addition of one or more other features, integers, steps or components and groups thereof. Therefore, the expression "a device comprising means A and B" should not be limited to a device consisting of components A and B only.
[0112] The "one embodiment" or "embodiment" mentioned in this specification means that the specific features, structures or characteristics described in conjunction with the embodiment are included in at least one embodiment of the present application. Therefore, the terms "in one embodiment" or "in an embodiment" appearing in various places in this specification do not necessarily refer to the same embodiment, but may refer to the same embodiment. In addition, in the various embodiments of the present application, if there is no special explanation and logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced to each other, and the technical features in different embodiments can be combined to form a new embodiment according to their inherent logical relationship.
[0113] Note that the above are only preferred embodiments of the present application and the technical principles used. Those skilled in the art will understand that the present invention is not limited to the specific embodiments described herein, and that various obvious changes, readjustments and substitutions can be made by those skilled in the art without departing from the scope of protection of the present invention. Therefore, although the present application is described in more detail through the above embodiments, the present invention is not limited to the above embodiments, and may also include more other equivalent embodiments without departing from the concept of the present invention, all of which belong to the protection scope of the present invention.
Claims
1. An automatic bus data interface simulation method, characterized in that: include: Generate several standard interface files based on the standard interface abstracted from the common test requirements of the airborne equipment; Compile and generate corresponding source code files and header files according to the standard interface files, and generate bus data interface simulation software by linking the source code files and header files; The bus data interface simulation software is run on the partition operating system, and the corresponding bus data interface simulation test is performed according to the configuration and rules in the standard interface file.
2. The method according to claim 1, characterized in that The compiling and generating corresponding source code files and header files according to the standard interface files includes: The automation script is called through the integrated development environment, the definition in the standard interface file is parsed by the automation script, and the source code file and header file of the C language are automatically generated according to the parsed definition.
3. The method according to claim 1, characterized in that The standard interface file includes at least one of the following: Message subscription attribute interface file, data forwarding attribute interface file, verification data forwarding attribute interface file, control command attribute interface file and message publishing attribute interface file.
4. The method according to claim 3, characterized in that The bus data interface simulation test includes at least one of the following: Message subscription, control command parsing, data forwarding, verification data forwarding, message publishing.
5. The method according to claim 4, characterized in that The simulation test of the message subscription includes: According to the configuration information in the message subscription attribute interface file, the subscribed message is registered in the internal message registration table according to the configuration information, and automatically identified and processed when the matching message arrives; the configuration information includes the channel ID, message type and message format.
6. The method according to claim 4, characterized in that The simulation test of data forwarding includes: According to the forwarding rules in the data forwarding attribute interface file, data is read from the source address according to the forwarding rules, and the data is filled in the data packet according to the target address and format requirements, and the generated data packet is sent to the target address; the forwarding rules include the source address, the target address, the data format requirements and the forwarding logic.
7. The method according to claim 4, characterized in that The simulation test of the message release includes: According to the configuration information in the message publishing attribute interface file, the published message is registered in the internal message publishing table according to the configuration information, and the corresponding message is generated according to the publishing requirements and sent to the designated bus; the configuration information includes the channel ID, message type and message format.
8. An automatic bus data interface simulation system, characterized in that: include: The standard interface layer is used to abstract the standard interface based on the common test requirements of the airborne equipment and generate several standard interface files; An automated generation tool, used to compile and generate corresponding source code files and header files according to the standard interface files, and to generate bus data interface simulation software by linking the source code files and header files; The simulation device is used to run the bus data interface simulation software on the partition operating system and perform the corresponding bus data interface simulation test according to the configuration and rules in the standard interface file.
9. A computing device, characterized in that include: processor; A memory for storing one or more programs; When the one or more programs are executed by the processor, the processor implements an automatic bus data interface simulation method as described in any one of claims 1 to 7.
10. A computer-readable storage medium, characterized in that: A computer program is stored thereon, and when the computer program is executed by a computer, an automatic bus data interface simulation method as described in any one of claims 1 to 7 is implemented.
Citation Information
Cited By
Airborne high-speed bus test system
CN120186066A
Beidou communication software development cross-platform adaptation method and system
CN120892087A