KR20080040103A - Software communication architecture based system for supporting component hot-swapping and supporting method thereof - Google Patents

Abstract

An SCA(Software Communication Architecture)-based system for supporting component hot-swapping and a supporting method thereof is provided to realize efficient system control and continuous operation even if a component is downed or replaced during the operation by realizing component hot-swapping in an application of the SCA-based system. An application module(140) is installed/operated in an SCA-based system(100) and is packaged into a plurality of components(144a-144n). A domain manager(131) provides a method for installing/canceling an application(141) in the application module, and an application update method supporting application component hot-swapping. A resource interface has a parameter for appointing a predetermined application component to start or stop the application component in the application module. An application factory(133) interface sets up connection with other application components after the application component is generated and replaced. The application update method appoints the application component of one application to be replaced, replaces the application component by clarifying an XML(eXtensible Markup Language) file(143a-143n) for the application component, and performs needed processes.

Description

SCA based system supporting component hot swapping and supporting method {Software Communication Architecture based System for supporting Component Hot-Swapping and Supporting Method}

1 is a schematic diagram of an SCA-based system supporting component hot swapping according to an embodiment of the present invention.

2 is a diagram illustrating a core framework interface of an SCA-based system according to an embodiment of the present invention.

3 is a diagram illustrating modified interfaces among core framework interfaces of an SCA-based system according to an embodiment of the present invention.

4 is a flowchart illustrating an application installation and instance creation method of an SCA-based system according to an exemplary embodiment of the present invention.

5 is a flowchart illustrating a method for processing component hot swapping in an SCA-based system according to an exemplary embodiment of the present invention.

6 is an operation flowchart illustrating a method of uninstalling an application and removing an instance of the SCA-based system according to an embodiment of the present invention.

The present invention relates to a software communication architecture (SCA) based system and a method for supporting the same, and more particularly, to an SCA based system and a method for supporting the component hot-swapping.

SCA is a standardized communication software structure that the Joint Tactical Radio System (JTRS) Joint Program Office (JPO) of the United States has proposed to greatly improve interoperability between communication systems and reduce development and deployment costs. The SCA adopts a common object request broker architecture (CORBA), which is an industry standard for a real-time operating system (OS) and a distributed object model, as a middleware to provide an integrated environment of heterogeneous hardware and software. This is an independent system design framework, not a specification specific to a particular system.

SCA-based system refers to a communication system or device based on this SCA structure. For example, SDR (Software Defined Radio) systems adopt SCA as a standard for software frameworks. In SCA, one application executes by installing or deploying several application components in one package.

Currently, a small number of systems using SCA-based software frameworks are being released, but the current version is constantly being upgraded with bug fixes and feature enhancements. Also, the SCA standard provides deployment level software component technology. It does not provide a mechanism to store or manage component files that can be deployed and replaced, and does not provide a mode switching method through software.

 The existing SCA standard configures SW components to be deployed as one application package, so that the deployment, operation, and control are carried out in package units, and when the replacement is necessary due to the update of a specific component in the application, the entire application is terminated. After that, the application package including the new component has to be redeployed and run, which is very inconvenient.

The technical problem to be solved by the present invention, SCA-based system that supports component hot swapping to more efficiently control the SCA-based system by changing and modifying the interface to support hot swapping in the SCA-based system And to provide a method of implementation thereof.

SCA based system according to one feature of the present invention for achieving the above object,

An application module disposed and driven in an SCA-based system and packaged into a plurality of application components; A domain manager interface for providing a method for installing and uninstalling an application in the application module and an application updating method for supporting hot swapping of the application component; A resource interface having a parameter specifying the specific application component to start or stop only a specific application component in the application module; And an application factory interface for establishing a connection with other application components after creation and replacement of the specific application component.

Hot swapping support method in an SCA-based system according to another aspect of the present invention,

a) modifying a domain manager interface, a resource interface, and an application factory interface included in the SCA based system to enable hot swapping functions; b) designating an application component to be replaced in the application module and terminating the previous application component; c) loading and executing the application component to be replaced; And d) resetting the connection associated with the application component to be replaced.

Hereinafter, an SCA-based system supporting component hot swapping and an implementation method thereof will be described in detail with reference to the accompanying drawings.

In general, hot-swapping refers to a technology for connecting and using various peripheral devices without turning off a computer. The hot-swapping according to an embodiment of the present invention is replaced due to an update of a specific component in an application. If you need to, you can relocate and run an application package containing new components without shutting down the entire application.

1 is a schematic configuration diagram of an SCA-based system supporting component hot swapping according to an embodiment of the present invention, and is a configuration diagram of an SCA-based system according to an embodiment of the present invention as viewed from the perspective of SCA-based software functional components. .

Referring to FIG. 1, the SCA-based system 100 according to an embodiment of the present invention basically includes a real-time operating system 110 and also includes a CORBA middleware 120 defined in the SCA standard.

In addition, a reconfigurable core framework (RCF) 130 based on SCA is disposed on the operating system 110 and the CORBA middleware 120. The reconfigurable core framework 130 is a domain manager. It is composed of several components such as a manager: 131, a device manager 132, an application factory 133, and a file manager 134 to support system reconfiguration. Accordingly, a plurality of applications 140 for software control and configuration are composed and packaged with application components 144a-144n.

Here, the domain manager 131 of the reconfiguration core framework 130 is responsible for registering and releasing devices and applications. In addition, for many logical devices that functionally abstract hardware devices, device manager 132 manages these multiple devices.

In addition, a plurality of XML (eXtensible Markup Language) files 143a to 143n describe hardware and software information, and the application factory 133 of the reconstruction core framework 130 is responsible for generating the application 140. In an embodiment of the present invention, the application factory 133 enables the transmission and reception of data by establishing a connection between the components described in the plurality of XML files 143a to 143n and the components 144a to 144n.

According to an embodiment of the present invention, the SW components are connected to each other by using an operator interface that is in charge of downloading, deploying, and driving an application package to the communication device 100 in association with the domain manager 131 of the reconfiguration core framework 130. It is configured as an application package and placed and run on an execution device. At this time, application package information, component package information, component information, and the like are described in each of the XML files 143a to 143n.

In addition, one domain manager 131 exists in the framework, and has all the information in the framework and plays a key role in controlling it.

An embodiment of the present invention performs a hot swapping function through a procedure of designating and terminating a specific component to be replaced, loading and executing a new component, and then reestablishing a connection related to the new component. This will be described in detail with reference to FIG. 6.

2 is a diagram illustrating a core framework interface of an SCA-based system according to an embodiment of the present invention.

2, a core framework interface of an SCA-based system according to an embodiment of the present invention may include a base application interface 210, a framework control interface 220, and a framework service interface. (Framework Service Interface: 230).

The base application interface 210 includes a port interface 211, a port provider interface 212, a lifecycle interface 213, a test object interface 214, a property set interface 215, a resource interface 216, and a resource. It consists of several interfaces, such as factory interface 217, which are the interfaces necessary for the application 140 shown in FIG. 1 to basically operate.

The framework control interface 220 is an interface for creating, managing, and controlling resources in the framework. The framework control interface 220 includes an application interface 221, an application factory interface 222, a domain manager interface 223, a device interface 224, The load device interface 225, the execution device interface 226, the aggregation device interface 227, the device manager interface 228, and the like.

Finally, the framework service interface 230 is a service related interface in the framework, and mainly refers to file related interfaces, and includes a file interface 231, a file system interface 232, a file manager interface 233, and a time interface. ).

Here, the domain manager 223 interface, the device manager interface 228, the application factory interface 222, and the file manager interface 233 illustrated in FIG. 2 are the domain manager 131 and the device manager 132 illustrated in FIG. 1. ), An interface corresponding to the application factory 133 and the file manager 134.

As described above, one domain manager interface 223 according to an embodiment of the present invention exists in the framework, has all the information in the framework, and plays a key role in controlling it.

Meanwhile, FIG. 3 is a diagram illustrating changed interfaces among core framework interfaces of an SCA-based system according to an embodiment of the present invention, wherein the changed domain manager interface 223, resource interface 216, and application factory interface for hot swapping are illustrated. (222) is shown.

The domain manager interface 223 stores information about various application interfaces 221, application factory interfaces 222, device manager interfaces 228, file manager interfaces 233, and domain manager profile interfaces in the framework. Provides methods for installing and uninstalling applications, registering and releasing devices and services, and registering and releasing event channels. Here, methods are functions that belong to an object or class.

In addition, the domain manager interface 223 according to an embodiment of the present invention is a function for hot swapping in addition to this function, and an application update method (updateApplication () method) is added. Here, the application update method may specify a component in one application to be replaced, specify and replace an XML file for this component, and then perform necessary processing subsequently.

The resource interface 216 adds a parameter to a start method (start () method) and a stop method (stop () method) to designate a specific component so that only a specific component can be started or stopped.

Finally, the application factory interface 222 has a create () method that creates a particular application, and also specifies the component to be replaced and the XML files associated with that component, thereby creating another component after creation and replacement of the component. In addition, an update method (update () method) is further provided to enable processing such as connection establishment.

Meanwhile, FIG. 4 is a flowchart illustrating an application installation and instance creation method of an SCA-based system according to an exemplary embodiment of the present invention.

Referring to Figure 4, the application installation and instance creation method of the SCA-based system according to an embodiment of the present invention are as follows.

First, a user executes an application installation command (installApplication) to install an application through the graphical user interface (GUI) 401 (S401). At this time, the application installation command is described as app1_SAD.xml in the form of an XML file. Here, SAD represents a Software Assembly Descriptor. In addition, the GUI 401 means a user.

Next, the domain manager 402 parses the app1_SAD.xml to generate the corresponding application factory 403, checks files specified in the SAD file (S402), and the generated application factory 403 generates the SAD.xml. A SAD parser 404 is generated to parse the file (S403).

Next, the user 401 executes an application factory information acquisition command to obtain information of the currently installed application factory 403 (S404), and the domain manager 402 of the currently installed application factory 403 The list is notified to the user 401 (S405).

Subsequently, the user 401 selects the corresponding application factory 403 to generate a specific application app1, executes an application instance creation command (S406), and the application factory 403 from the SAD parser 404. Request information of components to be executed (S407).

Next, the SAD parser 404 provides information such as an SPD and an SCD file of components to be executed (S408). Here, SPD is an abbreviation for Software Package Descriptor, and SCD is an abbreviation for Software Component Descriptor.

Thereafter, the SCD parser 405 is executed from the provided information to obtain information of the required SCD file (S409). In addition, the SPD parser 406 is generated to parse all the information necessary for generating the component (S410).

Next, the application factory 403 loads or executes all the components included in the file to the specified location using the information obtained from the SPD and SCD file (S411), and the execution device 407 is an assembly controller ( Create a process of 408 (S412), and also, the execution device 407 generates a process of components of a specific application (app1) (S413).

Subsequently, the application factory 403 requests information of the assembly controller 408 from the SAD parser 404 (S414), and the SAD parser 404 provides information about the assembly controller 408 (S415). The application factory 403 requests SAD instance creation information from the SAD parser 404 (S416), and the SAD parser 404 provides SAD instance creation information (S417).

Thereafter, the application factory 403 initializes the assembly controller 408 and configures parameters (S418). In addition, the application factory 403 initializes the generated components and configures the parameters (S419).

Next, the application factory 403 requests connection information from the SAD parser 404 (S420), the SAD parser 404 provides connection information (S421), and the application factory 403 provides the connection information. A connection is established by calling a port acquisition method (getPort () method) and a port connection method (connectPort () method) of each component by using S422.

A new application (app1) object is created through the above process (S423).

Next, the generated new application (app1) registers itself to the domain manager 402 through the application registration command (S424), the application factory 403 notifies the user 401 of the successful installation of the new application (app1) In operation S425, the user 401 executes a start command method (start () method) in order to operate the generated new application app1 (S426).

Then, the new application (app1) transmits a start command method (start () method) to the assembly controller 408, which is its agent (S427), the assembly controller 408 is all components of the specific application (app1) The start command method (start () method) is transmitted to the user (S428).

Then, the user executes the configuration command method (configure () method) to change the value of the parameter of the generated application app1 (S429).

Next, Application app1 transmits a configuration command method (configure () method) to the assembly controller 408, which is its agent (S430), and the assembly controller 408 identifies a specific application (app1) to which a parameter to change a value belongs. The configuration command method (configure () method) is transmitted to the components (S431). This completes both application installation and instance creation of the SCA-based system.

5 is a flowchart illustrating a method of processing component hot swapping in an SCA-based system according to an exemplary embodiment of the present invention.

Referring to FIG. 5, a method for processing component hot swapping of an SCA-based system according to an embodiment of the present invention is as follows.

First, the user 501 executes an application update command to replace a specific component in an application (S501).

Next, the domain manager 502 executes a stop command method (stop (com1) method) to stop the operation of the component com1 to replace the specific application (app1) 504 (S502), and the specific application (app1: 504 sends a stop command method (stop (com1) method) for stopping the operation of the component com1 to be replaced to the assembly controller 505 (S503).

Thereafter, when the assembly controller 505 sends a stop command method (stop (com1) method) to the corresponding replacement component com1, the replacement component com1 stops operation (S504), and the domain manager 502 replaces the replacement. In order to remove the component com1, a specific component removal command is transmitted to the execution device 507 (S505).

Subsequently, the execution device 507 terminates the process through the process termination command of the corresponding replacement component com1 (S506), and the domain manager 502 executes the replacement component com1, SAD, and SPD to execute the new component. In operation S507, the application factory 503 generates an XML parser 508 to parse XML files of the received SAD, SPD, and SCD. In this case, parsing of XML files is requested using the generated XML parser 508 (S508).

Next, after the application factory 503 loads and executes the replacement component com1 based on the parsed result (S509), the execution device 507 generates a process of the new replacement component com1 (S510). The application factory 503 initializes and configures a new component com1 (S511).

Thereafter, the application factory 503 requests the XML parser 508 for connection information associated with the replacement component com1 (S512), and the XML parser 508 provides the connection information (S513). 503 resets a new connection associated with the new replacement component com1 based on the provided connection information (S514), and the domain manager 502 specifies a start (com1) command to operate the generated replacement component com1. The application is sent to the app app 504 (S515).

Subsequently, the specific application (app1) 504 sends a start command (start (com1)) to the assembly controller 505, which is acting on its behalf (S516), and the assembly controller 505 starts to the replacement component com1. The replacement component com1 may be operated by transmitting a command start () (S517).

Next, when the domain manager 502 informs the user 401 of the successful replacement of the component com1 (S518), the user changes the value of the parameter of the changed specific application (app1: 504). ) method) (S519).

Then, the specific application (app1: 504) sends a configuration command method (configure () method) to the assembly controller 505, which is its agent (S520), the assembly controller 505 is the application (504) belonging to the parameter to change the value. Send a configuration command method (configure () method) to a specific component of the (S521). Accordingly, the component hot swapping process of the SCA based system according to the embodiment of the present invention is completed.

6 is a flowchart illustrating a method of uninstalling an application and removing an instance of an SCA-based system according to an exemplary embodiment of the present invention.

First, the user 601 executes a stop command method (stop () method) in order to stop the operation of a specific application (app1: 604) (S601).

Next, the specific application (app1: 604) sends a stop command method (stop () method) to the assembly controller 605, which is its agent (S602), and the assembly controller 605 sends all of the specific applications (app1: 604). A stop command method (stop () method) is transmitted to stop the operation of the component (S603).

Then, the user executes an object release command (releaseObject) to terminate the specific application (app1: 604) (S604).

Thereafter, the specific application (app1 604) executes an application deregistration command to the domain manager 602 to modify the information content of the domain manager 602 (S605), and the specific application (app1: 604) is an assembly controller. When the object release command (releaseObject) is transmitted to the step 605 (S606), the assembly controller 605 delivers the object release command (releaseObject) to all the components (S607).

Next, when the user 601 executes an application deregistration command to release a specific application 604 (S608), the domain manager 602 removes the specific application 604 from the application factory 603 list (S609). In operation S610, the domain manager 602 notifies the user 401 of the successful release of the application 604. This completes application uninstallation and instance removal of the SCA-based system.

As a result, an embodiment of the present invention can be applied to all systems having an SCA structure by changing or modifying the core framework and interfaces of various administrators to support hot swapping of components in an application in an SCA-based system. This SCA structure can be applied to SDR (Software Defined Radio) system.

Although embodiments of the present invention have been described above with reference to the accompanying drawings, those skilled in the art to which the present invention pertains may implement the present invention in other specific forms without changing the technical spirit or essential features thereof. I can understand that. Therefore, the embodiments described above are to be understood in all respects as illustrative and not restrictive.

According to the present invention, by enabling hot swapping of specific components in the application of the SCA-based system, it is possible to control the system more efficiently, and continue to operate without interruption even if any component is down or replaced during operation of the SCA-based system. can do.

Claims (11)

An application module arranged and driven in a Software Communication Architecture (SCA) based system and packaged into a plurality of application components; A domain manager interface for providing a method for installing and uninstalling an application in the application module and an application updating method for supporting hot swapping of the application component; A resource interface having a parameter specifying the specific application component to start or stop only a specific application component in the application module; And Application Factory Interface (Application Factory) for establishing a connection with other application components after creation and replacement of the specific application component SCA based system comprising a. The method of claim 1, The application update method designates a specific application component in one application to be replaced, specifies and replaces an XML file for the specific application component, and then performs necessary processing. The method of claim 1, And wherein said resource interface has parameters for specifying said particular application component in a start method and a stop method. The method of claim 1, The application factory interface, SCA-based system, characterized in that it comprises a generation method for generating the specific application component, and an update method for the connection settings. The method of claim 1, And the application factory interface specifies an application component to be replaced and XML files associated with the application component. a) changing a domain manager interface, a resource interface, and an application factory interface included in the SCA based system to enable hot-swapping functions; b) designating an application component to be replaced in the application module and terminating the previous application component; c) loading and executing the application component to be replaced; And d) resetting the connection associated with the application component to be replaced; Hot swapping support method in the SCA-based system comprising a. The method of claim 6, In step a), And the domain manager interface provides an application update method to support hot swapping of the application component. The method of claim 7, wherein The application update method designates one application component to be replaced in an application module, specifies and replaces an XML file for the specified application component, and then performs necessary processing. How to support swapping. The method of claim 6, In step a), And wherein the resource interface has parameters in a start method and a stop method that specify the specific application component to start or stop only a specific application component in the application module. The method of claim 6, In step a), And the application factory interface generates an application component included in an application module and establishes a connection with other application components after creation and replacement of the application component. The method of claim 10, And the application factory interface specifies an application component to be replaced and XML files associated with the application component.

Images