KR101157485B1 - System, apparatus and method for integrated middleware supporting mil-std-1553b - Google Patents

Abstract

PURPOSE: A system, an apparatus, and a method for integrated middleware supporting MIL-STD-1553B are provided to manage a library through matching. CONSTITUTION: A binding management module(130) manages connection between a detected device and an application program embodied as a provided integrated library. When the connection between the library of the detected device and integrated library exists, a device driving module(170) extracts the library of the detected device which is matched with the integrated library from a library storage module(190). The device driving module drives the detected device.

Description

Integrated middleware system, apparatus, and method that supports MIL-STD-1525K {SYSTEM, APPARATUS AND METHOD FOR INTEGRATED MIDDLEWARE SUPPORTING MIL-STD-1553B}

The present invention relates to an integrated middleware system, apparatus, and method for supporting MIL-STD-1553B. More specifically, MIL-STD-1553B allows a given application to be run on MIL-STD-1553B equipment from different manufacturers. It relates to an integrated middleware system, apparatus and method for supporting the above.

The MIL-STD-1553B has been widely used in various weapon systems as well as in avionics since its establishment in the 1970s. Despite its long history, MIL-STD-1553B is still in the spotlight due to its stability, reliability, and ease of system integration. Communication bus standard.

However, due to the unique library and communication specificity of each MIL-STD-1553B equipment manufacturer, there is a problem that the development and use of the application program is limited. For example, each MIL-STD-1553B equipment manufacturer provides its own non-standardized software library to its users, and as a result, the applications required to operate the equipment are also dependent on each manufacturer.

Accordingly, when using the MIL-STD-1553B equipment of other manufacturers it is impossible to use the existing application program, there is a problem to develop a new application program.

It is an object of the present invention to provide an integrated middleware system, apparatus, and method that supports MIL-STD-1553B such that certain applications are run on different manufacturers' MIL-STD-1553B equipment.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory and are not intended to limit the invention to the precise forms disclosed. Other objects, which will be apparent to those skilled in the art, It will be possible.

The integrated middleware system supporting the MIL-STD-1553B of the present invention for achieving the above object is a device detection module for detecting a mounted MIL-STD-1553B equipment, a library storage module for storing a library for the detected equipment A binding management module for managing a linkage between the detected device and an application program implemented with a provided integrated library, a library management module for matching and managing the integrated library and a library of the detected device with each other, and the linkage If it is determined that there is a reference to the library management module may include a device driving module for extracting the library of the detected equipment matching the integrated library in the library storage module to drive the detected equipment.

In this case, the integrated library may further include a storage module for storing the integrated library.

Meanwhile, the integrated middleware device supporting MIL-STD-1553B of the present invention is a library storage module that stores a library of MIL-STD-1553B equipment, and an interface between the device and an application program implemented as a provided integrated library. It may include a binding management module for managing and a library management module for matching and managing the integrated library and the library of the device.

In this case, the library storage module may be a library of a bus controller module defined in MIL-STD-1553B, a library of a remote terminal module, a library of a remote terminal to remote terminal (RT2RT) module, a bus monitor ( And a common library storage module for storing at least one of a library of a bus monitor module and a specialized library storage module for storing a library independently used by a manufacturer who manufactures the equipment.

In addition, if the device detected by the device detection module is not already registered, the binding management module checks the connection between the application and the device and binds and registers the device with the application to the application. can do.

The library management module may generate a mapping table in a form in which a pointer address indicating a library of the device stored in the library storage module is matched with the integrated library.

On the other hand, the integrated method of supporting the MIL-STD-1553B of the present invention is to calculate the number of MIL-STD-1553B equipment is detected that the installation, if the number of the calculated equipment is one of the operating application currently in operation and Binding and registering in a binding table indicating an association with an application program implemented as an integrated library, and searching the binding table to determine whether the device is registered and bound with the operation application when there are a plurality of calculated devices; If the search result is registered, binding the registered device with the operation application to register in the binding table; and if the search result is not registered, registering the selected device among unregistered devices with the operation application to register in the binding table. It may include a step.

As described above, an integrated middleware system, apparatus, and method for supporting MIL-STD-1553B according to the present invention is implemented as an integrated library by matching and managing an integrated library and a library required by the MIL-STD-1553B device. Applications can be run on a variety of MIL-STD-1553B instruments.

1 is a block diagram illustrating an integrated middleware system supporting MIL-STD-1553B in accordance with the present invention.
Figure 2 is a block diagram showing an integrated middleware device supporting MIL-STD-1553B associated with the present invention.
3 is a schematic diagram illustrating a binding table generated in a binding management module in an integrated middleware device supporting MIL-STD-1553B related to the present invention.
4 is a schematic diagram illustrating a mapping table generated in a library management module in an integrated middleware device supporting MIL-STD-1553B related to the present invention.
5 is a flow chart illustrating an integration method for supporting MIL-STD-1553B associated with the present invention.

Hereinafter, an integrated middleware system, apparatus, and method for supporting MIL-STD-1553B related to the present invention will be described in detail with reference to the accompanying drawings.

1 is a block diagram illustrating an integrated middleware system supporting MIL-STD-1553B according to the present invention.

The integrated middleware system supporting the MIL-STD-1553B shown in FIG. 1 includes a device detection module 110 for detecting a mounted MIL-STD-1553B device, and a library storage module 190 for storing a library for the detected device. ), A binding management module 130 that manages the linkage between the detected device and an application program implemented by a provided integrated library, and a library management module that matches and manages the integrated library and the library of the detected device. If it is determined that there is the linkage, the device driving module 170 for extracting a library of the detected equipment matching the integrated library from the library storage module with reference to the library management module to drive the detected equipment ) Is included.

The device detection module 110 detects MIL-STD-1553B devices that are installed in a system in which middleware is mounted. As a result of the detection, the identification number of the mounted MIL-STD-1553B device or the manufacturer's identification number can be obtained. The equipment detection module may be configured as an equipment automatic recognition agent.

The library storage module 190 may store a library for the detected equipment or may be the library itself. Libraries for the detected devices include libraries of Bus Controller modules, libraries of Remote Terminal modules, libraries of Remote Terminal To Remote Terminal (RT2RT) modules, and bus monitors as defined in the MIL-STD-1553B standard. It includes a common library, such as the library of the Bus Monitor module, and a library used independently by the manufacturer making the MIL-STD-1553B.

The binding management module 130 manages the linkage between the detected application and the application program implemented by the provided integrated library. The present invention is directed to an application program implemented as an integrated library provided or provided in an integrated middleware. Even if the intended application is intended to be used on various MIL-STD-1553B devices, the MIL-STD-1553B device and the application must be related to each other. For example, if A application is applied to MIL-STD-1553B equipment for B purpose, normal operation will not work. Therefore, the application program for the purpose of A should be applied to the MIL-STD-1553B equipment for the purpose of A. The relationship between the application program operated for the same purpose and the MIL-STD-1553B equipment will be referred to as connectivity.

Management of connectivity can be achieved by specifically binding the application and MIL-STD-1553B equipment as shown in Figure 3 by binding (solid line) to register in the binding table. In this case, the binding indicates that there is a connection between the application and the MIL-STD-1553B device. The binding table may be as shown in FIG. 3.

The library management module 150 matches and manages an integrated library for implementing an operation application program and a library of detected MIL-STD-1553B devices. Even if the application is implemented as an integrated library, it cannot be operated on the MIL-STD-1553B device unless the integrated library is supported by the MIL-STD-1553B device. In the present invention, at least for the application program implemented as an integrated library to be able to operate in a variety of MIL-STD-1553B equipment (of course there must be connectivity). To do this, the MIL-STD-1553B equipment that matches the integrated library should be used instead of the integrated library, considering the MIL-STD-1553B equipment that does not support the integrated library. At this time, the library of the MIL-STD-1553B device is stored in the library storage module, so instead of matching the integrated library, it is necessary to match the library of the MIL-STD-1553B device with the integrated library to extract the appropriate library of the MIL-STD-1553B device. . This matching is performed in the library management module.

The library management module may generate and use a mapping table as shown in FIG. 4 to match the library of the MIL-STD-1553B device and the integrated library.

The equipment driving module 170 is a module for driving MIL-STD-1553B equipment. In order to run MIL-STD-1553B, there must be MIL-STD-1553B. This confirmation is made in the equipment detection module 110. Next, there must be an application program to properly operate the MIL-STD-1553B equipment, and the library used to implement the application program and the library of the MIL-STD-1553B equipment must be identical. The existence of the application to operate the MIL-STD-1553B device is identified by the binding management module, and the identity of the library is mitigated by the library management module. In other words, the library used for the implementation of the application program is an integrated library, but the library management module and the library storage module allow the MIL-STD-1553B device to use its own library.

Therefore, the device driving module can allow an application program implemented as an integrated library to be operated on various MIL-STD-1553B devices using different libraries.

Looking at the above configuration, you can see that the integrated library is not required. This is because the library actually used is a library of MIL-STD-1553B devices. Of course, an integrated library may be included in the MIL-STD-1553B's library.

The integrated middleware system supporting MIL-STD-1553B may further include an integrated library storage module 180 for storing the integrated library. The integrated library storage module can also support MIL-STD-1553B using the integrated library, which is useful when you want to write an application that is implemented as an integrated library through the attached MIL-STD-1553B instrument.

2 is a block diagram illustrating an integrated middleware device supporting MIL-STD-1553B according to the present invention.

The integrated middleware device supporting MIL-STD-1553B shown in FIG. 2 is a library storage module 290 for storing a library of MIL-STD-1553B equipment, and an application program implemented with the integrated library provided with the equipment. Binding management module 230 for managing the connectivity between the library and the library management module 250 for managing the matching library and the library of the device to match each other.

The library storage module 290 is a library of bus controller modules defined in MIL-STD-1553B, a library of remote terminal modules, a library of remote terminal to remote terminal (RT2RT) modules, and a bus monitor ( A common library storage module 291 for storing at least one of a library of a bus monitor module and a specialized library storage module 293 for storing a library independently used by a manufacturer who manufactures the equipment may be included.

The library storage module can update the library stored according to the revision of MIL-STD-1553B standard, the update of the library used independently by each manufacturer, or the new version.

On the other hand, the library storage module can reduce the total capacity by storing only the library of the MIL-STD-1553B equipment that is expected to be mounted.

As described above with reference to FIG. 1, the binding management module 230 may check the connectivity between the application program implemented as the integrated library and the MIL-STD-1553B device, bind each other, and manage the binding table. The application can be extracted from the MIL-STD-1553B installed by the binding management module, and on the contrary, the MIL-STD-1553B can be selected.

If the MIL-STD-1553B device detected by the device detection module is not already registered, the binding management module checks the connection between the application and the device (which may be plural), and connects the device with the connection to the application. You can register by binding. That is, the binding management module can be updated. The bindings and binding updates made in the binding management module can be done automatically or manually.

Although the MIL-STD-1553B and the appropriate application are bound in the binding management module, the bound application must be implemented as a library of MIL-STD-1553B in order to operate normally on the MIL-STD-1553B. However, if an application implemented by a library provided by an existing manufacturer is bound to a device of another third party, and the integrated library is not included in the MIL-STD-1553B device's library, normal operation is not possible in this state.

The library management module 250 replaces the integrated library implementing the bound application program with a library of matching MIL-STD-1553B equipment. As a result, both bound applications and MIL-STD-1553B devices work properly.

As illustrated in FIG. 4, the library management module may generate a mapping table in a form in which a pointer address indicating a library of the MIL-STD-1553B device stored in the library storage module is matched with the integrated library. The generated mapping table can be used by various means such as an equipment driving module.

According to the above configuration, a matching is made between the integrated library used to implement the application program and the library of the MIL-STD-1553B device. With this status, the same application can be used on a variety of MIL-STD-1553B instruments, and multiple applications can be run on the same MIL-STD-1553B instruments.

5 is a flowchart illustrating an integration method for supporting MIL-STD-1553B related to the present invention.

The integrated method of supporting the MIL-STD-1553B shown in FIG. 3 relates to a method of binding to a currently running application program according to the number of MIL-STD-1553B devices largely installed, and is registered in FIG. 1 or 2. It may be described as the operation of the binding management module.

Integrated middleware that supports MIL-STD-1553B usually works to run the application. Therefore, when the integrated middleware is operated, there is an operating application that is an operating application.

First, the number of MIL-STD-1553B equipment that is detected to be installed is calculated (S 510).

If the calculated number of MIL-STD-1553B devices is 0 (S520), the binding management module terminates the operation.

If the calculated number of MIL-STD-1553B equipment is one (S520), the binding is performed with the currently running operating application program and registered in the binding table indicating the linkage with the application program implemented as the integrated library (S560). If there is an operational application with the estimated number of MIL-STD-1553B units being one, then this application will be for one MIL-STD-1553B unit. Therefore, the binding is registered immediately in the binding table without considering whether or not it is already registered in the binding table. The binding and registration are done automatically. At this time, if wrong binding is made, manual unbinding is possible. That is, the binding table of the binding management module can be updated manually by the user.

If there are multiple calculated MIL-STD-1553B devices, there can be a problem if all the detected devices are bound to the application and registered. This is because only a few of the MIL-STD-1553B units with multiple operational applications can be targeted.

Therefore, in this case, the binding table searches whether the MIL-STD-1553B device is registered with the operation application program (S530).

If it is registered as a search result (S540), the registered device is bound to the operation application program and registered in the binding table (S560). At this time, binding and registration are done automatically.

If the search result is not registered, the selected device (S 550) among the unregistered devices is bound to the operation application program and registered in the binding table (S 560). All devices detected as a result of the search may be unregistered devices, and only some of them may be unregistered devices. In either case, there may be MIL-STD-1553B equipment to which the user wishes to apply an operational application. At this time, the user can manually select the applicable MIL-STD-1553B device and bind it to the operation application to register in the binding table.

Using the binding table generated through the above process, the library management module matches the library of the MIL-STD-1553B device with the integrated library.

It will be understood by those skilled in the art that the present invention may be embodied in other specific forms without departing from the spirit or essential characteristics thereof. It is therefore to be understood that the embodiments described above are to be considered in all respects only as illustrative and not restrictive. The scope of the present invention is defined by the appended claims rather than the detailed description and all changes or modifications derived from the meaning and scope of the claims and their equivalents are to be construed as being included within the scope of the present invention do.

Applicable to communication systems using MIL-STD-1553B equipment.

It is particularly useful for communication systems where the replacement of MIL-STD-1553B equipment or application is frequent.

110 ... Equipment Detection Module 130, 230 ... Binding Management Module
150, 250 ... Library Management Module 170 ... Equipment Drive Module
190, 290 ... Library Storage Modules

Claims (7)

Equipment detection module for detecting equipped MIL-STD-1553B equipment;
A library storage module for storing a library for the detected equipment;
A binding management module that manages the linkage between the detected device and an application program implemented with a provided integrated library;
A library management module for matching and managing the integrated library and the library of the detected equipment with each other;
An equipment driving module configured to drive the detected equipment by extracting a library of the detected equipment matching the integrated library from the library storage module with reference to the library management module;
Middleware system supporting MIL-STD-1553B, including.
The method of claim 1,
Integrated middleware system supporting MIL-STD-1553B, further comprising an integrated library storage module for storing the integrated library.
A library storage module for storing a library of MIL-STD-1553B equipment;
A binding management module that manages the linkage between the device and an application program implemented by a previously provided integrated library; And
A library management module for matching and managing the integrated library and the library of the device with each other;
Middleware device that supports MIL-STD-1553B, including.
The method of claim 3, wherein
The library storage module
Among the libraries of the Bus Controller module, the library of the Remote Terminal module, the library of the Remote Terminal To Remote Terminal (RT2RT) module, and the library of the Bus Monitor module as defined in MIL-STD-1553B. A common library storage module for storing at least one; And
Integrated middleware device that supports MIL-STD-1553B, comprising; a specialized library storage module for storing a library independently used by a manufacturer that manufactures the equipment.
The method of claim 3, wherein
The binding management module checks the connection between the application and the device when the device detected by the device detection module is not already registered, and binds and registers a device having a connection to the application. Featured integrated middleware device supporting MIL-STD-1553B.
The method of claim 3, wherein
The library management module supports MIL-STD-1553B, wherein the library management module generates a mapping table in which a pointer address indicating a library of the device stored in the library storage module is matched with the integrated library.
Estimating the number of MIL-STD-1553B equipment in which mounting was detected;
If the calculated number of devices is one, binding to a currently running operating application and registering it in a binding table indicating connectivity with an application implemented as an integrated library;
If the calculated equipment is plural, searching in the binding table whether the equipment is registered by being bound to the operation application program;
If the search result is registered, binding the registered device with the operation application program and registering the registered device in the binding table; And
If the search result is unregistered, binding a selected device among unregistered devices with the operation application program and registering it in the binding table;
Integration method to support MIL-STD-1553B including.

Images