System, method and apparatus for generating integrated modular architecture model

Abstract

The present application discloses systems, methods, apparatus, and articles for generating an integrated modular architecture (IMA) model. An example apparatus includes: an interface importer for importing a first IMA protocol definition into a computer modeling environment to generate a library and generate IMA model objects; a model object handler for importing some of the IMA model objects into the computer modeling environment to generate a first IMA model of an aircraft system corresponding to the aircraft, and generating an IMA system model corresponding to the aircraft by generating multiple IMA models including the first IMA model. The example apparatus also includes an interface validator for validating the IMA system model by comparing the output of the IMA system model with the validation output; an interface exporter for generating manufacturing build instructions for the aircraft system when the IMA system model is validated; and a report generator for initiating production of the aircraft system.

Description

Technical Field

[0001] The present disclosure relates generally to aircraft, and more particularly, to systems, methods, and apparatus for generating an integrated modular architectural model. Background Art

[0002] In recent years, typical aircraft systems have become increasingly integrated to improve monitoring and operation of aircraft systems. Managing interfaces between aircraft systems has become increasingly complex. Cost increases may occur as aircraft systems are redesigned to improve integration inefficiencies discovered during the manufacture and assembly of aircraft systems. Computer-generated models may be used to evaluate the effectiveness of aircraft system designs prior to release for manufacturing. Summary of the invention

[0003] Systems, methods, apparatus, and articles for generating an integrated modular architecture (IMA) model are disclosed. An example apparatus includes an interface importer for importing a first IMA protocol definition into a first computer modeling environment to generate a plurality of libraries based on the first IMA protocol definition and a plurality of IMA model objects based on the plurality of libraries; a model object handler for importing some of the plurality of IMA model objects into the first computer modeling environment to generate a first IMA model of an aircraft system corresponding to the aircraft, and generating an IMA system model corresponding to the aircraft by generating a plurality of IMA models including the first IMA model. The example apparatus also includes an interface validator for validating the IMA system model by comparing an output of the IMA system model with a validation output; an interface exporter for generating manufacturing build instructions for the aircraft system when the IMA system model is validated; and a report generator for initiating production of the aircraft system based on the manufacturing build instructions.

[0004] An example computer-implemented method includes importing a first integrated modular architecture (IMA) protocol definition into a first computer modeling environment to generate a plurality of libraries based on the first IMA protocol definition, generating a plurality of IMA model objects based on the plurality of libraries, importing some of the plurality of IMA model objects into the first computer modeling environment to generate a first IMA model of an aircraft system corresponding to the aircraft, generating an IMA system model corresponding to the aircraft by generating a plurality of IMA models including the first IMA model, validating the IMA system model by comparing outputs of the IMA system model to validation outputs, generating manufacturing build instructions for the aircraft system in response to validating the IMA system model based on the comparison, and initiating production of the aircraft system based on the manufacturing build instructions.

[0005] An example non-transitory computer-readable storage medium includes instructions that, when executed, cause a machine to at least import a first integrated modular architecture (IMA) protocol definition into a first computer modeling environment to generate a plurality of libraries based on the first IMA protocol definition, generate a plurality of IMA model objects based on the plurality of libraries, import some of the plurality of IMA model objects into the first computer modeling environment to generate a first IMA model of an aircraft system corresponding to the aircraft, generate an IMA system model corresponding to the aircraft by generating a plurality of IMA models including the first IMA model, validate the IMA system model by comparing outputs of the IMA system model to validation outputs, generate manufacturing build instructions for the aircraft system when the IMA system model is validated based on the comparison, and initiate production of the aircraft system based on the manufacturing build instructions. BRIEF DESCRIPTION OF THE DRAWINGS

[0006] Figure 1 An example system workflow is depicted for generating a plurality of example aircraft system models associated with an example aircraft using an integrated modular architecture (IMA).

[0007] Figure 2 It is used for communication coupling Figure 1 Schematic diagram of an example aircraft network of example aircraft control hardware for an aircraft.

[0008] Figure 3 Depicted are example line replaceable unit (LRU) interface control database (ICD) objects in an example modeling environment and a corresponding example IMA model of the LRU ICD objects.

[0009] Figure 4 is a block diagram of an example implementation of an example model manager apparatus for implementing the examples disclosed herein.

[0010] Figure 5 It is a schematic diagram of importing example information from an example data source domain into an example language-specific domain via an example language-neutral domain.

[0011] Figure 6 is an example implementation of an example presentation layer of an example modeling system.

[0012] Fig. 7A Describes the process for generating, executing, and verifying Figure 1 An example IMA model generation system for multiple IMALRU models associated with an aircraft.

[0013] Figure 7B Depicted Fig. 7A A continuation of the IMA model generation system.

[0014] Figure 7C Depicted Figure 4 The model manager device generates a library associated with an example modeling environment.

[0015] Figure 8 It means that it can be executed to implement Figure 4 The model manager device is used to generate Figure 1 A flow chart of machine readable instructions for associating an IMA system model with an aircraft.

[0016] Fig. 9 It means that it can be executed to implement Figure 4 A model manager device is a flow chart of machine-readable instructions for importing definitions associated with an IMA system model into a modeling environment.

[0017] Fig.10 It means that it can be executed to implement Figure 4 A flow chart of machine-readable instructions for configuring a model manager device to configure (one or more) model objects associated with an IMA system model.

[0018] Fig.11 It means that it can be executed to implement Figure 4 A model manager means for generating a flow chart of machine-readable instructions for output associated with an IMA system model.

[0019] Fig.12 is constructed to execute Figure 8-Figure 11 Instructions to implement Figure 4 A block diagram of an example processing platform of a model manager apparatus.

[0020] These drawings are not to scale. In general, the same reference numbers will be used throughout the drawings and accompanying written description to refer to the same or like parts. DETAILED DESCRIPTION

[0021] Typical aircraft use highly integrated aircraft systems to improve control, monitoring, and operation of aircraft systems. As used herein, the term "aircraft system" refers to a sub-portion of an aircraft (e.g., an electrical system, a mechanical system, an electromechanical system, etc., and / or a combination thereof) that includes one or more coupled (e.g., electrically coupled, electromechanically coupled, mechanically coupled, etc.) components (e.g., electrical components, mechanical components, electromechanical components, etc.) operable to perform aircraft functions. For example, an aircraft system may correspond to a component such as an electric motor, a controller, a remote electronic unit, etc.

[0022] As typical aircraft systems include an increasing number of electrically interconnected components, validating the design of aircraft systems becomes increasingly complex. For example, designing an aircraft system may include evaluating interfaces and interconnections between the aircraft system and other aircraft systems that are electrically coupled to the aircraft system. Computer-generated models may be used to analyze the interconnections and validate the aircraft system design before releasing it for manufacturing.

[0023] In previous computer-generated model analysis implementations, using computer-generated models to analyze multiple interconnected aircraft systems is problematic. For example, a first computer-generated model used to simulate a first aircraft system may use a different architecture, different analysis criteria, different timing analysis, etc., than a second aircraft system modeled using a second computer-generated model. In such an example, attempting to successfully integrate the first and second computer-generated models to verify the interconnections between the first and second aircraft systems is unlikely.

[0024] Similarly, in previous computer-generated model analysis implementations, attempts have been made to successfully integrate and / or otherwise communicatively couple a first computer modeling environment (e.g., National LABVIEW TM ,OMG Compatibility complications arise from a first model based on a second computer modeling environment (e.g., a first model based on a second computer modeling environment, etc.) and a second model based on a second computer modeling environment. For example, compatibility complications are necessarily rooted in computer technology, because configurations, definitions, functions, etc. may be fundamentally different between computer modeling environments, thus generating compatibility issues between model interfaces during integration.

[0025] In previous implementations, attempts to address compatibility issues between models based on different computer modeling environments resulted in erroneous data and conversion errors. In some previous implementations, model developers created a conversion application or interface to convert data between models using different computer modeling environments. However, the manual process of creating the conversion interface is prone to human error because the large-scale models create many opportunities for typographical errors to be inserted by the model developer. Similarly, a model developer modifies one aspect of one of the models without updating the conversion interface to account for the modified aspect resulting in breaking the entire system model, generating erroneous data, etc.

[0026] In some previous implementations, models associated with conversion interfaces are not easily portable between applications. For example, a model associated with a first conversion interface in a first application will require the creation of a second conversion interface when the model is moved to a second application because conversion interfaces are application and / or computer modeling environment specific. As a result, rework occurs when attempting to reuse models across different applications and different computer modeling environments, thereby increasing development, verification, and testing time for project development.

[0027] The examples disclosed herein are operable to generate an integrated modular architecture (IMA) model. An IMA model is a computer-generated model used to simulate and / or otherwise verify functions associated with a vehicle system (e.g., an aircraft system) or a vehicle subsystem (e.g., an aircraft subsystem). In some examples, the IMA model is based on an integrated modular avionics concept that can replace many individual processors and line replaceable units (LRUs) with fewer, more centralized IMA processing units on some aircraft. In some aircraft, a common core system includes one or more common core resource (CCR) cabinets or IMA processing units, including one or more processing modules, power control modules, network switches, application-specific modules, etc. and / or combinations thereof.

[0028] In some disclosed examples herein, an IMA model manager apparatus transforms (e.g., automatically transforms) requirements and specifications of vehicles (e.g., aircraft, unmanned aerial vehicles, land-based vehicles, etc.) stored in a data source domain into a plurality of vehicle models (e.g., 100 vehicle models, 1000 vehicle models, 10,000 vehicle models, etc.) in a language-specific domain. For example, each of the plurality of vehicle models may include a plurality of abstract or software representations of requirements and specifications in a computer modeling environment.

[0029] In some examples, when used in a model-based development approach through automation of large-scale model generation, the IMA model manager apparatus supports interface control database (ICD) definition, maintenance, verification, analysis, and integration with functional requirements in native design tools, thereby eliminating errors and shortening project development time by reducing the amount of time to develop conversion interfaces associated with different computer modeling environments. As used herein, the term "interface control database" refers to a repository of information associated with interface information (e.g., communication addresses, communication nodes, device addresses, device identifiers, physical connection information (e.g., electrical contact locations, pin assignment details, wiring information, etc.), etc.), which is associated with interfaces between subsystems, systems, etc. and / or combinations thereof.

[0030] In some examples, the CCR cabinets of a vehicle contain the same or substantially similar hardware. However, each of the CCR cabinets may provide different functions and may be provided to the vehicle manufacturer by different contractors or suppliers. Integration between suppliers or between suppliers and vehicle manufacturers may cause problems even if they use the same CCR cabinet (e.g., the same hardware). The examples disclosed herein may alleviate these problems by generating an IMA model with standardized definitions for communicating parameters and signals between IMA models. In some examples, the IMA model with standardized definitions is embedded with metadata to convert and / or otherwise transform input data from an ICD, a model library, etc. and / or to convert and / or otherwise transform output data to an ICD, a model library, etc.

[0031] In some examples disclosed herein, a language neutral model (LNM) operating in a language neutral domain is deployed as a buffer between an ICD and a language specific model (e.g., an IMA model operating in a modeling environment). In some examples, the LNM operates as a buffer between the ICD and the computer modeling environment. For example, an IMA model manager device can generate an IMA model by generating an IMA library including IMA model objects based on information included in the ICD. For example, the IMA model manager device can import information from the ICD via the LNM and fill in the definition of the IMA model object with the imported information.

[0032] In some examples, the IMA model manager device can generate an IMA model by importing the IMA model object from the IMA library into the computer modeling environment to perform design verification, functional testing, etc. For example, the LNM can obtain corresponding information from the ICD using an ICD converter mechanism based on a first data formatting mode / schema of the ICD, and transfer the information to the computer modeling environment using a language-specific model converter mechanism based on a second data formatting mode of the computer modeling environment. In such an example, if the ICD is changed, a new conversion mechanism can be developed to convert the new ICD information into the LNM format while keeping the computer modeling environment or the second converter unaffected by the new ICD.

[0033] Figure 1 An example model manager 100 is depicted that executes an example model generation system 102 to generate one or more example vehicle models 104 using IMA. For example, the model manager 100 may be an IMA model manager. For example, the model generation system 102 may be an IMA model generation system. For example, the vehicle model 104 may be an aircraft system model, an unmanned vehicle system model, a land-based vehicle model, etc. Figure 1, vehicle model 104 is a model that includes one or more computer-based model objects associated with example aircraft systems 106 included in example aircraft 108. For example, aircraft system 106 may be an aileron actuation system, a flap actuation system, etc., which includes one or more electrical components, electromechanical components, hydraulic components, etc. Figure 1 An aircraft 108 is depicted in FIG. 1 , and additionally or alternatively, the examples disclosed herein may be applicable to any other type of vehicle, such as a land vehicle (e.g., a car, bus, truck, etc.), an unmanned vehicle, a water vehicle (e.g., a boat, a submarine, etc.), etc.

[0034] exist Figure 1 In the embodiment, the model generation system 102 implements the model management workflow 110 including the first operation 112. Alternatively, the model management workflow 110 may be Figure 1 Alternatively, the model management workflow 110 may include: Figure 1 At a first operation 112, the model manager 100 identifies (one or more) models for conversion to the ICD 114. For example, the model manager 100 may identify computer-based models associated with aircraft system components to be defined in the ICD, such as LRUs, remote data concentrators (RDCs), general processing modules (GPMs) included in CCR cabinets, etc.

[0035] exist Figure 1 In the illustrated example, the model management workflow 110 includes a second operation 116 at which the model manager 100 generates a model-ICD transformation. For example, the model manager 100 may generate a mapping between a model definition (e.g., model input parameters, model output parameters, etc.) and an ICD definition. The ICD definition may correspond to data fields, data structures, etc. based on a data format of the ICD. For example, the model manager 100 may generate a transformation by assigning standard data fields to aircraft system components (such as functional states, parameters, data sets, message structures, communication ports, etc.). The model manager 100 may populate the standard data fields with information corresponding to the aircraft system components. In response to populating the standard data fields, the model manager 100 may export the transformation to the ICD 114 for storage and future retrieval by the model manager 100.

[0036] In some examples, model manager 100 generates the transformation by mapping the aircraft system component to a reference aircraft system component (e.g., a previously defined aircraft system component) in ICD 114. For example, in response to determining that the aircraft system component matches the reference aircraft system component, ICD 114 may return a definition to be assigned and / or otherwise applied to the aircraft system component by model manager 100. For example, model manager 100 may assign and / or otherwise apply the definition associated with the reference aircraft system component to the aircraft system component.

[0037] exist Figure 1 , the model management workflow 110 includes a third operation 118 at which the model manager 100 generates (one or more) models using a model-ICD transformation. For example, the model manager 100 may generate an IMA model for an aircraft system component of interest. The model manager 100 may query the ICD 114 in a computer modeling environment (CME) for an ICD model object and a corresponding ICD definition associated with the aircraft system component of interest. In response to the query, the ICD 114 may return an ICD model object, and the model manager 100 may convert the ICD model object into a CME model object. The model manager 100 may convert the ICD definition associated with the ICD model object into a CME definition associated with the CME model object.

[0038] In some examples, the model manager 100 verifies the ICD definition by comparing the configuration parameters included in the returned ICD definition with one or more IMA definition rules. In response to the returned ICD definition satisfying one or more IMA definition rules, the model manager 100 can generate a transformation model 120 and / or a transformation model library 120. For example, the model manager 100 can generate one or more model objects, logical conditions, connection points, etc. included in and / or associated with the IMA model.

[0039] exist Figure 1 , the model manager 100 executes the vehicle model(s) 104 using the transformation model 120 and / or the transformation model library 120 to generate model outputs. For example, the model manager 100 may simulate functions or operating modes of the aircraft systems 106 of the aircraft 108 by executing the vehicle model(s) 104 to generate model outputs.

[0040] exist Figure 1, the aircraft system 106 is released to production at a fourth operation 122 by generating example output 124. For example, in response to successfully verifying the operation of the aircraft system 106 by simulating the corresponding vehicle model(s) 104, the model manager 100 may generate outputs such as alerts, reports, etc. indicating that the aircraft system 106 is released for assembly, construction, manufacturing, etc.

[0041] In some examples, the output 124 is supply chain build instructions. For example, the model manager 100 can generate instructions to be executed by the supply chain computing system to initiate the sequencing of components, the allocation of labor, etc. to build the aircraft system 106 associated with the IMA system model including one or more of the vehicle models 104. In another example, the model manager 100 can generate a report including the supply chain build instructions. For example, the supply chain build instructions can include drawings, requirements documents, specification documents, ICD documents, etc. associated with building the aircraft system 106 for the IMA system model.

[0042] In some examples, the output 124 is manufacturing build instructions. For example, the model manager 100 can generate instructions to be executed by a manufacturing computing system to initiate the manufacture of components, labor allocation, etc. to build an aircraft system 106 associated with an IMA system model including one or more of the vehicle models 104. In another example, the model manager 100 can generate a report including the manufacturing build instructions. For example, the manufacturing build instructions can include drawings, requirements documents, specification documents, ICD documents, etc. associated with building an aircraft system for the IMA system model 754.

[0043] In some examples, the output 124 is machine-readable instructions. For example, the model manager 100 may generate computer-readable instructions (e.g., binary code, hardware logic instructions, etc.) based on the conversion model 120 to be deployed by the aircraft 108, a flight simulator associated with the aircraft 108, etc. For example, the output 124 may be binary code that is used to implement the functions included in the conversion model 120. One or more hardware circuits may deploy the binary code to operate one or more aircraft systems 106 of the aircraft 108 during flight. Alternatively, the flight simulator may execute the binary code to simulate one or more aircraft systems 106 of the aircraft 108 during flight.

[0044] Figure 2 Is used for communication coupling Figure 1 1 is a schematic diagram of an example aircraft network 200 for example aircraft control hardware of the aircraft 108 . Figure 2 The aircraft network 200 is based on IMA and includes common core resources included in an example common core resource (CCR) cabinet 202. Figure 2 , CCR cabinet 202 includes an example general processing module (GPM) 204, which is a computing hardware platform that may include one or more processors, one or more graphics processing units, one or more network interfaces, the like, and / or combinations thereof.

[0045] Figure 2 The GPM 204 of FIG. 204 includes example software partitions 206 a, 208 a, 210 a, wherein each of the software partitions 206 a, 208 a, 210 a may perform a different aircraft system function. Partition 1 206 a may be a first partition included in the GPM 204, Partition 2 208 a may be a second partition included in the GPM 204, and Partition 3 210 a may be a third partition included in the GPM 204. Figure 2 , partition 1 206a includes an example software communication port (SW COM PORT) 206b and a first example hosted application 206c. The software communication port 206b may correspond to one or more queuing ports and / or sampling ports that are used to couple partition 1 206a to the first example A664 terminal system 214. For example, Figure 2 The software communication port 206 b may be a software abstraction of an ARINC 653 communication protocol receive port and an ARINC 653 communication protocol transmit port, etc., to facilitate communication between the GPM 204 and another component included in the aircraft network 208 .

[0046] exist Figure 2 middle, Figure 2 The first hosted application 206c is a software application capable of executing and / or otherwise performing software tasks associated with aircraft system functions. Figure 2 , partition 2 208a includes a second example software communication port 208b and a second example hosted application 208c. For example, the software communication port 208b can be a software abstraction of an ARINC 653 communication protocol receive port, an ARINC 653 communication protocol transmit port, etc. In some examples, the second hosted application 208c is the same software application as the first hosted application 206c, while in other examples, the first and second hosted applications 206c, 208c are different.

[0047] exist Figure 2 , GPM 204 includes an example core operating system (OS) 212 and a first A664 terminal system 214 . Figure 2The core OS 212 of is the base operating system on which the software partitions 206a, 208a, 210a operate. The first A664 end system 214 includes an example network interface controller (NIC) 216, which is a hardware controller that is capable of receiving data packets / data packets from an example CCR network switch (NS) 218 ​​and abstracting the received data packets for use by the software partitions 206a, 208a, 210a. Similarly, the first A664 end system 214 can receive an abstraction of data packets from the software partitions 206a, 208a, 210a and generate data packets based on the abstraction to be transmitted via the CCR NS 218. The CCR NS 218 is a fiber optic network switch. Alternatively, other types of network switches, such as copper-based Ethernet switches, can be used.

[0048] exist Figure 2 In the illustrated example of , the CCR NS 218 of the CCR cabinet 202 is communicatively coupled to an example application specific module (ASM) 219 including a second A664 terminal system 220. The ASM 219 is hardware and / or software for acquiring, transmitting and / or processing data via the second A664 terminal system 220. The CCR NS 218 couples the CCR cabinet 202 to the aircraft network 200 via an example NS 222. The NS 222 facilitates communication via the ARINC 664 (A664) communication protocol. For example, the NS 222 can facilitate communication between an A664 line replaceable unit (LRU) 224 and a remote data concentrator (RDC) 226 via the A664 communication protocol. However, alternative communication protocols such as ARINC 429 (A429) may be used.

[0049] exist Figure 2 , the A664 LRU 224 is modular hardware including one or more processors, one or more network interfaces, etc., capable of facilitating A664 communications using a third example A664 terminal system 228. Figure 2 The RDC 226 is a high-speed modular analog-to-digital and / or digital-to-analog conversion computing device that can process and format actuator data, sensor data, etc. into a common digital format through a communication protocol such as A429, A664, etc. For example, Figure 2 As depicted in , the RDC 226 obtains data (eg, analog signals, discrete signals, etc.) from an example sensor 230 and transmits commands (eg, control signals) to an example actuator 232. Figure 2In the embodiment, the RDC 226 transmits data to and receives data from the A429 LRU 234 including the A429 terminal system 236 via the A429 communication protocol. Figure 2 In the example, the RDC 226 is communicatively coupled to an example controller area network (CAN) bus 238 (eg, a bus based on the CAN communication protocol). Figure 2 , the CAN bus 238 is communicatively coupled to a first example CAN LRU 240 and a second example CAN LRU 242 (eg, LRUs capable of communicating via CAN, CAN-based LRUs, etc.).

[0050] Figure 3 An example LRU ICD object 300 and a corresponding example model 302 are depicted in an example modeling environment 304. Figure 3 In the example, the LRU ICD object 300 is included in Figure 1 A software abstraction in the ICD 114 of the LRU that can suppress low-level hardware details through a high-level interface. For example, the LRU ICD object 300 may correspond to Figure 2 A high level representation of the hardware and / or software corresponding to the A664 LRU 224, A429 LRU 234, first CAN LRU 240, or second CAN LRU 242. Figure 3 The LRU ICD object 300 corresponds to the LRU, alternatively, it can be combined with Figure 3 Any other hardware and / or software described that is abstracted or represented.

[0051] exist Figure 3 , LRU ICD object 300 includes an example ICD application block 306, which includes an example ICD application definition 308. ICD application block 306 is a representation of the functions performed by software (e.g., application software) executing on the LRU. ICD application definition 308 represents the functions performed by the software (e.g., application software) executing on the LRU. Figure 1 The ICD 114 may be used to construct a data structure of one or more data formats for the control logic functions of the LRU. Figure 3 , the ICD application definition 308 includes a first functional state definition 309a, a second functional state definition 309b, a first parameter definition 311a, a second parameter definition 311b, a first data set definition 313a, a second data set definition 313b, and a message structure definition 315. Alternatively, the ICD application definition 308 may include a first functional state definition 309a, a second functional state definition 309b, a first parameter definition 311a, a second parameter definition 311b, a first data set definition 313a, a second data set definition 313b, and a message structure definition 315. Figure 3There may be fewer or more functional state definitions 309a, 309b, parameter definitions 311a, 311b, data set definitions 313a, 313b, and / or message structure definitions 315 shown in the illustrated example.

[0052] exist Figure 3 In the example, parameter definitions 311a, 311b may correspond to encapsulation of signal data. For example, parameter definitions 311a, 311b may include data values ​​in any type of data format. Figure 3 In the embodiment, the data set definitions 313a, 313b can provide coherency associated with multiple parameter definitions 311a, 311b. For example, the first data set definition 313a can correspond to interface information associated with a first data source, and the second data set definition 313b can correspond to interface information associated with a second data source. For example, the parameter definitions 311a, 311b are associated with corresponding functional state definitions 309a, 309b and can correspond to the same data, but from different sources. For example, the first parameter definition 311a can correspond to the first functional state definition 309a, and the second parameter definition 311b can correspond to the second functional state definition 309b. The first parameter definition 311a can correspond to the first functional state definition 309a, and the second parameter definition 311b can correspond to the second functional state definition 309b. Figure 2 The second parameter definition 311b may correspond to the same state, but from Figure 2 CAN LRU 2 242 is obtained.

[0053] exist Figure 3 In the illustrated example, the functional state definitions 309a, 309b can correspond to metadata associated with the data set definitions 313a, 313b. For example, the functional state definitions 309a, 309b can describe the validity of the related data (e.g., parameter definitions 311a, 311b) by evaluating and / or otherwise determining the status of the related data. For example, the status can be a "failed / warning" state, a "no calculated data" state, a "normal operating state" state, or a "functional test" state. For example, the first functional state definition 309a can have a "failed / warning" state, which corresponds to the first parameter definition 311a having an unverified data value because the CAN LRU 1 240 is unresponsive, while the second parameter definition 311b has a verified data value.

[0054] In some examples, the "failed / warning" state provides a warning indicating that the source of the first parameter definition 311a is unresponsive. In response to the first parameter definition 311a being unresponsive, the model manager 100 may select a verification data value associated with the second parameter definition 311b. In some examples, the first functional state definition 309b may have a "no calculated data" state, which corresponds to the first parameter definition 311a that does not have an available data value that can be provided to the LRU ICD object 300. In some examples, when the verification data value is associated with the first parameter definition 311a, the first functional state definition 309b may have a "normal operating state". In some examples, when the data value associated with the first parameter definition 311a is calculated during a model test operation, the first functional state definition 309b may have a "functional test" state.

[0055] exist Figure 3 In the example, the message structure definition 315 may correspond to a collection or combination of one or more data set definitions associated with the ICD application block 306. For example, the message structure definition 315 may include all of the data set definitions 313a, 313b of the ICD application block 306. Additionally or alternatively, the ICD application definition 308 may include more than one data set definition. Figure 3 The ICD application definitions 308 depicted may be fewer or more.

[0056] In some examples, each LRU included in the ICD 114 has the same ICD application definition 308 with different values. For example, Figure 2 The A664LRU 224 can include Figure 2 However, the A664 LRU 224 may have different values ​​for the functional state definitions 309a, 309b, parameter definitions 311a, 311b, data set definitions 313a, 313b, etc., compared to the A429 LRU 234. In such an example, by using a standardized ICD application definition 308 for each similar or substantially similar component, the A664 LRU 224 may have different values ​​for the functional state definitions 309a, 309b, parameter definitions 311a, 311b, data set definitions 313a, 313b, etc. Figure 1 During the second operation 116, Figure 1 The ICD 114 can be used to quickly and accurately instantiate different types of LRUs in the ICD 114. For example, each LRU can have the same ICD application definition 308, each A664 end system can have the same ICD application definition as other A664 end systems, and so on.

[0057] exist Figure 3, LRU ICD object 300 includes an example ICD interface block 310, which includes an ICD interface definition 312. ICD interface block 310 is a representation of the communication functions performed by the communication terminal system defined by the ICD. For example, ICD interface block 310 may correspond to Figure 2 An abstraction of hardware and / or software corresponding to the first A664 terminal system 214, the second A664 terminal system 220, the third A664 terminal system 228 or the A429 terminal system 236.

[0058] exist Figure 3 In ICD interface definition 312, it is based on Figure 1 The ICD 114 uses one or more data formats to store data structures associated with the communication functions of the LRU. Figure 3 In the ICD interface definition 312, the ICD interface definition 312 includes a communication (COM) port definition, a virtual link (VL) definition, and a sub-VL definition. Figure 3 In the context of COM port definitions, a COM port definition is a socket. For example, a COM port definition may correspond to a preconfigured communication socket that provides a queue for transmitting messages to or receiving messages from a model object, application, computing device, etc. For example, a COM port definition may correspond to a queue port or a sampling port for queuing software partitions (such as Figure 2 Partition 1 206a) is coupled to a communication terminal system (such as Figure 2 The first A664 terminal system 214).

[0059] exist Figure 3 In the VL definition, a switching packet routing scheme based on a selected communication protocol is represented. For example, the VL definition may correspond to the switching packet routing scheme defined in the A664 Part 7 standard, where the destination MAC address is used to implement tree routing for each VL identification indicator. Figure 3 In the example, the sub-VL definition indicates the process used by the transmitter to call the VL definition to encapsulate the data before transmitting the data. For example, the sub-VL definition can include encapsulating the data from the COM port into a VL definition such as Figure 2 Instructions for the data format used by the transmitter of the NIC 216 to transmit the encapsulated data. Additionally or alternatively, the ICD interface definition 312 may include instructions for Figure 3 There are fewer or more definitions depicted in .

[0060] exist Figure 3 In the illustrated example, the model 302 is an IMA model that includes IMA model objects 314, 316. Figure 3, the model manager 100 generates the model 302 in the modeling environment 304 by importing the IMA model objects 314 , 316 into the modeling environment 304 and populating the IMA definitions 318 , 320 based on the information conversion from the LRU ICD object 300 to the modeling environment 304 .

[0061] exist Figure 3 In , model 302 is the corresponding abstraction of LRU ICD object 300 when it is converted and / or otherwise imported into modeling environment 304. Figure 3 In the modeling environment 304 is Alternatively, any other computer-based modeling environment may be used. Model 302 is generated when LRU ICD object 300 is migrated and / or otherwise converted from a first data format, such as an ICD data format, to a second data format, where the second data format is specific to modeling environment 304. However, in the previous embodiment, when LRU ICD object 300 is converted to Figure 3 When the modeling environment 304 is different from the modeling environment, a second model is generated, which can be Figure 3 In some examples, when trying to Figure 3 Integration problems occur when the model 302 of the embodiment is coupled to the second model. The examples disclosed herein solve the integration problems of such previous implementations.

[0062] exist Figure 3 In FIG. 3 , model 302 includes IMA model objects 314 , 316 to simulate and / or otherwise verify an aircraft system design. IMA model objects 314 , 316 include IMA application model object 314 and IMA interface model object 316 . Figure 3 The IMA application model object 314 includes an example IMA application definition 318 associated with the ICD application definition 308 of the LRU ICD object 300. Figure 3, the IMA application definition 318 represents metadata parameters associated with the message structure definition 315. For example, the IMA application definition "FUNCTIONAL STATUS A_MESSAGE" of the IMA application model object 314 may correspond to the "FUNCTIONAL STATUS" ICD application definition defined in the ICD application definition 308, wherein the IMA application definition is configured based on the dataset definitions 313a, 31b and the message structure definition 315 included in the ICD application definition 308. The IMA application definition 318 corresponds to an abstraction based on values ​​that execute application logic. For example, the IMA application definition "FUNCTIONAL STATUS A_MESSAGE" may correspond to an output value of a pressure sensor calculation function that calculates an engineering value measured by the pressure sensor based on one or more transformation or scaling functions.

[0063] Figure 3 The IMA interface model objects 316 include example IMA interface definitions 320 associated with the ICD interface definitions 312. For example, the IMA interface definition "TX_COM_PORT_10121" may correspond to a "COMPORT" ICD interface definition defined in the ICD interface definitions 312, where the IMA interface definition is configured based on the SUB-VL and VL ICD interface definitions defined in the ICD interface definitions 312. The IMA interface definitions 320 correspond to an abstraction of a software port for interconnecting different model blocks and / or different models.

[0064] exist Figure 3 In the embodiment, the IMA interface definition 320 may correspond to a socket application programming interface (API), such as a send() function call, a recv() function call, a write() function call, a read() function call, a recvfrom() function call, etc. For example, the IMA interface definition "TX_COM_PORT_10121" may correspond to a link or pointer included in another model block and / or another model, which receives a corresponding "FUNCTIONALSTATUS A_MESSAGE" value to perform a function or execute a software logic routine.

[0065] exist Figure 3, the IMA interface model object 316 includes an example network port model object 322 to simulate the coupling of the software layer of the LRU with the hardware layer of the LRU. For example, the network port model object 322 can be an A664 network port model object. For example, the network port model object 322 can use the IMA application definition 318 coupled to the IMA interface definition 320 to simulate the generation of data packets for transmission via the A664 communication protocol.

[0066] Figure 4 is used to implement the examples described in this article Figure 1 and Figure 3 A block diagram of an example implementation of the model manager 100 is shown in FIG. Figure 4 In the illustrated example, the model manager 100 includes an example modeling environment selector 410, an example data source selector 420, an example interface importer 430, an example interface exporter 440, an example model object handler 450, an example ICD converter 460, an example language specific model (LSM) converter 470, an example interface validator 480, and an example report generator 490.

[0067] exist Figure 4 In the illustrated example, the model manager 100 includes a modeling environment selector 410 to determine a modeling environment to generate an IMA model, such as Figure 3 In some examples, the modeling environment selector 410 selects an LSM environment to generate a model 302 with Figure 1 The IMA model associated with aircraft system 106 of aircraft 108 is shown in FIG. 4 . For example, modeling environment selector 410 may select To generate model 302. In some examples, modeling environment selector 410 determines whether to generate another model. For example, modeling environment selector 410 may determine whether to generate another model after model 302 has been generated, verified, and / or exported to Figure 1 The ICD 114 then generates a second model.

[0068] exist Figure 4 In the illustrated example, the model manager 100 includes a data source selector 420 to determine an interface control data source associated with the aircraft system to be modeled. In some examples, the interface control data source is a database, a spreadsheet (e.g., a golden spreadsheet), etc., or any other type of interface control document or information. For example, the model manager 100 may select Figure 1 ICD 114.

[0069] exist Figure 4In the illustrated example, the model manager 100 includes an interface importer 430 to retrieve and / or otherwise obtain data from an interface control data source. In some examples, the interface importer 430 obtains definitions from an interface control data source to populate a top-level abstract model, such as Figure 3 For example, the interface importer 430 can be from Figure 1 ICD 114 Figure 3 The interface importer 430 may be configured to obtain an ICD block from an interface control data source to populate the model 302. For example, the interface importer 430 may be configured to obtain an ICD block from an interface control data source. Figure 1 The ICD 114 of the ICD 114 obtains the ICD application block 306, the ICD interface block 310, etc. In some examples, the interface importer 430 generates a model library. For example, the interface importer 430 can generate one or more libraries of the modeling environment 304 in response to the generation of the IMA application definition 318, the IMA interface definition 320, etc.

[0070] exist Figure 4 In the illustrated example of FIG. 1 , the model manager 100 includes an interface exporter 440 to transfer and / or otherwise export data associated with the IMA model. In some examples, the interface exporter 440 exports the IMA definition to the ICD. For example, the interface exporter 440 may export one or more of the IMA application definition 318, the IMA interface definition 320, etc. from the IMA model to the ICD. Figure 3 Modeling environment 304 exported to Figure 1 In some examples, the interface exporter 440 exports the IMA model objects to the ICD. For example, the interface exporter can export one or more of the IMA application model objects 314, the IMA interface model objects, etc. from the modeling environment 304 to the ICD 114. In some examples, the interface exporter 440 exports the IMA model objects (such as Figure 3 The model 302 ) is exported from the modeling environment 304 to the ICD 114 .

[0071] In some examples, the interface exporter 440 generates output based on the IMA model. For example, the interface exporter 440 may generate output based on Figure 3The interface exporter 440 may generate machine-readable instructions (e.g., binary code) from the model 302 of the present invention. For example, the interface exporter 440 may compile and / or otherwise convert information associated with the model 302 into computer executable code. For example, the interface exporter 440 may compile the IMA application model object 314 and associated control logic, the IMA interface model object 316 and associated control logic, the IMA application definition 318, the IMA interface definition 320, etc., and / or a combination thereof into machine-readable instructions that may be executed by the aircraft system 106, the aircraft 108, a flight simulator associated with the aircraft 108, etc. In some examples, the interface exporter 440 deploys the machine-readable instructions to a vehicle and / or a vehicle simulator. For example, the interface exporter 440 may deploy the machine-readable instructions to the aircraft system 106, the aircraft 108, etc., and / or a flight simulator associated with the aircraft system 106, the aircraft 108, etc. In some examples, the interface exporter 440 directs, instructs, and / or otherwise causes the operation of the vehicle and / or the vehicle simulator. For example, interface exporter 440 may instruct aircraft systems 106 , aircraft 108 , etc. to replace existing machine-readable instructions included in aircraft systems 106 , aircraft 108 , etc. with machine-readable instructions generated by interface exporter 440 . In such examples, interface exporter 440 may cause aircraft systems 106 , aircraft 108 to perform operations such as flight operations, simulated flight operations, etc. using the machine-readable instructions generated by interface exporter 440 .

[0072] In some examples, interface exporter 440 is based on Figure 3 The model 302 generates supply chain and manufacturing build instructions. For example, the interface exporter 440 can generate supply chain and manufacturing build instructions based on the model 302. Figure 1 ICD 114, Figure 3 The information included in the model 302, etc. generates requirements, specifications, etc., indicating that the aircraft system 106 associated with the model 302 can be Figure 1 The interface exporter 440 may be released for production at the fourth operation 122 of the IMA system model. For example, the interface exporter 440 may direct or instruct one or more computing devices or systems associated with the aircraft system 106 and / or, more specifically, the manufacturing and supply chain of the aircraft 108 to initiate the construction of one or more prototypes, one or more production line sets, and the like of the aircraft system 106, the aircraft 108, and the like. For example, the interface exporter 440 may initiate the manufacturing of the vehicle system associated with the IMA system model. For example, the interface exporter 440 may initiate the production of the aircraft system 106 and / or the aircraft 108 based on the generated supply chain and / or manufacturing build instructions.

[0073] exist Figure 4In the illustrated example, the model manager 100 includes a model object handler 450 to import, configure, and / or modify models included in the modeling environment. In some examples, the model object handler 450 imports a model block of interest to be processed. For example, the model object handler 450 can import an IMA application model object 314, an IMA interface model object 316, etc. to be processed into the modeling environment 304. In some examples, the model object handler 450 connects two or more model objects associated with the IMA model. For example, the model object handler 450 can connect or communicatively couple Figure 3 The IMA application model objects 314 and the IMA interface model objects 316 are used to create relationships between the blocks in the model 302 .

[0074] In some examples, model object handler 450 selects a model object to be processed and / or determines whether to select another model object to be processed. In some examples, model object handler 450 adjusts definitions associated with an IMA model. For example, model object handler 450 may adjust definitions corresponding to Figure 3 The IMA application definition 318 includes the definition of the IMA application definition "FUNCTIONAL STATUS A_MESSAGE". In some examples, the model object handler 450 Figure 3 The model object handler 450 may generate a new model object in the modeling environment 304 of the embodiment of the present invention. For example, the model object handler 450 may generate a new model object by creating a blank model object in the modeling environment 304 and including one or more IMA application definitions, one or more IMA interface definitions, etc., and then generate new model object relationships and model object connections associated with the new model object. For example, the model object may correspond to an IMA component. The model object relationships and model object connections may correspond to software connections from a software partition to an end system. For example, the model object relationships and model object connections may correspond to converting a software partition to an end system. Figure 2 The first through third software partitions 206a, 208a, 210a are communicatively coupled to Figure 2 The first A664 terminal system 214 has a queuing port and a sampling port. In some examples, the model object handler 450 can generate an IMA system model in response to generating one or more IMA models.

[0075] exist Figure 4 In the illustrated example, the model manager 100 includes an ICD converter 460 to convert and / or otherwise convert Figure 1The ICD converter 460 may convert data included in an ICD 114 from an ICD data format to a language neutral model (LNM) data format. For example, the ICD converter 460 may be an ICD-LNM converter. The ICD converter 460 may convert (1) an ICD application definition 308 from the ICD 114 in an ICD data format associated with the ICD 114 to (2) an LNM definition included in the LNM in an LNM data format associated with the LNM. For example, the ICD converter 460 may select an ICD object of interest, such as a LRU ICD object 300, instantiate the LRU ICD object 300 in the LNM, and populate the LNM definition associated with the instantiated object in the LNM with the ICD application definition 308, the ICD interface definition 312, and the like.

[0076] exist Figure 4 In the illustrated example, the model manager 100 includes an LSM converter 470 to convert and / or otherwise transform data included in the LNM from the LNM data format to the LSM data format. For example, the LSM converter 470 can be a LNM-LSM converter. For example, the LSM converter 470 can select an IMA model object of interest, such as an IMA application model object 314, instantiate the IMA application model object 314 in the modeling environment 304, and populate the IMA application definition 318 with a corresponding LNM definition included in the LNM, which corresponds to the ICD application definition 308 included in the ICD 114. For example, there is a LNM model object for each IMA model object. Each model object includes the same number and type of attributes and elements, and therefore, data between the LNM model object and the IMA model object can be synchronized. For example, the LNM definition included in the LNM associated with the IMA application definition 318 includes the same number and type of attributes and elements.

[0077] In some examples, the LSM converter 470 converts (1) LNM definitions included in the LNM in an LNM data format specific to the LNM to (2) LNM definitions included in an LNM in an LNM data format specific to the LNM. Figure 3 The LSM converter 470 may generate an IMA application definition 318, an IMA interface definition 320, etc. in the LSM data format of the modeling environment 304. In some examples, the LSM converter 470 generates a presentation layer. For example, the LSM converter 470 may generate a presentation layer to simulate a network layer for tasks such as handling syntax processing of message data including format conversion, encryption / decryption, etc. to support the upper layers of the presentation layer. For example, the LSM converter 470 may generate a presentation layer 600 as shown below in combination with Figure 6 as described.

[0078] exist Figure 4In the illustrated example, the model manager 100 includes an interface validator 480 to confirm and / or otherwise verify that the converted information complies with definition rules (e.g., ICD definition rules, LNM definition rules, IMA definition rules, etc.). In some examples, the interface validator 480 verifies the ICD information. For example, the interface validator 480 can compare the information to be stored in the ICD 114 with the ICD definition rules, and when the information is verified based on the comparison, store the information in the ICD 114. In some examples, the interface validator 480 verifies the LNM information. For example, the interface validator 480 can compare the information to be stored in the LNM with the LNM definition rules, and when the information is verified based on the comparison, store the information in the LNM.

[0079] In some examples, interface validator 480 validates LSM information. For example, interface validator 480 may validate LSM information to be imported into LSM (e.g., Figure 3 The interface validator 480 may be configured to compare information in the modeling environment 304 of the IMA system model with the IMA definition rules, and import the information into the LSM when the information is verified based on the comparison. In some examples, the interface validator 480 generates an alarm in response to the ICD, LNM, and / or LSM information not being verified. For example, the interface validator 480 may stop the operation of the IMA system model and generate an error message, an alarm, etc. In some examples, the alarm is transmitted to a user interface to notify the user that the ICD, LNM, and / or LSM information needs to be modified to comply with the definition rules. For example, the user may modify the definition associated with the model object so that the model object complies with the definition rules.

[0080] In some examples, the interface validator 480 executes the IMA system model. For example, the interface validator 480 may execute, run, operate, etc. Figure 3 Model 302 of the present invention and generates one or more outputs. For example, interface validator 480 may generate outputs of aircraft system components such as actuators, sensors, network switches, etc. For example, interface validator 480 may execute model 302 to simulate Figure 2 The state of the actuator 232, such as whether the actuator 232 is disabled, enabled, operating at a specified capacity or power percentage, etc. In another example, the interface verifier 480 can execute the model 302 to simulate Figure 2 The interface verifier 480 can execute the model 302 to simulate the measurement of the sensor 230, such as the sensor 230 measuring pressure, speed, temperature, etc. In another example, the interface verifier 480 can execute the model 302 to simulate Figure 2 Parameters of NS 222, such as bandwidth, latency, throughput, IP address, media access control (MAC) address, communication protocol parameters, etc.

[0081] In some examples, interface validator 480 validates the IMA system model based on the output of the IMA system model. For example, interface validator 480 may validate the IMA system model by comparing the output of model 302 (e.g., pressure measurement of sensor 230, waiting time of NS 222, etc.) with the validation output. Figure 3 Model 302 of the embodiment of the present invention and based on the comparison, model 302 is verified. For example, the verification output can correspond to the expected value of model 302. For example, interface verifier 480 can compare the output of model 302 with the corresponding verification output and determine whether the output satisfies the verification output by substantially matching (e.g., matching or matching within a tolerance) the verification output. In some examples, interface verifier 480 can verify that one or more outputs meet the verification output by comparing one or more outputs with one or more corresponding verification outputs. Figure 3 302 of the model, and based on the comparison, determine that one or more outputs satisfy one or more corresponding verification outputs.

[0082] exist Figure 4 In the illustrated example, the model manager 100 includes a report generator 490 to generate reports based on actions performed by the model manager 100. In some examples, the report generator 490 generates reports when the model manager 100 creates an IMA model. For example, the report generator 490 can generate reports when validating one or more of the IMA application model objects 314, the IMA interface model objects 316, the IMA application definitions 318, the IMA interface definitions 320, etc., and / or combinations thereof (e.g., validating LNM definitions imported from the LNM based on comparison with LSM definition rules).

[0083] In some examples, report generator 490 generates a report including Figure 1 For example, the report generator 490 may generate a report indicating that the model 302 modeled with the model 302 may be released for production. Figure 2 The report generator 490 may include at least one of machine-readable instructions, supply chain build instructions, manufacturing build instructions, etc. For example, the report generator 490 may determine that the model 302 successfully executes the A664 LRU 224, Figure 1 For example, the report generator 490 may initiate verification and / or validation testing functions associated with the aircraft system 106, etc. by generating a report and transmitting an alert, notification, etc. including the report to another computing system (such as a supply chain computing system or a manufacturing computing system configured to generate a manufacturing order, a prototype manufacturing order, etc.). Figure 1The report generator 490 may initiate production of the aircraft 108 to generate A664 LRUs 224, aircraft systems 106, etc. when the corresponding models 302 have been executed and / or verified. For example, the report generator 490 may initiate production of the aircraft systems 106 and / or, more generally, the aircraft 108 based on at least one of manufacturing build instructions, supply chain build instructions, machine-readable instructions, etc.

[0084] and Figure 4 The implementation is described in Figure 1 and Figure 3 An example approach of the model manager 100 is as follows, Figure 4 One or more of the elements, processes and / or devices described in the examples may be combined, divided, rearranged, omitted, eliminated and / or implemented in any other manner. In addition, the modeling environment selector 410, the data source selector 420, the interface importer 430, the interface exporter 440, the model object handler 450, the LNM converter 460, the LSM converter 470, the interface validator 480, the report generator 490 and / or more generally Figure 1 and Figure 3 The model manager 100 may be implemented by hardware, software, firmware and / or any combination of hardware, software and / or firmware. Thus, for example, the modeling environment selector 410, the data source selector 420, the interface importer 430, the interface exporter 440, the model object handler 450, the LNM converter 460, the LSM converter 470, the interface validator 480, the report generator 490 and / or more generally any of the model manager 100 may be implemented by one or more analog circuits or (one or more) digital circuits, logic circuits, (one or more) programmable processors, (one or more) programmable controllers, (one or more) graphics processing units (GPUs), (one or more) digital signal processors (DSPs), (one or more) application specific integrated circuits (ASICs), (one or more) programmable logic devices (PLDs) and / or (one or more) field programmable logic devices (FPLDs). When any apparatus or system claims of this patent are read to cover purely software and / or firmware implementations, at least one or some of the modeling environment selector 410, data source selector 420, interface importer 430, interface exporter 440, model object handler 450, LNM converter 460, LSM converter 470, interface validator 480, and / or report generator 490 are expressly defined herein as comprising a non-transitory computer-readable storage device or storage disk such as a memory, digital versatile disk (DVD), compact disk (CD), Blu-ray disk, etc., including software and / or firmware. In addition, Figure 1 and Figure 3 The model manager 100 may include: Figure 4In addition to or in place of one or more elements, processes and / or devices described in Figure 4 One or more elements, processes and / or devices described in, and / or may include more than one of any or all of the described elements, processes and devices. As used herein, the phrase "in communication" includes variations thereof, including direct communication and / or indirect communication through one or more intermediate components, and does not require direct physical (e.g., wired) communication and / or continuous communication, but in addition, also includes selective communication at periodic intervals, scheduled intervals, non-periodic intervals and / or one-time events.

[0085] Figure 5 is a schematic diagram of importing information from an example data source domain 502 into an example language-specific domain 504 via an example language-neutral domain 506. Figure 5 , the data source domain 502 includes example ICD sources, such as a first example ICD source 508, a second example ICD source 510, and a third example ICD source 512. The first ICD source 508 and the second ICD source 510 are databases. The third ICD source 512 represents a group of one or more documents (e.g., a spreadsheet, a requirements document, a specification document, etc.).

[0086] exist Figure 5 , the first ICD source 508 includes a first ICD protocol definition 514. For example, the first ICD protocol definition 514 can be an ICD definition associated with the first communication protocol (e.g., Figure 3 For example, the first communication protocol may be an A429 communication protocol. For example, the first ICD protocol definition 514 may include ICD definitions corresponding to one or more A429 communication ports and / or control logic to implement the A429 communication ports. For example, the first ICD protocol definition 514 may correspond to an ICD interface definition that communicates with the A429 terminal system 236 and / or more generally communicates with the A429 terminal system 236. Figure 2 The A429 LRU 234 is associated with a queuing port and / or a sampling port.

[0087] In some examples, an ICD protocol definition, such as the first ICD protocol definition 514, may be associated with Figure 1 The interface information, requirement information, specification information, etc. associated with the aircraft system 106. For example, the first ICD protocol definition 514 can be associated with Figure 2The first ICD protocol definition 514 may include interface information associated with the NS 222 of the aircraft system 106, including communication port information (e.g., IP address, media access control (MAC) address, communication protocol address, etc.), connector pin assignment information, wiring information, etc. In another example, the first ICD protocol definition 514 may be requirement information, such as the number and / or type of components included in the aircraft system 106, such as Figure 2 The number of network switches in the aircraft network 200, the type of actuators 232 and / or sensors 230, and the number of network switches in the aircraft network 200. Figure 2 The number of multiple partitions used by the GPM 204 of the first ICD protocol definition 514, etc. In another example, the first ICD protocol definition 514 can be performance information of aircraft system components (e.g., bandwidth, data throughput, latency, etc. of the NS 222), firmware version information of aircraft system components, software version information of aircraft system components, etc.

[0088] exist Figure 5 , the second ICD source 510 includes a second ICD protocol definition 516. For example, the second ICD protocol definition 516 can be an ICD definition associated with a second communication protocol. For example, the second communication protocol can be an A664 communication protocol. For example, the second ICD protocol definition 516 can include an ICD definition corresponding to one or more A664 communication ports and / or control logic to implement the A664 communication port. For example, the second ICD protocol definition 516 can correspond to an ICD definition associated with the first A664 terminal system 214 and / or more generally with Figure 2 The GPM 204 is associated with a queuing port and / or a sampling port. Figure 5 , the third ICD source 512 includes documents that include information associated with the second ICD protocol definition 516. For example, the third ICD source 512 may include documents that include ICD definitions corresponding to one or more A664 communication ports and / or control logic to implement the A664 communication port.

[0089] The first ICD source 508, the second ICD source 510, and / or the third ICD source 512 may be implemented by a volatile memory (e.g., synchronous dynamic random access memory (SDRAM), dynamic random access memory (DRAM), RAMBUS dynamic random access memory (RDRAM), etc.) and / or a non-volatile memory (e.g., flash memory). The first ICD source 508, the second ICD source 510, and / or the third ICD source 512 may additionally or alternatively be implemented by one or more double data rate (DDR) memories (such as DDR, DDR2, DDR3, DDR4, mobile DDR (mDDR), etc.). The first ICD source 508, the second ICD source 510, and / or the third ICD source 512 may additionally or alternatively be implemented by one or more mass storage devices, such as (one or more) hard disk drives, (one or more) optical disk drives, (one or more) digital universal disk drives, solid-state drives, etc. Although the first ICD source 508 , the second ICD source 510 , and the third ICD source 512 are illustrated as a single database or a single document set in the illustrated example, the first ICD source 508 , the second ICD source 510 , and the third ICD source 512 may be implemented by any number and / or type of databases or document sets.

[0090] exist Figure 5 In the illustrated example, the model manager 100 converts data between the data source domain 502 and the language neutral model (LNM) 518 included in the language neutral domain 506 via the first ICD converter 520, the second ICD converter 522, and the third ICD converter 524. For example, Figure 4 The ICD converter 460 may implement the first to third ICD converters 520, 522, 524. For example, Figure 4 The ICD converter 460 may implement the first ICD converter 520 to convert (1) a first ICD protocol definition 514 included in the first ICD source 508 in an ICD data format specified by the first ICD source 508 to (2) a first LNM protocol definition 526 included in the LNM 518 in an LNM data format specified by the LNM 518. In some examples, the interface importer 430 instructs the ICD converter 460 to implement the first through third ICD converters 520, 522, 524.

[0091] In another example, the ICD converter 460 may implement a second ICD converter 522 to convert (1) a second ICD protocol definition 516 included in the second ICD source 510 in an ICD data format specified by the second ICD source 510 to (2) a second LNM protocol definition 528 included in the LNM 518 in an LNM data format specified by the LNM 518. In yet another example, the ICD converter 460 may implement a third ICD converter 524 to convert (1) a second ICD protocol definition 516 included in the third ICD source 512 in an ICD data format specified by the third ICD source 512 to (2) a second LNM protocol definition 528 included in the LNM 518 in an LNM data format specified by the LNM 518.

[0092] exist Figure 5 518, first LNM protocol definition 526 is a language-neutral definition associated with first ICD protocol definition 514. As used herein, the term "language-neutral definition" refers to a data structure that controls logic functions and related configuration parameters corresponding to functions of an aircraft component, aircraft subsystem, aircraft system, etc. that are independent of data source domain 502 and language-specific domain 504. For example, a language-neutral definition may include the same values ​​of attributes or elements as an ICD definition and / or a language-specific definition, but in a data format or data structure that is not used by the ICD definition or the language-specific definition. Thus, an ICD source included in data source domain 502 or a modeling environment included in language-specific domain 504 may be added, removed, or modified without affecting the language-neutral definitions (e.g., first LNM protocol definition 526, second LNM protocol definition 528, etc.) included in LNM 518.

[0093] exist Figure 5 512. In the embodiment of the present invention, the data format included in the first LNM protocol definition 526 and the second LNM protocol definition 528 is independent of the selection of one of the first ICD source 508, the second ICD source 510, or the third ICD source 512 to be processed. For example, the information included in the first LNM protocol definition 526 retains the same data format independent of the selected definition or selection of one of the first ICD source 508, the second ICD source 510, or the third ICD source 512. As a result, because the LNM 518 interacts with the first ICD source 508, the second ICD source 510, or the third ICD source 512 via one of the first to third ICD converters 520, 522, 524, when the model manager 100 modifies one or more of the first ICD source 508, the second ICD source 510, or the third ICD source 512, the LNM 518 is not affected.

[0094] exist Figure 5, the first LNM protocol definition 526 may include the same number and type of attributes and elements as the first ICD protocol definition 514. The information included in the first LNM protocol definition 526 is associated with the same communication protocol as the first ICD protocol definition 514. For example, the first LNM protocol definition 526 may correspond to the A429 communication protocol. For example, the first LNM protocol definition 526 may include language-neutral definitions corresponding to one or more A429 communication ports and / or control logic to implement the A429 communication ports. For example, the first LNM protocol definition 526 may correspond to an A429 terminal system 236 and / or more generally to an A429 terminal system 236. Figure 2 The A429 LRU 234 is associated with a queuing port and / or a sampling port.

[0095] exist Figure 5 , the second LNM protocol definition 528 may include the same number and type of attributes and elements as the second ICD protocol definition 516. The information included in the second LNM protocol definition 528 is associated with the same communication protocol as the second ICD protocol definition 516. For example, the second LNM protocol definition 528 may correspond to the A664 communication protocol. For example, the second LNM protocol definition 528 may include language-neutral definitions corresponding to one or more A664 communication ports and / or control logic to implement the A664 communication ports. For example, the second LNM protocol definition 528 may correspond to a communication protocol that is associated with the first A664 terminal system 214 and / or more generally with the second ICD protocol definition 516. Figure 2 The GPM 204 is associated with a queuing port and / or a sampling port.

[0096] exist Figure 5 In the illustrated example, the language-specific domain 504 includes a first modeling environment 530 and a second modeling environment 532. Alternatively, there may be fewer or more than Figure 5 The first and second modeling environments 530, 532 are depicted in FIG. Figure 5 In the illustrated example, the model manager 100 converts data between the language-neutral domain 506 and the language-specific domain 504 via a first language-specific model (LSM) converter 534, a second LSM converter 536, and a third LSM converter 538. For example, Figure 4 The LSM converter 470 may implement the first to third LSM converters 534, 536, 538. For example, Figure 4The LSM converter 470 of the interface importer 430 can implement the first LSM converter 534 to convert (1) a first LNM protocol definition 526 included in the LNM 518 in the LNM data format specified by the LNM 518 to (2) a first IMA protocol definition 540 included in the first modeling environment 530 in the first LSM data format 542 specified by the first modeling environment 530. In some examples, the interface importer 430 instructs the LSM converter 470 to implement the first through third LSM converters 534, 536, 538.

[0097] In another example, Figure 4 The LSM converter 470 may implement a second LSM converter 536 to convert (1) a second LNM protocol definition 528 included in the LNM 518 in a LNM data format specified by the LNM 518 to (2) a second IMA protocol definition 544 included in the first modeling environment 530 in a first LSM data format 542 specified by the first modeling environment 530. Figure 5 In the example, the first IMA protocol definition 540, the second IMA protocol definition 544, etc. may correspond to Figure 3 IMA application definitions 318 and / or IMA interface definitions 320 .

[0098] In another example, Figure 4 The LSM converter 470 can implement a third LSM converter 538 to convert (1) a second LNM protocol definition 528 included in the LNM 518 in a LNM data format specified by the LNM 518 into (2) a third IMA protocol definition 546 included in the second modeling environment 532 in a second LSM data format 548 specified by the second modeling environment 532.

[0099] exist Figure 5 In the embodiment, the first modeling environment 530 is based on the first LSM data format 542. The first modeling environment 530 is based on the selection of one of the ICD protocol definitions (e.g., the first ICD protocol definition 514, the second ICD protocol definition 516, etc.) and / or the selection of the ICD source (e.g., the first ICD source 508, the second ICD source 510, etc.) defined by the library 550 (e.g., the model library, the model object library, etc.). Figure 5In response to selecting the first ICD source 508, the model manager 100 may convert the first ICD protocol definition 514 to a first LNM protocol definition 526 via the first ICD converter 520. In response to generating the first LNM protocol definition 526, the model manager 100 may convert the first LNM protocol definition 526 to a first IMA protocol definition 540 via the first LSM converter 534. The model manager 100 may generate a library 550 based on the first IMA protocol definition 540.

[0100] exist Figure 5 In the example, the second modeling environment 532 is based on the second LSM data format 548. The second modeling environment 532 is defined by the block definition 552 (e.g., the model block definition, the model block object definition, etc.) based on the selection of one of the ICD protocol definitions (e.g., the first ICD protocol definition 514, the second ICD protocol definition 516, etc.) and / or the selection of the ICD source (e.g., the first ICD source 508, the second ICD source 510, etc.). Figure 5 For example, the model manager 100 may select the second ICD source 510 to generate an IMA model in the second modeling environment 532. In response to selecting the second ICD source 510, the model manager 100 may convert the second ICD protocol definition 516 to a second LNM protocol definition 528 via the second ICD converter 522. In response to generating the second LNM protocol definition 528, the model manager 100 may convert the second LNM protocol definition 528 to a third IMA protocol definition 546 via the third LSM converter 538. The model manager 100 may generate a block definition 552 based on the third IMA protocol definition 546.

[0101] exist Figure 5 In the embodiment, the data format included in the first LNM protocol definition 526 and the second LNM protocol definition 528 is independent of the selection of the first modeling environment 530 or the second modeling environment 532. For example, the information included in the second LNM protocol definition 528 retains the same data format independent of the selection of the first modeling environment 530 or the second modeling environment 532. As a result, because the LNM 518 interacts with the first modeling environment 530 and the second modeling environment 532 via one of the first to third LSM converters 534, 536, 538, when the model manager 100 modifies one or more of the libraries 550 or one or more of the block definitions 552, the LNM 518 is not affected. For example, the model manager 100 may import the second LNM protocol definition 528 into the first modeling environment 530 or the second modeling environment 532 without modifying the second LNM protocol definition 528.

[0102] In some examples, the model manager 100 generates LNM definitions (e.g., first and second LNM protocol definitions 526, 528) using one or more transformation rules. The transformation rules may represent a data structure (e.g., a transformation data structure) including one or more data components that the LNM definition must comply with and / or otherwise satisfy to be stored in the LNM 518. For example, the model manager 100 may convert the first IMA protocol definition 540 to the first LNM protocol definition 526 via the first LSM converter 534. In such an example, the first LSM converter 534 may compare the data structure of one of the first IMA protocol definitions 540 with the transformation rules including the transformation data structure. In response to a data structure that does not match the transformation data structure, the first LSM converter 534 may aggregate the missing data components of the data structure using the existing data components of the data structure and compile the aggregated components into a LNM definition. The first LSM converter 534 may export the LNM definition to the LNM 518 to become part of the first LNM protocol definition 526 and / or the second LNM protocol definition 528.

[0103] Figure 6 is an example implementation of an example representation layer 600 of an example modeling system 602. For example, the modeling system 602 may be an IMA modeling system. Figure 6 The modeled system 602 represents a modeled system of a first system 604 and a second system 606 based on the Open Systems Interconnection (OSI) model, which is a network framework for implementing communication protocols in layers, where control passes from one layer to the next. Figure 6 In the example, the upper layer 608 (e.g., the application layer) emulates the network layer, which provides network services to end-user applications, including protocols that focus on inter-process communication across the network. For example, the upper layer 608 can represent an abstraction of an Ethernet-based protocol (e.g., HTTP packets), a CAN bus protocol (e.g., CAN bus packets), an A429 protocol, etc.

[0104] exist Figure 6 In the network, upper layers 608 exchange data with each other using services provided by presentation layer 600. Presentation layer 600 emulates a network layer responsible for tasks such as handling syntax processing of message data including format conversion, encryption / decryption, etc. to support upper layers 608 above presentation layer 600. Figure 6The presentation layer 600 includes an example MAPOUT abstraction 610 and a corresponding example MAPIN abstraction 612. The MAPOUT abstraction 610 and the MAPIN abstraction 612 are abstractions of parameter data protocol communication blocks that can be included in a model in a modeling environment. For example, the MAPOUT abstraction 610 can be a presentation model block that can be inserted into a model in a modeling environment to enable the model manager 100 to select a presentation style for element names (e.g., Parameter Field Name, Defined Mnemonic Name, Defined Parameter Name, etc.). In such an example, the MAPIN abstraction 612 can obtain the element name from the MAPOUT abstraction 610, which can be presented to the model manager 100, a user of the modeling environment (e.g., a design engineer), etc.

[0105] Figure 6 The representation layer 600 includes an example DECODE abstraction 614 and a corresponding example ENCODE abstraction 616. In some examples, the DECODE abstraction 614 and the ENCODE abstraction 616 manipulate data encoded in a binary frame buffer to bus object elements. For example, the DECODE abstraction 614 and the ENCODE abstraction 616 can be representation model blocks that can be inserted into a model in a modeling environment to implement encoding / decoding of data. For example, the ENCODE abstraction 616 can encode data (e.g., a sensor value) by converting an analog voltage value to a binary value. In such an example, the DECODE abstraction 614 can decode the data by converting a binary value to an analog voltage value.

[0106] exist Figure 6 In the illustrated example, the modeling system 602 includes a lower layer 618 to simulate the transmission of digital data bits using a signaling type supported by a physical medium. For example, the lower layer 618 can include one or more of a session layer, a transport layer, a network layer, a data link layer, or a physical layer. For example, the lower layer 618 can be a simulation of data transmitted by electrical signals, electromagnetic signals, pulses of infrared or ordinary light, etc. For example, the lower layer 618 can be a simulation of data transmitted and / or received via an Ethernet cable, a radio antenna, a fiber optic cable, etc.

[0107] Fig. 7A Describes the process for generating, executing, and verifying Figure 1 The IMA model generation system 700 may be configured to generate a plurality of IMA models 702 associated with the aircraft 108. Fig. 7AIn the example, the IMA model 702 is an IMA LRU model 702. Alternatively, the IMA model 702 may be an IMA GPM model, an IMA ASM model, an IMA network switch model, an IMA RDC model, etc., and / or a combination thereof. Fig. 7A In the embodiment, the plurality of IMA LRU models 702 includes more than 10,000 IMA models. Alternatively, the IMA model generation system 700 may generate less than 10,000 IMA models. Fig. 7A In , the plurality of IMA LRU models 702 include a first IMA model 704. Fig. 7A , the first IMA model 704 is a first IMA LRU model (IMA LRU model 1) 704. For example, the first IMA LRU model 704 may correspond to Figure 2 For example, the first IMA LRU model 704 may simulate an A429 LRU 234, an A664 LRU 224, etc. In another example, one or more of the plurality of IMA LRU models 702 may correspond to an aircraft system 106 and / or more generally, Figure 1 Aircraft 108.

[0108] exist Fig. 7A In the example, the model manager 100 manages the IMA model generation system 700. Fig. 7A In the embodiment of the present invention, the model manager 100 converts information from a first ICD source 508, such as a first ICD protocol definition 514, into a LNM 518 via a first ICD converter 520. Fig. 7A In the example of FIG. 5 , the model manager 100 converts the information from the LNM 518 to the first IMA LRU model 704 in the first modeling environment 530 via the first LSM converter 534. For example, the first LSM converter 534 may convert the information from the LNM 518 into the first IMA LRU model 704 in the first modeling environment 530. Fig. 7A Over 10,000 IMA LRU models profiled.

[0109] exist Fig. 7A In the illustrated example, the model manager 100 generates, executes, and validates a plurality of IMA LRU models 702 including a first IMA LRU model 704. Fig. 7A The first IMA LRU model 704 includes Figure 6 The lower layer 618, the presentation layer 600 and the upper layer 608. Fig. 7A In the example, the lower layer 618 simulates obtaining data from the physical components. Fig. 7A , the lower layer 618 simulates obtaining network data from the example network switch 706. For example, the network switch 706 may correspond to Figure 2 CCR NS 218, NS222, etc. Fig. 7A In the embodiment, the lower layer 618 obtains network data (e.g., communication protocol data packets) from the network switch 706 via the digital communication (COM) read function (FX) 708. Fig. 7A In the example, the digital COM read function 708 is implemented by the first modeling environment 530 using machine-readable instructions to simulate obtaining network data from the network switch 706 and converting the obtained network data into a digital data format, such as a binary data format.

[0110] In some examples, the network switch 706 is simulated. For example, the digital COM reading function 708 can obtain previously recorded network data associated with the network switch 706. For example, the digital COM reading function 708 can read previously recorded and / or simulated communication protocol data packets from a database. In some examples, the network switch 706 is not simulated. For example, the digital COM reading function 708 can read in real time from a database such as Figure 2 CCR NS 218 Physical Devices for Obtaining Network Data.

[0111] exist Fig. 7A , the lower layer 618 simulates obtaining sensor data from an example sensor 710. For example, the sensor 710 may correspond to Figure 2 Sensor 230. Fig. 7A In , the lower layer 618 obtains sensor data (e.g., analog signal, digital signal, etc.) from the sensor 710 via the sensor reading function 711. Fig. 7A In the example, the sensor reading function 711 is implemented by the first modeling environment 530 using machine-readable instructions to simulate obtaining sensor data from the sensor 710 and converting the obtained sensor data into a digital format, such as a binary data format.

[0112] In some examples, the sensor 710 is simulated. For example, the sensor reading function 711 can obtain previously recorded sensor data associated with the sensor 710. For example, the sensor reading function 711 can read previously recorded and / or simulated analog signals, digital signals, etc. from a database. In some examples, the sensor 710 is not simulated. For example, the sensor reading function 711 can read in real time from a database such as Figure 2 The physical device of sensor 230 obtains sensor data.

[0113] exist Fig. 7A In the example, the first IMA LRU model 704 includes a representation layer 600 to facilitate simulation of converting binary data obtained from the lower layer 618 into data in engineering units to be used by the upper layer 608. Fig. 7AIn FIG. 1 , the first IMA LRU model 704 decodes or unpacks the data via an example DECODE function 712. For example, the DECODE function 712 may correspond to Figure 6 DECODE abstraction 614. DECODE function 712 can unpack the network data obtained by digital COM read function 708 to parse included information such as network address, network parameters, payload data, etc.

[0114] exist Fig. 7A In the example, the first IMA LRU model 704 maps the unpacked network data to the IMA protocol definition via the example MAPOUT function 714, such as Figure 5 The first IMA protocol definition 540. For example, the MAPOUT function 714 may correspond to Figure 6 The MAPOUT function 714 may associate or point information included in the unpacked network data to appropriate data fields included in the first IMA protocol definition 540. For example, the MAPOUT function 714 may generate one or more parameters representing attributes with associated values. For example, a parameter may be a value of a network address, a value of a network parameter, a value associated with payload data, etc.

[0115] exist Fig. 7A , the first IMA LRU model 704 converts and / or otherwise scales the binary data to data in engineering units via an engineering unit (EU) scaling function 716. For example, the EU scaling function 716 can convert binary data associated with an analog signal value (e.g., a voltage signal, a current signal, etc.) from the sensor 710 to engineering units associated with a physical parameter range such as pressure (e.g., 0-1000 pounds per square inch (PSI)), speed (e.g., 5000 revolutions per minute (RPM)), position percentage (e.g., 25% open, 75% closed, etc.), flow (e.g., 0-25 gallons per minute), etc.

[0116] exist Fig. 7A In FIG. 6 , the first IMA LRU model 704 uses the engineering unit data from the EU scaling function 716 to execute the control logic via the main function 718, the built-in test (BIT) function 720, and the support function 722 associated with the upper layer 608. Fig. 7A 718 may include one or more control logic routines. For example, the main functions 718 may include executing flap actuation commands, slat actuation commands, etc. of the aircraft 108 based on data obtained from the network switch 706. For example, the main functions 718 may include actuating physical components of the aircraft systems 106 and / or more generally the aircraft 108, such as motors, pumps, solenoids, valves, etc.

[0117] exist Fig. 7A In the example, BIT function 720 may correspond to executing Figure 2 For example, the BIT function 720 can simulate the RDC 226 associated with the BIT function 720. Figure 2 A429 LRU 234 obtains network data from Figure 2 The sensor 230 obtains sensor data, generates and / or transmits control signals to Figure 2 Actuator 232, etc. Fig. 7A In FIG. 7 , BIT function 720 includes remote monitoring function 724 and monitoring function 726. Fig. 7A China, the remote monitoring function 724 simulates obtaining network data from the network switch 706 and transmitting the network data to the Figure 2 The CAN bus 238 network. Fig. 7A , monitoring function 726 simulates obtaining sensor data from sensor 710 and transmitting the sensor data to a Figure 2 CAN bus 238, Figure 2 Networking of NS 222 et al.

[0118] exist Fig. 7A In FIG. 7 , the first IMA LRU model 704 includes a support function 722 to simulate the auxiliary control logic function using the engineering unit data from the EU scaling function 716. Fig. 7A In , support functions 722 include operation state management 728, file system 730, and data loading 732. Fig. 7A In the example, operational state management 728 corresponds to simulation of state information of physical components associated with the first IMA LRU model 704 (such as network switch 706, sensor 710, etc.) based on acquired network data and / or sensor data. Fig. 7A In the example, the file system 730 corresponds to a simulated LRU (such as Figure 2 A429 LRU 234, A664 LRU 224, etc.) operating system simulation. Fig. 7A In the example, data loading 732 corresponds to simulation of state information (such as processor utilization, storage device utilization, memory utilization, etc. of the simulated LRU).

[0119] exist Fig. 7A, the first LSM converter 534 converts one or more DECODE functions 712, MAPOUT functions 714, and / or EU scaling functions 716. For example, the first LSM converter 534 may convert more than 10,000 instances of the DECODE function 712, each instance including parameters associated with the first IMA protocol definition 540. For example, the first LSM converter 534 may convert a first instance of the DECODE function 712 using a first set of parameters based on the first IMA protocol definition 540 corresponding to a first function of the simulated LRU. In such an example, the first LSM converter 534 may convert a second instance of the DECODE function 712 using a second set of parameters based on the first IMA protocol definition 540 corresponding to a second function of the simulated LRU, wherein the first set of parameters is different from the second set of parameters. In such an example, the model manager 100 may generate a plurality of simulated functions that simulate the LRU based on the first IMA protocol definition 540.

[0120] Figure 7B Depicted Fig. 7A A continuation of the IMA model generation system 700. Figure 7B In FIG. 7 , the first IMA LRU model 704 includes an example binary scaling function 734 for converting engineering unit data into binary data. Figure 7B In the example, the first IMA LRU model 704 maps the transformed binary data to the IMA protocol definition, such as Figure 5 The first IMA protocol definition 540. For example, the MAPIN function 736 may correspond to Figure 6 The MAPIN function 736 may associate or direct the information included in the transformed binary to the appropriate data fields included in the first IMA protocol definition 540. For example, the MAPIN function 736 may associate the transformed binary data with the appropriate data fields included in the first IMA protocol definition 540. Figure 3 The IMA application definition 318, IMA interface definition 320, etc. are associated.

[0121] exist Figure 7B In the example, the first IMA LRU model 704 encodes or encapsulates the binary data into the communication protocol data packet via the example ENCODE function 738. For example, the ENCODE function 738 may correspond to Figure 6 ENCODE abstraction 616. ENCODE function 738 can convert binary data processed by upper layer 608 into digital data.

[0122] exist Figure 7BIn FIG. 7 , the first IMA LRU model 704 includes a lower layer 618 for transmitting and / or storing digital data via a digital COM write function 740, a non-volatile memory write function 742, and / or an actuator write function 744. Figure 7B In the example, the digital COM write function 740 is implemented by the first modeling environment 530 using machine readable instructions to simulate opening a network data session, wherein digital data can be written to a communication transmission buffer, wherein the digital data can be packaged and transmitted to the network in a first-in-first-out (FIFO) order. Figure 7B In the non-volatile memory write function 742, the digital data is written to the non-volatile memory. Figure 7B In the embodiment, the actuator write function 744 is implemented by the first modeling environment 530 using machine readable instructions to simulate writing digital data to the actuator buffer, wherein the digital data can be converted into a control signal to control the actuator, such as Figure 2 Actuator 232.

[0123] exist Figure 7B , the first IMA LRU model 704 includes an example COM protocol function 746 to encapsulate digital data into a communication protocol data format (e.g., A429 communication protocol data format, A664 communication protocol data format, etc.) to transmit it to the network via an example COM controller 748. For example, the COM protocol function 746 can encapsulate the digital data into an A429 data packet, and the COM controller 748 can transmit the A429 data packet via the A429 communication protocol.

[0124] exist Figure 7B In the example, the NVM write function 742 transmits the digital data to an example board support package (BSP) driver application programming interface (API) 750. For example, the BSP driver API 750 may implement one or more drivers or middleware to facilitate machine-readable instructions output for hardware. In response to the BSP driver API 750 processing the digital data, the first IMALRU model 704 stores the processed digital data in the NVM flash memory 752. Figure 7B In the embodiment, the actuator write function 744 transmits the digital data to the BSP driver API 750 to convert the digital data into control signals to control the actuator (such as Figure 2 In response to generating the control signal, the first IMA LRU model 704 stores the generated control signal in the NVM flash memory 752.

[0125] exist Figure 7B, the first LSM converter 534 converts one or more binary scaling functions 734, MAPIN functions 736, ENCODE functions 738, digital COM write functions 740, NVM write functions 742, and / or actuator write functions 744. For example, the first LSM converter 534 may convert more than 10,000 instances of the ENCODE function 738, each instance including parameters associated with the first IMA protocol definition 540. For example, the first LSM converter 534 may convert a first instance of the ENCODE function 738 using a first set of parameters based on the first IMA protocol definition 540 corresponding to a first function of the simulated LRU. In such an example, the first LSM converter 534 may convert a second instance of the ENCODE function 738 using a second set of parameters based on the first IMA protocol definition 540 corresponding to a second function of the simulated LRU, wherein the first set of parameters is different from the second set of parameters. In such an example, the model manager 100 may generate a plurality of simulated functions of the simulated LRU based on the first IMA protocol definition 540.

[0126] Figure 7C The model manager 100 generates and Figure 5 The first modeling environment 530 is associated with a library 550. Figure 7C In the illustrated example, the model manager 100 selects and / or otherwise determines a modeling environment to be deployed. Figure 7C In the model manager 100, select Figure 5 The first modeling environment 530 generates an example IMA system model 754. For example, the IMA system model 754 may include multiple IMA LRU models 702, including Fig. 7A and Figure 7B The first IMA LRU model 704.

[0127] exist Figure 7CIn the illustrated example of , the first modeling environment 530 includes an example IMA bus structure 756, which includes IMA bus elements 758. The IMA bus structure 756 is a bus object that specifies architectural properties of a simulated communication bus, which is different from the values ​​of signals facilitated by the simulated communication bus. For example, the IMA bus structure 756 can specify the number of elements in the bus, the order of the elements, whether and how the elements are nested, the data types of corresponding signals, etc. For example, the model manager 100 can create the IMA bus structure 756 for simulating the organization, syntax, or structure of an aircraft communication protocol such as ARINC 429, ARINC 664, etc. For example, the IMA bus structure 756 can correspond to the structure of ARINC 664, where the IMA bus element 758 corresponds to the definition or attribute of the ARINC 664 bus signal (e.g., the value of the ARINC 664 bus signal, the unit of measurement, etc.).

[0128] exist Figure 7C In the example, the first modeling environment 530 includes an ICD bus structure 760, which includes an example ICD bus element 762. The ICD bus structure 760 is a bus object that is based on the data stored in the data source domain 502 (such as Figure 5 The architecture properties of the simulated communication bus are specified by using the properties in the first ICD source 508). Figure 7C , the ICD bus structure 760 includes an ICD bus element 762 to map information included in the data source domain 502 to information included in the first modeling environment 530. For example, the model manager 100 may populate data included in the IMA bus element 758 using data included in the ICD bus element 762. For example, the model manager 100 may populate a first IMA bus element 764 included in the IMA bus element 758 using data included in a first ICD bus element 766 included in the ICD bus element 762.

[0129] In operation, the model manager 100 generates the IMA system model 754 by importing the information included in the LNM 518. Figure 7C In the example, the model manager 100 determines that the first modeling environment 530 will be used to generate the IMA system model 754. For example, the model manager 100 may select a data source such as Figure 5 The model manager 100 retrieves the first ICD source 508 to retrieve information for generating the IMA system model 754. The model manager 100 executes the first instructions 768 to transform and / or otherwise convert (1) the first LNM protocol definition 526 (which is based on the first ICD protocol definition 514 retrieved from the first ICD source 508) to (2) the first IMA protocol definition 540.

[0130] exist Figure 7CIn the example, the model manager 100 executes the second instructions 770 to generate the IMA bus structure 756 and the ICD bus structure 760. For example, the model manager 100 may direct the first modeling environment 530 to execute the second instructions 770 within the first modeling environment 530. In response to generating the IMA bus structure 756 and the ICD bus structure 760, the model manager 100 executes the third instructions 772 to initialize or start the first modeling environment 530. For example, the model manager 100 may direct the first modeling environment 530 to execute the third instructions 772 within the first modeling environment 530.

[0131] exist Figure 7C In the illustrated example, in response to initializing the first modeling environment 530, the model manager 100 executes fourth instructions 774 to generate based on the first LNM protocol definition 526 included in the LNM 518 Figure 5 Library 550. Figure 7C , libraries 550 include an example IMA MAPIN model library (ML) 775, an example IMA ENCODE model library 776, an example IMA DECODE model library 777, and an example IMA MAPOUT model library 778. Each of libraries 550 may include a plurality of IMA models, IMA model objects, IMA definitions, and the like.

[0132] exist Figure 7C , fourth instruction 774 converts first LNM protocol definition 526 into first IMA protocol definition 540. For example, when applicable, model manager 100 may direct first modeling environment 530 to import IMA models, IMA model objects (e.g., IMA application model objects 314, IMA interface model objects 316, etc.), IMA definitions (e.g., IMA application definitions 318, IMA interface definitions 320, etc.), etc. included in model library 550 into first modeling environment 530.

[0133] exist Figure 7C In the example, fourth instructions 774 generate IMA model objects 780, which include example IMA MAPIN model object 781, example IMA ENCODE model object 782, example DECODE model object 783, and example MAPOUT model object 784. In some examples, fourth instructions 774 are executed in response to user input. For example, in response to user input, fourth instructions 774 can generate one or more of IMA model objects 780. Figure 7C In the example, the IMA model object 780 corresponds to Figure 6 For example, the IMA MAPIN model object 781 may correspond to Figure 6 MapIn Abstract 612. Figure 7CIn the example, each of the IMA model objects 780 includes corresponding parameter information. For example, the IMA MAPIN model object 781 may include a corresponding parameter definition (e.g., Figure 3 One or more parameter identifiers of the parameter definition 311a, 311b).

[0134] exist Figure 7C In the illustrated example of , the model manager 100 generates the IMA system model 754 by importing one or more of the plurality of IMA LRU models 702 including the first IMA LRU model 704. Figure 7C , the model manager 100 generates each of the plurality of IMA LRU models 702 by importing model objects from the library 550 via the first library link 786. For example, the model manager 100 may instruct the first modeling environment 530 to import the first IMA LRU model 704 via the first library link 786 using the corresponding IMA model objects associated with the lower layer 618, the presentation layer 600, and the upper layer 608 from the library 550. Figure 7C In , the model manager 100 imports a plurality of IMA LRU models 702, wherein the lower layer 618, the presentation layer 600, and the upper layer 608 include corresponding first IMA protocol definitions 540. Figure 7C In the example, the library 550 is generated based on importing information from the IMA model object 780 via the second library link 788 .

[0135] exist Figure 7C In the illustrated example, the model manager 100 validates the IMA system model 754 based on comparing one or more attributes included in the IMA system model 754 to one or more attributes included in the IMA bus element 758, the ICD bus element 762, etc. For example, the IMA system model 754 may correspond to the aircraft system 106 and / or more generally Figure 1 The lower layer 618, the representation layer 600, and the upper layer 608 of the first IMA LRU model 704 are coupled together with the IMA bus structure 756. Figure 7C , the model manager 100 verifies whether the IMA bus structure 756 coupling the lower layer 618, the presentation layer 600, and the upper layer 608 of the first IMA LRU model 704 includes the properties specified by the ICD bus structure 760. For example, the model manager 100 may compare the properties of one of the parameters included in the lower layer 618 with the properties included in the ICD bus element 762. In response to determining that the IMA bus structure 756 does not have one or more of the properties specified by the ICD bus element 766 based on the comparison, the first modeling environment 530 stops the operation of the IMA system model 754 and generates an error message, an alarm, etc.

[0136] Figure 8-Figure 11 The method for implementing Figure 4 The model manager 100 is a flowchart representation of example hardware logic or machine readable instructions. The machine readable instructions may be a program or a portion of a program for use by a processor (such as the following in conjunction with Fig.12 The program may be embodied in software stored on a non-transitory computer-readable storage medium such as a CD-ROM, floppy disk, hard drive, DVD, Blu-ray disk, or memory associated with the processor 1212, but the entire program and / or portions thereof may alternatively be executed by a device other than the processor 1212 and / or embodied in firmware or dedicated hardware. In addition, although reference is made to Figure 8-Figure 11 The flowcharts illustrated in describe example procedures, and many other methods of implementing the model manager 100 may alternatively be used. For example, the order of execution of the blocks may be changed, and / or some of the blocks described may be changed, eliminated, or combined. Additionally or alternatively, any or all of the blocks may be implemented by one or more hardware circuits (e.g., discrete and / or integrated analog and / or digital circuits, FPGAs, ASICs, comparators, operational amplifiers (op-amps), logic circuits, etc.) constructed to perform corresponding operations without executing software or firmware.

[0137] As described above, the present invention may be implemented using executable instructions (e.g., computer and / or machine readable instructions) stored on a non-transitory computer and / or machine readable medium (e.g., a hard drive, flash memory, read-only memory, compact disk, digital versatile disk, cache, random access memory, and / or any other storage device or storage disk). Figure 8-Figure 11 processing, where the information is stored for any duration (e.g., for an extended period of time, permanently, for a transient instance, for temporary buffering, and / or for caching of information). As used herein, the term non-transitory computer readable medium is expressly defined to include any type of computer readable storage device and / or storage disk and to exclude propagating signals and to exclude transmission media.

[0138] As used herein, "including and comprising" (and all forms and tenses thereof) are used as open-ended terms. Thus, whenever a claim adopts any form of "including" (e.g., includes, including, comprise, comprising, having, etc.) as a preamble or in any type of claim, it should be understood that additional elements, terms, etc. may be present without falling outside the scope of the corresponding claim or recitation. As used herein, when the phrase "at least" is used as a transitional term, such as in the preamble of a claim, it is open-ended in the same manner as the term "comprising." The term "and / or," for example, when used in a form such as A, B, and / or C, refers to any combination or subset of A, B, C, such as (1) A alone, (2) B alone, (3) C alone, (4) A and B, (5) A and C, and (6) B and C.

[0139] Figure 8 It means that Figure 1 and Figure 3-7C The example method 800 performed by the model manager 100 to generate Figure 1 The method 800 begins at block 802, where the model manager 100 selects a modeling environment. For example, the modeling environment selector 410 may determine to use Figure 5 The first modeling environment 530 is used to generate Figure 7C 754 of the IMA system model.

[0140] At block 804, the model manager 100 selects (one or more) data sources to be processed. For example, the data source selector 420 may determine the data source to be processed using Figure 5 The first ICD source 508. At block 806, the model manager 100 imports the definition into the modeling environment. For example, the interface importer 430 can import information from the data source domain 502 into the language specific domain 504 via the language neutral domain 506. Fig. 9 An example process that may be used to implement block 806 is described.

[0141] At block 808, the model manager 100 imports the model object(s) into the modeling environment. For example, the model object handler 450 may import the model object(s) into the modeling environment. Figure 7A-7B The functions associated with the lower layer 618, the presentation layer 600, the upper layer 608, etc. of the first modeling environment 530 are imported to generate the first IMA LRU model 704. For example, the model object handler 450 can import the digital COM reading function 708, the sensor reading function 711, etc. into the first modeling environment 530. Fig. 7AIn another example, the model object handler 450 may import the DECODE function 712, the MAPOUT function 714, etc. into the Fig. 7A In the presentation layer 600.

[0142] At block 810, the model manager 100 configures (one or more) model objects. For example, the model object handler 450 may configure one or more definitions included in the first IMA protocol definition 540, the second IMA protocol definition 544, etc. Fig.10 An example process that may be used to implement block 810 is described.

[0143] At block 812, the model manager 100 determines whether to generate another IMA model. For example, the model object handler 450 may determine to generate a second IMA LRU model included in the plurality of IMA LRU models 702, a third IMA LRU model included in the plurality of IMA LRU models 702, and so on.

[0144] If at block 812, the model manager 100 determines to generate another IMA model, then control returns to block 808 to import (one or more) model objects into the modeling environment to generate another IMA model. If at block 812, the model manager 100 determines not to generate another IMA model, then at block 814, the model manager 100 generates an IMA system model. For example, the model object handler 450 may generate a plurality of IMA LRU models 702 by generating Figure 7C 754 of the IMA system model.

[0145] At block 816, the model manager 100 validates the IMA system model. For example, the interface validator 480 may execute the IMA system model 754, compare outputs of the IMA system model 754 to validation outputs (e.g., validation thresholds, validation rules, etc.), and validate the IMA system model 754 based on the outputs matching and / or otherwise satisfying the validation outputs. In another example, the interface validator 480 may validate the IMA system model 754 by comparing one or more attributes included in the IMA system model 754 to one or more attributes included in the IMA bus element 758, the ICD bus element 762, etc., and validate the IMA system model 754 based on the comparison. For example, the one or more attributes included in the IMA system model 754 may correspond to attributes of some of the first IMA protocol definition 540.

[0146] At block 818, the model manager 100 determines whether the validation was successful. For example, the interface validator 480 may determine that the IMA system model 754 does not conform to one or more IMA definition rules based on a comparison of one or more attributes included in the IMA system model 754 with one or more attributes included in the IMA bus element 758, the ICD bus element 762, etc.

[0147] If at block 818, the model manager 100 determines that the validation was unsuccessful, control returns to block 810 to reconfigure the model object. If at block 818, the model manager 100 determines that the validation was successful, at block 820, the model manager 100 generates output. For example, the interface exporter 440 may generate and deploy machine-readable instructions associated with the IMA system model 754 to the aircraft system 106 to be executed and / or more generally Figure 1 For example, the aircraft 108 may be operated by executing machine-readable instructions based on the IMA system model 754. In another example, the interface exporter 440 may generate and deploy supply chain and / or manufacturing build instructions based on the IMA system model 754 to activate the aircraft system 106 and / or more generally Figure 1 The production of aircraft 108. Fig.11 An example process that can be used to implement block 820 is described. In response to generating an output, Figure 8 The method 800 ends.

[0148] Fig. 9 It means that Figure 1 and Figure 3-7C Flowchart of an example method 900 performed by the model manager 100 to import definitions into a modeling environment. Fig. 9 The process can be used to implement Figure 8 The method 900 begins at block 902 where the model manager 100 selects an ICD definition to import. For example, the data source selector 420 may select the first ICD protocol definition 514 of the first ICD source 508 to import.

[0149] At block 904, the model manager 100 converts the ICD definition to a LNM definition. For example, the ICD converter 460 may implement the first ICD converter 520 to convert the first ICD protocol definition 514 to a LNM definition. Figure 5 The LNM 518 includes a first LNM protocol definition 526 .

[0150] At block 906, the model manager 100 validates the LNM definition. For example, the interface validator 480 may compare the first LNM protocol definition 526 to one or more LNM definition rules and validate the first LNM protocol definition 526 based on the comparison.

[0151] At block 908 , the model manager 100 determines whether the validation was successful.For example, the interface validator 480 may determine that the first LNM protocol definition 526 is validated based on the first LNM protocol definition 526 adhering to and / or otherwise satisfying one or more LNM definition rules.

[0152] If at block 908, the model manager 100 determines that the validation is unsuccessful, control proceeds to block 916 to generate an alarm. If at block 908, the model manager 100 determines that the validation is successful, at block 910, the model manager 100 converts the LNM definition to an IMA definition. For example, the LSM converter 470 may implement the first LSM converter 534 to convert the first LNM protocol definition 526 to the first IMA protocol definition 540.

[0153] At block 912, the model manager 100 validates the IMA definition. For example, the interface validator 480 may compare the first IMA protocol definition 540 to one or more IMA definition rules and validate the first IMA protocol definition 540 based on the comparison.

[0154] At block 914 , the model manager 100 determines whether the validation was successful.For example, the interface validator 480 may determine that the first IMA protocol definition 540 is validated based on the first IMA protocol definition 540 adhering to and / or otherwise satisfying one or more IMA definition rules.

[0155] If at block 914, the model manager 100 determines that the validation was unsuccessful, control proceeds to block 916 to generate an alert. For example, the interface validator 480 may generate an alert and display the alert on the user interface to notify the user that the validation was unsuccessful. In response to generating the alert, Fig. 9 Method 900 returns to Figure 8 Block 808 of the example may be to import the model object(s) into the modeling environment to generate the IMA model.

[0156] If at block 914, the model manager 100 determines that the validation is successful, control proceeds to block 918 to generate a modeling environment model library. For example, in response to generating the first IMA protocol definition 540, the interface importer 430 may generate Figure 5 The library is 550.

[0157] At block 920, the model manager 100 generates a model object. For example, in response to generating the library 550, the interface importer 430 may generate Figure 7C The IMA model object 780. In response to generating the model object, Fig. 9 Method 900 returns to Figure 8 Block 808 of the example may be to import the model object(s) into the modeling environment to generate the IMA model.

[0158] Fig.10 It means that Figure 1 and Figure 3-7C Flowchart of an example method 1000 that the model manager 100 performs to configure (one or more) model objects. Fig.10 The process can be used to implement Figure 8 The method 1000 begins at block 1002, where the model manager 100 selects a model object for processing. For example, the model object handler 450 may select Fig. 7A The DECODE function 712 is used for processing.

[0159] At block 1004, the model manager 100 selects a definition to process. For example, the model object handler 450 may select a first of the first IMA protocol definitions 540 for processing, such as in Figure 3 The IMA interface definition 320 includes the “TX_COM_PORT 10121” IMA interface definition.

[0160] At block 1006, the model manager 100 processes the definitions. For example, the model object handler 450 may add, delete, or modify one of the first IMA protocol definitions 540. For example, the model object handler 450 may modify the first IMA protocol definitions 540. Figure 3 The IMA interface definition 320 includes information associated with the “TX_COM_PORT10121” IMA interface definition.

[0161] At block 1008, the model manager 100 determines whether to select another definition for processing. For example, the model object handler 450 may determine to select the second of the first IMA protocol definitions 540 for processing.

[0162] If at block 1008, the model manager 100 determines to select another definition for processing, control returns to block 1004 to select another definition for processing. If at block 1008, the model manager 100 determines not to select another definition for processing, at block 1010, the model manager 100 validates the model object using the IMA definition rules. For example, the interface validator 480 may compare one or more of the first IMA protocol definitions 540 to one or more IMA definition rules.

[0163] At block 1012 , the model manager 100 determines whether the validation was successful. For example, the interface validator 480 may determine that one or more of the first IMA protocol definitions 540 conform to and / or otherwise satisfy one or more IMA definition rules.

[0164] If at block 1012, the model manager 100 determines that validation was unsuccessful, control returns to block 1004 to select a definition for processing. For example, the model object handler 450 may select a definition that failed validation. If at block 1012, the model manager 100 determines that validation was successful, at block 1014, the model manager 100 generates an IMA bus element. For example, the model manager 100 may generate a first IMA bus element 764 and associate the first IMA bus element 764 with the DECODE function 712.

[0165] At block 1016, the model manager 100 selects another model object to process. For example, the model object handler 450 may determine to select Fig. 7A MAPOUT function 714 is selected for processing. If at block 1016, the model manager 100 determines to select another model object for processing, control returns to block 1002 to select another model object for processing. If at block 1016, the model manager 100 determines not to select another model object for processing, then Fig.10 Method 1000 returns to Figure 8 Block 812 of the example determines whether to generate another IMA model.

[0166] Fig.11 It means that Figure 1 and Figure 3-7C Flowchart of an example method 1100 that the model manager 100 performs to generate output. Fig.11 The process can be used to implement Figure 8 The method 1100 begins at block 1102, where the model manager 100 generates a language neutral model (LNM) definition using transformation rules. For example, the interface exporter 440 may be based on Figure 7CThe IMA system model 754 includes the first IMA protocol definition 540 generated Figure 5 The first LNM protocol definition 526 is used to be exported to Figure 5 LNM 518.

[0167] At block 1104, the model manager 100 generates machine-readable instructions. For example, the interface exporter 440 may generate instructions corresponding to Figure 7C The IMA system model 754 includes computer executable code for executing the plurality of IMA LRU models 702 .

[0168] At block 1106, the model manager 100 generates supply chain building instructions. For example, the interface exporter 440 may generate Figure 1 The output 124 may include instructions executed by the supply chain computing system to initiate the sequencing of components, labor allocation, etc., to construct a Figure 7C The IMA system model 754 is associated with the aircraft system (e.g., Figure 1 Aircraft system 106).

[0169] At block 1108, the model manager 100 generates manufacturing build instructions. For example, the interface exporter 440 may generate Figure 1 The output 124 of the manufacturing computing system may include instructions executed by the manufacturing computing system to initiate component manufacturing, labor allocation, etc., to build a Figure 7C The IMA system model 754 is associated with the aircraft system (e.g., Figure 1 Aircraft system 106).

[0170] At block 1110 , the model manager 100 exports the LNM definition to the LNM. For example, the interface exporter 440 can export the first LNM protocol definition 526 to the LNM 518 , which can be used by other IMA models, other IMA system models, etc. In such an example, the interface exporter 440 can direct the first LNM protocol definition 526 to be converted to the first ICD protocol definition 514 via the first ICD converter 520 .

[0171] At block 1112, the model manager 100 deploys the machine-readable instructions to the vehicle and / or vehicle simulator. For example, the interface exporter 440 may deploy the machine-readable instructions to Figure 1 Aircraft systems 106 and / or aircraft 108 may be performed by aircraft systems 106 and / or aircraft 108 .

[0172] At block 1114, the model manager 100 initiates production of the vehicle associated with the IMA system model. For example, the interface exporter 440 may initiate production of the aircraft system 106, the aircraft 108, etc. associated with the IMA system model 754. In response to initiating production of the vehicle associated with the IMA system model, the method 1100 returns to Figure 8 The example ends with .

[0173] Fig.12 is constructed to execute Figure 8-Figure 11 Instructions to achieve Figure 1 and Figure 3-7C 1 is a block diagram of a processor platform 1200 of the model manager 100. The processor platform 1200 may be, for example, a server, a personal computer, a workstation, a self-learning machine (e.g., a neural network), or any other type of computing device.

[0174] The processor platform 1200 of the illustrated example includes a processor 1212. The processor 1212 of the illustrated example is hardware. For example, the processor 1212 may be implemented by one or more integrated circuits, logic circuits, microprocessors, GPUs, DSPs, or controllers from any desired family or manufacturer. The hardware processor may be a semiconductor-based (e.g., silicon-based) device. In this example, the processor 1212 implements Figure 4 The modeling environment selector 410, data source selector 420, interface importer 430, interface exporter 440, model object handler 450, ICD converter 460, LSM converter 470, interface validator 480 and report generator 490.

[0175] The processor 1212 of the illustrated example includes a local memory 1213 (e.g., a cache). The processor 1212 of the illustrated example communicates with a main memory including a volatile memory 1214 and a non-volatile memory 1216 via a bus 1218. The volatile memory 1214 may be comprised of synchronous dynamic random access memory (SDRAM), dynamic random access memory (DRAM), Dynamic Random Access Memory The non-volatile memory 1216 may be implemented by flash memory and / or any other desired type of memory device. Access to the main memory 1214, 1216 is controlled by a memory controller.

[0176] The processor platform 1200 of the illustrated example also includes an interface circuit 1220. The interface circuit 1220 may be implemented by any type of interface standard (such as an Ethernet interface, a universal serial bus (USB), interface, near field communication (NFC) interface and / or PCI express interface).

[0177] In the illustrated example, one or more input devices 1222 are connected to the interface circuit 1220. The input device(s) 1222 allow a user to enter data and / or commands into the processor 1212. The input device(s) may be implemented by, for example, an audio sensor, microphone, camera (still or video), keyboard, buttons, mouse, touch screen, track pad, trackball, isopoint device, and / or voice recognition system.

[0178] One or more output devices 1224 are also connected to the interface circuit 1220 of the illustrated example. The output device 1224 can be implemented, for example, by a display device (e.g., a light emitting diode (LED), an organic light emitting diode (OLED), a liquid crystal display (LCD), a cathode ray tube display (CRT), an in-plane switching (IPS) display, a touch screen, etc.), a tactile output device, a printer, and / or a speaker. Therefore, the interface circuit 1220 of the illustrated example typically includes a graphics driver card, a graphics driver chip, and / or a graphics driver processor.

[0179] The interface circuitry 1220 of the illustrated example also includes communication devices, such as transmitters, receivers, transceivers, modems, residential gateways, wireless access points, and / or network interfaces to facilitate data exchange with external machines (e.g., any type of computing device) via network 1226. Communications may be via, for example, an Ethernet connection, a digital subscriber line (DSL) connection, a telephone line connection, a coaxial cable system, a satellite system, a line-of-site wireless system, a cellular telephone system, etc.

[0180] The processor platform 1200 of the illustrated example also includes one or more mass storage devices 1228 for storing software and / or data. Examples of such mass storage devices 1228 include floppy disk drives, hard disk drives, compact disk drives, Blu-ray disk drives, redundant array of independent disks (RAID) systems, and digital versatile disk (DVD) drives.

[0181] Figure 8-Figure 11 The machine executable instructions 1232 may be stored in the mass storage device 1228, in the volatile memory 1214, in the non-volatile memory 1216, and / or on a removable, non-transitory computer-readable storage medium (such as a CD or DVD).

[0182] As can be appreciated from the foregoing, example systems, methods, apparatus, and articles of manufacture for generating an integrated modular architecture model have been disclosed. The model manager apparatus described herein generates abstractions of aircraft components and systems for generating an IMA model in a computer modeling environment. The model manager apparatus described herein stores definitions in an interface control data source to facilitate reuse of abstractions between IMA models. The model manager apparatus described herein converts information included in an interface control data source to a computer modeling environment via a language-neutral model.

[0183] The examples described herein reduce the time to generate an IMA model compared to previous examples due to the ability of the model manager device to import a previously defined or generated IMA model into a new IMA model. The examples described herein reduce the storage capacity required to generate an IMA model corresponding to a vehicle, such as an aircraft, due to the reduction in the number of unique IMA models required to generate the vehicle IMA model. Compared to previous examples that required different databases to facilitate mapping information between disparate data sources, the examples described herein improve database efficiency by using a language-neutral model database to facilitate data conversion between disparate data formatting information storage systems.

[0184] Furthermore, the present disclosure includes embodiments according to the following embodiments:

[0185] Embodiment 1 includes a device, which includes an interface importer, which is used to import a first integrated modular architecture (IMA) protocol definition into a first computer modeling environment to generate multiple libraries based on the first IMA protocol definition, and generate multiple IMA model objects based on the multiple libraries; a model object handler, which imports some of the multiple IMA model objects into the first computer modeling environment to generate a first IMA model of an aircraft system corresponding to the aircraft, and generates an IMA system model corresponding to the aircraft by generating multiple IMA models including the first IMA model; an interface verifier, which verifies the IMA system model by comparing the output of the IMA system model with the verification output; an interface exporter, when the IMA system model is verified, which is used to generate manufacturing build instructions for the aircraft system; and a report generator, which is used to start production of the aircraft system based on the manufacturing build instructions.

[0186] Embodiment 2 includes the apparatus of embodiment 1, wherein the first IMA protocol definition includes at least one of interface information, requirement information, or specification information associated with an aircraft system.

[0187] Embodiment 3 includes the apparatus of embodiment 1, wherein the interface importer imports the first IMA protocol definition by the following operations: instructing an interface control database (ICD) converter to use a first ICD converter to transform a first ICD protocol definition included in a first ICD source into a first language neutral model (LNM) protocol definition included in an LNM, and instructing a language specific model (LSM) converter to use a first LSM converter to transform the first LNM protocol definition into a first IMA protocol definition included in a first modeling environment.

[0188] Embodiment 4 includes the apparatus of embodiment 1, wherein the first IMA model comprises a lower layer, a presentation layer, and an upper layer, the lower layer comprising at least one of a digital communication reading function or a sensor reading function.

[0189] Embodiment 5 includes the apparatus of embodiment 4, wherein the interface verifier verifies the IMA system model by at least one of the following operations: obtaining network data from a network switch in real time via a digital communication read function or obtaining sensor data from a sensor in real time via a sensor read function.

[0190] Embodiment 6 includes the apparatus of embodiment 1, wherein the interface exporter generates machine-readable instructions based on the IMA system model, deploys the machine-readable instructions to at least one of the aircraft system or the aircraft, and causes operation of at least one of the aircraft system or the aircraft based on the machine-readable instructions.

[0191] Embodiment 7 includes a method, including importing a first integrated modular architecture (IMA) protocol definition into a first computer modeling environment to generate a plurality of libraries based on the first IMA protocol definition, generating a plurality of IMA model objects based on the plurality of libraries, importing some of the plurality of IMA model objects into the first computer modeling environment to generate a first IMA model of an aircraft system corresponding to the aircraft, generating an IMA system model corresponding to the aircraft by generating a plurality of IMA models including the first IMA model, validating the IMA system model by comparing an output of the IMA system model with a validation output, in response to validating the IMA system model based on the comparison, generating manufacturing build instructions for the aircraft system, and initiating production of the aircraft system based on the manufacturing build instructions.

[0192] Embodiment 8 includes the method of embodiment 7, wherein the first IMA protocol definition includes at least one of interface information, requirement information, or specification information associated with the aircraft system.

[0193] Embodiment 9 includes the method of embodiment 7, wherein importing the first IMA protocol definition includes converting a first interface control database (ICD) protocol definition included in a first ICD source into a first language neutral model (LNM) protocol definition included in an LNM using a first ICD converter, and converting the first LNM protocol definition into a first IMA protocol definition included in a first modeling environment using a first language specific model (LSM) converter.

[0194] Embodiment 10 includes the method of embodiment 9, further comprising comparing some of the first LNM protocol definitions to at least one LNM definition rule and validating the first LNM protocol definitions based on the comparison, and comparing some of the first IMA protocol definitions to at least one IMA definition rule and validating the first IMA protocol definitions based on the comparison.

[0195] Embodiment 11 includes the method of embodiment 7, wherein the first IMA model comprises a lower layer, a presentation layer, and an upper layer, the lower layer comprising at least one of a digital communication reading function or a sensor reading function.

[0196] Embodiment 12 includes the method of embodiment 11, wherein validating the IMA system model comprises at least one of obtaining network data in real time from a network switch via a digital communication read function or obtaining sensor data in real time from a sensor via a sensor read function.

[0197] Embodiment 13 includes the method of embodiment 7, further comprising generating machine readable instructions based on the IMA system model, deploying the machine readable instructions to at least one of the aircraft system or the aircraft, and causing operation of at least one of the aircraft system or the aircraft based on the machine readable instructions.

[0198] Embodiment 14 includes a non-transitory computer-readable storage medium including instructions that, when executed, cause a machine to at least import a first integrated modular architecture (IMA) protocol definition into a first computer modeling environment to generate a plurality of libraries based on the first IMA protocol definition, generate a plurality of IMA model objects based on the plurality of libraries, import some of the plurality of IMA model objects into the first computer modeling environment to generate a first IMA model of an aircraft system corresponding to the aircraft, generate an IMA system model corresponding to the aircraft by generating a plurality of IMA models including the first IMA model, validate the IMA system model by comparing an output of the IMA system model with a validation output, generate manufacturing build instructions for the aircraft system when the IMA system model is validated based on the comparison, and initiate production of the aircraft system based on the manufacturing build instructions.

[0199] Embodiment 15 includes the non-transitory computer-readable storage medium of embodiment 14, wherein the first IMA protocol definition includes at least one of interface information, requirement information, or specification information associated with an aircraft system.

[0200] Embodiment 16 includes the non-transitory computer-readable storage medium of embodiment 14, and further includes instructions which, when executed, cause the machine to at least utilize a first ICD converter to convert a first interface control database (ICD) protocol definition included in a first ICD source into a first language neutral model (LNM) protocol definition included in an LNM, and utilize a first language specific model (LSM) converter to convert the first LNM protocol definition into a first IMA protocol definition included in a first modeling environment.

[0201] Embodiment 17 includes the non-transitory computer-readable storage medium of embodiment 16, further comprising instructions that, when executed, cause the machine to at least compare one of the first LNM protocol definitions to the LNM definition rules and validate the first LNM protocol definition based on the comparison and compare one of the first IMA protocol definitions to the IMA definition rules and validate the first IMA protocol definition based on the comparison.

[0202] Embodiment 18 includes the non-transitory computer-readable storage medium of embodiment 14, wherein the first IMA model comprises a lower layer, a representation layer, and an upper layer, the lower layer comprising at least one of a digital communication reading function or a sensor reading function.

[0203] Embodiment 19 includes the non-transitory computer-readable storage medium of embodiment 18, and further includes instructions which, when executed, cause the machine to obtain network data in real time from a network switch via a digital communication reading function or obtain sensor data in real time from a sensor via a sensor reading function.

[0204] Embodiment 20 includes the non-transitory computer-readable storage medium of embodiment 14, and further includes instructions that, when executed, cause a machine to generate machine-readable instructions based at least on the IMA system model, deploy the machine-readable instructions to at least one of the aircraft system or the aircraft, and cause operation of at least one of the aircraft system or the aircraft based on the machine-readable instructions.

[0205] Although certain example systems, methods, devices, and articles have been disclosed herein, the scope of coverage of this patent is not limited thereto. Instead, this patent covers all systems, methods, devices, and articles that fully fall within the scope of the claims of this patent.

Claims

1. A device comprising: a memory including instructions; and at least one processor configured to execute instructions to at least: importing an interface control database (ICD) protocol definition associated with a communication protocol for a first aircraft system of the aircraft from an ICD source into a language neutral model (LNM), the ICD protocol definition corresponding to at least one control logic function or configuration parameter used by the communication protocol, the LNM corresponding to a model and computer modeling environment that uses a data format or data structure that is different from the ICD source, the LNM including a LNM protocol definition corresponding to the at least one control logic function or the configuration parameter, the ICD protocol definition being based on a first data format that is different from a second data format of the LNM protocol definition; converting at least one of the LNM protocol definitions to an Integrated Modular Architecture (IMA) protocol definition having a third data format of the computer modeling environment, the IMA protocol definition corresponding to at least one of the control logic function or the configuration parameter, the third data format being different from the first data format and the second data format; importing the IMA protocol definition into the computer modeling environment to generate a plurality of model libraries based on the IMA protocol definition; generating a plurality of IMA model objects based on the plurality of model libraries, the plurality of IMA model objects including a first IMA model object, the first IMA model object being used to simulate an operation of the first aircraft system based on the first aircraft system using the communication protocol; importing at least one of the plurality of IMA model objects into the computer modeling environment to generate a plurality of IMA models including a first IMA model, the first IMA model including the first IMA model object, the first IMA model for simulating operation of one or more aircraft systems of the aircraft based on one or more aircraft systems using the communication protocol, wherein the one or more aircraft systems include a first aircraft system; generating an IMA system model based on the plurality of IMA models, the IMA system model being used to simulate the operation of an aircraft using the communication protocol; validating the IMA system model by comparing a first output of the IMA system model to a validation output, the validation output corresponding to an expected output of the one or more aircraft systems; generating manufacturing build instructions for the first aircraft system in response to validating the IMA system model based on a comparison of the first output and the validation output; and The manufacturing build instructions are transmitted to a computing system to initiate production of the first aircraft system based on the manufacturing build instructions.

2. The device (100) according to claim 1, wherein: The first IMA protocol definition (540) includes at least one of interface information, requirement information, or specification information associated with at least one of the communication protocol or the first aircraft system.

3. The device according to claim 1, wherein: At least one processor executes instructions to: instructing the ICD to convert the ICD protocol definition contained in the ICD source into the LNM protocol definition contained in the LNM; and A language specific model (LSM) converter is directed to convert a plurality of the LNM protocol definitions into the IMA protocol definitions, a second data format of the LNM based on a first modeling language, and a third data format based on a second modeling language different from the first modeling language.

4. The device according to claim 1, wherein: The first IMA model includes one or more IMA model objects for implementing a lower layer, a presentation layer, and an upper layer, the lower layer including a second IMA model object that implements at least one of a digital communication reading function or a sensor reading function.

5. The apparatus of claim 4 , wherein the first aircraft system comprises a physical network switch and a physical sensor, the at least one processor communicates with the physical network switch and the physical sensor, and the at least one processor executes instructions to validate the IMA system model based on at least one of obtaining network data from the physical network switch via the digital communication read function or obtaining sensor data from the physical sensor via the sensor read function.

6. The device according to claim 1, wherein: The at least one processor executes instructions to: generating machine-readable instructions based on the IMA system model; deploying the machine-readable instructions to at least one of the first aircraft system or the aircraft; and Operation of at least one of the first aircraft system or the aircraft (108) is caused based on the machine-readable instructions.

7. A method comprising: importing an interface control database (ICD) protocol definition associated with a communication protocol for a first aircraft system of the aircraft from an ICD source into a language neutral model (LNM), the ICD protocol definition corresponding to at least one control logic function or configuration parameter used by the communication protocol, the LNM corresponding to a model and computer modeling environment that uses a data format or data structure that is different from the ICD source, the LNM including a LNM protocol definition corresponding to the at least one control logic function or the configuration parameter, the ICD protocol definition being based on a first data format that is different from a second data format of the LNM protocol definition; converting at least one of the LNM protocol definitions to an Integrated Modular Architecture (IMA) protocol definition having a third data format of the computer modeling environment, the IMA protocol definition corresponding to at least one of the control logic function or the configuration parameter, the third data format being different from the first data format and the second data format; importing the IMA protocol definition into the computer modeling environment to generate a plurality of model libraries based on the IMA protocol definition; generating a plurality of IMA model objects based on the plurality of model libraries, the plurality of IMA model objects including a first IMA model object, the first IMA model object being used to simulate an operation of the first aircraft system based on the first aircraft system using the communication protocol; importing at least one of the plurality of IMA model objects into the computer modeling environment to generate a plurality of IMA models including a first IMA model, the first IMA model including the first IMA model object, the first IMA model for simulating operation of one or more aircraft systems of the aircraft based on one or more aircraft systems using the communication protocol, wherein the one or more aircraft systems include a first aircraft system; generating an IMA system model based on the plurality of IMA models, the IMA system model being used to simulate the operation of an aircraft using the communication protocol; validating the IMA system model by comparing a first output of the IMA system model to a validation output, the validation output corresponding to an expected output of the one or more aircraft systems; generating manufacturing build instructions for the first aircraft system in response to validating the IMA system model based on a comparison of the first output and the validation output; and The manufacturing build instructions are transmitted to a computing system to initiate production of the first aircraft system based on the manufacturing build instructions. 8 . The method of claim 7 , wherein the IMA protocol definition includes at least one of interface information, requirement information, or specification information associated with at least one of the communication protocol or the first aircraft system.

9. The method of claim 7, wherein importing the IMA protocol definition comprises: converting the ICD protocol definition included in the ICD source into a LNM protocol definition included in the LNM using a first ICD converter; and A language specific model (LSM) converter is used to convert a plurality of the LNM protocol definitions into the IMA protocol definitions, a second data format of the LNM based on a first modeling language, and a third data format based on a second modeling language different from the first modeling language.

10. The method according to claim 9, further comprising: comparing a plurality of the LNM protocol definitions to at least one LNM definition rule, and validating the plurality of the LNM protocol definitions based on the comparing; and A plurality of the IMA protocol definitions are compared to at least one IMA definition rule, and the plurality of the IMA protocol definitions are validated based on the comparison.

11. The method according to claim 7, wherein: The first IMA model includes one or more IMA model objects for implementing a lower layer, a presentation layer, and an upper layer, the lower layer including a second IMA model object that implements at least one of a digital communication reading function or a sensor reading function.

12. The method of claim 11, wherein the first aircraft system comprises a physical network switch and a physical sensor, and further comprising validating the IMA system model based on at least one of obtaining network data from the physical network switch via the digital communication read function or obtaining sensor data from the physical sensor via the sensor read function.

13. The method according to claim 7, further comprising: generating machine-readable instructions based on the IMA system model; deploying the machine-readable instructions to at least one of the first aircraft system or the aircraft; and Operation of at least one of the first aircraft system or the aircraft is caused based on the machine-readable instructions.

Images