Model-based electronic information product interface definition and mapping method and device

Abstract

The invention discloses a model-based electronic information product interface definition and mapping method and device, and the method comprises the steps: defining a logic layer interface model of a single machine according to the logic function of an interface, decomposing and refining a black box function logic interface of a subsystem and a flow item borne by the black box function logic interface, and capturing all external interfaces of the concerned single machine; defining a physical layer interface model of the single machine, describing physical node information in the interface, and replacing the type of the external interface of the single machine from the logic layer interface model to the corresponding physical layer interface model; defining an equipment layer interface of the single machine, and generating single machine external electrical connector node information based on a mapping relation between the physical layer interface and the equipment layer interface; obtaining a user-defined interface information table, and generating an interface data list containing single-machine external connectors and connector node information based on the incidence relation of the model information; and analyzing a structured text which is exported by the SysML model and contains detailed information of a single-machine interface through a schematic diagram design tool, and automatically creating a schematic diagram design model of a corresponding interface connector.

Description

Technical Field

[0001] The present invention belongs to the field of electronic information technology for aerospace platforms, and in particular relates to a model-based electronic information product interface definition and mapping method and device. Background Art

[0002] Space platform electronic information products, such as onboard computers and measurement and control transponders, feature diverse service types and transmission rates, as well as complex interfaces. Onboard computers are the core of satellite platform control, while measurement and control products are the sole information link between a spacecraft and the ground after launch. Therefore, onboard electronic information products are crucial to the normal operation of satellites in orbit. Onboard electronic information products are connected to most satellite products through information interfaces, making their interface design crucial. Currently, scholars have conducted extensive research on the modeling and application of MBSE at the system and subsystem levels of spacecraft. However, in order to further apply the results of MBSE system modeling to the forward design of complex equipment, it is necessary to transfer the design information carried by the model to the equipment and product levels. Given the complex information flows and interface types of onboard electronic information products, transferring the SysML-based interface modeling information to the detailed design of the product is a pressing issue.

[0003] The invention patent "A System and Method for Generating Interface Forms Based on MBSE Models" proposes a system and method for generating interface forms based on MBSE models to address the time-consuming, inefficient, and error-prone manual coding of interface information in existing interface modeling processes. The invention patent "A Method for Defining an Unmanned Aerial Vehicle System Architecture Metamodel Based on SysML" utilizes SysML's internal block diagrams to define the interface relationships between the six architectural elements of a UAV. The invention patent "Parameter-Driven Launch Vehicle Modeling Method, Apparatus, Equipment, and Medium Based on MBSE" proposes a launch vehicle interface modeling solution; this involves confirming the launch vehicle's requirements modeling and then, based on the refinement and decomposition of the launch vehicle's use case scenarios, forming interfaces for the launch vehicle system context model. The invention patent "Digital Modeling Method for Electrical Interfaces of a Satellite Platform Standalone Integrated Management Unit" details the SysML-based modeling of onboard computer interfaces. By defining the interface data sheet for the integrated management unit based on the model, the number and attributes of the interfaces can be dynamically updated as the model is modified.

[0004] In summary, current relevant research has not yet systematically discussed how to capture stand-alone interfaces from subsystem black box interface models, how to model the physical node attributes inside interfaces in detail, and how to further map interface design information based on SysML models to detailed designs. Summary of the Invention

[0005] The present invention proposes a model-based electronic information product interface definition and mapping method and device. By constructing a three-layer interface model and model library for the logical layer, physical layer, and device layer of a single satellite-borne electronic information machine, it is used for the model-based interface design of the single machine, and generates an interface data sheet and schematic diagram file that describes the detailed information of the electrical interface node.

[0006] A first aspect of the present invention provides a model-based electronic information product interface definition and mapping method, comprising the following steps: Define the logical layer interface model of a single machine based on the logical function of the interface, decompose and refine the subsystem black box functional logical interface and the flow items it carries, and capture all external interfaces of the single machine of interest; Define the physical layer interface model of a single machine, describe the physical node information within the interface, and replace the type of the single machine's external interface with the corresponding physical layer interface model; Define the device layer interface of a single machine, and generate the external electrical connector node information of the single machine based on the mapping relationship between the physical layer interface and the device layer interface; Obtain the custom interface information table and generate an interface data sheet containing the single machine external connector and connector node information based on the association relationship of the model information; Parse the structured text containing detailed information of the single-machine interface exported from the SysML model, and use the schematic design tool to parse the structured text to automatically create a schematic design model of the corresponding interface connector.

[0007] Preferably, defining a stand-alone logical layer interface model according to the logical function of the interface further includes: The interface model is defined according to the functional type of the interface as follows: power supply, remote control, telemetry, and business data. Remote control is divided into OC command and digital remote control, telemetry is divided into integrated power direct acquisition and digital telemetry, and business data is divided into high-speed and low-speed input and output business data, and radio frequency input and output data. The logic layer interface model is specifically identified by the structural type "Logic Layer Interface".

[0008] Preferably, defining the physical layer interface model of a single machine further includes: The physical layer interface model is specifically identified by the construct type "physical layer interface"; The physical layer interface contains nested sub-interfaces. The sub-interfaces are defined by physical nodes and include at least several basic nodes, including Clock+, Clock-, Gate+, Gate-, Data+, Data-, Power+, Power-, GND, Signal+, Signal-, Telemetry+, Telemetry Return, AGND, and DGND. The physical node is defined by the interface block identified by the "Electrical Node" stereotype. The "Electrical Node" stereotype is used to describe the electrical properties of the physical node, including four attribute values: voltage, current, polarity, and signal type.

[0009] Preferably, defining the device layer interface of a single machine further includes: The device layer interface is defined by the interface block model identified by the "Device Layer Interface" stereotype and named after the electrical connector code. The interface block model defining the device layer interface is named after the electrical connector model and contains nested sub-interfaces. The sub-interfaces are the node numbers of the electrical connector plug-ins of the corresponding models. The attribute value "pin / hole type" and the "derived Property" attribute "electrical connector function description" are defined in the "Device Interface" stereotype. The constructor "BelongTo" of the defined relationship type is extended from the metamodel "Allocate". In the relationship defined by "BelongTo", the source points to the interface block model defined by the "Device Layer Interface" constructor, and the target points to the interface block model defined by the "Physical Layer Interface" constructor. The customization of the constructor "Device Layer Interface" is set so that the attribute "Electrical Connector Function Description" of the "Device Layer Interface" has the derivedPropertySpecification constructor, thereby assigning the attribute value by indexing the target in the relationship described by the relationship constructor "BelongTo".

[0010] Preferably, the logical layer interface stereotype implicitly includes a String type attribute: implementation item flow, which is used to automatically distribute the flow property in the interface block model of the upper level (such as the subsystem layer) to the downstream (such as the stand-alone layer), and further implementation includes: Define the relationship type's constructor "RealizeBy", which is extended from the metamodel "Dependency". In the relationship defined by "RealizeBy", the source points to the interface block model defined by the "Logical Layer Interface" constructor, and the target points to the specific flow property in the upper-level interface block model. The flow items captured by the upper-level interface model are allocated to the specified interface of the specific stand-alone machine at this level; set the customization of the constructor "Logical Layer Interface", and use the Derived PropertySpecification to index the flow property pointed to by the target in the relationship described by the relationship constructor "RealizeBy", thereby assigning the attribute "Realization Item Flow" of the "Logical Layer Interface".

[0011] Preferably, parsing the structured text containing detailed information of the stand-alone interface derived from the SysML model further includes: The table contents are automatically filled using the interface name of the captured stand-alone device layer interface model and the "Electrical Connector Function Description" attribute and the "Pin / Hole Type" attribute of the "Device Layer Interface" obtained through the model association relationship. The custom interface information table includes a custom table "Electrical Connector" with the table headers "Electrical Connector Code, Electrical Connector Function Description, Electrical Connector Model, Pin / Hole Type"; Through node mapping, the connector node number inside the device layer interface, the physical node definition of the associated physical layer interface, and the electrical property information of the physical node are captured, and the table content is automatically filled in; the custom interface information table includes a custom table "Electrical Connector Node Allocation", and the table header includes "Contact Number, Signal Content, Voltage (V), Current (A), Polarity, Signal Type".

[0012] Preferably, automatically creating a schematic design model of a corresponding interface connector by parsing the structured text using a schematic design tool further includes: Output all the connector names, types, node numbers, node signal contents, and node attributes of a single machine as a structured text "single machine interface attribute definition table"; Create a schematic file using the Altium Designer scripting language, parse and read the "Standalone Interface Attribute Definition Table", search the component library based on the connector type information, define the schematic component model for the standalone external connector, create the schematic netlabel and connection based on the node signal content and parameter attributes, and associate them with the component pins.

[0013] Based on the same concept, the second aspect of the present invention provides a model-based electronic information product interface definition and mapping device, characterized by comprising: The logical layer interface definition module is used to define the logical layer interface model of a single machine based on the logical functions of the interface, decompose and refine the subsystem black box functional logical interface and the flow items it carries, and capture all external interfaces of the single machine of interest; The physical layer interface definition module is used to define the physical layer interface model of a single machine, describe the physical node information inside the interface, and replace the type of the single machine's external interface with the corresponding physical layer interface model; The device layer interface definition module is used to define the device layer interface of a single machine and generate the external electrical connector node information of the single machine based on the mapping relationship between the physical layer interface and the device layer interface; An interface data sheet generation module is used to obtain a custom interface information table and generate an interface data sheet containing information about a single machine's external connectors and connector nodes based on the association relationship of the model information; The model generation module is used to parse the structured text containing detailed information of the single-machine interface exported by the SysML model, and automatically create the schematic design model of the corresponding interface connector by parsing the structured text through the schematic design tool.

[0014] Based on the same concept, the third aspect of the present invention provides an electronic device, comprising: a memory, the memory being used to store a processing program; a processor, the processor implementing any one of the above-mentioned model-based electronic information product interface definition and mapping methods when executing the processing program.

[0015] Based on the same concept, the fourth aspect of the present invention provides a readable storage medium, on which a processing program is stored. When the processing program is executed by a processor, any one of the above-mentioned model-based electronic information product interface definition and mapping methods is implemented.

[0016] Due to the adoption of the above technical solution, the present invention has the following advantages and positive effects compared with the prior art: 1. This invention proposes a specific solution for capturing a single-machine white-box interface model from a subsystem black-box interface model. This not only converts the subsystem interface black-box model into a white-box model based on the actual composition of the subsystem's individual machines, allowing forward deduction to derive the individual machine's interface, but also further allocates interface flow items to the individual machine's interface, establishing a more complete traceability relationship. This achieves a more logically rigorous and complete decomposition of interface functionality.

[0017] 2. This invention proposes a model-based interface modeling solution that captures detailed physical node information for standalone products. By using the logical, physical, and device layer models of the product interface, a mapping relationship between the interface's physical node information and connector nodes is established. Customized tables are used to capture the relationships between the models, and a single file of interface data is derived for actual satellite development.

[0018] 3. This invention proposes a SysML-based information transfer solution from interface modeling to schematic detailed design. By parsing the structured text derived from the SysML model, the interface schematic component model is automatically generated, thereby constraining the schematic detailed design.

[0019] 4. The interface modeling method proposed in this invention is applicable not only to stand-alone satellite electronic information systems, but also to detailed interface design of other stand-alone products based on SysML models. Interface design information is transferred to professional design software through model analysis. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] The specific embodiments of the present invention are further described in detail below with reference to the accompanying drawings, wherein: Figure 1This is a flowchart of a stand-alone product interface design based on a model according to an embodiment of the present invention; Figure 2 This is a schematic diagram of the refinement and decomposition of a single-machine logic layer interface to a subsystem black box interface according to an embodiment of the present invention; Figure 3 The "RealizeBy" relationship matrix of one embodiment of the present invention realizes the allocation of subsystem black box interface information flow; Figure 4 The "implementation item flow" attribute automatically assigned to the logic layer interface of an embodiment of the present invention; Figure 5 This is the definition of the physical layer interface of the S transponder according to one embodiment of the present invention; Figure 6 Definition of the relationship between the physical layer interface and the device layer interface according to an embodiment of the present invention; Figure 7 An S communication machine model with detailed physical node and electrical connector information according to an embodiment of the present invention; Figure 8 This is an example of an external interface representation of a stand-alone electrical connector generated based on a model according to an embodiment of the present invention; Figure 9 This is an example of node allocation for an S communication electromechanical connector generated based on a SysML model according to an embodiment of the present invention; Figure 10 This is an S communication machine external interface data sheet generated based on the SysML model according to an embodiment of the present invention; Figure 11 This is a schematic diagram of an external interface circuit generated based on a SysML model according to an embodiment of the present invention. DETAILED DESCRIPTION

[0021] The present invention will be further described below in conjunction with the accompanying drawings and specific embodiments. The advantages and features of the present invention will become more apparent from the following description and claims. It should be noted that the drawings are greatly simplified and not to exact ratios, and are intended solely to facilitate and clearly illustrate the embodiments of the present invention.

[0022] It should be noted that all directional indications in the embodiments of the present invention (such as up, down, left, right, front, back, etc.) are only used to explain the relative position relationship, movement status, etc. between the various components under a certain specific posture (as shown in the accompanying drawings). If the specific posture changes, the directional indication will also change accordingly.

[0023] Example In the detailed design of a standalone communication product, the design of the standalone external interface nodes is an important part. This embodiment builds a three-layer interface model of the standalone product: the logical layer, the physical layer, and the device layer. Through model-based interface design, the same source of interface data can be guaranteed.

[0024] The core solution of this embodiment is: a model-based electronic information product interface definition and mapping method, including the following steps: Define the logical layer interface model of a single machine based on the logical function of the interface, decompose and refine the subsystem black box functional logical interface and the flow items it carries, and capture all external interfaces of the single machine of interest; Define the physical layer interface model of a single machine, describe the physical node information within the interface, and replace the type of the single machine's external interface with the corresponding physical layer interface model; Define the device layer interface of a single machine, and generate the external electrical connector node information of the single machine based on the mapping relationship between the physical layer interface and the device layer interface; Obtain the custom interface information table and generate an interface data sheet containing the single machine external connector and connector node information based on the association relationship of the model information; Parse the structured text containing detailed information of the single-machine interface exported from the SysML model, and use the schematic design tool to parse the structured text to automatically create a schematic design model of the corresponding interface connector.

[0025] By constructing a three-layer interface model and model library for spaceborne electronic information standalone computers, encompassing the logical, physical, and device layers, this model is used for model-based interface design of standalone computers, generating interface data sheets and schematics that describe detailed information about electrical interface nodes. The logical layer model captures the standalone computer's external functional logical interface within the subsystem black box interface model. The physical layer model describes the detailed information about the physical nodes of the standalone computer's external electrical interfaces. The device layer model describes the standalone product's external electrical connectors and the electrical properties and parameters of their internal nodes. By constructing and utilizing the logical layer interface model to define interfaces, a functional description of all the standalone computer's external interfaces is achieved.

[0026] Preferably, defining a stand-alone logical layer interface model according to the logical function of the interface further includes: The interface model is defined according to the functional type of the interface as follows: power supply, remote control, telemetry, and business data. Remote control is divided into OC command and digital remote control, telemetry is divided into integrated power direct acquisition and digital telemetry, and business data is divided into high-speed and low-speed input and output business data, and radio frequency input and output data. The logic layer interface model is specifically identified by the structural type "Logic Layer Interface".

[0027] The logical layer interface stereotype implicitly contains a String attribute: the implementation item flow, which is used to automatically distribute the flow property in the interface block model of the previous level (such as the subsystem layer) to the downstream (such as the stand-alone layer). Further implementation includes: The constructor "RealizeBy" that defines the relationship type is extended from the metamodel "Dependency". In the relationship defined by "RealizeBy", the source points to the interface block model defined by the "Logical Layer Interface" constructor, and the target points to the specific flow property in the upper-level interface block model. The flow items captured by the upper-level interface model are allocated to the specified interface of the specific stand-alone machine at this level. The customization of the constructor "Logical Layer Interface" is set, and the flow property pointed to by the target in the relationship described by the relational constructor "RealizeBy" is indexed through Derived PropertySpecification, thereby assigning a value to the attribute "Realization Item Flow" of the "Logical Layer Interface".

[0028] The logical interface of a single machine is obtained through forward design deduction of the subsystem white box model. This includes two steps: functional decomposition and item flow allocation.

[0029] (1) Functional decomposition, that is, decomposing the subsystem functional interface into the logical interface of a single machine. Specifically: the subsystem black box functional interface model type is replaced by the subsystem white box logical interface type. The subsystem white box logical interface type contains nested sub-interfaces consisting of the single machine logical interface identified by the "Logical Layer Interface". The single machine logical interface mainly includes the four types mentioned above.

[0030] (2) Item flow allocation: Allocate the flow items of the subsystem black box interface to the stand-alone logical interface based on the specific implementation path. Specifically, the "RealizeBy" relationship establishes an association between the flow property of the subsystem black box functional interface and the corresponding stand-alone logical interface. Through the "RealizeBy" relationship, the "Realization Item Flow" property of the "Logical Layer Interface" can be automatically assigned by the item flow of the associated subsystem functional interface.

[0031] By decomposing all black box interface models of the subsystem, the functional description of all external interfaces of the single machine of concern is captured.

[0032] Design and define the physical layer interface model to describe the details of the physical nodes in the interface and the signals they transmit. The physical layer interface is defined by an interface block identified by the "Physical Layer Interface" stereotype. The physical layer interface contains nested sub-interfaces, which are defined by physical nodes. These include basic nodes such as Clock+, Clock-, Gate+, Gate-, Data+, Data-, Power+, Power-, GND, Signal+, Signal-, Telemetry+, Telemetry Return, AGND, and DGND.

[0033] Physical nodes are defined by interface blocks identified by the "Electrical Node" stereotype. The "Electrical Node" stereotype describes the electrical properties of a physical node, including four attribute values: voltage, current, polarity, and signal type.

[0034] By replacing the type of a single machine's external interface with a physical layer interface of the same meaning, the interface model of the single machine will contain detailed information about all physical nodes.

[0035] Define the device layer interface and implement the physical property assignment of the electrical connector plug-in node. The device layer interface is defined by the interface block model identified by the "Device Layer Interface" stereotype and named after the electrical connector code. The device layer interface model block is named after the electrical connector model and contains nested sub-interfaces, which are the node numbers of the electrical connector plug-in of the corresponding model. The "Device Interface" stereotype defines the attribute value "Pin / Socket Type" and the "Derived Property" attribute "Electrical Connector Function Description"; The constructor "BelongTo" of the defined relationship type is extended from the metamodel "Allocate". In the relationship defined by "BelongTo", the source points to the interface block model defined by the "Device Layer Interface" constructor, and the target points to the interface block model defined by the "Physical Layer Interface" constructor. The customization of the constructor "Device Layer Interface" is set so that the attribute "Electrical Connector Function Description" of the "Device Layer Interface" has the derivedPropertySpecification constructor, thereby assigning the attribute value by indexing the target in the relationship described by the relationship constructor "BelongTo".

[0036] Through the "BelongTo" relationship, the "Physical Layer Interface" associated with the "Device Layer Interface" can be identified, and the "Electrical Connector Function Description" attribute of the "Device Layer Interface" can be automatically assigned a value.

[0037] The specific process of assigning physical properties to the electrical connector node is as follows: Associate all physical layer interfaces of a single machine to the device layer interfaces through the "BelongTo" relationship and establish an interface mapping context.

[0038] Based on the interface mapping context, the electrical connector node of the device layer interface is associated with the physical node of the physical layer interface to form a node mapping pair.

[0039] In particular, the association method is typically performed through a connector.

[0040] The interface information is transferred to the circuit design based on the SysML model of the stand-alone machine and its interfaces. Specifically, by parsing the structured text of the stand-alone machine's external connector model, the schematic file of the stand-alone machine's external electrical interface is automatically generated based on Altium Designer's scripting tool.

[0041] (1) Output the names, types, node numbers, node signal contents, and node attributes of all connectors of a single machine as a structured text "single machine interface attribute definition table".

[0042] (2) Create a schematic file using the Altium Designer scripting language, parse and read the "Standalone Interface Attribute Definition Table," search the component library based on the connector type information, and define the schematic component model for the standalone external connector. Based on the node signal content and parameter attributes, create the schematic netlabels and connections, and associate them with the component pins.

[0043] Preferably, parsing the structured text containing detailed information of the stand-alone interface derived from the SysML model further includes: The table contents are automatically filled using the interface name of the captured stand-alone device layer interface model and the "Electrical Connector Function Description" attribute and the "Pin / Hole Type" attribute of the "Device Layer Interface" obtained through the model association relationship. The custom interface information table includes a custom table "Electrical Connector" with the table headers "Electrical Connector Code, Electrical Connector Function Description, Electrical Connector Model, Pin / Hole Type"; Through node mapping, the connector node number inside the device layer interface, the physical node definition of the associated physical layer interface, the electrical properties of the physical node and other information are captured, and the table content is automatically filled in; the custom interface information table contains the custom table "Electrical Connector Node Allocation", and the table header contains "Contact Number, Signal Content, Voltage (V), Current (A), Polarity, Signal Type".

[0044] Based on the same concept, this embodiment also provides an electronic device, including: a memory, the memory being used to store a processing program; and a processor, the processor implementing any one of the above-mentioned model-based electronic information product interface definition and mapping methods when executing the processing program.

[0045] Based on the same concept, this embodiment further provides a readable storage medium, on which a processing program is stored. When the processing program is executed by a processor, any one of the above-mentioned model-based electronic information product interface definition and mapping methods is implemented.

[0046] like Figure 1 As shown in the figure, taking the S transponder as an example, the model-based interface design process of aerospace electronic information stand-alone products is explained in detail.

[0047] The first step is to define the logical layer interface model for a single machine based on the interface's logical functions. This model decomposes and refines the subsystem's black box functional logical interfaces and the flows they carry, capturing all external interfaces of the machine in question. Using the logical layer interface model, define the interfaces and implement a functional description of all external interfaces of the machine.

[0048] The second step is to define the physical layer interface model of the single machine, describe the physical node information inside the interface, and replace the type of the single machine's external interface with the corresponding physical layer interface model.

[0049] The third step is to define the device layer interface of a single machine, and obtain the specific physical functions implemented by the connector node through the mapping relationship between the physical layer interface and the device layer interface.

[0050] The fourth step is to customize the interface information table and use the association relationship of the model information to generate an interface data sheet containing the single machine's external connector information and connector node information.

[0051] The fifth step is to export the structured text containing the single-machine interface information through the model. The schematic design tool automatically creates a schematic design model of the corresponding interface by parsing the structured text.

[0052] First, the individual device interfaces need to be captured and decomposed. The transponder's logical layer interface defines the logical functions of its various interfaces and refines and decomposes interfaces from subsystems. The transponder's logical layer electrical interfaces are categorized by function: power supply, remote control, telemetry, and service data. Remote control is further divided into OC commands and digital remote control, while telemetry is further divided into integrated power direct acquisition and digital telemetry. Data is further categorized into high-speed and low-speed input and output data, as well as RF input and output data.

[0053] The logical layer electrical interface type of a single machine is defined by an interface block identified by the "Logical Layer Interface" stereotype. The "Derived Property" attribute "Realization Item Flow" is defined in the "Logical Layer Interface." The "RealizeBy" stereotype, derived from the "Dependency" metamodel, is defined to implement the transfer and mapping of interface information flow items from the subsystem to the single machine.

[0054] like Figure 2As shown, the transponder's logical layer interface types are defined: the "S-communication Machine OC Command_L" and "S-communication Machine Digital Remote Control Command_L" interface blocks are nested sub-interfaces of the "Integrated Electronics and Measurement and Control Communication Remote Control Interface White Box." The "Integrated Electronics and Measurement and Control Communication Remote Control Interface White Box" inherits from the "Integrated Electronics and Measurement and Control Communication Remote Control Interface" black box functional interface class defined at the subsystem level. The black box functional interfaces defined at the subsystem level do not specify which interface on which single device implements their flow properties. Therefore, to whitebox the subsystem interfaces, two steps are required: interface decomposition and item flow allocation.

[0055] (1) Interface decomposition: Decompose the subsystem functional interface into the logical interfaces of a single machine. Specifically, the subsystem black box functional interface model type interface block is replaced by the subsystem white box logical interface type interface block. The subsystem white box logical interface type interface block contains nested sub-interfaces of the single machine logical interface. The single machine logical interface mainly includes the four types mentioned above. Figure 2 The "integrated electronic and measurement and control communication remote control interface white box" shown is decomposed into two interface blocks: "S communication machine OC instruction_L" and "S communication machine digital remote control instruction_L".

[0056] (2) Flow attribute allocation is achieved through the "RealizeBy" relationship. Specifically, the subsystem black box interface flow items are associated with the stand-alone logical interface according to the functional implementation path, and the "RealizeBy" relationship is used to establish the association relationship between the flow items of the subsystem functional interface and the corresponding stand-alone logical interface. This allows the "realization item flow" attribute of the "logical interface" to be automatically assigned by the internal item flow of the associated subsystem functional interface through the "RealizeBy" relationship. Figure 3 As shown in the figure, through the RealizeBy matrix, the "Transponder Power On Command" and "Transponder Power Off Command" in the flow property of the "Integrated Electronics and Measurement and Control Communication Remote Control Interface" are connected to the "S Communication Machine OC Command_L"; the "Ground Communication Modem Function Fault Module Reconstruction Command" is connected to the "S Communication Machine Digital Remote Control Command_L" to establish a RealizeBy relationship. The result is as follows: Figure 4 As shown, the "S Communication Machine OC Command_L" and "S Communication Machine Digital Remote Control Command_L" interface types automatically add the "Implementation Item Flow" attribute.

[0057] Next, the physical layer interface of a single machine is defined. The S-transponder physical layer interface model is used to describe the physical node information of the electrical interface. The S-transponder physical layer interface is defined by the "Physical Layer Interface" stereotype and named "Interface Function_P." The physical layer interface contains nested sub-interfaces, each defined by a physical node. These include several basic nodes: Clock+, Clock-, Gate+, Gate-, Data+, Data-, Power+, Power-, GND, Signal+, Signal-, Telemetry+, Telemetry Return, and AGND.

[0058] The physical node type is an interface block identified by the "Electrical Node" stereotype. The "Electrical Node" stereotype is used to describe the electrical properties of the physical node, including four attribute values: voltage, current, polarity, and signal type. Figure 5 The figure shows the physical layer interface definition of "S communication machine voice PCM_P" of the S answering machine model.

[0059] Next, define the external connector information for a single device. Define the device-level interface model for the S transponder, describing the node attributes and parameters of the physical product's electrical connector. The device-level interface is defined by an interface block identified by the "Device-Level Interface" stereotype and named after the electrical connector model. The device-level interface contains nested subinterfaces, each representing the node number of the connector. The "Device-Level Interface" stereotype defines the attribute value "Pin / Socket Type" and the "Derived Property" attribute "Electrical Connector Function Description."

[0060] Define the "Interface Implementation" relationship between the "Physical Layer Interface" and the "Device Layer Interface", indicating which type of electrical connector is used to implement the physical interface. The "Interface Implementation" relationship points from the "Device Layer Interface" to the "Physical Layer Interface". The "Interface Implementation" relationship is specifically defined by the "BelongTo" stereotype, which is derived from the "allocate" relationship. Figure 6 As shown in the example, an Interface Implementation relationship is defined between the Device Layer Interface named "J30JHT21ZK" and the Physical Layer Interface named "S Communication Machine Voice PCM_P." This Interface Implementation relationship identifies the Physical Layer Interface associated with the Device Layer Interface and automatically assigns a value to the Electrical Connector Function Description attribute of the Device Layer Interface.

[0061] Further construct the device layer interface library and the physical layer interface library. The device layer interface library defines the electrical connectors for the S communication machine. An interface block with the "Device Layer Interface" stereotype is used to define typical electrical connectors and their node numbers. In the physical layer interface library, an interface block with the "Physical Layer Interface" stereotype is used to define the physical layer interfaces and node information for typical electronic information products. Through interface inheritance, create the S communication machine's external interfaces, such as the remote control PCM signal interface and the OC remote control command interface.

[0062] After defining all physical layer interface blocks of a single machine, such as Figure 7 As shown in Figure a, the external interface type of the S transponder model is changed to the corresponding physical layer interface. The S transponder model interface now has a detailed description of the physical nodes.

[0063] In order to realize the node association of the connector with the physical node information: (1) If Figure 6 As shown in the figure, all physical layer interfaces are associated with the device layer interface through BelongTo.

[0064] (2) If Figure 7 As shown in b, define the S communication machine device layer model, set the external interface type to "Device Layer Interface", and establish an interface mapping context.

[0065] (3) Based on the interface mapping context, the electrical connector nodes of the single-machine device layer model "Device Layer Interface" are associated with the physical nodes of the interface defined by "Physical Layer Interface" to form a node mapping pair.

[0066] like Figure 8 As shown, the custom table "Electrical Connector" has the following headers: "Electrical Connector Code, Electrical Connector Function Description, Electrical Connector Model, Pin / Socket Type." By capturing the interface names of the standalone device layer model and deducing the "Electrical Connector Function Description" and "Pin / Socket Type" attributes of the "Device Layer Interface," the table contents are automatically populated. As shown in the figure, the function of the X01G electrical connector is "Relay Measurement and Control RF Signal Input," the model is "SMA-KF," and the pin / hole type is "Socket."

[0067] like Figure 9 As shown in the figure, the custom table "Electrical Connector Node Assignment" has a header containing information such as "Contact Number, Signal Content, Voltage (V), Current (A), Polarity, and Signal Type." Through node mapping, the node number of the "Device Layer Interface," the corresponding physical node definition, and the electrical properties of the physical node are captured, and the table content is automatically filled in.

[0068] like Figure 10 The figure shows the ICD form machine interface data sheet output after data processing.

[0069] By parsing the structured text output by the stand-alone external connector model, the schematic file of the stand-alone external electrical interface is automatically generated based on Altium Designer's scripting tool.

[0070] (1) Output the names, types, node numbers, node signal contents, and node attributes of all connectors of the S communication machine as a structured text "single machine interface attribute definition table".

[0071] (2) Create a schematic file using Altium Designer scripting language, search the component library based on the connector type information in the "Single Machine Interface Attribute Definition Table", and define the schematic component model of the connector. Create the schematic netlabel and connection based on the node attributes, and associate them with the component pins. Figure 11 Shown is a schematic diagram of external connector components based on the SysML model.

[0072] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the identification content specifically executed by the above-described system and device can refer to the corresponding process in the aforementioned method embodiment.

[0073] The embodiments of the present invention have been described in detail above with reference to the accompanying drawings, but the present invention is not limited to the above embodiments. Even if various changes are made to the present invention, if these changes fall within the scope of the claims of the present invention and their equivalents, they still fall within the scope of protection of the present invention.

Claims

1. A model-based electronic information product interface definition and mapping method, characterized in that: The steps include: Define the logical layer interface model of a single machine based on the logical function of the interface, decompose and refine the subsystem black box functional logical interface and the flow items it carries, and capture all external interfaces of the single machine of interest; Define the physical layer interface model of a single machine, describe the physical node information within the interface, and replace the type of the single machine's external interface with the corresponding physical layer interface model; Define the device layer interface of a single machine, and generate the external electrical connector node information of the single machine based on the mapping relationship between the physical layer interface and the device layer interface; Obtain the custom interface information table and generate an interface data sheet containing the single machine external connector and connector node information based on the association relationship of the model information; Parse the structured text containing detailed information of the single-machine interface exported from the SysML model, and use the schematic design tool to parse the structured text to automatically create a schematic design model of the corresponding interface connector.

2. The model-based electronic information product interface definition and mapping method according to claim 1, characterized in that: The definition of a single machine's logical layer interface model based on the logical function of the interface further includes: The interface model is defined according to the functional type of the interface as follows: power supply, remote control, telemetry, and business data. Remote control is divided into OC command and digital remote control, telemetry is divided into integrated power direct acquisition and digital telemetry, and business data is divided into high-speed and low-speed input and output business data, and radio frequency input and output data. The logic layer interface model is specifically identified by the structural type "Logic Layer Interface".

3. The model-based electronic information product interface definition and mapping method according to claim 1, characterized in that: The physical layer interface model of a single machine is further defined as follows: The physical layer interface model is specifically identified by the structural type "physical layer interface"; The physical layer interface contains nested sub-interfaces. The sub-interfaces are defined by physical nodes and include at least several basic nodes, including Clock+, Clock-, Gate+, Gate-, Data+, Data-, Power+, Power-, GND, Signal+, Signal-, Telemetry+, Telemetry Return, AGND, and DGND. The physical node is defined by the interface block identified by the "Electrical Node" stereotype. The "Electrical Node" stereotype is used to describe the electrical properties of the physical node, including four attribute values: voltage, current, polarity, and signal type.

4. The model-based electronic information product interface definition and mapping method according to claim 1, characterized in that: Defining the device layer interface of a single machine further includes: The device layer interface is defined by the interface block model identified by the "Device Layer Interface" stereotype and named after the electrical connector code. The interface block model that defines the device layer interface is named after the electrical connector model and contains nested sub-interfaces. The sub-interfaces are the node numbers of the corresponding electrical connector plug-in models. The "Device Interface" stereotype defines the attribute value "Pin / Socket Type" and the "Derived Property" attribute "Electrical Connector Function Description". The relationship type constructor "BelongTo" is defined, which is extended from the metamodel "Allocate". In the relationship defined by "BelongTo", the source points to the interface block model defined by the "Device Layer Interface" constructor, and the target points to the interface block model defined by the "Physical Layer Interface" constructor. The customization of the constructor "Device Layer Interface" is set so that the attribute "Electrical Connector Function Description" of the "Device Layer Interface" has the derivedPropertySpecification constructor, thereby assigning the attribute value by indexing the target in the relationship described by the relationship constructor "BelongTo".

5. The model-based electronic information product interface definition and mapping method according to claim 2, characterized in that: The logical layer interface structure implicitly contains a String attribute: the implementation of the item flow, which is used to automatically distribute the flow property in the upper-level interface block model to the downstream. Further implementation includes: Define the relationship type's constructor "RealizeBy", which is extended from the metamodel "Dependency". In the relationship defined by "RealizeBy", the source points to the interface block model defined by the "Logical Layer Interface" constructor, and the target points to the specific flow property in the upper-level interface block model. The flow items captured by the upper-level interface model are allocated to the specified interface of the specific stand-alone machine at this level; set the customization of the constructor "Logical Layer Interface", and use the Derived Property Specification to index the flow property pointed to by the target in the relationship described by the relationship constructor "RealizeBy", thereby assigning the attribute "Realization Item Flow" of the "Logical Layer Interface".

6. The model-based electronic information product interface definition and mapping method according to claim 1, characterized in that: The structured text exported by parsing the SysML model and containing detailed information about the single-machine interface further includes: The table contents are automatically filled using the interface name of the captured stand-alone device layer interface model and the "Electrical Connector Function Description" and "Pin / Hole Type" attributes of the "Device Layer Interface" obtained through the model association relationship. The custom interface information table includes a custom table called "Electrical Connector" with the table headers "Electrical Connector Code, Electrical Connector Function Description, Electrical Connector Model, and Pin / Hole Type." Through node mapping, the connector node number inside the device layer interface, the physical node definition of the associated physical layer interface, and the electrical property information of the physical node are captured, and the table content is automatically filled in; the custom interface information table includes the custom table "Electrical Connector Node Allocation", and the table header includes "Contact Number, Signal Content, Voltage (V), Current (A), Polarity, Signal Type".

7. The model-based electronic information product interface definition and mapping method according to claim 1, characterized in that: Automatically creating a schematic design model of a corresponding interface connector by parsing the structured text using a schematic design tool further includes: Output all the connector names, types, node numbers, node signal contents, and node attributes of a single machine as a structured text "single machine interface attribute definition table"; Create a schematic file using the Altium Designer scripting language, parse and read the "Standalone Interface Attribute Definition Table", search the component library based on the connector type information, define the schematic component model for the standalone external connector, create the schematic netlabel and connection based on the node signal content and parameter attributes, and associate them with the component pins.

8. A model-based electronic information product interface definition and mapping device, characterized in that: include: The logical layer interface definition module is used to define the logical layer interface model of a single machine based on the logical functions of the interface, decompose and refine the subsystem black box functional logical interface and the flow items it carries, and capture all external interfaces of the single machine of interest; The physical layer interface definition module is used to define the physical layer interface model of a single machine, describe the physical node information inside the interface, and replace the type of the single machine's external interface with the corresponding physical layer interface model; The device layer interface definition module is used to define the device layer interface of a single machine and generate the external electrical connector node information of the single machine based on the mapping relationship between the physical layer interface and the device layer interface; An interface data sheet generation module is used to obtain a custom interface information table and generate an interface data sheet containing information about a single machine's external connectors and connector nodes based on the association relationship of the model information; The model generation module is used to parse the structured text containing detailed information of the single-machine interface exported by the SysML model, and automatically create the schematic design model of the corresponding interface connector by parsing the structured text through the schematic design tool.

9. An electronic device, characterized in that: include: a memory for storing a processing program; A processor, wherein when executing the processing program, the processor implements the model-based electronic information product interface definition and mapping method according to any one of claims 1 to 7.

10. A readable storage medium, characterized in that: The readable storage medium stores a processing program, and when the processing program is executed by a processor, the model-based electronic information product interface definition and mapping method according to any one of claims 1 to 7 is implemented.

Images