KR20140045966A - Mobile terminal for connection with external device, and method for changing screen image thereof - Google Patents

Abstract

Provided is a mobile terminal which comprises: a docking interface unit; a docking agent; and an application framework, wherein the docking agent obtains display device information corresponding to a display device of an external device, if a docking sensing signal in accordance with a docking connection with the external device through the docking interface unit is received. At this time, the application framework updates preset information of system configuration information of the mobile terminal according to the obtained display device information. [Reference numerals] (AA) Start; (BB,DD) No; (CC) Yes; (S510) Docking connection is detected?; (S520) Receive display device information from a docking device; (S530) Obtain a DPI value corresponding to the received device information; (S540) Need to change DPI?; (S550) Request to update the DPI value and update the DPI value according to the same; (S560) Deliver an environment setting information change event and reflect the updated DPI value; (S570) Transmit image data of an image layout with the updated DPI to the docking device; (S575) Transmit current image data to the docking device

Description

Mobile terminal for connection with external device, and method for changing screen image

The present invention relates to a portable terminal and a driving method thereof, and more particularly, to a method of changing a screen based on display device information of an external device when the portable terminal is docked with an external device.

2. Description of the Related Art As semiconductor and wireless communication technologies are gradually developed, a mobile terminal has various additional functions such as a camera, MP3, Internet, game, etc. in addition to a basic phone call function. 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.

However, such a scheme does not support automatic change to a DPI value corresponding to display device information of a docked external device while the portable terminal is running at runtime. Therefore, through the display screen of the external device docked with the mobile terminal, the video signal corresponding to the DPI value of the display of the mobile terminal is enlarged and output by simply scaling the image. There was a problem such as not fully utilizing the size.

The present invention provides a portable terminal and a driving method thereof capable of providing an optimal use environment when the portable terminal is docked and connected to an external device.

In addition, the present invention, when the docking connection between the mobile terminal and the external device, the screen image is changed through the display screen of the external device adaptively changed according to the display device information of the external device, such as DPI, screen size, screen output basic direction It provides a method and apparatus that can be.

The present invention also provides a portable terminal capable of reconfiguring a screen layout corresponding to display device information of a docked external device while the portable terminal is running at runtime, and a method of changing the screen.

According to an aspect of the present invention, a method of changing a screen in a mobile terminal docked and connected to an external device,

Receiving a docking detection signal according to a docking connection with the external device;

Acquiring display device information corresponding to the display device of the docked external device;

Updating a preset value of system configuration information of the portable terminal according to the obtained display device information; And

I) The application running through the portable terminal or the application requested to be executed can configure a screen layout to be displayed by reflecting the update of the system configuration information. Delivery of a configuration information change event informing of a change in system configuration information, ii) restarting a screen of the running application, and iii) performing at least one of execution termination of an application other than a predetermined application among currently running applications. A screen changing method in a portable terminal is provided.

According to another aspect of the present invention, a portable terminal docked to an external device, the portable terminal comprising: a docking interface unit; Docking agent; And application frameworks,

The docking agent,

When the docking detection signal according to the docking connection with the external device through the docking interface unit is received, display device information corresponding to the display device of the external device is obtained.

The application framework,

A screen in which the preset of system configuration information of the portable terminal is updated according to the obtained display device information, and an application running on the portable terminal or a requested application is displayed to reflect the update of the system configuration information. I) delivery of a configuration information change event informing the running or requested application of the change of the system configuration information so that the layout can be reconfigured, ii) restarting the screen of the running application; And iii) at least one of execution termination of an application except for a predetermined application among currently running applications is provided.

According to an embodiment of the present invention, an optimal use environment may be provided when the mobile terminal is docked with an external device.

In addition, according to an embodiment of the present invention, when the docking connection between the mobile terminal and the external device, the screen image of the DPI, the screen size, the screen output basic direction, etc. is adaptively changed according to the display device information of the external device, It can be output through the display screen.

In addition, according to an exemplary embodiment of the present invention, the screen layout may be reconfigured according to the display device information of the docked external device while the portable terminal is running at runtime.

1 is an example of a block diagram of a portable terminal capable of executing a screen changing method according to an embodiment of the present invention.
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 and 6 are flowcharts illustrating a DPI change method in a mobile terminal coupled with a docking device according to an embodiment of the present invention.
7 is a diagram illustrating the architecture of an Android OS as an example of an operating system mounted on a portable terminal.
8 illustrates an example of a DPI determination table.
9 and 10 are diagrams for explaining a DPI-changed screen layout according to an embodiment of the present invention.
11 is a view for explaining an exception handling method according to an embodiment related to a screen change method of the present invention;
12 is a view for explaining an exception handling method according to another embodiment related to the screen changing method of the present invention.

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 (e.g., first, second, etc.) 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, the present invention will be described in detail with reference to the accompanying drawings. As the screen change element that may be applied to the screen change method in the portable terminal according to the present invention, there are various elements such as DPI, screen size, screen output basic direction, and the like. However, in the present specification, for the purpose of concentration and convenience of description, the screen change method will be mainly described based on DPI in accordance with an embodiment of the present invention. However, it will be apparent to those skilled in the art that the description through the present specification is fully understood that the change of the screen size and the change of the screen output basic direction may be handled in the same manner as in the DPI change. In addition, it will be understood by those skilled in the art that the screen size change and the screen output direction change may be simultaneously made with the DPI change.

[Description of Fig. 1]

1 is an example of a block diagram of a mobile terminal capable of executing a screen change method according to an embodiment of the present invention. 4 is a diagram illustrating a configuration of a docking interface unit.

Hereinafter, an example of a mobile terminal capable of executing the screen changing method of the present invention will be described with reference to FIG. 4 based on the block diagram of FIG. 1.

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

However, some of the components in FIG. 1 may not necessarily be necessary components necessary for the implementation of the present invention. Also, according to the embodiment, the mobile terminal 100 may include more components Of course it is possible.

Hereinafter, the components 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. According to an embodiment of the present invention, the portable terminal 100 may be a mobile communication terminal, and in this case, the wireless communication unit 110 may include a mobile communication module. Also, 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., according to the present invention, the mobile terminal docked and coupled to the external device does not necessarily include a wireless communication device. It may be a terminal including a wired communication device. In some cases, the terminal may not support a communication function.

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 particular, in the embodiment of the present invention, when the image processing unit 140 is docked coupled between the mobile terminal 100 and the docking device 200, the image processing, signal conversion processing for the image data to be transmitted to the docking device 200 And the like.

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, according to an embodiment of the present invention, the docking device 200 in a docked state may also function as the external storage unit 155. According to an embodiment of the present invention, the following data may be stored in the internal storage unit 150 and 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, in some embodiments, fewer or more interfaces may be included than the interfaces shown in FIG. 1. 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 obvious 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 embodiment of the present invention, the docking interface unit 170 may be a high definition multimedia interface (HDMI) as an interface for video / audio input / output when docked with the docking device 200. An example in which the Universal Serial Bus (USB) standard is used as a standard and an interface for data input and output is shown. In this case, the docking interface 170 may be provided with a connector for supporting HDMI and USB, respectively. However, FIG. 4 is just an example, and in addition, 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, according to an embodiment of the present invention, through the docking interface unit 170 provided in the portable terminal 100, by connecting to an electronic device or a home appliance having an HDMI or USB terminal, the image of the portable terminal 100 Audio can be output through the video output device and audio output device of the above electronic device or home appliance. That is, according to the exemplary embodiment of the present invention, the HDMI or USB terminal of the docking interface unit 170 may also be used for general electronic devices (for example, TVs and monitors) that do not have the same configuration as the docking device 200 to be described later. Through the screen of the portable terminal 100 can be transmitted 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, in an embodiment of the present disclosure, 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. For example, the docking agent 182 may be implemented in the “application” layer of the OS hierarchy of FIG. 7 to implement a corresponding function. In addition, the application framework 184 (the OS layer of FIG. 7) to execute a method of changing a screen during docking connection with an external device (this example illustrates the docking device 200) according to an embodiment of the present invention. The "application framework" layer of the structure) can perform specific functions.

Hereinafter, when the docking connection with the docking device 200 is made, a screen changing method in the mobile terminal 100 through the docking agent 182 and the application framework 184, in particular, an embodiment of the DPI changing method is shown. This will be described with reference to 5 and FIG. 6. However, prior to the description of FIGS. 5 and 6, an example of the docking device 200 will be briefly described with reference to FIGS. 2 and 3.

[Description of Fig. 2]

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 screen changing method of the present invention, the external device docked and connected to the portable terminal 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), etc. that do not have the same configuration as the docking device 200 to be described later, the screen changing method according to an embodiment of the present invention may be applied in the same or similar manner. Of course.

In addition, FIG. 3 illustrates an example of various appearance implementation designs for the docking device, and the docking device 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 detects a physical docking coupling with the portable terminal 100, and a power output unit that functions as a passage for supplying power to the portable terminal 100. Terminals, not shown).

According to an exemplary embodiment, as illustrated in FIG. 3, the docking interface unit 250 may be connected to 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. Can be formed. That is, according to an embodiment of the present invention, the docking coupling between the docking device 200 and the portable terminal 100 is docked such that the docking interface portions 170 and 250 of the two devices are physically coupled (or contacted) with each other. The portable terminal 100 may be inserted into the terminal insertion unit 251 of the device 200.

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. 3 illustrates a docking device 200 having a pad type, the docking device 200 may have a wide variety of designs (eg, a notebook type other than the pad type).

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 according to an exemplary embodiment.

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.

According to one embodiment of the present invention, the docking device 200 is a kind of dummy that does not perform any operation in the stand alone state (ie, cannot perform any operation / function useful to the user). It may be a device. 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 is implemented as a device that may be independently driven by mounting its own OS (here, the OS refers to an OS that enables stand-alone operation). 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, the portable terminal 100 and the docking device 200 have been described as two devices docked and coupled according to an embodiment of the present invention. Hereinafter, the portable terminal and the docking device will be described with reference to FIGS. 5 and 6. In the docking connection state, the description will be made mainly of the DPI changing method among the screen changing methods in the mobile terminal.

In particular, until now, the case in which the portable terminal and the external device (ie, the docking device) are docked and connected by the physical coupling between the docking interface 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 possible to use a docking connection method using), and in some cases, a docking method (named wireless docking) according to a wireless connection method, not a physical coupling, may be possible. However, hereinafter, for the purpose of concentrating and convenience of the description of the present invention, it will be described with reference to the case where the physical docking coupling is made similarly to FIG.

5 and 6 are flowcharts illustrating a method of changing a DPI in a mobile terminal coupled to a docking device according to an embodiment of the present invention. Here, FIG. 5 shows a method of changing a DPI in a portable terminal when docked and connected to an external device, and FIG. 6 shows an example of a method for changing DPI when a docked connection is disconnected (released).

7 is a diagram illustrating an architecture of an Android OS as an example of an operating system mounted on a portable terminal, FIG. 8 is a diagram illustrating an example of a DPI determination table, and FIGS. 9 and 10 are embodiments of the present invention. According to this, it is a figure for explaining the screen layout which changed DPI. Hereinafter, a method of changing a DPI in a mobile terminal docked and connected to an external device according to an embodiment of the present invention will be described with reference to FIGS. 7 and 10 with reference to FIGS. 5 and 6.

[Description of Fig. 5]

In operation S510, the docking agent 182 mounted on the mobile terminal 100 detects a docking connection with an external device.

Here, the detection of the docking connection may be used in the following manner. For example, the docking agent 182 may detect a docking connection with an external device according to the reception of the H / W-like HPD signal through the HOT PLUG DETECT terminal (see FIG. 4) of the HDMI interface. As another example, the docking agent 182 may detect the docking connection through communication with the external device through a USB net or an Android Debug Bridge (ADB) according to the docking connection with the external device. That is, the docking agent 182 receives the docking detection signal when the docking connection between the mobile terminal and the external device is performed through the H / W method or the specific communication method as described above to establish a docking connection with the external device. It can be detected.

In this case, the docking agent 182 may control the screen output of the display of the portable terminal 100 to be turned off or to switch the portable terminal 100 to a sleep mode. The docking agent 182 may control (switch) the display path such that an image is not output through the display screen of the portable terminal, but is output only through the display screen of the docking device when docked.

Thereafter, in step S520, the docking agent 182 identifies display device specifications of the docking device by receiving display device information mounted on the docking device from the docked external device (hereinafter, referred to as a docking device). can do.

For example, the display device information may include information regarding a screen resolution and a screen size. For example, extended display identification data (EDID) contains information about the manufacturer name, product type, EDID version, screen size, brightness, pixels, resolution, etc. The docking agent 182 docks by receiving this EDID information. The display apparatus information of the device may be checked.

Of course, in the flowchart of FIG. 5, the display device information is received from the docking device as an example. However, even when the display device information is not based on the EDID information described above, the display device such as the DPI information, the screen resolution, and the screen size information may be used. A method of directly obtaining information may be used. For example, the mobile terminal 100 receives or recognizes device identification information (hereinafter, referred to as a docking device ID) of the docking device 200 and obtains display device information of the corresponding device docked with the device based on the device identification information (hereinafter referred to as a docking device ID). That is, it may be confirmed or estimated. To this end, in the storage medium of the mobile terminal 100, the relevant display device information may be mapped and stored according to IDs of candidate device groups that can be docked and connected to the mobile terminal 100. In this case, the mapping information may be managed by the docking agent 182 of the mobile terminal 100.

In the manner as described above, if the display device information of the docking device is obtained, in step S530, the docking agent 182 obtains a DPI value corresponding to the received (obtained) display device information.

Here, the following method may be used as a method of obtaining a DPI value corresponding to the display device information of the docking device. That is, the docking agent 182 determines a DPI value corresponding to the display device of the docking device by referring to a DPI determination table (see FIG. 8) in which applicable DPI values for each screen resolution and screen size are mapped in advance. This is one example.

8 is a table exemplifying DPI specifications required by the Android OS. Referring to FIG. 8, a small screen (a screen size of about 3 inches or less), a normal screen (a screen size of about 3 to 4 inches, for example, a smartphone screen size), a large screen (a screen size of about 4 to 4 inches) 7 inches), extra large screen (approximately 7 inches or larger), and screen resolution class required DPI values.

Accordingly, the docking agent 182 may determine a DPI value suitable for the display apparatus of the docked external device by using the DPI determination table as shown in FIG. 8. As an example, it is assumed that the mobile terminal 100 has a screen resolution of 800 × 1280 and a screen size of a normal screen, and the docking device has a screen resolution of 800 × 1280 and a screen size of an Extra Large screen.

Therefore, based on the table of FIG. 8, the DPI suitable for the display device of the mobile terminal 100 is XHDPI (Extra high DPI) corresponding to 640x960, which is a screen resolution close to 800x1280 in the normal screen. On the contrary, based on the table of FIG. 8, a DPI suitable for the display device of the docking device becomes a medium DPI (MDPI) corresponding to 800 × 1280 on an extra large screen. That is, in spreading the screen image of the portable terminal 100 to the display screen of the docking device through a docking connection with the docking device, the screen image according to the DPI value suitable for the portable terminal is used instead of the display device of the docking device. You need to spray the reconstructed screen image according to the correct DPI value.

Therefore, the DPI change method in the mobile terminal 100 according to an embodiment of the present invention, when the mobile terminal 100 is not docked connection with the external device, according to the XHDPI value suitable for its display device After outputting the screen image through the display device of the docking connection, the screen image is reconstructed according to the MDPI value suitable for the display device included in the docking device, and the reconstructed screen image is sent to the docking device through the docking interface. It is to. To this end, the docking agent 182 refers to a DPI determination table such as the table of FIG. 8 to determine a DPI value suitable for the display device of the docked external device.

In step S520 and step S530 of FIG. 5 described above, after confirming the display device information of the docking device according to an embodiment of the present invention, using the DPI mapping table as illustrated in FIG. 8, the display device of the docking device The case of determining the appropriate DPI value has been described. However, another method may be used as a method of determining the DPI value suitable for the display device of the docking device. For example, as described above, when docked, the docking agent 182 checks or recognizes the device ID of the docking device, and then displays the docking device ID with a one-to-one mapped DPI value. It may be determined by a DPI value suitable for. However, hereinafter, for convenience and concentration of the description, the description will be made based on the case of steps S520 and S530 of FIG. 5.

In step S540, it is determined whether the determined DPI value has a different value from the DPI value of the mobile terminal 100 (that is, whether a DPI change is necessary). If it is not necessary to change the DPI value according to the determination result of step S540, the current screen image data may be sent to the docking device as it is (see step S575).

On the other hand, if the determined DPI value (i.e., the DPI value for the display device of the docking device) is different from the currently set DPI value (i.e., the DPI value preset for the display device of the mobile terminal), the portable terminal ( 100) performs step S550 to step S570 for changing the DPI value.

In step S550, when the DPI change is required, the docking agent 182 requests the application framework 184 to change (update) the DPI value, and the application framework 184 accordingly requests the system of the mobile terminal 100. The preset DPI value of the system configuration information is updated (modified) with the DPI value determined through the previous step.

In operation S560, the application framework 184 delivers an environment setting information change event, which informs the system environment setting information of the change, to the running or requested applications. The environment setting information change event may be an android.intent.action.CONFIGURATION_CHANGED event in the case of an Android OS. In addition, the application framework 184 allows an application running or requested to be executed through the mobile terminal 100 to reconfigure a screen layout to be displayed by reflecting the updated DPI value.

In this case, at least one of the following methods may be used as a method for allowing the running or requested application to reconfigure the screen layout to reflect the updated DPI value.

In a first manner, when the DPI value of the system is changed according to step S550, the application framework 184 directly (forces) user interface components or activities on the UI screen of each running application. By re-running, the screens of the running applications can be executed again to reflect the updated DPI value.

In a second manner, the application framework 184 calls a preference information change function (which may be the onConfigurationChanged () function in the case of Android OS), so that a running or requested application can reflect itself on the updated DPI value. You can also redraw the App screen. However, the detailed operation of the application framework according to the DPI change may be changed for each OS.

In a third manner, upon receiving a request to change the DPI value from the docking agent 182 according to step S550, the application framework 184 obtains a list of currently running applications and kills the processes of currently running applications. By doing so, when the corresponding applications are later executed (run) by the user or by the system, the application UI screen may be configured according to the changed DPI value.

In this case, the process killing application may be all applications currently running in the mobile terminal 100, but may be applications except for a specific application. Here, the specific applications to be excluded from the process kill process may include applications essential to the implementation of the present invention, such as applications where maintenance of service continuity is important, such as a call app or a music app, or a docking agent program. have. However, a specific application to be excluded from the process kill process may be changed or specified differently according to the designer's or user's choice.

In addition, the process kill process described above may have various modifications depending on the type of OS. For example, prior to executing a process kill in response to a request to change the DPI value, the application framework 184 runs a particular test application in the foreground for a very short time (e.g., a few msecs), previously known as foreground. By switching the application from the state to the background state, you can allow the application to throw an exception, such as saving the current state.

If a screen layout to be displayed reflecting the updated DPI value is configured (or reconfigured) according to the previous step S560, the docking agent 182, in step S570, according to the screen layout reflecting the updated DPI value The image data is transmitted to the docking device through the image input / output interface of the docking interface unit 170.

According to the above-described DPI changing method, when the portable terminal and the external device are docked, the image of the screen layout according to the DPI value suitable for the display device of the docking device may be output through the display screen of the docking device. .

An example screen for this is illustrated in FIGS. 9 and 10. 9 and 10, the screen layout configured in accordance with the XHDPI in the mobile terminal 100 (see the phone of FIGS. 9 and 10) is connected to the docking device (Docking of FIGS. 9 and 10) according to the docking connection. The screen layout is configured according to MDPI. Accordingly, the screen image output on the display screen of the docking device is not enlarged as the screen image of the portable terminal 100, but it is confirmed that more items are displayed according to the screen size of the docking device.

[Description of Fig. 6]

In FIG. 5, the docking connection between the mobile terminal and the docking device has been described in which the DPI is changed to match the display device of the docking device. Hereinafter, when the docking connection is disconnected (that is, released), the flow of changing the DPI to match the display device of the mobile terminal again will be described. However, in the case of FIG. 6, since the flow is generally similar to that of FIG. 5, a description overlapping with that of FIG. 5 will be omitted.

In operation S610, the docking agent 182 receives the undock signal according to the docking detachment with the external device. Accordingly, the docking agent 182 releases the docked connection mode in step S620. Here, the release of the docking connection mode means that the system setting values, the control paths, and the like changed according to the docking connection are returned.

As part of this process, the docking agent 182, in step S630, requests the application framework 184 to update to the DPI value corresponding to the display device information of the mobile terminal.

Then, the application framework 184, in step S640, DPI value corresponding to the display device information of the mobile terminal to the DPI value currently set as the system configuration information of the mobile terminal (that is, the DPI value changed according to the docking connection). Update again with Accordingly, the screen layout of the currently running applications is reconfigured to reflect the DPI value corresponding to the display device information of the mobile terminal. In this way, the reconstructed screen image is output through the display screen of the mobile terminal in step S650.

In the above, with reference to the flowcharts of FIGS. 5 and 6, the description has been focused on the change of the DPI value according to the docking connection and the undocking. Of course, it can be made together. In addition, the screen size change and the screen output direction change may also be based on the system configuration information change method described above.

As in the previous example, if the mobile terminal 100 has a screen resolution of 800 ㅧ 1280 and a screen size of Normal screen, and the docking device has a screen resolution of 800 ㅧ 1280 and a screen size of Extra Large screen, the docking connection Accordingly, the application framework 184 may change the screen size of the system configuration information to an extra large screen corresponding to the docking device.

In addition, in the case of FIG. 9, the screen output directions of the mobile terminal and the docking device are both "vertical longitudinal direction (that is, Portrait direction)", and in the case of FIG. 10, both have "horizontal longitudinal direction (ie, Landscape direction)". Although illustrated as an example, the screen output basic directions of the mobile terminal 100 and the docking device may be different from each other. For example, in the case of a mobile phone or a smartphone, the vertical length direction may be the basic direction of the screen output, and in the case of a notebook or tablet PC, the horizontal length direction may be the basic direction of the screen output.

Therefore, in this case, the docking agent 182 obtains information about the screen output basic direction of the display device of the docking device based on the screen resolution information or the screen size information of the docking device, the docking device device identification information, and the like. If the screen output basic direction of the docking device does not match the existing screen output direction of the portable terminal, the application framework 184 may also request an update to the screen output basic direction of the docking device. Accordingly, the application framework 184 not only updates the DPI value but also updates the screen output basic direction, and the screen layout of each application may be reconfigured to reflect the above-described changes of the screen output default direction. You can do that.

In the above, the DPI change method when the docking connection between the mobile terminal 100 and the docking device is made. Hereinafter, in applying the DPI changing method according to the above embodiments, an exception handling method in a specific situation will be described. An exception handling scheme to be described later is a specific method that may be generated because the DPI change method is applied to the mobile terminal, and the DPI value is different when the mobile terminal operates in a stand-alone manner and when the mobile terminal operates in a docked connection state. It is to solve the case. In this case, for example, a specific case requiring exception handling is as follows.

For example, a case where a specific App requests display device information to the application framework 184 of the mobile terminal 100 may correspond to this case. Recently, there is a variety of electronic devices having different screen sizes, DPIs, screen resolutions, and the like, such as mobile phones, tablet PCs, and laptops. Therefore, it is a general trend to provide an app or a screen suitable for the display device characteristics of each electronic device. .

For example, servers providing various applications distinguish applications for phones and apps for pads from applications that are generally provided according to a terminal to be connected, and also have different interfaces for this. More specifically, for example, when accessing the market through a mobile phone (generally, it will be accessed through a market app installed in the mobile phone), an interface for downloading an app for a phone is displayed on the screen, and the market is displayed through a pad. When connected to the screen, an interface for downloading an app for Pad is displayed on the screen.

Assuming that a specific App operates differently according to the display device information of the portable terminal for the same reason as described above (for example, a division between an App for a Phone and an App for a Pad), when the case of the present invention is applied, the portable When the terminal is operating in stand-alone mode, when accessing the specific App, the interface corresponding to the display device information of the portable terminal is shown, and in the docking connection state, the interface corresponding to the display device information of the docking device is shown in principle. It will be more natural. However, depending on the server, the dynamic interface may not be provided in real time according to the change of the display device information of the portable terminal according to the docking connection. Various embodiments of the exception handling scheme applicable to the mobile terminal for smooth interworking with such a server will be described.

[Description of Fig. 11-Exception Handling Scheme 1]

11 is a diagram illustrating an exception handling method according to an embodiment related to a screen change method of the present invention.

According to the determination of step S1110, when the docking connection state is not (the mobile terminal 100 operates in stand-alone), according to step S1120 a specific App is display device information (in this example, screen size information and DPI information) If the request is the same), the application framework 184 of the mobile terminal 100 may pass the display device information of the mobile terminal 100 to the specific App as in step S1130. This is a normal treatment procedure which is not different from the existing treatment method.

Unlike the above, when the docking connection state is determined according to the determination of step S1110, the DPI value will be changed to the DPI value corresponding to the display device of the docking device by the method as shown in FIG. 5 described above (see step S1140). In this state, when a specific App requests display device information as in step S1150, in step S1160, the application framework 184 does not display information corresponding to the display device of the docking device, but the display device information of the mobile terminal 100. To the specific App.

That is, in the exception handling method of FIG. 11, the DPI information, etc., of the system environment setting information of the mobile terminal 100 is changed (updated) to information corresponding to the display device of the docking device in the docking connection state, but is previously designated a specific App. When a request for display device information is received from the device, fixed information (that is, information currently set) is used instead of information set as actual (current) system configuration information (which may correspond to display device information of the docking device). Information corresponding to the display device information of the mobile terminal) to a specific app so that the app can interoperate with a server that provides a dynamic interface in real time as the display device information of the mobile terminal changes according to the docking connection. It is at its core.

To this end, when the API requesting display device information is called from any App, the application framework 184 determines whether the App which is the call requester is a predetermined specific App, and if it is determined that the App corresponds to the specific App, it is fixed. It serves to pass the display device information of the mobile terminal as the information to the specific App. In this case, the specific app transmits the received display device information to the related server. In contrast, when the App requesting the display device information does not correspond to a specific App, the application framework 184 may pass information set in the actual system configuration information.

According to the exception handling scheme as described above, the same display device information (that is, in this example, the display device information of the mobile terminal, which is always the same information regardless of docking connection) will always be the corresponding server through the specific App. Since it will be passed to, the problem of interface confusion as described above will not occur.

[Description of Fig. 12-Exception Handling Scheme 2]

12 is a diagram illustrating an exception handling method according to another embodiment related to a screen change method of the present invention.

As an exception handling scheme different from that of FIG. 11, in FIG. 12, when it is determined in step S1210 that the device is in the docking connection state, it will be changed to the DPI value of the docking device as in step S1220. This is the same as step S1140 of FIG. 11 described above. Of course, even when not in the docking connection state it can be processed in the same procedure as the steps S1120 and S1130 of FIG.

In such a docking connection state, when a specific App as described above is run (executed) (see step S1130), the application framework 184 returns the DPI value to the DPI value corresponding to the display device of the mobile terminal 100. (Step S1240). That is, in the exception handling method of the present example, even when the docking connection state, when a specific App is driven, the DPI value is changed back from the DPI value of the docking device to the DPI value of the mobile terminal 100.

According to such a change, after the specific App is driven, the display device information of the mobile terminal 100 is always fixed, and thus dynamic in real time according to the change of the display device information of the mobile terminal according to the docking connection. It can be linked with a server that provides an in-line interface. That is, as shown in FIG. 11, a method of passing fixed information is used, while FIG. 12 uses a method of actually changing the DPI when a specific App is driven. Of course, even in the case of Fig. 12, when an app other than the specific app designated in advance is driven, the DPI re-change processing as in the above-described step S1240 does not occur.

The above-described DPI re-change processing in step S1240 may be performed when the specific app is requested to be driven, and also when the specific app is switched to the background state and then back to the foreground state (see step S1230). ).

Subsequently, when the specific App is driven off or driven but switched to the background state as in Step S1250, the specific App may be changed back to a DPI value corresponding to the docking device (see Step S1255). It is also natural, of course, that when it is undocked (see step S1260), it can be restored to the DPI value of the mobile terminal (see step S1270).

In the above, two exception handling methods in applying the DPI changing method of the present invention have been described, but other exception handling methods may be used. That is, FIGS. 11 and 12 change the DPI value to the DPI value of the mobile terminal 100 in advance (in the case of FIG. 12) or the fixed information (in the case of FIG. 11) when the specific App is driven. Mainly explained how to hand over to App. However, in addition to the above scheme, a more active exception handling scheme may be used.

On the contrary, in the case of a server providing a dynamic interface in real time according to the change of the display device information of the portable terminal according to the docking connection, the specific App can directly and immediately notify the server of the change of the display device information.

As an example, whenever a change in a DPI value occurs (ie, whenever docked or undocked) in accordance with the application of the DPI change method of the present invention, the application framework 184 includes such a DPI change. A method of immediately notifying the information through the specific App or the server may be used.

As another example, when the particular App is running (i.e. connected to a server associated with that particular App) or / or when it is switched to the foreground, the information according to the currently set system configuration information (i.e. the current setting) Display device information) through the specific App or to the corresponding server.

While the present invention has been particularly shown and described with reference to exemplary embodiments thereof, it will be understood by those of ordinary skill in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention as defined by the following claims And changes may be made without departing from the spirit and scope of the invention.

Claims (1)

A screen changing method in a portable terminal docked and connected to an external device,
Receiving a docking detection signal according to a docking connection with the external device;
Acquiring display device information corresponding to the display device of the docked external device;
Updating a preset value of system configuration information of the portable terminal according to the obtained display device information; And
I) The application running through the portable terminal or the application requested to be executed can configure a screen layout to be displayed by reflecting the update of the system configuration information. Delivery of a configuration information change event informing of a change in system configuration information, ii) restarting a screen of the running application, and iii) performing at least one of execution termination of an application other than a predetermined application among currently running applications. Steps to
Screen change method in a mobile terminal comprising a.

Images