KR20130071092A - Docking device for connection with mobile terminal, and method for installing software thereof - Google Patents

Abstract

PURPOSE: A docking device which is connected to a portable terminal and a software installation method thereof are provided to allow the docking device to install docking control software suitable for the portable terminal. CONSTITUTION: When a response message for a connection request message is received after transmitting the connection request message to a portable terminal, a docking management unit(270) determines non-installing of a docking agent corresponding to a docking device in the portable terminal. The docking management unit extracts an installation file corresponding to the portable terminal among installation files stored in the docking device by using portable terminal information. The docking management unit transmits the extracted installation file and an installation command to the portable terminal. [Reference numerals] (210) Image output device; (220) Audio output device; (230) Touch input device; (235) Key pad input device; (240) Signal processing unit; (250) Docking interface unit; (252) Image input/output I/F; (254) Audio input/output I/F; (256) Data input/output I/F; (260) Storage device unit; (270) Docking management unit; (272) Connection setting unit; (274) Display control module; (276) Input event processing unit; (280) Power unit

Description

Docking device for connection with mobile terminal, and Method for installing software

The present invention relates to a docking device and a driving method thereof, and more particularly, to a software installation method when the docking device is docked with the portable terminal.

As semiconductor and wireless communication technologies are gradually developed, portable terminals have various additional functions such as cameras, MP3s, the Internet, games, etc., in addition to basic telephone call functions, thereby enabling the use of portable terminals. In recent years, smart phones, which have been enhanced with such functions, have begun to spread, and various application programs that can be used in smart phones have been developed in line with this trend.

However, since the portable terminal has to consider portability and mobility, there is no limit to the size of the terminal, and thus there is a problem in that the screen size, resolution, speaker performance, etc. are also limited.

In the prior art, in order to utilize data, sound source files, and contents stored in the portable terminal in a better use environment, a device (aka, docking station) capable of connecting the portable terminal to a laptop or a computer and the like has been developed. Laptops, computers, and the like have been used to output data, sound files, and contents stored in portable terminals to speakers with larger screens and better performance.

At this time, the software for docking control is installed in the portable terminal to suit the docking device corresponding to the portable terminal. However, as the docking devices that can be linked to and connected to the mobile terminal are diversified, corresponding software is required to be installed for each docking device.

Background Art of the Invention There is a patent document relating to a docking device for a mobile phone, a mobile phone that allows the user to quickly and conveniently use the voice call function, text transmission function, image processing function, Internet search function and other PC functions of the mobile phone A docking device for a device is disclosed.

KR 0313581 B1 Oct. 22, 2001 Drawing 1

The present invention provides a docking control software suitable for a portable terminal to which a docking device is connected.

According to an aspect of the present invention, a docking device docked with a portable terminal is provided a method for installing software on the portable terminal.

Software installation method according to an embodiment of the present invention, the docking device for storing the installation file and the installation file information of the docking agent for each mobile terminal, the docking management unit mounted on the docking device, the docking connection with the portable terminal Receiving a docking detection signal, the docking manager acquiring portable terminal information through a docking interface of the portable terminal, the docking manager transmitting a connection request message to the portable terminal, and the docking manager Determining that a docking agent corresponding to the docking device is not installed in the portable terminal when the response message for the connection request message is not received, from the installation file stored in the docking device using the portable terminal information; Description corresponding to the mobile terminal And a step, and transmitting the extracted installation files and install the docking command management section to the mobile terminal to extract a file.

According to another aspect of the present invention, a docking device docked with a portable terminal is disclosed.

A docking device according to an embodiment of the present invention includes a storage device for storing installation file and installation file information of a docking agent for each mobile terminal;

A docking interface unit docked and connected to the portable terminal; And

When the docking detection signal according to the docking connection is received, when the mobile terminal information is obtained through the docking interface of the mobile terminal, and a connection request message is transmitted to the mobile terminal, a response message for the connection request message is not received. It is determined that a docking agent corresponding to the docking device is not installed in the portable terminal, the installation file corresponding to the portable terminal is extracted from the installation files stored in the docking device using the portable terminal information, and the extracted installation file. And a docking management unit for transmitting an installation command to the portable terminal.

The present invention can improve the compatibility of the portable terminal and the docking device by installing the docking control software suitable for the portable terminal to which the docking device is connected even if the docking device is not the portable device.

1 is an example of a block diagram of a portable terminal connected to a docking device.
2 is an example of a block diagram of a docking device.
3 is an example of an external perspective view of the docking device of FIG. 2.
4 is a diagram illustrating a configuration of a docking interface unit.
5 is a flowchart illustrating a method of installing software on a portable terminal when the docking device is docked with the portable terminal.

While the present invention has been described in connection with certain exemplary embodiments, it is to be understood that the invention is not limited to the disclosed embodiments, but, on the contrary, is intended to cover various modifications and similarities. It should be understood, however, that the invention is not intended to be limited to the particular embodiments, but includes all modifications, equivalents, and alternatives falling within the spirit and scope of the invention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, the present invention will be described in detail with reference to the accompanying drawings. In addition, numerals used in the description of the present invention are merely an identifier for distinguishing one component from another.

Also, in this specification, when an element is referred to as being "connected" or "connected" with another element, the element may be directly connected or directly connected to the other element, It should be understood that, unless an opposite description is present, it may be connected or connected via another element in the middle.

In the present specification, the mobile terminal may include a mobile phone, a smart phone, a laptop computer, a digital broadcasting terminal, a personal digital assistant (PDA), a portable multimedia player (PMP), navigation, and the like.

Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings. In the following description of the present invention, the same reference numerals will be used for the same means regardless of the reference numerals in order to facilitate the overall understanding.

1 is an example of a block diagram of a portable terminal connected to a docking device. 4 is a diagram illustrating a configuration of a docking interface unit.

Hereinafter, an example of a portable terminal connected to the docking device will be described with reference to FIG. 4 based on the block diagram of FIG. 1.

Referring to FIG. 1, the portable terminal 100 coupled to the docking device 200 includes a wireless communication unit 110, an A / V input device unit 120, a user input unit 130, a sensing unit 135, and an image. The processor 140, the internal storage unit 150, the external storage unit 155, the image output device 160, the audio output device 165, the docking interface unit 170, the controller 180, and the power supply unit 190. ). The power supply unit 190 may include a battery for charging the terminal.

However, some of the components of FIG. 1 may not necessarily correspond to components necessary for the implementation of the present invention, and in some embodiments, the mobile terminal 100 includes more components than this. Of course you can.

Hereinafter, the components of the mobile terminal 100 will be described in order.

The wireless communication unit 110 performs a wireless communication function between the mobile terminal 100 and the wireless communication system or between the mobile terminal 100 and another terminal. The mobile terminal 100 may be a mobile communication terminal, in which case the wireless communication unit 110 may include a mobile communication module. In addition, according to the type of portable terminal, the wireless communication unit 100 may include a communication device such as a short range wireless communication module, a wireless internet module, a broadcast receiving module, a GPS receiving module, or the like.

In addition, in the present specification, the mobile terminal 100 is illustrated as including a device for wireless communication, such as a mobile phone, a smart phone, etc., the mobile terminal docked and coupled to the external device does not necessarily need to include a wireless communication device, wired It may be a terminal including a communication device or a terminal in which a communication function is not supported.

The A / V input unit 120 is for inputting an audio signal and / or a video signal, and may include a camera and a microphone.

The user input unit 130 is a user interface for receiving various commands from a user, and there is no particular limitation on the implementation method thereof. For example, the user input unit 130 may include a keypad input device and / or a touch input device such as a touch pad or a touch screen.

The sensing unit 135 may include various sensors such as an acceleration sensor, a proximity sensor, a contact sensor, and the like to implement additional functions / operations of the mobile terminal 100.

The image processor 140 converts / processes an image signal or data. In addition, when the portable terminal 100 is docked and coupled between the mobile terminal 100 and the docking device 200, the image processing unit 140 may perform image processing, signal conversion processing, etc. on image data to be transmitted to the docking device 200.

The internal storage unit 150 and the external storage unit 155 are used as a data storage location of the mobile terminal 100, and the internal storage unit 150 may be implemented as RAM, SDRAM, flash memory, or the like. The external storage unit 155 may be implemented as an SD card, a USB memory, or the like. In particular, the docking device 200 in a docked state may also function as the external storage unit 155.

The image output device 160 may be implemented as a liquid crystal panel, an AMOLED, and the like, and the audio output device 165 may include a speaker, a receiver, a buzzer, and the like.

When the docking interface unit 170 is physically docked between the portable terminal 100 and the docking device 200, the docking interface unit 170 outputs image data, an audio signal output, and a portable terminal (eg, from the portable terminal 100 to the docking device 200). 100 and the docking device 200 may include an interface for inputting and outputting data. To this end, the docking interface 170 may include an image input / output interface 172, an audio input / output interface 174, a data input / output interface 176, and the like, as shown in FIG. 1. Of course, fewer or more interfaces may be included than the interfaces shown in FIG. 1, depending on the embodiment. For example, the docking interface 170 may not include the audio input / output interface 174 according to the design. As another example, the docking interface unit 170 may be a power input terminal (not shown) that functions as a passage for receiving power from the docking device 200 side to the portable terminal 100 in a docked state with the docking device 200. ) May be included. In addition, it is apparent that the docking interface unit 170 may further include additional interfaces according to a design scheme.

A detailed configuration example of the docking interface unit 170 is illustrated through FIG. 4. Referring to FIG. 4, according to another exemplary embodiment, the docking interface unit 170 may include a high definition multimedia interface (HDMI) standard and data input / output as an interface for video / audio input / output when docked with the docking device 200. An example is shown where the Universal Serial Bus (USB) standard is used as the interface for the network. In this case, the docking interface 170 may be provided with a connector for supporting HDMI and USB, respectively. However, FIG. 4 is merely an example, and various interface configurations may be possible, and other video / audio input / output interface methods and data input / output interface methods other than HDMI and USB may be used.

In addition, through the docking interface unit 170 provided in the mobile terminal 100, by connecting to the electronic device or home appliances having an HDMI or USB terminal, the image / audio of the mobile terminal 100 to the electronic device or home appliances Can be output through the video output device and the audio output device. That is, the screen of the mobile terminal 100 may be connected to a general electronic device (for example, a TV or a monitor) that does not have the same configuration as the docking device 200 to be described later through the HDMI or USB terminal of the docking interface unit 170. Etc. can also be sent to the electronic device.

The controller 180 controls the components of the mobile terminal 100 and the overall operation of the mobile terminal 100. In particular, the controller 180 may include a docking agent 182 that performs an operation control function of the mobile terminal 100 according to the docking combination with the docking device 200. The docking agent 182 may be implemented as a software program, and when docked with the docking device 200, may be installed by the docking device 200.

Hereinafter, when the portable terminal 100 is docked with the docking device 200, an example of a software installation method of the portable terminal 100 by the docking device 200 will be described with reference to FIG. 5. However, prior to the description of FIG. 5, an example of the docking device 200 will be briefly described with reference to FIGS. 2 and 3.

2 is an example of a block diagram of a docking device, and FIG. 3 is an example of an external perspective view of the docking device of FIG. 2.

However, as described above, in applying the software installation method, the external device that is docked and connected to the mobile terminal 100 does not necessarily have the same configuration as the docking device 200 to be described later. That is, in the case of general electronic devices (eg, TVs, monitors) and the like that do not have the same configuration as the docking device 200 to be described later, the software installation method may be applied in the same or similar manner.

In addition, FIG. 3 illustrates an example of various appearance implementation designs for the docking device, and the docking device 200 is not limited thereto.

Hereinafter, the case of FIG. 2 and FIG. 3 is demonstrated.

2 and 3, the docking device 200 may include an image output device 210, an audio output device 220, a touch input device 230, a keypad input device 235, and a signal processor 240. The docking interface unit 250 may include a storage device unit 260, a docking manager 270, and a power supply unit 280. Here, the image output device 210, the audio output device 220, the touch input device 230, the keypad input device 235, the storage device unit 260, and the power supply unit 280 are the portable terminal 100 described above. The same components as in the bar, detailed description thereof will be omitted. Hereinafter, the docking interface 250 and the docking manager 270 will be described.

First, the docking interface unit 250 is physically docked with the docking interface unit 170 of the mobile terminal 100, thereby providing a connector for forming a docking connection relationship between the mobile terminal 100 and the docking device 200 ( connector) part. Accordingly, the docking interface unit 250 may be in a pair relationship with the docking interface unit 170 of the mobile terminal 100, in which case the same interface as the docking interface unit 170 of the mobile terminal 100 is provided. Configuration (see FIG. 4 above).

That is, the docking interface unit 250, when docked and coupled, the image input / output interface 252 for receiving image data from the portable terminal 100, the audio input / output interface 254 for receiving audio signals, and the portable terminal 100. It may include an interface 256 for data input and output to and from. In addition, the docking interface unit 250 may include a docking detection unit (not shown) that senses physical docking coupling with the mobile terminal 100, and a power output unit functioning as a passage for supplying power to the mobile terminal 100. Or a terminal, not shown).

For example, as illustrated in FIG. 3, the docking interface unit 250 may be formed at a specific portion in the terminal insertion unit 251 provided to allow the portable terminal 100 to be inserted into the main body of the docking device 200. have. That is, the docking coupling between the docking device 200 and the mobile terminal 100 is such that the docking interface 200 and the docking interface 170 and 250 of the two devices are physically coupled (or contacted) with each other, so that the terminal insertion unit ( It may be achieved by inserting the mobile terminal 100 into the 251.

3 illustrates a case where the portable terminal 100 is completely inserted into the terminal insertion unit 251, but according to the design of the terminal insertion unit 251, a portion of the portable terminal 100 (here The docking interface 170 should be included), but only a physical docking coupling may be made in such a manner that only the docking interface 170 is inserted. In addition, although FIG. 3 illustrates a docking device 200 having a bar-shaped pad shape, the docking device 200 has various designs (for example, a notebook type other than a pad type, a slide type other than a bar type, etc.). Of course it can have.

The docking manager 270 controls overall operation of the docking device 200 when docking is coupled between the mobile terminal 100 and the docking device 200. To this end, the docking manager 270 may include a connection setting unit 272, a display control module 274, and an input event processor 276.

Here, the connection setting unit 272 activates the power state of the docking device 200 (eg, transitions from a standby power state to a power-on state) when the docking engagement with the portable terminal 100 is first detected. Can play a role. In addition, the connection setting unit 272 may establish a host-device connection with the mobile terminal 100 in the docking coupling state.

Accordingly, the docking device 200 may provide the user with the same working environment as the user working environment (video and audio output environment / data input / output environment, etc.) in the portable terminal 100 in the docking combined state.

That is, in the docking combined state, the screen image of the portable terminal 100 is output to the screen of the docking device 200. To this end, the docking manager 270 may include a display control module 274. When the docking combination is first detected, the display control module 274 turns on the screen output of the image output apparatus 210 under the control of the docking manager 270, and receives the docking combination received from the mobile terminal 100. Data regarding the screen image of the mobile terminal 100 at the time point may be output through the image output device 210.

In addition, when receiving an input event (for example, a touch input event, etc.) from an input device (see reference numerals 230 and 235 of FIG. 4) of the docking device 200 in the docking coupling state, the input event processor 276. In response to the received input event, may generate and transmit an event signal used to control the operation of the mobile terminal 100 to the mobile terminal 100.

The docking device 200 may be a kind of dummy device that does not perform any operation in the stand-alone state (ie, cannot perform any operation / function useful to the user). When configured as above, the docking device 200 can be equipped with only the minimum possible functions (that is, display control, touch input control, etc.) and a minimum hardware configuration, so that a user can use a conventional tablet PC / pad / laptop product. While the same work environment is implemented, there may be an advantage of using a lower cost product.

Of course, in another embodiment of the present invention, the docking device 200 may be implemented as an apparatus that may be driven independently by mounting its own OS (herein, the OS refers to an OS that enables stand-alone operation). It may be. For example, the electronic device may be an electronic frame or a video / MP3 player when the mobile terminal 100 is separated from the mobile terminal 100, and the mobile terminal 100 may be extended to a function of the mobile terminal. In this case, of course, the hardware specification will require higher specifications than the form described above (which cannot operate independently).

So far, as the two devices docked and coupled, the portable terminal 100 and the docking device 200 have been described. Hereinafter, the docking device 200 in a docking connection state between the portable terminal 100 and the docking device 200. Will be described in the software installation method in the mobile terminal 100.

In particular, so far, the case in which the portable terminal 100 and the docking device 200 are docked and connected by a physical coupling between the docking interfaces has been mainly described. However, as used herein, the term "dock connection" refers to a docking connection using an intermediate medium (Hub), a specific connection cable (for example, an HDMI cable) in addition to a physical direct coupling method between docking interfaces provided in each device as described above. It is also clarified that docking connections using) are possible.

5 is a flowchart illustrating a method of installing software on a portable terminal when the docking device is docked with the portable terminal.

In operation S501, the mobile terminal 100 and the docking device 200 are docked. In this case, the docking manager 270 of the docking device 200 detects a docking connection with the portable terminal 100. For example, the portable terminal 100 and the docking device 200 may be physically connected using HDMI and USB.

In operation S502, the docking manager 270 of the docking device 200 obtains portable terminal information from the portable terminal 100 through the docking interface according to the detection of the docking connection. Here, the portable terminal information may include manufacturer information and model information. For example, the docking device 200 may obtain HDMI or USB device information of the mobile terminal 100 using an HDMI or USB interface, and the HDMI or USB device information may include manufacturer information and model information. .

In operation S503, the docking manager 270 of the docking device 200 transmits a connection request message to the mobile terminal 100. That is, the docking manager 270 attempts to connect to the docking agent 182 of the mobile terminal 100.

In operation S504, the docking manager 270 of the docking device 200 determines whether a response message to the connection request message to the portable terminal 100 is received. That is, the docking manager 270 determines whether the docking agent 182 responds.

In step S505, when there is no response from the docking agent 182, the docking management unit 270 of the docking device 200 indicates that the docking agent 182 corresponding to the docking device 200 is not installed in the mobile terminal 100. To judge.

In operation S506, when there is a response from the docking agent 182, the docking management unit 270 of the docking device 200 determines that the docking agent 182 corresponding to the docking device 200 is installed in the mobile terminal 100. Then, the version (Version) of the docking agent 182 is checked. Version information of the docking agent 182 may be included in the response message received from the mobile terminal (100).

The docking device 200 may store the installation file and the installation file information of the docking agent 182 for each mobile terminal in advance in the storage device 260. Here, the installation file information may include manufacturer information or model information of the mobile terminal 100, installation file name information, docking agent version information, whether to store the installation file, and download server address information of the installation file.

In operation S507, the docking management unit 270 of the docking device 200 compares the version information of the installation file information stored in the storage unit 260 with the version information of the docking agent 182 included in the received response message. It is determined whether the docking agent 182 version installed in the portable terminal 100 is an old version. Here, the docking manager 270 may extract the version information of the docking agent 182 from the installation file information by using the portable terminal information obtained in step S502.

If the version of the docking agent 182 of the mobile terminal 100 is an old version, the step S508 is entered. If it is not the old version, the step S516 is entered.

In operation S508, the docking manager 270 of the docking device 200 determines whether an installation file exists using the installation file information.

In operation S509, when the installation file exists, the docking management unit 270 of the docking device 200 extracts an installation file corresponding to the portable terminal 100 from the storage device unit 260.

In operation S510, the docking management unit 270 of the docking device 200 transmits the extracted installation file and the installation command to the mobile terminal 100.

In operation S511, the portable terminal 100 installs the docking agent 182 using the installation file according to the reception of the installation file and the installation command. When the docking agent 182 is installed, the process proceeds to step S515.

In operation S512, when the installation file does not exist, the docking management unit 270 of the docking device 200 extracts download server address information corresponding to the mobile terminal 100 from the installation file information.

In operation S513, the docking manager 270 of the docking device 200 transmits the extracted download server address information to the mobile terminal 100.

In operation S514, the mobile terminal 100 accesses the download server using the download server address information to download the installation file using the download server address information, and installs the docking agent 182 using the downloaded installation file. do.

In operation S515, the mobile terminal 100 transmits an installation success message to the docking device 200 according to the installation of the docking agent 182.

In operation S516, a connection procedure is performed between the docking agent 182 of the portable terminal 100 and the docking manager 270 of the docking device 200. That is, the docking agent 182 of the mobile terminal 100 and the docking management unit 270 of the docking device 200 exchange information for connection establishment (for example, a connection negotiation start message, a connection negotiation start ACK message, and the like). can do.

It will be apparent to those skilled in the art that various modifications and variations can be made in the present invention without departing from the spirit or scope of the invention as defined in the appended claims. It will be understood that the invention may be varied and varied without departing from the scope of the invention.

Claims (12)

A docking device docked with a portable terminal to install software on the portable terminal,
Storing, by the docking device, installation files and installation file information of a docking agent for each mobile terminal;
Receiving a docking detection signal according to the docking management unit mounted on the docking device, the docking connection with the portable terminal;
Acquiring, by the docking manager, portable terminal information through a docking interface of the portable terminal;
Transmitting, by the docking manager, a connection request message to the portable terminal;
Determining that a docking agent corresponding to the docking device is not installed in the portable terminal when the docking manager does not receive a response message to the connection request message;
Extracting, by the docking management unit, an installation file corresponding to the portable terminal from the installation files stored in the docking device using the portable terminal information; And
And transmitting the extracted installation file and the installation command to the portable terminal.
The method of claim 1,
The installation file information includes manufacturer information or model information of the mobile terminal, installation file name information, docking agent version information, whether to store the installation file information, download server address information of the installation file.
The method of claim 1,
The docking interface is a USB or HDMI interface, and the portable terminal information comprises manufacturer information or model information obtained using the USB or HDMI interface.
The method of claim 1,
After the docking manager transmits a connection request message to the portable terminal,
When the docking manager receives a response message to the connection request message, determining that a docking agent corresponding to the docking device is installed in the portable terminal, and confirming docking agent version information included in the response message;
Determining whether the docking agent is an old version of the docking agent installed in the portable terminal by comparing the docking agent version information corresponding to the portable terminal included in the installation file information with the docking agent version information included in the response message; ;
If the docking agent installed in the portable terminal is an old version, extracting an installation file corresponding to the portable terminal from the installation files stored in the docking device; And
And transmitting the extracted installation file and the installation command to the portable terminal.
The method according to claim 1 or 4,
Before extracting the installation file,
Determining, by the docking manager, whether there is an installation file corresponding to the portable terminal by using information on whether the installation file is stored in the installation file information;
Extracting, by the docking manager, download server address information of an installation file from the installation file information when the installation file does not exist; And
The docking management unit further comprises the step of transmitting the download server address information to the portable terminal. The method of claim 1,
Receiving, by the docking manager, an installation success message from the portable terminal according to the docking agent installation of the portable terminal; And
And performing a connection procedure between the docking manager and the docking agent.
A docking device docked with a portable terminal,
A storage unit which stores installation file and installation file information of the docking agent for each mobile terminal;
A docking interface unit docked and connected to the portable terminal; And
When the docking detection signal according to the docking connection is received, when the mobile terminal information is obtained through the docking interface of the mobile terminal, and a connection request message is transmitted to the mobile terminal, a response message for the connection request message is not received. It is determined that a docking agent corresponding to the docking device is not installed in the portable terminal, the installation file corresponding to the portable terminal is extracted from the installation files stored in the docking device using the portable terminal information, and the extracted installation file. And a docking management unit configured to transmit an installation command to the portable terminal.
The method of claim 7, wherein
The installation file information may include manufacturer information or model information of a mobile terminal, installation file name information, docking agent version information, storage file installation information, and download server address information of the installation file.
The method of claim 7, wherein
And the docking interface is a USB or HDMI interface, and the portable terminal information comprises manufacturer information or model information obtained using the USB or HDMI interface.
The method of claim 7, wherein
When the docking management unit receives a response message to the connection request message, the docking manager determines that a docking agent corresponding to the docking device is installed in the portable terminal, checks docking agent version information included in the response message, and installs the docking agent. By comparing the docking agent version information corresponding to the portable terminal included in the file information with the docking agent version information included in the response message, it is determined whether the docking agent installed in the portable terminal is an old version, and the docking installed in the portable terminal When the agent is an old version, the docking device, characterized in that for extracting the installation file corresponding to the portable terminal from the installation files stored in the docking device, and transmits the extracted installation file and the installation command to the portable terminal.
The method of claim 7, wherein
The docking management unit determines whether an installation file corresponding to the portable terminal exists by using the information on whether the docking management unit stores the installation file included in the installation file information, and if the installation file does not exist, the installation file Docking device, characterized in that for extracting the download server address information of the installation file from the information, and transmits the download server address information to the portable terminal.
The method of claim 7, wherein
The docking management unit performs a connection procedure with the docking agent when receiving a successful installation message from the portable terminal according to the installation of the docking agent of the portable terminal.

Images