US20130219290A1 - System and method of transmitting data by using widget window - Google Patents

Abstract

A system and method of transmitting data by using a widget window are provided. A method of transmitting, by a first device, a file by using a widget window includes selecting a file stored in the first device, and moving the file to the widget window, when the file is moved to the widget window, displaying a device selection list, and, when at least one device is selected from the device selection list, providing the file to the selected device, wherein the file is provided to the selected device via a second device that is connected with the first device.

Description

CROSS-REFERENCE TO RELATED PATENT APPLICATION
• This application claims the benefit under 35 U.S.C. §119(a) of a Korean patent application filed on Feb. 16, 2012 in the Korean Intellectual Property Office and assigned Serial No. 10-2012-0015892, the entire disclosure of which is hereby incorporated by reference.
BACKGROUND OF THE INVENTION
• 1. Field of the Invention
• The present invention relates to a system and method of transmitting data by using a widget window. More particularly, the present invention relates to a system and method of transmitting data to a device, which is selected by using a widget window, via another device.
• 2. Description of the Related Art
• Recently, contents such as pictures, moving pictures, and the like that are generated by using smart phones have increased dramatically, and as the smart phones have improved functions and office applications that are widely used, there is an increasing need to share data of a Personal Computer (PC) with mobile phones. Also, various services are provided to share data between a PC and a mobile phone by using a PC client, a cloud service, a window searcher, or the like. However, since it is required to use a Universal Serial Bus (USB) cable or to apply an account to a mobile phone and then to configure complicated settings to connect a PC and the mobile phone, a troublesome procedure is required to be performed to share data. Thus, there is a demand for a technology to effectively detect a device by using an address book stored in a mobile phone and transmit data to the detected device via the mobile phone.
SUMMARY OF THE INVENTION
• Aspects of present invention are to address at least the above-mentioned problems and/or disadvantages and to provide at least the advantages described below. Accordingly, an aspect of the present invention is to provide a system and method of effectively selecting a transmission target using a widget window and transmitting data to the selected device.
• Another aspect of the present invention is to provide a system and method of detecting a transmission target using a widget window from an address book stored in a source device and providing data to the transmission target via the source device.
• According to an aspect of the present invention, a method of transmitting, by a first device, a file by using a widget window is provided. The method includes selecting a file stored in the first device and moving the selected file to the widget window, when the selected file is moved to the widget window, displaying a device selection list, and, when at least one device is selected from the device selection list, providing the selected file to the selected device, wherein the selected file is provided to the device via a second device that is connected with the first device.
• The device selection list may include a list to select the second device that is connected with the first device and a list to select a third device that is not connected with the first device.
• When the second device is selected from the device selection list, the operation of providing the selected file may include an operation of providing the selected file to the selected second device.
• When the third device is selected from the device selection list, the method may further include inputting a keyword to the widget window and detecting a device in an address book received from the second device wherein the device corresponds to the input keyword and providing the selected file may include an operation of providing the selected file to the detected device.
• The keyword may include one of tag values, and the tag values may differ from each other according to types of applications installed in devices listed in the address book.
• The first device and the second device may be connected to each other via Wireless Fidelity (Wi-Fi) communication, and the second device may transmit data received from the first device to the detected device via at least one of Third Generation (3G) mobile communication and Fourth Generation (4G) mobile communication.
• The first device may include at least one of a Personal Computer (PC), a tablet PC, and a smart television (TV), and the second device may include a mobile communication terminal.
• The operation of moving the selected file may be performed in a drag and drop manner.
• In accordance with another aspect of the present invention, a first device of transmitting a file by using a widget window is provided. The first device includes a widget window generating unit for displaying a device selection list when a file stored in the first device is moved to the widget window on a screen of the first device, and a data transmitting unit for providing a file to a device selected from the device selection list, wherein the file is provided to the selected device via a second device that is connected with the first device.
• The device selection list may include the second device that is connected with the first device and a third device that is not connected with the first device.
• When the second device is selected from the device selection list, the data transmitting unit may provide the file to the selected second device.
• The first device may further include a detecting unit for detecting a device corresponding to a keyword that is input to the widget window when the third device is selected from the device selection list, and the detecting unit may detect the device in an address book received from the second device, wherein the device corresponds to the keyword.
• The data transmitting unit may provide the file to the detected device via the second device.
• The keyword may include one of tag values, and the tag values may differ from each other according to types of applications that are installed in devices listed in the address book.
• The first device and the second device may be connected to each other via Wireless Fidelity (Wi-Fi) communication and the second device may transmit data received from the first device to the detected device via at least one of Third Generation (3G) mobile communication and Fourth Generation (4G) mobile communication.
• The first device may include at least one of a Personal Computer (PC), a tablet PC, and a smart TV and the second device may include a mobile communication terminal.
• The file may be moved to the widget window in a drag and drop manner.
• According to another aspect of the present invention, a computer-readable recording medium having recorded thereon a program for executing the method, by using a computer, is provided.
• Other aspects, advantages, and salient features of the invention will become apparent to those skilled in the art from the following detailed description, which, taken in conjunction with the annexed drawings, discloses exemplary embodiments of the invention.
BRIEF DESCRIPTION OF THE DRAWINGS
• The above and other aspects, features, and advantages of certain exemplary embodiments of the present invention will be more apparent from the following description taken in conjunction with the accompanying drawings, in which:
• FIG. 1 is a diagram of a device detection system for data transmission according to an exemplary embodiment of the present invention;
• FIG. 2 is a diagram illustrating a structure of a first device according to an exemplary embodiment of the present invention;
• FIG. 3 is a diagram illustrating a structure of a second device according to an exemplary embodiment of the present invention;
• FIG. 4 is a flowchart of a method of transmitting data between devices according to an exemplary embodiment of the present invention;
• FIG. 5 is a flowchart of a method of detecting a device to receive data according to an exemplary embodiment of the present invention;
• FIG. 6 is a flowchart of a method of transmitting data between devices by using a widget window according to an exemplary embodiment of the present invention;
• FIG. 7 is a flowchart of a method of transmitting data between devices by using a widget window according to another exemplary embodiment of the present invention;
• FIG. 8 is a flowchart of a method of receiving and processing caller information of a third device performed by the first device, according to an exemplary embodiment of the present invention;
• FIG. 9 is a flowchart of a method of receiving a captured screen from the second device, performed by the first device, according to an exemplary embodiment of the present invention;
• FIG. 10 is a diagram illustrating a method of performing communication between devices according to an exemplary embodiment of the present invention;
• FIG. 11 illustrates an example of an address book according to an exemplary embodiment of the present invention;
• FIG. 12 illustrates an example of device detection for data transmission by the first device according to an exemplary embodiment of the present invention;
• FIG. 13 illustrates an example of a widget window for displaying a result of device detection according to an exemplary embodiment of the present invention;
• FIG. 14 illustrates an example of file transmission based on a file transmission method that is selected by the first device via a widget window according to an exemplary embodiment of the present invention;
• FIG. 15 illustrates an example of file transmission to a transmission target selected by the first device according to an exemplary embodiment of the present invention;
• FIG. 16 illustrates an example of message transmission by the first device according to an exemplary embodiment of the present invention;
• FIG. 17 illustrates an example in which caller information of the third device is displayed on the first device, and incoming-call connection information regarding whether or not to accept an incoming call from the third device is generated according to an exemplary embodiment of the present invention;
• FIG. 18 illustrates an example in which capture information and additional information are displayed on the first device according to an exemplary embodiment of the present invention; and
• FIG. 19 illustrates an example in which the first device receives and outputs content that is being executed in the second device according to an exemplary embodiment of the present invention.
• The same reference numerals are used to represent the same elements throughout the drawings.
DETAILED DESCRIPTION OF THE INVENTION
• The following description with reference to the accompanying drawings is provided to assist in a comprehensive understanding of exemplary embodiments of the invention as defined by the claims and their equivalents. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the invention. In addition, descriptions of well-known functions and constructions may be omitted for clarity and conciseness. The invention may, however, be embodied in many different forms and should not be construed as being limited to the exemplary embodiments of the present invention set forth herein. Although reference is made to the exemplary embodiments depicted in the drawings and the following descriptions, the embodiments disclosed herein are not meant to be exhaustive of the various alternative designs and embodiments that are encompassed by the disclosure.
• The terms and words used in the following description and claims are not limited to the bibliographical meanings, but, are merely used by the inventor to enable a clear and consistent understanding of the invention. Accordingly, it should be apparent to those skilled in the art that the following description of exemplary embodiments of the present invention is provided for illustration purpose only and not for the purpose of limiting the invention as defined by the appended claims and their equivalents.
• It is to be understood that the singular forms “a,” “an,” and “the” include plural referents unless the context clearly dictates otherwise. Thus, for example, reference to “a component surface” includes reference to one or more of such surfaces.
• Throughout the specification, it will also be understood that when an element is referred to as being “connected to” another element, it can be directly connected to the other element, or it can be electrically connected to the other element by having intervening elements disposed therebetween. Also, when a part “includes” or “comprises” an element, unless there is a particular description contrary thereto, the part can further include other elements, not excluding the other elements.
• Expressions such as “at least one of,” when preceding a list of elements, modify the entire list of elements and do not modify the individual elements of the list.
• FIG. 1 is a diagram of a device detection system for data transmission according to an exemplary embodiment of the present invention.
• Referring toFIG. 1, a device detection system includes afirst device100, asecond device200, and athird device300. Thefirst device100 may include at least one of a Personal Computer (PC), a tablet PC, and a smart television (TV), and thesecond device200 and thethird device300 may include mobile communication terminals, but types of the first throughthird devices100,200, and300 are not limited thereto.
• In the device detection system, thefirst device100 may detect thethird device300 to transmit and receive data using an address book stored in thesecond device200. In this case, thefirst device100 may separately generate and display a widget window for device detection and data transmission. When the widget window is selected by a user, thefirst device100 may provide the user with a service for the device detection. The widget window may be an execution window of an application that connects thefirst device100 and thesecond device200. Throughout the specification, the term “device detection” refers to detection of at least one of a user list and a device list that are included in an address book, i.e., detection of at least one of a telephone number of a device, a user name of a device, an e-mail address of a device user, and a Social Network Service (SNS) account of a device user, which are included in the address book.
• In addition, thefirst device100 may exchange data with thethird device300 by using a wireless communication function of thesecond device200. When thesecond device200 receives a text message from thethird device300, thefirst device100 may also receive the text message from thesecond device200 and may display the text message, and then the user may check the text message via thefirst device100 and may provide an answer message to thethird device300 via thesecond device200.
• In another example, when thesecond device200 receives a call request from thethird device300, thesecond device200 may provide the caller information of thethird device300 to thefirst device100. In this case, the user may check the caller information via thefirst device100 and may decide whether or not to receive the call request. The user may check the caller information of thethird device300 via thefirst device100, may write a message related to call reception, and may provide the message to thethird device300 via thesecond device200.
• In yet another example, thefirst device100 may provide a file stored in thefirst device100 to thesecond device200 via a widget window. Thefirst device100 may also receive content that is being executed in thesecond device200 and output the received content on its associated display.
• Thefirst device100 will be described in more detail with reference toFIG. 2.
• FIG. 2 is a diagram illustrating the structure of thefirst device100, according to an exemplary embodiment of the present invention.
• Referring toFIG. 2, thefirst device100 includes a connectingunit110, adata receiving unit120, a widgetwindow generating unit130, adata output unit140, a detectingunit150, adata transmitting unit160, a DataBase (DB)170, a transmitting and receivingunit180, and acontrol unit190.
• The connectingunit110 connects thefirst device100 and thesecond device200. In one example, the connectingunit110 may connect thefirst device100 and thesecond device200 via a user input in a widget window that is generated by the widgetwindow generating unit130 described below. For example, when a user selects a tethering button of the widget window, the connectingunit110 may request thesecond device200 for the connection. Although a user input is not separately input, if the widget window is executed, the connectingunit110 may request thesecond device200 for the connection.
• The connectingunit110 may store the previously received access information from thesecond device200, which is for connection to thesecond device200. The connectingunit110 may first request connection to thesecond device200 and then may receive the access information from thesecond device200. The access information for connection between thefirst device100 and thesecond device200 may be previously set in thefirst device100 and thesecond device200 by a user.
• Thedata receiving unit120 receives data from thesecond device200. For example, thedata receiving unit120 may receive an address book that is stored in thesecond device200 and may be used by thefirst device100 to detect a device to receive data using a widget window. In another example, thedata receiving unit120 may receive information from thesecond device200 associated with installed applications in the devices and may also include the address book. Alternatively, information associated with applications installed in the devices may be stored in the address book.
• Thedata receiving unit120 may also receive caller information of thethird device300 from thesecond device200. When thethird device300 requests a phone call, thedata receiving unit120 may receive the caller information of thethird device300 from thesecond device200, which may be displayed on a screen via the widget window.
• In yet another example, thedata receiving unit120 may receive a text message via thesecond device200. When thesecond device200 receives the text message from thethird device300, thedata receiving unit120 may receive the text message and device information of thethird device300 from thesecond device200. The device information may include at least one of a phone number, a user identification value, and an identification value of an application installed in the device.
• Also, thedata receiving unit120 may receive content that is being executed in thesecond device200. For example, thedata receiving unit120 may receive the content that is being executed in thesecond device200, in a streaming manner. In another example, when a screen is captured in thesecond device200, thedata receiving unit120 may receive the captured screen of thesecond device200.
• The widgetwindow generating unit130 generates a widget window for a data exchange with thesecond device200. The widget window may include a detection field for device detection that may be displayed on a pre-set area of a background screen of thefirst device100. A guide message for the device detection may also be displayed in the detection field of the widget window. For example, when a keyword is input via the detection field of the widget window, a device associated with the input keyword may be detected.
• When a file stored in thefirst device100 is moved to the widget window, the widgetwindow generating unit130 generates a file transmission method selection window that is used to select of a file transmission target. The file transmission method selection window may include a list for selecting the target device, such as thesecond device200 or thethird device300 that is not connected to thefirst device100. For example, the file transmission method selection window may include a selection list such as ‘transmission to second device’, ‘detection of another device’, or the like. Also, when thethird device300 is selected (i.e., when ‘detection of another device’ is selected), a guide message related to a keyword input may be displayed in the detection field of the widget window.
• Thedata output unit140 outputs data received from thesecond device200 on thefirst device100. For example, when the detection field of the widget window is selected in response to a user input, thedata output unit140 may display the address book received from thesecond device200 on a screen of thefirst device100.
• When thedata output unit140 receives the caller information from thesecond device200, thedata output unit140 may display the received caller information on the screen of thefirst device100. Thedata output unit140 may display a message regarding an incoming call on the screen of thefirst device100. In more detail, thedata output unit140 may extract a user name and a phone number of thethird device300 from the caller information of thethird device300, combine an extracted value with a predefined text, and output a guide message regarding whether or not to accept the incoming call on thefirst device100. For example, thedata output unit140 may display a guide message saying “An incoming call from Tom (555-1234). Do you want to accept this call?” on the screen of thefirst device100. When the user rejects to accept the incoming call, thedata output unit140 may display a message transmission window for transmission of a predetermined text message on the screen.
• Thedata output unit140 may output a text message that is received via thesecond device200 on the screen of thefirst device100. When thefirst device100 receives a message from thethird device300 via thesecond device200, thedata output unit140 generates a communication window for a message exchange between thefirst device100 and thethird device300 and displays the communication window on the screen.
• Thedata output unit140 may output the content that is being executed in thesecond device200 on thefirst device100. Thedata output unit140 may determine an application to execute based on content that is received from thesecond device200 and may output the content that is being executed in thesecond device200 using the determined application. For example, when thefirst device100 and thesecond device200 are connected to each other while a moving picture is reproduced in thesecond device200, thedata output unit140 may output content that is streamed from thesecond device200 in real-time to thefirst device100. In this case, application information to execute the received content may be previously set and stored in thefirst device100.
• The detectingunit150 may detect a device to receive data based on a user input via the widget window. When a user selects the widget window and inputs a keyword to the detection field of the widget window, the detectingunit150 may detect a device that corresponds to the input keyword from the address book received from thesecond device200.
• In this example, the keyword input by the user may include a pre-set tag value and the detectingunit150 may filter devices included in the address book according to the tag value. The tag value may differ from another tag value according to types of data transmission services that are supported by the devices included in the address book. For example, the tag value may be a prefix value, and in this regard, a prefix ‘A’ may be used to detect devices in which Twitter® is installed, and a prefix ‘B’ may be used to detect devices in which Facebook® is installed. Thus, when ‘A Tom’ is input to the widget window, the detectingunit150 may detect a device whose user name is ‘Tom’ from among the devices in which Twitter® is installed. In another example, when ‘B friends’ is input to the widget window, the detectingunit150 may detect a device of a user who is a friend of a user of thefirst device100 from among the devices in which Facebook® is installed.
• Thedata transmitting unit160 transmits data to thethird device300 via thesecond device200. Thedata transmitting unit160 may provide the data to thesecond device200 and may transmit the data to thethird device300 by using a communication function of thesecond device200.
• In more detail, thedata transmitting unit160 may provide a text message to thethird device300 via thesecond device200. When thethird device300 is detected and selected in thefirst device100 via the widget window, the communication window for a message exchange between thefirst device100 and thethird device300 may be generated in thefirst device100. For example, when a text message is input to the communication window by a user, thefirst device100 may transmit the text message to thethird device300 via thesecond device200.
• In addition, thedata transmitting unit160 may transmit information associated with acceptance of an incoming call. For example, when thethird device300 requests a phone call to thesecond device200, thesecond device200 may provide the caller information to thefirst device100. In this case, thefirst device100 may provide information related to acceptance of an incoming call to thethird device300 via thesecond device200. For example, when a user rejects the incoming call, thefirst device100 may provide thethird device300 with a message related to the rejection of the incoming call. For example, an input window message may be displayed on thefirst device100 and the user may input a message saying “I'm in a meeting so I can't receive your call” into the input window.
• Thedata transmitting unit160 may also transmit a file stored in thefirst device100 to thethird device300 via thesecond device200. For example, the user may select the file stored in thefirst device100, may move the selected file to the widget window, may detect thethird device300 via the widget window, and may transmit the selected file to thethird device300 via thesecond device200.
• TheDB170 stores information required for thefirst device100 to detect thethird device300 by using the address book stored in thesecond device200 and also stores information required to exchange data with thesecond device200 and thethird device300. For example, theDB170 may store information about the address book that is received from thesecond device200 and information about types of applications corresponding to different tag values.
• The transmitting and receivingunit180 exchanges data with thesecond device200 and thethird device300. The transmitting and receivingunit180 may exchange data with thethird device300 via thesecond device200.
• In order to allow thefirst device100 to detect thethird device300 and exchange data with thesecond device200 and thethird device300, thecontrol unit190 controls the connectingunit110, thedata receiving unit120, the widgetwindow generating unit130, thedata output unit140, the detectingunit150, thedata transmitting unit160, theDB170, and the transmitting and receivingunit180.
• Hereinafter, thesecond device200 will be described with reference toFIG. 3.
• FIG. 3 illustrates an example a structure of thesecond device200 according to an exemplary embodiment of the present invention.
• Referring toFIG. 3, thesecond device200 includes a connectingunit210, adata receiving unit220, adata transmitting unit230, a transmitting and receivingunit240, and acontrol unit250.
• The connectingunit210 connects thesecond device200 and thefirst device100 based on a user input via the widget window of thefirst device100. For example, when a user selects a tethering button included in the widget window of thefirst device100, the connectingunit210 may receive a connection request from thefirst device100.
• The connectingunit210 may provide thefirst device100 with access information for connection to thefirst device100. The access information may be previously received from thefirst device100 and may store the access information. In another example, the connectingunit210 may first receive a connection request from thefirst device100 and, in response, provide the access information to thefirst device100. In yet another example, the access information may be previously set in thefirst device100 and thesecond device200 by a user.
• Thedata receiving unit220 receives data to be provided to thethird device300 from thefirst device100. Thedata receiving unit220 may receive a text message input to thefirst device100. In this example, thedata receiving unit220 may also receive information associated with thethird device300 from thefirst device100. For example, thedata receiving unit220 may receive an identification value of thethird device300, a phone number of thethird device300, and/or a user name of thethird device300 from thefirst device100.
• Thedata receiving unit220 may also receive information that corresponds to acceptance of an incoming call from thethird device300. For instance, thedata receiving unit220 may receive a call-connection command or a phone call rejection signal from thefirst device100. Thedata receiving unit220 may also receive a message regarding the rejection of the incoming call from thefirst device100. For example, thedata receiving unit220 may receive a message saying “I'm in a meeting so I can't receive your call.”
• Also, thedata receiving unit220 may receive a file from thefirst device100. Thedata receiving unit220 may receive a file, which is selected and moved to the widget window in thefirst device100.
• Thedata transmitting unit230 also provides thefirst device100 with an address book stored in thesecond device200. The address book that is provided to thefirst device100 may be used in thefirst device100 to detect a device to receive data using the widget window. Thedata transmitting unit230 may also provide thefirst device100 with information about applications installed in devices, the information including the address book. Alternatively, information about applications installed in devices may be included in the address book.
• Thedata transmitting unit230 provides thefirst device100 with content that is being executed in thesecond device200 in a streaming manner. In another example, when a predetermined screen is captured in thesecond device200, thedata transmitting unit230 may provide thefirst device100 with the captured screen of thesecond device200.
• Thedata transmitting unit230 may also provide thethird device300 with data that is received from thefirst device100. For example, thedata transmitting unit230 may provide thethird device300 with a text message that is received from thefirst device100. In another example, thedata transmitting unit230 may provide thefirst device100 with a text message that is received from thethird device300.
• Thedata transmitting unit230 may provide thethird device300 with a file that is received from thefirst device100.
• The transmitting and receivingunit240 exchanges information with thefirst device100 and thethird device300 so that thefirst device100 may detect a device by using an address book of thesecond device200 and may provide data to the detected device via thesecond device200.
• Thecontrol unit250 controls all operations of thesecond device200. That is, thecontrol unit250 controls the connectingunit210, thedata receiving unit220, thedata transmitting unit230, and the transmitting and receivingunit240 so that thesecond device200 may provide the address book to thefirst device100 and data may be exchanged between thefirst device100 and thethird device300.
• Hereinafter, a method of transmitting data between devices will be described with reference toFIG. 4.
• FIG. 4 is a flowchart of a method of transmitting data between devices according to an exemplary embodiment of the present invention.
• In operation S400, thefirst device100 and thesecond device200 are connected to each other. In operation S400, thefirst device100 and thesecond device200 may be connected to each other based on a user input via a widget window of thefirst device100. For example, when a user selects a tethering button of the widget window, thefirst device100 may request connection to thesecond device200. In another example, if the widget window is executed, thefirst device100 may request the connection to thesecond device200. Also, when a screen is captured in thesecond device200, thefirst device100 may receive the captured screen from thesecond device200.
• At operation S400, thefirst device100 may first request a connection to thesecond device200 and then may receive the access information from thesecond device200. Also, the access information for connection between thefirst device100 and thesecond device200 may be stored or previously set in thefirst device100 and thesecond device200 by a user.
• At operation S402, thefirst device100 receives data from thesecond device200. For example, thefirst device100 may receive an address book that is stored in thesecond device200 and may be used by thefirst device100 to detect another device to receive data by using the widget window. Thefirst device100 may also receive information related to applications that are installed in the devices in the address book. Alternatively, information related to applications installed in the devices may be stored in the address book.
• In operation S402, thefirst device100 may receive caller information of thethird device300 from thesecond device200. When thethird device300 requests a phone call to thesecond device200, thedata receiving unit120 receives the caller information of thethird device300 from thesecond device200 and the received caller information may be displayed on a screen of thefirst device100 via the widget window.
• Also, in operation S402, thefirst device100 may receive a text message from thethird device300 via thesecond device200. When thesecond device200 receives the text message from thethird device300, thefirst device100 may receive the text message and device information of thethird device300 from thesecond device200. The device information may include a phone number, a user identification value, and/or an identification value of an application installed in a device.
• Also, in operation S402, thefirst device100 may receive content that is being executed in thesecond device200. Thefirst device100 may receive the content that is being executed in thesecond device200, for example, in a streaming manner.
• In operation S404, thefirst device100 outputs the widget window on its screen for a data exchange with thesecond device200. The widget window may include a detection field for device detection and may be displayed on a predefined area of a background screen of thefirst device100. A guide message may be displayed in the detection field of the widget window for the device detection. Referring toFIG. 4, the widget window is output after operation S402, but may be output before operation S400 or operation S402 to initiate file transfer, for example.
• In operation S406, thefirst device100 outputs the data that is received from thesecond device200. When the detection field of the widget window is selected in response to a user input, thefirst device100 may display an address book that is received from thesecond device200 on the screen of thefirst device100.
• When thefirst device100 receives the caller information of thethird device300 from thesecond device200, thefirst device100 may display the received caller information on the screen. In more detail, thefirst device100 may extract a user name and a phone number of thethird device300 from the caller information of thethird device300, may combine the extracted information with a predefined text, and then may output a guide message requesting acceptance of the incoming call. For example, thefirst device100 may display a guide message stating “An incoming call from Tom (555-1234). Do you want to receive this call?” When the user rejects the incoming call, thefirst device100 may display a message transmission window on the screen to transmit a predetermined text message to thethird device300.
• In operation S406, thefirst device100 may output a text message that is received by thesecond device200 on its screen. When thefirst device100 receives a message of thethird device300 via thesecond device200, thefirst device100 may generate a communication window for a message exchange between thefirst device100 and thethird device300 and may display the communication window on its screen.
• Thefirst device100 may output the content that is being executed in thesecond device200. Thefirst device100 may determine an application to execute the content received from thesecond device200 and may output the content that is being executed in thesecond device200 using the determined application. For example, when thefirst device100 and thesecond device200 are connected to each other while a moving picture is reproduced in thesecond device200, thefirst device100 may output content that is streamed from thesecond device200 in real-time to thefirst device100. In this example, application information to execute the received content may be previously set and stored in thefirst device100.
• In operation S408, thefirst device100 detects a device to receive data using the widget window based on a user input. When a user selects the widget window and inputs a predetermined keyword into the detection field of the widget window, thefirst device100 may detect a device that corresponds to the input keyword in the address book. When a file stored in thefirst device100 is moved to the widget window, a message for guiding a keyword with respect to detection of a device to receive the file may be displayed in the widget window.
• In this case, the keyword that is input by the user may include a predefined tag value and thefirst device100 may filter devices in the address book according to the tag value. The tag value may correspond to data transmission services that are supported by the devices in the address book. For example, the tag value may be a prefix value corresponding to a specific service or function. For example, a prefix ‘A’ may be used to detect devices having Twitter® is installed and a prefix ‘B’ may be used to detect devices having Facebook® is installed. Thus, when ‘A Tom’ is input to the widget window, thefirst device100 may detect a device whose user name is ‘Tom’ from among the devices in which Twitter® is installed. When ‘B friends’ is input to the widget window, thefirst device100 may detect a device of a user who is a friend of a user of thefirst device100 from among the devices in which Facebook® is installed.
• In operation S410, thefirst device100 provides thesecond device200 with data that will be provided to thethird device300, such as a text message that is input to thefirst device100, for example. When thethird device300 is detected and selected in thefirst device100 via the widget window, the communication window for a message exchange between thefirst device100 and thethird device300 may be generated to allow a user to input a text message and may transmit the text message to thethird device300 via thesecond device200.
• At operation S410, thefirst device100 may transmit information related to acceptance of an incoming call. For example, when thethird device300 requests a phone call to thesecond device200, thesecond device200 may provide the caller information to thefirst device100. In this case, thefirst device100 may provide information related to acceptance of an incoming call to thesecond device200. For example, when a user rejects the incoming call from thethird device300, thefirst device100 may provide thesecond device200 with a message related to the rejection of the incoming call. For example, an input window for an input of a call-connection message may be displayed on thefirst device100 and then the user may input a message stating “I'm in a meeting so I can't receive your call” into the input window.
• In another example of operation S410, thefirst device100 may transmit a file stored in thefirst device100 to thesecond device200. When a user selects a file stored in thefirst device100, the selected file may be provided to thesecond device200. For example, the user may select the file stored in thefirst device100 by placing the file in the widget window, may detect thethird device300 via the widget window, and may provide thesecond device200 with an identification value of thethird device300 and the selected file.
• In operation S412, thesecond device200 provides thethird device300 with the data received from thefirst device100. For example, thesecond device200 may provide the third device300 a text message received from thefirst device100, information about a call-connection, and/or a file. In this case, thesecond device200 may receive device information related to the third device300 (e.g., a phone number, an e-mail address, or the like) from thefirst device100 and may transmit the data to thethird device300 based on the received device information.
• Hereinafter, a method of detecting a device to receive data will be described with reference toFIG. 5.
• FIG. 5 is a flowchart of a method of detecting a device to receive data, according to an exemplary embodiment of the present invention.
• In operation S500, thefirst device100 and thesecond device200 may be connected to each other based on, for example, a user input via a widget window of thefirst device100. For example, when a user selects a tethering button of the widget window, thefirst device100 may request connection to thesecond device200 to further connect to thethird device300.
• In operation S502, thefirst device100 receives an address book from thesecond device200. The address book received from thesecond device200 may include at least one of a telephone number of a device, a user name of a device, an e-mail address of a device user, and an SNS account of a device user. The address book may be used by thefirst device100 to detect a device to receive data using the widget window. Also, thefirst device100 may receive information related to applications installed in the devices in the address book. Alternatively, information related to applications installed in the devices may be stored in the address book.
• In operation S504, thefirst device100 receives a keyword input for device detection via the widget window, which may include a detection field for device detection and may be displayed on a predefined area of a background screen of thefirst device100. A guide message for the device detection may also be displayed in the detection field of the widget window. The guide message may be displayed when a file is selected and then is moved to the widget window.
• In operation S504, thefirst device100 may also receive a keyword that is input by a user via the widget window. The keyword may include a user name of a device or a phone number of a device. In another example, the keyword may include a tag value associated with a service or a function. For example, the tag value may be a prefix value and detection targets may differ from each other according to the tag value. For example, a tag value ‘@’ may be used in detection through group names, and a tag value ‘#’ may be used in detection through phone numbers. In such an example, devices in the address book may be filtered according to the tag value. For example, a tag value ‘$’ may be used to filter recent reception and transmission contact addresses of the list, a tag value ‘A’ may be used to filter devices in which Twitter® is installed, and a tag value ‘B’ may be used to filter devices in which Facebook® is installed.
• In addition, the widget window may be used to search for contents and messages that are stored in thefirst device100 and thesecond device200. In this case, a tag value ‘!’ may be used to search for a music file, a tag value ‘!!’ may be used to search for a moving picture file, and a tag value ‘&’ may be used to search for a message.
• The widget window may be used to detect a peripheral device connected to thefirst device100. For example, a tag value ‘̂’ may be used to detect the peripheral device by using Digital Living Network Alliance (DLNA).
• In operation S506, thefirst device100 may detect the devices related to the input keyword in the address book. In this case, thefirst device100 may filter devices in which Twitter® is installed, and a prefix ‘B’ may be used to detect devices in which Facebook® is installed. Thus, when ‘A Tom’ is input to the widget window, thefirst device100 may filter the devices in which Twitter® is installed and then may detect a device whose user name is ‘Tom’ from among the filtered devices. Also, when ‘B friends’ is input to the widget window, thefirst device100 may filter the devices in which Facebook® is installed and then may detect a device of a user who is a friend of the user of thefirst device100 from among the filtered devices.
• In operation S508, thefirst device100 may provide thesecond device200 with the data to be provided to the detectedthird device300. For example, thefirst device100 may provide thesecond device200 with a text message input by the user or a file selected by the user. Thefirst device100 may also provide thesecond device200 with device information of thethird device300 to receive the data including a user name, a phone number, and/or an e-mail address of a user, for example.
• In operation S510, thesecond device200 transmits the data received from thefirst device100 to thethird device300 using the device information of thethird device300.
• Hereinafter, a method of transmitting data between devices by using a widget window will be described with reference toFIG. 6.
• FIG. 6 is a flowchart of a method of transmitting data between devices by using a widget window, according to an exemplary embodiment of the present invention.
• In operation S600, thefirst device100 and thesecond device200 may be connected to each other based on a user input via a widget window. For example, when a user selects a tethering button of the widget window, thefirst device100 may request connection to thesecond device200. In other examples, thesecond device200 may request connection to thefirst device100.
• In operation S602, in response to the user input, thefirst device100 may move a file that is selected to the widget window. For example, the user may select a file stored in thefirst device100 and move the selected file to the widget window in a drag and drop manner.
• In operation S604, thefirst device100 may display a file transmission method selection window on the screen to allow a user to select a file transmission method. The file transmission method selection window includes a list containing ‘file transmission’ for direct file transmission and ‘message transmission’ for file transmission via a message window.
• In operation S606, thefirst device100 determines whether ‘file transmission’ is selected in the file transmission method selection window. If ‘file transmission’ is selected according to a user input at operation S606, thefirst device100 directly transmits a file to thesecond device200 in operation S608.
• Also, in operation S606, if ‘file transmission’ is not selected, in operation S610, thefirst device100 determines whether ‘message transmission’ is selected in the file transmission method selection window.
• In operation S610, if ‘message transmission’ is selected, in operation S612, thefirst device100 detects a transmission target. In operation S612, thefirst device100 may receive a keyword to detect the transmission target by using a keyword input by the user.
• In this case, the keyword may include a user name of a device, a phone number of the device, or a tag value. For example, the tag value may be a prefix value corresponding to data transmission services that are supported by devices included in the address book. Thefirst device100 may filter the device by using the tag value included in the keyword. For example, a prefix ‘A’ may be used to detect devices in which Twitter® is installed, and a prefix ‘B’ may be used to detect devices in which Facebook® is installed. Thus, when ‘A Tom’ is input to the widget window, thefirst device100 may filter the devices in which Twitter® is installed and then may detect a device whose user name is ‘Tom’ from the filtered devices. When ‘B friends’ is input to the widget window, thefirst device100 may filter the devices in which Facebook® is installed and then may detect a device of a user who is a friend of the user of thefirst device100 from the filtered devices. Thefirst device100 selects at least one of the detected devices as a transmission target in the address book that is received from thesecond device200.
• In operation S614, thefirst device100 may generate the message transmission window with respect to the device detected in operation S612 and may insert the file into the generated message transmission window.
• However, whether or not to display the file transmission method selection window on thefirst device100 may be decided according to a state of thesecond device200. For example, when the message transmission window is displayed on thesecond device200, thefirst device100 may not display the file transmission method selection window.
• Display of the file transmission method selection window on thefirst device100 may be decided according to a state of thefirst device100. For example, when a message transmission window is displayed on thefirst device100, thefirst device100 may not display the file transmission method selection window. Also, thefirst device100 may insert the selected file into the message transmission window displayed on thefirst device100.
• In operations S616 and S618, thefirst device100 provides the selected file to thethird device300 via thesecond device200. In such an example, thethird device300 may be the device that is selected in operation S612.
• Hereinafter, a method of transmitting data between devices by using a widget window will be described with reference toFIG. 7.
• FIG. 7 is a flowchart of a method of transmitting data between devices by using a widget window, according to another exemplary embodiment of the present invention.
• In operation S700, thefirst device100 and thesecond device200 may be connected to each other based on a user input via a widget window of thefirst device100. For example, when a user selects a tethering button of the widget window, thefirst device100 may request connection to thesecond device200. In other examples, thesecond device200 may request connection to thefirst device100.
• In operation S702, thefirst device100 may move a file to the widget window that is selected in response to the user input. The user may select a file stored in thefirst device100 and may move the selected file to the widget window in a drag and drop manner.
• In operation S704, thefirst device100 outputs a selection list to select a target to receive the selected file. In operation S704, thefirst device100 may display a file transmission target selection window on the screen that includes a list containing ‘transmission to connected device’ for file transmission to thesecond device200 and ‘transmission to another device’ for file transmission to a device that is not connected to thefirst device100.
• In operation S706, thefirst device100 determines whether ‘transmission to connected device’ is selected in the file transmission target selection window. In operation S706, when ‘transmission to connected device’ is selected according to a user input, thefirst device100 directly transmits the selected file to thesecond device200 in operation S708.
• Returning to operation S706, when ‘transmission to connected device’ is not selected, thefirst device100 determines whether ‘transmission to another device’ is selected in the file transmission target selection window in operation S710.
• In operation S710, when ‘transmission to another device’ is selected, thefirst device100 detects a device to receive a file at operation S712. In operation S712, thefirst device100 may receive a keyword to be used in detecting and selecting the device to receive a file.
• In operations S714 and S716, thefirst device100 provides the selected file to thethird device300 via thesecond device200. In this example, thethird device300 may be the device that is detected in operation S712.
• Hereinafter, a method of receiving and processing caller information of thethird device300, performed by thefirst device100, will be described with reference toFIG. 8.
• FIG. 8 is a flowchart of a method of receiving and processing caller information of thethird device300, according to an exemplary embodiment of the present invention.
• In operation S800, thefirst device100 and thesecond device200 may be connected to each other based on a user input via a widget window of thefirst device100. For example, when a user selects a tethering button of the widget window, thefirst device100 may request connection to thesecond device200. In other examples, thesecond device200 may request connection to thefirst device100.
• In operation S802, thethird device300 requests call-connection to thefirst device100 via thesecond device200. Thesecond device200 may receive a call signal from thethird device300 including the caller information at operation S802.
• In operation S804, thesecond device200 may provide thefirst device100 with the caller information of thethird device300. For example, thesecond device200 may receive a phone number from thethird device300, may extract a user name, a group name, and the like with respect to the received phone number from an address book and transmit the caller information, including information from the address book to, thefirst device100 with the caller information of thethird device300.
• In operation S806, thefirst device100 may display the received caller information on a separate window on a screen of thefirst device100.
• In operation S808, thefirst device100 may display a selection menu in the display associated with the caller information. The selection menu may include items incoming-call connection information such as ‘accept incoming call’, ‘reject incoming call’, and ‘reject with message.’
• In operation S810, thefirst device100 generates incoming-call connection information according to the incoming-call connection information. The incoming-call connection information may include a command to accept the incoming call, a command to reject the incoming call, and a message regarding incoming-call connection. Thefirst device100 generates a command to accept the incoming call from thethird device300 based on the selected incoming-call connection information. For example, when a user selects ‘accept incoming call’ in the selection menu, thefirst device100 generates a command to accept a call-connection with thethird device300. When the user selects ‘reject incoming call’ in the selection menu, thefirst device100 may generate a command to reject the call-connection with thethird device300.
• When the user selects ‘reject with message’ in the selection menu, thefirst device100 may display a message input window on the screen and generate a message regarding whether or not to accept the incoming call. For example, thefirst device100 may generate a message saying “I'm in a meeting so I can't receive your call,” based on the user input to the message input window. The message input window may be separately displayed in the pop-up window that displays the caller information.
• In operation S812, thefirst device100 may provide thesecond device200 with the command to accept the incoming call, the command to reject the incoming call, and/or the message regarding incoming-call connection. When thefirst device100 provides thesecond device200 with the command to accept the incoming call, thesecond device200 may be connected to thethird device300 and may perform the call-connection.
• In operation S814, thesecond device200 provides the message regarding incoming-call connection to thethird device300. When thefirst device100 provides the command to reject the incoming call to thesecond device200, thesecond device200 may block the call-connection with thethird device300. Also, thesecond device200 may provide thethird device300 with a message received from thefirst device100.
• Hereinafter, a method of receiving a captured screen from thesecond device200 will be described with reference toFIG. 9.
• FIG. 9 is a flowchart of a method of receiving a captured screen from thesecond device200, according to an exemplary embodiment of the present invention.
• In operation S900, in response to a user input, thefirst device100 selects a capture icon in a widget window. The capture icon may include an icon to capture a screen of thesecond device200 and an icon to take a picture by using thesecond device200. One capture icon may be in the widget window and, when the capture icon is selected, a selection window for selection of capture types may be displayed. In this case, a user may select one of the capture types in the selection window and decide whether to capture the screen of thesecond device200 or to take a picture by using thesecond device200.
• In operation S902, thefirst device100 may request capture information. For example, the capture information may include a captured screen image of thesecond device200 or an image captured by thesecond device200.
• In operation S904, in response to the request for the capture information, thesecond device200 generates the captured screen image. When thefirst device100 requests the capture information, thesecond device200 may generate the captured screen image of thesecond device200 in operation S904.
• In operation S906, thesecond device200 generates the captured image, in response to the request for the capture information. In operation S902, when thefirst device100 requests the capture information including the image captured by thesecond device200, in operation S906, thesecond device200 may generate the captured image by using a photographing apparatus included in thesecond device200.
• In operation S908, thesecond device200 generates context information related to at least one of a screen capturing operation and an image photographing operation. The context information may include a time, a place, and weather, for example.
• In operation S910, thesecond device200 provides the capture information to thefirst device100. The capture information may include the captured screen image, the captured image, and the context information.
• In operation S912, thefirst device100 collects additional information from a server (not shown) based on the context information. In operation S912, thefirst device100 may check the context information included in the capture information and then may collect the additional information corresponding to the context information. For example, the additional information may include map information, area information, and news information, for example.
• In operation S914, thefirst device100 displays the received capture information and the additional information on the screen. Thefirst device100 may display at least one of the captured screen image and the captured image, and may also display the context information and the additional information which are related to the captured screen image and/or the captured image.
• Hereinafter, a method of performing communication between devices will be described with reference toFIG. 10.
• FIG. 10 is a diagram illustrating a method of performing communication between devices, according to an exemplary embodiment of the present invention.
• Referring toFIG. 10, thefirst device100 may use a wireless communication function of thesecond device200 via tethering. For example, thefirst device100 may be connected with thesecond device200 via Wireless Fidelity (Wi-Fi) communication. Also, thefirst device100 and thesecond device200 may be connected to each other by using a different wireless communication service such as a Third Generation (3G) mobile communication or the Fourth Generation (4G) mobile communication.
• In this case, a tethering function of thesecond device200 may be activated in response to a user input in a widget window in thefirst device100. For example, when a predetermined region is selected in the widget window displayed in thefirst device100, thefirst device100 may request thesecond device200 for activation of the tethering function. That is, when the widget window is active in thefirst device100, thefirst device100 may request thesecond device200 for the tethering function.
• Also, thefirst device100 and thesecond device200 may exchange access information for communication when the tethering function is requested.
• For example, a widget window application to perform device detection and data transmission using a widget window may be executed in thefirst device100. In this example, thefirst device100 and thesecond device200 may be connected to each other by using the widget window application. Also, a widget window agent in the widget window application that may be executed when a power of thefirst device100 is ON and may execute the widget window in thefirst device100 when a peripheral device for connection exists at a same Access Point (AP) as that of thefirst device100. The widget window application may detect thesecond device200 and connect thefirst device100 and the detectedsecond device200. In more detail, the widget window application may detect thesecond device200 that is a peripheral device of thefirst device100 and transmit an authentication code to the detectedsecond device200. Thesecond device200 may confirm the authentication code and perform Wi-Fi communication configuration for connection to thefirst device100. Also, thesecond device200 may provide thefirst device100 with an Internet Protocol (IP) value and a verified authentication code. The widget window application may authenticate the detectedsecond device200 to connect thefirst device100 and thesecond device200. After the authentication is performed between thefirst device100 and thesecond device200, thefirst device100 and thesecond device200 may be connected to each other without separate authentication.
• In another example, thefirst device100 and thesecond device200 may be connected to each other by using a Universal Serial Bus (USB) cable. In this example, the widget window application of thefirst device100 may execute the widget window on a screen of thefirst device100 and request thesecond device200 to execute a widget window application of thesecond device200. Also, when the USB connection between thefirst device100 and thesecond device200 is disconnected, thefirst device100 and thesecond device200 may be re-connected to each other via Wi-Fi communication.
• Hereinafter, an address book will be described with reference toFIG. 11.
• FIG. 11 illustrates an example of an address book according to an exemplary embodiment of the present invention.
• Referring toFIG. 11, the address book includes a speed-dial field90, auser field91, aphone number field92, agroup field93, adevice field94, and anapplication field95.
• Speed-dials corresponding to phone numbers are recorded in the speed-dial field90 and user names corresponding to the phone numbers are recorded in theuser field91. The phone numbers are recorded in thephone number field92 and group names of the user are recorded in thegroup field93. In the address book, types of devices corresponding to the phone numbers are recorded in thedevice field94. For example, device names such as ‘Galaxy S3’ and ‘I-Phone’ may be recorded in thedevice field94. Names of applications that are installed in the devices are recorded in theapplication field95. For example, names of messenger applications such as Twitter® and Facebook® may be recorded in theapplication field95. The address book may be directly provided from thesecond device200 to thefirst device100 or may be indirectly provided from thesecond device200 to thefirst device100 via a separate server (not shown), and thefirst device100 may detect a device to receive data using the address book.
• Also, prefixes may match with names of the devices recorded in thedevice field94 and the names of applications recorded in theapplication field95, respectively. Thus, when a user inputs a keyword for device detection, the user may also input a predetermined prefix to filter some of the devices by using the input prefix and perform detection with respect to the filtered devices.
• Hereinafter, an example of device detection for data transmission by thefirst device100 will be described with reference toFIG. 12.
• FIG. 12 illustrates an example of device detection for data transmission by thefirst device100, according to an exemplary embodiment of the present invention.
• Referring toFIG. 12, awidget window12 for data transmission may be displayed on ascreen10 of thefirst device100. When apredetermined button14 is selected in thewidget window12, thefirst device100 and thesecond device200 may be connected to each other. In another example, when thewidget window12 is active in thefirst device100, thefirst device100 and thesecond device200 may be connected to each other.
• Also, a user may input a keyword into adetection field16 of thewidget window12 to detect a target to receive data. For example, when the user inputs ‘B friends’ into thedetection field16, thefirst device100 may filter devices from an address book by using a prefix ‘B’ and detect a device that belongs to a friend of the user from among the filtered devices
• The detection result may be output to aseparate window17 and applications that are installed in the user's device may be displayed on aregion18 of the output result. When theregion18 is selected, a corresponding application may be executed in thesecond device200 to transmit data to the detected device via thesecond device200. In this example, thefirst device100 may provide thesecond device200 with a control command to execute the application and the data to be transmitted.
• Hereinafter, an example of a widget window for displaying a result of device detection will be described with reference toFIG. 13.
• FIG. 13 illustrates an example of a widget window for displaying a result of device detection, according to an exemplary embodiment of the present invention.
• Referring toFIG. 13, when a keyword ‘Kim’ is input to adetection field16 of awidget window12, adevice detection list1 corresponding to the keyword ‘Kim’ is displayed below thewidget window12. As illustrated inFIG. 13, thedevice detection list1 may include user names and phone numbers of detected devices. Thedevice detection list1 may also include a recentdevice detection list2 of devices that are recently used by a user that is distinguishably displayed on an upper portion of thedevice detection list1.
• Thedevice detection list1 may include a callingicon3 and a message transmission icon4. When the user selects the callingicon3, thefirst device100 may request thesecond device200 to make a call to a device displayed on thedetection list1. When the user selects the message transmission icon4, a message transmission window (not shown) is displayed on a screen of thefirst device100 and thefirst device100 may transmit a message, which is input to the message transmission window, to thethird device300 via thesecond device200.
• In addition, a plurality oficons5 is displayed on thewidget window12 to allow functions to be performed in thefirst device100. For example, theicons5 may include an icon for movement to a home-screen, an icon for reproduction of music, an icon for execution of an internet browser, and an icon for a request for a captured image. When the user selects the icon for a request for a captured image, thefirst device100 may request thesecond device200 for a captured screen image of thesecond device200. Also, when the user selects the icon for a request for a captured image, thefirst device100 may request thesecond device200 for an image captured by thesecond device200.
• Hereinafter, an example of file transmission based on a file transmission method that is selected by thefirst device100 via a widget window will be described with reference toFIG. 14.
• FIG. 14 illustrates an example of file transmission based on a file transmission method that is selected by thefirst device100 via a widget window, according to an exemplary embodiment of the present invention.
• Referring toFIG. 14, when a user selects afile21 from afolder20 that is displayed on ascreen10 of thefirst device100 and moves the selectedfile21 to awidget window12, aselection window23 may be displayed on thescreen10 for selection of a file transmission method. Theselection window23 may include a list containing ‘file transmission’ for direct file transmission and ‘message transmission’ for file transmission via a message.
• When ‘file transmission’ is selected from the selection list, thefirst device100 may provide a selected file to thesecond device200 without a separate procedure. When ‘message transmission’ is selected from the selection list, a guide message related to a keyword input may be displayed in adetection field16 of thewidget window12. In response, the user may input a keyword to thedetection field16 to detect a device, and thesecond device200 may generate a message transmission window24 with respect to the detected device and insert the selected file into the message transmission window24. Thefirst device100 may provide the file inserted into the message transmission window24 to the detected device via thesecond device200.
• Hereinafter, an example of file transmission to a file transmission target selected by thefirst device100 will be described with reference toFIG. 15.
• FIG. 15 illustrates an example of file transmission to a file transmission target selected by thefirst device100, according to an exemplary embodiment of the present invention.
• Referring toFIG. 15, when a user selects afile21 from afolder20 displayed on ascreen10 of thefirst device100 and moves thefile21 to awidget window12, aselection window22 is displayed for selection of a transmission target.
• For example, theselection window22 may include a selection list such as ‘transmission to second device’ and ‘detection of another device’. When thesecond device200 is selected from the selection list, thefirst device100 may provide the selectedfile21 to thesecond device200 without a separate procedure. When thethird device300 is selected from the selection list (i.e., when ‘detection of another device’ is selected), a guide message related to a keyword input may be displayed in adetection field16 of thewidget window12. Then, the user may input a keyword to thedetection field16 to detect a device and provide the selectedfile21 to the detected device via thesecond device200.
• FIG. 16 illustrates an example of message transmission by thefirst device100, according to an exemplary embodiment of the present invention.
• Referring toFIG. 16, when thesecond device200 receives a message from thethird device300, thesecond device200 may provide the received message to thefirst device100, which displays the received message on amessage window30. A user may input a message to themessage window30 and the input message may be provided to thethird device300 via thesecond device200. Also, the user may detect another device by using awidget window12 to provide a message to the other detected device via themessage window30.
• FIG. 17 illustrates an example in which caller information of thethird device300 is displayed on thefirst device100 and incoming-call connection information related to acceptance of an incoming call from thethird device300 is generated according to an exemplary embodiment of the present invention.
• Referring toFIG. 17, when thethird device300 attempts to make a phone call to thesecond device200, thesecond device200 may provide the caller information of thethird device300 to thefirst device100. In this example, thefirst device100 may receive the caller information and may display the caller information on a callreception notice window40. Afterward, a user may select an ‘accept’button41, a ‘reject’button42, or a ‘reject with message’button43 to accept or reject an incoming call. In response, thefirst device100 may generate the incoming-call connection information based on the selection. For example, when the user selects the ‘accept’button41, thefirst device100 may generate a command to accept the incoming call and provide the command to thesecond device200.
• When the user selects the ‘reject’button42, thefirst device100 may generate a command to reject the incoming call and then may provide the command to thesecond device200.
• In another example, when the user selects the ‘reject with message’button43, thefirst device100 may generate a command to reject the incoming call, provide the command to thesecond device200, and generate and display a separatemessage input window44 related to acceptance or rejection of the call. For example, the user may input a message saying “I'm in a meeting so I can't receive your call” to themessage input window44 and then thefirst device100 may provide the input message to thethird device300 via thesecond device200.
• FIG. 18 illustrates an example in which capture information and additional information are displayed on thefirst device100 according to an exemplary embodiment of the present invention.
• When thefirst device100 requests a captured image from thesecond device200, thesecond device200 may provide thefirst device100 with capture information including the captured image. Thefirst device100 may collect additional information from a server (not shown) by using context information included in the capture information.
• The capture information and the additional information are illustrated in the example ofFIG. 18. Animage60 captured by thesecond device200,location information62 about where theimage60 was captured, and mapinformation63 illustrating the location may be displayed on a screen of thefirst device100.
• FIG. 19 illustrates an example in which thefirst device100 receives and outputs content that is being executed in thesecond device200, according to an exemplary embodiment of the present invention.
• Referring toFIG. 19, when the user selects a predetermined button in awidget window12 displayed on thefirst device100, content that is being executed in thesecond device200 may be provided to thefirst device100. Thesecond device200 may stream the content to thefirst device100 in real-time, which may execute anapplication50 to reproduce the streamed content according to a type of the streamed content.
• According to the one or more exemplary embodiments of the present invention, a transmission target may be effectively selected by using a widget window and data may be transmitted to the file transmission target.
• Also, according to the one or more exemplary embodiments of the present invention, a transmission target may be detected from an address book stored in another device and, using the widget window, data may be transmitted to the detected transmission target via the other device.
• While the invention has been shown and described with reference to certain exemplary embodiments thereof, it will be understood by those skilled 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 appended claims and their equivalents.

Claims (43)

What is claimed is:

1. A system for transmitting data to a first mobile terminal and a second mobile terminal by using an execution window of an application displayed on a computer, the system comprising:

a computer for moving a file selected on a display screen to the execution window of the application that connects the computer and the first mobile terminal, for displaying a selection list when the file is moved to the execution window, and for transmitting the file to the first mobile terminal using the selected transmission method, wherein the selection list is used to select a transmission method related to the file; and

a mobile terminal for receiving the file from the computer, and for transmitting the file to the second mobile terminal that is connectable with the first mobile terminal,

wherein the selection list comprises a first selection for transmitting the file to the first mobile terminal and a second selection for transmitting the file to the second mobile terminal that is connectable with the first mobile terminal, and

wherein, when the second selection is selected, the computer transmits the file to the second mobile terminal via the first mobile terminal.

2. The system ofclaim 1, wherein, when the first selection for transmitting the file to the first mobile terminal is selected, the computer transmits the file to the first mobile terminal that is connected with the computer.

3. The system ofclaim 1, wherein a communication method between the computer and the first mobile terminal that is connected with the computer is different from a communication method between the second mobile terminal and the first mobile terminal.

4. The system ofclaim 3, wherein the computer and the first mobile terminal that is connected with the computer are connected to each other via Wireless Fidelity (Wi-Fi) communication, and the second mobile terminal and the first mobile terminal are connected to each other via at least one of Third Generation (3G) mobile communication and Fourth Generation (4G) mobile communication.

5. The system ofclaim 1, wherein, when the second selection is selected from the selection list, the computer generates a message input window, inserts the file into the message input window, and then provides the file to the first mobile terminal.

6. The system ofclaim 1, wherein, when the second selection is selected from the selection list, the computer receives a keyword that is input to the execution window,

the first mobile terminal provides the computer with an address book that is stored in the first mobile terminal, and

the computer searches for a phone number in the address book that corresponds to the input keyword and transmits the file to a fourth mobile terminal that corresponds to the phone number.

7. The system ofclaim 6, wherein the computer transmits the file to the fourth mobile terminal using a message input window.

8. The system ofclaim 6, wherein the keyword comprises one of tag values and the tag values correspond to applications installed in mobile terminals listed in the address book.

9. The system ofclaim 1, wherein the computer moves the file to the execution window in a drag and drop manner.

10. A method of transmitting, by a computer, a file by using an execution window of an application that connects the computer to a first mobile terminal, the method comprising:

moving a file selected on a screen of the computer to the execution window of the application;

when the file is moved to the execution window, displaying a selection list on the screen of the computer to select a transmission method; and

when a transmission method is selected from the selection list, transmitting the selected file using the selected transmission method;

wherein the selection list comprises a first selection for transmitting the file to the first mobile terminal and a second selection for transmitting the file to a second mobile terminal that is connectable with the first mobile terminal, and

wherein, when the second selection is selected, the transmitting of the selected file comprises transmitting the file to the second mobile terminal via the first mobile terminal.

11. The method ofclaim 10, wherein, when the first selection is selected, the transmitting of the file comprises transmitting the file to the first mobile terminal that is connected with the computer.

12. The method ofclaim 10, wherein a communication method between the computer and the first mobile terminal is different from a communication method between the second mobile terminal and the first mobile terminal.

13. The method ofclaim 12, wherein the computer and the first mobile terminal are connected to each other via Wireless Fidelity (Wi-Fi) communication, and the second mobile terminal and the first mobile terminal are connected via at least one of Third Generation (3G) mobile communication and Fourth Generation (4G) mobile communication.

14. The method ofclaim 10, wherein, when the second selection is selected, the transmitting of the file comprises:

generating a message input window;

inserting the file into the message input window; and

providing the file to the first mobile terminal.

15. The method ofclaim 10, wherein, when the second selection is selected the transmitting of the file further comprises:

receiving a keyword that is input to the execution window;

receiving an address book from the first mobile terminal; and

searching for a phone number in the address book that corresponds to the input keyword; and

transmitting the selected file to a third mobile terminal that corresponds to the searched phone number.

16. The method ofclaim 15, wherein the transmitting of the selected file comprises transmitting the file to the third mobile terminal using a message input window.

17. The method ofclaim 15, wherein the keyword comprises one of tag values, and

wherein the tag values correspond to applications installed in mobile terminals listed in the address book.

18. The method ofclaim 10, wherein the moving comprises moving the file to the execution window in a drag and drop manner.

19. A method of transmitting, by a first mobile terminal connected with a computer, a file received from the computer to a second mobile terminal, the method comprising:

when a file selected on a screen of the computer and is moved to an execution window of an application that connects the computer and the first mobile terminal, receiving the file from the computer; and

transmitting the file to the second mobile terminal that is connectable with the first mobile terminal,

wherein, when a selection for transmitting the file to the second mobile terminal is selected from a selection list displayed on the screen of the computer as the file is moved from the computer to the execution window, the transmitting of the file to the second mobile terminal comprises transmitting the file to the second mobile terminal.

20. The method ofclaim 19, wherein the selection list comprises a first selection for transmitting the file to the first mobile terminal, and a second selection for transmitting the file to the second mobile terminal that is connectable with the first mobile terminal.

21. The method ofclaim 19, wherein a communication method between the computer and the first mobile terminal is different from a communication method between the first mobile terminal and the second mobile terminal.

22. The method ofclaim 21, wherein the computer and the first mobile terminal are connected to each other via Wireless Fidelity (Wi-Fi) communication, and the first mobile terminal and the second mobile terminal are connected to each other via at least one of Third Generation (3G) mobile communication and Fourth Generation (4G) mobile communication.

23. The method ofclaim 19, wherein the receiving of the file comprises receiving the file from the computer via a message, wherein the file is inserted into a message input window that is generated by the computer when the second selection for transmitting the file to the second mobile terminal is selected from the selection list.

24. The method ofclaim 19, further comprising:

transmitting an address book stored in the first mobile terminal to the computer,

wherein, when the second selection for transmitting the file to the second mobile terminal is selected from the selection list by the computer, the address book is used in detection of a target to receive the file in response to a keyword that is input to the execution window.

25. The method ofclaim 24, wherein the keyword comprises a tag value that filters phone numbers that are searched for in response to the keyword.

26. A computer for transmitting a file by using an execution window of an application, the computer comprising:

a widget window generating unit for displaying a selection list on a screen of the computer to select a transmission method related to a file when the file that is selected on the screen of the computer is moved to the execution window of the application; and

a data transmitting unit for transmitting the file using a transmission method selected from the selection list,

wherein the selection list comprises a first selection for transmitting the file to a first mobile terminal and a second selection for transmitting the file to a second mobile terminal, and

wherein, when the second selection is selected, the data transmitting unit transmits the file to the second mobile terminal via the first mobile terminal.

27. The computer ofclaim 26, wherein, when the first selection is selected, the data transmitting unit transmits the file to the first mobile terminal.

28. The computer ofclaim 26, wherein a communication method between the computer and the first mobile terminal is different from a communication method between the second mobile terminal and the first mobile terminal.

29. The computer ofclaim 28, wherein the computer and the first mobile terminal are connected to each other via Wireless Fidelity (Wi-Fi) communication, and the second mobile terminal and the first mobile terminal are connected to each other via at least one of Third Generation (3G) mobile communication and Fourth Generation (4G) mobile communication.

30. The computer ofclaim 26, wherein, when the second selection is selected, the widget window generating unit generates a message input window and inserts the file into the message input window, and wherein the data transmitting unit provides the file to the first mobile terminal.

31. The computer ofclaim 26, further comprising:

a data receiving unit for receiving an address book from the first mobile terminal; and

a detecting unit for searching for a phone number based on a keyword that is input to the execution window,

wherein, when the second selection is selected, the detecting unit searches for the phone number in the address book which corresponds to the input keyword, and wherein the data receiving unit transmits the file to a third mobile terminal that corresponds to the phone number.

32. The computer ofclaim 31, wherein the data receiving unit transmits the file to the third mobile terminal using a message input window.

33. The computer ofclaim 31, wherein the keyword comprises one of tag values, and

the tag values correspond to applications installed in mobile terminals listed in the address book.

34. The computer ofclaim 26, wherein the file is moved to the execution window in a drag and drop manner.

35. A mobile terminal comprising:

a data receiving unit for receiving a file from a computer when the file that is selected and moved to an execution window of an application that connects the computer and a first mobile terminal; and

a data transmitting unit for transmitting the file to a second mobile terminal that is connectable with the first mobile terminal,

wherein, when a selection for transmitting the file to the second mobile terminal is selected from a selection list displayed on the screen of the computer as the file is moved from the computer to the execution window, the data transmitting unit transmits the file to the second mobile terminal.

36. The mobile terminal ofclaim 35, wherein the selection list comprises a first selection for transmitting the file to the first mobile terminal and a second selection for transmitting the file to the second mobile terminal.

37. The mobile terminal ofclaim 35, wherein a communication method between the computer and the first mobile terminal is different from a communication method between the first mobile terminal and the second mobile terminal.

38. The mobile terminal ofclaim 37, wherein the computer and the first mobile terminal are connected to each other via Wireless Fidelity (Wi-Fi) communication, and the first mobile terminal and the second mobile terminal are connected to each other via at least one of Third Generation (3G) mobile communication and Fourth Generation (4G) mobile communication.

39. The mobile terminal ofclaim 37, wherein the data receiving unit receives the file from the computer via a message, wherein the file is inserted into a message input window that is generated by the computer when the second selection is selected.

40. The mobile terminal ofclaim 37, wherein the data transmitting unit transmits an address book stored in the first mobile terminal to the computer and, wherein, when the second selection is selected, the address book is used in detection of a target to receive the file in response to a keyword that is input to the execution window.

41. The mobile terminal ofclaim 40, wherein the keyword comprises a tag value that is used to filter phone numbers that are searched for in response to the keyword.

42. A non-transitory computer-readable recording medium having recorded thereon a program for executing the method ofclaim 10, by using a computer.

43. A non-transitory computer-readable recording medium having recorded thereon a program for executing the method ofclaim 19, by using a computer.

Images