TWI671658B - Mobile terminal and method of executing function thereof,wearable device and method of executing sub-function thereof,and non-transitory computer-readable recording medium - Google Patents

Abstract

A mobile terminal includes: a communicator to communicate with a plurality of wearable devices; a memory to store capability information indicating the capabilities of the plurality of wearable devices; and a processor based on the capability information. Determining a first wearable device and a second wearable device among the plurality of wearable devices capable of performing a function of the mobile terminal, where the first wearable device is configured to perform a function of performing a function of the mobile terminal A first sub-function, the second wearable device is used to perform a second sub-function, and the second sub-function will be executed together with the first sub-function to perform the function of the mobile terminal, the processing The device is used to control the first wearable device to perform the first sub-function and to control the second wearable device to perform the second sub-function.

Description

Mobile terminal and its execution method, wearable device and its implementation Method for performing sub function and non-transitory computer-readable recording medium [Priority Statement]

This application claims Korean Patent Application No. 10-2014-0098635 filed on July 31, 2014, Korean Patent Application No. 10-2015-0000289 filed on January 2, 2015, and in 2015 The rights of Korean Patent Application No. 10-2015-0044551 filed on March 30, 2015, each of these Korean patent applications is filed at the Korean Intellectual Property Office, and the disclosure of these Korean patent applications The entire contents are incorporated into this case for reference.

One or more exemplary embodiments relate to a method for providing a function of a mobile terminal by using a plurality of wearable devices connected to the mobile terminal, and an electronic device thereof.

Various wearable devices can be operatively connected to the mobile terminal. One wearable device can be connected to the mobile terminal, or multiple wearable devices can be connected to the mobile terminal Mobile terminal. These wearable devices can perform specific operations according to specific purposes. For example, speakers or earphones that perform the audio output function of mobile devices and smart watches that complement the display function of mobile devices are available on the market. The mobile terminal performs multiple operations to perform specific functions. For example, the mobile terminal performs radio wave transmission or reception operations, audio input or output operations, and user interface (UI) operation operations to perform call functions. A headset with a microphone can be connected to a mobile terminal to perform audio input or output functions. However, since a general wearable device only performs a specific function, it may be difficult to perform all functions of the mobile terminal through a simple connection between a certain wearable device and the mobile terminal.

Therefore, there is a need for a system capable of performing a function of a mobile terminal without a separate user operation in accordance with a requested function using an operation of a wearable device connected to the mobile terminal.

Other aspects will be explained in part in the following description and these aspects will become partially obvious by the description, or may be known by practicing the exemplary embodiments.

According to an aspect of the exemplary embodiment, a mobile terminal includes: a communicator to communicate with a plurality of wearable devices; a memory to store capability information indicating capabilities of the plurality of wearable devices; and a processor To determine a first wearable device and a second wearable device of the plurality of wearable devices based on the capability information, and the first wearable device is configured to perform a function for performing the mobile terminal A first sub-function of the second wearable device for performing a second sub-function Yes, the second sub-function will be executed together with the first sub-function to perform the function of the mobile terminal, wherein the processor is used to control the first wearable device to perform the first sub-function And controlling the second wearable device to perform the second sub-function.

The processor may be used to control the communicator to transmit information about a user interface for performing the function of the mobile terminal to the first wearable device.

The processor may be used to access the capability information to determine that a wearable device of the plurality of wearable devices capable of performing a sub-function for performing the function of the mobile terminal is to be used to execute the wearable device. Sub-function wearable device.

The memory may further be used to store mapping information, and the mapping information may include device performance information and minimum performance information. The device performance information indicates device performance capabilities of the plurality of wearable devices. Represents the minimum performance required to execute the sub-functions for performing the functions of the mobile terminal, and the processor can be used to access the device performance information and the minimum performance information to determine The wearable device to be used to execute the sub-functions for performing the functions of the mobile terminal.

The processor may be used to access the device performance information and the minimum performance information to determine that the processor is capable of performing all the functions required for the sub-functions for performing the functions of the mobile terminal. The wearable device that states a sub-function is the wearable device that will be used to perform the sub-function.

The processor can be used to access the device performance information and the minimum Performance information to determine a wearable device of the plurality of wearable devices that will execute a user interface for performing the function of the mobile terminal.

The processor may be configured to use the sub-function execution result data of the first wearable device received from the first wearable device to control the second sub-function to be executed by the second wearable device.

According to an aspect of another exemplary embodiment, a mobile terminal includes: a communicator to communicate with a plurality of wearable devices; a memory to store capability information indicating capabilities of the plurality of wearable devices; and A processor for determining a first sub-function and a second sub-function based on the capability information, the first sub-function being executed by a first wearable device for performing a function of the mobile terminal, the The second sub-function is executed by the second wearable device together with the first sub-function to perform the function of the mobile terminal, wherein the processor may be used to control the communicator to communicate the first Information of a sub-function is transmitted to the first wearable device and information about the second sub-function is transmitted to the second wearable device.

According to another aspect of the exemplary embodiment, a mobile terminal includes: a communicator to communicate with a plurality of wearable devices; a memory to store mapping information, and the mapping information will be used to execute the mobile terminal A plurality of sub-functions of the functions of the plurality of wearable devices to be used to execute the plurality of sub-functions; and a processor to identify, based on the mapping information, among the plurality of wearable devices to perform the functions The connection of the first wearable device and the second wearable device of the plurality of sub-functions, wherein when the connection of the second wearable device is recognized, the processor may be used to control the communicator to be used for Information for performing a first sub-function is sent to the first A wearable device to execute the first sub-function together with a second sub-function to be performed by the second wearable device to perform the function of the mobile terminal, and when the second wearable is not recognized When the device is connected, the processor may be used to control the communicator to transmit information for performing the first sub-function to the first wearable device so that the second wearable device is not executed. In the case of the second sub-function, the first sub-function is executed to perform the function of the mobile terminal.

According to a further aspect of the exemplary embodiment, a wearable device includes: a communicator for receiving information from a mobile terminal for performing a first sub-function based on connection information, the connection information indicating that execution for performing Whether a plurality of wearable devices of a plurality of sub-functions of the functions of the mobile terminal are connected to the mobile terminal; and a processor configured to, when another wearable device is connected to the mobile terminal, based on the The information of the first sub-function and the first sub-function is executed together with a second sub-function to be executed by the other wearable device to perform the function of the mobile terminal, and when the other wearable When the device is not connected to the mobile terminal, the first sub-function is executed without performing the second sub-function of the other wearable device based on the information for performing the first sub-function Functions to perform the functions of the mobile terminal.

According to an aspect of another exemplary embodiment, a method for performing a function of a mobile terminal includes: generating capability information indicating a capability of a plurality of wearable devices; and determining a capability of the plurality of wearable devices based on the capability information. A first wearable device and a second wearable device, the first wearable device is used to perform a first sub-function for performing a function of the mobile terminal, and the second wearable device is used to perform a first Two sub-functions, the second sub-function will be executed together with the first sub-function to perform the function of the mobile terminal; controlling the first wearable device to perform the first sub-function; and controlling the The second wearable device performs the second sub-function.

The method may further include transmitting information about a user interface for performing the function of the mobile terminal to the first wearable device.

The method may further include determining, based on the capability information, a wearable device of the plurality of wearable devices capable of performing a sub-function for performing the function of the mobile terminal as a device that will perform the sub-function. Wearable device.

The method may further include: storing mapping information in the mobile terminal, the mapping information including device performance information and minimum performance information, the device performance information indicating device performance capabilities of the plurality of wearable devices, the The minimum performance information indicates a minimum performance required to execute the sub-functions for performing the functions of the mobile terminal, and the determining step may include analyzing the device performance information and the minimum performance Information to determine the wearable device that will perform the sub-functions for performing the functions of the mobile terminal.

The determining step may include analyzing the device performance information and the minimum performance information to determine that the sub-function can be executed with a performance required for performing the sub-function of the function of the mobile terminal. The wearable device that functions is the wearable device that will perform the sub-function.

The method may further include analyzing the device performance information and the minimum performance information to determine a wearable device among the plurality of wearable devices that will execute a user interface for performing the function of the mobile terminal. .

The method may further include using the sub-function execution result data of the first wearable device received from the first wearable device to control the second subfunction to be executed by the second wearable device.

According to another aspect of the exemplary embodiment, a method for performing a function of a mobile terminal includes: generating capability information indicating capabilities of a plurality of wearable devices; and determining a first sub-function and a second sub-function based on the capability information. The first sub-function is performed by a first wearable device for performing a function of the mobile terminal, and the second sub-function is performed by a second wearable device together with the first sub-function Transmitting information about the first sub-function to the first wearable device; and transmitting information about the second sub-function to the second wearable device.

According to an aspect of still another exemplary embodiment, a method for performing a function of a mobile terminal includes: generating mapping information, the mapping information mapping a plurality of sub-functions for performing functions of the mobile terminal to be used for performing all functions. A plurality of wearable devices of the plurality of sub-functions; identifying the first wearable device and the second of the plurality of wearable devices to perform the plurality of sub-functions based on the mapping information stored in the memory; Connection of a wearable device; and transmitting information to the first wearable device, wherein the step of transmitting the information to the first wearable device includes: when the second wearable device is identified During the connection, information for performing a first sub-function is transmitted to the first wearable device to execute the first sub-function together with a second sub-function to be performed by the second wearable device to Execute the function of the mobile terminal; and when the connection of the second wearable device is not recognized, transmit information for performing a first sub-function to the first wearable A device to execute the first sub-function without executing the second sub-function of the second wearable device to perform the function of the mobile terminal.

According to an aspect of another exemplary embodiment, a method for performing a sub-function of a wearable device includes: receiving information for performing a first sub-function according to connection information, the connection information indicating to perform an action for performing an action Whether multiple wearable devices with multiple sub-functions of the function of the terminal are connected to the mobile terminal; when another wearable device is connected to the mobile terminal, based on the information for performing the first sub-function, Executing the first sub-function together with a second sub-function to be performed by the other wearable device to perform the function of the mobile terminal; and when the other wearable device is not connected to the mobile terminal And, based on the information for executing the first sub-function, execute the first sub-function without performing the second sub-function of the other wearable device to perform all the actions of the mobile terminal. Mentioned function.

According to another aspect of the exemplary embodiment, there is provided a non-transitory computer-readable recording medium having a program embedded therein for causing a computer to execute one of the above methods.

110‧‧‧Mobile terminal

120‧‧‧ The first wearable device

130‧‧‧Second wearable device

210‧‧‧ The first wearable device

220‧‧‧Mobile Terminal

230‧‧‧Second wearable device

510‧‧‧Smart Watch

520‧‧‧Smartphone

521‧‧‧Operation

522‧‧‧operation

530‧‧‧Headphones

582‧‧‧ Operation

584‧‧‧operation

1110‧‧‧Caller number display object

1120‧‧‧Call Acceptance Control Object

1130‧‧‧Call Rejection / Message Transfer Object

1210‧‧‧Caller number display object

1220‧‧‧ Call time display object

1230‧‧‧ Audio control object added

1240‧‧‧Audio reduction control object

1250‧‧‧ Call end object

1421‧‧‧First operation execution request

1422‧‧‧ second operation execution request

1521‧‧‧Wireless network

1522‧‧‧Wired Network

1621‧‧‧Bluetooth communication

1622‧‧‧Bluetooth communication

1721‧‧‧WiFi connection

1722‧‧‧Bluetooth connection

2021‧‧‧The first operation execution result data

2022‧‧‧Second operation execution request

2111‧‧‧Call Accept Request

2122‧‧‧Operation

2211‧‧‧ Operation

2221‧‧‧ Operation

2222‧‧‧ Operation

2231‧‧‧ Operation

2311‧‧‧ Operation

2322‧‧‧ Operation

2421‧‧‧ Operation

2431‧‧‧ Operation

6010‧‧‧Smart Watch

6020‧‧‧Smartphone

6030‧‧‧Headphone

6210‧‧‧Smart Watch

6220‧‧‧Smartphone

6230‧‧‧Smart Glasses

6231‧‧‧Headphone

6810‧‧‧Smart Watch

6819‧‧‧ Operation

6820‧‧‧Smartphone

6830‧‧‧Smart Glasses

6831‧‧‧ Operation

6832‧‧‧Smart shoes

6833‧‧‧Vibration ability

6834‧‧‧Headphone

6835‧‧‧Audio output capability

7510‧‧‧Smart Watch

7520‧‧‧Smart Glasses

7530‧‧‧Smartphone

7540‧‧‧Smart shoes

7610‧‧‧Smart Watch

7611‧‧‧ Display capability

7620‧‧‧Smartphone

7630‧‧‧Headphone

7631‧‧‧Audio output capability

7810‧‧‧Smart Watch

7820‧‧‧Smartphone

7830‧‧‧Headphone

8300‧‧‧Mobile Terminal

8310‧‧‧Communication Unit

8311‧‧‧Short Range Wireless Communication Unit

8312‧‧‧Mobile Communication Unit

8313‧‧‧Broadcast receiving unit

8320‧‧‧Memory

8321‧‧‧User Interface Module

8322‧‧‧Touch screen module

8323‧‧‧Notification Module

8324‧‧‧ pronunciation-body module

8325‧‧‧Content storage module

8330‧‧‧Processor

8340‧‧‧User input unit

8350‧‧‧Output unit

8351‧‧‧Display unit

8352‧‧‧Audio output unit

8353‧‧‧Vibration motor

8360‧‧‧Sensing unit

8361‧‧‧Geomagnetic sensor

8362‧‧‧Acceleration sensor

8363‧‧‧Temperature / Humidity Sensor

8364‧‧‧Infrared sensor

8365‧‧‧Gyroscope sensor

8366‧‧‧Position sensor

8367‧‧‧Pressure sensor

8368‧‧‧ Proximity sensor

8369‧‧‧RGB sensor (brightness sensor)

8370‧‧‧Audio / video input unit

8371‧‧‧Camera

8372‧‧‧Microphone

8500‧‧‧ Wearable

8510‧‧‧communication unit

8511‧‧‧Short-range wireless communication unit

8512‧‧‧Mobile communication unit

8513‧‧‧Broadcast receiving unit

8520‧‧‧Memory

8530‧‧‧ processor

8540‧‧‧user input unit

8550‧‧‧Output unit

8560‧‧‧Sensing unit

8570‧‧‧Audio / video input unit

S212, S222, S224, S226, S228, S232‧‧‧ Operation

S310, S320, S330, S340, S350‧‧‧ Operation

S412, S414, S416, S418‧‧‧ Operation

S512, S514, S522, S524, S526, S528, S532, S534‧‧‧ Operation

S710, S720, S730‧‧‧ Operation

S1010, S1020, S1030, S1040, S1050‧‧‧ Operation

S2512, S2514, S2522, S2526, S2528, S2529, S2532, S2534‧‧‧ Operation

S2610, S2620, S2630, S2640‧‧‧ Operation

S2650, S2660, S2670, S2680‧‧‧ Operation

S2712, S2714, S2722, S2724, S2732, S2734, S2726‧‧‧ Operation

S3712, S3714, S3722, S3724, S3726, S3728, S3729, S3732, S3734‧‧‧ Operation

S3810, S3820‧‧‧ Operation

S4110, S4120‧‧‧ Operation

S5310, S5320‧‧‧ Operation

S5411, S5421‧‧‧ Operation

S5610, S5620, S5630, S5640‧‧‧ Operation

S5710, S5720, S5730, S5740‧‧‧ Operation

S5810, S5820, S5830, S5840‧‧‧ Operation

S5910, S5920, S5930‧‧‧ Operation

S6012, S6014, S6022, S6024, S6026, S6028, S6029, S6032, S6034, S6082, S6084‧‧‧ Operation

S6110, S6120, S6130‧‧‧ Operation

S6212, S6214, S6216, S6220, S6222, S6223, S6224, S6225, S6226, S6232‧‧‧ Operation

S6812, S6814, S6815, S6820, S6822, S6824, S6825, S6826, S6827, S6828, S6832, S6833, S6834, S6835, S6836, S6838‧‧‧ Operation

S7511, S7521, S7522, S7532, S7534, S7536, S7538, S7541, S7542‧‧‧ Operation

S7612, S7614, S7620, S7622, S7624, S7626, S7632, S7634‧‧‧ Operation

S7811, S7812, S7814, S7820, S7821, S7822, S7824, S7831, S7832‧‧‧ Operation

These and / or other aspects will become more apparent and easier to understand by reading the following description of the exemplary embodiments in conjunction with the accompanying drawings, in which: FIG. 1 is a diagram for explaining functions according to an exemplary embodiment Provide a diagram of the system.

FIG. 2 is an operation of a function providing system according to an exemplary embodiment Flowchart.

FIG. 3 is a flowchart of an operation of a mobile terminal according to an exemplary embodiment.

FIG. 4 is a flowchart of an operation of a first wearable device according to an exemplary embodiment.

Figures 5, 6, 7, 8, 9, 10, 11, 11, 12, 13, 14, 15, 15, 16, 17, 18, 19, 20, 21 22, 23, and 24 are diagrams for explaining a method for a function providing system to provide a call function of a mobile terminal according to an exemplary embodiment.

FIG. 25 is a flowchart of an operation of a function providing system according to an exemplary embodiment.

26A and 26B are flowcharts of a method for a mobile terminal to request a wearable device to perform an operation to perform a function of the mobile terminal according to an exemplary embodiment.

FIG. 27 is a flowchart of a method for causing a function providing system to receive capability information about a wearable device and generate capability information from a wearable device according to an exemplary embodiment.

FIG. 28, FIG. 29, FIG. 30, and FIG. 31 are block diagrams of a data structure that stores capability information about a wearable device in a wearable device according to an exemplary embodiment.

FIG. 32, FIG. 33, FIG. 34, FIG. 35, and FIG. 36 are diagrams illustrating capabilities of a wearable device stored in a mobile terminal according to an exemplary embodiment. Infographic.

37 and 38 are flowcharts of a method of operating a function providing system in consideration of capabilities according to an exemplary embodiment.

FIG. 39 is a diagram for explaining a method of dividing a call function among a plurality of functions that can be performed by a mobile terminal into a plurality of operations.

FIG. 40 is a diagram illustrating a data structure for a mobile terminal to store capability information corresponding to an operation according to an exemplary embodiment.

FIG. 41 is a flowchart of a method for causing a mobile terminal to determine an operation execution subject according to an exemplary embodiment.

FIG. 42 is a diagram illustrating operations performed and capabilities required for the operations performed by the mobile terminal when performing functions, according to an exemplary embodiment.

FIG. 43 is a conceptual diagram for explaining a method of using a capability information about a wearable device stored in a mobile terminal to find a wearable device capable of performing an operation.

FIG. 44 is a diagram illustrating capability information about a wearable device stored in a memory of a mobile terminal according to an exemplary embodiment.

FIG. 45 is a flowchart of a method of designating a device for performing an operation when a mobile terminal successfully searches for a plurality of devices with specific capabilities, according to an exemplary embodiment.

FIG. 46, FIG. 47, FIG. 48, and FIG. 49 are examples for illustrating a mobile terminal selecting a first wearable device and a Kth wearable device as a plurality of wearable devices with display capabilities according to an exemplary embodiment Illustration.

50, 51, and 52 are diagrams illustrating a method for enabling a mobile terminal to compare hardware performance of multiple wearable devices according to an exemplary embodiment.

FIG. 53 is a flowchart of a method for causing a mobile terminal to select a wearable device that will perform an operation from a plurality of wearable devices according to another exemplary embodiment.

FIG. 54 is a flowchart of a method for a mobile terminal to select a wearable device to perform an operation from a plurality of wearable devices in consideration of situation information according to an exemplary embodiment.

FIG. 55 is a diagram illustrating a method for causing a mobile terminal to store situation information data of a wearable device in a memory according to an exemplary embodiment.

FIG. 56 is a flowchart of a method for a mobile terminal to determine a device having a capability to perform an operation among a plurality of devices according to an exemplary embodiment.

57 and 58 are flowcharts of a method for causing a mobile terminal to determine a device for performing operations among a plurality of devices according to another exemplary embodiment.

FIG. 59 is a flowchart of a method for causing a mobile terminal to provide a user interface (UI) to a wearable device according to an exemplary embodiment.

FIG. 60 is a flowchart of a method for providing a call function according to an exemplary embodiment.

61 is a flowchart of a method for a smart phone to determine that it is to be transmitted to a user interface of a smart watch in a method of providing a call function according to an exemplary embodiment.

62, 63, and 64 are diagrams illustrating a method for providing a private information display function according to an exemplary embodiment.

65, 66, and 67 are diagrams illustrating a method for providing a private information display function according to another exemplary embodiment.

68 and 69 are diagrams for explaining a method for providing a navigation function according to an exemplary embodiment.

FIG. 70 is a diagram for explaining a method of providing a navigation function according to another exemplary embodiment.

FIG. 71 is a flowchart of a method for providing a navigation function according to an exemplary embodiment.

72 and 73 are diagrams for explaining a method for providing a navigation function according to still another exemplary embodiment.

74 and 75 are diagrams for explaining a method for providing a navigation function according to still another exemplary embodiment.

76 and 77 are diagrams illustrating a method for providing a music playback function according to an exemplary embodiment.

78, 79, 80, 81, and 82 are diagrams illustrating a method for providing a biometric information measurement function according to an exemplary embodiment.

83 and 84 are block diagrams illustrating a configuration of a mobile terminal according to an exemplary embodiment.

FIG. 85, FIG. 86, and FIG. 87 are diagrams for a method according to an exemplary embodiment. A block diagram illustrating the configuration of a wearable device.

Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings, wherein like reference numerals refer to the like elements throughout. In this regard, the exemplary embodiments may have different forms and should not be construed as limited to the descriptions set forth herein. Therefore, only the exemplary embodiments are explained below with reference to the drawings to explain aspects of the present description. As used herein, the term "and / or" includes any and all combinations of one or more of the associated listed items. Expressions such as "at least one of" when preceding a series of elements modify the entire series of elements, rather than modifying only individual elements of the series.

The terminology used in this specification is a general term currently widely used in the technology in consideration of the functions of the exemplary embodiments, but the term may be based on the intention, precedent, or the term of a person having ordinary knowledge in the technology. New technologies in technology have changed. Further, the specific term may be selected by the applicant, and in this case, the detailed meaning of the specific term will be set forth in the detailed description of the exemplary embodiment. Therefore, the terms used in the specification should not be understood as simple names, but based on the meaning of the terms and the general description of the exemplary embodiments.

It will also be understood that, unless otherwise defined, when the terms "comprises, includes" and "has" are used herein, they are used to indicate the presence of the stated element, but do not exclude the presence of other elements Or add. In addition, the terms "unit" and "module" as used in this article mean to handle at least one function or operation. Operating unit, which may be implemented by hardware, software, or a combination of hardware and software.

The term "short-range wireless communication" as used herein can refer to wireless local area network (LAN) (Wi-Fi), Bluetooth, ZigBee, Wi-Fi Direct (WFD), Ultra Wide Band (Ultra At least one of Wideband (UWB), Infrared Data Association (IrDA), Bluetooth Low Energy (BLE), near field communication (NFC), and Ant +, but not limited to this .

A wireless local area network (Wi-Fi) may include an infrastructure mode and an ad-hoc mode. In the infrastructure mode, an access point (AP) that transmits wireless signals exists. Data is exchanged with multiple terminals within a predetermined range around the access point. In a specific mode, multiple terminals exchange data with each other in a peer-to-peer (P2P) manner without access points.

Bluetooth is a standard technology that enables wireless communication devices to use low energy to perform wireless communication between them within a short range. Ultra-wideband is a wireless communication technology that uses low energy to transfer large amounts of data in a short period of time via a large frequency spectrum.

Wi-Fi Direct is a new version of Wi-Fi technology, and its main feature is that Wi-Fi Direct includes direct communication between devices. For example, devices equipped with Wi-Fi Direct can communicate with each other and share information with each other even when no hotspot, router, or access point is provided.

ZigBee is one of the Institute of Electrical and Electronic Engineers (IEEE) 802.15.4 standards that support short-range wireless communications. ZigBee is a type used to carry out at a distance of 10 meters to 20 meters Short-range wireless communication and ubiquitous computing technology in a wireless network environment, such as an environment established in a home or office.

Bluetooth low energy refers to the core function of Bluetooth V4.0. Bluetooth V4.0 is a short-range communication technology among various short-range communication technologies. Compared with the classic Bluetooth specification, Bluetooth low energy can have a relatively small duty cycle, can be produced at low cost, and can operate on coin-sized batteries for several years due to reduced average power and standby power.

Near field communication is a radio frequency identification (RFID) or electronic tag, which refers to a contactless short-range wireless communication using a frequency band of 13.56 million hertz (MHz). Near field communication uses short-range wireless communication technology to achieve data communication between devices at a distance of 10 cm. The near field communication may include a point-to-point mode, a reader / writer (R / W) mode, and a card emulation mode. Ant + refers to a wireless communication technology with low power consumption, and is used for short-range communication using the 2.4 gigahertz (GMHz) frequency band.

Exemplary embodiments will be explained with reference to the drawings so that the exemplary embodiments can be easily implemented by those having ordinary skill in the art. However, the exemplary embodiments may be implemented in various forms and are not limited to the exemplary embodiments described herein. In addition, for the sake of clarity and conciseness, descriptions of well-known functions and structures will be omitted, and similar reference numerals will be given to similar components throughout the specification.

FIG. 1 is a diagram for explaining a function providing system according to an exemplary embodiment.

Referring to FIG. 1, a function providing system according to an exemplary embodiment may include a mobile terminal 110, a first wearable device 120, and a second wearable device 130. The mobile terminal 110 according to an exemplary embodiment may provide functions of the mobile terminal 110 using operations of the mobile terminal 110 and the wearable devices 120 and 130 according to a connection state of the wearable devices 120 and 130 connected to the mobile terminal 110.

The term "function" as used herein may refer to performing at least one operation to achieve a specific goal. Execution of at least one operation for performing a function may refer to execution of at least one sub-function for performing the function.

For example, the functions described herein may be performed by executing at least one sub-function to achieve a specific goal. For example, in a situation where at least one operation needs to be performed to perform a function, the function may be performed by executing each sub-function for performing each operation. The sub-functions required for performing the functions may be performed to perform operations corresponding to each sub-function.

The term "ability" can refer to whether a particular type of operation can be performed. Functions, capabilities, and operations can be described in terms of devices. Performing a function of the device may refer to performing at least one operation performed by the device to achieve a specific goal. The capability of a device may refer to whether a particular device is capable of performing a particular type of operation.

Examples of functions may include a call function, a privacy protection function, a memo function, a multimedia playback function, a biological information measurement function, and a navigation function. However, the exemplary embodiment is not limited thereto. Examples of capabilities may include communication capabilities, information storage capabilities, audio output capabilities, and display capabilities. However, the exemplary embodiment is not limited thereto. Examples of operations can include communication operations, information storage operations, audio input Operation and display operation. However, the exemplary embodiment is not limited thereto. The execution of each operation may refer to the execution of a sub-function of the function. A function type, a capability type, and an operation type for determining the function, the capability, and the operation may be determined in advance.

The functions, capabilities, and operations will be explained in more detail with reference to the call function. The mobile terminal 110 performing a call function may perform a communication operation, an audio output operation, and an audio input operation to perform a plurality of sub-functions for performing a call function, and the communication operation is performed with the base station using a 2G, 3G, or 4G communication method. For wireless communication, the audio output operation uses a speaker to provide the user with received audio data as audio information, and the audio input operation generates voice data by recording a user's voice from a microphone. In addition, the mobile terminal 110 may perform a calling function by performing an operation of providing a user interface (UI).

The functionality, capabilities, and operation of the privacy protection function will now be explained. The mobile terminal 110 may perform the privacy protection function by performing a display operation, an audio output operation, and a display operation to perform a plurality of sub-functions for performing the privacy protection function. The previous display operation uses a display unit to display for asking the user whether to turn on The user interface of the privacy protection mode. The audio output operation provides the user with information to be provided as audio information to the user when the mode is the privacy protection mode. The latter display operation is not privacy in the mode The protected mode provides the user with information to be provided to the user as visual information.

The capability of a device may be determined according to the type of operation of the device based on whether the corresponding device has a specific capability. For example, if the headset is capable of performing audio output operations, the device may be determined to have audio output capabilities. If the headset includes a microphone And the audio input operation can be performed by performing audio recording, the device can be determined to have audio input capabilities. If the headset can perform Bluetooth communication operations, the device can be determined to have wireless communication capabilities.

For example, a device may perform operations based on its capabilities. A device may perform a specific function by performing at least one operation.

For example, the mobile terminal 110 may perform a call function. The mobile terminal 110 may perform a call function by performing a communication operation, an audio output operation, and an audio input operation. In this example, the mobile terminal 110 may include communication capabilities, audio output capabilities, and audio input capabilities to perform a call function. For example, the call function may include an audio input operation, an audio output operation, and a communication operation. The audio input operation is performed using a microphone having an audio input capability, and the audio output operation is performed using a speaker having an audio output capability. The communication operation is performed by using a communication unit having a communication capability.

The mobile terminal 110 according to an exemplary embodiment may provide operations of the mobile terminal 110 using operations performed by a plurality of wearable devices connected to the mobile terminal 110. The mobile terminal 110 according to an exemplary embodiment may determine whether the plurality of wearable devices are connected to the mobile terminal 110. The mobile terminal 110 according to an exemplary embodiment may obtain information about operations that can be performed by the wearable device connected to the mobile terminal 110 from the wearable device. In addition, the mobile terminal 110 according to an exemplary embodiment may store information about operations that can be performed by a wearable device connected to the mobile terminal 110 in a memory in advance. The mobile terminal 110 can determine whether the wearable device can perform the operation and interact with the operation of the wearable device connected to the mobile terminal 110 Work to perform the functions of the mobile terminal 110.

The mobile terminal 110 according to an exemplary embodiment may perform a connection with at least one wearable device. The mobile terminal 110 may transmit and receive data by performing a connection with at least one wearable device. The mobile terminal 110 may be a portable terminal (such as a smart phone and a personal computer (PC)), a fixed terminal (such as a desktop personal computer), or a repeater (such as a home network server)器). However, the exemplary embodiment is not limited thereto.

The mobile terminal 110 can recognize a wearable device connected to the mobile terminal 110. The mobile terminal 110 may generate capability information, that is, information about operations that can be performed by a wearable device connected to the mobile terminal 110. For example, the mobile terminal 110 may receive information from the wearable device about operations that can be performed by the wearable device connected to the mobile terminal 110. The mobile terminal 110 may receive capability information about the wearable device from the wearable device, and store the capability information about the wearable device in a memory. The mobile terminal 110 may include at least one of a memory and a database as a storage. In addition, the mobile terminal 110 may store capability information about certain wearable devices in advance. For example, the mobile terminal 110 may store the capability information about the wearable device issued by the same company in the memory in advance. In addition, the mobile terminal 110 may receive information about operations that can be performed by the wearable device from the wearable device or an external device (for example, a personal computer or a server), instead of storing the capability information in advance. For example, when the mobile terminal 110 is connected to a wearable device, the mobile terminal 110 may receive capability information about the wearable device connected to the mobile terminal 110 from the wearable device. Hereinafter, the mobile terminal will be explained in detail with reference to the exemplary embodiments. 110. Various situations or conditions for receiving capability information about a wearable device.

The capability information about the wearable device stored in the memory can be updated. For example, in a case where the mobile terminal 110 receives new capability information in a state where the mobile terminal 110 stores the capability information, the mobile terminal 110 may update the pre-stored capability information. In order to update the capability information, the mobile terminal 110 may request the capability information from the wearable device when the mobile terminal 110 is connected to the wearable device, or may periodically request the capability from the wearable device after the mobile terminal 110 is connected to the wearable device. Information. In addition, once an event such as a user input occurs, the mobile terminal 110 may request the capability information from the wearable device. To update the capability information, the mobile terminal 110 may request the capability information from an external device (for example, a personal computer or a server).

In the case where the capability information about the wearable device is updated, the entire capability information about operations that can be performed by the wearable device may be received and updated, or only the information about the wearable device corresponding to the specific function of the mobile terminal may be received and updated Capability information. In addition, the pre-stored information about the change in the capability information of the mobile terminal 110 may be only partially updated.

Version information can be used to manage the update of capability information. For example, the mobile terminal 110 may compare the version information of the pre-stored capability information with the version information of the new capability information used for updating, and perform it when the version information of the new capability information is later than the pre-stored capability information. Update. The capacity can be compared by comparing the operating performance. Performance information can be used to express how well a wearable device performs a specific operation. Use performance information to compare capabilities. As mentioned above, available Performance information to manage the performance of the wearable device in performing certain operations. Performance information can be stored in the wearable device in advance, or performance information measured by the wearable device can be stored. In addition, the mobile terminal 110 may receive performance information about the wearable device from the wearable device, and store and manage the performance information about the wearable device. Performance information can be managed in a state contained in capability information. Update performance information. For example, when the mobile terminal 110 receives new performance information in a state where the mobile terminal 110 stores performance information, the mobile terminal 110 may update the pre-stored performance information. In order to update performance information, the mobile terminal 110 may request performance information from the wearable device when the mobile terminal 110 is connected to the wearable device, or may periodically request performance from the wearable device after the mobile terminal 110 is connected to the wearable device. Information. In addition, when an event such as a user input occurs, the mobile terminal 110 may request performance information from the wearable device. In order to update the performance information, the mobile terminal 110 may request the performance information from an external device (such as a personal computer or a server).

An example of using performance information to compare capabilities is described below. For example, when the data transmission performance information of the first wearable device 120 using the orthogonal frequency division multiplexing (OFDM) communication method to perform the wireless communication operation is greater than the information about the use of the code division multiplexing access (code division multiple access, CDMA) communication method to perform the wireless communication operation of the data transmission performance information value of the second wearable device 130, it can be determined that the data transmission performance of the first wearable device 120 is greater than that of the second wearable device. Data transfer performance. In this way, the mobile terminal 110 can The data transmission performance information of the second wearable device 130 and the second wearable device 130 are compared, and it is determined that the data transmission capacity of the first wearable device 120 is relatively higher than that of the second wearable device 130. In addition, the mobile terminal 110 may determine that the wireless communication capability including the data transmission capability is relatively higher in the first wearable device 120 than in the second wearable device 130.

You can use common units to express performance information based on ability types. Therefore, the magnitudes of capabilities can be compared numerically with each other. For example, wireless communication capabilities can be compared with each other based on the bit rate per second. The mobile terminal 110 may determine whether to use the operation of the wearable device according to the connection state of the wearable device connected to the mobile terminal 110. For example, when the wearable device is disconnected from the mobile terminal 110, the mobile terminal 110 may determine the operation without using the wearable device.

The mobile terminal 110 may determine whether to use an operation of the wearable device according to a setting state of the wearable device connected to the mobile terminal 110. For example, a wearable device may be set to not allow control from other devices. In this case, the mobile terminal 110 may not control the corresponding wearable device. Therefore, the mobile terminal 110 can determine an operation without using the corresponding wearable device.

The first wearable device 120 and the second wearable device 130 according to an exemplary embodiment may be devices connected to the mobile terminal 110 to transmit data to the mobile terminal 110 and receive data from the mobile terminal 110. A wearable device may refer to a device used while being worn on or attached to a user's body. However, the exemplary embodiment is not limited thereto. The first wearable device 120 and the second wearable device 130 may be devices that operate at positions spaced from the user's body.

The first wearable device 120 and the second wearable device 130 according to an exemplary embodiment may be connected to the mobile terminal 110 via a wired network or a wireless network. For example, the first wearable device 120 and the second wearable device 130 may be connected to the mobile terminal 110 via the same network. According to another exemplary embodiment, the first wearable device 120 and the second wearable device 130 may be connected to the mobile terminal 110 via different networks.

The first wearable device 120 and the second wearable device 130 according to an exemplary embodiment may provide the mobile terminal 110 with its executable operation information and / or its capability information. The first wearable device 120 and the second wearable device 130 according to an exemplary embodiment may perform related operations in response to an operation execution request from the mobile terminal 110.

FIG. 2 is a flowchart of an operation of a function providing system according to an exemplary embodiment. In operation S222, the mobile terminal 220 may generate mapping information about a plurality of wearable devices. The mapping information may be information representing a wearable device performing an operation required when performing a specific function. For example, mapping information can represent actions required to perform a particular function. The mapping information may represent a wearable device for performing a desired operation. For example, the mapping information may indicate that a request to perform a specific operation is to be transmitted to a specific device. Mapping information may include information about which operation a particular device performs to perform a particular function.

For example, in order to perform a call function, the mobile terminal 220 may set the following mapping information. The mapping information may represent the use of headphones in multiple wearable devices to perform audio output operations. The mapping information may indicate that the audio output request and audio data are to be transmitted to the headsets in multiple wearable devices. The mapping information may represent the use of microphones in multiple wearable devices to perform audio input operations. Mapping information can indicate The input signal is transmitted to the microphones in the plurality of wearable devices. The microphone can be set in the headset. The mapping information may represent providing a smart watch with a user interface that is provided to a user to perform a call function. The mapping information may indicate that the user interface data and a request to execute the user interface provided to the user to perform a calling function should be transmitted to the smart watch.

According to another exemplary embodiment, in order to perform a privacy protection function, the mobile terminal 220 may set the mapping information as follows. The mapping information may represent providing a smart watch with a user interface that is provided to the user to perform privacy protection functions. The mapping information may indicate that the user interface data and a request to execute the user interface provided to the user to perform the privacy protection function should be transmitted to the smart watch. When the information to be provided to the user is private information, the mobile terminal 220 may provide the information in the form of auditory information through a headset. When the information to be transmitted to the user is not private information, the mobile terminal 220 may provide the information in the form of visual information through a smart watch. In order for the mobile terminal 220 to provide such information to the user, the mapping information may indicate that it is intended to provide auditory information through headphones in multiple wearable devices, and smart watches that want to provide visual information to multiple wearable devices. The mobile terminal 220 may use the mapping information to determine to which wearable device the auditory information is to be provided and to which wearable device the visual information is to be provided.

According to another exemplary embodiment, in order to perform a music playback function, the mobile terminal 220 may set the mapping information as follows. The mapping information may represent the use of headphones in multiple wearable devices to perform audio output operations. The mapping information may indicate that the audio output request and the music audio data are to be transmitted to the headphones in the plurality of wearable devices. Mapping Resources The message may indicate that the smart watch is provided with a user interface provided to the user to perform a music playback function. The mapping information may indicate that the user interface data and a request to execute a user interface provided to the user to perform a music playback function should be transmitted to the smart watch.

The mobile terminal 220 may store mapping information about at least one wearable device in a memory in advance. In addition, when the wearable device is connected to the mobile terminal 220, the mobile terminal 220 may generate mapping information about operations performed by the wearable device through a communication method or a communication module used when the wearable device is connected. In addition, the mobile terminal 220 may download capability information about at least one wearable device from an external device (for example, a personal computer or a server), or may directly receive capability information about at least one wearable device from a corresponding wearable device. The mapping information can be updated periodically. For example, in a case where the mobile terminal 220 receives new mapping information in a state where the mobile terminal 220 stores the mapping information, the mobile terminal 220 may update the pre-stored mapping information. To update the mapping information, the mobile terminal 220 may request the mapping information from the wearable device when the mobile terminal 220 is connected to the wearable device, or may periodically request the mapping from the wearable device after the mobile terminal 220 is connected to the wearable device. Information. In addition, once an event such as a user input occurs, the mobile terminal 220 may request mapping information from the wearable device. To update the mapping information, the mobile terminal 220 may request the mapping information from an external device (such as a personal computer or a server).

In operation S224, the mobile terminal 220 may check the connection of the wearable device based on the mapping information. The mobile terminal 220 may check the connection based on the mapping information Whether the wearable device to the mobile terminal 220 remains connected to the mobile terminal 220. For example, the mobile terminal 220 may refer to the mapping information to check whether the mobile terminal 220 is connected to the wearable device specified in the mapping information to perform a calling function. For example, the mobile terminal 220 may check whether the earphone for audio output is connected to the mobile terminal 220 by referring to the mapping information. The mobile terminal 220 may use a wireless communication method (for example, Bluetooth or ZigBee) to connect to the headset. For example, the mobile terminal 220 may check whether the smart watch used to provide a user interface is connected to the mobile terminal 220 by referring to the mapping information. The mobile terminal 220 may be connected to the smart watch using a wireless communication method (for example, Bluetooth or ZigBee).

In operation S226, the mobile terminal 220 may transmit a first operation execution request to the first wearable device 210. The mobile terminal 220 may transmit the first operation execution request to the operation execution subject determined based on the mapping information.

For example, the mobile terminal 220 may refer to the mapping information and send an operation execution request to the wearable device specified in the mapping information to perform a call function. For example, when the first operation is an audio output operation, the mobile terminal 220 may refer to the mapping information to send audio data and a request to perform an audio output operation to the headset to output audio data. In addition, when the first operation is a user interface providing operation, the mobile terminal 220 may refer to the mapping information to send the user interface data and a request to provide the user interface to the smart watch to provide the user interface.

In operation S212, the first wearable device 210 may perform a first operation. The first wearable device 210 may perform the first operation in response to the first operation execution request received from the mobile terminal 220. The first wearable device 210 may serve as a first The result of the operation produces a first operation execution result. The first operation execution result may be an output generated when the first wearable device 210 performs the first operation, and may be generated as many different types of output information. For example, the first wearable device 210 may perform a first operation to output audio data, output vibration, display a screen, or generate data processing result data. The output generated by the first wearable device 210 is not limited to the above example. If necessary, the first wearable device 210 may transmit a first operation execution result to the mobile terminal 220. The first wearable device 210 may transmit result data generated as a result of the first operation execution to the mobile terminal 220.

In operation S228, the mobile terminal 220 may transmit a second operation execution request to the second wearable device 230. The mobile terminal 220 may use the mapping information to transmit a second operation execution request to the second wearable device 230. The second operation execution request may be transmitted before the first wearable device 210 performs the first operation, may be transmitted at the same time as the first operation is performed, or may be transmitted after the execution of the first operation is completed.

The mobile terminal 220 may transmit a second operation execution request to the second wearable device 230 so that the second wearable device 230 performs the second operation to be performed while the first wearable device 210 is operating to perform the mobile terminal 220. Functions. The simultaneous execution of the first operation and the second operation is not limited to the simultaneous execution of the first operation and the second operation, but may also mean that both the first operation and the second operation are performed within a certain time frame of each other. The functions of the mobile terminal 220 are performed.

The mobile terminal 220 may transmit the second operation execution request to the operation execution subject determined based on the mapping information. For example, when the second operation is an audio output operation, the second operation execution request may be transmitted to an audio output based on the mapping information. Output-operated second wearable device.

In operation S232, the second wearable device 230 may perform a second operation. The second wearable device 230 may perform the second operation in response to the second operation execution request received from the mobile terminal 220.

FIG. 3 is a flowchart of an operation of the mobile terminal 220 according to an exemplary embodiment. In operation S310, the mobile terminal 220 according to an exemplary embodiment may generate mapping information about an operation for performing a function of the mobile terminal 220 and a wearable device that will perform the operation.

As described above, a function may include at least one operation. In addition, operations can be shaped based on capabilities. The mapping information may indicate which operation the wearable device connected to the mobile terminal 220 can perform. In addition, the mapping information may indicate whether the wearable device is connected to the mobile terminal 220.

As described above, the mobile terminal 220 may store the mapping information about the at least one wearable device in the memory in advance. When the wearable device is connected to the mobile terminal 220, the mobile terminal 220 can store information about the communication method or communication module used when the wearable device is connected to the mobile terminal 220, and generate information about the Mapping information for operations performed by the device. In addition, the mobile terminal 220 may download the capability information about the at least one wearable device from an external device (for example, a personal computer or a server), or directly receive the capability information about the at least one wearable device from the corresponding wearable device and The received capability information is stored in memory to generate mapping information. The memory may include any type of storage medium. Examples of memory can include volatile memory and non-volatile memory body. The memory may include a disk-shaped storage medium.

In operation S320, the mobile terminal 220 may use the mapping information stored in the memory to check the connection of the first wearable device 210 and the second wearable device 230 to perform related operations. A connection may refer to a connection that enables two different devices to communicate and be in a data-transmittable or receivable state. The connection may include a connection via wireless communication and / or wired communication.

The mobile terminal 220 may transmit information to the first wearable device 210. The type of information sent is not limited to any particular type. More specifically, the mobile terminal 220 may determine whether the second wearable device 230 is connected to the mobile terminal 220 in operation S330.

The mobile terminal 220 may use the connection information about the second wearable device 230 included in the mapping information to determine whether the second wearable device 230 is connected to the mobile terminal 220. For example, in a case where the mapping information indicates that the second wearable device 230 is connected to the mobile terminal 220, the mobile terminal 220 may determine that the second wearable device 230 is connected to the mobile terminal 220. In a case where the mapping information indicates that the second wearable device 230 is not connected to the mobile terminal 220, the mobile terminal 220 may determine that the second wearable device 230 is not connected to the mobile terminal 220.

In addition, in order to determine whether the second wearable device 230 is connected to the mobile terminal 220 to perform a specific operation, the mobile terminal 220 may use the mapping information to determine whether there is a second wearable connected to the mobile terminal 220 for a specific communication module or a specific communication method.式 装置 230。 Type device 230.

There are special connections for specific communication modules or specific output methods In the case of a fixed wearable device, the mapping information may store information about a specific wearable device connected for a specific communication module or a specific output method.

In addition, in order to determine whether the second wearable device 230 is connected to the mobile terminal 220 to perform a specific operation, the mobile terminal 220 may use the mapping information to determine whether there is a second wearable device 230 capable of performing a specific operation. The mapping information may include information about a wearable device capable of performing the operation. In the case where a specific wearable device is connected, the mapping information may store information about whether or not a specific wearable device is connected.

In operation S340, when the second wearable device 230 is connected to the mobile terminal 220, the mobile terminal 220 may transmit information for performing the operation to the first wearable device 210, so as to connect the operation with the second wearable device. The operations performed by the device are performed together to perform the functions of the mobile terminal 220.

The mobile terminal 220 may allocate a plurality of operations to be performed to perform the functions of the mobile terminal 220 to a plurality of wearable devices connected to the mobile terminal 220.

For example, in order to perform a call function, the mobile terminal 220 may assign a video output operation to a first wearable device 210 having a video output capability, and assign an audio input or output operation to a second wearable device having an audio input or output capability.式 装置 230。 Type device 230.

As described above, the feature that multiple operations are performed simultaneously may refer to performing operations performed concurrently to perform the functions of the mobile terminal 220. There may be specific correlations, specific correlations, or contexts between operations. For example, the execution result of the first operation can be used to determine whether the second operation is performed or not. The method of performing the second operation is changed according to the execution result of the first operation. Therefore, the first operation and the second operation can be performed in association with each other. Since the second operation may be performed simultaneously with the first operation or may be performed before or after the first operation, the first operation and the second operation may have a context. In addition, the second operation may be performed by the same or similar operation as the first operation, or the second operation may be performed in association with the same or similar operation. However, the above relationship may not exist between operations.

In operation S350, when the second wearable device 230 is not connected to the mobile terminal 220, the mobile terminal 220 may transmit information used to perform the operation to the first wearable device 210 so as not to perform the operation of the second wearable device. The operations are performed in the case of performing the functions of the mobile terminal 220. In a case where multiple wearable devices are not connected or operations cannot be assigned to the multiple wearable devices, the mobile terminal 220 may assign operations to only one wearable device.

For example, in a case where a first wearable device 210 capable of performing a video output operation is connected, the mobile terminal 220 may transmit information for performing a video output operation to the first while performing an audio input or output operation. Wearable device 210.

FIG. 4 is a flowchart of an operation of the first wearable device 210 according to an exemplary embodiment. The operation of the first wearable device 210 according to an exemplary embodiment will be explained with reference to FIG. 4.

In operation S412, the first wearable device 210 according to an exemplary embodiment may receive connection information from the mobile terminal 220. The connection information may indicate whether a wearable device that will perform an operation for performing a function of the mobile terminal 220 is connected to the mobile device Information of the terminal 220.

In operation S414, the first wearable device 210 may determine whether the second wearable device 230 is connected to the mobile terminal 220 based on the connection information about the wearable device received from the mobile terminal 220. When the connection information about the wearable device received from the mobile terminal 220 indicates that the second wearable device 230 is connected to the mobile terminal 220, the first wearable device 210 may determine that the second wearable device 230 is connected to the mobile terminal 220.

In operation S416, when the second wearable device 230 is connected to the mobile terminal 220, the first wearable device 210 may perform an operation performed together with the operation to be performed by the second wearable device 230 to perform the function of the mobile terminal 220 .

In operation S418, when the second wearable device 230 is not connected to the mobile terminal 220, the first wearable device 210 may perform the actions performed to perform the mobile terminal 220 without performing the operations of the second wearable device 230. Functional operation.

5 to 24 are diagrams for explaining a method for providing a calling function of the mobile terminal 110 in a function providing system according to an exemplary embodiment.

FIG. 5 is a conceptual diagram for explaining a function providing system for providing a call function according to an exemplary embodiment.

The function providing system for providing a call function according to an exemplary embodiment may include a smart watch 510, a smart phone 520, and a headset 530.

The smart phone 520 may correspond to the mobile terminal 110 described above. The smart watch 510 may correspond to the above-mentioned first wearable device 120, and the earphone 530 may correspond to the above Mentioned second wearable device 130. It is assumed that the earphone 530 includes a microphone.

For convenience of distinction, the terms “first” and “second” used in the first and second wearable devices 120 and 130 are conceptually used. In another exemplary embodiment, the smart watch 510 may correspond to the second wearable device 130 described above, and the earphone 530 may correspond to the first wearable device 120 described above.

5, the smart phone 520 may be connected to a smart watch 510 and a headset 530. The communication method between the smart phone 520 and the smart watch 510 may be the same as or different from the communication method between the smart phone 520 and the headset 530. For example, the smart phone 520 may communicate with the smart watch 510 through a Bluetooth connection, and the smart phone 520 may communicate with the headset 530 through a wired connection. In addition, the smart phone 520 can communicate with the headset 530 through a Bluetooth connection. According to other exemplary embodiments, many other communication protocols may be used.

In operation 521, the smart phone 520 may provide user interface data to the smart watch 510 to enable the smart watch 510 to control a call function. In operation 522, the smart phone 520 may provide audio data to the headset 530 to perform a call function. The user interface is a device or software that enables smooth interaction between the user and the mobile terminal 520 or between the user and the wearable devices 510 and 530.

FIG. 6 is a flowchart of a method performed by the system shown in FIG. 5 to provide a calling function according to an exemplary embodiment.

In operation S522, the smart phone 520 may generate mapping information about a plurality of wearable devices. In operation S524, the smart phone 520 may check the connection of the wearable device according to the mapping information.

In operation 582, when the smart watch 510 is connected to the smart phone 520, the smart phone 520 may control the smart watch 510 to display a user interface. Specifically, in operation S526, the smart phone 520 may transmit user interface data to the smart watch 510. In operation 512, the smart watch 510 may display a user interface according to the user interface data received from the smart phone 520. In operation S514, the smart watch 510 may transmit the user interface control result data to the smart phone 520.

In operation 584, when the earphone 530 is connected to the smart phone 520, the smart phone 520 may control the earphone 530 to output audio data and input audio. Specifically, in operation S528, the smart phone 520 may transmit the audio output data to the headset 530.

The smart phone 520 may transmit the output audio data to the headset according to the user interface control result data received from the smart watch 510. The output audio data may be audio data of other users received by the smart phone 520 from the base station or other terminals. The smart watch 510 may transmit control data generated by a user's user interface operation to the smart phone 520. The smart phone 520 may use the control data received from the smart phone 520 to determine whether to transmit the output audio data to the headset 530. In operation S532, the earphone 530 may output audio using audio output data. In operation S532, the earphone 530 may receive audio from the user and output audio data. In operation S534, the headset 530 may transmit the received audio data to the smart phone 520. The smart phone 520 may perform a calling function by transmitting audio data received from the headset 530 to a base station or other terminal.

FIG. 7 is a flowchart of a method for causing the earphone 530 to provide a user interface to the smart watch 510 according to an exemplary embodiment. The operation execution request transmitted from the mobile terminal to the first wearable device may be changed according to the connection status of the second wearable device, and the operation of the second wearable device may not be performed. For example, the user interface provided by the smart watch 510 in operation 582 shown in FIG. Details will be explained below with reference to FIG. 7.

In operation S710, the smart phone 520 according to an exemplary embodiment may determine whether the headset 530 is connected to the smart phone 520. In operation S720, when the headset 530 is connected to the smart phone 520, the smart phone 520 may transmit the call connection user interface to the smart watch 510. In operation S730, when the headset 530 is not connected to the smart phone 520, the smart phone 520 may provide a call notification user interface to the smart watch 510. The call notification user interface is an alternative user interface provided when it is impossible or difficult to provide a user interface for controlling functions of a mobile terminal, such as the smart phone 520. Mobile terminals can provide wearable devices with information indicating that it is impossible or difficult to provide a control user interface. In addition, when it is impossible or difficult to provide an operation control user interface, the mobile terminal 110 may not provide a user interface.

FIG. 8 is a conceptual diagram for explaining a notification user interface provided in a method for providing a call function according to an exemplary embodiment.

The notification user interface provided from the smart phone 520 to the smart watch 510 may be a user interface that notifies that a call acceptance request is received. As shown in Figure 8 The notification user interface provided to the smart watch 510 may be a user interface that displays a caller's phone number while notifying that a telephone call is received.

FIG. 9 is a conceptual diagram for explaining a notification user interface provided in a method of providing a call function according to another exemplary embodiment.

Referring to FIG. 9, a notification user interface according to another exemplary embodiment may notify that a call acceptance request is received together with a caller's phone number. In addition, the notification user interface according to another exemplary embodiment may include a call rejection input object and a message transmission object that allows the smart phone 520 to reject an incoming call, and the message transmission object receives a message transmission Enter to transfer the message to the caller.

10 to 13 are diagrams illustrating a call connection user interface according to an exemplary embodiment. FIG. 10 is a flowchart illustrating a call connection user interface according to an exemplary embodiment. In operation S1010, the call connection user interface may display a call acceptance object and a call rejection object.

The call connection user interface will be explained in more detail below with reference to FIG. 11. FIG. 11 is a conceptual diagram for explaining a call connection user interface according to an exemplary embodiment.

The smart phone 520 according to the exemplary embodiment may be connected to a headset 530 and a smart watch 510. When the operations of the headset 530 and the smart watch 510 can be controlled, the smart phone 520 can perform the operations of the headset 530 and the smart watch 510 and perform a call function.

When the operation of the headset 530 and the smart watch 510 can be controlled, the smart The phone 520 may provide a call connection user interface to the smart watch 510. The smart watch 510 may use the user interface data provided from the smart phone 520 to provide a user with a call connection user interface.

As shown in FIG. 11, the call connection user interface provided to the smart watch 510 may include a caller number display object 1110, a call acceptance control object 1120, and a call rejection / message transmission object 1130. The objects 1110, 1120, and 1130 included in the call connection user interface described with reference to FIG. 11 are merely exemplary, and the types and types of objects 1110, 1120, and 1130 displayed on the call connection user interface and The number is not limited to this.

The caller number display object 1110 may display a caller's phone number or other identifying information. The call acceptance control object 1120 may be an object that receives a call acceptance input from a user by receiving a user input (eg, a touch or an input) that is input to a corresponding object through a pointing device. The call rejection / message transmission object 1130 may be an object that receives call rejection input or message transmission input from the user by receiving user input (eg, touch or input) inputted to the corresponding object by the self-pointing device.

When the user touches the call acceptance object 1120 displayed on the smart watch 510, the smart watch 510 may generate a call acceptance input. The smart watch 510 may transmit a call acceptance input to the smart phone 520.

Similarly, when the user touches the call rejection / message transmission object 1130 displayed on the smart watch 510, the smart watch 510 may generate a call rejection input. The smart watch 510 may transmit a call rejection input to the smart phone 520.

Referring again to FIG. 10, in operation S1020, the call connection user interface may confirm whether a call acceptance input is received from the user. In operation S1030, when a call acceptance input is received from the user, the call connection user interface may display a busy user interface. The busy user interface will be described in detail below with reference to FIG. 12.

FIG. 12 is a conceptual diagram for explaining a busy line user interface according to an exemplary embodiment.

The smart phone 520 can be connected to a headset 530 and a smart watch 510. When the smart phone 520 performs the operations of the headset 530 and the smart watch 510 and performs the calling function of the smart phone 520, the smart phone 520 may provide a busy user interface to the smart watch 510. The smart watch 510 may provide the user with a busy user interface by using the user interface data received from the smart phone 520.

As shown in FIG. 12, the busy user interface provided to the smart watch 510 may include a caller number display object 1210, a call time display object 1220, an audio increase control object 1230, an audio decrease control object 1240, and a call end object 1250. The objects 1210, 1220, 1230, 1240, and 1250 are merely exemplary, and the types and numbers of the objects 1210, 1220, 1230, 1240, and 1250 displayed on the busy user interface are not limited thereto.

When a user input is received by the audio increase control object 1230, the audio decrease control object 1240, and the call end object 1250, the smart watch 510 may perform control according to the objects. For example, when a user input is input by adding an audio control object 1230, the smart watch 510 may increase the audio volume.

Referring again to FIG. 10, in operation S1040, when no call acceptance input is received from the user, the call connection user interface may confirm whether a call rejection input is received from the user. In operation S1050, when a call rejection input is received from the user, the call connection user interface may display a call rejection user interface. When both the call acceptance input and the call rejection input are not received, the call connection user interface can confirm whether to enter the call acceptance input or the call rejection input again.

The call rejection user interface will be explained in more detail below with reference to FIG. 13. FIG. 13 is a conceptual diagram for explaining a call rejection user interface according to an exemplary embodiment.

The smart phone 520 according to the exemplary embodiment may be connected to a headset 530 and a smart watch 510. When the call function can be performed using the operation of the headset 530 and the smart watch 510, the smart phone 520 can provide a call rejection user interface to the smart watch 510. The smart watch 510 may utilize the user interface data received from the smart phone 520 to provide the user with a call rejection user interface.

The call rejection user interface may include a caller number display object, a message transmission control object, and a call rejection control object. When a user input for selecting a message transmission control object is generated, the smart watch 510 may transmit a message transmission request to the smart phone 520 to transmit a message to a caller. The smart watch 510 may display a list of messages to be transmitted to the user and receive a user selection.

When a user input to select a call rejection control object is generated, the smart watch 510 may transmit a call rejection request to the smart phone 520.

A mobile terminal according to an exemplary embodiment will be described in detail below. 110 A method of transmitting an operation execution request to the first wearable device 120 and the second wearable device 130. 14 to 19 are diagrams for explaining the operation execution request transmitted by the smart phone 520 as the mobile terminal 110 to the smart watch 510 as the first wearable device 120 and as the second wear according to an exemplary embodiment Conceptual diagram of the method of the headset 530 of the device 130. Assuming that the mobile terminal 110, the first wearable device 120, and the second wearable device 130 are a smart phone 520, a smart watch 510, and a headset 530, respectively, the mobile terminal 110, the first wearable device 120, and the second wearable device will be described below Operation of the portable device 130.

FIG. 14 is a flowchart of a method for causing the mobile terminal 110 to transmit an operation execution request to the first wearable device 120 and the second wearable device 130 according to an exemplary embodiment. As shown in FIG. 14, the smart phone 520 may transmit a first operation execution request 1421 to the smart watch 510 and a second operation execution request 1422 to the headset 530. The smart phone 520 may transmit the first operation execution request and the second operation execution request to the first wearable device 510 and the second wearable device 530 at the same time or not to the first wearable device 510 and the second wearable device 530.

15 to 17 are conceptual diagrams illustrating a communication method between the mobile terminal 110 and the first wearable device 120 and the second wearable device 130 according to an exemplary embodiment.

FIG. 15 is a conceptual diagram for explaining a communication method between the mobile terminal 110 and the first wearable device 120 and the second wearable device 130 according to an exemplary embodiment. The mobile terminal 110 according to the exemplary embodiment may use the same communication method or different communication methods to transmit data to the first wearable device 120 and the second wearable device 120. The wearable device 130 receives data from the first wearable device 120 and the second wearable device 130.

15, a smart phone 520 according to an exemplary embodiment may communicate with a smart watch 510 via a wireless network 1521 and communicate with a headset 530 via a wired network 1522. This is only exemplary, and the communication method between the smart phone 520 and the first wearable device 510 and the second wearable device 530 is not limited to this. For example, the smart phone 520 can communicate with the smart watch 510 via a wired network, and communicate with the headset 530 via a wireless network. In addition, the smart phone 520 can communicate with both the smart watch 510 and the headset 530 via a wired network or a wireless network.

For example, referring to FIG. 16, the smart phone 520 may use Bluetooth communication 1621 and 1622 to transmit data to the smart watch 510 and the headset 530 and receive data from the smart watch 510 and the headset 530. Referring to FIG. 17, the smart phone 520 may use Wi-Fi connection 1721 to transmit data to and receive data from the smart watch 510, and use Bluetooth connection 1722 to transmit data to and receive data from the earphone 530. data.

FIG. 18 is a diagram illustrating an example in which the smart phone 520 according to an exemplary embodiment transmits an operation execution request and data related to the operation execution to the first wearable device 510 and the second wearable device 530. The smart phone 520 according to the exemplary embodiment may transmit an operation execution request and data related to the operation execution to the first wearable device 510 and the second wearable device 530. The data related to the execution of the operation may be transmitted before the request, simultaneously with the request, or after the request is transmitted.

As shown in FIG. 18, the smart phone 520 may transmit both an operation execution request and data related to the operation execution to only one wearable device and only the operation execution request to another wearable device. For example, the smart phone 520 may transmit the first operation execution request and data related to the operation execution to the smart watch 510 and the second operation execution request to the headset 530.

FIG. 19 illustrates an example in which the smart phone 520 according to an exemplary embodiment transmits an operation execution request and data related to the operation execution to the first wearable device 510 and the second wearable device 530. When the wearable device is capable of performing display operations and input operations and providing a user interface to the user, the wearable device may be provided with a user interface for controlling the smart phone 520. For example, the smart phone 520 may transmit data of a user interface for controlling the smart phone 520 to the wearable device. The wearable device may utilize the received user interface data to display the user interface, receive user input, and provide the user interface to the user.

As shown in FIG. 19, the smart phone 520 may transmit an operation execution request, data related to the operation execution, and user interface data to only one wearable device, and only transmit the operation execution request to another wearable device.

For example, the smart phone 520 may transmit the first operation execution request, the data related to the operation execution, and the user interface data to the smart watch 510, and transmit the second operation execution request to the headset 530.

Hereinafter, a method for causing a first wearable device to control a mobile terminal and a second wearable device according to an exemplary embodiment will be explained in detail. Figures 20 to 24 are the roots A conceptual diagram for explaining a method of enabling the smart watch 510 to control the headset 530 in a method of providing a function according to an exemplary embodiment.

Referring to FIG. 20, the smart watch 510 may transmit the first operation execution result data 2021 to the smart phone 520. The smart phone 520 may use the first operation execution result data 2021 received from the smart watch 510 to transmit a second operation execution request 2022 for controlling the headset 530 to the headset 530.

The operation of causing the smart watch 510 to initiate a call will be explained with reference to FIG. 21. The smart watch 510 may transmit a call acceptance request 2111 to the smart phone 520. The smart phone 520 may initiate a call in response to a call acceptance request received from the smart watch 510. The smart phone 520 may transmit the audio output data of the other party received from the base station or the external terminal to the headset 530 in operation 2122. The smart phone 520 may also transmit an audio input request to the headset 530.

A data flow during a call in a method of providing a function according to an exemplary embodiment will be explained below with reference to FIG. 22.

The smart phone 520 may transmit user interface data including information generated during a call to the smart watch 510 in operation 2221, so that the smart watch 510 displays the information generated during the call. For example, the user interface data may include the caller's phone number, caller identity, caller's photo, and call duration. In addition, the smart phone 520 can provide user interface data to the smart watch 510 to enable the user to control the call status during the call. The smart watch 510 may provide a user interface for a user by using the user interface data received from the smart phone 520.

The smart watch 510 can receive user interface input from a user and generate call control data. For example, the smart watch 510 may receive user interface input to end a call or user interface input to increase or decrease audio volume. The smart watch 510 may transmit call control data including the generated information to the smart phone 520 according to a user interface input received from the user in operation 2211. Control information may include information about controls for increasing or decreasing audio volume or ending a call.

The smart phone 520 may use the call control data received from the smart watch 510 to control a call. For example, the smart phone 520 may use call control data to end a call, or increase or decrease the audio volume of the headset 530. The smart phone 520 may transmit the audio output data to the headset 530 in operation 2222.

The headset 530 may include a microphone. The microphone can receive user audio. The microphone can record the user's audio and generate audio input data. In addition, the headset 530 may include a user interface such as a physical button. The headset 530 can receive call control input from the user through the user interface and generate call control data. For example, the headset 530 may receive a user interface input for ending a call or a user interface input for increasing or decreasing audio volume from a user. The headset 530 may transmit the call control data to the smart phone 520 according to a user interface input received from the user in operation 2231.

FIG. 23 is a conceptual diagram for explaining a method of causing a smart watch 510 to end a call in a method of providing a function, according to an exemplary embodiment.

First, the smart watch 510 recognizes the end of the call (call end). For example, the smart watch 510 may receive a call end input from a user and recognize the call end. The smart watch 510 may transmit a call end request to the smart phone 520 in operation 2311. The smart phone 520 may end the call in response to a call end request received from the smart watch 510. The smart phone 520 may transmit an audio input end request to the headset 530 in operation 2322. When the audio input end request is received from the smart phone 520, the headset 530 may end the audio input operation of the microphone.

FIG. 24 is a conceptual diagram for explaining a method of causing a headset 530 to end a call in a method of providing a function, according to an exemplary embodiment.

The headset 530 may transmit a call end request to the smart phone 520 according to a call end input received from the user in operation 2431. The smart phone 520 may end a call in response to a call end request received from the headset 530. The smart phone 520 may transmit user interface data indicating the end of the call to the smart watch 510 in operation 2421. The smart watch 510 may use the user interface data received from the smart phone 520 to provide the user with a user interface indicating that the call is over. As described above, the user interface can be provided by displaying the user interface on the display unit.

FIG. 25 is a flowchart of an operation of the function providing system according to an exemplary embodiment. In operation S2522, the mobile terminal 220 may generate capability information about a plurality of wearable devices. The capability information may be information about capabilities that enable the wearable device to perform a particular operation.

The mobile terminal 220 may upload capability information about at least one wearable device Pre-stored in memory. In addition, the mobile terminal 220 may download capability information about at least one wearable device from an external device (for example, a personal computer or a server). In addition, the mobile terminal 220 may directly receive capability information about at least one wearable device from the corresponding wearable device. A method of enabling the mobile terminal 220 to directly receive capability information about the wearable device will be explained below with reference to FIG. 27.

In operation S2526, the mobile terminal 220 may determine an operation execution subject according to the capability. In operation S2528, the mobile terminal 220 may transmit a first operation execution request to the first wearable device 210. The mobile terminal 220 may transmit the second operation execution request to the operation execution subject determined based on the capability. For example, if the first wearable device 210 has the capability to perform the first operation, the mobile terminal 220 may transmit the first operation execution request to the first wearable device 210.

In operation S2512, the first wearable device 210 may perform a first operation. The first wearable device 210 may perform the first operation in response to the first operation execution request received from the mobile terminal 220.

The first wearable device 210 may generate a first operation execution result as a result of performing the first operation. The first operation execution result may be an output generated when the first wearable device 210 performs the first operation, and may be generated as any one of various types of output. For example, the first wearable device 210 may perform a first operation to output audio data, output vibration, display a screen, or generate and output data processing result data. The output generated by the first wearable device 210 is not limited to the above example.

In operation S2514, the first wearable device 210 may transmit a first operation execution result to the mobile terminal 220. The first wearable device 210 may be used as a first operation. The result data generated as the execution result is transmitted to the mobile terminal 220. Since operation S2514 is optional, operation S2514 can be omitted.

In operation S2529, the mobile terminal 220 may transmit a second operation execution request to the second wearable device 230. The mobile terminal 220 may transmit the second operation execution request to the operation execution subject determined based on the capability. For example, if the second wearable device 230 has the capability to perform the second operation, the mobile terminal 220 may transmit the second operation execution request to the second wearable device 230.

In operation S2532, the second wearable device 230 may perform a second operation. The second wearable device 230 may perform the second operation in response to the second operation execution request received from the mobile terminal 220. The second wearable device 230 may generate a second operation execution result as a result of performing the second operation. The second operation execution result may be an output generated when the second wearable device 230 performs the second operation, and may be generated as any one of various types of outputs. For example, the second wearable device 230 may perform a second operation to output audio data, output vibration, display a screen, or generate and output data processing result data. The output generated by the second wearable device 230 is not limited to the above example.

In operation S2534, the second wearable device 230 may transmit a second operation execution result to the mobile terminal 220. The second wearable device 230 may transmit the result data generated as a result of the execution of the second operation to the mobile terminal 220. Since operation S2534 is optional, operation S2534 can be omitted.

FIG. 26A is a flowchart of a method of causing a mobile terminal 220 to request a wearable device to perform an operation to perform a function of the mobile terminal according to an exemplary embodiment. In operation S2610, the mobile terminal 220 may generate capability information about a plurality of wearable devices. The capability information may be information about capabilities that enable the wearable device to perform a particular operation.

In operation S2620, the mobile terminal 220 may use the capability information about the plurality of wearable devices to determine a first wearable device 210 that will perform a first operation for performing a function of the mobile terminal 220, and will perform a first Operate a second wearable device 230 that performs a second operation together to perform a function of the mobile terminal 220. In other words, the mobile terminal 220 may use the capability information about the plurality of wearable devices 210 and 230 to determine from the plurality of wearable devices 210 and 230 that the first sub-function to perform the function of the mobile terminal 220 will be performed. A first wearable device 210 and a second wearable device 230 that will perform a second sub-function that is performed together with the first sub-function to perform the function of the mobile terminal 220.

In operation S2630, the mobile terminal 220 may transmit information about the first operation to the first wearable device 210. In operation S2640, the mobile terminal 220 may transmit information about the second operation to the second wearable device 230.

FIG. 26B is a flowchart of a method of causing a mobile terminal 220 to request a wearable device to perform an operation to perform a function of the mobile terminal according to another exemplary embodiment. In operation S2650, the mobile terminal 220 may generate capability information about a plurality of wearable devices.

In operation S2660, the mobile terminal 220 may use the capability information about the plurality of wearable devices 210 and 230 to determine a first operation to be performed by the first wearable device 210 for performing functions of the mobile terminal 220 and a first operation to be performed by the first Second wear The wearable device 230 performs a second operation together with the first operation to perform the functions of the mobile terminal 220. In operation S2660, the mobile terminal 220 may use the capability information about the plurality of wearable devices 210 and 230 to determine a first sub-function to be executed by the first wearable device 210 for performing a function of the mobile terminal 220 and a function The second wearable device 230 executes together with the first sub-function to perform a second sub-function of the function of the mobile terminal 220.

In operation S2670, the mobile terminal 220 may transmit information about the first operation to the first wearable device 210. In operation S2680, the mobile terminal 220 may transmit information about the second operation to the second wearable device 230.

FIG. 27 is a flowchart of a method for causing a function providing system to receive capability information about a plurality of wearable devices and generate capability information about a plurality of wearable devices from a wearable device according to an exemplary embodiment. In operation S2722, the mobile terminal 220 may request the capability information from the first wearable device 210. The capability information request may be a message transmitted from the mobile terminal 220 to the first wearable device 210 such that the mobile terminal 220 requests information about operations that can be performed by the first wearable device 210.

In operation S2712, the first wearable device 210 may retrieve capability information. The first wearable device 210 may retrieve the capability information in response to the capability information request received from the mobile terminal 220. The information about the capabilities of the wearable device stored in the wearable device will be explained below with reference to FIGS. 28 to 31.

In operation S2714, the first wearable device 210 may transmit the capability information about the first wearable device 210 to the mobile terminal 220. In operation S2724, The mobile terminal 220 may request the capability information from the second wearable device 230. In operation S2732, the second wearable device 230 may retrieve capability information. The second wearable device 230 may retrieve the capability information in response to the capability information request received from the mobile terminal 220. In operation S2714, the first wearable device 210 may transmit the capability information about the first wearable device 210 to the mobile terminal 220.

The operations S2722 in which the mobile terminal 220 requests the capability information from the first wearable device 210 and the mobile terminal 220 requesting to obtain the capability information from the second wearable device 230 may be performed in different ways (for example, tandem, parallel, simultaneous, different times, etc.) Operation of capability information S2724. Therefore, the operation in which the mobile terminal 220 receives capability information from the first wearable device 210 and the operation in which the mobile terminal 220 receives capability information from the second wearable device 230 can be performed together.

The mobile terminal 220 may then use the capability information received from the wearable device to generate capability information about at least one wearable device. A method for enabling the mobile terminal 220 to store capability information will be described below with reference to FIGS. 32 to 36.

In FIG. 27, the time point at which the mobile terminal 220 requests the first wearable device 210 and the second wearable device 230 to obtain capability information may vary according to various situations or conditions. For example, when the mobile terminal 220 is connected to at least one of the first wearable device 210 and the second wearable device 230, the mobile terminal 220 may request capability information from the connected wearable device.

In addition, after the mobile terminal 220 is connected to at least one of the first wearable device 210 and the second wearable device 230, the mobile terminal 220 may request capability information from the connected wearable device.

In addition, once an event such as a user input is received, the mobile terminal 220 may request the capability information from the wearable device.

For example, when receiving a user input requesting the execution of a function of the mobile terminal 220, the mobile terminal 220 may request to obtain it from at least one of the first wearable device 210 and the second wearable device 230 related to the function execution. Capability information. Examples of user input requesting function execution may include user input requesting execution of an application for performing the function execution, user input selecting an icon representing the application, User input to lock screen for unlocking and user input to select multimedia content to be played back or executed by the function execution. In addition, the mobile terminal 220 may provide a user interface that allows the user to check whether to request the capability information from the first wearable device 210 and the second wearable device 230, and to the A wearable device 210 and a second wearable device 230 request capability information.

The capability information received by the mobile terminal 220 may be maintained in a memory. After the capability information is stored in the memory, access to the capability information may be restricted after a predetermined time has elapsed. For example, when the execution of the function performed by the mobile terminal 220 using the capability information is completed, the capability information may be encrypted, a password may be set to protect the capability information, or the capability information may be deleted from the memory or automatically transmitted to External device.

28 to 31 are diagrams of a data structure in which capability information about a wearable device is stored in the wearable device according to an exemplary embodiment.

FIG. 28 is a diagram for explaining when the wearable device according to the exemplary embodiment is In the case of a smart watch, a diagram of a data structure of the smart watch, including information about the capabilities of the smart watch. Referring to FIG. 28, a smart watch according to an exemplary embodiment may store a data structure including a device ID or capability information in a memory. The memory can further store information such as remaining battery capacity and the information shown in FIG. 28. The device ID may be an identifier for identifying a specific device from a plurality of wearable devices. Referring to FIG. 28, a smart watch according to an exemplary embodiment may store display capabilities, Bluetooth capabilities, heart rate measurement capabilities, and vibration output capabilities as information about the capabilities of the smart watch. The capabilities of the smart watch shown in FIG. 28 are merely exemplary, and the exemplary embodiment is not limited thereto.

FIG. 29 is a diagram for explaining a data structure of smart glasses that stores capability information about the smart glasses when the wearable device according to the exemplary embodiment is smart glasses. Referring to FIG. 29, the smart glasses according to an exemplary embodiment may store a data structure including a device ID or capability information in a memory. The memory can store other information as well as the information shown in FIG. 29. The device ID may be an identifier for identifying a specific device from a plurality of wearable devices. Referring to FIG. 29, the smart glasses according to the exemplary embodiment may store display capabilities, Bluetooth capabilities, and audio output capabilities as information about the capabilities of the smart glasses. The capabilities of the smart glasses shown in FIG. 29 are merely exemplary, and the exemplary examples are not limited thereto.

FIG. 30 is a diagram for explaining a data structure of a smart shoe including capability information about the smart shoe when the wearable device according to the exemplary embodiment is a smart shoe. Referring to FIG. 30, a smart shoe according to an exemplary embodiment may store a data structure including a device ID or capability information in a memory. Memory can be changed Other information and the information shown in FIG. 30 are stored. The device ID may be an identifier for identifying a specific device from a plurality of wearable devices. Referring to FIG. 30, a smart shoe according to an exemplary embodiment may store a display capability, a Bluetooth capability, a heart rate measurement capability, and a vibration output capability as information about the capability of the smart shoe. The capabilities of the smart shoe shown in FIG. 30 are merely exemplary, and the exemplary embodiment is not limited thereto.

FIG. 31 is a diagram for explaining a data structure of a headset including capability information about the headset when the wearable device according to the exemplary embodiment is a headset. Referring to FIG. 31, a headset according to an exemplary embodiment may store a data structure including a device ID or capability information in a memory. The memory can further store other information and the information shown in FIG. 31. The device ID may be an identifier for identifying a specific device from a plurality of wearable devices. Referring to FIG. 31, a headset according to an exemplary embodiment may store an audio input capability and an audio output capability as information about the capability of the headset. The capabilities of the earphone shown in FIG. 31 are merely exemplary, and the exemplary embodiment is not limited thereto.

FIG. 32 to FIG. 46 are diagrams illustrating the capability information of the wearable device stored in the mobile terminal 220 according to an exemplary embodiment.

FIG. 32 is a diagram illustrating a data structure of a memory for the mobile terminal 220 to store capability information about a smart watch according to an exemplary embodiment.

As shown in FIG. 32, the capability information about the first wearable device 210 may be stored in the memory of the mobile terminal 220. In the exemplary embodiment shown in FIG. 32, the mobile terminal 220 may store capability information about the smart watch as the first wearable device 210. In the exemplary embodiment shown in FIG. 32, the capability information about the first wearable device 210 may be stored as the capability information about the smart watch. Display capabilities, Bluetooth capabilities, heart rate measurement capabilities, and vibration output capabilities.

FIG. 33 is a diagram of a data structure of a memory for the mobile terminal 220 to store capability information about smart watches and earphones.

As shown in FIG. 33, the capability information about the plurality of wearable devices may be stored in a memory of the mobile terminal 220. The mobile terminal 220 may set identifiers of a plurality of wearable devices in the order connected to the mobile terminal 220. For example, if the smart watch is the first device connected to the mobile terminal 220, the mobile terminal 220 may assign the identifier of the first wearable device 210 to the smart watch. If the headset is a second device connected to the mobile terminal 220, the mobile terminal 220 may recognize the headset as the second wearable device 230 and assign an identifier of the second wearable device 230 to the headset. This description is merely exemplary, and the exemplary embodiments are not limited thereto.

In the exemplary embodiment shown in FIG. 33, the mobile terminal 220 may store capability information about a smart watch as the first wearable device 210 and capability information about a headset as the second wearable device 230. In the memory of the mobile terminal 220, the identifier of the wearable device can be used to access the capability information of the wearable device.

The information about the connection status of the wearable device stored in the memory of the mobile terminal 220 can be used to distinguish the first wearable device 210 and the second wearable device 230 from each other. For example, the device ID of the first wearable device 210 and the device ID of the second wearable device 230 may be stored in the memory of the mobile terminal 220. The identifier assigned to the wearable device by the mobile terminal 220 can be used as a general secret for distinguishing the device ID of each wearable device and the capability information of each wearable device. key. These methods are merely exemplary, and the exemplary embodiments are not limited thereto.

FIG. 34 is a diagram illustrating a data structure of a memory for the mobile terminal 220 to store capability information about two smart watches according to an exemplary embodiment.

As shown in FIG. 34, capability information about multiple wearable devices of the same type may be stored in the memory of the mobile terminal 220. The mobile terminal 220 may store capability information about the first smart watch as the first wearable device 210 and capability information about the second smart watch as the second wearable device 230.

The first wearable device 210 and the second wearable device information 230 can be distinguished from each other by using information about the connection status of the wearable device stored in the memory of the mobile terminal 220. For example, the device ID of the first wearable device 210 and the device ID of the second wearable device 230 may be stored in the memory of the main device. These methods are merely exemplary, and the exemplary embodiments are not limited thereto.

FIG. 35 is a diagram illustrating a data structure of a memory for the mobile terminal 220 to store capability information about a smart watch according to an exemplary embodiment.

As shown in FIG. 35, the capability information about the wearable device may be stored together with the stored information about the wearable device. In the exemplary embodiment shown in FIG. 35, the mobile terminal 220 may store the device ID of the smart watch as the first wearable device 210, and may further store capability information about the smart watch, the capability information including a display Capabilities, Bluetooth capabilities, and heart rate measurement capabilities.

FIG. 36 is a diagram illustrating a data structure of a memory for the mobile terminal 220 to store capability information about a smart watch according to an exemplary embodiment.

As shown in Figure 36, the capability information about multiple wearable devices can Capability information for the plurality of wearable devices is stored together with information about the plurality of wearable devices. Referring to FIG. 36, information about the smart watch as the first wearable device 210 may be stored in the memory of the mobile terminal 220, and includes a device ID of the smart watch and capability information about the smart watch. Information about the capabilities of the smart watch may include display capabilities, Bluetooth capabilities, and heart rate measurement capabilities. Similarly, the information about the headset as the second wearable device 230 may include a device ID of the headset and capability information about the headset. Capability information about the headset may include audio input capabilities and audio output capabilities. These methods are merely exemplary, and the exemplary embodiments are not limited thereto.

FIG. 37 is a flowchart of an operation of a function providing system according to an exemplary embodiment. The operation of the function providing system described with reference to FIG. 37 may further include operation S3724, which is an operation of classifying a plurality of operations constituting a function according to capabilities.

Explanation of the same operation previously described with reference to FIG. 25 will be omitted, and operation S3724 will be explained. In operation S3724, the mobile terminal 220 may classify the plurality of operations constituting a function according to capabilities. The mobile terminal 220 can classify the call function into: audio input operation, performed using a microphone with recording capability; audio output operation, performed using a speaker with audio output capability; information display operation, using a display unit with information display capability to Perform; and communication operations, using a communication unit with radio wave transmission or reception capabilities to perform.

Details will be explained below with reference to FIG. 38. FIG. 38 is a diagram that causes the mobile terminal 220 to classify the plurality of operations constituting a function according to an exemplary embodiment. Method flow chart.

Referring to FIG. 38, in operation S3810, the mobile terminal 220 may generate operation information about operations constituting a function. FIG. 39 is a conceptual diagram for explaining a method for causing the mobile terminal 220 to generate operation information on operations constituting a function according to an exemplary embodiment.

A method of dividing a call function among a plurality of functions that can be performed by the mobile terminal 220 into a plurality of operations will be explained below with reference to FIG. 39. As shown in Figure 39, the call function can be divided into multiple operations. For example, the call function may include an information display operation, an audio input operation, an audio output operation, and a transmission or reception operation.

The information display operation may be an operation in which the mobile terminal 220 displays information when the user is talking on the phone. The audio input operation may be an operation in which the mobile terminal 220 receives a user's audio (eg, voice data). The audio output operation may be an operation in which the mobile terminal 220 outputs a user's audio. The transmitting or receiving operation may be an operation in which the mobile terminal 220 transmits audio of a user received from another device or receives audio of a user from another device.

As shown in FIG. 39, the mobile terminal 220 may receive information about operations constituting a function in advance. For example, the mobile terminal 220 may receive operation information from a user. In addition, the mobile terminal 220 may receive operation information from another host device or other external device (such as a server or a wearable device).

The mobile terminal 220 may store information about a plurality of operations constituting a function in advance. The mobile terminal 220 may store information about a plurality of operations constituting the function in advance for each of the plurality of functions.

Referring again to FIG. 38, in operation S3820, the mobile terminal 220 may generate capability information about each operation. FIG. 40 is a diagram illustrating a data structure for the mobile terminal 220 to store capabilities corresponding to operations according to an exemplary embodiment. FIG. 40 illustrates capability information regarding capabilities of a wearable device for performing multiple operations.

As shown in FIG. 40, the capabilities of the wearable device for performing a plurality of operations constituting a call function may be stored in the mobile terminal 220. To perform information display operations, the wearable device may be required to have display capabilities. To perform audio input operations, the wearable device may be required to have audio input capabilities. To perform audio output operations, the wearable device may be required to have audio output capabilities. To perform a transmission or reception operation, the wearable device may need to be capable of communication.

As shown in FIG. 40, the mobile terminal 220 may generate capability information about capabilities for performing operations. The mobile terminal 220 may receive capability information from a user or from an external device. The capability information may be stored in the mobile terminal 220 in advance.

The mobile terminal 220 may manage the operation information and capability information by using a separate data set. For example, as shown in FIG. 40, the mobile terminal 220 may match the operation information with the capability information and store the operation information and the capability information in a memory. According to another exemplary embodiment, the mobile terminal 220 may store the operation information in the memory after the operation information is included in the operation information.

FIG. 41 is a flowchart of a method for causing the mobile terminal 220 to determine an operation execution subject according to an exemplary embodiment. In operation S4110, the mobile terminal 220 may search for a wearable device having a capability corresponding to the capability information regarding the operation. under The operation S4110 will be explained with reference to FIGS. 42 to 48. In operation S4120, the mobile terminal 220 may select a wearable device that will perform the operation from the found wearable devices. Operation S4120 will be explained below with reference to FIGS. 49 to 61.

FIG. 42 is a diagram illustrating operations performed by functions performed by the mobile terminal 220 and capabilities for the operations according to an exemplary embodiment.

A method of causing the mobile terminal 220 to determine a wearable device that will perform an information display operation during execution of a call function will be explained below with reference to FIG. 42.

The mobile terminal 220 according to an exemplary embodiment may perform an information display operation during execution of a call function. For example, the mobile terminal 220 can know that the mobile terminal 220 should perform the information display operation at a specific time point by using the function execution order information stored in the memory. As shown in FIG. 42, the mobile terminal 220 can know that the mobile terminal 220 should have a display capability to perform an information display operation with reference to operation information and capability information.

According to another exemplary embodiment, the mobile terminal 220 may recognize a situation in which an operation requiring a specific capability may occur during execution of a function. The mobile terminal 220 may recognize that certain capabilities may need to be fulfilled during execution of a function. For example, the mobile terminal 220 may recognize that an operation requiring display capability may occur during the execution of a function. The operation may be an information display operation. For example, when a screen output signal or output data is generated during the execution of a function, the mobile terminal 220 may recognize that an operation requiring display capability may occur. The mobile terminal 220 may recognize that signals or information generated during the execution of the calling function may be required to perform operations requiring specific capabilities.

FIG. 43 is a conceptual diagram for explaining a method of using the capability information about the wearable device stored in the mobile terminal 220 to find a wearable device capable of performing an operation.

The mobile terminal 220 according to an exemplary embodiment may use the capability information about the wearable device stored in the memory to select a wearable device having the capability to perform an operation. The capability information about the wearable device may be sequentially stored in the memory of the mobile terminal 220 or non-sequentially stored in the memory of the mobile terminal 220. Separate indexes can be used to access capability information about wearables.

FIG. 43 illustrates an example in which the capability information about the wearable device is sequentially stored in the memory of the mobile terminal 220. In the exemplary embodiment shown in FIG. 43, the mobile terminal 220 may sequentially retrieve capability information about the wearable device.

FIG. 44 is a diagram illustrating capability information about a wearable device stored in a memory of the mobile terminal 220 according to an exemplary embodiment.

Referring to FIG. 44, the mobile terminal 220 may retrieve capability information about the first wearable device 210. The memory may store display capabilities and Bluetooth capabilities as capability information about the first wearable device 210. The mobile terminal 220 may confirm that a display capability exists in the capability information about the first wearable device 210 and determine that the first wearable device 210 is a device capable of performing a display operation. The mobile terminal 220 may end the search for the wearable device. If there is no display capability in the capability information about the first wearable device 210, the mobile terminal 220 may retrieve the capability information about the next wearable device.

FIG. 45 is a method when the mobile terminal 220 successfully searches for a specific capability A flow chart of a method for specifying a wearable device for performing operations on multiple devices.

In operation S4510, the mobile terminal 220 may search for a wearable device having a capability corresponding to the capability information regarding the operation. When a wearable device having a required capability is found during retrieving the capability information of the wearable device, the mobile terminal 220 may end the search for additional wearable devices. On the other hand, even when a wearable device having a required capability is found, the mobile terminal 220 can continue to search for a wearable device having a required capability.

In operation S4520, the mobile terminal 220 may select a wearable device that will perform the operation in consideration of the hardware performance of the found wearable device.

FIG. 46 to FIG. 49 are diagrams for explaining in which the mobile terminal 220 according to the exemplary embodiment selects the first wearable device 210 and the Kth wearable device as a plurality of wearable devices having display capabilities. Diagram of the paradigm.

In FIG. 46, the mobile terminal 220 can know that the first wearable device 210 has a display capability by retrieving information about the capabilities of the first wearable device 210. The mobile terminal 220 may determine the first wearable device 210 as a device having a display capability. The mobile terminal 220 may end the search for the device, but the mobile terminal 220 may store information indicating that the first wearable device 210 has the capability in the memory, and continue searching for other devices with display capabilities to select multiple wearable Device.

In FIG. 47, the mobile terminal 220 can know that the second wearable device 230 does not have a display capability by retrieving the capability information about the second wearable device 230. The mobile terminal 220 can retrieve capability information about the next wearable device without The capability information about the second wearable device 230 is processed separately.

In FIG. 48, as a result of sequentially acquiring capability information about the wearable device, the mobile terminal 220 may retrieve capability information about the Kth wearable device. The mobile terminal 220 may confirm that the display capability is included in the capability information of the Kth wearable device, and determine that the Kth wearable device has the display capability.

Finally, as shown in FIG. 49, the mobile terminal 220 may determine the first wearable device 210 and the Kth wearable device as wearable devices with display capabilities.

FIG. 50 to FIG. 52 are diagrams illustrating a method for enabling the mobile terminal 220 to compare the hardware performance of multiple wearable devices according to an exemplary embodiment.

FIG. 50 is a conceptual diagram of a data structure of performance information of a wearable device stored in a memory of the mobile terminal 220 according to an exemplary embodiment. As shown in FIG. 50, the capability information about the wearable device may include hardware performance information and software performance information about the wearable device.

In the exemplary embodiment shown in FIG. 50, for the display capability situation, the first wearable device 210 and the Kth wearable device may include hardware regarding screen size, prescribed resolution, processor performance, and memory performance. Performance and / or software performance. This list of performance types is exemplary only, and the types of performance according to the exemplary embodiments are not limited thereto.

The mobile terminal 220 may select a wearable device that will perform the operation considering the performance for a specific capability. In addition, the mobile terminal 220 may consider the performance of various capabilities to select a wearable device that will perform operations. For example, the mobile terminal 220 may calculate the performance score for at least two capabilities, and select the performance score based on the calculated performance score. Optional wearable device. The mobile terminal 220 may apply different weights to different hardware performances.

FIG. 51 is a conceptual diagram of a data structure in which the mobile terminal 220 stores the minimum performance information in the memory for the minimum hardware performance required to have the capability, according to an exemplary embodiment.

The mobile terminal 220 according to an exemplary embodiment may store the minimum performance information in a memory for a capability required for performing a specific operation. Minimum performance information can be determined for specific capabilities. The minimum performance information may be information indicating the minimum performance required by the wearable device in order to perform a specific operation requested by the mobile terminal 220 to perform the wearable device. The mobile terminal 220 according to an exemplary embodiment may utilize the lowest performance information to determine a wearable device that will perform a specific operation. For example, the mobile terminal 220 according to an exemplary embodiment may use the minimum performance information stored in the mobile terminal 220 and the performance information about the wearable device obtained from the wearable device to determine a wearable that will perform a specific operation Device.

For example, even when there is a wearable device capable of performing a specific operation, the mobile terminal 220 according to the exemplary embodiment may perform performance information about the wearable device and minimum performance information about the mobile terminal 220 for the specific operation. Compare and determine the corresponding wearable device as a wearable device that will perform a specific operation only when the performance information about the wearable device meets the minimum performance.

The mobile terminal 220 according to an exemplary embodiment may determine a wearable device that performs a specific operation by transmitting the minimum performance information about a specific capability to perform a specific operation to the wearable device, and from the wearable device Received if minimum performance is met. According to another exemplary embodiment, according to an exemplary implementation For example, the mobile terminal 220 may determine a wearable device that will perform a specific operation by: receiving performance information from the wearable device to perform a specific operation, and comparing the performance information received from the wearable device with the minimum performance. Information for comparison. For example, if the performance of the specific capability of the wearable device is equal to or higher than the minimum performance, it can be determined that the mobile terminal 220 and the wearable device meet the minimum performance.

Details will be explained below with reference to FIG. 51. As shown in FIG. 51, the mobile terminal 220 according to the exemplary embodiment may store the minimum performance information in a memory for a display capability required for performing an information display operation. Minimum performance information can be determined for specific capabilities. The minimum performance information may be information indicating the minimum performance required by the wearable device in order to perform a specific operation requested by the mobile terminal 220 to perform the wearable device. For example, the minimum performance information about display capabilities can be determined based on screen size, required resolution, processor performance, or memory performance. Referring to FIG. 51, the minimum required resolution for performing the information display operation may be 320 × 240, but it should be understood that according to an exemplary embodiment, the minimum required resolution may be greater than or less than 320 × 240. Therefore, in the exemplary embodiment shown in FIG. 51, the minimum performance information on a prescribed resolution in the display capability is 320 × 240.

FIG. 52 is a conceptual diagram of a data structure in which hardware performance of a wearable device is stored in a memory of the mobile terminal 220 according to an exemplary embodiment.

As shown in FIG. 52, the maximum resolution of the display capability of the first wearable device 210 is 220 × 80, and the maximum resolution of the display capability of the Kth wearable device is 1020 × 768.

The mobile terminal 220 may choose to be able to provide more than 320 × 240 (that is, The K-th wearable device with a high resolution of the display required for the line information display operation is used as a wearable device for performing the information display operation.

According to an exemplary embodiment, when there are multiple wearable devices that provide a higher resolution than the minimum resolution of the display required to perform the information display operation, the mobile terminal 220 may select a wearable device based on a preset criterion Device. For example, the mobile terminal 220 may select a wearable device whose maximum resolution has the smallest difference from the required resolution of the display. In addition, the mobile terminal 220 may select a wearable device whose aspect ratio is substantially equal to the aspect ratio of the desired resolution of the display.

FIG. 53 is a flowchart of a method for causing the mobile terminal 220 to select a wearable device that will perform an operation from a plurality of wearable devices according to another exemplary embodiment.

In operation S5310, the mobile terminal 220 may search for a wearable device that performs a capability corresponding to the capability information about the operation. In the above manner, the mobile terminal 220 may search for a wearable device having the capability to perform the operation. In operation S5320, the mobile terminal 220 may consider whether the capabilities of the found wearable device are available and select a wearable device that will perform the operation. The mobile terminal 220 may consider various factors to determine the wearable device that will perform the operation, such as whether the user can recognize information provided by the self-wearable device, whether the mobile terminal 220 can control the wearable device, the user Whether the wearable device is worn and / or the mobile terminal 220 is capable of displaying a notification to the user in a situation where the mobile terminal 220 provides a user interface. Hereinafter, the above-mentioned situation will be explained with reference to the drawings.

FIG. 54 is a flowchart of a method for the mobile terminal 220 to select a wearable device that will perform an operation from a plurality of wearable devices in consideration of situation information according to an exemplary embodiment. In operation S5411, the mobile terminal 220 may search for a wearable device having a capability corresponding to the capability information about the operation.

In operation S5421, the mobile terminal 220 may select the wearable device that will perform the operation in consideration of the situation information about the found wearable device. The mobile terminal 220 may consider the wearing position information about the wearable device as the situation information about the wearable device. For example, the mobile terminal 220 can determine whether to display information around the user's wrist or display information in the user's field of vision, and can determine whether to display the information to the user through a smart watch or to the user through smart glasses. User display information.

In addition, the mobile terminal 220 may consider the environment in which the wearable device is located. For example, the mobile terminal 220 may use the light intensity input from the illuminance sensor to determine whether the user may not immediately recognize the smart watch because the smart watch is covered by a collar. In addition, the mobile terminal 220 can utilize the biological information. When the wearable device measures the biological information, the mobile terminal 220 may determine that the user is wearing the corresponding wearable device and use the corresponding wearable device to perform the information display operation.

FIG. 55 is a diagram illustrating a method for causing the mobile terminal 220 to store the situation information data of the wearable device in the memory according to an exemplary embodiment. The mobile terminal 220 may store situation information about the wearable device for each of the plurality of wearable devices.

Referring to FIG. 55, the first wearable device 210 is a smart watch and the Kth wearable device is smart glasses. In the exemplary embodiment shown in FIG. 55, the situation information about the first wearable device 210 and the Kth wearable device may include the wearing position, the surrounding brightness information, and whether the wearable device is worn or not.

For example, when the corresponding wearable device has a preset illuminance or a surrounding brightness that is higher than the preset illuminance, the mobile terminal 220 may use a plurality of pieces of information about the first wearable device 210 and the Kth wearable device The surrounding brightness information determines the wearable device as the device that will perform the information display operation.

The availability of situational information is explained in more detail below. The mobile terminal 220 may receive basic information indicating that the first wearable device 210 is a smart watch from the first wearable device 210 and obtain information indicating that the first wearable device 220 is worn on a user's wrist.

In addition, the mobile terminal 220 may use the camera module of the first wearable device 210 to obtain information about the surrounding brightness of the first wearable device 210. The mobile terminal 220 may use the heart rate measurement module of the first wearable device 210 to obtain information about whether the user is wearing the first wearable device 210, and may use the vibration module of the first wearable device 210 to confirm the user Whether the first wearable device 210 is recognized.

Similarly, the mobile terminal 220 may receive basic information indicating whether the K-th wearable device is smart glasses from the K-th wearable device, and obtain situation information indicating whether the K-th wearable device is worn on the face. The mobile terminal 220 may use the camera module of the Kth wearable device to obtain information about the surrounding brightness of the Kth wearable device, information about whether to wear the Kth wearable device, and whether the user recognizes Information displayed on the Kth wearable device. In addition, the mobile terminal 220 can obtain information about whether to set an interference prohibition mode on the Kth wearable device from the Kth wearable device, and determine whether the mobile terminal 220 can control the Kth wearable device under the current situation. .

FIG. 56 is a flowchart of a method for causing the mobile terminal 220 to determine a device having the capability to perform an operation from a plurality of devices according to an exemplary embodiment.

In operation S5610, the mobile terminal 220 may check whether there is a device whose determination as to whether the device is available has not been determined. If there is no device that has not been determined as to whether the device is available, the mobile terminal 220 may determine that no device is available.

In operation S5620, the mobile terminal 220 may determine whether it is possible to control the first device in the list of devices whose determination as to whether the device is available has not been determined. When the wearable device is in an uncontrollable state, the situation information may indicate that the corresponding wearable device is in an uncontrollable state. In addition, when the mobile terminal 220 transmits a response request to the wearable device and does not receive a response from the corresponding wearable device, the mobile terminal 220 may determine that the corresponding wearable device is in an uncontrollable state. In addition, when the mobile terminal 220 transmits a control request to the wearable device and does not receive a response from the corresponding wearable device, the mobile terminal 220 may determine that the corresponding wearable device is in an uncontrollable state.

In operation S5630, when it is possible to control the first device in the list of devices whose determination as to whether the device is available has not been determined, the mobile terminal 220 may perform the operation using the corresponding first device.

In operation S5640, when it is impossible to control the judgment as to whether the device is available When the first device in the list of devices that has not been determined is disconnected, the mobile terminal 220 may utilize another available device to perform the operation. The mobile terminal 220 may re-determine an available device for a device other than the first device in a list of devices whose determination as to whether the device is available has not been determined. For example, the mobile terminal 220 may perform operation S5610 and subsequent operations on devices other than the first device in the list of devices whose determination as to whether the device is available has not been determined.

57 and 58 are flowcharts of a method for causing the mobile terminal 220 to determine a device for performing operations from a plurality of devices according to an exemplary embodiment.

Referring to FIG. 57, in operation S5710, the mobile terminal 220 may check whether there is a device whose determination as to whether the device is available has not been determined in a similar manner to the device determination method shown in FIG. 56 and determine a wearable device that will perform the operation. In operation S5720, the mobile terminal 220 may determine a device that will perform the operation based on whether the wearable device is worn.

In operation S5720, the mobile terminal 220 may determine whether the user is wearing the first device in the list of devices whose determination as to whether the device is available has not been determined. For example, when the value of the biological signal measured by the wearable device is within a valid range, the mobile terminal 220 may determine that the corresponding wearable device is being worn.

When it is determined that the first wearable device is being worn, the mobile terminal 220 may determine the first wearable device as an available device. In operation S5730, the mobile terminal 220 may perform operations using the available first device. When it is determined that the first wearable device is not worn, the mobile terminal 220 may determine the first wearable device as an unavailable device. In operation S5740, the mobile terminal 220 may utilize the other of the available wearable devices to Perform the operation. The mobile terminal 220 may re-determine wearing or non-wearing for a device other than the first device in the list of devices that has not been determined in the determination as to whether the device is available. For example, the mobile terminal 220 may perform operations S5710 and S5720 on devices other than the first device in the list of devices that have not yet been determined as to whether the device is available, and perform operations S5730 or S5740 again.

Referring to FIG. 58, in a similar manner to the device determination method shown in FIG. 56, the mobile terminal 220 may determine a wearable device that will perform an operation. In operation S5810, the mobile terminal 220 may check whether there is a device whose determination as to whether the device is available has not been determined. In operation S5820, the mobile terminal 220 may determine a device that will perform the operation based on whether the wearable device can display a notification.

In operation S5820, the mobile terminal 220 may determine whether the first device in the list of devices for which the determination as to whether the device is available has not been determined is capable of displaying a notification. For example, the mobile terminal 220 may retrieve capability information about the wearable device and determine whether the corresponding wearable device has information display capability.

When it is determined that the first wearable device can display the notification, the mobile terminal 220 may determine the first wearable device as an available device. In operation S5830, the mobile terminal 220 may perform the operation by using the first wearable device.

When it is determined that the first wearable device cannot display the notification, the mobile terminal 220 may determine the first wearable device as an unavailable device. In operation S5840, the mobile terminal 220 may utilize another available wearable device to perform a required operation. The mobile terminal 220 may re-determine whether a device other than the first device in the list of devices whose determination as to whether the device is available has not been determined is capable of displaying a notification. For example In other words, the mobile terminal 220 may perform operations S5810 and S5820 on devices other than the first device in the list of devices that have not yet been determined as to whether the device is available, and perform operations S5830 or S5840 again.

FIG. 59 is a flowchart of a method for causing a mobile terminal 220 to provide a user interface to a wearable device according to an exemplary embodiment.

In operation S5910, the mobile terminal 220 according to an exemplary embodiment may determine whether a plurality of operations can be assigned to a plurality of wearable devices.

In operation S5920, when it is determined that a plurality of operations can be assigned to the plurality of wearable devices, the mobile terminal 220 may provide an operation control user interface for at least one of the plurality of wearable devices.

In operation S5930, when it is determined that it is impossible (or difficult) to assign a plurality of operations to the plurality of wearable devices, the mobile terminal 220 may simply provide a function notification user interface.

The function notification user interface is an alternative user interface provided when it is impossible (or difficult) to provide an operation control user interface. The mobile terminal 220 may provide the wearable device with information indicating that it is impossible (difficult) to provide an operation control user interface. In addition, when it is impossible (or difficult) to provide an operation control user interface, the mobile terminal 220 may not provide a user interface.

FIG. 60 is a flowchart of a method performed by a call function providing system to provide a call function according to an exemplary embodiment.

FIG. 60 is a flowchart of a method for providing a call function according to an exemplary embodiment. In operation S6022, the smart phone 6020 may generate information about a plurality of Capability information for wearables. In operation S6024, the smart phone 6020 may classify a plurality of operations constituting a function according to capabilities. In operation S6026, the smart phone 6020 may determine the operation execution subject according to the capability. In operation S6028, the smart phone 6020 may transmit user data to the smart watch 6010. In operation S6012, the smart watch 6010 may display the user interface according to the user interface data received from the smart phone 6020. In operation S6014, the smart watch 6010 may transmit the user interface control result data to the smart phone 6020. In operation S6029, the smart phone 6020 may transmit the audio output data to the headset 6030.

The smart phone 6020 may transmit the output audio data to the headset 6030 according to the user interface control result data received from the smart watch 6010. The output audio data may be audio data of another user received by the smart phone 6020 from the base station or other terminals. The smart watch 6010 can transmit the control data generated by the user's user interface operation to the smart phone 6020. The smart phone 6020 can use the control data received from the smart phone 6020 to determine whether to send the output audio data to the headset 6030. In operation S6029, the earphone 6030 may use the audio output data to output audio. In operation S6032, the headset 6030 may receive the audio of the user and generate audio data. The headset 6030 may include a microphone and receive audio from a user. In operation S6034, the headset 6030 may transmit the received audio data to the smart phone 6020. The smart phone 6020 may perform a calling function by transmitting audio data received from the headset 6030 to a base station or other terminal.

FIG. 61 is a method for causing a smart phone 6020 to determine to be transmitted to a smart watch 6010 in a method for providing a calling function according to an exemplary embodiment. Flowchart of the user interface method.

Referring to FIG. 61, in operation S6110, the smart phone 6020 may determine whether there are both a wearable device having a capability of providing a user interface and a wearable device having a capability of inputting and outputting audio.

When it is determined that there is both a wearable device having a capability to provide a user interface and a wearable device having a capability to input and output audio, the smartphone 6020 may provide a call connection user interface. For example, in operation S6120, the smart phone 6020 may provide a call connection user interface to a wearable device having the capability of providing a user interface.

In operation S6130, when it is determined that there is not any one of a wearable device having a capability to provide a user interface and a wearable device having a capability to input and output audio, the smart phone 6020 may provide the existing wearable device Notify the user interface. In operation S6130, when it is determined that there is no wearable device capable of providing a user interface and a wearable device capable of inputting and outputting audio, the smart phone 6020 may provide the notification user interface to the smart type Phone 6020.

The notification user interface may be a user interface for information notification, and the type of information is not limited to any particular type. For example, the notification user interface may be a user interface that notifies the smart phone 6020 that a call acceptance request has been received from the base station or another terminal. In addition, the notification user interface may be a user interface that notifies that the connection of the wearable device required for providing the calling function is insufficient.

FIG. 62 to FIG. 64 are diagrams for explaining a method according to an exemplary embodiment. A diagram of a method for providing a private information display function.

As shown in FIGS. 62 to 64, the smart watch 6210, the smart phone 6220, and the smart glasses 6230 may be used to implement a method for providing a private information display function according to an exemplary embodiment.

Referring to FIG. 62, the smart phone 6220 may transmit privacy-protected or unprotected query user interface data to the smart watch 6210. The smart watch 6210 can provide the user with a privacy-protected or unprotected query user interface, and receive relevant inputs from the user. When receiving an input to run the privacy protection mode from the user, the smart watch 6210 may transmit the privacy protection mode opening message to the smart phone 6220. When receiving the privacy protection mode opening message, the smart phone 6220 may transmit data predefined as private data to the smart glasses 6230.

Referring to FIG. 63, when the self-user receives an input that does not run the privacy protection mode, or when the user does not receive an input to run the privacy protection mode, the smart watch 6210 may transmit the privacy protection mode shutdown message to Smart phone 6220. When receiving the privacy protection mode shutdown message, the smart phone 6220 may transmit data predefined as private data to the smart watch 6210.

The smart watch 6210 may not transmit the privacy protection mode message to the smart phone 6220 when it receives the input that does not run the privacy protection mode from the user, or when it does not receive the input to run the privacy protection mode from the user. When the privacy protection mode message is not received within a preset time, the smart phone 6220 may transmit data that is predefined as private data to the smart watch 6210.

The provision of private information according to an exemplary embodiment will be explained below with reference to FIG. 64 Method of displaying functions.

In operation S6220, the smart phone 6220 may generate capability information about a plurality of wearable devices. In operation S6222, the smart phone 6220 may transmit privacy-protected or unprotected query user interface data to the smart watch 6210.

In operation S6212, the smart watch 6210 may provide the user with a privacy protected or unprotected query user interface. The smart watch 6210 may receive input regarding privacy protection or non-protection from a user via a user interface. In operation S6214, the smart watch 6210 may transmit the result data of the query about privacy protection or non-protection generated by using the input data about privacy protection or non-protection received from the user to the smart phone 6220.

In operation S6227, the smart phone 6220 may use the result data received from the smart watch 6210 to determine privacy protection or non-protection. In operation S6227, when the result data has a value for requesting privacy protection, the smart phone 6220 may determine the current state as the privacy protection mode. In operation S6224, in the privacy protection mode, the smart phone 6220 may transmit data to the smart glasses 6230. FIG. 62 illustrates an example in which data requiring privacy protection in the privacy protection mode is transmitted to the smart glasses 6230 and the smart glasses 6230 displays data requiring privacy protection. The smart glasses 6230 can display information to the user so that only a person wearing the smart glasses 6230 can easily recognize the information. Since the information requiring privacy protection is displayed on the smart glasses 6230, the user can personally observe the information requiring privacy protection.

In operation S6226, when the result data is not available for requesting privacy When the value is protected, the smart phone 6220 may determine the current state as a privacy non-protected mode. In operation S6226, in the privacy unprotected mode, the smart phone 6220 may transmit data to the smart watch 6210. In the privacy unprotected mode, data that does not require privacy protection can be transmitted to the smart watch 6210. In operation 6216, as shown in FIG. 63, the smart watch 6210 may display data that does not require privacy protection.

65 to 67 are diagrams for explaining a method for providing a private information display function according to another exemplary embodiment.

As shown in FIGS. 65 to 67, a smart watch 6210, a smart phone 6220, and a headset 6231 can be used to implement a method for providing a private information display function according to another exemplary embodiment.

A method of providing a private information display function according to another exemplary embodiment will be explained below with reference to FIG. 67.

In operation S6220, the smart phone 6220 may generate capability information about a plurality of wearable devices. In operation S6222, the smart phone 6220 may transmit privacy-protected or unprotected query user interface data to the smart watch 6210.

In operation S6212, the smart watch 6210 may provide the user with a privacy protected or unprotected query user interface. The smart watch 6210 may receive input regarding privacy protection or non-protection from a user via a user interface. In operation S6214, the smart watch 6210 may transmit the result data about the privacy protection or non-protection query generated by using the input data about privacy protection or non-protection received from the user to the smart phone 6220.

In operation S6227, the smart phone 6220 can utilize a smart phone Table 6210 receives the result data to determine privacy protection or non-protection. In operation S6227, when the result data has a value for requesting privacy protection, the smart phone 6220 may determine the current state as the privacy protection mode. In operation S6225, in the privacy protection mode, the smart phone 6220 may transmit data to the headset 6231. The smart phone 6220 can convert the data into audio data to transmit the data to the headset 6231. For example, the smart phone 6220 can convert the text data into corresponding audio data and output the audio data in S6223. FIG. 67 illustrates an example in which data requiring privacy protection in the privacy protection mode is transmitted to the headset 6231 and the headset 6231 displays data requiring privacy protection. The headset 6231 can provide information to the user, so that only a person wearing the headset 6231 can easily recognize the information. Since the information requiring privacy protection is output through the headset 6231, the user can personally confirm the information requiring privacy protection.

In operation S6222, when the result data does not have a value for requesting privacy protection, the smart phone 6220 may determine the current state as a privacy non-protection mode. In operation S6226, in the privacy unprotected mode, the smart phone 6220 may transmit data to the smart watch 6210. In the privacy unprotected mode, data that does not require privacy protection can be transmitted to the smart watch 6210. In operation S6216, as shown in FIG. 66, the smart watch 6210 may display data that does not require privacy protection.

68 and 69 are diagrams for explaining a method for providing a navigation function according to an exemplary embodiment. FIG. 68 is a diagram for explaining a system for providing a navigation function according to an exemplary embodiment.

A system for providing navigation functions according to an exemplary embodiment may include Smart phone 6820, smart watch 6810, and smart glasses 6830.

The smart phone 6820 can be connected to the smart watch 6810 and the smart glasses 6830, and when the smart phone 6820 can use the display capabilities of the smart watch 6810 and the smart glasses 6830, respectively, Glasses 6830 display different information.

Use of the wearable device is explained below. Since the smart watch 6810 is worn on the wrist of the user, the user may need to move his wrist to observe the information displayed on the smart watch 6810. Therefore, the user can confirm the information displayed on the smart watch 6810 at any time.

Since the smart glasses 6830 is worn on the user's face, the user can observe the information displayed on the smart glasses 6830 at any time. On the other hand, if too much information is displayed on the smart glasses 6830, there is a risk that the smart glasses 6830 will hinder the user's observation.

The smart phone 6820 may take into account the use environment of the smart watch 6810 and the smart glasses 6830 to display different information about the wearable device. For example, the smart phone 6820 may transmit data indicating the movement direction to the smart glasses 6830. Referring to FIG. 68, the smart glasses 6830 may display a direction symbol on the display screen of the smart glasses 6830 to direct the user to turn right in operation 6831. The smart glasses 6830 may display a direction symbol in an area other than the center area of the display screen of the smart glasses 6830. For example, the smart glasses 6830 may display a direction symbol in the outermost area of the display screen. In addition, the smart glasses 6830 can display the direction symbols flashing at regular intervals on the display screen.

In addition, the smart phone 6820 may transmit data for displaying additional information about the movement direction to the smart watch 6810. In addition to the direction information simply displayed on the smart glasses 6830, the smart watch 6810 may display additional information used to guide the user to move forward 30 meters to the right alley in operation 6819.

FIG. 69 is a flowchart of a method of providing a navigation function according to an exemplary embodiment. In operation S6812, the smart phone 6820 may receive capability information from the smart watch 6810. In operation S6832, the smart phone 6820 may receive capability information from the smart glasses 6830. The S6812 and S6832 can be started in response to the smart phone 6820 transmitting the capability information transmission request to the smart watch 6810 and the smart glasses 6830.

The smart phone 6820 may receive capability information indicating that the smart watch 6810 has a display capability from the smart watch 6810. The smart phone 6820 may further receive information indicating that the smart watch 6810 is worn on the wrist of the user from the smart watch 6810. The smart phone 6820 may receive the situation information from the smart watch 6810 by receiving an identifier indicating the device type from the smart watch 6810.

Similarly, the smart phone 6820 may receive capability information indicating that the smart glasses 6830 has a display capability from the smart glasses 6830. The smart phone 6820 may further receive, from the smart glasses 6830, information indicating that the smart glasses 6830 is worn on the user's face. Similarly, the smart phone 6820 may receive situation information from the smart glasses 6830 by receiving an identifier indicating the device type from the smart glasses 6830.

In operation S6820, the smart phone 6820 may generate a Capability information for wearable devices. The smart phone 6820 may use the capability information received from the smart watch 6810 and the smart glasses 6830 to generate capability information about the plurality of wearable devices in the memory.

In operation S6822, the smart phone 6820 may use the capability information about the plurality of wearable devices to allocate operations to the wearable devices. The smart phone 6820 may use the capability information about the plurality of wearable devices to allocate operations for displaying navigation to the wearable devices.

Since the smart phone 6820 has the display capabilities of both the smart watch 6810 and the smart glasses 6830, the smart phone 6820 can determine that the operation for displaying navigation information can be assigned to both the smart watch 6810 and the smart glasses 6830 . In operation S6826, the smart phone 6820 may use the situation information about the smart watch 6810 and the smart glasses 6830 to transmit data for displaying additional information to the smart watch 6810. In operation S6824, the smart phone 6820 may transmit data for displaying the driving direction to the smart glasses 6830. For example, the smart phone 6820 may use the information indicating that the smart watch 6810 is worn on the user's wrist to transmit multiple additional information to the smart watch 6810. The smart phone 6820 may transmit simple information (such as a driving direction) that should be displayed immediately to the smart glasses 6830 by using information indicating that the smart glasses 6830 are worn on the user's face.

In operation S6814, the smart watch 6810 may use the additional information data received from the smart phone 6820 to display additional information to the user. Similarly, in operation S6834, the smart glasses 6830 may utilize the smart phone 6820 The received driving direction instruction data displays the driving direction to the user.

70 and 71 are diagrams for explaining a method for providing a navigation function according to another exemplary embodiment.

FIG. 70 is a diagram for explaining a system for providing a navigation function according to an exemplary embodiment.

A system for providing a navigation function according to an exemplary embodiment may include a smart phone 6820, a smart watch 6810, and a smart shoe 6832.

The smart phone 6820 can be connected to a smart watch 6810 and a smart shoe 6832. If the smart phone 6820 can utilize the display capability 6819 of the smart watch 6810 and the vibration capability 6833 of the smart shoe 6832, the smart phone 6820 can display different information to the smart watch 6810 and the smart shoe 6832.

Use of the wearable device is explained below. Since the smart watch 6810 is worn on the wrist of the user, the user should move his wrist to observe the information displayed on the smart watch 6810. Therefore, the user can confirm the information displayed on the smart watch 6810 at any time.

Since the smart shoe 6832 is worn on the user's feet, it may be difficult for the user to confirm the information provided on the smart shoe 6832 in a visual form. Since the smart shoes 6832 are worn on the user's feet, the user's feet can be notified by vibration. Therefore, the user can confirm the information provided by the smart shoe 6832 by vibration at any time. The smart shoe 6832 may include an individual vibrator for each foot of the user, and separately provide vibration to the left and right shoes.

The smart phone 6820 can take into account the smart watch 6810 and smart shoes 6832 uses the environment to indicate different information to the wearable device. For example, the smart phone 6820 may transmit data indicating the direction of movement to the smart shoe 6832. Referring to FIG. 70, in operation 6833, the smart shoe 6832 may use the vibrator of the right foot shoe to provide vibration only to the right foot shoe to provide the user with direction information for guiding the user to turn right.

In addition, the smart phone 6820 may transmit data for displaying additional information about the movement direction to the smart watch 6810. In addition to the directional information simply provided by the smart shoes 6832, the smart watch 6810 may display additional information for guiding the user to move forward 30 meters to the right alley in operation 6819.

FIG. 71 is a flowchart of a method for providing a navigation function according to an exemplary embodiment.

In operation S6812, the smart phone 6820 may receive capability information from the smart watch 6810. In operation S6833, the smart phone 6820 may receive capability information from the smart shoe 6832. The operation of S6812 and S6833 can be started in response to the smart phone 6820 transmitting the capability information transmission request to the smart watch 6810 and the smart shoe 6832.

The smart phone 6820 may receive capability information indicating that the smart watch 6810 has a display capability from the smart watch 6810. The smart phone 6820 may further receive information indicating that the smart watch 6810 is worn on the wrist of the user from the smart watch 6810. The smart phone 6820 may receive the situation information from the smart watch 6810 by receiving an identifier indicating the device type from the smart watch 6810.

Similarly, the smart phone 6820 may receive an indication from the smart shoe 6832 Smart shoes 6832 has the ability to display information about the ability. The smart phone 6820 may further receive information indicating that the smart shoes 6832 are worn on the user's feet from the smart shoes 6832. Similarly, the smart phone 6820 may receive the situation information from the smart shoe 6832 by receiving the identifier indicating the device type from the smart shoe 6832.

In operation S6820, the smart phone 6820 may generate capability information about a plurality of wearable devices. The smart phone 6820 may use the capability information received from the smart watch 6810 and the smart shoe 6832 to generate capability information about the plurality of wearable devices in the memory.

In operation S6822, the smart phone 6820 may use the capability information about the plurality of wearable devices to allocate operations to the wearable devices. The smart phone 6820 may utilize the capability information about the plurality of wearable devices to allocate operations for displaying navigation information to the wearable devices.

Since the smart watch 6810 has a display capability and the smart shoe 6832 has a vibration capability, the smart phone 6820 can allocate operations for displaying navigation information to the smart watch 6810, and use vibration to provide navigation information Operations are assigned to smart shoes 6832.

In operation S6826, the smart phone 6820 may use the situation information about the smart watch 6810 and the smart shoe 6832 to transmit data for displaying additional information to the smart watch 6810. In operation S6825, the smart phone 6820 may transmit the vibration data indicating the driving direction to the smart shoe 6832. For example, the smart phone 6820 may use the information indicating that the smart watch 6810 is worn on the user's wrist to transmit multiple additional information to the smart watch 6810. The smart phone 6820 can transmit simple information (such as a driving direction) that should be displayed immediately to the smart shoe 6832 by using information indicating that the smart shoe 6832 is worn on the user's feet.

In operation S6814, the smart watch 6810 may use the additional information data received from the smart phone 6820 to display additional information to the user. In operation S6835, the smart shoe 6832 may use the driving direction instruction data received from the smart phone 6820 to provide the user with a driving direction through vibration.

72 and 73 are diagrams for explaining a method for providing a navigation function according to another exemplary embodiment.

FIG. 72 is a diagram for explaining a system for providing a navigation function according to an exemplary embodiment.

A system for providing a navigation function according to an exemplary embodiment may include a smart phone 6820, a smart watch 6810, and a headset 6834.

The smart phone 6820 can be connected to a smart watch 6810 and a headset 6834. If the smart phone 6820 can utilize the display capability 6819 of the smart watch 6810 and the audio output capability 6835 of the headset 6834, the smart phone 6820 can indicate information to the smart watch 6810 and different information to the headset 6834.

Since the smart watch 6810 is worn on the wrist of the user, the user should move his wrist to observe the information displayed on the smart watch 6810. Therefore, the user can confirm the information displayed on the smart watch 6810 at any time.

The headset 6834 can provide notification to the user through audio output. Therefore, the user can confirm the information provided by the audio output of the headset 6834 at any time. For example In other words, the earphone 6834 can provide the user with an audio output for guiding the user to turn right. In addition, the earphone 6834 can instruct the user to turn right by outputting a right turn notification sound only to the right earphone 6834.

The smart phone 6820 may provide navigation data to the wearable device taking into account the capability information and situation information of the smart watch 6810 and the headset 6834. For example, the smartphone 6820 may transmit audio data indicating the direction of movement to the headset 6834. As shown in FIG. 72, the earphone 6834 can provide the user with hearing information 6835 for guiding the user to turn to the right.

In addition, the smart phone 6820 may transmit data for displaying additional information about the movement direction to the smart watch 6810. In addition to the hearing information provided by the headset 6834, the smart watch 6810 can display additional information, which is a visual information 6819 used to guide the user to move 30 meters forward to the right alley.

FIG. 73 is a flowchart of a method for providing a navigation function according to an exemplary embodiment.

In operation S6812, the smart phone 6820 may receive capability information from the smart watch 6810. In operation S6836, the smart phone 6820 may receive capability information from the headset 6834. The S6812 and S6836 can be started in response to the capability information transmission request being transmitted to the smart watch 6810 and the headset 6834 on the smart phone 6820.

The smart phone 6820 may receive capability information indicating that the smart watch 6810 has a display capability from the smart watch 6810. The smart phone 6820 may further receive information indicating that the smart watch 6810 is worn on the wrist of the user from the smart watch 6810. The smart phone 6820 can be accessed from the smart watch 6810 An identifier indicating the type of the device is received and situation information is received from the smart watch 6810.

Similarly, the smart phone 6820 may receive capability information from the headset 6834 indicating that the headset 6834 has audio output capabilities. The smart phone 6820 may further receive from the headset 6834 information indicating that the headset 6834 is worn on the user's ear. Similarly, the smart phone 6820 may receive situation information from the headset 6834 by receiving an identifier indicating the device type from the headset 6834.

In operation S6820, the smart phone 6820 may generate capability information about a plurality of wearable devices. The smart phone 6820 may use the capability information received from the smart watch 6810 and the headset 6834 to generate capability information about the plurality of wearable devices in the memory.

In operation S6822, the smart phone 6820 may use the capability information about the plurality of wearable devices to allocate operations to the wearable devices. The smart phone 6820 may utilize the capability information about the plurality of wearable devices to allocate operations for providing navigation information to the wearable devices.

Since the smart watch 6810 has a display capability and the earphone 6834 has an audio output capability, the smart phone 6820 can assign operations for displaying navigation information to the smart watch 6810 and will be used to provide navigation information through audio output. Operations are assigned to headset 6834.

In operation S6828, the smart phone 6820 may use the situation information about the smart watch 6810 and the headset 6834 to transmit data for displaying visual navigation information to the smart watch 6810. In operation S6827, the smart phone 6820 may transmit the auditory navigation information to the headset 6834. For example, the smart phone 6820 Multiple pieces of additional information may be transmitted to the smart watch 6810 by using information indicating the situation in which the smart watch 6810 is worn on the user's wrist. The smart phone 6820 may use the situation information indicating that the earphone 6834 provides the user with auditory information, and transmit simple information (such as the driving direction) that should be displayed immediately to the earphone 6834.

In operation S6815, the smart watch 6810 may use the visual data received from the smart phone 6820 to display visual navigation information to the user. In operation S6838, the earphone 6834 may use the audio data received from the smart phone 6820 to provide audio navigation information through audio output.

74 and 75 are diagrams for explaining a method for providing a navigation function according to another exemplary embodiment.

FIG. 74 is a diagram for explaining a navigation system according to an exemplary embodiment. Referring to FIG. 74, a navigation system according to an exemplary embodiment may include a smart phone 7530, a smart watch 7510, a smart glasses 7520, and a smart shoe 7540.

The smartphone 7530 can be connected to multiple wearable devices for performing operations. When the capabilities of the connected wearable device are available, the operation of some or all of the connected wearable devices may be utilized to perform the functions of the smart phone 7530.

In the exemplary embodiment shown in FIG. 74, as described above, the smart phone 7530 may transmit the data for displaying the additional information of the navigation display to the smart watch 7510. The smart phone 7530 can transmit data for displaying the movement direction immediately and simply to the smart glasses 7520. The smart phone 7530 may transmit data for providing a moving direction to a user by vibration.

On the other hand, the smart phone 7530 can use some wearable devices to Provide navigation function. In the exemplary embodiment shown in FIG. 74 where two wearable devices have display capabilities, the smartphone 7530 may display additional information about only one of the wearable devices 7510 and 7520 with display capabilities.

FIG. 75 is a flowchart of a method for providing a navigation function according to an exemplary embodiment. Specifically, FIG. 75 is a flowchart of a method of providing a navigation function using one of the wearable devices having a display capability and the smart shoe 7540.

First, the smart phone 7530 may receive capability information about the executable capabilities of the wearable device from the wearable device. In operation S7511, the smart phone 7530 may receive capability information from the smart watch 7510. In operation S7521, the smart phone 7530 may receive capability information from the smart glasses 7520. In operation S7541, the smart phone 7530 may receive capability information from the smart shoe 7540. The S7511, S7521, and S7541 can be started in response to the capability information transmission request being transmitted to the smart watch 7510, smart glasses 7520, and smart shoes 7540 on the smart phone 7530.

The smart phone 7530 may receive capability information indicating that the smart watch 7510 has a display capability from the smart watch 7510. In addition, the smart phone 7530 may further receive information indicating that the smart watch 7510 is worn on the wrist of the user from the smart watch 7510. The smart phone 7530 may receive the situation information from the smart watch 7510 by receiving the identifier indicating the device type from the smart watch 7510.

Similarly, the smart phone 7530 may receive capability information indicating that the smart glasses 7520 has a display capability from the smart glasses 7520. Smart phone 7530 Information indicating that the smart glasses 7520 is worn on the user's face can be further received from the smart glasses 7520. Similarly, the smart phone 7530 may receive the situation information from the smart glasses 7520 by receiving an identifier indicating the device type from the smart glasses 7520.

In addition, the smart phone 7530 may receive capability information indicating that the smart shoe 7540 has a display capability from the smart shoe 7540. The smart phone 7530 may further receive information indicating that the smart shoe 7540 is worn on the user's feet from the smart shoe 7540. Similarly, the smart phone 7530 may receive the situation information from the smart shoe 7540 by receiving the identifier indicating the device type from the smart shoe 7540.

In operation S7532, the smart phone 7530 may generate capability information about a plurality of wearable devices. The smart phone 7530 may use the capability information received from the smart watch 7510, the smart glasses 7520, and the smart shoes 7540 to generate capability information about the plurality of wearable devices in the memory.

In operation S7534, the smart phone 7530 may use the capability information about the wearable device to allocate the operation to the wearable device. The smart phone 7530 may use the capability information about the plurality of wearable devices to allocate operations for displaying navigation to the wearable devices.

Since the smart watch 7510 and smart glasses 7520 have display capabilities and the smart shoes 7540 have vibration capabilities, the smart phone 7530 can assign operations for displaying navigation information to the smart watch 7510 or smart glasses 7520, and borrow The operation for providing navigation information is assigned to the smart shoe 7540 by vibration.

For example, when a wearable device is connected, the user can preset the priority of the wearable device to be used. For example, the user may set the highest priority to the smart shoes 7540, the second highest priority to the smart glasses 7520, and the third highest priority to the smart watch 7510. The order of priority is exemplary and not limited to this. This feature is not limited to the provision of navigation functions, but can be applied to the provision of various functions of mobile terminals.

In addition, when a wearable device is connected, the user can preset the number of wearable devices to be used. For example, a user may preset two wearable devices or three or more wearable devices to provide a dynamic navigation function. This feature is not limited to the provision of navigation functions, but can be applied to the provision of various functions.

In the following, for exemplary purposes only, it is assumed that priorities are entered in the order of smart shoes 7540, smart glasses 7520, and smart watches 7510 according to the preset priorities for the smart phone 7530, and two wears are used Device to provide navigation. The smart phone 7530 may use the smart shoes 7540 and the smart glasses 7520 to provide navigation functions according to the priority.

In operation S7536, since the smart shoe 7540 has a vibration capability, the smart phone 7530 may transmit driving direction instruction data for notifying the driving direction by vibration to the smart shoe 7540. In operation S7542, the smart shoe 7540 may use the driving direction instruction data received from the smart phone 7530 to output the driving direction by vibration.

In operation S7538, the smart phone 7530 may transmit data for displaying additional information to the smart glasses 7520. In operation S7522, the smart eye The mirror 7520 may use the additional information received from the smartphone 7530 to display the additional information.

In the exemplary embodiment of the present invention, the example in which the wearable device to be used is determined according to the preset priority of the wearable device has been explained, but the method of setting the wearable device is not limited to this. For example, as described above, the wearable device to be used may be determined in consideration of the situation information. For example, considering whether the connected device is a wearable device being worn or whether the connected wearable device supports the minimum required performance or is greater than the required minimum performance, the device to be used is determined. Wearable device.

76 and 77 are diagrams illustrating a method for providing a music playback function according to an exemplary embodiment.

FIG. 76 is a diagram for explaining a system for providing a music playback function according to an exemplary embodiment.

A system for providing a music playback function according to an exemplary embodiment may include a smart phone 7620, a smart watch 7610, and a headset 7630.

The smartphone 7620 can be connected to a smart watch 7610 and a headset 7630. If the smart phone 7620 can use the display capability 7611 of the smart watch 7610 and the audio output capability 7631 of the headset 6830, the smart phone 7620 can indicate different information to the smart watch 7610 and the headset 7630.

Since the smart watch 7610 is worn on the wrist of the user, the user should move his wrist to observe the information displayed on the smart watch 7610. Therefore, the user can confirm the information displayed on the smart watch 7610 at any time.

The earphone 7630 can output the music being played back to the user through audio output. Therefore, the user can listen to music through the audio output of the headset 7630. The smart phone 7620 may take into account the capability information and situation information of the smart watch 7610 and the headset 7630, and allocate the operation for playing back music to each wearable device, and request the operation execution and / or be used for the operation execution. Data to the wearable to perform the assigned action. For example, the smart phone 7620 may transmit data for outputting audio of the music being played back to the headset 7630, and transmit data for displaying characters of the music being played back to the smart watch 7610.

FIG. 77 is a flowchart of a method for providing a music playback function according to an exemplary embodiment.

In operation S7612, the smart phone 7620 may receive capability information from the smart watch 7610. In operation S7632, the smartphone 7620 may receive capability information from the headset 7630. The operation of S7612 and S7632 can be started in response to the smart phone 7620 transmitting the capability information transmission request to the smart watch 7610 and the headset 7630.

The smart phone 7620 may receive capability information indicating that the smart watch 7610 has a display capability from the smart watch 7610. In addition, the smart phone 7620 may further receive information indicating that the smart watch 7610 is worn on the wrist of the user from the smart watch 7610. The smart phone 7620 may receive the situation information from the smart watch 7610 by receiving an identifier indicating the type of the device from the smart watch 7610.

Similarly, the smart phone 7620 may receive capability information from the headset 7630 indicating that the headset 7630 has audio output capabilities. The smart phone 7620 can be further The headset 7630 receives information indicating that the headset 7630 is worn on a user's ear. Similarly, the smartphone 7620 may receive situation information from the headset 7630 by receiving an identifier indicating the device type from the headset 7630.

In operation S7620, the smartphone 7620 may generate capability information about a plurality of wearable devices. The smart phone 7620 may use the capability information received from the smart watch 7610 and the headset 7630 to generate capability information about the plurality of wearable devices in the memory.

In operation S7622, the smart phone 7620 may use the capability information about the plurality of wearable devices to allocate operations to the wearable devices. The smart phone 7620 may use the capability information about the plurality of wearable devices to allocate an operation for providing information related to music playback to each wearable device.

Since the smart watch 7610 has a display capability and the earphone 7630 has an audio output capability, the smart phone 7620 can assign operations to display music playback information to the smart watch 7610 and use the audio output to provide music playback Information operations are assigned to the headset 7630.

In operation S7626, the smart phone 7620 may use the situation information about the smart watch 7610 and the headset 7630 to transmit visual data (such as music words (e.g., lyrics)) for displaying visual music playback information to the smart watch. 7610. In operation S7624, the smartphone 7620 may transmit the audio data for outputting audio to the headset 7630.

In operation S7614, the smart watch 7610 may use the visual data received from the smart phone 7620 to display visual data (e.g., music) to the user. Word). In operation S7634, the earphone 7630 may use audio data received from the smartphone 7620 to provide audio output.

78 to 82 are diagrams illustrating a method for providing a biological information measurement function according to an exemplary embodiment.

As shown in FIG. 78, a smart watch 7810, a smart phone 7820, and a headset 7830 can be used to implement a method for providing a biological information measurement function according to an exemplary embodiment.

The smart watch 7810 can measure the biological information data and transmit the measured biological information data to the smart phone 7820. For example, the smart watch 7810 may include a temperature sensor for measuring a user's body temperature. The smart watch 7810 may include a blood pressure measurement sensor for measuring a user's blood pressure.

The smart phone 7820 may convert the measured data into audio and transmit the converted audio to the headset 7830, so as to provide the user with the biological information data measured by the smart watch 7810 through the headset 7830.

The smart phone 7820 can determine the user's physical condition by using the biological information data measured by the smart watch 7810 according to a preset method. For example, when the body temperature of the user is within a preset normal range, the smart phone 7820 may determine that the body temperature of the user is within the normal range. When the temperature of the user is outside the preset normal range, the smart phone 7820 may determine that the temperature of the user is not within the normal range. Similarly, when the user's blood pressure is within a preset normal range, the smart phone 7820 may determine that the user's blood pressure is within the normal range. When the user's blood pressure is outside the preset normal range, the smart phone 7820 can determine the user's blood pressure The pressure is outside the normal range.

When the biological information about the user is outside the normal range, the smart phone 7820 may provide a notification to the user. The smart phone 7820 may provide notification to the user through the headset 7830.

FIG. 79 is a flowchart of a method for providing a biological information measurement function according to an exemplary embodiment.

In operation S7820, the smart phone 7820 may generate capability information about a plurality of wearable devices. In operation S7812, the smart watch 7810 can measure biological information. In operation S7814, the smart watch 7810 may transmit the measured biological information to the smart phone 7820.

In operation S7822, the smart phone 7820 may convert the received biological information into audio data. In operation S7824, the smart phone 7820 may transmit the audio data to the headset 7830.

In operation S7832, the earphone 7830 may provide the biological information to the user by outputting the biological information received from the smart phone 7820 in the form of audio.

FIG. 80 is a flowchart of a method for providing a biological information measurement function according to an exemplary embodiment.

Referring to FIG. 80, in operation S7811, when a user inputs a biometric information measurement request to the smart watch 7810, the smart watch 7810 may transmit the biometric information measurement request to the smart phone 7820. In operation S7812, the smart watch 7810 can measure biological information. In operation S7814, the smart watch 7810 The measured biological information can be transmitted to the smartphone 7820.

In operation S7822, the smart phone 7820 may convert the received biological information into audio data. The smart phone 7820 may receive a biometric information measurement request from the smart watch 7810 and convert the received biometric information into audio data.

In operation S7824, the smart phone 7820 may transmit the audio data to the headset 7830. In operation S7832, the earphone 7830 may provide the biological information to the user by outputting the biological information received from the smart phone 7820 in the form of audio.

FIG. 81 is a flowchart of a method for providing a biological information measurement function according to an exemplary embodiment.

Referring to FIG. 81, in operation S7821, when the user inputs a biometric information measurement request to the smart phone 7820, the smart phone 7820 may transmit the biometric information measurement request to the smart watch 7810. In operation S7812, the smart watch 7810 can measure biological information. In operation S7814, the smart watch 7810 may transmit the measured biological information to the smart phone 7820.

In operation S7822, the smart phone 7820 may convert the received biological information into audio data. The smart phone 7820 may receive a biometric information measurement request from the smart watch 7810 and convert the received biometric information into audio data.

In operation S7824, the smart phone 7820 may transmit the audio data to the headset 7830. In operation S7832, the headset 7830 can be input by audio The biological information is provided to the user based on the biological information received by the smartphone 7820.

FIG. 82 is a flowchart of a method for providing a biological information measurement function according to an exemplary embodiment.

Referring to FIG. 82, in operation S7831, when a user inputs a biometric information measurement request into the headset 7830, the headset 7830 may transmit the biometric information measurement request to the smart phone 7820. In operation S7821, when the smart phone 7820 receives a biometric information measurement request from the headset 7830, the smart phone 7820 may transmit the received biometric information measurement request to the smart watch 7810. Subsequently, the smart watch 7810, the smart phone 7820, and the headset 7830 can be operated in substantially the same manner as the biological information measurement method described with reference to FIG. 81.

83 and 84 are block diagrams illustrating a configuration of a mobile terminal 8300 according to an exemplary embodiment.

As shown in FIG. 83, the mobile terminal 8300 according to an exemplary embodiment may include a communication unit 8310 (for example, a communicator), a memory 8320, and a processor 8330. However, all of the elements shown in FIG. 83 are not required, and some of the elements shown may be omitted or otherwise modified. The mobile terminal 8300 may be implemented using a larger number of components than those shown in FIG. 83, or may be implemented using a smaller number of components than those shown in FIG. 83.

For example, as shown in FIG. 84, the mobile terminal 8300 according to an exemplary embodiment may include a user input unit 8340 (for example, a user input device), an output unit 8350 (for example, an output device), and a sensing unit 8360 ( (For example, sensors) And an audio / video (A / V) input unit 8370 (for example, an audio / video input device), and a communication unit 8310, a memory 8320, and a processor 8330.

Hereinafter, each element of the mobile terminal 8300 will be described in order.

The communication unit 8310 may include one or more elements for communicating between the mobile terminal 8300 and an external device or between the mobile terminal 8300 and a server. For example, the communication unit 8310 may include a short-range wireless communication unit 8311, a mobile communication unit 8312, and a broadcast receiving unit 8313.

The short-range wireless communication unit 8311 may include a Bluetooth communication unit, a Bluetooth low energy (BLE) communication unit (for example, a Bluetooth low energy communicator), a near field communication (NFC) / RFID unit (for example, a near field communicator), and a wireless local storage. Wireless local access network (WLAN) (Wi-Fi) communication unit (for example, wireless local access network communicator), Zigbee communication unit (for example, Zigbee communicator), infrared data protocol (IrDA) communication unit (E.g. infrared data protocol communicator), Wi-Fi Direct Connect (WFD) communication unit (e.g. Wi-Fi direct communicator), Ultra Wideband (UWB) communication unit (e.g. Ultra Wideband Communicator), or Ant + Communication unit (for example, Ant + communicator), but it is not limited to this.

The mobile communication unit 8312 may include, but is not limited to, a 3G communication unit (for example, a 3G communicator) and / or a 4G communication unit (for example, a 4G communicator). The mobile communication unit 8312 can transmit and receive wireless signals with at least one selected from a base station, an external terminal, and a server via a mobile communication network. Wireless signals can include voice call signals, video call signals, or various types of data based on text or multimedia message transmission and reception.

The broadcast receiving unit 8313 may receive a broadcast signal and / or broadcast related information via a broadcast channel. The broadcasting channel may include a satellite channel and a terrestrial channel. According to various exemplary embodiments, the mobile terminal 8300 may not include the broadcast receiving unit 8313.

The communication unit 8310 can communicate with multiple wearable devices. The communication unit 8310 may receive information about the executable operations of the wearable device from the wearable device. The communication unit 8310 may receive capability information about the wearable device from the wearable device.

The communication unit 8310 may transmit information about operations performed by the wearable device to the wearable device. The information about the operation may include an operation execution request and / or information for performing the operation.

The communication unit 8310 can receive pulse information, electrocardiogram (ECG) information, and temperature information from an external wearable device. For example, the mobile terminal 8300 can receive pulse information and temperature information from a smart watch.

The memory 8320 can store programs for processing and controlling the processor 8330, and can store input data or output data. For example, the memory 8320 can store applications and multimedia content. In addition, the memory 8320 may store information about operations for performing functions of the mobile terminal 8300. The memory 8320 may store mapping information about an operation for performing a function of the mobile terminal 8300 and a wearable device that will perform the operation. The memory 8320 may store capability information about the wearable device.

The memory 8320 may include at least one storage medium selected from the following: flash memory, hard disk, multimedia card micro memory, card memory (for example, SD or XD memory), random access memory (random access memory, RAM), static random access memory (SRAM), read-only memory (ROM), electrically erasable programmable read-only memory , EEPROM), programmable read-only memory (PROM), magnetic memory, magnetic disks and optical disks. In addition, the mobile terminal 8300 can operate a web storage or a cloud server that performs the storage function of the memory 8320 on the Internet.

The programs stored in the memory 8320 can be classified into a plurality of modules according to functions. For example, the program can be classified into a user interface module 8321, a touch screen module 8322, a notification module 8323, and a speak-to-text (STT) module 8324.

The user interface module 8321 may provide a dedicated user interface or a graphical user interface (GUI) that interacts with the mobile terminal 8300 according to an application program. The touch screen module 8322 can detect a user's touch gesture on the touch screen and transmit information about the touch gesture to the processor 8340. According to an exemplary embodiment, the touch screen module 8322 may recognize and analyze a touch code. The touch screen module 8322 can be implemented using separate hardware including a controller.

Various types of sensors can be set in or near the touch screen to sense touches on the touch screen or hover over the touch screen. An example of a sensor for sensing a touch on a touch screen may be a tactile sensor. The tactile sensor can sense the touch of a specific object with a higher sensitivity than the sensitivity of a human touch. Tactile sensors can sense information such as the roughness of the touch surface, the hardness of the touched object, and the touch point temperature.

In addition, an example of a sensor for sensing a touch on a touch screen may be a proximity sensor.

The proximity sensor may use electromagnetic force or infrared rays instead of any mechanical contact to detect whether there is an object near the predetermined detection surface or an object existing near the sensor. Examples of proximity sensors may include transmission-type photoelectric sensors, direct reflection-type photoelectric sensors, mirror reflection-type photoelectric sensor, radio frequency oscillation-type proximity sensor, electrostatic capacity-type proximity sensor, magnetic proximity sensor, and infrared proximity sensor. Examples of the user's touch gestures include tap, touch and hold, double-tap, drag, panning, flick, drag Drag-and-drop, swipe, etc.

The notification module 8323 may generate a signal for notifying the occurrence of an event in the mobile terminal 8300. Examples of the events occurring in the mobile terminal 8300 may include call signal reception, message reception, key signal input, and schedule notification. The notification module 8323 can output a notification signal in the form of a video signal through the display unit 8351. The notification module 8323 can output a notification signal in the form of an audio signal through the audio output unit 8352. The notification module 8323 can output a notification signal in the form of a vibration signal through the vibration motor 8353.

The pronunciation-text module 8324 can convert the speech contained in the multimedia content into a text to generate a transcript corresponding to the multimedia content. Transcripts can be mapped to information about the playback time of multimedia content.

The content storage module 8325 may include at least one type of content. The content storage module 8325 can store multimedia content. The content storage module 8325 can store the multimedia content to be played back in the mobile terminal 8300 or at least one wearable device. The multimedia content may include text data, still image and / or moving image data, audio data, and the like.

The processor 8330 may include a central processing unit (CPU), an application processor (AP), and / or an accelerated processing unit (APU), but is not limited thereto. For example, the processor 8330 may include an ARM processor, an Intel processor, and / or an AMD processor, but is not limited thereto. The processor 8330 may control the overall operation of the mobile terminal 8330. For example, the processor 8330 can control the output unit 8350, the user input unit 8340, the communication unit 8310, the sensing unit 8360, and the audio / video input unit 8370 by executing programs stored in the memory 8320.

The processor 8330 can use the mapping information stored in the memory 8320 to identify the connection between the first wearable device and the second wearable device that will perform the operation. When the connection of the second wearable device is recognized, the processor 8330 may control the communication unit 8310 to transmit information for performing the operation to the first wearable device, so as to communicate the operation with the operation to be performed by the second wearable device. Perform together to perform the functions of the mobile terminal 8300.

When the connection of the second wearable device is not recognized, the processor 8330 may control the communication unit 8310 to transmit information for performing the operation to the first wearable device to perform without performing the operation of the second wearable device. The operations are performed to perform the functions of the mobile terminal 8300.

The processor 8330 may control the communication unit 8310 to transmit information about a user interface for performing functions of the mobile terminal 8300 to the first wearable device.

The processor 8330 may use the mapping information to determine a wearable device capable of performing an operation for performing a function of the mobile terminal 8300 as a wearable device that will perform the operation.

The processor 8330 may use the device performance information and the minimum performance information to determine a wearable device that will perform operations for performing the functions of the mobile terminal 8300. The mapping information may include device performance information about the wearable device and minimum performance information required to perform operations for performing functions of the mobile terminal 8300.

The processor 8330 may use the device performance information and the minimum performance information to determine a wearable device capable of performing an operation with performance required for performing operations of the functions of the mobile terminal 8300 as a wearable device that will perform the operation.

The processor 8330 may use the device performance information and the minimum performance information to determine a wearable device that will execute a user interface for performing functions of the mobile terminal 8300.

The processor 8330 may use the operation execution result data of the first wearable device received from the first wearable device to control the operations to be performed by the second wearable device.

The processor 8330 may use the mapping information stored in the memory 8320 to identify the connection of the first wearable device and the second wearable device that will perform the operation. When the connection of the second wearable device is recognized, the processor 8330 may control the communication unit 8310 to transmit information for executing a user interface to the first wearable device, so that the user interface and the second wearable device The audio output operations performed by the device are performed together to perform the functions of the mobile terminal 8300. When the connection of the second wearable device is not recognized, the processor 8330 may control the communication unit 8310 to transmit the information for performing the user interface to the first wearable device, so as not to perform the audio output operation of the second wearable device. The user interface is performed to perform the functions of the mobile terminal 8300.

The processor 8330 may use the capability information about the plurality of wearable devices stored in the memory 8320 to determine a wearable device that will perform a first operation for performing a function of the mobile terminal 8300, and a wearable device that will perform the first operation. An operation of a second wearable device that performs a second operation together to perform a function of the mobile terminal 8300. The processor 8330 may use the information about the determined device to control the communication unit 8310 to transmit information about the first operation to the first wearable device, and transmit information about the second operation to the second wearable device.

The user input unit 8340 may be a unit that allows a user to input data for controlling the mobile terminal 8300. For example, the user input unit 8340 may include a key pad, a dome switch, a touch pad (for example, a touch capacitive touch pad, a pressure resistive touch pad, and an infrared beam sensor). Test type touch pad, surface acoustic wave type touch pad, overall strain gauge type touch pad, piezoelectric effect type touch pad Etc.), jog wheel and jog switch, but it is not limited to this.

The output unit 8350 can output an audio signal, a video signal, or a vibration signal. The output unit 8350 may include a display unit 8351 (for example, a display), an audio output unit 8352 (for example, an audio output device), and a vibration motor 8353.

The display unit 8351 can display information processed by the mobile terminal 8300. In a case where the display unit 8351 and the touch pad form a layered structure to form a touch screen, the display unit 8351 can also be used as an input device and an output unit. The display unit 8351 may include at least one selected from the group consisting of a liquid crystal display (LCD), a thin-film transistor-liquid crystal display (TFT-LCD), and an organic light-emitting diode. (organic light-emitting diode, OLED), flexible display, three-dimensional (3D) display and electrophoretic display. According to the implementation of the mobile terminal 8300, the mobile terminal 8300 may include two or more display units 8351.

The audio output unit 8352 can output audio data received from the communication unit 8310 or audio data stored in the memory 8320. In addition, the audio output unit 8352 can output audio signals (for example, call signal reception sound, message reception sound, and notification sound) related to the functions performed by the mobile terminal 8300. The audio output 8352 may include a speaker, a buzzer, and the like.

The vibration motor 8353 can output vibration signals. For example, the vibration motor 8353 may output a vibration signal corresponding to the output of audio data or video data (eg, call signal reception sound, message reception sound, etc.). Also, when the touch input When the touch screen is reached, the vibration motor 8353 can output vibration signals.

The sensing unit 8360 may sense a state of the mobile terminal 8300 or a state around the mobile terminal 8300, and transmit the sensed information to the processor 8330.

The sensing unit 8360 may include at least one selected from the following: a geomagnetic sensor 8361, an acceleration sensor 8362, a temperature / humidity sensor 8363, an infrared sensor 8364, a gyroscope sensor 8365, a position sensor Sensors (for example, Global Position System (GPS)) 8366, pressure sensor 8367, proximity sensor 8368, and RGB sensor (illumination sensor) 8369, but it is not limited to this. Since the function of each sensor can be inferred intuitively from the name of the sensor, it will not be described again.

The audio / video input unit 8370 enables a user to input audio or video signals, and may include a camera 8371 and a microphone 8372. The camera 8371 can obtain an image frame (for example, a still picture or a moving picture) by using an image sensor in a video call mode or a shooting mode. The image captured by the image sensor may be processed by the processor 8330 or a separate image processor (not shown).

The image frame processed in the camera 8371 can be stored in the memory 8320, or can be transmitted to the outside through the communication unit 8310. The audio / video input unit 8370 may include two or more cameras 8371 according to the configuration of the mobile terminal 8300.

The microphone 8372 can receive external audio signals and process the external audio signals into electrical voice data. For example, the microphone 8372 may receive audio signals from an external device or a person speaking. The microphone 8372 can use various noise cancellation algorithms to eliminate noise generated during the process of receiving external audio signals.

85 to 87 are block diagrams illustrating a configuration of a wearable device 8500 according to an exemplary embodiment.

As shown in FIG. 85, the wearable device 8500 according to an exemplary embodiment may include a communication unit 8510 (for example, a communicator), a memory 8520, a processor 8530, a user input unit 8540 (for example, a user input device), and An output unit 8550 (for example, an outputter). However, not all the elements shown in FIG. 85 are necessary. For example, as shown in FIG. 86, the user input unit 8540 can be omitted. Therefore, the wearable device 8500 can be implemented with a smaller number of components than those shown in FIG. 85. As shown in FIG. 87, the wearable device 8500 can be implemented using a larger number of components than those shown in FIG. 85.

For example, as shown in FIG. 87, the wearable device 8500 according to an exemplary embodiment may include a user input unit 8540 (eg, a user input device), an output unit 8550 (eg, an output device), and a sensing unit 8560 (Eg, a sensor) and an audio / video input unit 8570 (audio / video input), and a communication unit 8510 (eg, a communicator), a memory 8520, and a processor 8530. The components of the wearable device 8500 may be substantially the same as those of the mobile terminal 8300, or the components of the wearable device 8500 may correspond to the components of the mobile terminal 8300, but are different in some aspects. Hereinafter, elements of the wearable device 8500 that are different from those of the mobile terminal 8300 will be explained.

The communication unit 8510 may include one or more components for communicating between the wearable device 8500 and the mobile terminal 8300. For example, the communication unit 8510 may include a short-range wireless communication unit 8511 (for example, a short-range wireless communicator), mobile communication The communication unit 8512 (for example, a mobile communicator) and the broadcast receiving unit 8513 (for example, a broadcast receiver).

The communication unit 8510 may receive information from the mobile terminal 8300 for performing operations according to connection information about whether a wearable device to perform operations for performing functions of the mobile terminal 8300 is connected to the mobile terminal 8300.

The communication unit 8510 may transmit the result data obtained by performing the operation according to the information used to perform the operation to the mobile terminal 8300. For example, the wearable device 8500 can transmit pulse information and temperature information to the mobile terminal 8300.

The processor 8530 can control the overall operation of the wearable device 8500. For example, the processor 8530 can control the output unit 8550, the user input unit 8540, the communication unit 8510, the sensing unit 8560, and the audio / video input unit 8570 by executing programs stored in the memory 8520.

Based on the information used to perform the operation, the processor 8530 can control the communication unit 8510, the memory 8520, the user input unit 8540, the sensing unit 8560, and the audio / video input unit 8570 when another wearable device is connected to the mobile terminal 8300. Performing an operation to perform the operation together with an operation to be performed by another wearable device to perform a function of the mobile terminal 8300, and performing an operation to perform the operation when the other wearable device is not connected to the mobile terminal 8300 In the case of the operation of the wearable device, the operation is performed to perform the operation of the mobile terminal 8300.

In addition, other exemplary embodiments may also be implemented by computer-readable codes or instructions in or on a medium (for example, computer-readable medium) to control at least one processing element to implement any of the above-described exemplary implementations. example. The media may correspond to content Any media or any type of media that may store and / or transmit computer readable codes may be stored and / or transmitted.

Computer readable codes can be recorded or transmitted on media in various ways. Examples of media include recording media (such as magnetic storage media (e.g., read-only memory, floppy disks, hard disks, etc.) and optical recording media (e.g., optical discs). Compact disc read only memory (CD-ROM) or digital versatile disc (DVD)), and transmission media (such as Internet transmission media). Therefore, according to one or more exemplary embodiments, the medium may be such a defined and measurable structure for containing or carrying signals or information, such as a device carrying a bit stream. The media can also be located on a distributed network, allowing computer-readable codes to be stored or transmitted and executed in a distributed fashion. In addition, the processing elements may include a processor or a computer processor, and the processing elements may be distributed and / or contained in a single device.

It should be understood that the exemplary embodiments described herein should be considered in a descriptive sense only and not for purposes of limitation. Descriptions of features or aspects in each exemplary embodiment should generally be considered as being available for other similar features or aspects in other exemplary embodiments.

Although one or more exemplary embodiments have been described with reference to the drawings, those having ordinary knowledge in the art will understand that various forms and forms can be made without departing from the spirit and scope defined by the scope of the following patent applications. Changes in details.

Claims (15)

A mobile terminal includes: a communicator to communicate with a plurality of wearable devices; a memory to store capability information indicating the capabilities of the plurality of wearable devices; and a processor to be based on the capability information And determining a first wearable device and a second wearable device among the plurality of wearable devices, where the first wearable device is configured to perform a first sub-function for performing a function of the mobile terminal, the The second wearable device is configured to perform a second sub-function, and the second sub-function is to be executed together with the first sub-function to perform the function of the mobile terminal, wherein the processor is configured to control the first sub-function A wearable device performs the first sub-function and controls the second wearable device to perform the second sub-function. The mobile terminal according to item 1 of the patent application scope, wherein the processor is configured to control the communicator to transmit information about a user interface for performing the function of the mobile terminal to the first wearer式 装置。 Devices. The mobile terminal according to item 1 of the scope of patent application, wherein the processor is configured to access the capability information to determine that the plurality of wearable devices can execute a function for performing the functions of the mobile terminal. The sub-function wearable device serves as a wearable device to be used to perform the sub-function. The mobile terminal according to item 3 of the scope of patent application, wherein the memory is further used to store mapping information, the mapping information includes device performance information and minimum performance information, and the device performance information indicates the multiple wearables A device performance capability of the device, the minimum performance information indicates a minimum performance required to execute the sub-functions for performing the functions of the mobile terminal, and the processor is used to access the device Performance information and the minimum performance information to determine the wearable device to be used to perform the sub-functions for performing the functions of the mobile terminal. The mobile terminal according to item 4 of the scope of patent application, wherein the processor is configured to access the device performance information and the minimum performance information to determine that the The performance required for the sub-functions of the function is the wearable device that performs the sub-function as the wearable device that will be used to perform the sub-function. The mobile terminal according to item 4 of the patent application scope, wherein the processor is configured to access the device performance information and the minimum performance information to determine that the plurality of wearable devices will be used to execute A wearable device of the user interface of the mobile terminal. The mobile terminal according to item 1 of the scope of patent application, wherein the processor is configured to use the sub-function execution result data of the first wearable device received from the first wearable device to control the second device to be controlled by the second wearable device. The second sub-function performed by the wearable device. A mobile terminal includes: a communicator to communicate with a plurality of wearable devices; a memory to store capability information indicating the capabilities of the plurality of wearable devices; and a processor to be based on the capability information A first sub-function and a second sub-function are determined, the first sub-function is performed by a first wearable device for performing a function of the mobile terminal, and the second sub-function is used by a second wearable device And a first-type device is executed together with the first sub-function to execute the function of the mobile terminal, wherein the processor controls the communicator to transmit information about the first sub-function to the first wearable Device and transmitting information about the second sub-function to the second wearable device. A mobile terminal includes: a communicator to communicate with a plurality of wearable devices; a memory to store mapping information, and the mapping information maps a plurality of sub-functions for performing functions of the mobile terminal to the application A plurality of wearable devices performing the plurality of sub-functions; and a processor for identifying a first wearable device of the plurality of wearable devices based on the mapping information to perform the plurality of sub-functions And a second wearable device, wherein when the connection of the second wearable device is identified, the processor is used to control the communicator to transmit information for performing a first sub-function to the A first wearable device to execute the first sub-function together with a second sub-function to be performed by the second wearable device to perform the function of the mobile terminal, and when the second When the wearable device is connected, the processor is configured to control the communicator to transmit information for performing the first sub-function to the first wearable device so that the second wearable device is not executed. Executing the first sub-function when the second sub-function-type device in order to perform the functions of the mobile terminal. A wearable device includes a communicator for receiving information from a mobile terminal for performing a first sub-function based on connection information, the connection information indicating that a plurality of sub-functions for performing a function of the mobile terminal will be performed Whether the plurality of wearable devices are connected to the mobile terminal; and a processor configured to, when another wearable device is connected to the mobile terminal, based on the information for performing the first sub-function, The first sub-function is performed together with a second sub-function to be performed by the other wearable device to perform the function of the mobile terminal, and when the other wearable device is not connected to the mobile terminal, Executing the first sub-function without performing the second sub-function of the other wearable device based on the information for performing the first sub-function to execute the mobile terminal Features. A method for performing a function of a mobile terminal, the method comprising: generating capability information indicating capabilities of a plurality of wearable devices; and determining a first wearable device and a first of the plurality of wearable devices based on the capability information. Two wearable devices, the first wearable device is used to perform a first sub-function for performing a function of the mobile terminal, the second wearable device is used to perform a second sub-function, and the second sub-function A function to be executed together with the first sub-function to perform the function of the mobile terminal, to control the first wearable device to perform the first sub-function; and to control the second wearable device to perform the The second sub-function. A method for performing a function of a mobile terminal, the method comprising: generating capability information indicating capabilities of a plurality of wearable devices; and determining a first sub-function and a second sub-function based on the capability information, the first sub-function Configured to be executed by a first wearable device for performing a function of the mobile terminal, and the second sub-function is configured to be executed by a second wearable device together with the first sub-function; Transmitting information about the sub-function to the first wearable device; and transmitting information about the second sub-function to the second wearable device. A method for executing a function of a mobile terminal, the method comprising: generating mapping information, the mapping information mapping a plurality of sub-functions for performing a function of the mobile terminal to a plurality of A wearable device; identifying a connection between a first wearable device and a second wearable device of the plurality of wearable devices to perform the multiple sub-functions based on the mapping information stored in the memory; and Transmitting information to the first wearable device, wherein the step of transmitting the information to the first wearable device includes: when the connection of the second wearable device is identified, using the Information for performing a first sub-function is transmitted to the first wearable device to execute the first sub-function together with a second sub-function to be performed by the second wearable device to perform all the functions of the mobile terminal The function described above; and when the connection of the second wearable device is not recognized, transmitting information for performing a first sub-function to the first wearable device so as not to execute the Executing the first sub-function when the second sub-functional dicarboxylic wearable device in order to perform the functions of the mobile terminal. A method for executing a sub-function of a wearable device, the method comprising: receiving information for performing a first sub-function according to connection information, the connection information representing a plurality of sub-functions for performing functions of a mobile terminal Whether the plurality of wearable devices are connected to the mobile terminal; when another wearable device is connected to the mobile terminal, the first sub-function is based on the information for executing the first sub-function Execute with the second sub-function to be performed by the other wearable device to perform the function of the mobile terminal; and when the other wearable device is not connected to the mobile terminal, based on the The information of the first sub-function executes the first sub-function to perform the function of the mobile terminal without executing the second sub-function of the other wearable device. A non-transitory computer-readable recording medium having stored thereon a program for causing a computer to execute the method described in item 11 of the scope of patent application.