Interlocking software generation method and system based on meta-model

Abstract

The application provides a method and system for generating interlocking software based on a meta model, which comprises the following steps: obtaining a meta model of interlocking basic elements, wherein the meta model describes the control logic of the basic elements respectively; determining a line data file, wherein the line data file describes the layout and connection relationship of the basic elements of a specified station yard; and generating interlocking software based on the meta model and the line data file; and the basic elements comprise a turnout, a signal machine, a section and a route. The application can flexibly instantiate the interlocking software of the relevant structure of a corresponding station yard according to the scene-independent meta model, which is beneficial to saving system reserved resources, improving the universality and automation degree of the product and saving costs.

Description

TECHNICAL FIELD

[0001] The application belongs to the technical field of rail transit application software, and particularly relates to a method and system for generating interlocking software based on a meta-model. BACKGROUND

[0002] Interlocking software is an important component of a rail transit signal control system. Regardless of the type of rail transit signal system, interlocking software or interlocking logic is the core of the ground system.

[0003] The process of developing interlocking software in a traditional mainstream development mode is as shown in FIG. 1. First, a general interlocking software is developed, and then, when generating special interlocking software applied to an actual station yard, the general interlocking software is instantiated based on the configuration data, the station yard data in the configuration data is configured into the general interlocking software, an instantiated interlocking program is generated, and the interlocking program is compiled / linked to generate special interlocking software. Figure 1

[0004] In this way, most of the processes in the simulation, testing, and confirmation stages from the source code to the target software in the compilation process need to be manually involved, which inevitably consumes human resources and time. In the instantiation stage of the general interlocking software, when complex requirements exceed the functional range of the general interlocking software, the general interlocking software needs to be redeveloped to meet the actual application requirements. Therefore, the general interlocking software reserves computer resources such as a large memory and computing power in the development process to consider universality. When the volume of the instantiated object is not large in the instantiation process, the reserved resources are wasted. Therefore, the volume of the interlocking software program for a simple station yard scene is not small, which causes waste of resources and costs. Therefore, the traditional interlocking software development process has the disadvantages of a long development cycle, high costs, and poor scene applicability. SUMMARY

[0005] To overcome the above-mentioned disadvantages, the application provides a method and system for generating interlocking software based on a meta-model, which can realize a platform-independent development process on the basis of ensuring the requirements, specifications, and functional integrity of the interlocking software, and automatically adapt to variable scene requirements by self-adapting the software size according to the scene size.

[0006] The application provides a method for generating interlocking software based on a meta-model, which comprises the following steps.

[0007] A meta-model of interlocking basic elements is obtained, and the meta-model respectively describes the control logic of the basic elements.

[0008] A line data file is determined, and the line data file describes the layout and connection relationship of the basic elements of a specified station yard.

[0009] ​generating interlocking software based on the meta-model and the track data file;

[0010] The basic elements include: turnouts, signals, sections and routes.

[0011] Further, determining the track data file comprises:

[0012] determining the interlocking logic topology file and the track data topology file;

[0013] The track data topology file is used to describe the number, attributes, membership and control relationship of the interlocking basic elements;

[0014] The interlocking logic topology file is used to describe the input and output relationship between the meta-models and the system-level input and output relationship.

[0015] Further, generating interlocking software based on the meta-model and the track data file comprises:

[0016] parsing the track data topology and the interlocking logic topology file, and generating interlocking software according to the description of the track data topology and the interlocking logic topology file.

[0017] Further, generating interlocking software based on the meta-model and the track data file comprises:

[0018] parsing the track data topology file, determining the track structure of the station yard according to the number, attributes, membership and control relationship of the basic elements, and instantiating the business control logic model corresponding to the track structure based on the meta-model.

[0019] Further, generating interlocking software based on the meta-model and the track data file comprises:

[0020] parsing the interlocking logic topology file, and integrating the input and output interfaces of all business control logic models having external interfaces into a system-level business data interface framework according to the system-level input and output relationship.

[0021] Further, generating interlocking software based on the meta-model and the track data file comprises:

[0022] parsing the track data topology file and the interlocking logic topology file, connecting the business control logic models according to the input and output relationship between the meta-models, the instantiation sequence of the meta-models, and the membership and control relationship of the basic elements, and generating an interlocking logic model.

[0023] Further, generating interlocking software based on the meta-model and the track data file further comprises:

[0024] The line data topology file is parsed, and according to the reserved parameters of the meta model in the line data file, the reserved parameters of the instantiated business control logic model are set to generate a differentiated business control logic model.

[0025] Further, generating interlocking software based on the meta model and the line data file further comprises:

[0026] The first running business control logic model is set to delay for one cycle to prevent the generation of an algebraic ring when the output data of the second running business control logic model is required.

[0027] Further, generating interlocking software based on the meta model and the line data file comprises:

[0028] The interlocking logic model is automatically compiled for the corresponding hardware platform interface, and the interlocking logic model and the platform interface after automatic compilation jointly constitute the interlocking software.

[0029] Further, the resource configuration volume is set in the meta model according to the meta model itself attribute.

[0030] The application also provides an interlocking software generation system based on a meta model, comprising:

[0031] A meta model acquisition module is configured to acquire a meta model of an interlocking basic element, and the meta model describes the control logic of the basic element;

[0032] A file determination module is configured to determine a line data file, and the line data file describes the layout and connection relationship of the basic elements of a specified station yard;

[0033] An interlocking software generation module is configured to generate interlocking software based on the meta model and the line data file;

[0034] The basic elements include a turnout, a signal machine, a section and a route.

[0035] The application also provides an interlocking software generation system based on a meta model, comprising at least one processor and at least one memory;

[0036] The memory stores a computer program for executing any of the above methods, and the processor calls the computer program in the memory to execute any of the above methods.

[0037] The interlocking software generation method and system based on a meta model provided by the application have the following advantages:

[0038] The meta-model is constructed according to a specification, is independent of a scene, and can be flexibly instantiated into interlocking software of a corresponding station scene related structure and deployed to a platform in the face of different station scene scenes.

[0039] The resource configuration volume can be set according to the meta-model itself attribute. In the process of generating interlocking software according to the meta-model, the system resource configuration is set according to the number of instantiated meta-models, which overcomes the waste problem of reserving resources such as a larger memory in the development process of general interlocking software in order to consider universality, and also does not appear the problem of insufficient reserved resources under a complex station scene environment.

[0040] The software generation process is a instantiation process based on the meta-model, and the construction of the meta-model is fully decoupled from the demand, so that the coupling degree is reduced from the system level, and a high cohesion and low coupling system architecture is realized.

[0041] The business logic between the meta-models is relatively independent, when a new function needs to be added, the corresponding meta-model or the input / output port of the open meta-model can be developed, without damaging the original meta-model system and internal structure, so that the interlocking software has strong expansibility.

[0042] The model-based system engineering development method enables the testing, verification, confirmation and process of software and system to have automatic conditions, improves the automation level, efficiency and product safety.

[0043] The model-based development process can continuously verify early, can find errors as soon as possible, and then generate code with higher reliability, thereby improving software quality and reducing development process cost.

[0044] Other features and advantages of the present application will be set forth in the following description, and in part will become apparent to those skilled in the art from the description, or can be learned by practice of the application. The objects and other advantages of the present application will be realized and attained by the structure particularly pointed out in the description and claims, and the appended drawings. BRIEF DESCRIPTION OF DRAWINGS

[0045] In order to more clearly illustrate the technical solutions of the embodiments of the present application or the prior art, the following will briefly introduce the drawings needed to be used in the embodiment or prior art description. Obviously, the drawings in the following description are some embodiments of the present application, and those skilled in the art can obtain other drawings according to these drawings without creative labor.

[0046] Figure 1 A flowchart of an interlocking software generation method according to the prior art is shown;

[0047] Figure 2The logical decision layer structure and system interface diagram of the interlocking software according to the embodiment of the present application is shown.

[0048] Figure 3 The overall hierarchical architecture diagram according to the embodiment of the present application is shown.

[0049] Figure 4 The flow diagram of the preparation stage and the generation stage in the meta-model-based interlocking software generation process according to the embodiment of the present application is shown.

[0050] Figure 5 The flow diagram of the compilation stage in the meta-model-based interlocking software generation process according to the embodiment of the present application is shown.

[0051] Figure 6 The meta-model-based interlocking software generation system structure diagram according to the embodiment of the present application is shown.

[0052] Figure 7 The meta-model-based interlocking software generation system structure diagram according to another embodiment of the present application is shown. DETAILED DESCRIPTION

[0053] To make the objectives, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be described clearly and completely below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are some but not all of the embodiments of the present application. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative work fall within the protection scope of the present application.

[0054] The embodiment of the present application provides a meta-model-based interlocking software generation method, comprising the following steps:

[0055] A meta-model of the interlocking basic elements is acquired, and the meta-model respectively describes the control logic of the basic elements.

[0056] A line data file is determined, and the line data file describes the layout and connection relationship of the basic elements of a specified station yard.

[0057] The interlocking software is generated based on the meta-model and the line data file.

[0058] The basic elements include: a turnout, a signal machine, a section and a route.

[0059] The meta-model is basic data obtained by modeling control logics of the turnout, the signal machine, the section and the route respectively. In order to guarantee the train running safety and efficiency, the interlocking software needs to control the turnouts, the signal machines, the section devices and the route logics in the railway signal system. According to the minimum control unit of the controlled object, the control logic of the control unit is modeled to obtain the meta-model. Without loss of generality, the control logic of each type of basic element corresponds to one or more meta-models, such as a turnout control logic meta-model, a signal machine control logic meta-model, a section control logic meta-model and a route control logic meta-model. The data form of the meta-model is not limited in the embodiment of the present application, which can be a class diagram, a model design diagram, a logic code and the like. Moreover, according to different types of basic elements, a plurality of meta-models corresponding to the type of basic element can be constructed. Exemplarily, for different types of turnouts, a plurality of meta-models can be constructed to meet the control logics of different types of turnouts, for example, a double-open turnout control logic meta-model, a triple-open turnout control logic meta-model and the like. For different types of sections, different section control logic meta-models can also be constructed.

[0060] In the construction of the interlocking software, the model-based system engineering method is adopted, and the actual interlocking software product is instantiated based on the meta-model of the abstract business logic. Compared with the traditional text-based system design and development method, the model-based system engineering is a model-centered development method, and the process control of the system engineering is integrated. The characteristics are high model integration, continuous early verification, integrated automatic simulation, testing, verification and confirmation process methods in the whole life cycle of the product.

[0061] The model-based interlocking software generation process will be described in detail below in combination with the system architecture of the interlocking software.

[0062] As shown in Figure 2 The interlocking software body of the embodiment of the present application is composed of a logic decision layer, a data layer and an interface layer.

[0063] The logic decision layer includes the interlocking business logic such as the route control logic, the section control logic, the signal machine control logic and the turnout control logic of the whole station, and is responsible for the interlocking operation. In the interlocking software running, the logic decision layer accesses the static data in the static database of the data layer, and interacts with the platform-related interface program of the interface layer to exchange the command, the state and other data.

[0064] The data layer includes the parameter definition static database generated according to the data topology, and stores the related data used for the interlocking operation.

[0065] The interface layer includes platform-related interface programs written according to hardware platform characteristics, and is responsible for establishing the contact between the logical decision layer and the hardware platform (generally a computer security platform) of the interlocking software application. Data and / or commands from the logical decision layer are processed by the interface layer to call the devices or physical interfaces of the hardware platform; data and / or commands from external subsystems are processed by the interface layer for interlocking operation by the logical decision layer.

[0066] The interlocking software body also has a signal device interface and an external system interface. The external system interface is used for data connection between the interlocking software and other external systems, such as communication with a TIAS (Train Integrated Automation System) center device through the external system interface, and establishment of a data and command transmission relationship with a ZC (Zone Controller) ground device system. On the signal device interface, the interlocking software transmits the states of external devices such as turnouts, signals and sections to the interlocking software through the signal device interface, and issues commands to drive the actions of these devices after interlocking operation.

[0067] As shown in FIG. 1, the logical decision layer of the interlocking software includes a plurality of business control logic models, each of which is generated by instantiating a corresponding meta-model according to a rule. Figure 3 As shown in FIG. 1, the logical decision layer of the interlocking software includes a plurality of business control logic models, each of which is generated by instantiating a corresponding meta-model according to a rule.

[0068] The turnout control business logic is composed of N turnout control logic models (denoted by symbol A in the figure) corresponding to N turnouts in the station yard, and exemplarily N = 4. The signal control business logic is composed of M signal control logic models (denoted by symbol B in the figure) corresponding to M signals in the station yard, and exemplarily M = 3. The section control business logic is composed of P section control logic models (denoted by symbol C in the figure) corresponding to P sections in the station yard, and exemplarily P = 3. The route control business logic is composed of Q route control logic models (denoted by symbol D in the figure) corresponding to Q routes in the station yard, and exemplarily Q = 4.

[0069] Each type of business logic is connected according to the meta-model interface relationship and the line and device relationship of the station yard. For example, the instantiated turnout control logic model and the route control logic model are connected according to the device relationship between the turnout and the route; the instantiated signal control logic model and the route control logic model are connected according to the device relationship between the signal and the route; and the instantiated section control logic model and the route control logic model are connected according to the line containing the section and the route.

[0070] The interlocking software also interacts with data / commands of external devices such as turnouts, signals, sections, etc., and is connected with ground devices such as zc and central devices such as TIAS.

[0071] The process of generating the interlocking software can be divided into several stages: a data preparation stage, an interlocking logic model generation stage, and a compilation stage.

[0072] Data preparation stage

[0073] The metamodel of the interlocking basic elements is obtained and the line data file is determined. As shown in Figure 4 The basic unit for constructing the interlocking software is the metamodel and the line data file.

[0074] The metamodel is the basic business logic unit that constitutes the interlocking software, such as the control logic of signals, turnouts, sections, and routes. The line data file specifies the layout and connection relationship of the basic elements of the station yard. Exemplarily, the line data file is written in a standardized xml language. In the embodiment of the present application, the line data file includes two types: an interlocking logic topology file and a line data topology file. Determining the line data file means writing, generating, or obtaining the two files, etc. The design and implementation of the two files are described in detail below.

[0075] (1) The line data topology file is used to describe the number, attributes, membership, and control relationship of interlocking basic elements such as turnouts, sections, signals, and routes. In the metamodel, the resource configuration volume is set according to the attributes of the metamodel itself. Specifically, the metamodel sets the resource configuration volume according to its type (turnout, section, etc.), the number of interfaces, etc., such as the size of computer memory and other resources occupied in the control logic of the metamodel. Further, the line data topology file also describes the reserved parameters of the metamodel to realize the differentiated metamodel instantiation process.

[0076] In the embodiment of the present application, the line data topology file is automatically searched by a visual line drawing tool. After drawing the line graph in the graphical tool according to the design requirements, the route is automatically searched based on the line graph elements, the interlocking data is generated, and the interlocking data is verified by a formal method to determine its consistency and completeness. The verified interlocking data is used as the line data topology file.

[0077] Exemplarily, a segment of the line data topology file is as follows, which describes the control relationship of the turnout control logic PCS0_D10 to the power unlocking logic PCS0_POW0, the turnout D10, the routes PCS0_RT1, PCS0_RT5, PCS0_RT6, PCS0_RT7, and the section PCS0_SEC1. Each line of data is explained and described after " / / ".

[0078] <pcs_point id="PCS0_D10"> / / Interlocked switch control relationship description, id data is "PCS0_D10"

[0079] <pcs_poweron>PCS0_POW0< / pcs_poweron> / / The switch is unlocked by power-on

[0080] <point> D10< / point> / / Switch D10

[0081] <pcs_route>PCS0_RT1< / pcs_route> / / Route PCS0_RT1

[0082] <pcs_route>PCS0_RT5< / pcs_route> / / Route PCS0_RT5

[0083] <pcs_route>PCS0_RT6< / pcs_route> / / Route PCS0_RT6

[0084] <pcs_route>PCS0_RT7< / pcs_route> / / Route PCS0_RT7

[0085] <pcs_section>PCS0_SEC1< / pcs_section> / / Section PCS0_SEC1

[0086] < / pcs_point> / / End of interlocked switch control relationship description

[0087] The number of basic elements can be embodied by the number of tags contained in the file, and the membership relationship can be embodied by the tag hierarchy relationship, which is not limited by the embodiments of the present application.

[0088] (2) Interlocking logic topology file is used to describe the input and output relationship between meta-models, the system level input and output relationship, and further, the meta-model instantiation sequence, which is the specific of interlocking specification at the business logic level. The input and output relationship between meta-models reflects the data flow relationship of different meta-models. The link relationship (internal input and output interface) between basic business logics in interlocking software is described by describing the data flow between ports of different meta-models, such as the input and output relationship between the ports of each turnout control logic meta-model, section control logic meta-model, signal control logic meta-model and route control logic meta-model. The system level input and output relationship is the association between the system input and output interface of interlocking software and meta-models (input and output interface between internal and external). The meta-model instantiation sequence is the processing sequence when instantiating meta-models in the process of generating interlocking software, such as the model instantiated first and the model instantiated later.

[0089] When generating interlocking software for the first time, the interlocking business logic is meta-modeled in the data preparation stage to generate meta-models and interlocking logic topology files. Different meta-models have different input and output relationships and system level input and output relationships in the interlocking logic topology file. The meta-models and the interlocking logic topology file have a corresponding relationship and are generated at the same time in the data preparation stage, and can meet the general interlocking software requirements, but will not be repeated for different meta-models, thereby providing comprehensive and basic interlocking software instantiation materials. When generating interlocking software again subsequently, the meta-models and interlocking logic topology files can be directly obtained without the need to build meta-models again, and only the line data topology file needs to be prepared in the data preparation stage. When the interlocking software has requirements other than the interlocking logic topology file for a specific station environment, the obtained interlocking logic topology file is modified according to the requirements to generate a new interlocking logic topology file.

[0090] The line data file includes the interlocking logic topology file and the line data topology file. The connection relationship of the line data file includes the control relationship in the line data topology file, the membership relationship and the input and output relationship between meta-models in the interlocking logic topology file, and the system level input and output relationship. The software and hardware relationship, the control relationship and the data flow relationship of the basic elements in the complex station environment are abstracted into two independent files, the interlocking logic topology file and the line data topology file, by the embodiments of the present application. The interlocking logic topology file and the line data topology file can be generated in different stages, respectively describe the universal meta-model relationship and the specific station line relationship, and are organically combined in the instantiation process to generate interlocking software suitable for the station environment, and realize flexible resource configuration.

[0091] Exemplarily, a fragment of the interlocking logic topology file is as follows, which describes the input and output relationship between the section control logic meta-model and the route control logic meta-model. Each line of data is explained and described after “ / / ”.

[0092] <topology> / / Topology relationship description begins: describe the input and output relationship between meta-models or system-level input and output relationship

[0093]

[0094]

[0095] Interlocking logic model generation phase

[0096] As shown in Figure 4 , the construction process of interlocking software, parsing the line data topology and interlocking logic topology file, generating interlocking software according to the description of line data topology and interlocking logic topology file. In the generation process of interlocking model, the strategy of first overall and then local, first framework and then details is adopted.

[0097] Parsing the line data topology file, determining the line structure of the station yard according to the number, attributes, membership relationship and control relationship of basic elements, and instantiating the business control logic model corresponding to the line structure based on the meta-model. For example, according to the number of signal machines, the signal machine control logic meta-model is instantiated into the signal machine control logic model, and the corresponding number of signal machine control logic models are copied to form a one-to-one relationship between the signal machine control logic and the actual signal machine entity in the line.

[0098] Because the resource configuration is set according to the attribute of the meta-model itself, when instantiating the interlocking software, the required reserved resources are dynamically calculated according to the number of meta-models that need to be instantiated. If the station yard scale is small, the number of instantiated meta-models is small, and a small amount of resources can be configured, if the station yard scale is large, the resources are reserved according to the business control logic model.

[0099] Parsing the interlocking logic topology file, integrating the input and output interfaces of all business control logic models with external interfaces into a system-level business data interface framework according to the system-level input and output relationship, that is, establishing the external interface relationship of the interlocking software as a whole system.

[0100] Parsing the line data topology file, setting the reserved parameters of the instantiated business control logic model according to the reserved parameters of the meta-model in the line data file. For example, the output data dimension of the route logic meta-model is different due to the different number of controlled sections, therefore, the output dimension is set as the reserved parameter, which can be set during instantiation, and different section business control logic models are generated according to the different set parameters.

[0101] The line data topology file and the interlocking logic topology file are parsed, and the business control logic models are linked according to the input and output relations (i.e. the port linking relations between the business logics), the meta-model instantiation sequence, and the membership relations and control relations of the basic elements, so as to generate the interlocking logic model. The linking refers to connecting the input and output ports of the models, and establishing a calling relation between the code functions of the models.

[0102] When the first-run business control logic model needs the output data of the second-run business control logic model, the first-run business control logic model is set to delay for one cycle to prevent the generation of an algebraic ring (so the second-run business control logic model is likely to need to use the output data of the first-run business control logic model, thereby causing a deadlock of mutual waiting), i.e. the first-run business control logic model takes the output data of the next cycle of the second-run business control logic model as the input data of the current cycle of the first-run business control logic model.

[0103] At this point, the interlocking logic kernel of the whole line is constructed.

[0104] Compilation stage

[0105] The interlocking logic model is used to generate the special interlocking software. As shown in FIG. 6, the interlocking logic model is adapted to the corresponding hardware platform interface for automatic compilation, and the interlocking logic model and the platform interface after automatic compilation jointly constitute the interlocking software, which is used as the special interlocking software applied to the special station yard line. Figure 5

[0106] Based on the same inventive concept, the embodiment of the present application also provides an interlocking software generation system based on the meta-model, as shown in FIG. 7, the system comprises: Figure 6 The meta-model acquisition module is used to acquire the meta-model of the interlocking basic element, and the meta-model describes the control logic of the basic element.

[0107] The file determination module is used to determine the line data file, and the line data file describes the layout and connection relation of the basic elements of the specified station yard.

[0108] The interlocking software generation module is connected with the meta-model acquisition module and the file determination module, and is used to generate the interlocking software based on the meta-model and the line data file.

[0109] The line data file comprises the interlocking logic topology file and the line data topology file, wherein the interlocking logic topology file and the meta-model can be generated simultaneously in the data preparation stage, so the file determination module can also be connected with the meta-model acquisition module.

[0110] The basic elements comprise a turnout, a signal machine, a section and a route.

[0111] The basic elements comprise a turnout, a signal machine, a section and a route.​

[0112] The specific implementation logic of the meta-model based interlocking software generation system of the embodiments of the present application can be obtained according to any of the above embodiments of the meta-model based interlocking software generation method, and will not be described again.

[0113] The method of the present application can be implemented by a computer or an embedded program controlled system. Therefore, correspondingly, the embodiments of the present application provide a meta-model based interlocking software generation system, as shown in the accompanying drawings, the system comprises at least one processor and at least one memory; the memory stores a computer program for executing the method of any of the embodiments of the present application, and the processor invokes the computer program in the memory to execute the method of any of the embodiments of the present application. Figure 7

[0114] Further, the memory can be communicatively connected with the one or more processors, and the memory stores instructions executable by the one or more processors, and the instructions are executed by the one or more processors to enable the one or more processors to implement the method of the present application.

[0115] Although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those skilled in the art that the technical solutions recorded in the foregoing embodiments can still be modified, or some of the technical features can be replaced by equivalents; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present application.​< / topology>

Claims

1. A method for generating interlocking software based on a meta-model, characterized in that, The method comprises the following steps: obtaining a meta-model of interlocking basic elements, the meta-model being basic data respectively modeled by control logic of the basic elements, wherein the control logic of each type of basic element corresponds to construction of one or more meta-models; determining a line data file, the line data file describing the layout and connection relationship of the basic elements of a specified station; the connection relationship of the line data file including control relationship in a line data topology file, input and output relationship between meta-models in an interlocking logic topology file, and system-level input and output relationship; determining the line data file comprises: determining an interlocking logic topology file and a line data topology file; wherein the line data topology file is automatically searched by a visual line drawing tool to generate routes; the line data topology file is used to describe the number, attributes, membership relationship and control relationship of interlocking basic elements; the interlocking logic topology file is used to describe the input and output relationship between meta-models, and the system-level input and output relationship; generating interlocking software based on the meta-model and the line data file; when the interlocking software is generated for the first time, the interlocking business logic is modeled in the data preparation stage to generate the interlocking logic topology file; wherein the meta-model has a corresponding relationship with the interlocking logic topology file, and is generated simultaneously in the data preparation stage; the basic elements include: switches, signal machines, sections and routes.

2. The meta-model based interlocking software generation method of claim 1, wherein, generating interlocking software based on the meta-model and the line data file comprises: parsing the line data topology and the interlocking logic topology file to generate the interlocking software according to the description of the line data topology and the interlocking logic topology file.

3. The meta-model based interlocking software generation method according to claim 2, characterized in that, generating interlocking software based on the meta-model and the line data file comprises: parsing the line data topology file to determine the line structure of the station according to the number, attributes, membership relationship and control relationship of the basic elements, and instantiating the business control logic model corresponding to the line structure based on the meta-model.

4. The meta-model based interlocking software generation method of claim 3, wherein, generating interlocking software based on the meta-model and the line data file comprises: parsing the interlocking logic topology file to integrate the input and output interfaces of all business control logic models having external interfaces into a system-level business data interface framework according to the system-level input and output relationship.

5. The meta-model based interlocking software generation method of claim 4, wherein, generating interlocking software based on the meta-model and the line data file comprises: parsing the line data topology file and the interlocking logic topology file to connect the business control logic models according to the input and output relationship between the meta-models, the instantiation sequence of the meta-models, and the membership relationship and control relationship of the basic elements, and generating an interlocking logic model.

6. The meta-model based interlocking software generation method according to any one of claims 3-5, characterized in that, generating interlocking software based on the meta-model and the line data file further comprises: parsing the line data topology file to set the reserved parameters of the instantiated business control logic model according to the reserved parameters of the meta-model in the line data file, so as to generate a differentiated business control logic model.

7. The meta-model based interlocking software generation method according to any one of claims 3-5, characterized in that, generating interlocking software based on the meta-model and the line data file further comprises: setting a first-running business control logic model to delay for one cycle when the output data of a second-running business control logic model is needed, so as to prevent the generation of an algebraic loop.

8. The meta-model based interlocking software generation method according to any one of claims 3-5, characterized in that, Generating interlocking software based on the meta-model and the line data file comprises: Adapting the corresponding hardware platform interface for the interlocking logic model for automatic compilation, and the interlocking logic model and the platform interface after automatic compilation together constitute the interlocking software.

9. The meta-model-based interlocking software generation method according to any one of claims 1-5, characterized in that, In the meta-model, the resource configuration volume is set according to the meta-model itself attribute.

10. A meta-model based interlocking software generation system, characterized by, Comprise: The meta-model acquisition module is used for acquiring the meta-model of the interlocking basic element, and the meta-model is the basic data obtained by modeling the control logic of the basic element respectively, wherein the control logic of each type of basic element corresponds to build one or more meta-models; The file determination module is used for determining a line data file, and the line data file describes the layout and connection relationship of the basic elements of a specified station; the connection relationship of the line data file includes the control relationship in the line data topology file, the membership relationship, and the input and output relationship between the meta-models in the interlocking logic topology file, and the system-level input and output relationship; Determining the line data file comprises: Determining the interlocking logic topology file and the line data topology file; wherein determining the line data file refers to writing, generating or acquiring the interlocking logic topology file and the line data topology file; the line data topology file is automatically searched by a visual line drawing tool to generate a route; the line data topology file is used to describe the number, attributes, membership relationship and control relationship of the interlocking basic elements; the interlocking logic topology file is used to describe the input and output relationship between the meta-models, the system-level input and output relationship; The interlocking software generation module is used for generating interlocking software based on the meta-model and the line data file; when generating the interlocking software for the first time, the interlocking business logic is meta-modeled in the data preparation stage to generate the interlocking logic topology file; wherein the meta-model has a corresponding relationship with the interlocking logic topology file, and is generated at the same time in the data preparation stage; The basic elements include: switches, signal machines, sections and routes.

11. A meta-model based interlocking software generation system, characterized by, The system comprises at least one processor and at least one memory; the memory stores a computer program for executing any one of the methods of claims 1-9, and the processor calls the computer program in the memory to execute the method of any one of claims 1-9.

Images