KR20050066281A - Descriptor file architecture based on sca system and file parsing method thereof - Google Patents

Abstract

The present invention relates to a descriptor file structure of a SCA (Software Communicartion Architecture) based system and a file parsing method thereof.

The present invention is a software assembly included in a component assembly package, among descriptor files to which an XML (Extension Markup Language) document type definition (DTD) structure describing deployment information on a component file in an SCA-based system is applied. In the Software Assembly Descriptor (SAD) and Device Configuration Descriptor (DCD), delete the modules (component file group module, type attribute of component file module and component file reference module, etc.) that describe component placement information. Then, add the component file module including only the identifier attribute in the component placement module of the distribution module.

According to the present invention, the structure of the descriptor files included in the component assembly package can be simplified, and the file parsing time can be shortened.

Description

Descriptor file architecture based on SCA system and file parsing method

The present invention relates to a software communication architecture (SCA) based system, and more particularly, to a structure of a descriptor file included in a component assembly package in an SCA based system and a file parsing method thereof.

The SCA standard aims to significantly improve interoperability between communication systems and reduce development and deployment costs in the Joint Tactical Radio System (JTRS) Joint Program Office (JPO), which was established to develop future communication systems using technologies that have been developed until recently. The proposed communication software architecture is designed to ensure portability and configurability of software and hardware, and to ensure interoperability between products developed using SCA.

SCA adopts the common object request broker architecture (CORBA), the industry standard for distributed object models, 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 based on this SCA structure. For example, SDR (Software Defined Radio) systems adopt SCA as a standard for software frameworks.

Information about such hardware and software components is described as a domain profile by applying XML (Extended Markup Language) document type definition (DTD). Among these domain profiles, a software assembly descriptor and a software assembly descriptor are described. The device configuration descriptor file based on the DTD structure of the component is redundantly managed by the elements representing the component file layout-related information, that is, the storage module when the file is loaded in a lightweight system. In addition, when parsing such files, performance may be degraded depending on the process of accessing unnecessary modules.

Therefore, the technical problem to be achieved by the present invention is to solve a conventional problem, a configuration module for expressing the component file arrangement related information among the XML DTD structure of the software assembly descriptor and device configuration descriptor included in the component assembly package in the SCA-based system To simplify the file size.

In addition, the technical problem to be achieved by the present invention is to reduce the time to parse the configuration module representing the component file arrangement related information of the software assembly descriptor and the device configuration descriptor file.

Another object of the present invention is to provide a method of systematically assigning a file name that simultaneously supports a file name and a type in the software assembly descriptor and the device configuration descriptor file.

In order to achieve this technical problem, a descriptor file structure according to an aspect of the present invention is provided in a descriptor file structure for a software assembly descriptor included in a component assembly package in an SCA-based system. A distribution module for defining a relationship between a device and a component defining a layout pattern of components to be arranged together; A description module for defining descriptive information about the component assembly; An assembly control module displaying a component that performs a control role for the assembly; And a connection module for providing a communication path connection relationship between components in the assembly. In addition, it may further include an external port module for describing an interface utilized externally by the component.

The distribution module includes a component placement module defining a set arrangement of components; And a co-location module that performs a function of collecting component instances to be placed together on one device.

The colocation module includes a plurality of component placement modules for gathering component instances to be placed together on one device.

Such a component placement module includes a component file module that performs a function of referring to a local file corresponding to a software package descriptor including component information, including an identifier attribute identifying a component file; And a component instance module for describing instantiation of a component related to the component file module. Here, the component file module includes a file reference module that performs a function of referring to a local file corresponding to a software package descriptor including component information.

In addition, the descriptor file structure according to another aspect of the present invention is a descriptor file structure for a device configuration descriptor included in a component assembly package in an SCA-based system, the distribution module comprising a set of modules used to define a specific arrangement of components; Description module for providing information about the device configuration; A device manager package module for performing a function of referring to a software package descriptor for a device manager corresponding to the device configuration descriptor; And a connection module for displaying a service instance used by the device manager and device component in the device configuration descriptor. In addition, the domain manager module for displaying a method for the device manager to obtain a domain manager object reference; And a file system name module displaying a file system name of the device manager.

Herein, the distribution module is composed of a plurality of component arrangement modules, and each component arrangement module refers to a local file corresponding to a domain manager configuration descriptor or a software package descriptor including the component information. A component file module including an identifier attribute for identifying; A component instance module that performs a function of describing a special instantiation of a component associated with the component file module; A device arrangement module that performs a function of referring to another component instance module in which the component instance module in the component arrangement module is to be disposed; A device aggregation module used when there is an aggregation relationship in which the component instance module of the device in the component placement module refers to another component instance module; And a device package file module that performs a function of referring to a device package descriptor file including a hardware device definition.

On the other hand, in the descriptor file structure having such a feature, in the component file module, the identifier attribute is used to refer to the local file, and the component type and the component file uniquely indicate a component type in the component file name of the identifier attribute. It is assigned by identifying component identifier.

In addition, the file parsing method according to another aspect of the present invention is a method for parsing a software assembly descriptor or device configuration descriptor file included in a component assembly package in an SCA-based system, and a) whether a component placement module exists in the file. Determining whether or not; b) parsing a component file module if the component arrangement module exists and storing it in an internal variable; And c) parsing a file reference module based on the identifier attribute included in the component file module and storing the file name in an internal variable.

Here, after performing the step c), the process transitions to the step a) and repeats the steps a) to c), and the step a) ends the file parsing if the component arrangement module does not exist.

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.

1 shows the general structure of an SCA-based system.

As shown in FIG. 1A, an SCA-based system processes a single device manager 101 component that manages a device, a plurality of logical device 102 components that functionally abstract hardware devices, logs, and events. It may include a plurality of library 105 components configured in the form of a plurality of service 103 components, a plurality of XML data 104 components and a library describing hardware and software information, and supporting components.

In contrast, as shown in FIG. 1B, an SCA-based system includes one device manager 111 component managing a device, a plurality of logical device 112 components functionally abstracting a hardware device, logs, and events. A plurality of service 113 components for processing the information, a plurality of XML data 114 components describing hardware and software information, a plurality of library 115 components configured in a library form to support the components, for software control and configuration It may include a number of application 116 components, a domain manager 117 component that manages a domain, one file manager 118 component that manages a system, and a plurality of XML parser 119 components that parse XML data. .

As illustrated in FIG. 1, a domain profile describing configuration information of an SCA-based system that may be configured with respective hardware and software components has a structure as follows. 2 is a schematic structural diagram of a domain profile.

As shown in FIG. 2, the domain profile 20 includes a device configuration descriptor 21, a domain manager configuration descriptor 22, a software assembly descriptor 23, a software package descriptor 24, and a software component descriptor 25. It includes. In addition, a property descriptor including a property to be applied to a software / hardware component, a profile descriptor providing an absolute file path for the components 21 to 24, and a device package descriptor including hardware configuration related property information about the device are additionally added. It may also include.

Meanwhile, the device configuration descriptor 21 may describe a component to be initially driven on a node where the device manager is located, a method of obtaining a domain manager, a method of connecting a service to the component, and features for the device manager (such as a file system name). A file that provides a means of describing). This file may not exist in the domain profile or may exist in multiple instances.

The domain manager configuration descriptor 22 is a file that provides configuration information for the domain manager and a means for describing a service to be used, and there may be only one in the domain profile.

The software assembly descriptor 23 is a file that provides a means of describing the aggregated functional applications and the interconnect characteristics of the components within those applications and may or may not exist in the domain profile.

A software component descriptor 25 is a file that provides a means of describing information about an interface provided and / or used by a particular software component. There is only one for each software package descriptor 24 in a domain profile. It may not.

Software package descriptor 24 is a file that provides a means of describing information such as software package related name, author, properties file, implementation code information, hardware / software dependencies, etc. to identify a software component implementation. May exist.

In an SCA-based system as described above, a software assembly descriptor 23 file describing the aggregated functional application and the interconnection characteristics of the components within such an application generally consists of the following structure.

3 is a block diagram illustrating an XML DTD structure of a general software assembly descriptor.

As shown in FIG. 3, the software assembly descriptor 30 is largely composed of a component file group module 31, a distribution module 32, an explanation module 33, an assembly control module 34, a connection module 35, and An external port module 36 is included.

The component file group module 31 is a module used to display an assembly constituting one or more component files, and there may be one. The component file group module 31 is composed of a plurality of component file modules 311 to perform operations. The component file module 311 refers to a local file corresponding to the software package descriptor 24 including component information. The module includes an identifier attribute 3111 uniquely identifying a component file and a type attribute 3112 indicating a type of a component. Here, the type attribute 3112 uses a name (eg, SPD) that points to the software package descriptor 24 of FIG. 2. Meanwhile, the component file module 311 includes one file reference module 312 therein, and the file reference module 312 substantially stores a local file corresponding to the software package descriptor 24 including component information. See.

The distribution module 32 is a module used to define a relationship between a device and a component that defines a layout pattern of components and a layout pattern of components to be arranged together on one device. If a component file is defined in the component file group module 31, a distribution pattern of the corresponding component file is defined in the distribution module 32.

The distribution module 32 is largely composed of the component placement module 321 and the same position placement module 322 to perform the operation. In this case, the component arrangement module 321 may be a module used to define a particular arrangement of components. The colocation module 322 is a module used to collect component instances to be co-located on one device.

The component arrangement module 321 is largely composed of a component file reference module 3211 and a component instance module 3212 to define a special arrangement of components to perform an operation. Here, the component file reference module 3211 is a module used to refer to a specific software package descriptor file and is necessarily present to include an attribute corresponding to the identifier attribute 3111 of the component file module 311. In addition, the component instance module 3212 may exist as a module describing a special instantiation of a component related to the component file reference module 3211. Here, the co-location module 322 may have a plurality of the same component placement module 3221 as the component placement module 321 to collect the component instances to be arranged together on one device. The component arrangement module 3221 is composed of a component file reference module 32211 and a component instance module 32212 which perform the same functions as the component file reference module 3211 and the component instance module 3212 to perform an operation. do.

In order to further simplify the general software assembly descriptor of an SCA-based system having a structure as described above, the software assembly descriptor according to an embodiment of the present invention simplifies the configuration module representing the component file placement-related information to store the file of the system. Ensure that places are managed efficiently

4 is a block diagram illustrating an XML DTD structure of a software assembly descriptor according to an embodiment of the present invention.

As shown in FIG. 4, the software assembly descriptor according to the embodiment of the present invention includes a distribution module 51, an explanation module 52, an assembly control module 53, a connection module 54, and an external port module ( 55).

Similar to the function defined in FIG. 3, the distribution module 51 is a module used to define a relationship between a device and a component that defines a layout pattern of components and a layout pattern of components to be arranged together on one device. May exist.

Specifically, the distribution module 51 is largely composed of the component placement module 511 and the same position placement module 512 to perform an operation. Like the function defined in FIG. 3, the component arrangement module 511 may exist as a module used to define a special arrangement of components, and if there are no components, a plurality of components may be present. Like the function defined in FIG. 3, the co-location module 512 may be present as a module used to group component instances to be co-located on a device, or may exist in plural.

The component arrangement module 511 is largely composed of a component file module 5111 and a component instance module 5112 to define a special arrangement of components. The component file module 5111 is a module that refers to a local file corresponding to a software package descriptor including component information, and includes an identifier attribute 51111 that uniquely identifies a component file therein. In addition, the component file module 5111 includes one file reference module 521 therein. The file reference module 521 refers to a local file corresponding to a software package descriptor including component information.

Like the function defined in FIG. 3, the component instance module 5112 may be provided as a module for describing a special instantiation of a component related to the component file module 5111. The colocation module 512 may include a plurality of the same component placement module 5121 as the component placement module 511 to collect component instances to be co-located on one device. The component arrangement module 5121 is composed of a component file module 5211 and a component instance module 5212 which perform the same functions as the component file module 5111 and the component instance module 5112 to perform an operation.

On the other hand, the description module 52 is a module that defines the descriptive information about the component assembly, may not exist, if there is only one may exist.

The assembly control module 53 is a module indicating a component that performs an important control role for the assembly, and there may be only one per assembly. The connection module 54 is a module that provides a communication path connection relationship between components in the assembly. The connection module 54 may not exist, and only one may exist if present.

The external port module 55 is a module for describing an interface utilized externally by a component. The external port module 55 may not exist, and if present, only one may exist.

As described above, the software assembly descriptor according to the embodiment of the present invention refers to the component file group module 31, the type attribute 3112 of the component file module 311, and the component file in the conventional software assembly descriptor illustrated in FIG. 3. By removing the modules 3211 and 32211 and adding the component file modules 5111 and 5211 including only the identifier attributes 51111 and 52111 into the component placement modules 511 and 5121 of the distribution module 51. You can simplify the configuration module, which represents the component file placement-related information in the XML DTD structure of the software assembly descriptor file.

In addition, in an SCA-based system as described above, a method for describing a component to be initially executed on a node where a device manager is located, a method for obtaining a domain manager, a method for connecting a service to a component, and a feature for a device manager ( Configuration of the device configuration descriptor 21 describing the file system name and the like) can be simplified.

First of all, for the understanding of the present invention, the structure of a general device configuration descriptor will be briefly described.

5 is a block diagram illustrating an XML DTD structure of a general device configuration descriptor.

The device configuration descriptor 40 is largely composed of a component file group module 41, a distribution module 42, a description module 43, a device manager package module 44, a connection module 45, a domain manager module 46, and a file. System Name Module 47 is included.

The component file group module 41 is a module used to refer to the layout information of the component driven on the device. The component file group module 41 may not exist or may exist only in one case.

The component file group module 41 is composed of a plurality of component file modules 411 to perform an operation. The component file module 411 refers to a local file corresponding to the domain manager configuration descriptor 22 and the software package descriptor 24 including component information. An identifier attribute 4111 uniquely identifies a component file therein. And a type attribute 4112 indicating the type of the component. The type attribute 4112 uses a name (eg, a DMD) pointing to the domain manager configuration descriptor 22 of FIG. 2 or a name (eg, an SPD) pointing to a software package descriptor 24.

The component file module 411 includes one file reference module 412 therein, wherein the file reference module 412 includes the domain manager configuration descriptor 22 or the software package descriptor 24 substantially including component information. Refers to the local file corresponding to.

In the embodiment of the present invention, in order to simplify the general device configuration descriptor of the SCA-based system having the structure described above, the configuration module representing the component file layout related information is simplified to efficiently manage the file storage location of the system. Be sure to

6 is an XML DTD structure diagram of a device configuration descriptor file according to an embodiment of the present invention.

The device configuration descriptor 60 according to an embodiment of the present invention is largely divided into a distribution module 61, an explanation module 62, a device manager package module 63, a connection module 64, a domain manager module 65, and a file system. It consists of a name module 66 to perform the operation,

The distribution module 61 may not exist as a module consisting of a set of modules used to define a specific arrangement of components, or only one may exist. The distribution module 61 is composed of a component arrangement module 611 to perform an operation. The component placement module 611 is a module used to define a particular arrangement of components. The component arrangement module 611 is largely divided into component file module 6111, component instance module 6112, device arrangement module 6113, device assembly module 6114, and device package file module 6115 to define a special arrangement of components. ) To perform the operation.

The component file module 6111 refers to a local file corresponding to the domain manager configuration descriptor or software package descriptor including the component information, and includes an identifier attribute 61111 that uniquely identifies the component file therein.

The component file module 6111 includes a file reference module 621 therein, which refers to a local file corresponding to a domain manager configuration descriptor or a software package descriptor including component information. do.

There are a plurality of component instance modules 6112 as modules describing special instantiation of components related to the component file module 6111, and the device arrangement module 6113 is the component instance module 6112 in the component placement module 611. ) Is a module used to refer to another component instance module 6112 to be placed, and may exist or may exist if one exists.

The device aggregation module 6114 is a module that is used when there is an aggregation relationship that refers to the component instance module 6112 and another component instance module 6112 of a device in the component arrangement module 611. There may be one. The device package file module 6115 may be a module used to refer to a device package descriptor file defined in FIG. 2 including a hardware device definition.

On the other hand, the description module 62 is a module that provides information on the device configuration, if not present or only one exists, the device manager package module 63 is a software package descriptor for the device manager corresponding to the device configuration descriptor There can be only one as a reference module.

In addition, the connection module 64 may be present as a module used to indicate a service instance used by the device manager and the device component in the device configuration descriptor.

The domain manager module 65 may exist as a module indicating how the device manager obtains a domain manager object reference. There may be one. The file system name module 66 does not exist as a module that displays the file manager name of the device manager. Or if present, one may be present.

As described above, in the device configuration descriptor according to the embodiment of the present invention, the component file group module 41, the type attribute 4112 of the component file module 411, and the component file reference module 4211 of FIG. 5 are removed. By adding the component file module 6111 including only the identifier attribute 61111 in the component arrangement module 611 of the distribution module 61, the component file arrangement related information in the XML DTD structure of the device configuration descriptor file is added. Simplify the configuration module to represent.

In particular, in the software assembly descriptor and device configuration descriptor described above, an embodiment of the present invention provides a component type through an identifier attribute included in the component file modules 5111 and 5211 of FIG. 4 and the component file module 6111 of FIG. 6. Give the component file name so that it can be displayed together.

7 is a structural diagram illustrating a component file name assignment through an identifier attribute of such a component file module.

The component file module 70 includes an identifier attribute 701 that uniquely identifies a component file therein for referencing a local file corresponding to a descriptor including component information, wherein the component file name of the identifier attribute 701 ( 71 assigns a file name by dividing the component type 711 indicating the component type and the component identifier 712 uniquely identifying the component file.

Accordingly, the component file module 70 may be systematically given a file name that supports the file name and the type simultaneously without separately managing the type attribute indicating the component type.

Next, a method of parsing a component file module of a software assembly descriptor / device configuration descriptor file having such a structure will be described.

8 illustrates a process of parsing a component file module of a software assembly descriptor / device configuration descriptor file according to an embodiment of the present invention.

In an embodiment of the present invention, first, by analyzing whether the component placement module exists (100 ~ S110), if the component placement module exists, the step of parsing and storing the component file module in the internal variable (S120).

Next, after parsing the file reference module based on the identifier attribute included in the component file module and storing the corresponding file name in an internal variable (S130), the process proceeds to step S110 and the component arrangement module Repeat the step of analyzing whether it exists. If the component placement module does not exist according to this iteration, the parsing process ends (S140).

As described above, compared with conventionally analyzing the existence of the component placement module at the time of file parsing, and sequentially parsing the component file reference module and the component file module file reference module, the component placement module according to an embodiment of the present invention. By analyzing the existence of and parsing only the component file module and the file reference module, it is possible to minimize the time for parsing the component file module representing the component file arrangement related information.

Although the preferred 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.

According to such an embodiment of the present invention, the file size is minimized by simplifying a configuration module that expresses component file placement related information among XML DTD structures of a software assembly descriptor and a device configuration descriptor included in a component assembly package in an SCA-based system. can do. Accordingly, when loading such a file in a system that seeks to be lightweight, the storage location can be efficiently used.

In addition, when parsing a file, it is possible to shorten the time for parsing a configuration module that expresses information related to component file placement of the software assembly descriptor and the device configuration descriptor file.

In addition, by including the file type in the component file name, it is effective to systematically manage file names that simultaneously support the file name and type.

1 is a structural diagram of a general SCA-based system.

2 is a structural diagram of a general domain profile.

3 is an XML DTD structure diagram of a typical SCA software assembly descriptor file.

4 is an XML DTD structure diagram of a software assembly descriptor file according to an embodiment of the present invention.

5 is an XML DTD structure diagram of a general SCA device configuration descriptor file.

6 is an XML DTD structure diagram of a device configuration descriptor file according to an embodiment of the present invention.

FIG. 7 is a structural diagram illustrating a component file name assignment through an identifier attribute of the component file module illustrated in FIGS. 4 and 6.

8 is a flowchart illustrating a process of parsing a component file module of a software assembly descriptor / device configuration descriptor file according to an embodiment of the present invention.

Claims (13)

In the descriptor file structure for a software assembly descriptor that is included in a component assembly package on a Software Communication Architecture (SCA) -based system, A distribution module for defining a relationship between a device and a component that defines a layout pattern of components and a layout pattern of components to be arranged together on one device; A description module for defining descriptive information about the component assembly; An assembly control module displaying a component that performs a control role for the assembly; And Connection module providing communication path connection relationship between components in the assembly Descriptor file structure containing a. The method of claim 1 A descriptor file structure further comprising an external port module that describes an interface utilized externally by the component. The method of claim 1 The distribution module A component placement module for defining a set arrangement of components; And Co-location module that functions to group component instances to be placed together on one device Descriptor file structure containing a. The method of claim 3, The colocation module comprises a plurality of component placement modules for gathering component instances to be deployed together on one device. The method according to claim 3 or 4 The component placement module A component file module for performing a function of referring to a local file corresponding to a software package descriptor including component information, including an identifier attribute identifying a component file; A component instance module describing instantiation of a component associated with the component file module Descriptor file structure containing The method of claim 5 The component file module has a descriptor file structure including a file reference module that performs a function of referring to a local file corresponding to a software package descriptor including component information. In an SCA-based system, in the descriptor file structure for the device configuration descriptor that is included in the component assembly package: A distribution module consisting of a set of modules used to define a particular arrangement of components; Description module for providing information about the device configuration; A device manager package module for performing a function of referring to a software package descriptor for a device manager corresponding to the device configuration descriptor; And A connection module for displaying a service instance used by a device manager and a device component in the device configuration descriptor Descriptor file structure that includes. The method of claim 7, A domain manager module displaying a method of the device manager obtaining a domain manager object reference; And File system name module to display the file system name of the device manager Descriptor file structure that includes more. The method of claim 7, The distribution module is composed of a plurality of component arrangement module, each component arrangement module, A component file module including an identifier attribute identifying a component file therein as a module referencing a local file corresponding to a domain manager configuration descriptor or a software package descriptor including the component information; A component instance module that performs a function of describing a special instantiation of a component associated with the component file module; A device arrangement module that performs a function of referring to another component instance module in which the component instance module in the component arrangement module is to be disposed; A device aggregation module used when there is an aggregation relationship in which the component instance module of the device in the component placement module refers to another component instance module; And Device package file module that performs the function of referencing the device package descriptor file containing the hardware device definitions. Descriptor file structure containing a. The method of claim 9 The component file module A descriptor file structure containing a file reference module that performs the function of referencing a local file corresponding to a domain manager configuration descriptor or software package descriptor containing component information. The method according to claim 6 or 9 In the component file module, the identifier attribute is used to refer to the local file, and a descriptor file for dividing the component file name of the identifier attribute into a component type indicating a component type and a component identifier uniquely identifying the component file. rescue. In a method for parsing a software assembly descriptor or device configuration descriptor file included in a component assembly package on an SCA-based system, a) determining whether a component placement module exists in the file; b) parsing a component file module if the component arrangement module exists and storing it in an internal variable; And c) parsing a file reference module based on the identifier attribute included in the component file module and storing the file name in an internal variable File parsing method comprising a. The method of claim 12, After performing step c), the process is transferred to step a), and steps a) to c) are repeated. In the step a), the file parsing method ends the file parsing if the component arrangement module does not exist.