Rocket test launch control system design method based on model system engineering

Abstract

The invention discloses a rocket test launch control system design method based on model system engineering, and belongs to the technical field of rocket test launch control system design. According to the design method, a carrier rocket test launch control system model is divided into four layers including an overall layer, a subsystem layer, a subsystem layer and a single machine layer from top to bottom; on the basis of four aspects of'object ', 'interaction', 'information 'and'behavior', model architecture design is performed on the basis of SysML elements, a modularized carrier rocket test launch control system model architecture is formed, and the core design of the carrier rocket test launch control system is realized. According to the method, collaborative design can be assisted more quickly, automatic inspection and simulation testing can be carried out, and the development time is shortened.

Description

TECHNICAL FIELD

[0001] The present application relates to a rocket launch control system design method based on model system engineering, belonging to the technical field of rocket launch control system design. BACKGROUND

[0002] In modern aerospace technology, the launch control system of a carrier rocket plays a crucial role. This system is mainly responsible for various detections before the launch of the rocket, controls during the launch, and data processing and analysis after the launch, ensuring that the rocket can accurately and correctly send satellites or other payloads into the intended orbit. Its functions cover pre-launch checks, real-time monitoring of launch status, fault diagnosis and handling, and other aspects, and it is one of the key factors to ensure the success of rocket launches. Therefore, the performance of the launch control system of a carrier rocket is directly related to the success and safety of the entire launch mission.

[0003] However, despite the importance of the launch control system of a carrier rocket, there are still some problems in its development process at the present stage:

[0004] Low communication efficiency: Traditional design methods usually rely on text documents for communication and cooperation, i.e., using a large number of texts, tables or pictures to guide the design and implementation of the system. Due to the complexity of the system composition and the file system, this approach is prone to inconsistent information transmission. Due to the differences in understanding of team members with different backgrounds, misunderstandings and errors may occur during project implementation, resulting in low development efficiency in the design stage, high cost in ensuring quality control, and poor performance in multi-model design versatility.

[0005] Increased risk of errors: In the process of manual and text-based document management, the risk of common errors and inconsistencies is high. Traditional methods lack effective error checking mechanisms, which can easily lead to design flaws and implementation problems.

[0006] Design and requirements are disconnected: Traditional design methods have difficulty effectively managing and tracking all requirements when dealing with complex systems. This disconnection makes the final product of the project may not fully meet the expected goals.

[0007] Due to the above problems, designers often need to invest a lot of time in manual design and verification, which not only delays the development cycle, but also increases the likelihood of errors, thereby affecting the quality and reliability of the final product.

[0008] At the present stage, there is still a lack of specific digital modeling methods for the development of domestic launch control systems of carrier rockets, and the traditional engineering application landing mode is still used in the field of domestic aerospace launch control, and the model-based system engineering mode is still in its infancy. Meta-model is a model of a model, which provides the basis for the structure and semantics of modeling languages.

[0009] Basic elements of meta-model design:

[0010] (1) Elements: A meta-model can define various elements that can be used in a model, such as classes, interfaces, attributes, operations, etc.

[0011] (2) Relationships: A meta-model can define relationships that can be established between elements, such as associations, generalizations, dependencies, etc.

[0012] (3) Attributes: A meta-model can define attributes of elements, such as name, type, visibility, etc.

[0013] (4) Constraints: A meta-model can define constraints that must be satisfied by model elements, such as certain elements must exist in a specific context. SUMMARY

[0014] The technical problem solved by the present application is to overcome the shortcomings of the prior art and provide a rocket launch control system design method based on model system engineering.

[0015] The technical solution of the present application is:

[0016] A rocket launch control system design method based on model system engineering, comprising:

[0017] The launch vehicle launch control system model is divided into four layers, from top to bottom, which are overall layer, subsystem layer, subsystem layer and single machine layer; based on "object", "interaction", "information" and "behavior" four aspects, respectively based on SysML element model architecture design, form modular launch vehicle launch control system model architecture, realize the core design of launch vehicle launch control system.

[0018] Further, based on the Block element of SysML, object design is carried out, and five types of entity models applied to different levels are obtained:

[0019] The overall model is applied to the overall layer, including the name;

[0020] The subsystem model is applied to the subsystem layer, including the name;

[0021] The subsystem model is applied to the subsystem layer, including the name and system code;

[0022] The single machine model and the software model are applied to the single machine layer; the single machine model includes device name, device code, device location, network port quantity, switch, design unit, production unit, standby quantity and deployment software name; the software model is applied to the single machine model and includes software name, software code, software version, key level, software category, programming language, running environment, software size, design unit name and evaluation unit name.

[0023] Further, the "interaction" design is performed to establish a port model, a connection model and an interface model.

[0024] The port model is contained in the entity model and serves as an access point of internal and external information of the entity model; the port model is designed based on the Port element of SysML and is divided into a hardware port model and a network port model to adapt to two transmission modes of hardware and network of the launch, control and measurement system.

[0025] The connection model is used to describe the connection port relationship between the port models and is designed based on the Connector element of SysML; the interface model is used to express the information in the port model and is designed based on the Interface element of SysML.

[0026] Further, the network port model is used to describe the network port on the single machine device, and the model data includes port name, network port model, IP address, port number, network speed and node code.

[0027] Further, the hardware port model is used to describe the aviation plug on the single machine device, and the model data includes port name, plug model, plug form and plug point number.

[0028] Further, the "information" design is performed to establish a flow model, a signal model and a parameter model.

[0029] The flow model is realized based on the generalization of the FlowProperty of SysML and is used to express the information flow under the interface of the hardware port model and the interface of the network port model, and is respectively a hardware flow model and a network flow model.

[0030] The signal model is obtained based on the extension of the Signal base class of SysML and is used to give the signal information under the interface of the network port model and includes signal name, signal code, table number and code.

[0031] The parameter model is realized based on the Property of SysML and is used to describe the specific value carried in each model object and includes parameter name, data value and data type.

[0032] Further, the network flow model comprises a flow name, a flow direction, an information word format, a protocol mode and a frequency; wherein the information word format is a communication information framing format used in the ground measurement and control network, one information word is used for transmission of one parameter information, and specifically comprises:

[0033] A first information word format is used for transmission of online parameters without telemetry time, and comprises a table number, a code, a data type, data and an out-of-tolerance mark;

[0034] A second information word format is used for transmission of single time series data transmission with telemetry time, and comprises a table number, a code, a telemetry time, a data type, data and an out-of-tolerance mark;

[0035] A third information word format is used for transmission of immediate acquisition state quantities with telemetry date, time or control date, time, and comprises a table number, a code, a telemetry date, a telemetry time, whether there is a control time, a control time, a data type, a switch state and an out-of-tolerance mark;

[0036] A fourth information word format is used for software device binding or cross-system information transmission of communication parameter fixed and whole table transmission information, and comprises a table number and all parameters.

[0037] Further, a "behavior" design is performed, the behaviors of the whole ground measurement and control system are decomposed into states of a series of stages, a state model is established; a series of work flows are completed in different states, a flow model is established; and an action model is established for actions in the flow;

[0038] The state model is established based on a state machine diagram, and comprises a name, a code and a division object;

[0039] The flow model is established based on a state machine diagram, and comprises a name, a code, a normal next node and an abnormal next node;

[0040] The action model is established based on an activity diagram, and according to four basic actions of time triggering, signal triggering, signal sending and state jumping, corresponding models are respectively established; and through permutation and combination of the four basic action models, various flow models of the ground measurement and control system are expressed.

[0041] Further, according to the four basic actions of time triggering, signal triggering, signal sending and state jumping, corresponding models are respectively established, and specifically are:

[0042] The time triggering action model comprises a time origin and a relative length; a triggering condition is determined according to the time origin and the relative length, when a set time is reached, the flow model is passed down, and if the state jumps out, the triggering condition is not met;

[0043] The signal triggering action model comprises a monitoring signal, a condition expression and a cycle time; a triggering condition is determined according to the monitoring signal parameter and the condition expression, and when the monitoring signal reaches the condition expression value, the flow proceeds downward, and if the condition is not met, the state is exited;

[0044] The signal sending action model comprises an assignment signal and a setting value, and the assignment signal is internally assigned with a parameter value and sent;

[0045] The state exit action model comprises an exit option, and a normal exit goes to a state normal node, and an abnormal exit goes to a state abnormal node.

[0046] Further, based on the four aspects of 'object', 'interaction', 'information' and 'behavior', model architecture design is respectively carried out, and through the model architecture, the modelization of layout diagrams, circuit diagrams and matching tables in the development of the measurement and launch control system is realized, and the core design of the measurement and launch control system is completed.

[0047] Compared with the prior art, the present application has the following advantages:

[0048] (1) By using the modeling tool, the designer can quickly build and modify the model of the measurement and launch control system according to the method of the present application, which helps faster collaborative design and reduces development time. The model architecture can realize the comprehensive modelization of the core design documents such as layout diagrams, circuit diagrams and matching tables in the development of the traditional measurement and launch control system.

[0049] (2) The measurement and launch control system model designed based on the present application can integrate design specifications and taboos into the automatic checking rules of the tool, so that the platform becomes a carrier of design experience; a large number of efficient auxiliary function development is possible, and the analysis, checking and traceability requirements in the design process will become easy to realize.

[0050] (3) At present, the development of ground measurement and launch control systems in the field of space transportation still uses product prototypes or prototypes for physical verification, which has high testing and verification cost and difficulty in design optimization before production. The measurement and launch control system model designed based on the present application can allow the designer to simulate and test the model at an early stage, which can discover potential problems in the design process as soon as possible, rather than after the physical prototype is made, thereby greatly reducing the optimization cost. BRIEF DESCRIPTION OF DRAWINGS

[0051] Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiments. The accompanying drawings are included to provide a description of the preferred embodiments and are not intended to limit the scope of the present application. Moreover, the same reference numerals are used throughout the same figures. In the drawings:

[0052] Figure 1A schematic diagram of layered design of a launch vehicle measurement and launch control system according to an embodiment of the present application;

[0053] Figure 2 A framework diagram of a rocket measurement and launch control system according to an embodiment of the present application;

[0054] Figure 3 A schematic diagram of an entity model according to an embodiment of the present application;

[0055] Figure 4 A schematic diagram of a port model according to an embodiment of the present application;

[0056] Figure 5 A schematic diagram of a flow model design according to an embodiment of the present application;

[0057] Figure 6 A schematic diagram of a signal model design according to an embodiment of the present application;

[0058] Figure 7 A layout diagram based on model implementation according to an embodiment of the present application;

[0059] Figure 8 A circuit diagram based on model implementation according to an embodiment of the present application;

[0060] Figure 9 A schematic diagram of model implementation of an automatic error reporting function when interface models between two devices do not match according to an embodiment of the present application;

[0061] Figure 10 A schematic diagram of partial measurement and launch process simulation of a measurement and launch control system according to an embodiment of the present application. DETAILED DESCRIPTION

[0062] Exemplary embodiments of the present disclosure will be described below in greater detail with reference to the accompanying drawings. Although exemplary embodiments of the present disclosure are shown in the drawings, it is understood that the present disclosure can be implemented in various forms and should not be limited by the embodiments set forth herein. Rather, these embodiments are provided so that the present disclosure can be more thoroughly understood and the scope of the present disclosure can be accurately conveyed to those skilled in the art.

[0063] The present application proposes a rocket measurement and launch control system design method based on model system engineering. Based on the idea of meta-model design, the overall architecture of the ground measurement and launch control system model is designed, the meta-model method for constructing the ground measurement and launch control system is defined, and the elements, element attributes and relationships between elements that can be used in the model are defined.

[0064] S1: overall architecture design

[0065] According to the structured idea of "layered level" and "classified type", such as Figure 1As shown, the launch control system model of the carrier rocket is divided into four layers, from top to bottom, the overall layer, the subsystem layer, the subsystem layer and the single machine layer. Among them, the subsystem layer includes the ground launch control system and the electrical system; each subsystem layer is further divided, for example, the ground launch control system includes the measurement system, the power control system and the data transmission communication system; each subsystem layer system is further divided into single machine layer, for example, the power control system is divided into multiple single machines, including auxiliary power temperature adapter, on-orbit power interface adapter, on-orbit power control combination and power command workstation.

[0066] As shown in the model element design architecture proposed for specific levels, different levels of design are supported. The entire architecture can core express the "object", "interaction", "information" and "behavior" four aspects of information of system design. In order to consider the feasibility of model implementation, the design of each model element is based on the existing elements of SysML to expand or generalize: Figure 2

[0067] "Object" is an entity model, based on Block element, 5 types of entity models are designed in categories, respectively "overall model", "subsystem model", "subsystem model", "single machine model" and "software model".

[0068] "Interaction" includes port model, connection model and interface model: port model is based on Port element, 2 types of port model are designed in categories, respectively "hardware port" and "network port", to adapt to the two major transmission modes of launch control system hardware and network; connection model is based on Connector element, interface model is based on Interface element.

[0069] "Information" includes flow model, signal model and parameter model: flow model is based on Flow element, 2 types of flow model are designed in categories, respectively "hardware flow" and "software flow", to adapt to the different information flow characteristics of launch control system hardware and network; signal model is based on Signal element, parameter model is based on Property element.

[0070] "Behavior" includes state model, flow model and action model: state model and flow model are based on state machine; action model is based on activity diagram, 4 types of action model are designed, respectively "time trigger", "signal trigger", "signal sending" and "state jump out" as the basic unit of implementation of various behaviors.

[0071] S2: Object design

[0072] Entity model is realized by generalizing the basic element Block of SysML, the meta-model design based on Profile Diagram is as follows: Figure 3 ​As shown, there are five types of models, including "overall model", "subsystem model", "subsystem model", "single machine model" and "software model".

[0073] Different categories of models are suitable for different levels of "object" expression:

[0074] (1) Overall model is suitable for overall layer

[0075]

[0076] (2) Subsystem model is suitable for subsystem layer

[0077]

[0078] (3) Subsystem model is suitable for subsystem layer

[0079]

[0080] (4) Single machine model is suitable for single machine layer

[0081]

[0082] For non-networking devices in the hardware device matching table, such as the arrow power interface adapter, the number of network ports is 0, and the switch is empty.

[0083] (5) Software model is suitable for single machine layer, because software is physically dependent on specific hardware for operation, so software model is contained in a specific single machine model. In this embodiment, the software model only describes the basic design information of the software in the single machine, and the functional logic of the software is developed uniformly in the logic model in the single machine.

[0084]

[0085]

[0086] S3: Interaction design

[0087] (1) Port model

[0088] Port model is contained in entity model as access point of internal and external information of entity.

[0089] Based on the characteristics of ground launch control system, two types of ports are generalized based on ProxyPort: hardware port and network port, such as Figure 4 As shown, it is used to adapt to two types of information transmission methods used in actual system design.

[0090] Hardware port

based on Port

[0091] HardwarePort is used to describe the aviation plug on real single machine device. In this part, the model library of connector type can be created according to the connector type, and the specific connector can be used as a generalized instance of a certain connector type based on the model library.

[0092] Based on Port, a series of plug models such as J599I / 20KJ35SA can be generalized. All the plugs using this specification can use the generalization relationship of SysML to create instances. All instances inherit the properties of the plug model library and achieve the functions of the model library.

[0093]

[0094] NetworkPort

based on Port

[0095]

[0096]

[0097] (2) Port model

[0098] Interface model is used as the type of port to express the information in the port. Usually, an interface model maintains the internal information flow of a pair of connected ports.

[0099]

[0100] (3) Connection model

[0101] Connection model is used to describe the connection between ports, based on IBD diagram and Connector design:

[0102]

[0103] S4: Information design

[0104] According to the characteristics of ground launch control system, the same function has different forms in different stages, for example: "core first stage oxygen filling valve opening" function is sent to the measurement and control combination through the network in the back end, and the measurement and control combination uses internal board card to send to the front end of the rocket through hardware circuit. Usually, a function has "network + hardware" two stages, so two types of flow models are designed to express two stages, and the type can be set to express a function with a signal.

[0105] (1) Flow model

[0106] Flow model is used to express the information flow under the interface. In order to adapt to the aviation plug and network interface form involved in typical electrical system, two types of flow models are designed: hardware flow model and network flow model. Based on FlowProperty generalization, such asFigure 5 As shown.

[0107] Hardware flow:

[0108]

[0109]

[0110] Network flow:

[0111]

[0112] Wherein the information word format is a communication information framing format used in the ground measurement and control network, and its specific modes include the following:

[0113] a) Information word format 1

[0114] Information word format 1 can be used to transmit network parameters without telemetry time (supporting single data transmission with variable byte length). The specific framing format is shown in the table below, one information word is used for the transmission of one parameter information, and the table number and code are used as the unique identifier of each information word.

[0115] Field Data type Number of bytes Table number unsigned short 2 Encoding unsigned short 2 Data type unsigned char 1 Data Variable, determined by data type N Outlier flag unsigned char 1

[0116] Wherein the measurement and control network information uses parameter table communication:

[0117] The table number is the identifier of the table where the parameter is located, and the code is the arrangement order of the parameter in the table. Therefore, the table number and code are used as the unique identifier of each parameter.

[0118] The 2-byte, 4-byte and 8-byte integers in the data type field are arranged with the low byte first and the high byte last. The floating point number should comply with the IEEE 754 standard format.

[0119] The data field is used to fill in the parameter value, and the length is not fixed and varies with the data type.

[0120] The coding rules of data type and data field are shown in the table below:

[0121]

[0122]

[0123] The out-of-tolerance flag field is used to identify whether the test data is out of tolerance, indicating whether the parameter is out of tolerance. The data type is unsigned char, 0 represents normal, 1 represents out of tolerance, and 2 represents no judgment.

[0124] b) Information word format 2

[0125] Information word format 2 can be used for transmission of single time series data transmission with telemetry time, the specific framing format is shown in the following table, one information word is used for the transmission of one parameter information, and the table number and code are used as the unique identifier of each information word. Unlike information word format 1, information word format 2 has a telemetry time field (8-byte floating point number).

[0126] Field Data type Number of bytes Table number unsigned short 2 Encoding unsigned short 2 Telemetry time double 8 Data type unsigned char 1 Data Variable, determined by data type N Outlier flag unsigned char 1

[0127] c) Information word format 3

[0128] Information word format 3 is used for transmission of on-site status quantities with telemetry date, time or control date, time, the specific framing format is shown in the following table, one information word is used for the transmission of one parameter information, and the table number and code are used as the unique identifier of each information word. Information word format 3 has fields of telemetry date (4-byte unsigned integer), telemetry time (8-byte floating point number), whether there is control time (1-byte signed integer), control time (8-byte floating point number), and its data field is only the switch state (1-byte signed integer), and the other fields have the same meaning as information word format 1.

[0129]

[0130] d) Information word format 4

[0131] Information word format 4 is used for the case of fixed communication parameters and whole table transmission information, which is commonly used for software device binding or cross-system information transmission. Since the code information is omitted, the receiving party determines according to the parameter order, so the communication efficiency is higher than that of information word formats 1, 2 and 3, and the specific framing is shown in the following table, where N is the number of parameters in this table.

[0132]

[0133] (2) Signal model

[0134] The signal model is obtained by extending the Signal base class, and the table number, code and other information concerned in the network interface agreement of the ground measurement and control system are added, as shown in Figure 6

[0135] (3) Parameter model

[0136] The parameter model is used to describe the specific values carried in the model object, which is realized through Property.

[0137] S5: Behavior design

[0138] ​According to the characteristics of the ground launch control system, the entire system behavior can be divided into a series of stages of large state, and a series of work processes are completed in different states. There can be parallel or serial relationship between processes, for example, in the presence of abnormal situation process can switch to the previous process or enter the disposal process, and finally achieve the final goal of the specific stage.

[0139] (1) State model

[0140] (2) Process model

[0141] (3) Action model

[0142] The action model is used to implement specific logic, and the pre-launch process of the ground launch control system is classified and arranged. The embodiment proposes to use four types of basic action models as the basic unit of logic: time trigger, signal trigger, signal sending and state jump. Through the permutation and combination of the four types of basic action models, various process expressions of the launch control system can be applied, and the modular design of the process can be realized.

[0143] a) Time trigger

[0144]

[0145]

[0146] b) Signal trigger

[0147] c) Signal sending

[0148] d) State jump

[0149] In the design stage of the rocket launch control system, the invention can first complete the general system modeling construction, and the established model has better reusability, which reduces the development workload of the launch control system in different models. At the same time, good results can be achieved in terms of communication consistency, development efficiency, simulation verification and code generation, accelerating the digital transformation of the launch control system development. Compared with the traditional system development method, the invention can bring the following beneficial effects:

[0150] (1) Design efficiency is improved

[0151] By using the modeling tool, the designer can quickly build and modify the model of the test and launch control system according to the method, help faster collaborative design, and reduce the development time. The model architecture can realize the overall modeling of the layout, circuit diagram, and supporting table of the test and launch control system development. The layout and circuit diagram realized based on the model are as shown in Figure 7 、 Figure 8 .

[0152] (2) Auxiliary design and development

[0153] The design specification and taboo can be integrated into the automatic checking rules of the tool based on the model, so that the platform becomes the carrier of design experience. A large number of efficient auxiliary function development is possible, and the analysis, checking, and traceability requirements in the design process will become easy to realize. For example Figure 9 The automatic error reporting function when the interface model of two devices does not match is realized.

[0154] (3) Simulation test and verification

[0155] At present, the development of the ground test and launch control system in the field of carrier still carries out physical verification through product prototypes or prototypes, the test and verification cost is high, and the design optimization before production is difficult. Based on the construction model, the designer can simulate and test the model in the early stage, as shown in Figure 10 , potential problems can be found early in the design process, rather than after the physical prototype is made, which greatly reduces the optimization cost.

[0156] The above-described embodiments are only the preferred specific embodiments of the present application, and the usual changes and replacements made by those skilled in the art within the scope of the technical solutions of the present application should be included in the protection scope of the present application.

Claims

1. A rocket launch control system design method based on model system engineering, characterized in that, Comprise: The launch vehicle measurement and control system model is divided into four layers, from top to bottom, the overall layer, subsystem layer, subsystem layer and single machine layer; Based on the "object", "interaction", "information" and "behavior" four aspects, respectively based on SysML element model architecture design, form modular launch vehicle measurement and control system model architecture, realize the core design of launch vehicle measurement and control system.

2. The method according to claim 1, wherein, Based on the Block element of SysML, the object design is obtained, which is applied to five kinds of entity models in different levels: The overall model is applied to the overall layer, including the name; The subsystem model is applied to the subsystem layer, including the name; The subsystem model is applied to the subsystem layer, including the name and system code; The single machine model and software model are applied to the single machine layer; The single machine model includes device name, device code, device location, network port quantity, switch, design unit, production unit, standby quantity and deployment software name; The software model is applied to the single machine model, including software name, software code, software version, key level, software category, programming language, running environment, software size, design unit name and evaluation unit name.

3. The method according to claim 2, wherein, "Interaction" design is carried out, and port model, connection model and interface model are established; The port model is contained in the entity model as an access point for internal and external information of the entity model; The port model is designed based on the Port element of SysML, which is divided into hardware port model and network port model to adapt to the two transmission modes of measurement and control system hardware and network; The connection model is used to describe the connection port relationship between the port models, which is designed based on the Connector element of SysML; The interface model is used to express the information in the port model, which is designed based on the Interface element of SysML.

4. The method according to claim 3, wherein, The network port model is used to describe the network port on the single machine device, and the model data includes port name, network port model, IP address, port number, network speed and node code.

5. The method according to claim 3, wherein, The hardware port model is used to describe the aviation plug on the single machine device, and the model data includes port name, plug model, plug form and plug point number.

6. The method of claim 1, wherein the method is characterized by: "Information" design is carried out, and flow model, signal model and parameter model are established; The flow model is realized based on the generalization of SysML FlowProperty, which is used to express the information flow under the interface of hardware port model and network port model, respectively hardware flow model and network flow model; The signal model is obtained based on the extension of SysML Signal base class, which is used to give the signal information under the interface of network port model, including signal name, signal code, table number and code; The parameter model is realized based on the Property of SysML, which is used to describe the specific value carried in each model object, including parameter name, data value and data type.

7. The model-based systems engineering method for designing a launch control system of a rocket according to claim 6, wherein, The network flow model includes flow name, flow direction, information word format, protocol mode and frequency; Among them, the information word format is the communication information framing format used in the ground measurement and control network, one information word is used for the transmission of one parameter information, which includes: The first information word format is used for transmitting the online parameter without telemetry time, including table number, code, data type, data and out-of-tolerance mark; The second information word format is used for transmitting the single time series data transmission with telemetry time, including table number, code, telemetry time, data type, data and out-of-tolerance mark; The third information word format is used for transmitting the instant state quantity with telemetry date, time or control date, time, including table number, code, telemetry date, telemetry time, whether there is control time, control time, data type, switch state and out-of-tolerance mark; The fourth information word format is used for transmitting the software device binding or cross-system information transmission of the fixed communication parameter and whole table transmission information, including table number and all parameters.

8. The model-based systems engineering approach for the design of a launch control system of a rocket as claimed in claim 1, wherein, The "behavior" design is performed to decompose the whole ground measurement and launch control system behavior into a series of state of stages, to establish a state model; a series of work flows are completed in different states to establish a flow model; and an action model is established for the actions in the flow; The state model is established based on a state machine diagram, including name, code and division object; The flow model is established based on a state machine diagram, including name, code, normal post-node and abnormal post-node; The action model is established based on an activity diagram, and according to four basic actions of time trigger, signal trigger, signal sending and state jump, corresponding models are respectively established; through permutation and combination of the four basic action models, various flow expressions of the ground measurement and launch control system are applicable.

9. The model-based systems engineering approach to the design of a launch control system for a rocket according to claim 8, wherein, According to the four basic actions of time trigger, signal trigger, signal sending and state jump, corresponding models are respectively established, specifically as follows: The time trigger action model includes time origin and relative length; the trigger condition is determined according to the time origin and relative length, when the set time is reached, the trigger condition is met, the flow is passed downward, and if not met, the state jumps out; The signal trigger action model includes monitoring signal, condition expression and cycle time; the trigger condition is determined according to the monitoring signal parameter and condition expression, when the monitoring signal reaches the condition expression value within the cycle time, the trigger condition is met, the flow is passed downward, and if not met, the state jumps out; The signal sending action model includes assignment signal and setting value, the assignment signal is internally parameterized and sent; The state jump action model includes jump options, the normal jump goes to the state normal post-node, and the abnormal jump goes to the state abnormal post-node.

10. The model-based systems engineering approach for the design of a launch control system of a rocket as claimed in claim 1, wherein, Based on the four aspects of "object", "interaction", "information" and "behavior", the model architecture design is respectively performed, through the model architecture, the modelization of the layout diagram, circuit diagram and supporting table in the development of the measurement and launch control system is realized, and the core design of the measurement and launch control system is completed.

Images