KR100779213B1 - Method and apparatus for managing usb device for linux desktop - Google Patents

Abstract

The present invention relates to an apparatus and method for efficiently managing an application for a USB device when using the USB device in a Linux desktop.

The present invention recognizes the USB event for the USB device delivered from the Linux kernel in real time and analyzes the USB event to inform the user of the analysis result of the USB event in real time to the user through a user interface, the USB event is USB In the case of a file system mount event according to the connection, the directory of the file system mount is output, and when the USB device is connected, it is determined whether the device driver required by the USB device is installed. If not, the device driver server is connected to the device driver server to install the device driver. Remote install automatically.

Linux, Desktop, Real Time Notification, USB Device, Remote Installation

Description

Application management method and device of USB device on Linux desktop {METHOD AND APPARATUS FOR MANAGING USB DEVICE FOR LINUX DESKTOP}

1 is a schematic structural block diagram of a Linux desktop to which the present invention is applied.

2 is a block diagram of an application management apparatus of a USB device according to the present invention.

3 is a flowchart illustrating an application management method of a USB device according to the present invention.

4 is a flowchart illustrating a process of processing a file system mount event in a method of managing an application of a USB device according to the present invention.

5 is a flowchart illustrating a remote driver installation process for a USB device according to an embodiment of the present invention.

Explanation of symbols on the main parts of the drawings

110: help program interface unit 120: USB event analysis unit

130: USB device information processing unit 140: notification unit

150: user interface unit 160: browsing unit

170: device driver installation unit 180: user command processing unit

200: Help Program 300: Linux Kernel

The present invention relates to the application management of the USB (Universal Serial Bus (USB) device), the device and method for efficiently managing the application for the USB device, especially when using a USB device in a Linux desktop It is about.

The computer operating system Linux (LINUX) is a program's open source code that allows programmers to add specific features as they wish, and is the basic operating system for computers that can be ported to any platform. The core applications required for Linux are already available, and some of the world's leading telecommunications companies, including IBM, Compaq, and Intel, are releasing server products running on Linux and willing to support them. As Linux users continue to grow, more and more companies are looking to commercialize Linux, and Linux installation and configuration, management and management skills, and programming training are becoming more active.

USB is a serial port that solves the slow speed and limited device connectivity issues of traditional external expansion ports (serial or parallel), connecting peripherals such as audio players, joysticks, keyboards, phones, scanners, and printers to computers. It is a plug and play interface. Recently, most computers and computer peripherals support the application of USB devices. Here, the application of the USB device generally means a program designed to perform a task to a user or another program in using the USB device. For example, there may be a program for performing a function of managing and processing access information, removal information, capacity information, file system mount information, model information, and the like of the USB device. In order for Linux desktop users to use USB devices efficiently, it is important to manage their application efficiently.

In general, however, Linux desktops with Linux as their operating system do not provide the ability to efficiently manage USB device applications. That is, when a Linux desktop user connects a USB device to a USB device port, the connection status of the USB device is not immediately known, and when mounting a file system according to the USB connection, the directory for mounting the file system If the driver is not installed for the UBS device connected to the Linux desktop, the device driver must be installed manually.

In this regard, Korean Patent No. 432663 (Signal Processing Apparatus and Method thereof) and Korean Patent No. 424993 (Agent provided by a USB device for executing a USB device dependent program in a USB host) and a paper " Peter Chubb, "Linux Kernel Infrastructure for User-Level Device Drivers", Linux.Conf.Au 2004, CD distribution, Jan 2004, and the like have been proposed to solve some of the problems described above.

The prior patent No. 432663 configures a power manager that resolves a USB device signal to a FIFO in order to solve a device stop when a plurality of USB devices are connected, so that operation is normally performed. In addition, the prior patent No. 424993 enables the device function and diagnosis by the agent of the executable file included in the USB device when the USB device is plugged in. The device agent drives the applet to provide more information, It is supposed to provide a URL. A data processing system for obtaining detailed information about a device is disclosed, in addition to being generally recognized as a mass storage device for a CD ROM, a floppy driver, and the like. Furthermore, the paper proposes a method of resourceing a device driver in user mode. This method is easy to develop to support device drivers and can provide functionality as an interface in user mode. Using this method, new device drivers can be easily provided, but application management for managing existing USB device drivers and installing uninstalled device drivers is not described.

As described above, the above-mentioned prior arts provide a solution to an unstable use such as the suspension of a USB hardware device, a data processing for obtaining information about the USB device, and a method of providing a device driver at a user level. Even if the connection or removal of the USB device is normal, the connection or removal notification is not implemented in real time at the application management level of the USB device, and when the file system is mounted according to the USB connection, it cannot be output to the user in real time, It does not provide a method for remote installation or server-based device driver installation.

The present invention has been proposed to solve the above problems, the application management device of the USB device to inform the user of the connection or removal information of the USB device according to the USB event in real time when a USB event occurs in the Linux desktop and The purpose is to provide a method.

In addition, the present invention has a further object to provide an application management apparatus and method for a USB device for outputting the directory contents to the user in real time when the file system is mounted in accordance with the connection of the USB device in the Linux desktop.

In addition, the present invention can efficiently manage the application of the USB device in the Linux desktop by remotely installing the device driver when the device driver is not installed when the USB device is connected in the Linux desktop with the above objects. It is another object to provide an apparatus and method.

Application management apparatus for a USB device in the Linux desktop according to the present invention for achieving the above object, USB that recognizes the USB event for the USB device delivered from the Linux kernel in real time and analyzes the information of the USB event An event analyzer; And a notification unit for notifying the user of the information of the USB event in real time to the user interface.

In an embodiment of the present disclosure, the application management apparatus of the USB device acquires information of the USB device according to the USB event and inputs an entry for the information of the USB device in a device information list written according to the type of the USB event. The apparatus may further include a USB device information processing unit for updating, wherein the notification unit may notify the user of updated corresponding entry information in the device information list.

Here, the USB device information processing unit adds an entry for the USB device to the device information list when the USB device is connected, and deletes an entry for the USB device from the device information list when the USB device is removed.

In an embodiment of the present disclosure, the USB event information may include connection or removal information of a USB device, and the USB device connection information may include file system mount information.

In one embodiment of the present invention, the notification unit preferably informs the user of one or more information in a group including connection information, file system mount information, removal information, capacity information or model information of the USB device.

In one embodiment of the present invention, the application management apparatus of the USB device of the present invention may further include a browsing unit for browsing the directory of the file system mount when the USB event is a file system mount event according to the USB connection. .

In another embodiment of the present invention, the application management apparatus of the USB device of the present invention determines whether a device driver required by the USB device is installed when the USB device is connected, and if not installed, automatically installs the corresponding device driver automatically. The apparatus may further include a device driver installation unit.

The device driver installation unit may include a request and reception unit for requesting and receiving a device driver installation service for the USB device by accessing a device driver server; And an installation unit for installing the received device driver in a device module directory.

In an embodiment of the present disclosure, the USB event analyzer may include: a register configured to register a callback function for receiving the USB event; And a receiver configured to receive a USB event by using the callback function.

In addition, the application management method of the USB device in the Linux desktop according to the present invention for achieving the above object, the receiving step of receiving a USB event for the USB device delivered from the Linux kernel in real time; An analysis step of analyzing information of the USB event; An information acquisition step of acquiring information on the USB device; An information updating step of updating the acquired information of the USB device to a previously prepared device information list according to the information of the USB event; And a notification step of informing the user of the update result in real time.

In an embodiment of the present disclosure, the receiving step may include: identifying configuration information of a currently connected USB device; And generating an event socket for registering the USB event and registering a callback function.

In an embodiment of the present disclosure, the information of the USB event may include connection or removal information of a USB device, and the connection information of the USB device may include mount information of a file system.

In one embodiment of the present invention, the information update step adds a corresponding entry to the device information list when the received USB event is a connection of a USB device.

In an embodiment of the present disclosure, the information updating step deletes the corresponding entry in the device information list when the received USB event is the removal of the USB device.

In one embodiment of the present invention, the application management method of the USB device of the present invention, after the analyzing step, browsing the directory of the file system mount if the USB event is a file system mount event according to the USB connection It may further include.

In this case, the browsing step may include: generating a child process for browsing the directory when the file system mount event is recognized; Acquiring path information of a USB device in the child process; Obtaining a mount point of the file system and obtaining a directory path for the file system mount; And outputting the directory path through a file browser.

In another embodiment of the present invention, the application management method of the USB device of the present invention, after the notification step, determining whether the device driver required by the USB device is installed when the USB device is connected; And if not installed may further include an installation step for remotely installing the device driver.

In this case, the installation step may include requesting a device driver installation service for the USB device by accessing a device driver server; Receiving the device driver from the device driver server; And installing the received device driver in a device module directory.

In the following, a detailed description of a preferred embodiment of the present invention will be described with reference to the accompanying drawings. In the following description of the present invention, in the case where it is determined that detailed descriptions of related well-known functions or configurations may unnecessarily obscure the subject matter of the present invention, detailed descriptions thereof will be omitted so as not to obscure the subject matter of the present invention. will be.

1 is a schematic structural block diagram of a Linux desktop to which the present invention is applied.

Referring to FIG. 1, the application management apparatus 100 for a USB device according to the present invention receives a USB event notified from the Linux kernel 300 of a Linux desktop through the help program 200 to guide the user. That is, when the help program 200 in the Linux desktop receives the USB event notified from the Linux kernel 300 as the lower layer, the helper program 200 notifies the application management apparatus 100 of the upper layer USB device. Thus, the USB device application management apparatus 100 of the present invention receives the USB event and analyzes it, manages the application of the corresponding USB device according to the analysis result of the USB event, and informs the user in real time. In this case, the USB device application management apparatus 100 preferably calls a function of an application corresponding to the USB event when a USB event occurs by using a call back function.

2 is a block diagram of an application management apparatus of a USB device according to the present invention.

2, the application management apparatus 100 of the USB device according to the present invention, the help program interface unit 110, USB event analysis unit 120, USB device information processing unit 130, notification unit 140 , A user interface unit 150, a browsing unit 160, a device driver installation unit 170, and a user command processing unit 180.

The application management apparatus 100 of the USB device of the present invention operates according to the USB event transmitted from the help program 200. That is, when a USB event occurs, the application management apparatus 100 of the USB device receives the USB event from the help program 200 through the help program interface 110 using a callback function.

The USB event analyzer 120 initializes configuration information of the user interface 150 and the USB device currently connected to the Linux desktop, registers a callback function for receiving the USB event, and uses the callback function. The USB program is received through the help program interface 110. In addition, the USB event analyzer 120 analyzes the received USB event. For example, it is preferable to analyze whether the USB event is a connection event or a removal event of the USB device, and further, whether the file system mount event is analyzed when the USB device is connected. Here, a file system is a way of naming files on a computer and logically indicating where they should be placed for storage or retrieval. All common operating systems have a file system where files are located somewhere hierarchically. Filesystems include a format for setting the path to a file through the directory structure. Filesystem mounts make a set of files available to users within this filesystem structure.

The USB device information processing unit 130 grasps and manages related information of the USB device corresponding to the USB event. That is, the USB device information processing unit 130 creates a device information list for managing information on the USB device and updates the information of the USB device in the device information list. For example, when the USB event is a connection of a USB device, various kinds of information about the USB device are acquired, an entry for the obtained information is added to a previously prepared device information list, and when the USB device is removed, the device information list is displayed. Delete the entry. As such, the USB device information processing unit 130 records the information on the USB device in the device information list whenever a USB event is notified so that the user 10 can be informed of various kinds of information on the USB device in real time. And manage it.

The notification unit 140 preferably notifies the user 10 of the analysis result of the USB event analysis unit in real time through the user interface unit 150. More preferably, the analysis result may be notified to the user 10 in real time together with various types of information recorded in the device information list. For example, when the USB event is received, the notification unit 140 may inform the user 10 only whether the connection event or the removal event of the USB device is received. System mount information, model information, etc.) may be informed to the user 10.

The user interface unit 150 is responsible for interfacing between the application management apparatus 100 and the user 10 of the USB device.

 The browsing unit 160 automatically recognizes the file system mount position when the USB event is a connection event of the USB device, in particular, a file system mount event, and browses the directory of the USB device to the user 10 in real time. Let (10) be aware of this. This saves users the trouble of opening or finding the filesystem mount directory of a USB device on the Linux desktop.

The device driver installation unit 170 determines whether a device driver for the USB device is installed when the USB event is a connection event of the USB device, and if not installed, the device driver installation unit 170 provides a device driver installation service. It connects to a driver server (not shown), requests transmission of a corresponding device driver, receives an installation file of a device driver from the device driver server, and installs it in a device module directory. As a result, when a USB device is connected, an uninstalled device driver is automatically installed.

In addition, the application management apparatus 100 of the USB device of the present invention may process information by the user (10). When the user 10 transmits a user command to the application management apparatus 100 of the USB device through the user interface unit 150, the user command processor 180 displays various information of the corresponding UBS device according to the user command. Process, and transmits the result to the user 10 through the user interface unit 150.

3 is a block diagram of a USB event analysis unit according to an embodiment of the present invention.

Referring to FIG. 3, the USB event analysis unit 120 according to the present invention registers a callback function 121 for registering a callback function for receiving a USB event transmitted from the help program interface 110 and the registered callback function. It includes a USB event receiving unit 122 for receiving the USB event. As such, the USB event analyzer 120 of the present invention receives the USB event by using the callback function and analyzes whether the received USB event is a connection event or a removal event of the USB device.

4 is a block diagram illustrating a device driver installation unit according to an embodiment of the present invention.

Referring to FIG. 4, the device driver installation unit 170 according to the present invention connects to a device driver server (not shown) of a remote place, requests a device driver installation service for the USB device, and responds to the request. And a device driver installation unit 172 which installs the received device driver in the predetermined device module directory. In particular, the device driver installation unit 170 according to the present invention determines whether the device driver for the USB device is installed, and if not installed, the remote site for providing the corresponding device driver installation service in the request and reception unit 171. Connects to a device driver server (not shown) to request transmission of the corresponding device driver, and receives an installation file of the device driver from the device driver server. In addition, the device driver installation unit 172 installs the received device driver in a specific device module directory.

5 to 7 are flowcharts illustrating an application management method of a USB device according to an embodiment of the present invention.

5 is a flowchart illustrating an application management method of a USB device according to occurrence of a USB event in a Linux desktop according to an embodiment of the present invention.

Referring to FIG. 5, in the application management initialization step S501, the user interface unit 150 for outputting information to the user 10 is initialized, and the configuration of the USB device currently connected in the configuration information initialization step S503. Understand the information. Configuration information of the USB device is stored and managed in a previously prepared device information list. After that, when the new USB device is connected, the same management information as that of the currently connected USB device is managed.

Next, an event socket for processing a new USB event is generated (S505), and a callback function for receiving a USB event is registered (S507). After these steps are performed, a USB event is received by the callback function (S509). Determine the type of the received USB event (S511), if the USB event is a USB device connection, obtain the information of the USB device, create a corresponding entry in the USB device information list and register the device information (S513). In operation S517, the notification unit 140 notifies the user of the USB device connection and / or the USB device information in real time. In this case, the notification may be implemented in various ways. For example, a pop-up message may be notified while the program is running.

Subsequently, it is determined whether the device driver required by the USB device is installed (S519). If it is already installed, the corresponding device driver information is added to the corresponding entry in the device information list (S521). The driver performs a remote installation process (S523).

Meanwhile, in step S511, if the received USB event is a removal event of the USB device, the USB device may be removed in real time using a pop-up message after acquiring information on the removed USB device and deleting the corresponding entry from the USB device information list. Inform (S525 ~ S529).

Here, the notification steps S517 and S529 may notify the user only of the type of the USB event, and may also inform the USB device related information as well as the type of the USB event. For example, only the USB device may be notified of whether the USB device is connected or removed, and the USB device may also be informed of capacity information, file system mount information, model information, and the like.

6 is a flowchart illustrating a process of processing a file system mount event in an application management method of a USB device according to an embodiment of the present invention.

Referring to FIG. 6, when the received USB event is a USB connection event, in particular, a file system mount event in step S513 of FIG. 5, the user automatically outputs a file stored in the USB device. It is shown.

As shown in FIG. 6, when a file system mount event is recognized when the USB device is connected (S601), a child process for processing the same is generated (S603). The child process acquires device path information on the USB device (S605). Subsequently, a location of the file system mount is obtained (S607), a directory path for the file system mount is obtained (S609), for example, a file name is output through a file browser (S611), and the process ends. This has the advantage of reducing the need to open the USB device mount directory in Linux or to artificially find the directory path.

FIG. 7 is a flowchart illustrating a remote device driver installation process for a USB device according to an embodiment of the present invention. As shown in FIG. 4, when a USB device device driver is not installed, the device driver is not installed. FIG. 1 illustrates an embodiment of remotely installing a device driver.

Referring to FIG. 7, a remote device driver server (not shown) generates a service request socket for obtaining a device driver installation service request from the USB device application management apparatus 100 (S701). Subsequently, after generating the request service receiving daemon (S703), the service waits for a service request for device driver installation for the USB device from the USB device application management apparatus 100 (S705). When a device driver installation service request is received from the USB device application management apparatus 100 (S707), a child process for processing a corresponding service request is generated to process the requested service (S709). At this time, the storage location of the requested device driver is checked (S711). If the storage location directory of the corresponding device driver exists, the file name of the installation command of the device driver is transmitted to the USB device application management apparatus 100 (S713, If the storage location directory of the corresponding device driver does not exist, the service request for the device driver installation to the USB device application management apparatus 100 is rejected and the corresponding child process is terminated (S713 and S715). Here, the installation command file name of the device driver contains information on the transmission of the corresponding device driver.

When the installation command file name is transmitted (S717), the USB device application management apparatus 100 opens the received installation command file, and requests the device driver server of the remote device to transmit a device driver installation file (S719, S721). ). Subsequently, the device driver server transmits the corresponding installation file according to the installation file transmission request of the USB device application management apparatus 100 (S723). The USB device application management apparatus 100 analyzes the contents of the transmitted installation file and requests transmission of the corresponding device driver file (S725 and S727).

Subsequently, the device driver server transmits a device driver file to the USB device application management apparatus 100 (S729), and the USB device application management apparatus 100 determines a corresponding device driver from the received device driver file. After installation in the device module directory, the installation completion notification is terminated (S731, S733). Subsequently, the device driver server proceeds back to step S705 to wait for a new installation service request for the device driver.

The drawings and detailed description of the invention are merely exemplary of the invention, which are used for the purpose of illustrating the invention only and are not intended to limit the scope of the invention as defined in the appended claims or claims. Therefore, those skilled in the art will understand that various modifications and equivalent other embodiments are possible from this. Therefore, the true technical protection scope of the present invention will be defined by the technical spirit of the appended claims.

As described above, according to the present invention, when the user uses the USB device in the Linux desktop, the application of the USB device can be efficiently managed.

In addition, the present invention can automatically output the directory of the file system mount when the file system mount event for the USB device is received, so that the user can directly open or find the directory.

Furthermore, the present invention further maintains device driver maintenance by using a method that can effectively manage the USB driver of a frequently used USB device in a single server without using an individual, and can effectively handle this when accessing a large client. It has the effect of convenience.

Claims (20)

A USB event analyzer for recognizing and analyzing a USB event for a USB device delivered from a Linux kernel in a real time event driven manner; A USB device information processing unit for updating the pre-written device information list by acquiring information of the USB device when the USB event is a connection event or a removal event; A browsing unit for browsing a directory of the file system mount if the USB event is a file system mount event; And And a device driver installation unit for automatically remotely installing the device driver if the device driver for the USB device in which the connection event has occurred is not installed. The method of claim 1, And a notification unit which notifies, in real time, of an operation result of one of the USB device information processing unit, the browsing unit, and the device driver installation unit through a user interface. The method of claim 1, wherein the USB device information processing unit, Adding an entry for the USB device to the device information list when the USB device is connected; and deleting an entry for the USB device from the device information list when the USB device is removed. Application management device. delete The method of claim 1, And a connection event of the USB device comprises a file system mount event for the USB device. The method of claim 2, wherein the notification unit, And at least one piece of information is informed to the user in a group including connection information, file system mount information, removal information, capacity information or model information of the USB device. delete delete The method of claim 1, wherein the device driver installation unit, A request and reception unit accessing a device driver server to request and receive a device driver installation service for the USB device; And A device driver installation unit for installing the received device driver in a device module directory; Application management apparatus of the USB device in the Linux desktop comprising a. The method of claim 1, wherein the USB event analyzer, A callback function registerer that registers a callback function for receiving the USB event; And A USB event receiver for receiving a USB event by using the callback function; Application management apparatus of the USB device in the Linux desktop, further comprising. A receiving step of receiving a USB event for a USB device delivered from a Linux kernel in a real time event driven manner; Analyzing the USB event to determine a type of the USB event; An information updating step of acquiring information on the USB device and updating the pre-written device information list if the USB event is a connection event or a removal event of the USB device; A browsing step of browsing a directory of a file system mount if the USB event is a file system mount event of the USB device; An installation step of remotely installing a corresponding device driver if a device driver required by the USB device is not installed when the USB device is connected; And And a notification step of informing the user of the operation result of the update step, the browsing step, or the installation step in real time. The method of claim 11, wherein the receiving step, Identifying configuration information of a currently connected USB device; And Creating an event socket for processing the USB event and registering a callback function; Application management method of the USB device in the Linux desktop, characterized in that it further comprises. delete delete The method of claim 11, wherein the information update step, And if the received USB event is a connection event of a USB device, adding the corresponding entry to the device information list. The method of claim 11, wherein the information update step, And deleting the corresponding entry in the device information list when the received USB event is a removal event of the USB device. delete The method of claim 11, wherein the browsing step comprises: Creating a child process for browsing the directory upon recognizing the filesystem mount event; Acquiring path information of a USB device in the child process; Obtaining a mount point of the file system and obtaining a directory path for the file system mount; And Outputting the directory path through a file browser; Application management method of the USB device in the Linux desktop comprising a. The method of claim 11, wherein the installation step, Accessing a device driver server and requesting a device driver installation service for the USB device; Receiving the device driver from the device driver server; And Installing the received device driver in a device module directory; Application management method of the USB device in the Linux desktop comprising a. delete

Images