Patent Description:
In general, terminals may be divided into a mobile or portable terminal and a stationary terminal according to whether or not terminals are movable. In addition, mobile terminals may be divided into a handheld terminal and a vehicle mount terminal according to whether or not users can directly carry it around.

As the functions of terminals are becoming more diverse, terminals can support more complicated functions such as capturing images or video, reproducing music or video files, playing games, receiving broadcast signals, and the like. By comprehensively and collectively implementing such functions, mobile terminals are embodied in the form of a multimedia player or device.

In order to support and increase functions of the terminals, improvement of structural part and/or software part of terminals may be considered.

However, in the related art, when the user receives a call or a text message while using a supplementary function of a mobile terminal, the user must stop or temporarily stop the operation of the supplementary function or the display to receive the call or check the text message. Also, in the related art, even when multitasking is available to be performed, because an application displays information through the entire screen, the user must change the application displayed on the entire screen to perform multitasking. In addition, the related art has a problem in that it is not easy for another application to use information, which is inputted or outputted in an application being executed, causing a user inconvenience in using the different application. <CIT> relates to a views management system that has a computer display which provides a hideable view bar having pane splitting controls and a list of open views. Through selection of specific ones of the pane splitting controls, a system user can configure the display to show any number and arrangement of tiled views. <CIT> relates to a system wherein a touch location detection section detects the location on a display screen where the operator's finger touches. A transfer length calculation section calculates the transfer length La of the operator's finger from the touch start location S to the touch end location E. A transfer length judgment section judges whether or not the transfer length La is greater than a reference transfer length Ls. A location shift calculation section calculates the location shift δ of the operator's finger. A location shift judgment section judges whether or not the location shift δ is less than a predetermined reference location shift δs. When La > Ls and δ < δs, a screen split control section controls the operation of an image display section so as to split a display screen.

Accordingly, one object of the present invention is to provide a mobile terminal having an input method which is different from the conventional one.

Another object of the present invention is to provide a mobile terminal capable of displaying an event that occurs or information processed by a different application while a user is executing a certain application along with the application being currently executed according to a user intention, and facilitating an exchange of information between the executed applications.

To achieve the above objects, there is provided a mobile terminal according to independent claim <NUM>, wherein the dependent claims represent embodiments of the invention.

According to exemplary embodiments of the present invention, a multitasking environment which can be easily regulated by the user is provided. Also, a task currently performed by the user is not interfered with by an event, or the like, which occurs while a main application is being executed, and at the same time, the user can easily check occurring event at a desired time. Also, when the user wants to perform a different operation along with the main application, the user can easily select an application desired to be executed without interfering with the current operation. In addition, the user can easily check several applications which are being concurrently executed.

In addition, information input to or output from one of applications which are concurrently executed can be easily used by a different application which is being executed, thereby providing a more convenient multitasking environment to the user.

Further scope of applicability of the present invention will become apparent from the detailed description given hereinafter. However, it should be understood that the detailed description and specific examples, while indicating preferred embodiments of the invention, are given by illustration only, since various changes and modifications within the scope of the invention will become apparent to those skilled in the art from this detailed description.

The present disclosure will become more fully understood from the detailed description given hereinbelow and the accompanying drawings, which are given by illustration only, and thus are not limitative of the present disclosure, and wherein:.

A mobile terminal according to exemplary embodiments of the present invention will now be described with reference to the accompanying drawings. In the following description, usage of suffixes such as 'module', 'part' or 'unit' used for referring to elements is given merely to facilitate explanation of the present disclosure, without having any significant meaning by itself. In describing the present disclosure, if a detailed explanation for a related known function or construction is considered to unnecessarily divert the gist of the present disclosure, such explanation has been omitted but would be understood by those skilled in the art. The accompanying drawings of the present disclosure aim to facilitate understanding of the present disclosure and should not be construed as limited to the accompanying drawings.

The mobile terminal associated with the present disclosure may include mobile phones, smart phones, notebook computers, digital broadcast receivers, PDAs (Personal Digital Assistants), PMPs (Portable Multimedia Player), navigation devices, and the like. It would be understood by a person in the art that the configuration according to the embodiments of the present disclosure can be also applicable to the fixed types of terminals such as digital TVs, desk top computers, or the like, except for any elements especially configured for a mobile purpose.

<FIG> is a schematic block diagram of a mobile terminal according to an embodiment of the present disclosure.

The mobile terminal <NUM> may include a wireless communication unit <NUM>, an A/V (Audio/Video) input unit <NUM>, a user input unit <NUM>, a sensing unit <NUM>, an output unit <NUM>, a memory <NUM>, an interface unit <NUM>, a controller <NUM>, and a power supply unit <NUM>, and the like. <FIG> shows the mobile terminal as having various components, but it should be understood that implementing all of the illustrated components is not a requirement. Greater or fewer components may alternatively be implemented.

The elements of the mobile terminal will be described in detail as follows.

The wireless communication unit <NUM> typically includes one or more components allowing radio communication between the mobile terminal <NUM> and a wireless communication system or a network in which the mobile terminal is located. For example, the wireless communication unit may include at least one of a broadcast receiving module <NUM>, a mobile communication module <NUM>, a wireless Internet module <NUM>, a short-range communication module <NUM>, and a location information module <NUM>.

The broadcast receiving module <NUM> receives broadcast signals and/or broadcast associated information from an external broadcast management server (or other network entity) via a broadcast channel.

The broadcast channel may include a satellite channel and/or a terrestrial channel. The broadcast management server may be a server that generates and transmits a broadcast signal and/or broadcast associated information or a server that receives a previously generated broadcast signal and/or broadcast associated information and transmits the same to a terminal. The broadcast signal may include a TV broadcast signal, a radio broadcast signal, a data broadcast signal, and the like. Also, the broadcast signal may further include a broadcast signal combined with a TV or radio broadcast signal.

The broadcast associated information may refer to information associated with a broadcast channel, a broadcast program or a broadcast service provider. The broadcast associated information may also be provided via a mobile communication network and, in this case, the broadcast associated information may be received by the mobile communication module <NUM>.

The broadcast signal may exist in various forms. For example, it may exist in the form of an electronic program guide (EPG) of digital multimedia broadcasting (DMB), electronic service guide (ESG) of digital video broadcast-handheld (DVB-H), and the like.

The broadcast receiving module <NUM> may be configured to receive signals broadcast by using various types of broadcast systems. In particular, the broadcast receiving module <NUM> may receive a digital broadcast by using a digital broadcast system such as multimedia broadcasting-terrestrial (DMB-T), digital multimedia broadcasting-satellite (DMB-S), digital video broadcast-handheld (DVB-H), the data broadcasting system known as media forward link only (MediaFLO®), integrated services digital broadcast-terrestrial (ISDB-T), etc. The broadcast receiving module <NUM> may be configured to be suitable for every broadcast system that provides a broadcast signal as well as the above-mentioned digital broadcast systems.

Broadcast signals and/or broadcast-associated information received via the broadcast receiving module <NUM> may be stored in the memory <NUM> (or anther type of storage medium).

The mobile communication module <NUM> transmits and/or receives radio signals to and/or from at least one of a base station (e.g., access point, Node B, etc.), an external terminal (e.g., other user devices) and a server (or other network entities). Such radio signals may include a voice call signal, a video call signal or various types of data according to text and/or multimedia message transmission and/or reception.

The wireless Internet module <NUM> supports wireless Internet access for the mobile terminal. This module may be internally or externally coupled to the terminal. The wireless Internet access technique implemented may include a WLAN (Wireless LAN) (Wi-Fi), Wibro (Wireless broadband), Wimax (World Interoperability for Microwave Access), HSDPA (High Speed Downlink Packet Access), or the like.

The short-range communication module <NUM> is a module for supporting short range communications. Some examples of short-range communication technology include BluetoothTM, Radio Frequency IDentification (RFID), Infrared Data Association (IrDA), Ultra-WideBand (UWB), ZigBeeTM, and the like.

The location information module <NUM> is a module for checking or acquiring a location (or position) of the mobile terminal. A typical example of the location information module is a GPS (Global Positioning System).

The A/V input unit <NUM> is configured to receive an audio or video signal. The A/V input unit <NUM> may include a camera <NUM> (or other image capture device) and a microphone <NUM> (or other sound pick-up device). The camera <NUM> processes image data of still pictures or video obtained by an image capture device in a video capturing mode or an image capturing mode. The processed image frames may be displayed on a display unit <NUM> (or other visual output device).

The image frames processed by the camera <NUM> may be stored in the memory <NUM> (or other storage medium) or transmitted via the wireless communication unit <NUM>. Two or more cameras <NUM> may be provided according to the configuration of the mobile terminal.

The microphone <NUM> may receive sounds (audible data) via a microphone (or the like) in a phone call mode, a recording mode, a voice recognition mode, and the like, and can process such sounds into audio data. The processed audio (voice) data may be converted for output into a format transmittable to a mobile communication base station (or other network entity) via the mobile communication module <NUM> in case of the phone call mode. The microphone <NUM> may implement various types of noise canceling (or suppression) algorithms to cancel (or suppress) noise or interference generated in the course of receiving and transmitting audio signals.

The user input unit <NUM> (or other user input device) may generate input data from commands entered by a user to control various operations of the mobile terminal. The user input unit <NUM> may include a keypad, a dome switch, a touch pad (e.g., a touch sensitive member that detects changes in resistance, pressure, capacitance, etc. due to being contacted) a jog wheel, a jog switch, and the like.

The sensing unit <NUM> (or other detection means) detects a current status (or state) of the mobile terminal <NUM> such as an opened or closed state of the mobile terminal <NUM>, a location of the mobile terminal <NUM>, the presence or absence of user contact with the mobile terminal <NUM> (i.e., touch inputs), the orientation of the mobile terminal <NUM>, an acceleration or deceleration movement and direction of the mobile terminal <NUM>, etc., and generates commands or signals for controlling the operation of the mobile terminal <NUM>. For example, when the mobile terminal <NUM> is implemented as a slide type mobile phone, the sensing unit <NUM> may sense whether the slide phone is opened or closed. In addition, the sensing unit <NUM> can detect whether or not the power supply unit <NUM> supplies power or whether or not the interface unit <NUM> is coupled with an external device. The sensing unit <NUM> may include a proximity sensor <NUM>.

The output unit <NUM> is configured to provide outputs in a visual, audible, and/or tactile manner (e.g., audio signal, video signal, alarm signal, vibration signal, etc.). The output unit <NUM> may include the display unit <NUM>, an audio output module <NUM>, an alarm unit <NUM>, a haptic module, and the like.

The display unit <NUM> may display (output) information processed in the mobile terminal <NUM>. For example, when the mobile terminal <NUM> is in a phone call mode, the display unit <NUM> may display a User Interface (UI) or a Graphic User Interface (GUI) associated with a call or other communication (such as text messaging, multimedia file downloading, etc.). When the mobile terminal <NUM> is in a video call mode or image capturing mode, the display unit <NUM> may display a captured image and/or received image, a UI or GUI that shows videos or images and functions related thereto, and the like.

The display unit <NUM> may include at least one of a Liquid Crystal Display (LCD), a Thin Film Transistor-LCD (TFT-LCD), an Organic Light Emitting Diode (OLED) display, a flexible display, a three-dimensional (3D) display, or the like.

Some of them may be configured to be transparent or light-transmissive to allow viewing of the exterior, which may be called transparent displays. A typical transparent display may be, for example, a TOLED (Transparent Organic Light Emitting Diode) display, or the like. Through such configuration, the user can view an object positioned at the rear side of the terminal body through the region occupied by the display unit <NUM> of the terminal body.

The mobile terminal <NUM> may include two or more display units (or other display means) according to its particular desired embodiment. For example, a plurality of display units may be separately or integrally disposed on one surface of the mobile terminal, or may be separately disposed on mutually different surfaces.

Meanwhile, when the display unit <NUM> and a sensor (referred to as a 'touch sensor', hereinafter) for detecting a touch operation are overlaid in a layered manner to form a touch screen, the display unit <NUM> may function as both an input device and an output device. The touch sensor may have a form of a touch film, a touch sheet, a touch pad, and the like.

The touch sensor may be configured to convert pressure applied to a particular portion of the display unit <NUM> or a change in the capacitance or the like generated at a particular portion of the display unit <NUM> into an electrical input signal. The touch sensor may be configured to detect the pressure when a touch is applied, as well as the touched position and area.

When there is a touch input with respect to the touch sensor, a corresponding signal (signals) are transmitted to a touch controller. The touch controller processes the signals and transmits corresponding data to the controller <NUM>. Accordingly, the controller <NUM> may recognize which portion of the display unit <NUM> has been touched.

With reference to <FIG>, a proximity sensor <NUM> may be disposed within or near the touch screen. The proximity sensor <NUM> is a sensor for detecting the presence or absence of an object relative to a certain detection surface or an object that exists nearby by using the force of electromagnetism or infrared rays without a physical contact. Thus, the proximity sensor <NUM> has a considerably longer life span compared with a contact type sensor, and it can be utilized for various purposes.

Examples of the proximity sensor <NUM> may include a transmission type photoelectric sensor, a direct reflection type photoelectric sensor, a mirror-reflection type photo sensor, an RF oscillation type proximity sensor, a capacitance type proximity sensor, a magnetic proximity sensor, an infrared proximity sensor, and the like. In case where the touch screen is the capacitance type, proximity of the pointer is detected by a change in electric field according to the proximity of the pointer. In this case, the touch screen (touch sensor) may be classified as a proximity sensor.

In the following description, for the sake of brevity, recognition of the pointer positioned to be close to the touch screen will be called a 'proximity touch', while recognition of actual contacting of the pointer on the touch screen will be called a 'contact touch'. In this case, when the pointer is in the state of the proximity touch, it means that the pointer is positioned to correspond vertically to the touch screen.

By employing the proximity sensor <NUM>, a proximity touch and a proximity touch pattern (e.g., a proximity touch distance, a proximity touch speed, a proximity touch time, a proximity touch position, a proximity touch movement state, or the like) can be detected, and information corresponding to the detected proximity touch operation and the proximity touch pattern can be outputted to the touch screen.

The audio output module <NUM> may convert and output as sound audio data received from the wireless communication unit <NUM> or stored in the memory <NUM> in a call signal reception mode, a call mode, a record mode, a voice recognition mode, a broadcast reception mode, and the like. Also, the audio output module <NUM> may provide audible outputs related to a particular function performed by the mobile terminal <NUM> (e.g., a call signal reception sound, a message reception sound, etc.). The audio output module <NUM> may include a speaker, a buzzer, or other sound generating device.

The alarm unit <NUM> (or other type of user notification means) may provide outputs to inform about the occurrence of an event of the mobile terminal <NUM>. Typical events may include call reception, message reception, key signal inputs, a touch input etc. In addition to audio or video outputs, the alarm unit <NUM> may provide outputs in a different manner to inform about the occurrence of an event. For example, the alarm unit <NUM> may provide an output in the form of vibrations (or other tactile or sensible outputs). When a call, a message, or some other incoming communication is received, the alarm unit <NUM> may provide tactile outputs (i.e., vibrations) to inform the user thereof. By providing such tactile outputs, the user can recognize the occurrence of various events even if his mobile phone is in the user's pocket. Outputs informing about the occurrence of an event may be also provided via the display unit <NUM> or the audio output module <NUM>. The display unit <NUM> and the audio output module <NUM> may be classified as a part of the alarm unit <NUM>.

A haptic module <NUM> generates various tactile effects the user may feel. A typical example of the tactile effects generated by the haptic module <NUM> is vibration. The strength and pattern of the haptic module <NUM> can be controlled. For example, different vibrations may be combined to be outputted or sequentially outputted.

Besides vibration, the haptic module <NUM> may generate various other tactile effects such as an effect by stimulation such as a pin arrangement vertically moving with respect to a contact skin, a spray force or suction force of air through a jet orifice or a suction opening, a contact on the skin, a contact of an electrode, electrostatic force, etc., an effect by reproducing the sense of cold and warmth using an element that can absorb or generate heat.

The haptic module <NUM> may be implemented to allow the user to feel a tactile effect through a muscle sensation such as fingers or arm of the user, as well as transferring the tactile effect through a direct contact. Two or more haptic modules <NUM> may be provided according to the configuration of the mobile terminal <NUM>.

The memory <NUM> may store software programs used for the processing and controlling operations performed by the controller <NUM>, or may temporarily store data (e.g., a phonebook, messages, still images, video, etc.) that are inputted or outputted. In addition, the memory <NUM> may store data regarding various patterns of vibrations and audio signals outputted when a touch is inputted to the touch screen.

The memory <NUM> may include at least one type of storage medium including a Flash memory, a hard disk, a multimedia card micro type, a card-type memory (e.g., SD or DX memory, etc), a Random Access Memory (RAM), a Static Random Access Memory (SRAM), a Read-Only Memory (ROM), an Electrically Erasable Programmable Read-Only Memory (EEPROM), a Programmable Read-Only memory (PROM), a magnetic memory, a magnetic disk, and an optical disk. Also, the mobile terminal <NUM> may be operated in relation to a web storage device that performs the storage function of the memory <NUM> over the Internet.

The interface unit <NUM> serves as an interface with every external device connected with the mobile terminal <NUM>. For example, the external devices may transmit data to an external device, receives and transmits power to each element of the mobile terminal <NUM>, or transmits internal data of the mobile terminal <NUM> to an external device. For example, the interface unit <NUM> may include wired or wireless headset ports, external power supply ports, wired or wireless data ports, memory card ports, ports for connecting a device having an identification module, audio input/output (I/O) ports, video I/O ports, earphone ports, or the like.

The identification module may be a chip that stores various types of information for authenticating the authority of using the mobile terminal <NUM> and may include a user identity module (UIM), a subscriber identity module (SIM) a universal subscriber identity module (USIM), and the like. In addition, the device having the identification module (referred to as 'identifying device', hereinafter) may take the form of a smart card. Accordingly, the identifying device may be connected with the terminal <NUM> via a port.

When the mobile terminal <NUM> is connected with an external cradle, the interface unit <NUM> may serve as a passage to allow power from the cradle to be supplied therethrough to the mobile terminal <NUM> or may serve as a passage to allow various command signals inputted by the user from the cradle to be transferred to the mobile terminal therethrough. Various command signals or power inputted from the cradle may operate as signals for recognizing that the mobile terminal is properly mounted on the cradle.

The controller <NUM> typically controls the general operations of the mobile terminal. For example, the controller <NUM> performs controlling and processing associated with voice calls, data communications, video calls, and the like. The controller <NUM> may include a multimedia module <NUM> for reproducing multimedia data. The multimedia module <NUM> may be configured within the controller <NUM> or may be configured to be separated from the controller <NUM>.

The controller <NUM> may perform a pattern recognition processing to recognize a handwriting input or a picture drawing input performed on the touch screen as characters or images, respectively.

The power supply unit <NUM> receives external power or internal power and supplies appropriate power required for operating respective elements and components under the control of the controller <NUM>.

Various embodiments described herein may be implemented in a computer-readable or its similar medium using, for example, software, hardware, or any combination thereof.

For hardware implementation, the embodiments described herein may be implemented by using at least one of application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors, controllers, micro-controllers, microprocessors, electronic units designed to perform the functions described herein. In some cases, such embodiments may be implemented by the controller <NUM> itself.

For software implementation, the embodiments such as procedures or functions described herein may be implemented by separate software modules. Each software module may perform one or more functions or operations described herein. Software codes can be implemented by a software application written in any suitable programming language. The software codes may be stored in the memory <NUM> and executed by the controller <NUM>.

<FIG> is a front perspective view of the mobile terminal according to an exemplary embodiment of the present invention.

The mobile terminal includes a bar type terminal body <NUM>. Without being limited thereto, the present invention can be also applicable to a slide type mobile terminal, a folder type mobile terminal, a swing type mobile terminal, a swivel type mobile terminal and the like, including two or more bodies.

The terminal body includes a case (or casing, housing, cover, etc.) constituting the external appearance of the terminal body. In the present exemplary embodiment, the case may be divided into a front case <NUM> and a rear case <NUM>. Various electronic components are installed in the space between the front case <NUM> and the rear case <NUM>. One or more intermediate cases may be additionally disposed between the front case <NUM> and the rear case <NUM>.

The cases may be formed by injection-molding a synthetic resin or may be made of a metallic material such as stainless steel (STS) or titanium (Ti), etc..

The display unit <NUM>, the audio output module <NUM>, camera <NUM>, and the user input unit <NUM> (<NUM>, <NUM>), the microphone <NUM>, the interface <NUM>, and the like, may be located on the terminal body, namely, mainly, on the front case <NUM>.

The display unit <NUM> occupies the most portion of the front surface of the front case <NUM>. The audio output unit <NUM> and the camera <NUM> are disposed at a region adjacent to one of both end portions of the display unit <NUM>, and the user input unit <NUM> and the microphone <NUM> are disposed at a region adjacent to another of the both end portions. The user input unit <NUM>, the interface <NUM>, and the like, may be disposed at the sides of the front case <NUM> and the rear case <NUM>.

The user input unit <NUM> is manipulated to receive commands for controlling the operation of the mobile terminal <NUM>, and may include a plurality of manipulation units <NUM> and <NUM>. The manipulation units <NUM> and <NUM> may be generally called a manipulating portion, and they can employ any method so long as they can be manipulated in a tactile manner by the user.

Content inputted by the first and second manipulation units <NUM> and <NUM> may be variably set. For example, the first manipulation unit <NUM> receives commands such as start, end, scroll, or the like, and the second manipulation unit <NUM> may receive commands such as adjustment of size of a sound outputted from the audio output unit <NUM> or conversion to a touch recognition mode of the display unit <NUM>.

<FIG> is a rear perspective view of the mobile terminal illustrated in <FIG> according to an exemplary embodiment of the present invention.

With reference to <FIG>, a camera <NUM>' may additionally be disposed on a rear surface of the terminal body, namely, on the rear case <NUM>. The camera <NUM>' may have an image capture direction which is substantially opposite to that of the camera <NUM> (See <FIG>), and may support a different number of pixels (i.e., have a different resolution) than the camera <NUM>.

For example, camera <NUM> may operate with a relatively lower resolution to capture an image(s) of the user's face and immediately transmit such image(s) to another party in real-time during video call communication or the like. Meanwhile the camera <NUM>' may operate with a relatively higher resolution to capture images of general objects with high picture quality, which may not require immediately transmission in real time. The cameras <NUM> and <NUM>' may be installed on the terminal such that they are rotated or popped up.

A flash <NUM> and a mirror <NUM>, may be additionally disposed adjacent to the camera <NUM>'. When an image of the subject is captured with the camera <NUM>', the flash <NUM> illuminates the subject. The mirror <NUM> allows the user to see himself when he wants to capture his own image (i.e., self-image capturing) by using the camera <NUM>' of the second body <NUM>.

An audio output unit <NUM>' may be additionally disposed on the rear surface of the terminal body. The audio output unit <NUM>' may implement a stereoscopic function along with the audio output unit <NUM> (See <FIG>), and may be used for implementing a speaker phone mode during call communication.

A broadcast signal receiving antenna <NUM> may be disposed at the side of the terminal body in addition to an antenna that supports mobile communications. The antenna <NUM> forming a portion of the broadcast reception module <NUM> (in <FIG>) may be installed to be protracted.

A power supply unit <NUM> for supplying power to the mobile terminal <NUM> may be mounted on the terminal body <NUM>. The power supply unit <NUM> may be installed in the terminal body or may be directly detached from the outside of the terminal body.

A touch pad for detecting a touch may be additionally mounted on the rear case <NUM>. Such touch pad may be configured to be light-transmissive like the display unit <NUM>. In this case, when the display unit <NUM> is configured to output visual information from both sides thereof, the visual information can be recognized through the touch pad <NUM>. Information outputted to the both sides of the display unit1 <NUM> may be all controlled by the touch pad <NUM>. Alternatively, a display may be additionally mounted on the touch pad <NUM>, and a touch screen may be disposed on the rear case <NUM>.

The touch pad <NUM> is operated in relation to the display unit <NUM> of the front case <NUM>. The touch pad <NUM> may be disposed to be parallel to the rear side of the display unit <NUM>. The touch pad <NUM> may have the same size or smaller than the display unit <NUM>.

A control method that may be implemented in the terminal configured as described above according to exemplary embodiments of the present invention will now be described with reference to the accompanying drawings. The exemplary embodiments to be described may be used alone or may be combined to be used. Also, the exemplary embodiments to be described may be combined with a user interface (UI) so as to be used.

<FIG> shows a main window, <FIG> shows sub-windows, <FIG> are views showing a main window and a sub-window actually displayed on a display unit according to an exemplary embodiment of the present invention.

According to an exemplary embodiment of the present invention, the display unit may have at least two layers. In an exemplary embodiment of the present invention, a main window may refer to a window of an upper layer, and a sub-window may refer to a window of a lower layer than that of the main window. Here, the window refers to a manipulated screen of the mobile terminal or a single screen displaying input and output information as an application is executed. The window may occupy the entire screen of the display unit or a portion of the entire screen.

Individual applications or the same application may be executed on each window. Functions that can be executed on each of the windows may include various applications such as a voice or video call, a text message reception or origination, text chatting, sound resource reproducing, playing games, the mobile Internet, a DMB, navigation, an E-book reader, a camera, a phone book, a document creator, and the like.

When the mobile terminal is in a standby mode (namely, the mobile terminal is in a state in which a particular application is not executed and waits for an event occurrence or a user input), or when one application is being executed, information is displayed through only a main window occupying the entire screen.

The size of the main window <NUM> may be changed according to a user input. For example, horizontal or vertical bars <NUM> and <NUM> are displayed at edges of the main window, and when the user drags the bars through a touch screen, the controller provides control to resize the main window according to the user's drag position. Or, an indicator <NUM> may be displayed at the corner of the main window <NUM> to allow the user to drag it to change the size of the main window. When the main window is resized, the controller newly outputs the information, which has been output through the main window, according to the size of the changed main window.

When two or more applications are executed (including execution of one application and the occurrence of one event), one is output through the main window and the other is output through a sub-window. Two or more sub-windows may be provided according to the number of executed applications. As for the sub-windows, the entire screen of a lower layer may be divided into sub-window (<NUM>, <NUM>, <NUM>) and simultaneously displayed, regardless of the relationship between the upper and lower layers.

As discussed above, the mobile terminal according to an exemplary embodiment of the present invention may be configured to include a display buffer (not shown) for recording and storing image data displayed on the display unit <NUM> such that the main window and at least one lower sub-window can be displayed, and a screen controller (not shown) configured to output image data to the display buffer to allow a corresponding screen image to be displayed on the display unit <NUM> and control the display buffer. The display buffer and the screen controller may be implemented to be included in the display unit <NUM>. Here, the screen controller determines which screen image is to be displayed on the display unit <NUM> under the control of the controller <NUM> and control dividing or disposing of a screen window to allow a main window and/or sub-window to be output to the display unit <NUM>. Also, one or more display buffers according to an exemplary embodiment of the present invention are controlled, and in this case, image data is output to the display buffer or updated according to a layer or position of a window to be output.

With reference to <FIG>, only a portion of a sub-window of a lower layer which is not covered by the main window of an upper layer is displayed on the display unit. Also, the main window of the upper layer is not covered by the sub-window of the lower layer. Thus, by variably regulating the size of the main window, the main window and a portion of the sub-window which does not overlap with the main window can be displayed together.

<FIG> shows a case in which the size of the main window is regulated to allow two sub-windows to be displayed. <FIG> shows a case in which one sub-window is displayed. <FIG> shows a case in which one sub-window and portions of two sub-window are displayed. <FIG> shows a case in which the main window is reduced to its maximum level such that the main window is not displayed and three sub-windows are displayed. With reference to <FIG>, the name <NUM>, <NUM>, and <NUM> of the applications being executed in each of the sub-windows are displayed at a lower portion of each of the sub-windows, and only the names <NUM> and <NUM> of the executed applications or the name <NUM> and the sub-window <NUM> may be displayed together by adjusting the size of the main window.

The size of the main window may be selected from among certain sizes as illustrated in <FIG>, or may be successively changed according to a user input regardless of the disposition of the sub-window.

<FIG> are views illustrating the disposition of a plurality of sub-windows.

The size of each of the sub-windows may vary depending on the number of the sub-windows, or may be fixed. With reference to <FIG>, when there are four sub-windows, each sub-window has a size obtained by quartering the screen size of the overall display unit. If there are two sub-windows, each sub-window would have a size obtained by halving the screen size of the overall display unit.

Differently, with reference to <FIG>, each sub-window may have a sized size regardless of the number of the sub-windows. For example, each sub-window may have a size obtained by trisecting the screen size of the overall display unit. <FIG> shows a case in which two sub-windows are disposed and a far-right area is empty. <FIG> show a case in which four sub-windows are disposed. The sub-windows displayed on the display unit can be interchanged by shifting the sub-windows disposed in a row according to a user input. In case of <FIG>, as the user drags the sub-windows to the left, sub-windows sub2, sub3, and sub4 are displayed (of course, they are displayed only when not covered by the main window. Of course, the array of sub-window may be shifted to the far right to display the sub-window sub1, while the other remaining space may remain empty (namely, the sub-windows are disposed in a row), or the sub-windows sub3 and sub4 (namely, the sub-windows may be disposed in a circular form).

<FIG> are views showing sub-windows and the main window described above with reference to <FIG>. <FIG> shows a sub-window disposed like that of <FIG> and a main window resized to have a two-thirds size. As illustrated, only the sub-window sub4 is shown, while the sub-windows sub2 and sub3 are not shown as being covered by the main window. By dragging the displayed sub-window area, the user is able to shift the disposed sub-windows and change the resultantly displayed sub-windows.

With reference to <FIG>, indicators <NUM>, <NUM>, and <NUM> indicating sub-windows covered by the main window and an indicator <NUM> of a sub-window, which is positioned at a right side of the displayed sub-window and not displayed, may be displayed.

With reference to <FIG>, the sub-windows are generated in the occurrence of an event such as an execution of an application by the user, a call signal reception, a text message reception, alarming while an application is being executed on a main window, and when the application executed according to a user's input or the like is terminated, the sub-windows become extinct. The plurality of sub-windows may be disposed in a row according to the sub-window generation order, to finally displayed order, the frequently displayed order, the order set by the user, and the like. For example, the first generated sub-window sub1 may be disposed at the far left, and the most recently generated sub-window sub4 may be disposed at the far right.

For example, a virtual sub-window (new) <NUM> to be newly generated may be positioned at a right side of the most recently generated sub-window. For example, in a state of being displayed as shown in <FIG>, when the user drags the sub-window to the left, the new sub-window sub5 <NUM> is generated. A standby screen image, a manipulated screen image, an application list available for multitasking, and the like, may be displayed on the sub-window sub5, without executing a particular application. When the user simply drags the sub-window to the right without any other manipulation, the sub-window sub5 may become extinct. Or, as shown in <FIG>, it may be constantly displayed (<NUM>) like the already generated sub-windows.

<FIG> is a flow chart illustrating the process of controlling a main window and a sub-window when an event occurs while an application is being executed according to an exemplary embodiment of the present invention.

When the mobile terminal is turned on, a standby mode screen image is displayed on the main window of the display unit of the mobile terminal (step S100). As described above, the standby mode refers to a state in which various function keys or menu keys are displayed and a user's input or an event occurrence awaits.

When the user selects an application (App0) desired to be executed by using the menu key, or the like, displayed on the display unit (step S110), the controller loads the application selected by the user and executes it, and provides control to output information processed by the application through a main window of the display unit (step S120).

When the controller detects an occurrence of an event in the course of executing the application App0 (step S130), an indicator indicating the occurrence of the event, or the like, is displayed (step S140). The event may be a call signal reception, a text message reception, alarming, and the like, and the indicator may be an icon, a character box, and the like, indicating the corresponding event as generated.

With the indicator displayed, a sub-window with respect to the generated event is generated (step S150). The generated sub-window is not displayed until before a user's input, and the main window is maintained to be the same as before. Information regarding the event may be stored in the display buffer for the sub-window, or an application related to an event is executed and information processed and outputted accordingly may be stored in the display buffer for the sub-window.

In order to check the generated event, the user reduces the main window by dragging the bar at the edge of the main window or the indicator (step S160).

When the main window having the reduced size is input by the user, the controller provides control to continuously output the information, which is output from the application App0, through the main window having the size changed according to the size of the input main window (step S170).

At the same time, a sub-window not covered by the main window as the main window is reduced in size is displayed on the display unit, and event information, or the like, is displayed through the sub-window (step S180).

<FIG> are views showing main windows and sub-windows displaying an event occurring while an application is being executed as described with reference to <FIG>.

With reference to <FIG>, information processed by a certain application App0 is output through the main window occupying the entire screen of the display unit.

With reference to <FIG>, when a text message is received while the application App0 is executed, an indicator <NUM> having a shape of an icon indicating the text message reception is displayed along with a signal sound indicating the text message reception or without a signal sound. The indicator may blink until such time as the user checks it or for a certain period of time. Or, the indicator may serve as an indicator for regulating the size of the main window. In order to check the received text message, the user drags the indicator to the left.

With reference to <FIG>, as the user drags the indicator, the size of the main window is reduced and a sub-window <NUM>, which has been covered by the main window, is displayed. If there is no sub-window covered by the main window, the indicator may not be displayed or a meaningless indicator <NUM> may be displayed.

When the user checks the text message, the user may touch an OK key <NUM> to close the sub-window <NUM> on which the text message is displayed. When there is no any other sub-window, the main window is returned to an entire screen or a sub-window displaying a screen image of a standby mode may be displayed.

With reference to <FIG>, when a reply (<NUM>) key of a reception message checking sub-window <NUM> is touched, a sub-window <NUM> for sending a text message is displayed. The displayed information may be simply changed from the sub-window <NUM> for checking a reception message as shown in <FIG>, but a sub-window <NUM> different from the sub-window for checking a reception message may be generated. As described above, the same application may be executed in two or more windows. While the sub-window <NUM> for originating a message is generated, the sub-window <NUM> previously displayed for checking the reception message is shifted to the left and covered by the main window, not being displayed. An indicator <NUM> for indicating it may be displayed on the main window.

With reference to <FIG>, when the user drags the indicator <NUM> to the left, the sub-window <NUM> for checking a reception message, which has been covered, is displayed. The user may create a text message and send it, while viewing the received text message.

With reference to <FIG>, the user may drag the indicator <NUM> displayed in the main window in the course of checking and sending the text message (or the user may drag the bar displayed at the edge of the main window or simply drag the edge of the main window) to cover a portion of a sub-window, one sub-window, or the entire sub-windows. The covered sub-window are simply not shown, rather than being closed, and an application being executed in the sub-window is not affected. Indicators <NUM> and <NUM> indicating the applications executed by the covered sub-windows may be displayed on the main window occupying the entire screen.

<FIG> is a flow chart illustrating the process of controlling the main window and the sub-window when a user wants to execute another application while one application is being executed according to an exemplary embodiment of the present invention.

When the mobile terminal is turned on, a standby mode screen image is displayed on the main window of the display unit (step S200). As described above, the standby mode refers to a state in which various function keys or menu keys are displayed and a user's input or an event occurrence awaits.

When the user selects an application (App0) desired to be executed by using the menu key, or the like, displayed on the display unit (step S210), the controller loads the application selected by the user and executes it, and provides control to output information processed by the application through a main window of the display unit (step S220).

When the user wants to execute another application together while executing the application App0, the user drags the bar or the indicator at the edge of the main window to reduce the main window (step S230).

When the main window having the reduced size is input by the user, the controller provides control to continuously output the information, which is output from the application App0, through the main window having the size changed according to the size of the input main window (step S240).

Also, because there is no already generated sub-window, a sub-window is newly generated and displayed according to the reduction in size of the main window (step S250). Or, when the main window is reduced, an empty space is displayed, and as described above, when the user drags the empty space to the left, a new sub-window can be generated and displayed.

A standby mode screen image for displaying a list of applications to be executed or various function keys or menu keys may be displayed on the newly generated sub-window (step S260).

The user selects an application (App1) desired to be executed through the standby screen of the sub-window (step S270). The controller loads and executes the application selected by the user, and provides control to output information processed by the application through the sub-window of the display unit (step S280).

When the application (App1) executed on the sub-window according to the user input, or the like, is terminated, the controller closes the sub-window (step S300). Accordingly, the sub-window becomes extinct, and the main window can be enlarged to the entire screen. When the user enlarges the main window without terminating the application (App1) (step S310), the sub-window is maintained, rather than becoming extinct, and the information processed by the application App0 is output through the main window occupying the entire screen (step S320).

<FIG> show main window and sub-windows displayed when the user wants to execute another application while one application is being executed as described with reference to <FIG>.

With reference to <FIG>, information processed by a certain application (App0) is output through the main window occupying the entire screen of the mobile terminal (<FIG>). When the user wants to execute another application together in the course of executing the application App0, the user drags a bar or an indicator <NUM> at the edge of the main window to reduce the main window. The indicator may have a form of an icon indicating that a sub-window is newly generated.

With reference to <FIG>, as the user reduces the main window, a sub-window <NUM> is displayed. A list of application that can be executable may be displayed on the newly generated sub-window <NUM>.

With reference to <FIG>, when the user selects an application from the application list, the controller executes the selected application (App1) and outputs information through the sub-window <NUM>. When the user wants to execute another application while the application App1 is being executed through the sub-window <NUM>, the user drags the sub-window to the left as described above.

With reference to <FIG>, when there is a drag input in the course of executing the application App1 in the sub-window, a new sub-window <NUM> is generated, and a standby screen image is displayed on the sub-window <NUM>. The sub-window <NUM> on which the application App1 is being executed is shifted to the left and covered by the main window, and an indicator <NUM> indicating it is displayed on the main window. Of course, the user may further reduce the main window to the left to display both of the sub-windows <NUM> and <NUM>.

With reference to <FIG> and <FIG>, when an event occurs while the application App1 is being executed on the sub-window <NUM>, an indicator <NUM> indicating the occurrence of the event may be displayed and blink. When the user drags the indicator or the sub-window to the left, the sub-window <NUM> on which the application App1 is being executed is shifted to the left and covered, and a sub-window <NUM> displaying information regarding the generated event is generated.

<FIG> is a flow chart illustrating the process of displaying a sub-window when a plurality of applications are executed through main windows and sub-windows.

In a state in which information output from the application App0 through the main window occupying the entire screen is displayed (step S400), the user drags the bar or the indicator of the main window to reduce the main window in order to check a sub-window (step S410).

The controller reduces the main window and displays the output information of the application App0 through the reduced main window (step S420).

Also, the controller displays a sub-window (n) in a space generated according to the size reduction in the main window (step S430). As described above, one or more sub-windows may be displayed according to the size of the reduced main window. The displayed sub-window may be the most recently generated sub-window, the most recently displayed sub-window, and the like.

With the sub-window displayed (step S430), when the user want so change the sub-window being displayed, for example, the user may drag the displayed sub-window to the left or to the right to shift the sub-window(s) (step S440). Or the user may change the displayed sub-window by clicking or dragging the indicator with respect to each sub-window displayed on the main window or the sub-window.

When a drag is inputted in a first direction, e.g., when a first drag is inputted by the user, a sub-window (n-<NUM>), which has been generated before the displayed sub-window was generated, is displayed (step S450), and when a drag is inputted in a second direction, e.g., when a left drag is inputted, a later generated sub-window (n+<NUM>) may be displayed (step S460). When there is no later generated sub-window, a new sub-window is displayed and a standby mode screen image may be displayed.

<FIG> and <FIG> are views showing changing of applications output through main window and sub-windows. When two or more applications are being executed, information processed by the first executed application may be output through a main window, and the subsequently executed application may be output through a sub-window. When the user wants to output the application, which is being executed on the sub-window, through the main window, or vice versa, the application executed on the main window may be changed according to a user input.

With reference to <FIG>, with the main window and the sub-window displayed, when the user drags the sub-window sub3 to the main window or drags the name (App1) of the application executed in the sub-window to the main window, the application being executed in the main window is changed from the application App0 to the application App1 or App3 and the application App0 is executed in the sub-window.

With reference to <FIG>, the main window occupies the entire screen and indicators of applications executed in sub-windows covered by the main window are displayed on the main window. In this state, when the user drags one (App1) of the displayed indicators to the main window or double clicks the application App1, the application being executed in the main window is changed from the application App0 to the application App1, and the application App0 is executed in the sub-window.

In the above description, the main window and the sub-windows are positioned at upper and lower layers, respectively, and the sub-window of the lower layer not covered by the main window is displayed according to resizing of the main window, but the present invention is not limited thereto. The present invention can be applicable to any case in which displaying of a certain application through the main window is maintained and an event or a different application generated according to a user control can be displayed (on a sub-window) simultaneously.

For example, regardless of the relationship of upper and lower layers of a main window and a sub-window, the entire screen may be divided (into a main window display area and a sub-window display area) according to a user's resizing input to simultaneously display a main window and a sub-window.

Also, when a certain input (e.g., a touch input of an indicator) is detected without resizing a main window (so the main window occupies the entire screen), a sub-window may be displayed in the form of a picture-in-picture (PIP) on the main window. The divided sub-window display area or the PIP correspond to a portion not covered by the main window of the upper layer as described above, so the methods as described above with reference to <FIG> can be applicable in the same manner. Besides, the present invention can be applicable to various cases in which two or more windows are displayed on the same screen.

Hereinafter, a method of simply using information, which is input or output or processed in each application, by a different application in a multitasking environment in which two or more windows are displayed on the same window will now be described in detail.

<FIG> are views showing transmitting and receiving a message through a sub-window while a Web browser is being driven through a main window according to an exemplary embodiment of the present invention.

When the user drives a Web browser of the mobile terminal, the Web browser is displayed through a main window occupying the entire screen. When the user wants to send a particular Web page to a counterpart terminal by using a text message service, and the like, the text message creation application is driven and displayed on a sub-window as described above (See <FIG>).

When a certain signal is input, the controller <NUM> inputs information processed by the application executed in the main window, namely, processed by the Web browser, to the application executed in the sub-window, namely, to the text message creation application (See <FIG>).

The certain signal may be a signal of dragging a Web page being displayed on the main window and dropping it to the sub-window on which the message creation application is being executed.

The information processed by the Web browser may be an Internet access address such as a URL related to the Web page being currently displayed, image information obtained by converting the currently output Web page into an image format such as a screen capture, or the like.

When the information is input to the text message creation application of the sub-window, the received URL and/or an image of the Web page is displayed on a text message creation window, and a text message, a phone number of a counterpart, and the like, are received from the user and the URL information and/or Web page image information to the counterpart terminal.

Upon receiving the message including the URL information and/or image information, the terminal discriminately displays the URL information and/or image information of the message (See <FIG>). When the user selects the displayed URL information and/or image information through a touch or the like, the controller <NUM> detects it and drives the Web browser to access the received corresponding Web page and display it on the main window or the sub-window (See <FIG>).

<FIG> are views showing transmitting and receiving a message through a sub-window while a navigation is being executed through a main window according to an exemplary embodiment of the present invention.

When the user drives a navigation of the mobile terminal, a map is displayed through a main window occupying the entire screen. When the user wants to transmit information regarding the currently displayed map, the user's current location, a destination, a movement path, and the like, by using a text message service or the like to the counterpart terminal, the user drives the text message creation application and displays it on a sub-window (See <FIG>).

When a certain signal is input, the controller <NUM> input an application executed in the main window, namely, information process by the navigation, to the application being executed in the sub-window, namely, to the text message creation application (See <FIG>).

The certain signal may be a signal of dragging the map being displayed on the main window and dropping it to the sub-window on which the text message creation application is executed, by the user.

The information processed by the navigation may refer to coordinate information of the map currently displayed, the location information regarding the user's current location, destination, and the like, movement path information, vicinity area information, and/or image information obtained by converting the map currently displayed on the main window into an image format, or the like through a screen capture, or the like.

When the information is inputted to the text message creation application of the sub-window, the coordinate information, the location information, the movement path information, the vicinity area information and/or image information as received is displayed on a text message creation window, and a text message, a phone number of a counterpart, and the like, are received from the user and the information is transmitted to the counterpart terminal.

Upon receiving the message including the information, the terminal discriminately displays the coordinate information, the location information, the movement path information, the vicinity area information and/or image information of the message (See <FIG>). When the user selects the displayed location information, and the like, through a touch, or the like, the controller <NUM> detects it, drives the navigation, and displays the map of a point related to the received corresponding information on the main window or the sub-window. The user's current location, destination, a movement path, vicinity area information, and the like, may be displayed on the map according to the received information.

<FIG> are views showing transmitting and receiving a message through a sub-window while a broadcast program is being viewed through a main window according to an exemplary embodiment of the present invention.

When the user drives a broadcast view application or various video reproducing application of the mobile terminal, a video such as a broadcast, or the like, is displayed through a main window occupying the entire screen. When the user wants to transmit information regarding the currently displayed video by using a text message service or the like to the counterpart terminal, the user drives the text message creation application and displays it on a sub-window as described above (See <FIG>).

When a certain signal is input, the controller <NUM> input an application executed in the main window, namely, information process by the broadcast view application, to the application being executed in the sub-window, namely, to the text message creation application (See <FIG>).

The certain signal may be a signal of dragging the video being displayed on the main window and dropping it to the sub-window on which the text message creation application is executed, by the user.

The information processed by the broadcast view application may refer to channel information of a currently reproduced program, title, information regarding a broadcast time, image information captured during the reproducing operation, and the like. In case of the video reproducing application, the information processed by the video reproducing application refer to information regarding a file name of the video being reproduced, a contents title, an access address related to a VOD, and the like, the position of a currently reproduced frame, an image captured during the reproducing operation, and the like.

When the information is input to the text message creation application of the sub-window, the program information and/or image information as received is displayed on a text message creation window, and a text message, a phone number of a counterpart, and the like, are received from the user and the information is transmitted to the counterpart terminal.

Upon receiving the message including the information, the terminal discriminately displays the program information and/or image information of the message (See <FIG>). When the user selects the displayed program information, and the like, through a touch, or the like, the controller <NUM> detects it, drives the broadcast view application or the video reproducing application and reproduces a program or a video related to the received corresponding information. When frame information of a particular position of the video is included to be received, the reproducing may be started from the corresponding frame (See <FIG>).

In the above embodiment, the Web browser, navigation, broadcast view application or video reproducing application, the message creation application, and the like, have been described, but the present invention is not limited thereto. For example, an application that is able to exchange information simultaneously executed and processed may include a camera-related application, a voice/video call, text/video chatting, an E-book reader, a document editor, various games, a phone book, and the like.

Information delivered from one application (e.g., which is displayed through a main window) being executed to another application (e.g., which is displayed through a sub-window) being executed may be image information obtained by capturing the main window.

Also, the delivered information may be particular information which is input/output or processed according to an executed application. For example, in case of a camera-related application, the delivered information may be an image captured by the camera or a preview image. In case of the E-book reader, the title or author of an E-book being currently displayed, a page or a sentence being displayed, or E-book file information being displayed. In case of a phone book-related application, the delivered information may be information such as a name, a phone number, an e-mail, an address, an image, and the like, selected by the user. As for each information, a certain identifier for identifying the type of each information may be added to the information and then delivered, or the information may be converted into a certain format and then delivered.

In an exemplary embodiment of the present invention, the information delivered between applications may be determined according to the application executed in the main window and/or the sub-window, or information to be delivered may be selected according to a user selection.

In the above description, the message creation application is mainly described as the application executed in the sub-window, but the present invention is not limited thereto. For example, the application which receives information from another application being executed may include a video call, video/text chatting, a document creator, and the like, as well as the text message creation application. The information delivered from the application being executed in the main window may be processed by the application executed in the sub-window. For example, in case of a video call-related application, a received image may be transmitted as a substitute image to a counterpart or various types of information received via a data channel, or the like, may be transmitted to the counterpart.

<FIG> is a flow chart illustrating the process of the exemplary embodiments described with reference to <FIG>.

When an application to be executed is selected by the user, the controller <NUM> drives the application APP1 and displays it through a main window occupying the entire screen (step S510). While the application APP1 is being driven, when an event occurs and a command for resizing the main window is input by the user or when another application APP2 to be executed simultaneously is selected by the user, the controller reduces the main window and displays a sub-window displaying the APP2 (including information or the application related to the generated event) along with the main window (step S520).

In the state in which the main window and the sub-window are simultaneously displayed, when a certain input, for example, a touch input for dragging from the main window to the sub-window is detected, the controller <NUM> inputs the information related to the application APP1, e.g., information processed by the application APP1, information inputted to be processed by the application APP1, information processed by the application APP1 and output, and the like, so that the corresponding information can be processed by the application APP2 (step S540).

The controller <NUM> processes the input information by the application APP2 and performs a certain function according to the application APP2.

In the embodiments of the present disclosure, the above-described method can be implemented as codes that can be read by a processor in a program-recorded medium. The processor-readable medium includes a ROM, a RAM, a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, and the like. The processor-readable medium also includes implementations in the form of carrier waves or signals (e.g., transmission via the Internet).

The mobile terminal according to the embodiments of the present disclosure is not limited in its application of the configurations and methods, but the entirety or a portion of the embodiments can be selectively combined to be configured into various modifications.

The exemplary embodiments of the present disclosure have been described with reference to the accompanying drawings.

The terms used in the present application are merely used to describe particular embodiments, and are not intended to limit the present disclosure.

Claim 1:
A mobile terminal comprising:
a display (<NUM>) configured to display one or more windows;
a controller (<NUM>) configured to:
display a first window on which a first application (APP0) is executed to occupy an entire screen of the display (<NUM>);
display an indicator (<NUM>) to be dragged at the first window;
display a list of applications that can be executable on the mobile terminal;
receive selection of an application from the list of applications to execute the second application (Appl); and
divide the entire screen into two separate areas including a first display area and a second display area to display the first window and a second window (<NUM>); and
resize the first window displaying the first application (APP0) to be reduced and display the second window (<NUM>) displaying the second application (APP1) with the reduced first window,
characterized in that the controller (<NUM>) further configured to:
detect a drag input for dragging from the first window to the second window (<NUM>); and when the first window and the second window are simultaneously displayed; and
input information related to the first application (APP0) to the second application (APP1) to be processed by the second application (APP1) when the touch input for dragging is detected; and
process the input information by the second application (APP1) to perform a certain function according to the second application (APP1),
wherein the input information related to the first application (APP0) that is displayed on the first display area is displayed on the second display area of the second application (APP1) when the drag input is input.