KR101271213B1 - Apparatus for managing of new device component of mobile terminal and method of the same - Google Patents

Abstract

The present invention relates to a device management apparatus and method for a new device component of a mobile terminal. The present invention relates to a device related file defined in a domain profile, arranged in a file directory structure, and managed when a mode is changed to a new device while operating a corresponding domain system. The device component related file corresponding to the file is additionally placed in the file directory to reconfigure the component in the domain system. According to the present invention, when adding a device component managed by the domain system of the mobile terminal, there is an advantage that it is possible to add the corresponding device component in real time even during the operation of the domain system. In addition, it is possible to efficiently operate system resources by adding only the corresponding device component while maintaining an existing file without having to reconfigure all management components in the domain system.

Description

Apparatus for managing of new device component of mobile terminal and method of the same}

The present invention relates to an apparatus and method for managing a new device component of a portable terminal, and more particularly, to an apparatus and method for managing a new device component of a portable terminal for installing a new device component in real time during operation of a component in a domain system of the portable terminal. will be.

The present invention is derived from the research conducted as part of the IT growth engine technology development project of the Ministry of Knowledge Economy and the Ministry of Information and Communication Research and Development. [Task management number: 2006-S-012-03, Task name: Development of middleware platform for SDR terminals] .

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

SCA adopts the real-time operating system (OS) and 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. Here, SCA is not a standard that is limited to a specific system but an independent system design framework.

SCA allows an application that performs the function of one waveform to bundle several components into one package, install it on hardware, deploy it, and run it. A representative example of adopting the SCA is a software defined radio (SDR) terminal system. SDR terminal systems adopt SCA as a standard for the software framework.

When reconfiguring the system according to a mode change, the SDR terminal removes existing application components from the corresponding device and newly installs application components to operate in a new mode in the SDR terminal. Subsequently, the SDR terminal finds a device in which installed application components operate and arranges and drives the application component on the device, thereby reconfiguring the system.

In order to support this method, a naming server, which has information on all components (domain manager, device manager, device, service, and application component) in SDR terminal is basically operated, and the device manager component in the domain It drives a domain manager that manages information such as devices, services, and application components, and drives a device manager that manages logical devices and services.

In addition, the device manager manages a device component that manages a device managed by a device manager and a service management component that manages a service, and then drives an application component through a mode change to reconfigure the system.

As such, prior to driving the application components required to reconfigure the SCA-based system, the management components such as naming server, domain manager, device manager component, device component, and service management component must be driven in advance. There was a problem that took a long time.

In order to solve this problem, there is a demand for adding and installing new device components in real time during system operation, but the existing SCA-based SDR terminal system does not provide real-time during system operation.

In order to solve the above problems, the present invention manages a new device component of a mobile terminal for efficiently operating resources in the domain system by installing and installing device components in real time during component operation in the domain system of the mobile terminal. It is an object of the present invention to provide an apparatus and a method thereof.

The device management apparatus for a new device component of a mobile terminal according to the present invention for achieving the above object includes a domain profile in which a component related file operated in a domain system of the mobile terminal is defined, and a device component for managing a device in the domain system. And manages component related files defined in the domain profile in a file directory structure, and additionally arranges device component related files corresponding to the new device in the file directory when a mode is changed to a new device while the domain system is in operation. And a device manager component to reconfigure the components in the domain system.

The device manager component checks whether a directory for adding and placing a device component related file of a new device exists in the file directory when the new device is added, and stores the device component related file in the corresponding directory. .

The device manager component may further generate a file directory in which the device component related file is to be placed when a directory for additionally arranging the device component related file does not exist.

The device component related file may include at least one of a device configuration descriptor file, an XML file, and an executable file.

The device configuration descriptor file may include at least one of initial driving information of the device manager component and the new device information.

The XML file may include a software package descriptor file, a software component descriptor file, and an attribute descriptor file.

The device manager component may arrange the device component descriptor file, the XML file, and the executable file in parallel in a corresponding file directory.

On the other hand, the new device component management method of a portable terminal according to the present invention for achieving the above object, the step of arranging and managing the component-related files operating in the domain system of the portable terminal in a file directory structure, the domain When the mode is changed to a new device while the system is operating, additionally disposing a device component related file corresponding to the new device in the file directory, and executing the device component related file additionally arranged in the file directory to execute the device component. Driving a step.

Before the step of additionally placing in the file directory, characterized in that it comprises a step of checking whether there is a directory to additionally place the device component related files.

If there is a directory in which the device component related file is to be additionally placed, the method may further include copying the device component related file and storing the file in the corresponding directory.

If there is no directory in which the device component related file is additionally placed, the method may further include generating a file directory in which the device component related file is to be placed.

The device component related file may include at least one of a device configuration descriptor file, an XML file, and an executable file.

The device configuration descriptor file may include at least one of initial driving information of the device manager component and the new device information.

The XML file may include a software package descriptor file, a software component descriptor file, and an attribute descriptor file.

The additional disposing may include disposing the device configuration descriptor file, the XML file, and the executable file in a corresponding file directory.

According to the present invention, when adding a device component managed by the domain system of the mobile terminal, there is an advantage that it is possible to add the corresponding device component in real time even during the operation of the domain system.

In addition, it is possible to efficiently operate system resources by adding only the corresponding device component while maintaining an existing file without having to reconfigure all management components in the domain system. In addition, there is an advantage that can shorten the installation time of new components, and minimize power consumption in reconfiguring components.

In addition, by installing a device component using the SPD XMP parsing method during the domain system operation, the parsing method is simplified and the parsing time is minimized.

Hereinafter, embodiments of the present invention will be described with reference to the accompanying drawings.

The present invention relates to an apparatus and method for managing device components in a domain system of a mobile terminal. In the following embodiment, the portable terminal is described as an SCA-based SDR terminal as an example, but is not limited thereto.

1 is a block diagram showing the configuration of an SCA-based SDR terminal system according to an embodiment of the present invention.

In particular, the present invention is a change in the method of managing a device in a Software Defined Radio (SDR) terminal system based on SCA (SCA), when adding a device component for managing it, in real time during operation An apparatus and method for installing a new device component remotely or in a terminal.

Referring to FIG. 1, an SCA-based SDR terminal system according to the present invention includes a naming server 110, a domain manager component 120, a domain profile, a device manager component 140, and a device component 150. It is composed.

The naming server 110 registers each component when the domain manager component 120, the device manager component 140, and the device component 150 are driven. Therefore, by querying the information of the component registered in the naming server 110, it is possible to obtain the information of a specific component.

Meanwhile, when there is a request for deregistration of a specific component among registered components, the naming server 110 may deregister the corresponding component.

Domain manager component 120 manages domains in an SCA-based system. At this time, the domain manager component 120 manages information of the device manager component 140 and the device component 150 existing in the domain. The domain manager component 120 also manages information such as service components (not shown) and application components (not shown).

The domain profile describes the hardware devices and software components that make up the SCA-based system domain as files. The device configuration descriptor (DCD) file and software containing information about all the components in the SDR terminal. Package Descriptor (SPD) files, Software Component Descriptor (SCD) files, Properties Descriptor (PRF) files, etc. Include.

Here, the DCD file basically includes the device manager component 140 related information and defines device information and configuration information of the device. In addition, the SPD file defines information for identifying an implementation target in implementing a unit software component. In addition, the SCD file defines interface and port information provided or used by a component, and the PRF file defines detailed attribute information of a device.

In this case, the DCD file, the SPD file, the SCD file, the PRF file, and the like are described in the form of an XML (eXtensible Markup Language) file.

In addition, the domain profile defines a directory to which device component 150 related files belong in an SCA-based domain system.

The device manager component 140 defines a device installation method, a search method of the domain manager component 120, and the like. Accordingly, the domain manager component 120 manages the information of the device component 150 in accordance with the content defined by the device manager component 140.

In other words, domain manager and device manager component 140 manages the registration and release of device component 150.

The domain manager loads and executes the device manager component 140 by parsing a device manager component related file, that is, an SPD file, an SCD file, or a PRF file, from a DCD file included in an XML file when the system is running. To be driven. The device manager component 140 driven as described above loads and executes all components included in the DCD file, and drives the component. The driven component registers the corresponding component to the device manager component 140.

At this time, the device manager component 140 registers the device component 150 managed by itself and the corresponding device manager component 140 with the domain manager component 120.

On the other hand, the device manager component 140 places the device component 150-related files in the directory, and when adding a new device component 150, by adding the new device component 150-related files to the directory, Only files related to the new device component 150 may be changed and registered in the file.

2 and 3 illustrate a file directory structure in an SCA-based SDR terminal according to the present invention. In particular, when installing the device component 150 for the additional device during the operation of the SDR terminal, the file directory structure for copying and installing the relevant device component 150 related file is shown.

First, the domain profile describes the XML file of the device component 150 to add. Here, the XML file includes an SPD file, an SCD file, and a PRF file. Accordingly, the device component 150 related SPD file, SCD file, and PRF file are obtained from the XML file of the device component 150 to be added from the domain profile. In this case, the device manager component 140 copies the SPD file, the SCD file, and the PRF file obtained from the XML file to place in the file directory.

In addition, the device manager component 140 extracts and copies the executable file related to the device component 150 to be added and similarly arranges the file in the file directory.

The device manager component 140 finally copies the DCD file including the corresponding device component 150 to place in the file directory. At this time, the device manager component 140 checks the DCD file name to be added. The device manager component 140 compares the DCD file name to be added with an existing DCD file name for initial startup. If the DCD file name to be added is different from the existing DCD file name, the device manager component 140 causes the DCD file to be added to the directory to be added separately from the directory in which the existing DCD file is disposed as shown in FIG. 2.

That is, when the DCD file name to be added is different from the existing DCD file name, the file directory of the device component 150 to be added is the DCD file 201 for initial operation and the DCD file 203 including the device component 150 to be added. , SPD / SCD / PRF file 205 of device component 150 to be added, and executable file 207 of device component 150 to be added. The device manager component 140 then removes the DCD file 201 for initial startup.

Meanwhile, when the DCD file name to be added and the existing DCD file name are the same, the device manager component 140 replaces the existing DCD file with the DCD file to be added and arranges the same, as shown in FIG. 3.

That is, when the DCD file name to be added is identical to the existing DCD file name, the file directory of the device component 150 to be added is the DCD file 201 including the device component 150 to be added and the device component 150 to be added. It has a structure that includes an SPD / SCD / PRF file 205 and an executable 207 of the device component 150 to add.

Thus, when reconfiguring a component according to a mode change in an SCA-based system, it is possible to efficiently manage system resources by installing and operating only the corresponding device component 150 to be added without having to restart all components. have. In addition, there is an advantage that can reduce the component installation time according to the SCA-based system reconfiguration, and minimize the power consumption.

In addition, in addition to the device component 150 to be added, there is an effect that the state of the registration information of the continuously operated components is kept consistent.

Hereinafter, the operation of the present invention will be described.

4 and 5 are flowcharts illustrating an operation flow for a method for installing a new device component 150 in an SCA-based system according to the present invention.

First, referring to FIG. 4, when there is a mode switch request (S300), the device manager component 140 performs an installation operation of the device component 150 corresponding to the requested mode (S310). In this case, the device manager component 140 determines whether a directory to which the corresponding device component 150 is to be copied exists (S320).

If there is no directory to which the device component 150 related file is to be copied (S330), the device manager component 140 may stop the installation operation of the device component 150. Of course, after requesting to configure a directory to copy the device component 150 related files, it may be restarted from the 'S300' process.

On the other hand, if there is a directory to copy the file associated with the device component 150 (S330), the device manager component 140 copies the XML file of the device component 150 from the domain profile to be placed in the file directory (S340). In addition, the device manager component 140 copies the executable file of the corresponding device component 150 and places it in a file directory (S350). In addition, the device manager component 140 copies the DCD file including the corresponding device component 150 and arranges it in a file directory (S360).

At this time, the device manager component 140 checks the DCD file name including the corresponding device component 150. If the DCD file name including the device component 150 is the same as the DCD file name including the existing device component 150 (S370), the existing DCD file is replaced with the DCD file to be added and placed in the directory. (S380).

On the other hand, if the DCD file name including the device component 150 is different from the DCD file name including the existing device component 150 (S380), after placing the DCD file to be added to the directory, and the existing DCD file Remove from the directory (S390).

The device manager component 140 arranges all of the files related to the device component 150 in a directory and performs the process after FIG. 5A.

Referring to FIG. 5, the device manager component 140 parses an XML file placed in a file directory. Here, the XML file includes an SPD / SCD / PRF file, and the device manager component 140 allows the SPD file to be parsed among the XML files in step S400 (S400).

The device manager component 140 loads the executable file extracted from the parsing result of the SPD file into the corresponding device component 150 (S410). Accordingly, the device component 150 drives the executable file loaded by the device manager component 140 (S420).

The device manager component 140 registers the driving device component 150 (S430) and registers it with the domain manager (S440). At this time, the domain manager initializes and configures the corresponding device component 150.

Finally, the device manager component 140 registers itself with the naming server 110 (S450). Thus, the process of installing the new device component 150 in the SCA-based SDR terminal system is terminated.

As described above, the apparatus and method for managing a new device component of a mobile terminal according to the present invention are not limited to the configuration and method of the embodiments described above, but the embodiments may be modified in various ways. All or some of the embodiments may be selectively combined.

1 is a block diagram showing a system configuration applied to a portable terminal according to an embodiment of the present invention.

2 and 3 are exemplary diagrams illustrating a file directory structure according to an exemplary embodiment of the present invention.

4 and 5 are flowcharts illustrating an operation flow for a method for managing a new device component of a mobile terminal according to an embodiment of the present invention.

Claims (15)

delete A new device component management apparatus for a mobile terminal, A domain profile in which component related files operated in a domain system of the mobile terminal are defined; A device component for managing a device in the domain system; And The component related files defined in the domain profile are arranged and managed in a file directory structure, and when the mode is changed to a new device during operation of the domain system, a device component related file corresponding to the new device is additionally arranged in the file directory. A device manager component for reconfiguring components in the domain system; The device manager component, When adding the new device, check whether a directory for adding and placing a device component related file of the new device exists in the file directory, and stores the device component related file in the corresponding directory. Component management device. The method according to claim 2, The device manager component, And a file directory for arranging the device component related file is additionally generated when a directory for additionally arranging the corresponding device component related file does not exist. A new device component management apparatus for a mobile terminal, A domain profile in which component related files operated in a domain system of the mobile terminal are defined; A device component for managing a device in the domain system; And The component related files defined in the domain profile are arranged and managed in a file directory structure, and when the mode is changed to a new device during operation of the domain system, a device component related file corresponding to the new device is additionally arranged in the file directory. A device manager component for reconfiguring components in the domain system; The device component related file is And at least one of a device configuration descriptor file, an XML file, and an executable file. The method of claim 4, The device configuration descriptor file is And at least one of initial driving information of the device manager component and the new device information. The method of claim 4, The XL file is, And a software package descriptor file, a software component descriptor file, and an attribute descriptor file. The method of claim 4, The device manager component, And arranging the device component descriptor file, the XML file, and the executable file in parallel in a corresponding file directory. delete As a new device component management method of a mobile terminal, Arranging and managing a component related file operated in a domain system of the mobile terminal in a file directory structure; Checking whether a directory in which the device component related file is to be additionally placed exists; Placing a device component related file corresponding to the new device in the file directory when the mode is changed to a new device while the domain system is in operation; And And driving the device component by executing a corresponding device component related file additionally disposed in the file directory. The method of claim 9, If there is a directory in which the device component related file is to be additionally placed, copying the device component related file and storing the device component related file in a corresponding directory. The method of claim 9, And generating a file directory in which the device component related file is to be placed, if there is no directory in which the device component related file is to be additionally placed. As a new device component management method of a mobile terminal, Arranging and managing a component related file operated in a domain system of the mobile terminal in a file directory structure; Placing a device component related file corresponding to the new device in the file directory when the mode is changed to a new device while the domain system is in operation; And And driving the device component by executing a corresponding device component related file additionally disposed in the file directory. The device component related file is And at least one of a device configuration descriptor file, an XML file, and an executable file. The method of claim 12, The device configuration descriptor file is And at least one of initial driving information of the device manager component and the new device information. The method of claim 12, The XL file is, A method of managing a new device component for a mobile terminal, comprising a software package descriptor file, a software component descriptor file, and an attribute descriptor file. The method of claim 12, The additional arrangement step, And arranging the device configuration descriptor file, the XML file, and the executable file in parallel in a corresponding file directory.

Images