KR20070061084A - Sca based application system and the method of exchanging component in operation thereof - Google Patents

Abstract

An SCA-based application system and a method for exchanging a component in operation of the same are provided to prevent data from being transmitted to wrong object reference by component replacement owing to abnormal stop of the component or a request of a system manager, and prevent system down caused by wrong data transmission. An XML(eXtensible Markup Language) file storing part(130) stores an XML file for selectively operating the components(140,150) required for operating an application An assembly controller(120) cancels a name of the replaced component and the name of a data input port of the replaced component when the component is replaced, and registers the name of the new component and the name of the data input port of the new component. The component transfers output data based on data input port information, which is received from a naming server(110), of other components by responding to object reference query information transferred to the name server.

Description

SCA-based application system and the method of exchanging component in operation

1 is a block diagram illustrating an SCA-based application system according to an embodiment of the present invention.

2 is a block diagram illustrating a naming tree registered in a naming server for a naming service according to an embodiment of the present invention.

3 is a block diagram illustrating components in accordance with an embodiment of the present invention.

4 illustrates a data type according to an embodiment of the present invention.

5 is a flowchart illustrating a process of starting an application service according to an embodiment of the present invention.

6 is a flowchart illustrating a service stopping process associated with a component to be replaced according to an embodiment of the present invention.

7 is a flowchart illustrating a process of restarting an application service after component replacement according to an embodiment of the present invention.

The present invention relates to a software communication architecture (hereinafter referred to as SCA) based application system and a method of replacing components during its operation.

SCA is a standardized communication software architecture proposed by the Joint Tactical Radio System (JTRS) Joint Program Office (JPO) to significantly improve interoperability between communication systems and reduce development and deployment costs.

SCA is composed of hierarchical structure of application and operating environment, and dual operating environment consists of Real-Time Operating System (RTOS), Core Framework (CF) and COVA ( It consists of the Common Object Request Broker Architecture (CORBA) interface. SCA adopts CORBA (Common Object Request Broker Architecture), an industry standard for distributed object models, as a middleware to provide an integrated environment of heterogeneous hardware and software. System design framework.

An SCA based application system refers to a communication system based on an SCA structure, and a software defined radio (SDR) system is a representative example of an SCA based application system. Software-based wireless communication systems can accommodate multiple wireless communication standards by converting modular software without modification of hardware and adopt SCA as a standard of software framework.

An application that performs a waveform function in an SCA-based application system executes a bundle of components in a single package. As a result, if one or multiple components of an application operation fail or require replacement, the entire application package can be removed from the system and the application package with the new components rebuilt to load and run the entire package back into the system. It was not possible to replace components during operation.

If the redeployment of the application is omitted, when a failure or replacement of one or more components occurs, the destination information (Port Object Reference) of each input / output port, which is the runtime information of the corresponding component, is changed and connected with the corresponding component. All connection information that is present will be lost. As a result, if another component attempts to send data to the I / O port associated with the component that is failing or replaced, it can cause an error in writing the data to the wrong memory address, causing the entire application to be affected and the system to crash. have.

Because of this, it is difficult to apply the SCA-based application system that must terminate the entire application in order to replace the application package in the device that operates without interruption for the mobile communication service, such as the base station.

In order to solve such a problem, the present invention proposes an SCA-based application system and a method for replacing a component during its operation, even if any component is replaced during operation, thereby preventing the occurrence of an error or a system down.

According to an aspect of the present invention, an SCS-based application system includes an XML file storage unit and an XML file storing an XML file representing driving information for selectively driving a component required for operating a specific application. An assembly controller for analyzing and driving the component and the name of the component to be replaced and the data input port of the component to be replaced when the component is replaced, and the name of the newly arranged and driven component and the data of the newly placed and driven component Contains a naming server that registers the name of the input port.

On the other hand, the component replacement method during the operation of the SSIS-based application system having two or more components driven by the assembly controller according to an aspect of the present invention, (a) generating a deregistration request signal of the component to be replaced, ( b) unregister the name of the component to be replaced and the name of the data input port of the component to be replaced, delete it from the system, (c) deploy and run the new component, and (d) name and new component of the new component. Registering the name of the data input port of the, and resuming the application service.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings so that those skilled in the art may easily implement the present invention. As those skilled in the art would realize, the described embodiments may be modified in various different ways, all without departing from the spirit or scope of the present invention. In the drawings, parts irrelevant to the description are omitted in order to clearly describe the present invention, and like reference numerals designate like parts throughout the specification.

In addition, when a part is said to "include" a certain component, it means that it may further include other components, without excluding other components unless otherwise stated.

In addition, the term module described herein refers to a unit for processing a specific function or operation, which may be implemented in hardware, software, or a combination of hardware and software.

1 is a block diagram illustrating an SCA-based application system according to an embodiment of the present invention.

As shown in FIG. 1, the SCA-based application system 100 includes a naming server 110, an assembly controller 120, an XML file storage 130, a component A 140, and a component B. It consists of 150.

For reference, the SCA-based application system 100 shown in FIG. 1 includes only two components, Component A 140 and Component B 150, but for convenience of description, a typical SCA-based application system is It includes at least three components. A component deployed in an SCA-based application system is defined as a software module or element that implements a complete set of functions. It is usually in the form of a shared library, but depending on the deployment environment, binary code, byte code, etc. , Or one of the source files written in the Script Language.

All components in component A 140 and component B 150, that is, the SCA-based application system 100, are driven by the assembly controller 120, naming their names and the names of their data input ports. Register). When one component included in the SCA-based application system 100 transmits data to another component, for example, when component A 140 transmits data to component B 150, component A 140 is naming server 110. The output data destination query information is transmitted to the controller, and the data input port information of the component B 150 received accordingly is recognized as its output data destination information (Object Reference), and the data is transmitted. Every component in the SCA-based application system 100 has data input ports 141 and 151 and data output ports 142 and 152, respectively, and monitors data received at its data input port and can receive it. If data other than data is input, it is not received to prevent the occurrence of an error. On the other hand, a component that detects its own abnormal operation or receives a component replacement request from the assembly controller 120 cancels the registration of its name registered in the naming server 110 and the name of its data input port.

The XML file storage unit 130 stores an XML file defining driving information of all components in the SCA-based application system 100. Here, the driving information is information for selectively driving only components necessary for the execution of the application as an arbitrary application is disposed and executed in the assembly controller 120. XML files provide mechanisms that place constraints on storage, placement, and logical structure. Extensible Markup (XML) describes the classification of data objects and the activities of computer programs that process them. Language), which is stored in units called entities. An entity consists of parsed or uninterpreted data. Double parsed data consists of letters, some of which form letter data, and some of which form markup. do.

The assembly controller 120 controls the driving of all components in the SCA-based application system 100, that is, component A 140 and component B 150. The assembly controller 120 controls to start or stop the driving of each component, and registers its name and the name of the application with the naming server 110 when any application is placed and driven in the SCA-based application system 100. do. The assembly controller 120 parses an XML file stored in the XML file storage 130 to selectively drive components required for execution of the corresponding application among all components in the SCA-based application system 100. When the assembly controller 120 receives a component replacement request from the SCA-based application system 100 manager, the assembly controller 120 transmits a component replacement request signal to the component to be replaced and deletes the corresponding component. In addition, the assembly controller 120 that is notified of the occurrence of abnormal shutdown from any component deletes the component.

The naming server 110 receives a registration request signal from the assembly controller and the component as any application is deployed and driven, and thus naming tree names of the assembly controller 120, the application, the component, and the data input port of each component. Register). When the naming server 110 receives the output data destination query information including the name of another component to transmit data from any component in the SCA-based application system 100, the naming server 110 receives the data input port information of the corresponding component registered in the naming tree. To pass. On the other hand, the naming server 110 cancels the registration of the name of the component and the name of the data input port when abnormal operation stops or receives a cancellation request signal from the component that receives the component replacement request.

2 is a block diagram illustrating a naming tree registered in a naming server for a naming service according to an embodiment of the present invention.

The naming server (110 in FIG. 1) is an assembly controller (120 in FIG. 1) and component A (140 in FIG. 1) and component B as any application X is deployed and driven in an SCA-based application system (100 in FIG. 1). Upon receiving the registration request signal from 150 in FIG. 1, a naming tree as shown in FIG. 2 is constructed. In this case, the illustrated component A_DataPort and component B_DataPort mean data input ports of component A (140 of FIG. 1) and component B 150, respectively.

The naming server (110 in FIG. 1) registers the names of the assembly controller (120 in FIG. 1) and component A (140 in FIG. 1) and component B (150 in FIG. 1) at the bottom of application X, and component A (FIG. 1). Enter the name of the data input port 141 of component A (140 of FIG. 1) at the bottom of the name of 140 of 1, and enter the data of component B (150 of FIG. 1) at the bottom of the name of component B (150 of FIG. 1). The name of the port 151 is registered.

Here, the names of the assembly controller (120 in FIG. 1) and component A (140 in FIG. 1), component B (150 in FIG. 1), data input port 141 and data input port 151 are SCA based applications. Since it must be unique within the system (100 in FIG. 1), it is created based on the Universally Unique Identifier (UUID) worldwide.

3 is a block diagram illustrating components in accordance with an embodiment of the present invention.

As shown in FIG. 3, the component A 140 includes a data input port 141, a data output port 142, an operation information input / output port 143, a control unit 144, and an output data destination information storage unit 145. , Operation state management unit 146, a data storage unit 147, and a received data monitoring unit 148.

The data input port 141 and the data output port 142 are for mutual communication with other components, and the operation information input / output port 143 is for transmitting and receiving operation information of the component A 140. The operation information input / output port 143 receives a driving command from the assembly controller 120 (120 of FIG. 1) when the application is driven, and registers a registration request signal including a name of the component A 140 and a name of the data input port 141. (110 in FIG. 1). In addition, the operation information input and output port 143 receives the replacement request of the component A 140 from the assembly controller (120 of FIG. 1), or when an abnormal operation interruption occurs in the running component A 140, the operation state management unit The registration cancellation request signal generated at 146 is transmitted to the naming server 110 of FIG. 1.

The output data destination information storage unit 145 stores data input port 141 and data output port 142 information defined by the control unit 144, and output data destinations received from the naming server (110 in FIG. 1). Save the information.

The operation state management unit 146 generates a registration request signal or a registration cancellation request signal to be transmitted to the naming server (110 of FIG. 1) according to the operation state of the component. The operation state manager 156 generates a registration request signal when the component A 140 starts to be driven by the controller 144 that receives the driving information from the assembly controller 120 (120 of FIG. 1) when the application is driven. The operation state management unit 156 receives a replacement request of the component A 140 from the assembly controller 120 (or FIG. 1) or generates a registration cancellation request signal when it detects an abnormal operation interruption of the component A 140 being driven. . The data storage unit 147 stores data input / output with other components.

The controller 144 controls the driving of the component A 140. When the controller 144 receives the driving information from the assembly controller 120 (see FIG. 1), the controller 144 drives the component A 140 and uses the runtime information of the component A 140 sensed at this time to use the data input port 141. And a data output port 142. When the controller 144 detects that the registration request signal is generated by the operation state manager 146, the controller 144 receives a registration request signal including a name of the component A 140 and a name of the data input port 141. 110, and when the deregistration request signal is generated by the operation state manager 146, the deregistration request signal is transmitted to the naming server 110 (FIG.

When data transmission to another component is required, the controller 144 transmits output data destination query information including the name of another component to be transmitted or the name of the data input port of the other component to the naming server (110 of FIG. 1). Accordingly, output data destination information received from the naming server 110 (in FIG. 1) is stored in the output data destination information storage unit 145.

The control unit 144 transfers the data stored in the data storage unit 147 to the output data destination information determined through the data output port 142 according to the information stored in the output data destination information storage unit 145, and receives the data monitoring unit. According to the monitoring result of 148, it is determined whether to store the data input to the data input port 141 and selectively stores the data in the data storage unit 147.

The reception data monitoring unit 148 monitors the data received through the data input port 141 and transfers or deletes the data to the data storage unit 147 under the control of the control unit according to the result. In this case, the data monitoring by the reception data monitoring unit 148 is to determine whether the component A 140 has received data to be delivered to a destination address other than the data to be received. A data type according to an example is shown in FIG. 4.

4 illustrates a data type according to an embodiment of the present invention.

The data type shown in FIG. 4 is for error-free and accurate data transmission and reception between components in an SCA-based application system (100 in FIG. 1), and includes an Src component identifier of a string type and a string type. It includes a Dst component identifier, an ID (Id) of a string type, and a Value variable of an Any type. Here, the Src component identifier and the string type DST component identifier indicate a component for transmitting data and a component for receiving data, respectively. In addition, ID (Id) is a delimiter for identifying what kind of value the value (Value) information, the value (Value) is the data actually transmitted between the components.

Using this data type, the reception data monitoring unit 148 of FIG. 3 monitors the DST of data input to the component A (140 of FIG. 3) through the data input port 141 of FIG. 3. Component A (140 in FIG. 3) may determine whether data to be received has been received.

5 is a flowchart illustrating a process of starting an application service according to an embodiment of the present invention.

When an arbitrary application X is placed and driven in the SCA-based application system (100 in FIG. 1), the assembly controller (120 in FIG. 1) parses the XML file stored in the XML file storage unit (130 in FIG. 1). In operation S301, component A (140 in FIG. 1) and component B (150 in FIG. 1) required for the execution of the application X are driven (S302). Component A (140 of FIG. 1) and Component B (150 of FIG. 1), which have received the driving information from the assembly controller (120 of FIG. 1), have their own name and the name of their data input port, respectively. In order to register at 110 of 1, a registration request signal is generated and transmitted to the naming server (110 of FIG. 1). The naming server 110 (110 of FIG. 1) receives this and registers a name of each of component A (140 of FIG. 1) and component B (150 of FIG. 1) and a name of a data input port (S303). Each of component A (140 in FIG. 1) and component B (150 in FIG. 1) outputs output data destination query information including the name of another component or the name of a data input port of another component to transmit data to and from each other. It forwards to the naming server (110 in FIG. 1) and receives output data destination information from the naming server (110 in FIG. 1) accordingly. The component X (140 of FIG. 1) and the component B (150 of FIG. 1) start the application X service by delivering data according to the received output data destination information, respectively (S304).

6 is a flowchart illustrating a service stopping process associated with a component to be replaced according to an embodiment of the present invention.

The case where component A (140 in FIG. 1) is replaced will be described as an example.

When abnormal operation interruption of the component A (140 of FIG. 1) occurs or a replacement request by the SCA-based application system (100 of FIG. 1) administrator is received from the assembly controller (120 of FIG. 1) (S401), the operation state detection unit 3, 146 of FIG. 3 generates a deregistration request signal, and the controller 144 of FIG. 3 transmits a deregistration request signal to the naming server 110 of FIG. 1. The naming server 110 (in FIG. 1) receives a deregistration request signal from component A (140 in FIG. 1) and the data input port (140 in FIG. 1) of component A (140 in FIG. 1). The name of 141 of FIG. 3 is unregistered (S402). The component A (140 of FIG. 1) deregistered from the naming server 110 of FIG. 1 is deleted from the memory of the SCA based application system 100 of FIG. 1 (S403).

7 is a flowchart illustrating a process of restarting an application service after component replacement according to an embodiment of the present invention.

When component A (140 in FIG. 1) is replaced and disposed, the assembly controller (120 in FIG. 1) parses an XML file of component A (140 in FIG. 1) stored in an XML file storage unit (130 in FIG. 1). In step S501, the component A (140 in FIG. 1) is driven (S502). Component A (140 in FIG. 1) transmits a registration request signal to the naming server (110 in FIG. 1), and the naming server (110 in FIG. 1) that receives it receives the name of component A (140 in FIG. 1) and component A. The name of the data input port (141 in FIG. 1) in (140 in FIG. 1) is registered (S503).

 Each of component A (140 in FIG. 1) and component B (150 in FIG. 1) outputs output data destination query information including the name of another component or the name of a data input port of another component to transmit data to and from each other. It forwards to the naming server (110 in FIG. 1) and receives output data destination information from the naming server (110 in FIG. 1) accordingly. The component X (140 of FIG. 1) and the component B (150 of FIG. 1) respectively resume application X services by delivering data according to the received output data destination information (S504).

As described above, the present invention provides a component according to a request of an administrator of an SCA-based application system (100 of FIG. 1) or occurrence of abnormal downtime of a component through the use of a naming service and a new data type of a naming server (110 of FIG. 1). It is possible to provide an SCA-based application system in which components can be replaced during operation, which prevents data from being transferred to wrong destination information during replacement.

The embodiments of the present invention described above are not implemented only through the apparatus and the method, but may be implemented through a program for realizing a function corresponding to the configuration of the embodiment of the present invention or a recording medium on which the program is recorded. Implementation may be easily implemented by those skilled in the art from the description of the above-described embodiments.

Although the embodiments of the present invention have been described in detail above, the scope of the present invention is not limited thereto, and various modifications and improvements of those skilled in the art using the basic concepts of the present invention defined in the following claims are also provided. It belongs to the scope of rights.

By the above-described configuration, it is possible to prevent data from being delivered to wrong destination information due to abnormal operation interruption of a component or replacement of a component according to a request of an SCA-based application system administrator, and downtime of the entire application system.

As a result, the SCA-based application system can be applied to devices that operate uninterruptedly for mobile communication services such as base stations, and the free replacement of application components during operation.

Claims (15)

An XML file storage unit for storing an XML file representing driving information for selectively driving a component required for operating a specific application; An assembly controller for interpreting the XML file to drive the component; And Naming that registers the name of the component to be replaced and the data input port of the replaced component when the component is replaced, and registers the name of the newly arranged and driven component and the name of the data input port of the newly deployed and driven component. server Software communication architecture (SCA) based application system comprising a. The method of claim 1, The component is an SSC-based application that delivers output data based on data input port information of another component received from the naming server in response to the output data destination query information transmitted to the naming server for data transmission and reception between the components. system. The method of claim 2, The output data destination query information includes a name of a data transfer destination component or a name of a data input port of the data transfer destination component. The method of claim 2, The data transmitted / received between the components is a string type Src component identifier, a string type Dst component identifier, a string type ID, and an Any value. SSIS-based application system containing variables. The method of claim 4, wherein And the component accepts or deletes the received data according to a result of monitoring the DS component identifier of the received data. The method of claim 1, The replacement of the component is carried out in accordance with the abnormal operation of the component or a system administrator based on the replacement request for the component of the system-based system. The method of claim 1, And the assembly controller and the component generate a registration request signal for registering a name of the assembly controller, a name of the component, and a name of a data input port of the component as the specific application is driven. The method of claim 7, wherein The S-based application system which detects the occurrence of abnormal operation stop or receives a component replacement request from the system manager generates a registration cancellation request signal and transmits it to the naming server. A method of replacing a component during operation of an SCA based application system having two or more components driven by an assembly controller, (a) generating a deregistration request signal for the component to be replaced; (b) deregistering the name of the component to be replaced and the name of the data input port of the component to be replaced and deleting from the system; (c) deploying and driving new components; And (d) registering the name of the new component and the name of the data input port of the new component and restarting an application service; How to replace components during the operation of the ES-based application system comprising a. The method of claim 9, In the step (a), The deregistration request signal is generated when the occurrence of abnormal shutdown of the component to be replaced is detected or a system administrator receives a replacement request for the component to be replaced. The method of claim 9, Deregistration of step (b) above, The naming server that registers and stores names of two or more components and names of data input ports of the two or more components driven by the assembly controller receives the deregistration request signal of the component to be replaced generated in step (a). How to replace components during the operation of the SSIS-based application system. The method of claim 9, In the step (c), The new component is a component replacement method during operation of the ES-based application system is driven in response to receiving the drive information from the assembly controller. The method of claim 11, In step (d), The component during operation of an essay-based application system in which the naming server receives and registers a registration request signal including a name of the new component and a name of a data input port of the new component from the new component driven in the step (c). How to replace. The method of claim 13, Resuming the application service of step (d), And at least two components driven by the assembly controller deliver output data based on data input port information of another component received from the naming server. The method of claim 14, And at least two components receive data input port information of the other component in response to output data destination query information transmitted to the naming server.

Images