KR100599193B1 - The base station system, Recording medium for Device Configuration Descriptor having XML DTD and parsing method for Device Configuration Descriptor - Google Patents

Abstract

The present invention provides a base station system that efficiently manages a device when accommodating a node that does not support COVA in a COVA environment.

The base station system according to the present invention is a COBA based node capable of COBA-based communication, at least one non-Coba-based node that is not capable of COBA-based communication, and performs an internal communication path function between the COVA-based node and the non-Cova-based node. Including the bus. Each of the non-cobar based nodes includes a first non-cobar application module, which is a non-cobar based device related component. COVA-based nodes are COVA application modules that perform COVA communication functions as COVA-based device-related components, COVA bus modules that perform communication path functions that provide COVA communication, and COB-based device-related components through COVA bus modules. And a first COVA adapter module providing communication means between the non-coma application module and the COVA application module.

CORBA, Non-Cobar, Parsing, Base Station

Description

The base station system, recording medium for Device Configuration Descriptor having XML DTD and parsing method for Device Configuration Descriptor}

FIG. 1 is a diagram schematically illustrating a configuration of a base station system 100 supporting a cobar based node and a noncobar based node according to a first embodiment of the present invention.

FIG. 2 is a diagram illustrating in detail the configuration of the KOVA based node 110 and the non-Cova based nodes 130 _{1 to} 130 _N illustrated in FIG. 1.

3 is a diagram illustrating an XML DTD structure of the DCD 300 according to the first embodiment of the present invention.

4 is a diagram illustrating a detailed configuration of the component file group element 350 of FIG. 3.

5 shows a detailed configuration of the dispensing element 360 of FIG. 3.

6 is a diagram illustrating the structure of an XML DTD of the DCD 400 according to the second embodiment of the present invention.

FIG. 7 is a diagram illustrating in detail the configuration of the component file group element 450 of FIG. 6.

8 is a flowchart illustrating a process of parsing the component file group element 450 of the DCD 400 file according to the second embodiment of the present invention.

9 is a diagram illustrating an XML DTD structure of the DCD 500 according to the third embodiment of the present invention.

FIG. 10 is a diagram illustrating in detail the configuration of the component file group element 550 of FIG. 9.

11 is a flowchart illustrating a process of parsing the component file group element 550 of the DCD 500 file according to the third embodiment of the present invention.

The present invention relates to a base station system, and more particularly, to a base station system based on SCA (Software Communication Architecture).

In general, SDR (Software Defined Radio) technology is a wireless technology that reduces the processing of hardware with fixed functions by placing the digital signal processing unit as close to the antenna side as possible and expands the part of programmable hardware to increase the flexibility using software. Meaning, it is a collection of hardware and software technologies that enable a programmable system architecture of wireless communication.

The Software Communication Architecture (SCA) has been recognized by the SDR Forum as a standard for software architecture for such SDR embedded systems. SCA has proposed the Joint Tactical Radio System (JTRS) Joint Program Office (JPOS), which was established to develop the communication system of the future using advanced technology until recently, to greatly improve interoperability between communication systems and reduce development and deployment costs. Communication software architecture. In addition, SCA adopts the CORBA (Common Object Request Broker Architecture), an industry standard for distributed object models, as a middleware to provide a flexible integration environment of this type of hardware and software written in various languages. The information is described in a domain profile by applying an extensible markup language document type definition (hereinafter referred to as XML DTD). Among these domain profiles, the device configuration descriptor (DCD) file is a file that provides a means of describing components to be initially run on the device manager node. The device configuration descriptor file is driven in the form of a component to perform an operation. One node exists to manage the devices that exist in the node, and one DCD file exists per device manager component.

Saehwa Kim's paper "SCA-based Component Framework for Software Defined Radio", published in the Journal WSTFES'03 (2003.05), proposes a component framework for SDR based on SCA. It was. In particular, it includes a component model that defines components as CORBA objects that support object management functions, a package model that uses SCA's XML descriptors, an SCA-based deployment environment, a startup procedure to recover deployment state, and a deployment procedure that supports dynamic component replacement. A defined deployment model is presented. In particular, the domain profile part is briefly defined mainly on the description, association, and function of each descriptor proposed by SCA, and the package is divided into component packages and component assembly packages. In addition, the startup procedure for loading and executing Device Manager components using the Device Configuration Descriptor (DCD) has been described, and how to execute application-related components using the Software Assembly Descriptor (SAD) has been described. . As such, each node described the relationship between deploying and connecting software and hardware components using these descriptor-related domain profiles.

On the other hand, in order to perform COBA communication with a node that does not support COVA in a node that does not support COVA, adapters for communication with a node that does not support COVA are required in a node that supports COVA and such a proxy ( Adapter components in charge of logical devices serving as proxy) reside in the COVA-based node and communicate with components of the non-Coba-based node. For each node, a device manager component must manage an adapter component and a non-cobar component that communicate with the non-cobar component.

Therefore, a method for efficiently managing components and an optimal parsing method are required so that a device manager can manage non-cobar components and cobar components for each node. In particular, in a base station system operating in a single or multiple mode, when the real-time related traffic information transmission path accommodates non-cobar and the control-related information transmission path accommodates cobar in consideration of the overall performance, the non-cobar component and the cobar component are XML files. There is an urgent need for a method that can be properly managed for each node using.

SUMMARY OF THE INVENTION The present invention has been made in an effort to provide a base station system that efficiently manages a device when a node that does not support COVA in a COVA environment (Nonkova) and a method of parsing the same.

Another technical problem to be solved by the present invention is to manage non-cobar components and cobar components appropriately for each node using XML files when the real-time related traffic information transmission path accommodates non-cobars and the control-related information transmission paths accommodate cobars. By providing a DCD structure that manages components efficiently.

A base station system according to an aspect of the present invention includes a COVA-based node capable of COBA-based communication; At least one non-cobar based node that is not capable of cobar based communication; And an internal bus that performs a communication path function between the cobar based node and the non-cobar based node.

Each of the non-cobar based nodes includes a first non-cobar application module which is a non-cobar based device related component.

The COVA-based node may include: a COVA application module configured to perform a COBA communication function as a COVA-based device related component; A coba bus module performing a communication path function for providing coba communication; And a first COVA adapter module providing a communication means between the first non-coma application module and the COVA application module through the COVA bus module as a COVA-based device related component.

The COVA-based node may further include a core framework module that performs a framework of components of the COVA-based node by communicating via the COVA bus module.

The COVA-based node includes a second non-Cova application module that performs non-Cova communication as a non-Cova-based device-related component. And a second COVA adapter module configured to perform non-Cova communication with the second non-Cova application module and connected to the coba bus module.

A recording medium according to another aspect of the present invention is a recording medium that stores a device configuration descriptor file that manages a device of a base station system and includes an XML DTD structure. At least one non-cobar based node that is not capable of communication, wherein the coba-based node and device-related components disposed in the non-cobar-based node are managed by a device manager that is a component provided in the cobar-based node,

The device configuration descriptor file includes: a domain manager element indicating how the device manager obtains an entity reference value; A device manager package element which is an element representing a software package descriptor for managing implementation related information for the device manager; A component file group element which is an element defining at least one component file driven in the cobar based node and the non-cobar based node; And a distribution element that is an element that defines the placement of components of the cobar based node and the noncobar based node.

The component file group element may include a plurality of node classification elements capable of distinguishing the cobar based node and at least one non-cobar node.

At least one component file element including a local file element including a descriptor file including component information; And a name attribute defining a directory of the cobar based node and at least one non-cobar node.

A parsing method according to another aspect of the present invention is a method in which a device manager of a base station system parses a component file group element of a device configuration descriptor file including an XML DTD structure. A base node and at least one non-cobar based node which is not capable of coba based communication, wherein the component file group element includes a name attribute and at least one attribute defining a directory of the coba based node and at least one non-cobar node; It includes a plurality of node classification elements each having a component file element,

a) determining whether the node classification element exists; b) parsing the name attribute of the node distinguishing element and storing a node directory in an internal variable; And c) parsing a local file element of the component file element and storing it in an internal variable.

Before step c), the method may further include d) determining whether there is a component file element to be parsed in the node classification element. After step c) is completed, step d) may be performed again.

In step d), if there is no component file element to parse, step a) may be performed again.

DETAILED DESCRIPTION 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. Like parts are designated by like reference numerals throughout the specification.

First, a base station system according to a first embodiment of the present invention will be described in detail with reference to FIGS. 1 to 5.

FIG. 1 is a diagram schematically illustrating a configuration of a base station system 100 supporting a cobar based node and a noncobar based node according to a first embodiment of the present invention.

The base station system 100 is a base station system that operates in SCA-based single mode or multiple modes. The base station system 110, which is capable of cobar communication, and the N non-cobar base nodes 130 _{1 to} 130 _{N that} are not capable of cobar communication. And an internal bus 120 that performs the communication path function.

FIG. 2 is a diagram illustrating in detail the configuration of the KOVA based node 110 and the non-Cova based nodes 130 _{1 to} 130 _N illustrated in FIG. 1. In general, the base station system 100 may include N non-cobar based nodes 130 _{1 to} 130 _N , but in the present embodiment, two non-cobar based nodes 130 ₁ and 130 ₂ may be included in the present embodiment for simplicity of description. The case of inclusion will be described.

The non-cobar based nodes 130 ₁ and 130 ₂ include non-cobar application modules 131 and 132 which are non-cobar-based device related components operating in the corresponding non-cobar-based nodes, respectively.

COVA-based node 110 is the COVA adapter module (111, 112), non-Cova application module 113, COVA adapter module 114, COVA application module 115, COVA bus module 116 and core framework framework ( 150).

The COVA adapter modules 111 and 112 are COVA-based device-related components, and the non-Cova application modules 131 and 132 of the non-Cova-based nodes 130 ₁ and 130 ₂ and the other Cova components within the Cova-based node 110 are included. To provide a means of communication.

The non-cobar application module 113 is a non-coba-based device-related component, and performs a non-coba communication function at the coba-based node 110 and is used when real time is to be guaranteed.

The COVA adapter module 114 is a COVA-based device-related component. The COVA adapter module 114 performs a COVA communication function at the COVA-based node 110 and performs a non-Coba communication with the non-cobar application module 113.

COVA application module 115 is a COB-based device-related component is a component that performs the COVA communication function in the COB-based node 110.

COVA bus module 116 is an internal bus that performs a communication path function for providing COVA communication.

The core framework module 150 includes a file manager 151, an execution device 152, a device manager 153, a domain manager 154, an SMS parser 155, an SMS file 156, and an IDL 157. ), Service 158.

The file manager 151 is a component that manages a file system, the execution device 152 is a component that loads and executes a service component on the COB-based node 110, and the device manager 153 is a device related component disposed in the node. This component manages them.

The domain manager 154 is a component that manages all the components in the domain, the XMP parser 155 is a component that parses all component-related profiles, and the XML file 156 is a file managing all component information. A component of type. IDL 157 is a component in the form of an interface related library defined for COVA communication, and service 158 is a service related component such as a log service.

The non-cobar application module 113 considers the performance of the coba-based node 110 so that traffic is used for non-coba components and control is used for the coba component.

As described above, in the base station system operating in SCA-based single mode or multi-mode, the real-time related traffic information transmission path accepts non-cobar and the control-related information transmission path selects a structure that accommodates cobar. There is.

The following describes in detail the XML DTD in which the device manager 153 describes information about each component of the DCD file, which is a file providing a means for describing components to be initially driven on the COBA-based node 110.

3 is a diagram illustrating an XML Document Type Definition (DTD) structure of an SCA device configuration descriptor (DCD) file according to a first embodiment of the present invention. In this case, one DCD file exists in each device manager component in the SCA structure to manage a device existing on a COVA-based node. That is, the device manager component exists for each node, and the DCD file exists for each COVA-based node.

As shown in FIG. 3, the DCD 300 includes a description element 310, a domain manager element 320, a file system name element 330, a device manager package element 340, a component file group element 350, and a distribution element. 360, a connection element 370.

The description element 310 is an element for providing information on device configuration, and the file system name element 330 is an element for displaying a file system name managed by the device manager 153. The description element 310 and the file system name element 330 may not exist, and if present, one each is sufficient.

The domain manager element 320 is an element indicating how the device manager 153 obtains an object reference value of the domain manager 154.

There is only one device manager package element 340 as an element indicating a software package descriptor for managing implementation related information for the device manager 153.

The component file group element 350 is an element defining one or more component files that are run on the COVA-based node 110. The component file group element 350 may not exist or, if present, one is sufficient.

The distribution element 360 is disposed of the components of the COVA-based node 110, that is, the COVA adapter modules 111 and 112, the noncobar application module 113, the COVA adapter module 114, and the COVA application module 115. This element defines.

The connecting element 370 may include components of the COVA-based node 110, that is, the COVA adapter modules 111 and 112, the non-cobar application module 113, the COVA adapter module 114, and the COVA application module 115 and the device. An element providing a communication path connection relationship between the manager 153 and the service 158 does not exist or exists if one exists.

4 is a diagram illustrating a detailed configuration of the component file group element 350 of FIG. 3.

The component file group element 350 includes a plurality of component file elements 351. Each component file element 351 includes a local file element 352. The local file element 352 refers substantially to a local file corresponding to a descriptor file containing component information. That is, the component file element 351 includes an identifier attribute uniquely identifying the component file by referring to the local file of the local file element 352 and a type attribute indicating the type of the component.

5 shows a detailed configuration of the dispensing element 360 of FIG. 3.

The distribution element 360 may include a plurality of component placement elements 361. Component placement element 361 is an element used to define a particular arrangement of components. Specifically, the component placement element 361 is largely divided into component file reference elements 362, component instance elements 363, device placement elements 364, device aggregation elements 365, and device packages to define a particular arrangement of components. Element 366.

The component file reference element 362 is an element used to refer to the configuration descriptor of the domain manager 154 (FIG. 2) and the specific software package descriptor file, and is an identifier of the component file element 351 of the component file group element 350. Required to include an attribute corresponding to an attribute.

There are a plurality of component instance elements 353 as elements describing special instantiation of components associated with the component file reference element 362.

There is one device placement element 354 that is not present or is present as an element used to reference another component instance element 363 to which the component instance element 363 in the component placement element 361 is to be placed.

The device aggregation element 365 is an element that is used when there is an aggregation relationship in which the component instance element 363 in the component arrangement element 361 refers to another component instance element 363, and one exists. .

The device package element 366 is an element used to refer to a device package descriptor file containing a hardware device definition, and if present, there is one.

As such, in the SCA illustrated in FIG. 3, an XML DTD structure of the DCD file exists for each device manager 154 to manage device components existing on the COVA-based node 110. Therefore, there is a problem that it is difficult for one device manager 154 to efficiently manage non-Cova components and COVA components included in each of the COBY-based nodes and the non-Cova-based nodes, and also to parse them efficiently.

The second and third embodiments of the present invention for solving this problem will be described with reference to FIGS. 6 to 11.

First, a second embodiment of the present invention will be described with reference to FIGS. 6 to 8.

6 is a diagram illustrating the structure of an XML DTD of the DCD 400 according to the second embodiment of the present invention. The DCD 400 according to the second embodiment of the present invention differs from the DCD 300 according to the first embodiment in that the component file group element 450 includes a plurality of node classification elements.

Specifically, as shown in FIG. 6, the DCD 400 includes the description element 410, the domain manager element 420, the file system name element 430, the device manager package element 440, the component file group element 450, and the like. Distribution element 460 and connecting element 470.

The description element 410, the domain manager element 420, the file system name element 430, and the device manager package element 440 are the same as the DCD 300 of the first embodiment, and thus detailed description thereof will be omitted.

The distribution element 460 is a component of the COVA-based node 110, that is, the arrangement of the COVA adapter modules 111 and 112, the non-Cova application module 113, the COVA adapter module 114, and the COVA application module 115. Rather, it is an element defining the arrangement of each of the plurality of non-cobar based nodes 130, that is, the non-cobar application module 131. The detailed configuration of the distribution element 460 is the same as that of the first embodiment shown in FIG.

In addition, the connection element 470 may also include components of each of the plurality of non-cobar-based nodes 130, that is, the non-cobar application module 131 and the home framework module 150. A device for providing a communication path connection relationship between the device manager 153 and the service 158. If one does not exist or exists, one exists.

Next, the component file group element 450 will be described in detail.

FIG. 7 is a diagram illustrating in detail the configuration of the component file group element 450 of FIG. 6.

As shown in FIG. 7, the component file group element 450 includes a node distinguishing element 455 so as to distinguish between nodes of the COVA-based node 110 and the plurality of non-cobar-based nodes 130. Each node classification element 455 also includes a plurality of component file elements 451 including a local file element 452 and a name attribute 453 defining a node directory. The definition of the local file element 452 defined under the component file element 451 by the node delimiter element 455 including the name attribute 453 can be simplified, and the directory attribute in the name attribute of the local file element 452 can be simplified. There is no need to specify a specific configuration, node-level consistency is maintained, and the method of managing components of a specific node can be simplified.

8 is a flowchart illustrating a process of parsing the component file group element 450 of the DCD 400 file according to the second embodiment of the present invention.

When parsing of the component file group element 450 starts, it is first determined whether the node classification element 455 exists (S110).

If the node classification element 455 does not exist, parsing of the component file group element 450 is terminated because the managing node does not exist (S150).

If the node classification element 455 exists, since there is a node to manage, the node attribute defined by parsing the name attribute 453 of the node classification element is stored in an internal variable (S120). In operation S130, it is determined whether the component file element 451 exists.

If the component file element 451 exists, the local file element 452 in the component file element 451 is parsed and stored in an internal variable (S140).

If it is determined in step S130 that the component file element 451 does not exist, the process returns to step S110 to repeat steps S110 to S130. Therefore, if the component file element 451 does not exist, the process goes to check whether there is another node.

According to such a parsing method, a single device manager 154 can efficiently parse non-Cova components and COVA components of the COBY-based node and the non-Cova-based node.

Next, a third embodiment of the present invention will be described with reference to FIGS. 9 and 10.

9 is a diagram illustrating an XML DTD structure of the DCD 500 according to the third embodiment of the present invention. The DCD 500 according to the third embodiment of the present invention differs from the DCD 400 according to the second embodiment in that the component file group element 550 includes number attributes.

Specifically, as shown in FIG. 9, the DCD 500 includes a description element 510, a domain manager element 520, a file system name element 530, a device manager package element 540, a component file group element 550, Distribution element 560 and connecting element 570.

The description element 510, the domain manager element 520, the file system name element 530, the device manager package element 540, the distribution element 560, and the connection element 570 correspond to the DCD 400 of the second embodiment. Since the same, detailed description is omitted. The component file group element 550 will be described in detail.

FIG. 10 is a diagram illustrating in detail the configuration of the component file group element 550 of FIG. 9.

As illustrated in FIG. 10, the component file group element 550 includes a node distinguishing element 555 so as to distinguish between nodes of the COVA-based node 110 and the plurality of non-cobar-based nodes 130. Each node classification element 555 also includes a plurality of component file elements 551 including a local file element 552 and a name attribute 553 defining the same node directory. The definition of the local file element 552 defined under the component file element 551 by the node distinguishing element 555 including the name attribute 553 can be simplified, and the directory attribute in the name attribute of the local file element 552 can be simplified. There is no need to specify a specific configuration, node-level consistency is maintained, and the method of managing components of a specific node can be simplified.

In addition, the component file group element 550 includes a number attribute 544. The number attribute 544 is an attribute that defines the number of all Cobi-based nodes and non-cobar-based nodes that can be managed by the COBA-based node 110 in the base station system. The internal structure of the DCD file can be easily understood, and the parsing algorithm can be simplified by defining the current total number of nodes when parsing.

11 is a flowchart illustrating a process of parsing the component file group element 550 of the DCD 500 file according to the third embodiment of the present invention.

When parsing of the component file group element 550 starts, it is first determined whether the node classification element 555 exists or whether the number attribute 544 is not the end (S210).

If the node classification element 555 does not exist or the number attribute ends, parsing of the component file group element 550 is terminated because the managing node does not exist (S250).

If the node classification element 555 is present or the number attribute is not the end, since there is a node to manage, the node attribute defined by parsing the name attribute 553 of the node classification element is stored in an internal variable (S220). In operation S230, it is determined whether the component file element 551 exists.

If the component file element 551 exists, the local file element 552 in the component file element 551 is parsed and stored in an internal variable (S240).

If it is determined in step S130 that the component file element 551 does not exist, the process returns to step S210 to repeat steps S210 to S230. Therefore, if the component file element 551 does not exist, the process goes to check whether there is another node.

According to such a parsing method, one device manager 154 may efficiently parse the non-Cobar component and the COVA component for each COBIO-based node and non-Cobar-based node.

Although the preferred embodiment of the present invention has been described in detail above, the present invention is not limited thereto, and various other changes and modifications are possible.

The present invention relates to an efficient base station device management structure and a parsing method that can be accommodated by non-cobar in an SCA-based base station system operating in a single mode or multi-mode, and a real-time related traffic information transmission path accommodates non-cobar and a control-related information transmission path. The performance of the base station system can be improved by selecting a structure for accommodating COVA.

In addition, by reconfiguring the device configuration descriptor file, it is possible to efficiently manage components of Coby-based nodes and non-cobar-based nodes in one device manager component in managing components operating in Coby-based nodes and non-Coba-based nodes in the base station. In addition, a single device manager component can more efficiently parse non-Cobar components and COVA components of COBIO-based nodes and non-Cobar-based nodes.

Claims (22)

COVA based node capable of COBA based communication; At least one non-cobar based node that is not capable of cobar based communication; And And an internal bus that performs a communication path function between the KOVA-based node and the non-Cova-based node. Each of the non-cobar based nodes includes a first non-cobar application module which is a non-cobar based device related component. The COVA-based node may include: a COVA application module configured to perform a COBA communication function as a COVA-based device related component; A coba bus module performing a communication path function for providing coba communication; And a first COVA adapter module for providing a communication means between the first noncoma application module and the COVA application module through the COBA bus module as a COVA based device related component. The method of claim 1, The cobar based node, Core framework module for performing a framework of components of the COVA-based node by communication through the COVA bus module. Base station system further comprising. The method of claim 2, The cobar based node, A non-Coba-based device related component, comprising: a second non-cobar application module for performing non-coba communication; And A COVA-based device related component comprising: a second COVA adapter module configured to perform non-Cova communication with the second non-Cova application module and to be connected to the cova bus module; Base station system further comprising. The method of claim 3, The COBA-based node is a base station system for performing traffic communication through a non-Coba-based component, and control-related communication through a COVA-based component. The method of claim 2, The core framework module, A device manager which is a component that manages device-related components disposed in the cobar-based node and the non-cobar-based node; An XML file which is a component that manages information of components; And XML parser for parsing the profile of the XML file Base station system comprising a. The method of claim 5, The core framework module, A file manager which is a component for managing a file system; An execution device that is a component that loads and executes a service component; A domain manager that is a component that manages components in a domain; IDL, an interface-related library type component defined for COVA communication; And A base station system further comprising a service that is a service related component. The method of claim 5, The device manager is a base station system for managing device-related components using a device configuration descriptor (Device Configuration Descriptor) including an XML DTD (eXtensible Markup Language Document Type Definition) structure. The method of claim 7, wherein The device configuration descriptor is And a component file group element defining a component file of at least one component driven in the cobar based node and the noncobar based node. The method of claim 8, The component file group element includes a plurality of node classification elements capable of distinguishing the cobar based node and the at least one noncobar node. Each node classification element includes at least one component file element including a local file element including a descriptor file including component information. The method of claim 9, The component file group element is The base station system further comprises a number attribute that is an attribute defining the number of the Coba-based node and at least one non-cobar node that can be managed. The method of claim 9 or 10, Each of the node distinguishing elements further includes a name attribute defining a directory of the cobar based node and at least one noncobar node. A recording medium for managing a device of a base station system and storing a device configuration descriptor file including an XML DTD structure, The base station system includes a coba-based node capable of coba-based communication and at least one non-cobar-based node that is not capable of coba-based communication. The device-related components disposed in the cobar based node and the non-cobar based node are managed by a device manager, which is a component provided in the cobar based node, The device configuration descriptor file is A domain manager element indicating how the device manager obtains an entity reference value; A device manager package element which is an element representing a software package descriptor for managing implementation related information for the device manager; A component file group element which is an element defining at least one component file driven in the cobar based node and the non-cobar based node; And And a distribution element, the distribution element being an element defining the arrangement of components of the cobar based node and the noncobar based node.  The method of claim 12, The component file group element is And a plurality of node classification elements capable of distinguishing the cobar based node and the at least one noncobar node.  The method of claim 13, At least one component file element including a local file element including a descriptor file including component information; And And a name attribute defining a directory of the COVA-based node and at least one non-cobar node. The method of claim 13, The component file group element is And a number attribute, which is an attribute defining the number of the COVA-based nodes and at least one non-cobar node that can be managed. The method according to any one of claims 12 to 15, The device configuration descriptor file is And a connection element which is an element that provides a communication path connection relationship between components of the COVA-based node and the non-Cova-based node. A device manager of a base station system parses a component file group element of a device configuration descriptor file including an XML DTD structure. The base station system includes a coba-based node capable of coba-based communication and at least one non-cobar-based node that is not capable of coba-based communication. The component file group element includes a plurality of node distinguishing elements each having a name attribute defining at least one of the coba-based node and at least one non-cobar node, and at least one component file element. a) determining whether the node classification element exists; b) parsing the name attribute of the node distinguishing element and storing a node directory in an internal variable; And c) parsing the local file element of the component file element and storing it in an internal variable. The method of claim 17, Before step c) d) determining whether there is a component file element to parse in the node classification element. The method of claim 18, And parsing d) after step c) ends. The method of claim 18, In step d), Parsing if the component file element to be parsed does not exist again. The method of claim 17, In step a) Parsing method when the node separation element does not exist parsing. The method of claim 17, The component file group element is Further comprising a number attribute that is an attribute defining the number of the COVA-based node and the at least one non-cobar node that can be managed, In step a), it is determined whether the number attribute is the last, parsing is terminated when the number attribute is last, and b) if the number attribute is not last.

Images