KR102469752B1 - Wearable device and method for controlling the same - Google Patents

Abstract

A wearable device and a control method thereof are provided. A wearable device may include a sensor unit configured to detect at least one movement of the wearable device; and a first mode for determining a state of the wearable device based on the detected motion and executing a preset function of the wearable device or a second mode for ignoring execution of the preset function based on the determined state. and a control unit controlling the wearable device to operate the wearable device in a mode.

Description

Wearable device and its control method {Wearable device and method for controlling the same}

Embodiments of the present invention relate to a wearable device and a control method thereof.

Recently, various types of wearable devices are being used. A wearable device refers to a type of electronic device that can be worn on the body, and various types of wearable devices such as smart watches, smart glasses, and smart bands, for example, are provided. Due to the nature of devices carried by users, wearable devices can collect various information about users, such as measuring body signals and recognizing motions. Also, based on the collected information, the wearable device may provide various functions. However, when various functions are provided based on information collected from the wearable device, an operation unintentional by the user is recognized, causing inconvenience to the user.

Embodiments of the present invention are intended to prevent a wearable device from malfunctioning against the user's intention when the wearable device recognizes a user's motion and provides a predetermined function.

In addition, embodiments of the present invention are intended to increase user convenience by changing function settings of the wearable device or executing necessary functions when the user of the wearable device is driving.

In addition, embodiments of the present invention are intended to provide various functions to the user by communicating with the vehicle while the user of the wearable device is driving.

In addition, embodiments of the present invention are intended for a wearable device to more accurately recognize a user's driving state.

A first aspect of the present disclosure is a sensor unit for detecting at least one movement of the wearable device; A first mode for determining a state of the wearable device based on the detected motion and executing a preset function of the wearable device based on the determined state or a second mode for ignoring execution of the preset function It is possible to provide a wearable device including a; control unit for controlling the wearable device so that the wearable device operates.

Further, the controller determines whether a state of the wearable device corresponds to a state in which a user of the wearable device is driving a vehicle based on the detected motion, and determines whether the first mode is performed according to the state of the wearable device. Alternatively, the second mode may be selected.

In addition, when the state of the wearable device corresponds to a state in which the user is driving a vehicle, the controller operates the wearable device in the second mode, and the state of the wearable device corresponds to a state in which the user is driving a vehicle. If it does not correspond to , the wearable device may be operated in the first mode.

Also, the preset function may be a function corresponding to the detected motion.

The wearable device further includes a display unit displaying state information of the wearable device, wherein the display unit is automatically activated in the first mode according to the detected motion, and the display unit is activated in the second mode. can be ignored.

Also, the number of steps of the user may be counted by a pedometer application running on the wearable device in the first mode according to the detected motion, and the count of the number of steps may be ignored in the second mode.

Further, the controller may execute a preset application when the state of the wearable device corresponds to a state in which the user of the wearable device is driving a vehicle.

Also, when the state of the wearable device corresponds to a state in which the user of the wearable device is driving a vehicle, the controller may block a notification provided to the wearable device from an external device connected to the wearable device.

Also, when the state of the wearable device corresponds to a state in which a user of the wearable device is driving a vehicle, the controller may control the vehicle so that the wearable device uses at least one output device of the vehicle.

In addition, when the state of the wearable device corresponds to a state in which the user of the wearable device is driving a vehicle, the control unit obtains at least one of state information and driving information of the vehicle from the vehicle, and connects the wearable device to the wearable device. At least one of the vehicle state information and the driving information may be provided to an external device.

In addition, the sensor unit includes an acceleration sensor for detecting vibration and rotation angle,

The control unit may determine the state of the vehicle by comparing the detected vibration pattern and the detected rotation angle pattern with a pre-stored vibration pattern and a stored rotation angle pattern, respectively.

The wearable device may further include a communication unit configured to receive vehicle information from the vehicle, and the control unit may determine a state of the wearable device based on the received vehicle information, such that a user of the wearable device is driving a vehicle. It can be judged whether it corresponds to .

In addition, when the received vehicle information is public transportation vehicle information, the controller determines that the state of the wearable device does not correspond to a state in which the user of the wearable device is driving a vehicle. can

In addition, a second aspect of the present disclosure includes sensing at least one movement of the wearable device; determining a state of the wearable device based on the detected motion; and controlling the wearable device to operate the wearable device in a first mode of executing a preset function of the wearable device or a second mode of ignoring execution of the preset function, based on the determined state; Including, it is possible to provide a control method of a wearable device.

In addition, the determining of the state may include determining whether the state of the wearable device corresponds to a state in which the user of the wearable device is driving a vehicle based on the detected movement, and determining whether the state of the wearable device Accordingly, the first mode or the second mode may be selected.

The controlling may include operating the wearable device in the second mode when a state of the wearable device corresponds to a state in which the user is driving a vehicle, and the state of the wearable device corresponds to a state in which the user is driving a vehicle. If it does not correspond to the current state, the wearable device may be operated in the first mode.

Also, the preset function may be a function corresponding to the detected motion.

Also, the display unit of the wearable device may be automatically activated in the first mode according to the detected movement, and activation of the display unit may be ignored in the second mode.

Also, the number of steps of the user may be counted by a pedometer application running on the wearable device in the first mode according to the detected motion, and the count of the number of steps may be ignored in the second mode.

The controller may control the vehicle so that the wearable device uses at least one output device of the vehicle when the state of the wearable device corresponds to a state in which the user of the wearable device is driving the vehicle. have.

In addition, a third aspect of the present disclosure, the communication unit for receiving state information of the wearable device from the wearable device; and determining a driving state of a user wearing the wearable device based on the state information, and providing a control command for executing at least one function of the wearable device to the wearable device through the communication unit according to the driving state. It is possible to provide a mobile device for controlling a wearable device, including a; control unit to do.

The communication unit may receive vehicle information from a vehicle terminal, and the control unit may determine whether the user is driving based on the received vehicle information and state information of the wearable device.

In addition, the control unit determines a condition for the wearable device to execute the function, and provides information on the determined condition to the wearable device together with the control command, wherein the condition is related to the driving state of the user. may be a condition.

In addition, a fourth aspect of the present disclosure includes receiving state information of the wearable device from the wearable device; determining a driving state of a user wearing the wearable device based on state information of the wearable device; and providing the wearable device with a control command for executing at least one function of the wearable device according to the determined driving state.

In addition, a fifth aspect of the present disclosure may provide a computer-readable recording medium on which a program for executing the method of the fourth aspect is recorded on a computer.

According to embodiments of the present invention, when a wearable device recognizes a user's motion and provides a predetermined function, it is possible to prevent the wearable device from malfunctioning against the user's intention.

In addition, according to embodiments of the present invention, when a user of the wearable device is driving, user convenience can be increased by changing a function setting of the wearable device or executing a necessary function.

In addition, according to the embodiments of the present invention, when the user of the wearable device is driving, there is an effect of providing various functions to the user by communicating with the vehicle.

In addition, according to embodiments of the present invention, there is an effect that the wearable device can more accurately recognize the user's driving state.

1 is a diagram for explaining an operation of a wearable device 100 according to an exemplary embodiment.
2 is a diagram illustrating a structure of a wearable device 100a according to an exemplary embodiment.
3 is a diagram illustrating a structure of a sensor unit 210a according to an exemplary embodiment.
4 is a flowchart illustrating a method for controlling a wearable device according to an exemplary embodiment.
5 is a diagram for explaining a process of changing a function setting of the wearable device 100b according to an exemplary embodiment.
6 is a diagram illustrating a structure of a wearable device 100b according to an exemplary embodiment.
7 is a diagram illustrating an operation of the wearable device 100b according to an exemplary embodiment.
8 is a diagram illustrating motion recognition of the wearable device 100b according to an exemplary embodiment.
9 is a diagram illustrating an operation of the wearable device 100b according to an exemplary embodiment.
10 is a diagram for explaining an operation of the wearable device 100b according to an exemplary embodiment.
11 is a diagram describing an operation of the wearable device 100b according to an exemplary embodiment.
12 is a diagram for explaining an operation of the wearable device 100b according to an exemplary embodiment.
13 is a diagram for explaining an operation of the wearable device 100b according to an exemplary embodiment.
14 is a flowchart illustrating a control method of the wearable device 100b according to an exemplary embodiment.
15 is a diagram for explaining an operation of executing a preset function in the wearable device 100b when a user is driving, according to an exemplary embodiment.
16 is a diagram for explaining an operation of executing a preset function when a user is driving in the wearable device 100b according to an exemplary embodiment.
17 is a diagram for explaining an operation of executing a preset function in the wearable device 100b when a user is driving, according to an exemplary embodiment.
18 is a diagram illustrating a structure of a wearable device 100c according to an exemplary embodiment.
19 is a diagram illustrating how the wearable device 100c communicates with external devices 1910a, 1910b, and 1910c according to an embodiment.
20 is a diagram showing the structure of a communication unit 1810a according to an embodiment.
21 is a flowchart illustrating a control method of the wearable device 100c according to an exemplary embodiment.
22 is a diagram illustrating the wearable device 100c and the external device 1910b according to an embodiment.
23 is a diagram illustrating the wearable device 100c and the external device 1910b according to an embodiment.
24 is a flowchart illustrating a control method of the wearable device 100c according to an exemplary embodiment.
25 is a flowchart illustrating a method of determining whether a wearable device user is driving, according to an embodiment.
26 is a diagram for explaining a method of determining whether a user of the wearable device 100a is driving, according to an exemplary embodiment.
27 is a diagram illustrating a structure of a wearable device 100b according to an embodiment.
28 is a diagram illustrating a structure of a wearable device 100a according to an exemplary embodiment.
29 is a diagram illustrating a structure of a wearable device 100b according to an embodiment.
30 is a diagram illustrating a structure of a wearable device 100a according to an exemplary embodiment.
31 is a diagram illustrating a structure of a wearable device 100a according to an exemplary embodiment.
32 is a flowchart illustrating a method of determining whether a user of a wearable device is driving, according to an embodiment.
33 is a diagram for explaining a method of determining whether a user is driving according to an embodiment.
34 is a diagram for explaining a method of determining whether a user is driving according to an embodiment.
35 is a diagram for explaining a method of determining whether a user is driving according to an embodiment.
36 is a flowchart illustrating a method of determining whether a user is driving according to an embodiment.
37 is a diagram for explaining a method of determining whether a user is driving according to an embodiment.
38 is a diagram for explaining a method of determining whether a user is driving according to an embodiment.
39 is a flowchart illustrating a method of determining whether a user is driving according to an embodiment.
40 is a flowchart illustrating a method for controlling a wearable device according to an embodiment.
41 is a flowchart illustrating a method of determining whether a user of the wearable device 100a is riding in a vehicle according to an exemplary embodiment.
42 is a flowchart illustrating a method of determining whether a user of the wearable device 100a is riding in a vehicle according to an exemplary embodiment.
43 is a flowchart illustrating a method of determining whether a user of the wearable device 100a is riding in a vehicle according to an exemplary embodiment.
44 is a flowchart illustrating a control method of the wearable device 100a according to an embodiment.
45 is a flowchart illustrating a method of determining whether a user has boarded public transportation according to an embodiment.
46 is a flowchart illustrating a method of determining whether a user has boarded public transportation according to an embodiment.
47 is a flowchart illustrating a method of determining whether a user has boarded public transportation according to an embodiment.
48 is a block diagram illustrating a configuration of a wearable device 100d according to an exemplary embodiment.
49 is a diagram illustrating an example in which the wearable device 100 performs a specific function according to a user's situation in a vehicle using at least one of a mobile device 1910a and a vehicle 1910b, according to an embodiment. to be.
50 is a flowchart of a method in which the wearable device 100 forms a network with the mobile device 1910a and the vehicle 1910b and performs a specific function while the user is driving, according to an embodiment.
51 is a flowchart of a method of forming a network with a mobile device 1910a by the wearable device 100 and performing a specific function while a user is driving, according to an embodiment.
52 is a flowchart of a method of performing a specific function when the wearable device 100 forms a network with the vehicle 1910b and the user is driving, according to an embodiment.
53 is a flowchart of a method of executing a function of the wearable device 100 according to a control command received from the mobile device 1910a when the wearable device 100 satisfies a predetermined condition, according to some embodiments.
54 is a flowchart of a method of executing a function of the wearable device 100 according to a control command received from a vehicle 1910b when the wearable device 100 satisfies a predetermined condition, according to some embodiments.
55 is a diagram illustrating an example in which the wearable device 100 of a user driving a vehicle 1910b and the mobile device 1910a perform a call with another device 200 of another user, according to some embodiments.
FIG. 56 is a diagram illustrating an example of a method in which the wearable device 100c of a user while driving makes a phone call with another device 200 through the mobile device 1910a, according to some embodiments.
FIG. 57 is a diagram illustrating an example of a method for a user's wearable device 100c while driving to make a direct phone call with another device 200, according to some embodiments.

Advantages and features of the present invention, and methods of achieving them, will become clear with reference to the embodiments described below in conjunction with the accompanying drawings. However, the present invention is not limited to the embodiments disclosed below, but may be implemented in various different forms, and only these embodiments make the disclosure of the present invention complete, and common knowledge in the art to which the present invention belongs. It is provided to completely inform the person who has the scope of the invention, and the present invention is only defined by the scope of the claims.

The terms used in this specification will be briefly described, and the present invention will be described in detail.

The terms used in the present invention have been selected from general terms that are currently widely used as much as possible while considering the functions in the present invention, but these may vary depending on the intention of a person skilled in the art or precedent, the emergence of new technologies, and the like. In addition, in a specific case, there is also a term arbitrarily selected by the applicant, and in this case, the meaning will be described in detail in the description of the invention. Therefore, the term used in the present invention should be defined based on the meaning of the term and the overall content of the present invention, not simply the name of the term.

When it is said that a certain part "includes" a certain component throughout the specification, it means that it may further include other components without excluding other components unless otherwise stated. Also, the term "unit" used in the specification means a hardware component such as software, FPGA or ASIC, and "unit" performs certain roles. However, "unit" is not meant to be limited to software or hardware. A “unit” may be configured to reside in an addressable storage medium and may be configured to reproduce on one or more processors. Thus, as an example, “unit” can refer to components such as software components, object-oriented software components, class components and task components, processes, functions, properties, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuitry, data, databases, data structures, tables, arrays and variables. Functionality provided within components and "parts" may be combined into fewer components and "parts" or further separated into additional components and "parts".

Hereinafter, with reference to the accompanying drawings, embodiments of the present invention will be described in detail so that those skilled in the art can easily carry out the present invention. And in order to clearly explain the present invention in the drawings, parts irrelevant to the description are omitted.

1 is a diagram for explaining an operation of a wearable device 100 according to an exemplary embodiment.

When the wearable device 100 according to this embodiment recognizes that a user wearing the wearable device 100 is driving, it automatically executes a function provided by the wearable device 100 (S110), or the wearable device 100 It is possible to change the settings of functions provided in (S120).

The wearable device 100 refers to an electronic device in a form wearable by a user. The wearable device 100 may be implemented in the form of, for example, a wrist watch, eyeglasses, earrings, necklaces, earphones, earring-type accessories, shoes, rings, clothes, helmets, and the like. However, it is not limited thereto, and the wearable device 100 may be implemented in a detachable form directly on the user's body. For example, the wearable device 100 may be implemented in the form of a patch, and may be attached to or detached from the user's body in an adhesive or non-adhesive manner. Also, the wearable device 100 may be implemented in a form inserted into the user's body. For example, the wearable device 100 is implemented in the form of electronic skin (epidermal electronics, or E-Skin) or electronic tattoo (E-Tattoo) to be inserted into the epidermis or inside the body through a medical procedure. can

Wearing the wearable device 100 means that the user carries the wearable device 100 in a form that comes into contact with the user's body in a preset manner. For example, the user wears a watch on his wrist, wears glasses, puts earrings on his ears, puts a necklace around his neck, puts earphones on his ears, puts earring-type accessories on his ears, wears shoes, etc. , the wearable device 100 may be worn in the form of wearing a ring on a finger, wearing clothes, or wearing a helmet.

When the user is driving, it means sitting in the driver's seat of the vehicle and manipulating the vehicle. For example, when a user sits in the driver's seat of a vehicle and turns the steering wheel, operates gears, operates the accelerator and brake pedals, or checks the instrument panel of the vehicle, the user is driving. situation can be recognized. The vehicle includes, for example, a car, a motorcycle, a bicycle, a bus, a subway, a subway, a train, an airplane, a helicopter, a ship, and the like.

A function provided by the wearable device 100 may be a function provided by an operating system (OS) or a function provided by an application. The functions include, for example, screen automatic turn-on, navigation, speeding notification, traffic situation information provision, drowsy driving prevention, augmented reality display, standby mode switching, notification, step counter, vehicle communication, communication with other electronic devices, etc. function may be included.

When recognizing that a user wearing the wearable device 100 is driving, the wearable device 100 may automatically execute a function set to be provided to the user while driving. For example, when recognizing that the user is driving, the wearable device 100 may automatically execute functions such as navigation, speeding notification, provision of traffic condition information, prevention of drowsy driving, display of augmented reality, and communication with a vehicle.

When recognizing that a user wearing the wearable device 100 is driving, the wearable device 100 may change settings of functions provided by the wearable device 100 . For example, when the user of the wearable device 100 is driving, the wearable device 100 blocks an automatic screen turn-on function, puts the wearable device 100 into a standby mode, blocks notifications, or steps on a pedometer. It can block counting or block or activate some of the communication with the vehicle.

2 is a diagram illustrating a structure of a wearable device 100a according to an exemplary embodiment.

The wearable device 100a according to this embodiment includes a sensor unit 210 and a controller 220.

The sensor unit 210 obtains state information of the wearable device 100a. The sensor unit 210 may include at least one sensor capable of acquiring state information of the wearable device 100a. The state information includes a sensing value output from a sensor provided in the sensor unit 210 .

The sensing value may vary according to the type of sensor provided in the sensor unit 210 . For example, the sensing value may include an acceleration value, location information, and an imaging signal.

The controller 220 controls overall operations of the wearable device 100a. The control unit 220 according to the present embodiment determines whether the user wearing the wearable device 100a is driving based on the state information output from the sensor unit 210, and if the user is driving, the wearable device 100a ), or at least one function of the wearable device 100a is executed.

3 is a diagram illustrating a structure of a sensor unit 210a according to an exemplary embodiment.

The sensor unit 210a according to the present embodiment includes a gyro sensor 302, a position detection module 304, a geomagnetic field sensor 306, a touch screen 308, a proximity/touch sensor 310, and an acceleration sensor 312. , a camera 314, a microphone 316, an infrared sensor 318, and a tilt sensor 320 may include at least one or a combination thereof. However, it is not limited thereto, and the sensor unit 210a may further include various sensors such as an air pressure sensor, an illuminance sensor, and a gravity sensor. The location detection module 304 may include, for example, a global positioning system (GPS) module, a Wi-Fi Protected Setup (WPS) module, a Bluetooth Low Energy (BLE) module, and the like.

The type of sensor provided in the sensor unit 210a may vary depending on the implementation form or embodiment of the wearable device 100a. For example, the wearable device 100a in the form of a wristwatch according to an embodiment includes a location detection module 304, a geomagnetic sensor 306, a touch screen 308, an acceleration sensor 312, a camera 314, and a microphone 316 . In addition, the wearable device 100a in the form of glasses according to an embodiment includes a gyro sensor 302, a position detection module 304, a proximity/touch sensor 310, an acceleration sensor 312, a camera 314, and a microphone 316. ), and a tilt sensor 320.

4 is a flowchart illustrating a method for controlling a wearable device according to an exemplary embodiment.

The wearable device 100 acquires state information of the wearable device 100 (S402). For example, the wearable device 100 uses a sensor provided in the wearable device 100 to obtain an acceleration value, a vibration value, an inclination value, location information, geomagnetic field information, proximity/touch information, an image pickup signal, sound, and infrared rays. State information such as a detection value may be obtained.

Next, the wearable device 100 determines whether the user wearing the wearable device 100 is driving by using the state information (S404). Whether the user is driving can be determined by determining whether status information appearing when the user is driving is detected using the status information. The wearable device 100 may store driving state information that appears when the user is driving. Also, the wearable device 100 may compare the stored driving state information with the acquired state information to determine whether the user is driving. The wearable device 100 may determine that the user is driving when a difference between the stored driving state information and the acquired state information is equal to or less than a reference value as a result of the comparison.

When the wearable device 100 determines that the user is driving (S404), the function settings of the wearable device 100 are changed (S406). In the case of driving, the function to be changed may be predetermined and designated. For example, when a user is driving, settings for automatically turning on a screen and a pedometer function are previously designated to be changed, and the wearable device 100 may retain information on functions to change settings. Changing the settings of the function may mean blocking the function or changing the execution form of the function. For example, when it is determined that the wearable device 100 is driving, it reads a text message aloud, makes a call through a speaker phone, changes the call to an automatic answering mode, or automatically responds to an incoming call with a text message or disable the screen auto-on function, which automatically turns on the screen when a preset motion is detected, disable step counter counting, turn off Wi-Fi and NFC (near field communication), or disable voice recognition. Function settings may be changed in the form of activating the function, changing the size and number of buttons on the user interface screen, or changing the size and number of buttons on the user interface screen of the peripheral device.

5 is a diagram for explaining a process of changing a function setting of the wearable device 100b according to an exemplary embodiment.

The wearable device 100a according to an embodiment may detect motion information and provide a pedometer function for counting the user's number of steps (S502). For example, the controller 220 may count the user's number of steps by using an acceleration measurement value generated by the acceleration sensor 312 of the sensor unit 210 . According to an embodiment, whenever the sensor unit 210a determines that the generated acceleration measurement values in the x, y, and z directions are greater than or equal to a predetermined threshold acceleration value in the x, y, and z directions, an interrupt signal is generated. may be generated and transmitted to the control unit 220. The controller 220 may increase the number of steps each time the interrupt signal is received from the sensor unit 210a.

When it is determined that the user is driving, the wearable device 100a according to this embodiment deactivates the pedometer function (S504). When the pedometer function is deactivated, if the wearable device 100a determines that the user is driving, it may not increase the step count value even if motion information satisfying the condition for increasing the step count value is detected.

According to this embodiment, the wearable device 100a does not increase the number of steps in a situation where the user is driving, thereby improving the accuracy of the pedometer function. The wearable device 100a according to this embodiment may be implemented in various forms such as a wrist watch, a bracelet, a band, glasses, clothes, shoes, a ring, and earrings.

6 is a diagram illustrating a structure of a wearable device 100b according to an exemplary embodiment.

The wearable device 100b according to this embodiment includes a sensor unit 210, a controller 220, and a display unit 610.

The sensor unit 210 obtains state information of the wearable device 100b. The sensor unit 210 may include at least one sensor capable of acquiring state information of the wearable device 100b.

The controller 220 controls overall operations of the wearable device 100b. The control unit 220 according to the present embodiment determines whether the user wearing the wearable device 100b is driving based on the state information output from the sensor unit 210, and if the user is driving, the wearable device 100b ), or at least one function of the wearable device 100b is executed.

The display unit 610 displays state information of the wearable device 100b, an application execution screen, and the like. The display unit 610 may include, for example, a liquid crystal display device or an organic light emitting display device. The display unit 610 may be provided in various positions and in various shapes according to the shape of the wearable device 100b. For example, when the wearable device 100b is implemented in the form of a wristwatch, the display unit 610 may be disposed on the watch face. When the wearable device 100b is implemented in the form of glasses, the display unit 610 may be disposed on the eyeglasses in the form of a transparent display. When the wearable device 100b is implemented in the form of a helmet, the display unit 610 may be disposed in the form of a transparent display on a transparent window portion disposed in front of the helmet.

7 is a diagram illustrating an operation of the wearable device 100b according to an exemplary embodiment.

According to an embodiment, the wearable device 100b is implemented in the form of a wrist watch, and can be used in a form worn on a user's wrist as shown in FIG. 7 . In the wearable device 100b in the form of a wrist watch according to the present embodiment, the user assumes a posture in which the hand is lowered as shown in S702, and then moves the display unit 610 of the wearable device 100b toward the user's face as in S704. When the wearable device 100b takes a posture of raising its arms, an automatic screen turning on function in which the display unit 610 of the wearable device 100b is changed from an off state (S702) to an on state (S704) may be provided.

8 is a diagram illustrating motion recognition of the wearable device 100b according to an exemplary embodiment.

The function of automatically turning on the screen as described in FIG. 7 may be provided by detecting motion of the wearable device 100b. As shown in FIG. 8 , the wearable device 100b according to the present embodiment detects a preset type of motion, and when such motion is detected, the display unit 610 may be automatically turned on. For example, as shown in FIG. 8 , the movement of the display unit 610 of the wearable device 100b in the vertical direction and then in the horizontal direction while making a circular motion is a preset form for performing the screen auto-turning function. can be the movement of In addition to the motions shown in FIG. 8 , motions for performing the automatic screen turning on function may be set in various forms.

The wearable device 100b may include a gyro sensor, an acceleration sensor, and the like in the sensor unit 210 to detect motion information.

9 is a diagram illustrating an operation of the wearable device 100b according to an exemplary embodiment.

The wearable device 100b in the form of a watch that provides the screen auto-turning function as described with reference to FIG. 7 may block the screen auto-turning function when recognizing that the user is driving, according to an embodiment. Blocking the screen auto-turning function means that the display unit 610 is not automatically turned on even when the wearable device 100b detects a previously set motion for the screen auto-turning function described above.

When the user wears the wearable device 100b in the form of a wristwatch and drives, when holding and turning the steering wheel with the hand on the side wearing the wearable device 100b, a preset type of movement for the screen auto-turning function occurs. can be detected. For example, as shown in FIG. 9 , when the user rotates the steering wheel in an upward direction while holding the left or right side of the steering wheel with the hand on the side wearing the wearable device 100b (S902) (S904), motion of a preset type for the automatic screen turning on function described above in FIGS. 7 and 8 may be detected. According to the present embodiment, even if the user rotates the steering wheel as shown in FIG. 9 and the wearable device 100b detects a preset motion for the screen auto-turning function, the display unit 610 is not automatically turned on, so that the user's intention and Otherwise, it is possible to prevent the display unit 610 from turning on and causing inconvenience to the user.

10 is a diagram for explaining an operation of the wearable device 100b according to an exemplary embodiment.

According to this embodiment, while the user is driving, the wearable device 100b may change the size, number, and arrangement of objects displayed on the display unit 610 (S1004). Here, the object includes, for example, an object for executing a function or an application, an object for selecting and reproducing content, and the like. Also, the object may be displayed in the form of, for example, an icon, a thumbnail image, a music playlist, or a video playlist.

According to this embodiment, when the user is driving, the wearable device 100b may increase the size of an object displayed on the display unit 610 compared to when the user is not driving. Also, when the user is driving, the wearable device 100b may reduce the number of objects displayed on the display unit 610 compared to when the user is not driving. Also, when the user is driving, the wearable device 100b may increase the distance between objects displayed on the display unit 610 compared to when the user is not driving. For example, as shown in FIG. 10 , three application execution icons are displayed on the display unit 610 when not driving (S1002), and two application execution icons are displayed on the display unit 610 when driving (S1002). As it is, the interval between the application execution icons may widen (S1004).

According to the present embodiment, when a user manipulates the wearable device 100b while driving, each object is made more visible, can be easily manipulated, the complexity of manipulation is reduced, and the possibility of errors occurring during manipulation is reduced. can reduce

11 is a diagram describing an operation of the wearable device 100b according to an exemplary embodiment.

When it is determined that the user is driving, the wearable device 100b according to this embodiment changes a method of providing a notification to the user. Here, the notification includes, for example, a text message notification, a phone call notification, and a notification generated by an application. The form of the notification includes at least one of turning on the screen and displaying notification content, sound, and vibration, or a combination thereof.

According to an embodiment, the wearable device 100b may not provide a notification when it is determined that the user is driving. In this case, even if a notification event such as a text message or phone call occurs, the wearable device 100b does not perform an operation for notification (eg, turning on the screen, displaying notification contents, sound, or vibration).

According to another embodiment, when it is determined that the user is driving, the wearable device 100b outputs notification content as a voice. For example, when it is determined that the user is driving and a text message is received, the wearable device 100b reads the content of the text message as a voice as shown in FIG. 11 . When the notification is generated from an application, the wearable device 100b may read the content of the notification generated from the application as a voice. To this end, the wearable device 100b may include a module that converts the contents of the notification into voice. Therefore, according to the present embodiment, when a notification event occurs while driving, the user can recognize the content of the notification without manipulating the wearable device 100b or checking the display unit 610 .

12 is a diagram for explaining an operation of the wearable device 100b according to an exemplary embodiment.

According to this embodiment, when it is determined that the user is driving and a call is received, the wearable device 100b uses a speakerphone function when receiving a call. The speakerphone function refers to a function that allows a user to make a phone call while the user's face is separated from the wearable device 100b, and the wearable device 100b uses a speaker provided in the wearable device 100b, Voice data may be output at a preset volume corresponding to the speakerphone function. In the speakerphone function, the set volume is higher than when receiving a call without using the function.

According to an embodiment, when it is determined that the user is driving and a call is received, the wearable device 100b may respond to the incoming call through voice recognition. To this end, the wearable device 100b may activate a microphone and voice recognition function for voice recognition when it is determined that the user is driving and a call is received.

13 is a diagram for explaining an operation of the wearable device 100b according to an exemplary embodiment.

According to this embodiment, when it is determined that the user is driving, the wearable device 100b activates a voice recognition function, recognizes the user's voice and executes a function or application of the wearable device 100b, or executes the function or application can be manipulated. For example, as shown in FIG. 13 , when the user says “navigation” while driving, the wearable device 100b may recognize the user's voice and execute the navigation function.

14 is a flowchart illustrating a control method of the wearable device 100b according to an exemplary embodiment.

According to an embodiment, when it is determined that the wearable device 100b is driving, it executes a preset function. First, the wearable device 100b acquires state information of the wearable device 100b (S1402), and determines whether a user wearing the wearable device 100b is driving (S1404). When the user wearing the wearable device 100b is driving, the wearable device 100b executes a preset function (S1406).

The preset function may be designated in advance by a manufacturer or designer of the wearable device 100b or by a user of the wearable device 100b according to embodiments.

According to an embodiment, when it is determined that the wearable device 100b is driving, it may immediately execute a preset function without user input.

According to another embodiment, if it is determined that the wearable device 100b is driving, it may provide a user interface for selecting whether or not to execute a preset function and execute the preset function according to a user input. The user interface capable of selecting whether or not to execute the preset function may select, for example, a form of querying by voice and receiving a user input through voice recognition, or whether to execute a function preset in the display unit 100b. It may be provided in a form of displaying a menu and receiving a user input through the displayed menu.

According to an embodiment, the wearable device 100b executes a preset function when it is determined that the user is driving, and then terminates the executed preset function when it is determined that the user is not driving. When the preset function is terminated, according to an embodiment, it may be automatically terminated, or a user interface may be provided for the user to select whether or not to terminate, and the function may be terminated based on a user input.

15 is a diagram for explaining an operation of executing a preset function in the wearable device 100b when a user is driving, according to an exemplary embodiment.

According to this embodiment, the wearable device 100b may execute a navigation function when the user is driving. In addition, the wearable device 100b may automatically end the navigation function when it is determined that the user is not driving after executing the navigation function when it is determined that the user is driving. In this case, the wearable device 100b receives navigation information (eg, road guidance information) from a navigation device (not shown) installed in the vehicle, and displays the received navigation information on the screen of the wearable device 100b. can However, it is not limited thereto, and the wearable device 100b may execute a navigation application installed in the wearable device 100b and use functions provided by the executed navigation application.

16 is a diagram for explaining an operation of executing a preset function when a user is driving in the wearable device 100b according to an exemplary embodiment.

According to this embodiment, the wearable device 100b may execute a function for preventing drowsy driving when the user is driving. For example, the wearable device 100b arranges the camera 1610 at a position where the user's eyes can be photographed, photographs the user's eyes, and determines whether the user is in a sleepy state. For example, the wearable device 100b detects the user's eye blink pattern when the user's eyes are closed at a standard rate or more compared to the usual state, and detects the user's eye blink pattern to detect the user's sleepy state when the rate of time the user closes their eyes increases. judge

To this end, the sensor unit 210 of the wearable device 100b may include a camera 314 . The camera 314 is disposed at a location capable of photographing the user's eyes. For example, when the wearable device 100b is implemented in the form of glasses, the camera 314 may be disposed on a glasses frame or eyeglass lens to face the user's eyes.

When it is determined that the user is sleepy, the wearable device 100b may perform a sleepiness prevention operation such as outputting a sound or generating a vibration.

17 is a diagram for explaining an operation of executing a preset function in the wearable device 100b when a user is driving, according to an exemplary embodiment.

The wearable device 100b according to the present embodiment is implemented in the form of glasses or a helmet, and displays vehicle information, navigation information, traffic information, etc. in augmented reality on the display unit 610 disposed in front of the user when the user is driving. It is provided in the form of AR, Augmented Reality). For example, as shown in FIG. 17, navigation information is displayed in the form of augmented reality. Augmented reality may be implemented by displaying a 3D image on the display unit 610 .

18 is a diagram illustrating a structure of a wearable device 100c according to an exemplary embodiment.

The wearable device 100c according to this embodiment includes a sensor unit 210, a controller 220, a display unit 610, and a communication unit 1810.

The sensor unit 210 obtains state information of the wearable device 100c. The sensor unit 210 may include at least one sensor capable of obtaining state information of the wearable device 100c.

The controller 220 controls overall operations of the wearable device 100c. The control unit 220 according to the present embodiment determines whether the user wearing the wearable device 100c is driving based on the state information output from the sensor unit 210, and if the user is driving, the wearable device 100c ), or at least one function of the wearable device 100c is executed.

The display unit 610 displays status information of the wearable device 100c, an application execution screen, and the like. The display unit 610 may include, for example, a liquid crystal display device or an organic light emitting display device. The display unit 610 may be provided in various positions and in various shapes according to the shape of the wearable device 100c.

The communication unit 1810 communicates with an external device. The communication unit 1810 may exchange data, control signals, status signals, and the like with an external device. Also, the communication unit 1810 may provide a plurality of communication methods, and the types of communication methods provided by the communication unit 1810 may vary according to embodiments.

19 is a diagram illustrating how the wearable device 100c communicates with external devices 1910a, 1910b, and 1910c according to an embodiment.

The external devices 1910a, 1910b, and 1910c may be at least one of a vehicle 1910b in which a user is riding, a smartphone 1910a, a tablet PC, and another wearable device 1910c, or a combination thereof. While communicating with various external devices 1910a, 1910b, and 1910c, the wearable device 100c controls the external devices 1910a, 1910b, and 1910c, provides information to the external devices 1910a, 1910b, and 1910c, or provides information to the external devices 1910a, 1910b, and 1910c. Devices 1910a, 1910b, and 1910c are available. Also, in this specification, the vehicle 1910b may refer to the entire vehicle or a computing device installed in the vehicle. The computing device may be, but is not limited to, a device installed in an automobile by an automobile manufacturer when manufacturing the automobile. The computing device may be a device manufactured by a manufacturer other than an automobile manufacturer, and may be installed in a vehicle by a user. In addition, the computing device may monitor the operation of the vehicle and electrically control the operation of the vehicle.

20 is a diagram showing the structure of a communication unit 1810a according to an embodiment.

The communication unit 230 according to this embodiment includes at least one of a Bluetooth module 2010, a Wi-Fi module 2020, a near field communication (NFC) module 2030, and a mobile communication module 2040, or these may include a combination of A Bluetooth module 2010, a Wi-Fi module 2020, a near filed communication (NFC) module 2030, and a mobile communication module 2040 may be selectively provided according to embodiments.

The mobile communication module 2040 may transmit/receive calls and text messages through a mobile communication network, and perform data communication using the mobile communication network. The mobile communication network includes, for example, code division multiple access (CDMA), global system for mobile communication (GSM), second-generation mobile communication such as PCD (personal digital cellular), IMT-2000 (International Mobile Telecommunication 2000), W-CDMA (Wideband Code Division Multiple Access), CDMA2000 (Code Division Multiple Access 2000) and 3rd generation mobile communications, LTE (Long Term Evolution) and LTE-A (Long Term Evolution advanced) 4th generation mobile communications A communication network using at least one of the methods is included.

21 is a flowchart illustrating a control method of the wearable device 100c according to an exemplary embodiment.

When the wearable device 100c according to this embodiment determines that the user wearing the wearable device 100c is driving (S2102), it transmits information indicating that the user is driving to the external device 1910a (S2104). The external device 1910a may be, for example, a smart phone 1910a or a tablet PC.

According to an embodiment, the wearable device 100c may transmit a control signal for changing an operation mode of the external device 1910a together with information indicating that it is driving to the external device 1910a. The wearable device 100c may control the external device 1910a to change the external device 1910a to a driving mode, a power saving mode, a notification blocking mode, and the like.

According to an embodiment, when receiving information indicating that the user is driving from the wearable device 100c, the external device 1910a changes the operation mode of the external device 1910a to a mode previously determined to be performed when the user is driving. (S2106). For example, upon receiving information indicating that the device is driving from the wearable device 100c, the external device 1910a may change the operation mode of the external device 1910a to a driving mode, a power saving mode, or a notification blocking mode.

According to an embodiment, when the operation mode is changed by the wearable device 100c, the external device 1910a may allow the wearable device 100c to perform part of the operation of the external device 1910a instead. For example, when the external device 1910a is notified by the wearable device 100c that it is driving and the operation mode is controlled to change, the external device 1910a does not provide a notification, but instead the wearable device 100c notifies. can operate to provide

According to another embodiment, when a control signal for changing an operation mode is received from the wearable device 100c, the external device 1910a changes the operation mode according to the received control signal.

22 is a diagram illustrating the wearable device 100c and the external device 1910b according to an embodiment.

According to this embodiment, when it is determined that the user wearing the wearable device 100c is driving, the wearable device 100c may turn off some of the communication modules included in the communication unit 1810b and turn on only some of the communication modules. have. For example, when the communication unit 1810b includes the Wi-Fi module 2020, the NFC module 2030, and the Bluetooth module 2010, and it is determined that the user of the wearable device 100c is driving, the wearable device ( 100c) may turn off the Wi-Fi module 2020 and the NFC module 2030 of the communication unit 1810b and turn on the Bluetooth module 2010. According to this embodiment, the vehicle 1910b includes a Bluetooth module 2210, and the Bluetooth module 2210 of the vehicle 1910b can communicate with the Bluetooth module 2010 of the wearable device 100c.

According to the present embodiment, when it is determined that the user of the wearable device 100c is driving, communication modules providing communication methods that are rarely used while driving are turned off, thereby reducing power consumption of the wearable device 100c. It works.

23 is a diagram illustrating the wearable device 100c and the external device 1910b according to an embodiment.

According to this embodiment, when it is determined that the user is driving, the wearable device 100c may use the output unit 2310 provided in the vehicle 1910b. For example, when it is determined that the user is driving, the wearable device 100c may use the speaker 2312 and the display unit 2314 provided in the output unit 2310 of the vehicle 1910b. The wearable device 100c may use the speaker 2312 provided in the vehicle 1910b to output music, sound notification, navigation guidance, and the like. In addition, the wearable device 100c may display a navigation screen, text message contents, notification contents, etc. through the display unit 2314 provided in the vehicle 1910b.

24 is a flowchart illustrating a control method of the wearable device 100c according to an exemplary embodiment.

When it is determined that the driver wearing the wearable device 100c is driving, the wearable device 100c according to the present embodiment may provide information collected from the vehicle to a smartphone, a tablet PC, or the like. First, when it is determined that the user is driving (S2402), the wearable device 100c requests state information and driving information from the vehicle 1910b (S2404). Here, the state information includes, for example, vehicle identification information, vehicle model, remaining fuel amount, driving distance, fuel economy, or speed. The driving information includes a driving distance, a destination, and the like.

According to an embodiment, the request for the status information and driving information transmitted from the wearable device 100c to the vehicle 1910b may include an information request signal and information about a device to provide the information. According to another embodiment, the request for the status information and driving information transmitted from the wearable device 100c to the vehicle 1910b includes a request signal for information, a type of requested information, and information about a device to provide the information. can include The information on the device to provide the information may include, for example, the device type, device identifier, communication establishment address, and the like.

Upon receiving the request for status information and driving information, the vehicle 1910b transmits the status information and driving information to at least one or a combination of the wearable device 100c, the smartphone 1910a, and the tablet PC (S2406) .

The wearable device 100c, smart phone 1910a, tablet PC, etc. that have received the status information and driving information manage the status information and driving information (S2408). For example, the smartphone 1910a may create a vehicle accounting book using the state information and driving information.

25 is a flowchart illustrating a method of determining whether a wearable device user is driving, according to an embodiment.

The wearable device 100a (see FIG. 2) according to the present embodiment detects vibration (S2502). According to an embodiment, the sensor unit 210 of the wearable device 100a may include an acceleration sensor and detect vibration using a sensing value detected by the acceleration sensor.

The wearable device 100a compares the detected vibration with a previously stored vibration pattern (S2504). The previously stored vibration pattern may indicate a vibration pattern of the vehicle generated by the engine of the vehicle and the road surface. When driving while wearing the wearable device 100a, vibration of the vehicle may be transmitted to the wearable device 100a through the user's body. When the user holds the steering wheel while driving, vibration of the vehicle may be transmitted to the wearable device 100a with high intensity through the steering wheel and body.

When the detected vibration is identical to or similar to the stored vibration pattern, the wearable device 100a determines that the user is driving (S2506). The fact that the vibration patterns are the same or similar means that the difference between the detected vibration and the previously stored vibration pattern is equal to or less than a preset reference value. According to an embodiment, when a correlation value between the detected vibration and the previously stored vibration pattern is greater than or equal to a reference value, the wearable device 100a may determine that the user is driving.

26 is a diagram for explaining a method of determining whether a user of the wearable device 100a is driving, according to an exemplary embodiment.

According to an embodiment, the wearable device 100a detects vibration, compares it with a stored vibration pattern, and determines whether the user of the wearable device 100a is driving according to the comparison result. For example, as shown in FIG. 26 , when a user grabs a steering wheel 2610 of a vehicle while wearing the wearable device 100a, vibration of the vehicle is transmitted through the steering wheel 2610 of the vehicle. , the wearable device 100a detects vehicle vibration.

Vibration transmitted through the steering wheel 2610 of the vehicle is stronger than vibration transmitted to vehicle occupants other than the driver. According to an embodiment, the wearable device 100a may determine whether the user is driving by considering not only the pattern of the detected vibration but also the strength of the vibration. For example, even if the detected vibration pattern is identical to or similar to a previously stored vibration pattern, the wearable device 100a does not determine that the user of the wearable device 100a is driving when the strength of the vibration is less than a reference value, and the detected vibration When the pattern is the same as or similar to the previously stored vibration pattern and the strength of the vibration is greater than or equal to the reference value, it may be determined that the user of the wearable device 100a is driving.

27 is a diagram illustrating a structure of a wearable device 100b according to an embodiment.

According to an embodiment, the wearable device 100b may be implemented in the form of a smart watch. In the wearable device 100b in the form of a smart watch, sensors of the sensor unit 210 may be disposed below the watch face, on the inner circumferential surface of the watch strap 2710, and on the fastening portion 2726. For example, a heart rate sensor, a temperature sensor, a sweat sensor, a blood pressure sensor, a proximity sensor, and the like may be disposed below the watch face 2722 . In addition, a proximity/contact sensor or the like may be disposed on the inner circumferential surface 2724 of the watch strap. In addition, a conduction sensor, a hall sensor, a magnetic sensor, etc. may be disposed on the fastening unit 2726 to detect whether or not it is fastened. In addition, a touch screen may be disposed on the watch face 2730. In addition, an acceleration sensor, a gyro sensor, an illuminance sensor, a geomagnetic sensor, and the like may be disposed at various positions.

The wearable device 100b in the form of a smart watch may have a structure in which the watch strap 2710 is detachable from the watch face 2730 . In this case, a sensor (eg, a conductivity sensor, a proximity sensor, a hall sensors, magnetic sensors, etc.) may be disposed.

The controller 220 of the smart watch may detect vibration using an acceleration sensor. Also, the controller 220 of the smart watch may detect the user's movement using a gyro sensor.

In addition, the controller 220 of the smart watch may determine whether the smart watch is worn or not worn based on whether the fastening unit 2726 is in a fastened state and a detection value of a biosensor such as a heartbeat sensor.

28 is a diagram illustrating a structure of a wearable device 100a according to an exemplary embodiment.

According to this embodiment, the wearable device 100a may be implemented in the form of a smart bracelet (or smart band). In the wearable device 100a in the form of a smart bracelet, sensors may be disposed at positions such as the body 2810, the fastening part 2820, and the inner circumferential surface 2830. For example, an acceleration sensor, a gyro sensor, a motion sensor, a geomagnetic sensor, a position detection module, etc. are disposed on the body 2810, or a conductivity sensor, a hall sensor, or a magnetic A sensor or the like may be disposed, or a temperature sensor, a heart rate sensor, or the like may be disposed on the inner circumferential surface 2830 .

29 is a diagram illustrating a structure of a wearable device 100b according to an embodiment.

According to this embodiment, the wearable device 100b may be implemented in the form of a smart ring. In the wearable device 100b in the form of a smart ring, sensors may be disposed on the display unit 2910, the body 2920, the inner circumferential surface 2930, and the outer circumferential surface 2940. For example, a touch screen is disposed on the display unit 2910, a temperature sensor, a heart rate sensor, etc. are disposed on the inner circumferential surface 2930, or an acceleration sensor, a gyro sensor, a geomagnetic sensor, a position detection module, and movement are disposed on the body 2920. A sensor, an illuminance sensor, and the like may be disposed. In addition, a touch sensor or the like may be disposed on the outer circumferential surface 2940 .

30 is a diagram illustrating a structure of a wearable device 100a according to an exemplary embodiment.

According to this embodiment, the wearable device 100a may be implemented in the form of an earphone. In the earphone type wearable device 100a, sensors may be disposed on the outer circumferential portion 3010 and the sound board 3020. For example, a heart rate sensor may be disposed on the outer circumferential portion 3010 and a temperature sensor may be disposed on the sound board 3020 . In addition, an acceleration sensor, a gyro sensor, a geomagnetic sensor, or the like may be disposed on the outer circumferential portion 3010 or the body 3030 .

31 is a diagram illustrating a structure of a wearable device 100a according to an exemplary embodiment.

According to this embodiment, the wearable device 100a may be implemented in the form of clothes. In the wearable device 100a in the form of clothes, a temperature sensor, a heart rate sensor, and the like may be disposed on the inner skin, and an acceleration sensor, a gyro sensor, a position detection module, and a geomagnetic sensor may be disposed at various locations.

32 is a flowchart illustrating a method of determining whether a user of a wearable device is driving, according to an embodiment.

According to this embodiment, the wearable device 100a determines whether the user is driving based on the detected motion.

First, the wearable device 100a detects motion (S3202). Movement may be detected in the form of, for example, a movement pattern or a rotation angle. Movement may be detected using an acceleration sensor, a gyro sensor, a motion sensor, etc. provided in the sensor unit 210 of the wearable device 100a.

Next, the wearable device 100a compares the detected movement with the stored movement pattern (S3204). The wearable device 100a may compare the detected movement and the stored movement pattern by calculating a difference between the detected movement and the stored movement pattern or performing a correlation operation.

When the detected movement and the stored movement pattern are the same or similar, the wearable device 100a determines that the user is driving (S3206).

33 is a diagram for explaining a method of determining whether a user is driving according to an embodiment.

According to an embodiment, the wearable device 100b may detect a motion of rotating the steering wheel and determine that the user is driving. As shown in FIG. 33 , when a user is driving, a motion of rotating a steering wheel frequently occurs. The movement of rotating the steering wheel appears as a movement of the wearable device 100b along the circular shape of the steering wheel. The wearable device 100b detects a type of motion using an acceleration sensor, a gyro sensor, a motion sensor, and the like, and determines that the user is driving when the type of the detected motion is similar to a pre-stored motion of rotating a steering wheel. have. According to an embodiment, the wearable device 100b detects a rotation angle using an acceleration sensor, and when the rotation angle is the same as or similar to a pre-stored rotation angle, it may be determined that the user is driving.

Also, according to an embodiment, the wearable device 100b may determine that the user is driving when a motion of the same or similar type as the previously stored rotation angle is detected for a reference time or more or a reference number of times or more.

According to an embodiment, the wearable device 100b may determine whether the user is driving in consideration of the detected vibration and motion. For example, the wearable device 100b may determine that the user is driving when the detected vibration is similar to a previously stored vibration pattern and the detected motion is similar to a previously stored motion pattern.

34 is a diagram for explaining a method of determining whether a user is driving according to an embodiment.

According to an embodiment, the wearable device 100a is implemented in the form of a shoe, and detects a movement of stepping on or pressing a vehicle pedal 3410 (eg, a brake pedal, an accelerator pedal, or a clutch pedal) to indicate that the user is driving. can judge The user repeats an action of pressing or pressing the car pedal 3410 while driving, and as a result, as shown in FIG. Rotational motion occurs. In addition, when the user is driving, the above-described up and down rotational motion occurs within a limited angular range. For example, while the user is driving, a vertical rotational motion of the wearable device 100a may be detected within a range of 270 degrees to 360 degrees. Therefore, according to an embodiment, the wearable device 100a in the form of a shoe may determine that the user is driving when the upward and downward rotation motion is detected. Information on the vertical rotation motion may be previously stored in the wearable device 100a.

Also, according to an embodiment, the wearable device 100a in the form of a shoe may determine that the user is driving when the above-mentioned up and down rotation motion is detected for a reference time or more or a reference number of times or more.

According to this embodiment, the sensor unit 210 of the wearable device 100a may include an acceleration sensor or a gyro sensor, and may detect the vertical rotation motion using the acceleration sensor or the gyro sensor.

35 is a diagram for explaining a method of determining whether a user is driving according to an embodiment.

According to an embodiment, the wearable device 100a is implemented in the form of a shoe and detects movement between a plurality of vehicle pedals 3410a and 3410b (eg, a brake pedal, an accelerator pedal, or a clutch pedal), It may be determined that the user is driving. The user moves between the plurality of car pedals 3410a and 3410b while driving, and as a result, as shown in FIG. There is a movement that rotates left and right around the center. In addition, when the user is driving, the above left and right rotation motion occurs within a limited angular range. For example, when the user is driving, left and right rotational motion of the wearable device 100a may be detected within a range of 90 degrees. Therefore, according to an embodiment, the wearable device 100a in the form of a shoe may determine that the user is driving when the left and right rotation motion is detected. Information on the left and right rotation motion may be previously stored in the wearable device 100a.

Also, according to an embodiment, the wearable device 100a in the form of a shoe may determine that the user is driving when the above-mentioned left and right rotation motion is detected for a reference period or more than a reference number of times.

According to this embodiment, the sensor unit 210 of the wearable device 100a may include an acceleration sensor or a gyro sensor, and may detect the left and right rotation motion using the acceleration sensor or the gyro sensor.

36 is a flowchart illustrating a method of determining whether a user is driving according to an embodiment.

According to this embodiment, the sensor unit 210 of the wearable device 100a includes a camera, and when a scene previously stored in the wearable device 100a is detected, it may be determined that the user is driving.

First, the wearable device 100a takes a picture using a camera (S3602). The captured scene may vary depending on the position where the camera is placed in the wearable device 100a and the user's situation. For example, when the wearable device 100a is implemented in the form of glasses and a camera is disposed in front of the glasses, the wearable device 100a may capture a scene in the direction of the user's gaze. As another example, when the wearable device 100a is implemented in the form of a wrist watch or a bracelet and a camera is disposed on a watch band, the wearable device 100a may capture a left or right direction of the user.

The wearable device 100a determines whether a pre-stored scene is detected from the photographed image (S3604). The pre-stored scene may be a scene highly likely to be detected while driving. For example, the pre-stored scenes may be scenes such as a steering wheel, an automobile instrument panel, and a side mirror.

Comparison between a pre-stored scene and a photographed image may be performed using various algorithms for scene detection. For example, the pre-stored image represents the shape of the circular shape and the scale shape of the instrument panel of a vehicle, and the wearable device 100a may detect the circular shape and the shape of the scale shape of the instrument panel from the photographed image. For shape comparison, a correlation technique may be used, for example.

When the stored scene is detected, the wearable device 100a determines that the user is driving (S3606).

37 is a diagram for explaining a method of determining whether a user is driving according to an embodiment.

According to this embodiment, the wearable device 100a may be implemented in the form of glasses (or smart glasses). In the wearable device 100a in the form of eyeglasses, sensors may be disposed on the eyeglass frame 3710, the temples 3720, the part 3730 in contact with the temples of the temples, the nose support 3740, the glasses 3750, and the like. For example, a touch sensor is placed on the frame 3710, a touch sensor is placed on the temples 3720, a pulse sensor is placed on the part 3730 that contacts the temple, or an acceleration sensor is placed on the nose pad 3740. Various sensors may be disposed at various positions, such as a , touch sensor, or the like, or an iris sensor disposed on the eyeglasses 3750 . Also, according to an embodiment, a camera 3760 may be disposed at a predetermined position of the temple 3720 or the frame 3710 .

According to an embodiment, the wearable device 100a in the form of smart glasses photographs the front using the camera 3760 and analyzes the photographed image to determine whether the user is driving. For example, as shown in FIG. 37 , images of the shape of a dashboard and a side mirror of a vehicle are stored in advance in the wearable device 100a, and the wearable device 100a converts the previously stored images from the captured images. When detected, it may be determined that the user is driving.

According to an embodiment, the shape of the instrument panel of a vehicle may be stored for each type of vehicle. For example, shapes of a dashboard of model vehicle A of company A and a dashboard of model vehicle B of company B may be respectively stored in the wearable device 100a. Also, the wearable device 100a may determine the model of the vehicle based on the shape of the instrument panel.

Similarly, the shape of the side mirror may be stored for each type of vehicle. Also, the wearable device 100a may determine the vehicle model based on the shape of the side mirror.

38 is a diagram for explaining a method of determining whether a user is driving according to an embodiment.

According to this embodiment, the wearable device 100a may be implemented in the form of a helmet. In the helmet-shaped wearable device 100a, sensors may be disposed on a helmet shell 3810, a liner, a shield 3830, and the like. For example, a touch sensor is disposed on the helmet shell 3810 or the shield 3830, a pulse sensor is disposed on the liner, an acceleration sensor, a gyro sensor, etc. are disposed on the helmet shell 3810, the shield 3830, or the liner. Alternatively, various sensors may be disposed in various positions, such as an iris sensor disposed on the shield 3830. Also, according to an embodiment, a camera 3820 may be disposed at a predetermined position of the helmet shell 3810 or the shield 3830.

According to an embodiment, the wearable device 100a in the form of a helmet photographs the front using a camera 3820 and analyzes the photographed image to determine whether the user is driving. For example, as shown in FIG. 38 , if images of the shape of a motorcycle instrument panel and side mirrors are stored in advance in the wearable device 100a, and the wearable device 100a detects the previously stored images from the captured images, It may be determined that the user is driving.

According to an embodiment, the shape of the instrument panel of a motorcycle may be stored for each type of motorcycle. For example, shapes of a dashboard of model vehicle A of company A and a dashboard of model vehicle B of company B may be respectively stored in the wearable device 100a. Also, the wearable device 100a may determine the type of motorcycle based on the shape of the instrument panel.

Similarly, the shape of the side mirror may be stored for each type of motorcycle. Also, the wearable device 100a may determine the vehicle model based on the shape of the side mirror.

39 is a flowchart illustrating a method of determining whether a user is driving according to an embodiment.

According to an embodiment, the wearable device 100c may determine that the user is driving when entering the vehicle 1910b registered to the wearable device.

First, when the wearable device 100c enters the vehicle 1910b, it establishes communication with the vehicle 1910b (S3902). For example, the wearable device 100c may establish a wireless communication channel with the vehicle 1910b.

Next, the wearable device 100c receives vehicle information from the vehicle 1910b (S3904). The vehicle information may include, for example, a vehicle type, vehicle identification number, vehicle state information, vehicle driving information, and the like. The unique number of the vehicle may include, for example, a vehicle license plate number, an identification number of the vehicle itself, and the like. Also, in this specification, the vehicle 1910b may be a computing device installed in a vehicle, and in this case, the vehicle information may be device information about the computing device installed in the vehicle. The device information may include, for example, information about an identification value of the device, specifications of the device, network conditions of the device, and applications running in the device. However, it is not limited thereto. According to an embodiment, the vehicle information may be automatically transmitted from the vehicle 1910b to the wearable device 100c when communication between the wearable device 100c and the vehicle 1910b is established. According to another embodiment, the license plate number may be transmitted from the vehicle 1910b to the wearable device 100c when there is a request from the wearable device 100c to the vehicle 1910b.

When the vehicle 1910b is a registered vehicle (S3906), the wearable device 100c may determine that the user is driving (S3908). When vehicle information is received, the wearable device 100c may compare pre-stored vehicle information with the received vehicle information to determine whether it is a registered vehicle. The vehicle information used to determine whether the vehicle is a registered vehicle may include, for example, a license plate number and an identification number of the vehicle itself. Also, when communication between the wearable device 100c and the vehicle 1910b is established, the wearable device 100c transmits vehicle information (eg, device information of a computing device installed in the vehicle) of the vehicle 1910b to the vehicle 1910b. ), and based on the received vehicle information, it may be determined whether the vehicle 1910b is a pre-registered vehicle.

In addition, the wearable device 100c may establish communication with the vehicle 1910b using vehicle information (eg, device information of a computing device installed in the vehicle) of the vehicle 1910b. For example, the wearable device 100c may search for the vehicle 1910b by receiving vehicle information broadcast from the vehicle 1910b in order to establish Bluetooth communication with the vehicle 1910b, and use the received vehicle information It can be used to access the vehicle 1910b.

40 is a flowchart illustrating a method for controlling a wearable device according to an embodiment.

According to this embodiment, the wearable device 100a determines whether the user is riding a vehicle when determining whether the user is driving, and determines whether the user is driving when it is determined that the user is riding a vehicle.

First, the wearable device 100a acquires state information of the wearable device 100a (S4002). As described above, the wearable device 100a may obtain state information of the wearable device 100a using various sensors provided in the wearable device 100a.

Next, the wearable device 100a determines whether the user of the wearable device 100a is riding in a vehicle by using the state information (S4004). For example, the wearable device 100a may determine that the user is riding in a vehicle when vibration of a pre-stored pattern is detected, or when communication with the vehicle is established.

When it is determined that the user is riding in a vehicle, the wearable device 100a determines whether the user is driving (S4006). For example, the wearable device 100a may determine that the user is driving when a rotational motion of a steering wheel is detected, when a rotational motion of pressing or pressing a car pedal is detected, or when a registered vehicle is detected. have.

When it is determined that the user is driving, the wearable device 100a may change function settings of the wearable device 100a or execute a preset function (S4008).

According to an embodiment, when it is determined that the user is riding in a vehicle, the wearable device 100a may change a function setting or execute a function (S4010). For example, when it is determined that the user is riding in a vehicle, the wearable device 100a may execute a user interface capable of controlling sound output functions such as a radio and an optical disc player of the vehicle, a user interface capable of controlling navigation, and the like. have. In addition, when it is determined that the user is riding in a vehicle, the wearable device 100a may change communication settings such as turning off Wi-Fi and turning on Bluetooth.

41 is a flowchart illustrating a method of determining whether a user of the wearable device 100a is riding in a vehicle according to an exemplary embodiment.

According to this embodiment, the wearable device 100a determines whether the user is riding in a vehicle based on the speed of the vehicle. First, the wearable device 100a measures speed (S4102). The speed of the wearable device 100a may be obtained by calculating a movement distance per hour based on a location detected by a location detection module (eg, a GPS module) included in the wearable device 100a. As another example, the speed of the wearable device 100a may be calculated based on the acceleration detected by the acceleration sensor.

Next, when the measured speed is equal to or greater than the reference speed (S4104), the wearable device 100a determines that the user is riding in a vehicle (S4106). For example, when the speed measured by the wearable device 100a is 30 km/hour or more, the wearable device 100a may determine that the user is riding in a vehicle.

42 is a flowchart illustrating a method of determining whether a user of the wearable device 100a is riding in a vehicle according to an exemplary embodiment.

According to this embodiment, the wearable device 100a determines whether a user is riding in a vehicle based on vehicle acceleration. First, the wearable device 100a measures acceleration (S4202). The acceleration of the wearable device 100a may be calculated based on the acceleration detected by an acceleration sensor provided in the wearable device 100a.

Next, when the measured acceleration pattern is a previously stored acceleration pattern (S4204), the wearable device 100a determines that the user is riding in a vehicle (S4206). The pre-stored acceleration pattern may include, for example, an acceleration change pattern corresponding to at least one of vehicle acceleration/deceleration, lane change, left turn, right turn, and U-turn, or a combination thereof. When the previously stored acceleration pattern is repeatedly detected, the wearable device 100a may determine that the wearable device 100a is riding in a vehicle. For example, the wearable device 100a may determine that the user is riding in a vehicle when the pre-stored acceleration pattern is detected more than a reference number of times within a reference time.

43 is a flowchart illustrating a method of determining whether a user of the wearable device 100a is riding in a vehicle according to an exemplary embodiment.

According to this embodiment, the wearable device 100a determines whether the user is riding in a vehicle based on the detected sound. First, the wearable device 100a detects sound (S4302). The sound of the wearable device 100a may be detected using a microphone provided in the wearable device 100a.

Next, the wearable device 100a determines whether the detected sound is similar to a previously stored sound pattern (S4304). The pre-stored sound pattern may include, for example, a car engine sound, a motorcycle engine sound, a bus engine sound, a subway sound, an airplane sound, and the like. Comparison between the detected sound and the previously stored sound pattern may be performed using a correlation technique or the like.

When the detected sound is similar to the previously stored sound pattern, the wearable device 100a determines that the user is riding in a vehicle (S4306).

44 is a flowchart illustrating a control method of the wearable device 100a according to an embodiment.

According to this embodiment, the wearable device 100a determines whether the user has boarded public transportation.

First, the wearable device 100a acquires state information of the wearable device 100a (S4402).

The wearable device 100a determines whether the user is riding in a vehicle based on the state information (S4404). As described above, whether or not the user is riding in a vehicle can be known by establishing communication with the vehicle or by detecting speed, acceleration, sound, and the like.

When the user is riding a vehicle, the wearable device 100a determines whether the user is riding public transportation (S4406). Whether or not the user has boarded public transportation may be determined using a geomagnetic field value, sound, vibration, and the like.

When the user is not riding public transportation, the wearable device 100a determines whether the user is driving (S4408). As described above, whether the user is driving may be determined using vibration, movement, and a captured image. When the user is riding public transportation, the wearable device 100a determines that the user is not driving. According to this embodiment, the wearable device 100a has an effect of reducing the possibility of erroneously determining that the user is driving when the user is riding public transportation.

When the user is driving, the wearable device 100a changes function settings of the wearable device 100a or executes a preset function (S4410).

According to an embodiment, when it is determined that the user is riding public transportation (S4406), the wearable device 100a may change a preset function or execute a function when riding public transportation. For example, when riding public transportation, a notification method may be changed to vibration or a subway or bus route guidance application may be executed.

According to another embodiment, the wearable device 100a may determine the type of public transportation based on state information of the wearable device, and change function settings or execute functions according to the type of public transportation. For example, the wearable device 100a may determine which public transportation among subway, bus, train, and airplane the user has boarded based on the vibration pattern, and change function settings or execute the function according to the type of public transportation. have. For example, the wearable device 100a may execute a subway route guidance application when it is determined that the user has boarded the subway, and may execute a bus route guidance application when it is determined that the user has boarded the bus. Also, when it is determined that the user has boarded an airplane, the wearable device 100a may change the wearable device 100a to an airplane mode or turn off the communication module.

45 is a flowchart illustrating a method of determining whether a user has boarded public transportation according to an embodiment.

According to this embodiment, the wearable device 100a may determine whether the user has boarded public transportation by measuring a geomagnetic field. First, the wearable device 100a measures the earth's magnetic field. The wearable device 100a according to the present embodiment may include a geomagnetic sensor and measure a geomagnetic field using the geomagnetic sensor (S4502).

Next, the wearable device 100a compares the measured earth magnetic field with a pre-stored earth magnetic field pattern (S4504), and when the pre-stored earth magnetic field pattern is detected, it may be determined that the user has boarded public transportation (S4506). . For example, the wearable device 100a may pre-store the earth magnetic field pattern of the subway or train, and determine that the user has boarded the subway or train when the earth magnetic field pattern of the subway or train is detected.

46 is a flowchart illustrating a method of determining whether a user has boarded public transportation according to an embodiment.

According to this embodiment, the wearable device 100a may measure sound to determine whether the user has boarded public transportation. First, the wearable device 100a measures sound. The wearable device 100a according to the present embodiment may include a microphone and measure sound using the microphone (S4602).

Next, the wearable device 100a compares the measured sound with a pre-stored sound pattern (S4604), and when the pre-stored sound pattern is detected, it may be determined that the user has boarded public transportation (S4606). For example, the wearable device 100a may pre-store a sound pattern of a subway, subway, bus, train, airplane, ship, etc., and determine that the user has boarded public transportation when the pre-stored sound pattern is detected. . The sound pattern may include an engine vibration sound, a public transportation announcement, and the like. Also, the wearable device 100a may determine the type of public transportation according to the detected sound pattern.

47 is a flowchart illustrating a method of determining whether a user has boarded public transportation according to an embodiment.

According to this embodiment, the wearable device 100a may determine whether the user has boarded public transportation by measuring vibration. First, the wearable device 100a measures vibration. The wearable device 100a according to the present embodiment may include an acceleration sensor and measure vibration using the acceleration sensor (S4702).

Next, the wearable device 100a compares the measured vibration with a previously stored vibration pattern (S4704), and when the previously stored vibration pattern is detected, it may be determined that the user has boarded public transportation (S4706). For example, the wearable device 100a may pre-store a vibration pattern of a subway, subway, bus, train, airplane, ship, or the like, and determine that the user has boarded public transportation when the previously stored vibration pattern is detected. . Also, the wearable device 100a may determine the type of public transportation according to the detected vibration pattern.

48 is a block diagram illustrating a configuration of a wearable device 100d according to an exemplary embodiment.

As shown in FIG. 48, the wearable device 100d may include, for example, a mobile phone, a tablet PC, a PDA, an MP3 player, a kiosk, an electronic photo frame, a navigation device, a digital TV, a wrist watch, or an HMD. It can be applied to various types of devices such as wearable devices such as (Head-Mounted Display).

48, the wearable device 100d includes a display unit 4810, a controller 4870, a memory 4820, a GPS chip 4825, a communication unit 4830, a video processor 4835, an audio processor 4840, At least one of a user input unit 4845, a microphone unit 4850, an imaging unit 4855, a speaker unit 4860, and a motion detection unit 4865 may be included.

The display unit 4810 may include a display panel 4811 and a controller (not shown) that controls the display panel 4811 . The display panel 4811 is implemented in various forms such as LCD (Liquid Crystal Display), OLED (Organic Light Emitting Diodes) display, AM-OLED (Active-Matrix Organic Light-Emitting Diode), PDP (Plasma Display Panel), etc. It can be. The display panel 4811 may be implemented to be flexible, transparent, or wearable. The display unit 4810 may be combined with the touch panel 4847 of the user input unit 4845 to provide a touch screen (not shown). For example, a touch screen (not shown) may include an integral module in which a display panel 4811 and a touch panel 4847 are coupled in a laminated structure.

The memory 4820 may include at least one of an internal memory (not shown) and an external memory (not shown).

The built-in memory includes, for example, volatile memory (eg, DRAM (Dynamic RAM), SRAM (Static RAM), SDRAM (Synchronous Dynamic RAM), etc.), non-volatile memory (eg, OTPROM (One Time Programmable ROM) ), PROM (Programmable ROM), EPROM (Erasable and Programmable ROM), EEPROM (Electrically Erasable and Programmable ROM), Mask ROM, Flash ROM, etc.), hard disk drive (HDD), or solid state drive (SSD). can include According to an embodiment, the controller 4870 may load and process a command or data received from at least one of a non-volatile memory or other components into a volatile memory. Also, the controller 4870 may store data received or generated from other components in a non-volatile memory.

The external memory may include, for example, at least one of CF (Compact Flash), SD (Secure Digital), Micro-SD (Micro Secure Digital), Mini-SD (Mini Secure Digital), xD (extreme Digital), and Memory Stick. can include

The memory 4820 may store various programs and data used for the operation of the wearable device 100d. For example, at least a part of content to be displayed on the lock screen may be temporarily or semi-permanently stored in the memory 4820 .

The controller 4870 may control the display 4810 to display a portion of content stored in the memory 4820 on the display 4810 . In other words, the controller 4870 may display some of the content stored in the memory 4820 on the display 4810 . Alternatively, when a user gesture is made in one area of the display unit 4810, the controller 4870 may perform a control operation corresponding to the user's gesture.

The controller 4870 may include at least one of a RAM 4871 , a ROM 4872 , a CPU 4873 , a graphic processing unit (GPU) 4874 , and a bus 4875 . RAM 4871, ROM 4872, CPU 4873 and GPU 4874 may be connected to each other through a bus 4875.

The CPU 4873 accesses the memory 4820 and performs booting using the O/S stored in the memory 4820. In addition, various operations are performed using various programs, contents, data, etc. stored in the memory 4820 .

The ROM 4872 stores command sets for system booting and the like. For example, when the turn-on command is input to the wearable device 100d and power is supplied, the CPU 4873 copies the OS stored in the memory 4820 to the RAM 4871 according to the command stored in the ROM 4872, and the OS You can boot the system by running When booting is completed, the CPU 4873 copies various programs stored in the memory 4820 to the RAM 4871 and executes the programs copied to the RAM 4871 to perform various operations. When the booting of the wearable device 100d is completed, the GPU 4874 displays the UI screen on the area of the display unit 4810. Specifically, the GPU 4874 may create a screen displaying an electronic document including various objects such as content, icons, and menus. The GPU 4874 calculates attribute values such as coordinate values, shape, size, color, etc. of each object to be displayed according to the layout of the screen. Also, the GPU 4874 may create screens of various layouts including objects based on the calculated attribute values. A screen generated by the GPU 4874 may be provided to the display unit 4810 and displayed in each area of the display unit 4810, respectively.

The GPS chip 4825 may calculate the current location of the wearable device 100d by receiving a GPS signal from a Global Positioning System (GPS) satellite. The controller 4870 may calculate the user's location using the GPS chip 4825 when using a navigation program or when the user's current location is needed.

The communication unit 4830 may perform communication with various types of external devices according to various types of communication methods. The communication unit 4830 may include at least one of a Wi-Fi chip 4831, a Bluetooth chip 4832, a wireless communication chip 4833, and an NFC chip 4834. The controller 4870 may communicate with various external devices using the communication unit 4830 .

The Wi-Fi chip 4831 and the Bluetooth chip 4832 may perform communication using the Wi-Fi method and the Bluetooth method, respectively. In the case of using the Wi-Fi chip 4831 or the Bluetooth chip 4832, various connection information such as an SSID and a session key is first transmitted and received, and various information can be transmitted and received after a communication connection is established using this. The wireless communication chip 4833 refers to a chip that performs communication according to various communication standards such as IEEE, ZigBee, 3rd Generation (3G), 3rd Generation Partnership Project (3GPP), and Long Term Evolution (LTE). The NFC chip 4834 refers to a chip that operates in a Near Field Communication (NFC) method using a 13.56 MHz band among various RF-ID frequency bands such as 135 kHz, 13.56 MHz, 433 MHz, 860 to 960 MHz, and 2.45 GHz.

The video processor 4835 may process video data included in content received through the communication unit 4830 or content stored in the memory 4820 . The video processor 4835 may perform various image processing such as decoding, scaling, noise filtering, frame rate conversion, and resolution conversion on video data.

The audio processor 4840 may process audio data included in content received through the communication unit 4830 or content stored in the memory 4820 . The audio processor 4840 may perform various processes such as decoding or amplifying audio data and filtering noise.

When a playback program for multimedia content is executed, the controller 4870 drives the video processor 4835 and the audio processor 4840 to reproduce the corresponding content. The speaker unit 4860 may output audio data generated by the audio processor 4840.

The user input unit 4845 may receive various commands from the user. The user input unit 4845 may include at least one of a key 4846, a touch panel 4847, and a pen recognition panel 4848.

The key 4846 may include various types of keys such as mechanical buttons and wheels formed in various regions such as the front, side, or rear surfaces of the main body of the wearable device 100d.

The touch panel 4847 can sense a user's touch input and output a touch event value corresponding to the sensed touch signal. When the touch panel 4847 is combined with the display panel 4811 to form a touch screen (not shown), the touch screen may be implemented with various types of touch sensors such as capacitive, resistive, or piezoelectric. The capacitive type is a method of calculating touch coordinates by detecting microelectricity caused by a user's body when a part of the user's body touches the touch screen surface by using a dielectric coated on the surface of the touch screen. The pressure-sensitive type includes two electrode plates embedded in the touch screen, and calculates touch coordinates by sensing that when a user touches the screen, the top and bottom plates of the touched point are in contact and current flows. A touch event occurring in a touch screen may be mainly generated by a human finger, but may also be generated by an object made of a conductive material capable of applying capacitance change.

The pen recognition panel 4848 detects a proximity input or touch input of a pen according to operation of a user's touch pen (eg, a stylus pen or a digitizer pen), and detects the detected pen proximity event or pen Touch events can be output. The pen recognition panel 4848 may be implemented, for example, using an EMR method, and may detect a touch or proximity input according to a pen proximity or a change in strength of an electromagnetic field caused by a touch. In detail, the pen recognition panel 4848 includes an electromagnetic induction coil sensor (not shown) having a grid structure and an electronic signal processing unit (not shown) that sequentially provides an AC signal having a predetermined frequency to each loop coil of the electromagnetic induction coil sensor. ). If a pen with a resonant circuit is present near the loop coil of the pen recognition panel 4848, a magnetic field transmitted from the loop coil generates a current based on mutual electromagnetic induction in the resonant circuit in the pen. Based on this current, an induced magnetic field is generated from the coil constituting the resonant circuit in the pen, and the pen recognition panel 4848 detects this induced magnetic field from the loop coil in the signal receiving state, thereby determining the approaching position of the pen or A touch location can be detected. The pen recognition panel 4848 may be provided with a predetermined area under the display panel 4811 , for example, an area covering the display area of the display panel 4811 .

The microphone unit 4850 may receive a user's voice or other sounds and convert them into audio data. The controller 4870 may use the user's voice input through the microphone unit 4850 in a call operation or convert it into audio data and store it in the memory 4820 .

The imaging unit 4855 may capture a still image or a moving image according to a user's control. The imaging unit 4855 may be embodied in plural, such as a front camera and a rear camera.

When the imaging unit 4855 and the microphone unit 4850 are provided, the controller 4870 performs a control operation according to a user's voice input through the microphone unit 4850 or a user's motion recognized by the imaging unit 4855. may be For example, the wearable device 100d may operate in a motion control mode or a voice control mode. When operating in the motion control mode, the controller 4870 may activate the imaging unit 4855 to capture an image of the user, track a change in motion of the user, and perform a corresponding control operation. When operating in the voice control mode, the controller 4870 may operate in a voice recognition mode in which a user voice input through the microphone unit 4850 is analyzed and a control operation is performed according to the analyzed user voice.

The motion detection unit 4865 may detect the motion of the main body of the wearable device 100d. The wearable device 100d may be rotated or tilted in various directions. In this case, the motion detector 4865 may detect motion characteristics such as rotation direction, angle, and inclination using at least one of various sensors such as a geomagnetic sensor, a gyro sensor, and an acceleration sensor.

In addition, although not shown in FIG. 48, in the embodiment, a USB port to which a USB connector can be connected in the wearable device 100d, various external input ports for connecting to various external terminals such as a headset, mouse, LAN, etc., DMB (Digital Multimedia Broadcasting) may further include a DMB chip for receiving and processing signals, various sensors, and the like.

The names of components of the above-described wearable device 100d may be different. Also, the wearable device 100d according to the present disclosure may include at least one of the above-described components, and some components may be omitted or additional components may be further included.

The touch panel 4847, the microphone unit 4850, the imaging unit 4855, and the motion detection unit 4865 of FIG. 48 may correspond to the sensor units 210 of the wearable devices 100a, 100b, and 100c. The controller 4870 of FIG. 48 may correspond to the controller 220 of the wearable devices 100a, 100b, and 100c. The display unit 4810 of FIG. 48 may correspond to the display units 610 of the wearable devices 100b and 100c. The communication unit 4830 of FIG. 48 may correspond to the communication unit 1810 of the wearable device 100c.

49 is a diagram illustrating an example in which the wearable device 100 performs a specific function according to a user's situation in a vehicle using at least one of a mobile device 1910a and a vehicle 1910b, according to an embodiment. to be.

Referring to FIG. 49 , the wearable device 100 may be communicatively connected to at least one of a mobile device 1910a and a vehicle 1910b through a network. Network includes Local Area Network (LAN), Wide Area Network (WAN), Value Added Network (VAN), mobile radio communication network, satellite communication network, and combinations thereof It is a data communication network in a comprehensive sense that allows each network constituent entity shown in FIG. 49 to communicate smoothly with each other, and may include wired Internet, wireless Internet, and mobile wireless communication network. In addition, the wearable device 100 may be a device with relatively low computing power. Accordingly, the wearable device 100 utilizes the computing power of the mobile device 1910a and/or the vehicle 1910b to perform can perform a specific function according to the user's situation. The wearable device 100 may perform a predetermined function of the wearable device 100 according to whether the user has entered a vehicle or whether the user is driving.

50 is a flowchart of a method in which the wearable device 100 forms a network with the mobile device 1910a and the vehicle 1910b and performs a specific function while the user is driving, according to an embodiment.

Referring to FIG. 50 , a mobile device 1910a connected to the wearable device 100 may use vehicle information received from a vehicle 1910b to determine whether a user has entered the vehicle, and motion information of the wearable device 100 It is possible to determine the user's status using

In step S5002, the mobile device 1910a may establish communication with the vehicle 1910b. The mobile device 1910a may be connected to the vehicle 1910b through short-range communication, but is not limited thereto.

In step S5004, the vehicle 1910b may provide vehicle information to the mobile device 1910a. The vehicle information may include, for example, a vehicle model, vehicle identification number, vehicle state information, and vehicle driving information. The vehicle's unique number may include, for example, a license plate number or an identification number of the vehicle itself. According to an embodiment, the vehicle information may be automatically transmitted from the vehicle 1910b to the mobile device 1910a when communication between the mobile device 1910a and the vehicle 1910b is established. According to another embodiment, the vehicle 1910b may transmit vehicle information to the mobile device 1910a in response to a request from the mobile device 1910a.

In step S5006, the mobile device 1910a may determine that the user has entered the vehicle 1910b. The mobile device 1910a may determine that the user has entered the vehicle 1910b by receiving vehicle information from the vehicle 1910b and comparing the received vehicle information with vehicle information pre-registered in the mobile device 1910a. .

In step S5008, the mobile device 1910a may request motion information from the wearable device 100. The mobile device 1910a may request motion information of the wearable device 100 from the wearable device 100 at predetermined intervals. Alternatively, the mobile device 1910a may request motion information of the wearable device 100 from the wearable device 100 when it is determined that a preset event has occurred. For example, if the mobile device 1910a determines that the mobile device 1910a moves in a preset pattern, the mobile device 1910a may request motion information of the wearable device 100 from the wearable device 100 . Also, for example, when the mobile device 1910a receives preset vehicle information from the vehicle 1910b and determines that the vehicle 1910b moves in a preset pattern, the mobile device 1910a sends the wearable device 100 a wearable Motion information of the device 100 may be requested. However, it is not limited thereto.

In step S5010, the wearable device 100 may sense the movement of the wearable device 100. The wearable device 100 uses sensors provided in the wearable device 100 to obtain acceleration values, vibration values, inclination values, location information, earth magnetic field information, proximity/touch information, image pickup signals, sounds, infrared detection values, and the like. By obtaining state information, motion information of the wearable device 100 may be generated.

In step S5012, the wearable device 100 may provide motion information of the wearable device 100 to the mobile device 1910a. The wearable device 100 may transmit motion information of the wearable device 100 to the mobile device 1910a at a preset period. Alternatively, when a predetermined event occurs, the wearable device 100 may transmit motion information of the wearable device 100 to the mobile device 1910a. For example, the wearable device 100 may transmit motion information of the wearable device 100 to the mobile device 1910a when the change value of the motion of the wearable device 100 is greater than or equal to a preset value. Also, for example, the wearable device 100 may transmit movement information of the wearable device 100 to the mobile device 1910a when the wearable device 100 moves in a preset pattern. For example, when the wearable device 100 determines that the wearable device 100 rotates clockwise or counterclockwise at an angle greater than or equal to a preset value, the wearable device 100 may transmit motion information of the wearable device 100 to the mobile device 1910a. have. However, it is not limited thereto.

In step S5014, the mobile device 1910a may determine whether the user is driving. The mobile device 1910a may analyze motion information of the wearable device 100 to determine whether the user is driving. In addition, the mobile device 1910a may further use motion of the mobile device 1910a, a communication state with the vehicle 1910b, and vehicle information received from the vehicle 1910b to determine whether the user is driving. For example, the mobile device 1910a may determine whether the user is driving, whether the user has stopped the vehicle while driving, and whether the speed of the vehicle 1910b driven by the user is equal to or greater than a predetermined value. However, it is not limited thereto.

In step S5016, the mobile device 1910a may determine a preset function of the wearable device 100 corresponding to the driving state. Functions of the wearable device 100 may be set in various ways according to the user's driving state. The functions of the wearable device 100 according to the user's driving state include, for example, a function for controlling the radio and an optical disc player of the vehicle 1910b, a function for controlling the navigation of the vehicle 1910b, and the wearable device 100 ), and a function of activating/deactivating the screen of the wearable device 100. However, it is not limited thereto.

In step S5018, the mobile device 1910a may provide the wearable device 100 with a control command for changing function settings or executing a function. The mobile device 1910a may identify an operating system (OS) installed in the wearable device 100 and transmit a control command in a format usable by the wearable device 100 to the wearable device 100 .

In step S5020, the wearable device 100 may change function settings or execute functions. The wearable device 100 may change a function setting of the wearable device 100 or execute a function by using a control command received from the mobile device 1910a. For example, the wearable device 100 displays a user interface for changing the volume of a radio and an optical disc player of the vehicle 1910b and a user interface for controlling navigation of the vehicle 1910b on the screen of the wearable device 100. can be displayed on Also, for example, the wearable device 100 may change communication settings of the wearable device 100 . Also, for example, the wearable device 100 may activate or deactivate a screen of the wearable device 100 . However, it is not limited thereto.

51 is a flowchart of a method of forming a network with a mobile device 1910a by the wearable device 100 and performing a specific function while a user is driving, according to an embodiment. In FIG. 51 , the wearable device 100 and the mobile device 1910a may not communicate with the vehicle 1910b, and the mobile device 1910a communicates with the wearable device 100 and sets functions of the wearable device 100. It may be changed or the function of the wearable device 100 may be executed.

Steps S5106 to S5118 of FIG. 51 correspond to steps S5008 to S5020 of FIG. 50 , and descriptions of steps S5106 to S5116 are omitted for convenience.

In step S5102, the mobile device 1910a may sense the movement of the mobile device 1910a. The mobile device 1910a may detect a movement of the mobile device 1910a using at least one sensor in the mobile device 1910a.

In step S5104, the mobile device 1910a may determine whether the user has entered the vehicle 1910b. The mobile device 1910a may determine that the user has entered the vehicle 1910b when the movement pattern of the mobile device 1910a is a preset pattern. In addition, the mobile device 1910a may determine that the user has entered the vehicle 1910b when the moving speed of the mobile device 1910a is greater than or equal to a preset value. However, it is not limited thereto.

When the mobile device 1910a determines that the user has entered the vehicle 1910b, the mobile device 1910a may search for the wearable device 100 in the vicinity. Also, in step S5106, the mobile device 1910a may request motion information of the wearable device 100 from the searched wearable device 100.

52 is a flowchart of a method of performing a specific function when the wearable device 100 forms a network with the vehicle 1910b and the user is driving, according to an embodiment.

Steps S5208 to S5220 of FIG. 52 correspond to steps S5008 to S5020 of FIG. 50 , and descriptions of steps S5208 to S5220 are omitted for convenience.

In step S5202, the vehicle 1910b may establish communication with the wearable device 100. When the user enters the vehicle, the wearable device 100 may search for the vehicle 1910b and establish communication with the searched vehicle 1910b.

In step S5204, the wearable device 100 may transmit device information to the vehicle 1910b. As the wearable device 100 establishes communication with the vehicle 1910b, it may transmit the identification value and OS information of the wearable device 100 to the vehicle 1910b.

Thereafter, the vehicle 1910b may determine that the user has entered the vehicle 1910b and control functions of the wearable device 100 .

53 is a flowchart of a method of executing a function of the wearable device 100 according to a control command received from the mobile device 1910a when the wearable device 100 satisfies a predetermined condition, according to some embodiments.

In step S5302, the mobile device 1910a may determine a preset function of the wearable device 100 corresponding to the user's driving state. Functions of the wearable device 100 may be set in various ways according to the user's driving state. The functions of the wearable device 100 according to the user's driving state include, for example, a function for controlling the radio and an optical disc player of the vehicle 1910b, a function for controlling the navigation of the vehicle 1910b, and the wearable device 100 ), and a function of activating/deactivating the screen of the wearable device 100. However, it is not limited thereto.

In step S5304, the mobile device 1910a may determine a condition for executing a function of the wearable device 100. The conditions for executing the function of the wearable device 100 are the driving state of the vehicle 1910b, the distance between the current location of the vehicle 1910b and the destination, the current time, and the type of function currently activated in the wearable device 100. etc. can be determined based on. In addition, the mobile device 1910a may set conditions for function execution for each function of the wearable device 100 .

For example, the mobile device 1910a may set a condition for the wearable device 100 to perform a specific function when it is determined that the vehicle 1910b is stopped for a predetermined amount of time or longer. For example, the mobile device 1910a may set a condition for the wearable device 100 to activate the screen of the wearable device 100 when it is determined that the vehicle 1910b is stopped for 5 seconds or longer. However, it is not limited thereto.

Also, for example, the mobile device 1910a may set a condition so that the wearable device 100 performs or does not perform a specific function when it is determined that the vehicle 1910b is driving for a predetermined amount of time or more. . For example, if it is determined that the vehicle 1910b is driving for 1 second or more, the wearable device 100 may set a condition not to execute a function unrelated to the control of the vehicle 1910b. However, it is not limited thereto.

In step S5306, the mobile device 1910a may transmit a control command for executing the function of the wearable device 100 to the wearable device 100, and in step S5308, the mobile device 1910a executes the function of the wearable device 100. Information on the condition for may be transmitted to the wearable device 100 .

In step S5310, the wearable device 100 may sense the movement of the wearable device 100. The wearable device 100 may sense the movement of the wearable device 100 using various sensors included in the wearable device 100 . However, the wearable device 100 is not limited thereto, and the wearable device 100 may obtain various types of information necessary for determining whether a condition for executing a function corresponding to a control command received from the mobile device 1910a is satisfied.

In step S5312, the wearable device 100 may determine whether a condition for executing a function is satisfied. The wearable device 100 may identify a function corresponding to the control command received from the mobile device 1910a and determine whether a condition corresponding to the identified function is satisfied. For example, if the function corresponding to the control command received from the mobile device 1910a is a function of activating the screen of the wearable device 100, the wearable device 100 based on motion information of the wearable device 100, It may be determined whether the vehicle 1910b has been stopped for more than 5 seconds.

As a result of the determination in step S5312, if it is determined that the conditions for executing the function of the wearable device 100 are satisfied, in step S5314 the wearable device 100 may execute the function of the wearable device 100 according to the received control command. .

54 is a flowchart of a method of executing a function of the wearable device 100 according to a control command received from a vehicle 1910b when the wearable device 100 satisfies a predetermined condition, according to some embodiments.

Referring to FIG. 54 , the vehicle 1910b of FIG. 54, like the mobile device 1910a of FIG. A control command and condition information may be transmitted to the wearable device 100 .

55 is a diagram illustrating an example in which the wearable device 100 of a user driving a vehicle 1910b and the mobile device 1910a perform a call with another device 200 of another user, according to some embodiments.

Referring to FIG. 55 , another device 200 of another user may make a call to the user's mobile device 1910a, and the mobile device 1910a may call the user through the wearable device 100c when the user is driving. It may work with the wearable device 100c to make a phone call with another user. The mobile device 1910a may relay a voice call for a phone call between the wearable device 100c and the other device 200 . Alternatively, the mobile device 1910a may provide call information of the other device 200 to the wearable device 100c so that a call may be connected between the wearable device 100c and the other device 200 .

FIG. 56 is a diagram illustrating an example of a method in which the wearable device 100c of a user while driving makes a phone call with another device 200 through the mobile device 1910a, according to some embodiments. In FIG. 56 , the mobile device 1910a may relay a phone call between the wearable device 100c and another device 200 while the phone call function of the mobile device 1910a is activated.

In step S5600, the mobile device 1910a may determine the user's driving state. The mobile device 1910a may determine whether the user is driving. The mobile device 1910a may determine whether the user is driving by analyzing the motion of the wearable device 100c. In addition, the mobile device 1910a may determine whether the user is driving by using movement of the mobile device 1910a, a communication state with the vehicle 1910b, and vehicle information received from the vehicle 1910b. For example, the mobile device 1910a may determine whether the user is driving, whether the user has stopped the vehicle while driving, and whether the speed of the vehicle 1910b driven by the user is equal to or greater than a predetermined value. However, it is not limited thereto.

In step S5602, the mobile device 1910a may determine whether the navigation application is executed. The mobile device 1910a may determine whether a navigation application in the mobile device 1910a is running. Meanwhile, the mobile device 1910a may determine whether a navigation device in the vehicle is running.

In step S5604, the mobile device 1910a may receive a call for a phone call from the other device 200. The other device 200 may transmit a call for making a phone call to the mobile device 1910a, and the mobile device 1910a may receive the transmitted call.

In step S5606, the mobile device 1910a may inform the wearable device 100c of receiving a call from another device 200. When it is determined that the user is driving, the mobile device 1910a may notify the wearable device 100c that a call has been received from another device 200 . In addition, the mobile device 1910a may notify the wearable device 100c that a call has been received from another device 200 when it is determined that a navigation application in the mobile device 1910a is running. In this case, the mobile device 1910a may provide call information (eg, phone number, user name, etc.) of the other device 200 to the wearable device 100c.

In step S5608, the wearable device 100c may display a UI for making a phone call. The wearable device 100c may output the call information received from the mobile device 1910a through the display of the wearable device 100c. The UI for making a phone call may include a button for determining whether to make a call with another device 200 . Also, the wearable device 100c may output a ringtone through a speaker of the wearable device 100c or generate vibration through a diaphragm within the wearable device 100c.

In step S5610, the wearable device 100c may receive a user input for making a phone call. The wearable device 100c may receive a user input through the displayed UI. Also, the wearable device 100c may receive a user's voice command for making a phone call.

In step S5612, the wearable device 100c may request a call connection between the mobile device 1910a and the other device 200 from the mobile device 1910a. The wearable device 100c may request the mobile device 1910a to establish a network for a phone call between the mobile device 1910a and another device 200 .

In step S5614, the mobile device 1910a may connect a call with the other device 200. The mobile device 1910a can connect a call with the other device 200 by forming a network for a call with the other device 200 . Also, as the call between the mobile device 1910a and the other device 200 is connected, the mobile device 1910a can relay a phone call between the wearable device 100c and the other device 200.

In step S5616, the mobile device 1910a may receive another user's call voice from the other device 200. The other device 200 may acquire another user's call voice and transmit the obtained other user's call voice to the mobile device 1910a. The mobile device 1910a may receive another user's call voice transmitted from the other device 200 from the other device 200 .

In step S5618, the mobile device 1910a may provide another user's call voice to the wearable device 100c. The mobile device 1910a may transmit another user's call voice to the wearable device 100c through a pre-established network with the wearable device 100c. In this case, the mobile device 1910a may convert the format of another user's call voice according to the specifications of the wearable device 100c.

In step S5620, the wearable device 100c may output another user's call voice. The wearable device 100c may output another user's voice through a speaker of the wearable device 100c. Also, the wearable device 100c may convert another user's call voice into text and output the converted text through the display of the wearable device 100c.

In step S5622, the wearable device 100c may obtain a call voice input from the user. The user may utter a call voice toward the wearable device 100c for a phone call with another user, and the wearable device 100c may record the user's call voice.

In step S5624, the wearable device 100c may provide the user's phone call voice to the mobile device 1910a. In step S5626, the mobile device 1910a may provide the user's call voice to the other device 200. The mobile device 1910a may transfer the user's call voice to the other device 200 .

FIG. 57 is a diagram illustrating an example of a method for a user's wearable device 100c while driving to make a direct phone call with another device 200, according to some embodiments. Since steps S5700 to S5710 of FIG. 57 correspond to steps S5600 to S5610 of FIG. 56 , descriptions of steps S5700 to S5710 will be omitted for convenience.

In step S5712, the mobile device 1910a may terminate the phone call function. The mobile device 1910a may end the phone call function after notifying the wearable device 100c of receiving the call. The wearable device 100c may transmit an AKC signal indicating that the call reception notification has been successfully received to the mobile device 1910a, and after the mobile device 1910a receives the AKC signal, communication with the other device 200 You can end the phone call function for phone calls.

However, the point at which the mobile device 1910a terminates the phone call function is not limited to the above. For example, the mobile device 1910a may end the phone call function after confirming that a phone call between the wearable device 100c and the other device 200 starts. Alternatively, for example, after the wearable device 100c requests the other device 200 to form a network for a phone call with the other device 200, the mobile device 1910a may end the phone call function.

In step S5714, the wearable device 100c may form a network for a call with another device 200. After receiving a user input for a phone call, the wearable device 100c may request another device 200 to connect the call. The wearable device 100c may request a call connection for a phone call from the other device 200 by using the phone number of the other device 200 received from the mobile device 1910a. In this case, the wearable device 100c may inform the other device 200 that the user is the same as the user of the mobile device 1910a.

Also, the other device 200 may receive a call connection request from the wearable device 100c and display a UI for call connection on the display of the other device 200 . In addition, the other device 200 may use a displayed UI, for example, a guide phrase such as "Do you want to establish a call connection with the wearable device 100c being used by the user of the mobile device 1910a you called?" can display.

In addition, a network for a call between the other device 200 and the wearable device 100c may be formed based on a user input through the UI displayed in the other device 200 .

In step S5716, the wearable device 100c may receive another user's call voice from the other device 200. The other device 200 may obtain another user's call voice and transmit the obtained other user's call voice to the wearable device 100c.

In step S5718, the wearable device 100c may output another user's call voice. The wearable device 100c may output another user's voice through a speaker of the wearable device 100c. Also, the wearable device 100c may convert another user's call voice into text and output the converted text through the display of the wearable device 100c.

In step S5720, the wearable device 100c may obtain a call voice input from the user. The user may utter a call voice toward the wearable device 100c for a phone call with another user, and the wearable device 100c may record the user's call voice.

In step S5722, the wearable device 100c may provide the user's call voice to the other device 200.

Meanwhile, the present invention can be implemented by storing computer readable codes in a computer readable storage medium. The computer readable storage medium includes all types of storage devices in which data readable by a computer system is stored.

The computer-readable code, when read and executed by a processor from the computer-readable storage medium, is configured to perform steps for implementing the method for controlling a wearable device according to the present invention. The computer readable code may be implemented in various programming languages. Also, functional programs, codes, and code segments for implementing the embodiments of the present invention can be easily programmed by those skilled in the art.

Examples of computer-readable storage media include ROM, RAM, CD-ROM, magnetic tape, floppy disk, optical data storage devices, and the like. In addition, the computer readable storage medium may be distributed to computer systems connected by a network, so that computer readable codes may be stored and executed in a distributed manner.

Although the embodiments of the present invention have been described with reference to the above and accompanying drawings, those skilled in the art to which the present invention pertains can implement the present invention in other specific forms without changing the technical spirit or essential features. You will understand that there is Therefore, the embodiments described above should be understood as illustrative in all respects and not limiting.

Claims (41)

delete delete delete delete delete delete delete delete delete delete delete delete delete delete delete delete delete delete delete delete delete delete delete delete delete For mobile devices,
a sensor detecting at least one motion of the mobile device;
a communication unit that communicates with the vehicle;
output interface; and
including at least one processor, wherein the at least one processor comprises:
Controlling the communication unit to establish Bluetooth communication with the vehicle based on vehicle information received from the vehicle;
determine a state of the mobile device corresponding to whether a user of the mobile device is driving the vehicle based on at least one of a communication state with the vehicle and the detected at least one motion of the mobile device;
Based on the determined state, controlling the mobile device to operate in a first mode for providing a notification through the mobile device or a second mode for providing the notification through another device instead of the mobile device;
Based on receiving a text message in the second mode, controlling the output interface to output an audio signal including content of the text message;
Based on establishing Bluetooth communication between the mobile device and the vehicle, transmitting music data to the vehicle through Bluetooth communication to output music data using a speaker included in the vehicle;
The at least one processor,
Communicating with a wearable device through the communication unit;
and transmitting information indicating that the user is driving to the wearable device, based on determining that the user of the mobile device is driving, and controlling the wearable device to change an operation mode to a driving mode. The method of claim 26,
and the state of the mobile device corresponds to whether a user of the mobile device is driving the vehicle. The method of claim 26,
the sensor comprises an acceleration sensor configured to detect vibration and rotation angles of the mobile device;
The at least one processor compares a pre-stored vibration pattern with the detected pattern of vibration, compares a pre-stored pattern of rotation angle with a pattern of the detected rotation angle, and determines a state of the mobile device based on the comparison. , a mobile device. The method of claim 26,
The mobile device of claim 1 , wherein the at least one processor determines whether a state of the mobile device corresponds to a state in which a user of the mobile device is driving the vehicle, based on the vehicle information. According to claim 29,
Wherein the vehicle information includes a vehicle identification number or license plate of the vehicle. The method of claim 26,
The mobile device, wherein the at least one processor controls the mobile device to perform a preset function in the first mode and not to perform a preset function in the second mode, based on the determined state. According to claim 31,
wherein the at least one processor is configured to automatically terminate the preset function based on determining that a user of the mobile device is not driving the vehicle. According to claim 31,
The at least one processor,
Based on determining that the user of the mobile device is not driving the vehicle, providing a user interface for selecting whether or not to end the preset function;
and terminating the preset function based on a user input. The method of claim 26,
Wherein the vehicle information relates to a public transportation vehicle, the at least one processor is configured to determine that a state of the mobile device does not correspond to a state in which a user of the mobile device is driving the vehicle. The method of claim 26,
The mobile device, wherein the at least one processor is configured to transmit a text message in an automatic answering mode based on receiving an incoming call in the second mode. A method for controlling a mobile device,
detecting at least one movement of the mobile device using a sensor of the mobile device;
establishing, by a processor of the mobile device, Bluetooth communication with the vehicle based on vehicle information received from the vehicle;
Determine, by the processor, a state of the mobile device corresponding to whether a user of the mobile device is driving the vehicle based on at least one of a communication state with the vehicle and the detected at least one motion of the mobile device doing;
Controlling, by the processor, the mobile device to operate in a first mode for providing a notification through the mobile device or a second mode for providing the notification through another device instead of the mobile device, based on the determined state step;
outputting an audio signal including contents of the text message based on the text message received in the second mode through an output interface of the mobile device;
Transmitting, by the processor, music data to the vehicle through Bluetooth communication to output music data using a speaker included in the vehicle, based on establishing Bluetooth communication between the mobile device and the vehicle. ;
communicating with the wearable device; and
and transmitting information indicating that the user is driving to the wearable device based on determining that the user of the mobile device is driving, and controlling the wearable device to change an operation mode to a driving mode. control method. 37. The method of claim 36,
wherein the state of the mobile device corresponds to whether a user of the mobile device is driving the vehicle. 37. The method of claim 36,
determining, by the processor, based on the vehicle information whether a state of the mobile device corresponds to a state in which a user of the mobile device is driving the vehicle. 37. The method of claim 36,
The vehicle information includes a vehicle identification number or a license plate of the vehicle. 37. The method of claim 36,
The mobile device control method further comprising transmitting a text message in an automatic answering mode based on receiving an incoming call in the second mode. A computer-readable recording medium on which a program for executing the method of any one of claims 36 to 40 is recorded on a computer.

Images