Patent Description:
Terminals can be classified into mobile/portable terminals and stationary terminals. In particular, the mobile terminals can be further classified into handheld terminals and vehicle mounted terminals according to possibility of user's direct portability.

Recently, functions of a mobile terminal tend to be diversified. For instance, the diversified functions include a function of data and audio communication, a function of photographing and video-making through a camera, a function of audio recording, a function of music file play through a speaker system, a function of outputting an image or video to a display unit, and the like. A prescribed terminal is further equipped with an electronic game play function or performs a multimedia player function. Particularly, a recent mobile terminal is able to receive multicast signals for providing visual contents such as a broadcast, a video, a television program and the like.

Meanwhile, devices with artificial intelligence capabilities are being discussed in various fields. A basic feature of these artificial intelligence devices is that they exist in stand states to interact with users. However, if a touch interface is used in stand state, there is a problem that a user should access the device every time. If a physical contact (e.g., a touch) is made with the device, there are limitations that a position of the device may change or that the device may fall. Voice recognition may be considered as another interface to solve this problem, but so far there is a problem with recognition rate performance.

<CIT> Al relates to a system and method for using multiple perceptual sensing technologies to capture information about a user's actions and for synergistically processing the information. <CIT> Al discloses a pointing interaction method, apparatus and system.

The present disclosure is intended to solve the above problem and other problems through the specification of the present disclosure.

A technical task of one embodiment of the present disclosure is to implement a vision-based UI using a depth camera rather than touch or voice recognition. In particular, in order to reduce an image processing time, an image of a part corresponding to a user's hand should be quickly and accurately extracted from an image acquired by the depth camera, for which a depth value (ex: Z-axis distance) of the image is used. When a user uses a vision-based UI, it can be assumed that a camera and a hand are closer to each other in comparison to other body. In this case, a background or other bodies that are farther than a random distance can be ignored through depth values, so only an image of the hand can be extracted quickly.

A technical task of another embodiment of the present disclosure is to accurately measure a direction that a finger points in and a distance between a device and the finger. To this end, it is intended to accurately measure a user and a point indicated by the finger and a fingertip and a hand image should be separated on the basis of a distance. Thus, a solution for accurately detecting a distance between the fingertip and the device is provided.

Dependent claims describe preferred embodiments.

In one technical aspect of the present disclosure, provided herein is a method of controlling a device including a depth camera according to one embodiment of the present disclosure, the method including acquiring a depth image using the depth camera, changing the device from a first state into a second state by analyzing the acquired depth image with reference to a memory, determining whether a user's finger points to the device with reference to the memory, changing the device from the second state into a third state if determining that that the user's finger points to the device, tracking an end point of the user's finger, and displaying a target point having a position changed in response to the tracked end point of the user's finger.

In another technical aspect of the present disclosure, provided herein is a device including a depth camera according to one embodiment of the present disclosure, the device including a memory storing one or more commands, a depth camera capturing at least one user's hand, a display module, and a controller configured to control the memory, the depth camera and the display module. The controller is further configured to control the depth camera to capture the at least one user's hand and control the display module to output a visual feedback changed based on the captured user's hand.

Effects of a mobile terminal and control method thereof according to the present disclosure are described as follows.

According to at least one of embodiments of the present disclosure, a new solution for interaction between a user and a device through a target point indicated by a user with a finger is provided.

According to at least one of embodiments of the present disclosure, a method of detecting a target point more accurately is defined in detail.

According to at least one of embodiments of the present disclosure, visual feedback for enabling a user to recognize a target point more easily and conveniently is provided.

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

Description will now be given in detail according to exemplary embodiments disclosed herein, with reference to the accompanying drawings. For the sake of brief description with reference to the drawings, the same or equivalent components may be provided with the same reference numbers, and description thereof will not be repeated. In general, a suffix such as "module" and "unit" may be used to refer to elements or components. Use of such a suffix herein is merely intended to facilitate description of the specification, and the suffix itself is not intended to give any special meaning or function. In the present disclosure, that which is well-known to one of ordinary skill in the relevant art has generally been omitted for the sake of brevity. The accompanying drawings are used to help easily understand various technical features and it should be understood that the embodiments presented herein are not limited by the accompanying drawings. As such, the present disclosure should be construed to extend to any alterations, equivalents and substitutes in addition to those which are particularly set out in the accompanying drawings.

It will be understood that when an element is referred to as being "connected with or to" another element, the element can be connected with the other element or intervening elements may also be present. In contrast, when an element is referred to as being "directly connected with" another element, there are no intervening elements present.

Mobile terminals presented herein may be implemented using a variety of different types of terminals. Examples of such terminals include cellular phones, smart phones, user equipment, laptop computers, digital broadcast terminals, Personal Digital Assistants (PDAs), Portable Multimedia Players (PMPs), navigators, slate PCs, tablet PCs, ultra books, wearable devices (for example, smart watches, smart glasses, Head Mounted Displays (HMDs)), and the like.

By way of non-limiting example only, further description will be made with reference to particular types of mobile terminals. However, such teachings apply equally to other types of terminals, such as those types noted above. In addition, these teachings may also be applied to stationary terminals such as digital TV, desktop computers, digital signage and the like.

Reference is now made to <FIG>, where <FIG> is a block diagram of a mobile terminal in accordance with the present disclosure, and <FIG> and <FIG> are conceptual views of one example of the mobile terminal, viewed from different directions.

The mobile terminal <NUM> is shown having components such as a wireless communication unit <NUM>, an input unit <NUM>, a sensing unit <NUM>, an output unit <NUM>, an interface unit <NUM>, a memory <NUM>, a controller <NUM>, and a power supply unit <NUM>. It is understood that implementing all of the illustrated components is not a requirement, and that greater or fewer components may alternatively be implemented. Referring now to <FIG>, the mobile terminal <NUM> is shown having wireless communication unit <NUM> configured with several commonly implemented components.

The wireless communication unit <NUM> typically includes one or more modules which permit communications such as wireless communications between the mobile terminal <NUM> and a wireless communication system, communications between the mobile terminal <NUM> and another mobile terminal, communications between the mobile terminal <NUM> and an external server.

To facilitate such communications, the wireless communication unit <NUM> includes one or more of a broadcast receiving module <NUM>, a mobile communication module <NUM>, a wireless Internet module <NUM>, a short-range communication module <NUM>, and a position location module <NUM>.

The sensing unit <NUM> is typically implemented using one or more sensors configured to sense internal information of the mobile terminal, the surrounding environment of the mobile terminal, user information, and the like. For example, in <FIG>, the sensing unit <NUM> is shown having a proximity sensor <NUM> and an illumination sensor <NUM>. If desired, the sensing unit <NUM> may alternatively or additionally include other types of sensors or devices, such as a touch sensor, an acceleration sensor, a magnetic sensor, a G-sensor, a gyroscope sensor, a motion sensor, an RGB sensor, an infrared (IR) sensor, a finger scan sensor, a ultrasonic sensor, an optical sensor (for example, camera <NUM>), a microphone <NUM>, a battery gauge, an environment sensor (for example, a barometer, a hygrometer, a thermometer, a radiation detection sensor, a thermal sensor, and a gas sensor, among others), and a chemical sensor (for example, an electronic nose, a health care sensor, a biometric sensor, and the like), to name a few. The mobile terminal <NUM> may be configured to utilize information obtained from sensing unit <NUM>, and in particular, information obtained from one or more sensors of the sensing unit <NUM>, and combinations thereof.

The controller <NUM> typically functions to control overall operation of the mobile terminal <NUM>, in addition to the operations associated with the application programs. The controller <NUM> processes signals, data, information and the like inputted or outputted through the above-mentioned components and/or runs application programs saved in the memory <NUM>, thereby processing or providing a user with appropriate information and/or functions.

The controller <NUM> may provide or process information or functions appropriate for a user by processing signals, data, information and the like, which are input or output by the various components depicted in <FIG>, or activating application programs stored in the memory <NUM>. As one example, the controller <NUM> controls some or all of the components illustrated in <FIG> according to the execution of an application program that have been stored in the memory <NUM>.

At least one portion of the respective components mentioned in the foregoing description can cooperatively operate to embody operations, controls or controlling methods of the mobile terminal according to various embodiments of the present invention mentioned in the following description. Moreover, the operations, controls or controlling methods of the mobile terminal can be embodied in the mobile terminal by running at least one or more application programs saved in the memory <NUM>.

Referring still to <FIG>, various components depicted in this figure will now be described in more detail.

The mobile communication module <NUM> can transmit and/or receive wireless signals to and from one or more network entities. Typical examples of a network entity include a base station, an external mobile terminal, a server, and the like. Such network entities form part of a mobile communication network, which is constructed according to technical standards or communication methods for mobile communications (for example, Global System for Mobile Communication (GSM), Code Division Multi Access (CDMA), CDMA2000(Code Division Multi Access <NUM>), EV-DO(Enhanced Voice-Data Optimized or Enhanced Voice-Data Only), Wideband CDMA (WCDMA), High Speed Downlink Packet access (HSDPA), HSUPA(High Speed Uplink Packet Access), Long Term Evolution (LTE) , LTE-A(Long Term Evolution-Advanced), and the like).

In some embodiments, another mobile terminal (which may be configured similarly to mobile terminal <NUM>) may be a wearable device, for example, a smart watch, a smart glass or a head mounted display (HMD), which is able to exchange data with the mobile terminal <NUM> (or otherwise cooperate with the mobile terminal <NUM>). The short-range communication module <NUM> may sense or recognize the wearable device, and permit communication between the wearable device and the mobile terminal <NUM>. In addition, when the sensed wearable device is a device which is authenticated to communicate with the mobile terminal <NUM>, the controller <NUM>, for example, may cause transmission of data processed in the mobile terminal <NUM> to the wearable device via the short-range communication module <NUM>. Hence, a user of the wearable device may use the data processed in the mobile terminal <NUM> on the wearable device. For example, when a call is received in the mobile terminal <NUM>, the user may answer the call using the wearable device. Also, when a message is received in the mobile terminal <NUM>, the user can check the received message using the wearable device.

The position-location module <NUM> is generally configured to detect, calculate, derive or otherwise identify a position of the mobile terminal. As an example, the position-location module <NUM> includes a Global Position System (GPS) module, a Wi-Fi module, or both. If desired, the position-location module <NUM> may alternatively or additionally function with any of the other modules of the wireless communication unit <NUM> to obtain data related to the position of the mobile terminal.

The input unit <NUM> may be configured to permit various types of input to the mobile terminal <NUM>. Examples of such input include audio, image, video, data, and user input. Image and video input is often obtained using one or more cameras <NUM>. Such cameras <NUM> may process image frames of still pictures or video obtained by image sensors in a video or image capture mode. The processed image frames can be displayed on the display unit <NUM> or stored in memory <NUM>. In some cases, the cameras <NUM> may be arranged in a matrix configuration to permit a plurality of images having various angles or focal points to be input to the mobile terminal <NUM>. As another example, the cameras <NUM> may be located in a stereoscopic arrangement to acquire left and right images for implementing a stereoscopic image.

The sensing unit <NUM> is generally configured to sense one or more of internal information of the mobile terminal, surrounding environment information of the mobile terminal, user information, or the like. The controller <NUM> generally cooperates with the sending unit <NUM> to control operation of the mobile terminal <NUM> or execute data processing, a function or an operation associated with an application program installed in the mobile terminal based on the sensing provided by the sensing unit <NUM>. The sensing unit <NUM> may be implemented using any of a variety of sensors, some of which will now be described in more detail.

The proximity sensor <NUM> may include a sensor to sense presence or absence of an object approaching a surface, or an object located near a surface, by using an electromagnetic field, infrared rays, or the like without a mechanical contact. The proximity sensor <NUM> may be arranged at an inner region of the mobile terminal covered by the touch screen, or near the touch screen.

The proximity sensor <NUM>, for example, may include any of a transmissive type photoelectric sensor, a direct reflective type photoelectric sensor, a mirror reflective type photoelectric sensor, a high-frequency oscillation proximity sensor, a capacitance type proximity sensor, a magnetic type proximity sensor, an infrared rays proximity sensor, and the like. When the touch screen is implemented as a capacitance type, the proximity sensor <NUM> can sense proximity of a pointer relative to the touch screen by changes of an electromagnetic field, which is responsive to an approach of an object with conductivity. In this case, the touch screen (touch sensor) may also be categorized as a proximity sensor.

The term "proximity touch" will often be referred to herein to denote the scenario in which a pointer is positioned to be proximate to the touch screen without contacting the touch screen. The term "contact touch" will often be referred to herein to denote the scenario in which a pointer makes physical contact with the touch screen. For the position corresponding to the proximity touch of the pointer relative to the touch screen, such position will correspond to a position where the pointer is perpendicular to the touch screen. The proximity sensor <NUM> may sense proximity touch, and proximity touch patterns (for example, distance, direction, speed, time, position, moving status, and the like).

In general, controller <NUM> processes data corresponding to proximity touches and proximity touch patterns sensed by the proximity sensor <NUM>, and cause output of visual information on the touch screen. In addition, the controller <NUM> can control the mobile terminal <NUM> to execute different operations or process different data according to whether a touch with respect to a point on the touch screen is either a proximity touch or a contact touch.

A touch sensor can sense a touch applied to the touch screen, such as display unit <NUM>, using any of a variety of touch methods. Examples of such touch methods include a resistive type, a capacitive type, an infrared type, and a magnetic field type, among others. As one example, the touch sensor may be configured to convert changes of pressure applied to a specific part of the display unit <NUM>, or convert capacitance occurring at a specific part of the display unit <NUM>, into electric input signals. The touch sensor may also be configured to sense not only a touched position and a touched area, but also touch pressure and/or touch capacitance. A touch object is generally used to apply a touch input to the touch sensor. Examples of typical touch objects include a finger, a touch pen, a stylus pen, a pointer, or the like.

When a touch input is sensed by a touch sensor, corresponding signals may be transmitted to a touch controller. The touch controller may process the received signals, and then transmit corresponding data to the controller <NUM>. Accordingly, the controller <NUM> may sense which region of the display unit <NUM> has been touched. Here, the touch controller may be a component separate from the controller <NUM>, the controller <NUM>, and combinations thereof.

In some embodiments, the controller <NUM> may execute the same or different controls according to a type of touch object that touches the touch screen or a touch key provided in addition to the touch screen. Whether to execute the same or different control according to the object which provides a touch input may be decided based on a current operating state of the mobile terminal <NUM> or a currently executed application program, for example.

The touch sensor and the proximity sensor may be implemented individually, or in combination, to sense various types of touches. Such touches includes a short (or tap) touch, a long touch, a multi-touch, a drag touch, a flick touch, a pinch-in touch, a pinch-out touch, a swipe touch, a hovering touch, and the like.

If desired, an ultrasonic sensor may be implemented to recognize position information relating to a touch object using ultrasonic waves. The controller <NUM>, for example, may calculate a position of a wave generation source based on information sensed by an illumination sensor and a plurality of ultrasonic sensors. Since light is much faster than ultrasonic waves, the time for which the light reaches the optical sensor is much shorter than the time for which the ultrasonic wave reaches the ultrasonic sensor. The position of the wave generation source may be calculated using this fact. For instance, the position of the wave generation source may be calculated using the time difference from the time that the ultrasonic wave reaches the sensor based on the light as a reference signal.

The camera <NUM> typically includes at least one a camera sensor (CCD, CMOS etc.), a photo sensor (or image sensors), and a laser sensor.

Implementing the camera <NUM> with a laser sensor may allow detection of a touch of a physical object with respect to a 3D stereoscopic image. The photo sensor may be laminated on, or overlapped with, the display device. The photo sensor may be configured to scan movement of the physical object in proximity to the touch screen. In more detail, the photo sensor may include photo diodes and transistors at rows and columns to scan content received at the photo sensor using an electrical signal which changes according to the quantity of applied light. Namely, the photo sensor may calculate the coordinates of the physical object according to variation of light to thus obtain position information of the physical object.

In some embodiments, the display unit <NUM> may be implemented as a stereoscopic display unit for displaying stereoscopic images.

A typical stereoscopic display unit may employ a stereoscopic display scheme such as a stereoscopic scheme (a glass scheme), an auto-stereoscopic scheme (glassless scheme), a projection scheme (holographic scheme), or the like.

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

The memory <NUM> can store programs to support operations of the controller <NUM> and store input/output data (for example, phonebook, messages, still images, videos, etc.). The memory <NUM> may store data related to various patterns of vibrations and audio which are output in response to touch inputs on the touch screen.

The memory <NUM> may include one or more types of storage mediums including a Flash memory, a hard disk, a solid state disk, a silicon disk, a multimedia card micro type, a card-type memory (e.g., SD or DX memory, etc), a Random Access Memory (RAM), a Static Random Access Memory (SRAM), a Read-Only Memory (ROM), an Electrically Erasable Programmable Read-Only Memory (EEPROM), a Programmable Read-Only memory (PROM), a magnetic memory, a magnetic disk, an optical disk, and the like. The mobile terminal <NUM> may also be operated in relation to a network storage device that performs the storage function of the memory <NUM> over a network, such as the Internet.

The controller <NUM> may typically control the general operations of the mobile terminal <NUM>. For example, the controller <NUM> may set or release a lock state for restricting a user from inputting a control command with respect to applications when a status of the mobile terminal meets a preset condition.

The power supply unit <NUM> can receive external power or provide internal power and supply the appropriate power required for operating respective elements and components included in the mobile terminal <NUM>. The power supply unit <NUM> may include a battery, which is typically rechargeable or be detachably coupled to the terminal body for charging.

Also, the power supply unit <NUM> may include a connection port. The connection port may be configured as one example of the interface unit <NUM> to which an external charger for supplying power to recharge the battery is electrically connected.

Also, various embodiments can be implemented in the computer and similar recording materials using software, hardware and the combination of software and hardware.

Referring now to <FIG> and <FIG>, the mobile terminal <NUM> is described with reference to a bar-type terminal body. However, the mobile terminal <NUM> may alternatively be implemented in any of a variety of different configurations. Examples of such configurations include watch-type, clip-type, glasses-type, or as a folder-type, flip-type, slide-type, swing-type, and swivel-type in which two and more bodies are combined with each other in a relatively movable manner, and combinations thereof. Discussion herein will often relate to a particular type of mobile terminal (for example, bar-type, watch-type, glasses-type, and the like). However, such teachings with regard to a particular type of mobile terminal will generally apply to other types of mobile terminals as well.

The mobile terminal <NUM> will generally include a case (for example, frame, housing, cover, and the like) forming the appearance of the terminal.

In this embodiment, the case is formed using a front case <NUM> and a rear case <NUM>. Various electronic components are incorporated into a space formed between the front case <NUM> and the rear case <NUM>. At least one middle case may be additionally positioned between the front case <NUM> and the rear case <NUM>.

The display unit <NUM> is shown located on the front side of the terminal body to output information. As illustrated, a window 151a of the display unit <NUM> may be mounted to the front case <NUM> to form the front surface of the terminal body together with the front case <NUM>.

In some embodiments, electronic components may also be mounted to the rear case <NUM>. Examples of such electronic components include a detachable battery <NUM>, an identification module, a memory card, and the like. Rear cover <NUM> is shown covering the electronic components, and this cover may be detachably coupled to the rear case <NUM>. Therefore, when the rear cover <NUM> is detached from the rear case <NUM>, the electronic components mounted to the rear case <NUM> are externally exposed.

As illustrated, when the rear cover <NUM> is coupled to the rear case <NUM>, a side surface of the rear case <NUM> is partially exposed. In some cases, upon the coupling, the rear case <NUM> may also be completely shielded by the rear cover <NUM>. In some embodiments, the rear cover <NUM> may include an opening for externally exposing a camera 121b or an audio output module 152b.

The cases <NUM>, <NUM>, <NUM> may be formed by injection-molding synthetic resin or may be formed of a metal, for example, stainless steel (STS), aluminum (Al), titanium (Ti), or the like.

As an alternative to the example in which the plurality of cases form an inner space for accommodating components, the mobile terminal <NUM> may be configured such that one case forms the inner space. In this example, a mobile terminal <NUM> having a uni-body is formed in such a manner that synthetic resin or metal extends from a side surface to a rear surface.

If desired, the mobile terminal <NUM> may include a waterproofing unit (not shown) for preventing introduction of water into the terminal body. For example, the waterproofing unit may include a waterproofing member which is located between the window 151a and the front case <NUM>, between the front case <NUM> and the rear case <NUM>, or between the rear case <NUM> and the rear cover <NUM>, to hermetically seal an inner space when those cases are coupled.

The mobile terminal <NUM> may be provided with the display unit <NUM>, the 1st audio output unit 152a, the 2nd audio output unit 152b, the proximity sensor <NUM>, the illumination sensor <NUM>, the light output unit <NUM>, the 1st camera 121a, the 2nd camera 121b, the 1st manipulating unit 123a, the 2nd manipulating unit 123b, the microphone <NUM>, the interface unit <NUM>, and the like.

<FIG> and <FIG> depict certain components as arranged on the mobile terminal.

However, it is to be understood that alternative arrangements are possible and within the teachings of the instant disclosure. Some components may be omitted or rearranged. For example, the first manipulation unit 123a may be located on another surface of the terminal body, and the second audio output module 152b may be located on the side surface of the terminal body.

The display unit <NUM> outputs information processed in the mobile terminal <NUM>. The display unit <NUM> may be implemented using one or more suitable display devices.

Examples of such suitable display devices include a liquid crystal display (LCD), a thin film transistor-liquid crystal display (TFT-LCD), an organic light emitting diode (OLED), a flexible display, a <NUM>-dimensional (3D) display, an e-ink display, and combinations thereof.

The display unit <NUM> may be implemented using two display devices, which can implement the same or different display technology. For instance, a plurality of the display units <NUM> may be arranged on one side, either spaced apart from each other, or these devices may be integrated, or these devices may be arranged on different surfaces.

The display unit <NUM> may also include a touch sensor which senses a touch input received at the display unit. When a touch is input to the display unit <NUM>, the touch sensor may be configured to sense this touch and the controller <NUM>, for example, may generate a control command or other signal corresponding to the touch. The content which is input in the touching manner may be a text or numerical value, or a menu item which can be indicated or designated in various modes.

The touch sensor may be configured in a form of a film having a touch pattern, disposed between the window 151a and a display on a rear surface of the window 151a, or a metal wire which is patterned directly on the rear surface of the window 151a. Alternatively, the touch sensor may be integrally formed with the display. For example, the touch sensor may be disposed on a substrate of the display or within the display.

The display unit <NUM> may also form a touch screen together with the touch sensor. Here, the touch screen may serve as the user input unit <NUM> (see <FIG>). Therefore, the touch screen may replace at least some of the functions of the first manipulation unit 123a.

The first audio output module 152a may be implemented in the form of a speaker to output voice audio, alarm sounds, multimedia audio reproduction, and the like.

The window 151a of the display unit <NUM> will typically include an aperture to permit audio generated by the first audio output module 152a to pass. One alternative is to allow audio to be released along an assembly gap between the structural bodies (for example, a gap between the window 151a and the front case <NUM>). In this case, a hole independently formed to output audio sounds may not be seen or is otherwise hidden in terms of appearance, thereby further simplifying the appearance and manufacturing of the mobile terminal <NUM>.

The optical output module <NUM> can be configured to output light for indicating an event generation. Examples of such events include a message reception, a call signal reception, a missed call, an alarm, a schedule notice, an email reception, information reception through an application, and the like. When a user has checked a generated event, the controller can control the optical output unit <NUM> to stop the light output.

The first camera 121a can process image frames such as still or moving images obtained by the image sensor in a capture mode or a video call mode. The processed image frames can then be displayed on the display unit <NUM> or stored in the memory <NUM>.

The first and second manipulation units 123a and 123b may also be commonly referred to as a manipulating portion, and may employ any tactile method that allows the user to perform manipulation such as touch, push, scroll, or the like. The first and second manipulation units 123a and 123b may also employ any non-tactile method that allows the user to perform manipulation such as proximity touch, hovering, or the like.

In the figure, the first operation unit 123a is a touch key, the invention is not limited thereto. For example, the first operation unit 123a a mechanical key, or a combination of a touch key and a touch key.

The contents input by the first and second operation units 123a and 123b are variously set can be. For example, the first operation unit 123a may issue a command such as a menu, a home key, a cancel, and the second operation unit 123b receives the first sound output from the first or second sound output unit 152a or 152b the size of the sound to be output, and the switch to the touch recognition mode of the display unit <NUM> can be input.

The rear input unit can be manipulated by a user to provide input to the mobile terminal <NUM>. The input may be used in a variety of different ways. For example, the rear input unit may be used by the user to provide an input for power on/off, start, end, scroll, control volume level being output from the first or second audio output modules 152a or 152b, switch to a touch recognition mode of the display unit <NUM>, and the like. The rear input unit may be configured to permit touch input, a push input, or combinations thereof.

The rear input unit may be located to overlap the display unit <NUM> of the front side in a thickness direction of the terminal body. As one example, the rear input unit may be located on an upper end portion of the rear side of the terminal body such that a user can easily manipulate it using a forefinger when the user grabs the terminal body with one hand. Alternatively, the rear input unit can be positioned at most any location of the rear side of the terminal body.

Embodiments that include the rear input unit may implement some or all of the functionality of the first manipulation unit 123a in the rear input unit. As such, in situations where the first manipulation unit 123a is omitted from the front side, the display unit <NUM> can have a larger screen.

As a further alternative, the mobile terminal <NUM> may include a finger scan sensor which scans a user's fingerprint. The controller <NUM> can then use fingerprint information sensed by the finger scan sensor as part of an authentication procedure. The finger scan sensor may also be installed in the display unit <NUM> or implemented in the user input unit <NUM>.

The microphone <NUM> is shown located at an end of the mobile terminal <NUM>, but other locations are possible. If desired, multiple microphones may be implemented, with such an arrangement permitting the receiving of stereo sounds.

The interface unit <NUM> may serve as a path allowing the mobile terminal <NUM> to interface with external devices. For example, the interface unit <NUM> may include one or more of a connection terminal for connecting to another device (for example, an earphone, an external speaker, or the like), a port for near field communication (for example, an Infrared Data Association (IrDA) port, a Bluetooth port, a wireless LAN port, and the like), or a power supply terminal for supplying power to the mobile terminal <NUM>. The interface unit <NUM> may be implemented in the form of a socket for accommodating an external card, such as Subscriber Identification Module (SIM), User Identity Module (UIM), or a memory card for information storage.

The second camera 121b is shown located at the rear side of the terminal body and includes an image capturing direction that is substantially opposite to the image capturing direction of the first camera unit 121a. If desired, second camera 121a may alternatively be located at other locations, or made to be moveable, in order to have a different image capturing direction from that which is shown.

The second camera 121b can include a plurality of lenses arranged along at least one line. The plurality of lenses may also be arranged in a matrix configuration. The cameras may be referred to as an "array camera. " When the second camera 121b is implemented as an array camera, images may be captured in various manners using the plurality of lenses and images with better qualities.

As shown in <FIG>, a flash <NUM> is shown adjacent to the second camera 121b. When an image of a subject is captured with the camera 121b, the flash <NUM> may illuminate the subject.

As shown in <FIG>, the second audio output module 152b can be located on the terminal body. The second audio output module 152b may implement stereophonic sound functions in conjunction with the first audio output module 152a, and may be also used for implementing a speaker phone mode for call communication.

At least one antenna for wireless communication may be located on the terminal body. The antenna may be installed in the terminal body or formed by the case. For example, an antenna which configures a part of the broadcast receiving module <NUM> may be retractable into the terminal body. Alternatively, an antenna may be formed using a film attached to an inner surface of the rear cover <NUM>, or a case that includes a conductive material.

A power supply unit <NUM> for supplying power to the mobile terminal <NUM> may include a battery <NUM>, which is mounted in the terminal body or detachably coupled to an outside of the terminal body. The battery <NUM> may receive power via a power source cable connected to the interface unit <NUM>.

Also, the battery <NUM> can be recharged in a wireless manner using a wireless charger. Wireless charging may be implemented by magnetic induction or electromagnetic resonance.

The rear cover <NUM> is shown coupled to the rear case <NUM> for shielding the battery <NUM>, to prevent separation of the battery <NUM>, and to protect the battery <NUM> from an external impact or from foreign material. When the battery <NUM> is detachable from the terminal body, the rear case <NUM> may be detachably coupled to the rear case <NUM>.

An accessory for protecting an appearance or assisting or extending the functions of the mobile terminal <NUM> can also be provided on the mobile terminal <NUM>. As one example of an accessory, a cover or pouch for covering or accommodating at least one surface of the mobile terminal <NUM> may be provided. The cover or pouch may cooperate with the display unit <NUM> to extend the function of the mobile terminal <NUM>. Another example of the accessory is a touch pen for assisting or extending a touch input to a touch screen.

Meanwhile, in the present invention, it can be displayed using a flexible display. In the following, this will be discussed in more detail with attached drawings.

<FIG> is a conceptual view to describe another example of a deformable mobile terminal <NUM> according to the present invention.

Referring to <FIG>, a display unit <NUM> may be configured deformable in response to an external force. This deformation may include at last one of curving, bending, folding, twisting, rolling, and combinations thereof. The deformable display unit <NUM> may be named "flexible display unit". In particular, the flexible display unit <NUM> may include a general flexible display, an electronic paper (also known as e-paper), and a combination thereof. In general, a mobile terminal <NUM> may be configured to include the same or similar features of the former mobile terminal <NUM> shown in <FIG>.

Generally, a flexible display means a display that is light-weighted and non-fragile in a manner of being fabricated on a thin and flexible substrate having such properties of paper as curving, bending, folding, twisting, and rolling while maintaining the properties of an existing flat panel display.

The e-paper may be used to refer to a display technology that employs the properties of a general ink. The e-paper is different from the existing flat panel display in using reflective light. The e-paper is generally understood as changing displayed information by electrophoresis using twist balls or capsules.

In a state that the flexible display unit <NUM> is not deformed (for example, a state that the flexible display unit <NUM> has an infinite radius of curvature, referred to as a <NUM>st state), a display region of the flexible display unit <NUM> becomes a flat surface. In a state that the flexible display unit <NUM> is deformed from the <NUM>st state by an external force (for example, a state that the flexible display unit <NUM> has a finite radius of curvature, referred to as a <NUM>nd state), the display region may become a curved surface or a bent surface. As illustrated, information displayed in the second state may include a visual information outputted through the curved surface. The visual information may be implemented in a manner that light emission of each unit pixel (sub-pixel) arranged in a matrix configuration is controlled independently. In this case, the unit pixel denotes an elementary unit for representing a single color.

The flexible display unit <NUM> may enter not a flat state but a curved state (for example, a vertically curved state, a horizontally curved state, etc.) in the <NUM>st state. In doing so, if an external force is applied to the flexible display unit <NUM>, the flexible display unit <NUM> may be deformed into a flat state (or a less curved state) or a more curved state.

If desired, the flexible display unit <NUM> may embody a flexible touchscreen by being combined with a touch sensor. If a touch is applied to the flexible touchscreen, the controller <NUM> (cf. <FIG>) can perform a control in response to the touch input. The flexible touchscreen may be configured to sense a touch input not only in the <NUM>st state but also in the <NUM>nd state.

Meanwhile, the mobile terminal <NUM> according to the modified example may include a deformation sensing means for sensing the deformation of the flexible display unit <NUM>. The deformation sensing means may be included in the sensing unit <NUM> shown in <FIG>.

The deformation sensing means is provided to the flexible display unit <NUM> or the case <NUM> to sense information related to the deformation of the flexible display unit <NUM>. Examples of such information related to the deformation of the flexible display unit <NUM> may include a deformed direction of the flexible display unit <NUM>, a deformed degree of the flexible display unit <NUM>, a deformed position of the flexible display unit <NUM>, a deformed time of the flexible display unit <NUM>, an acceleration for restoring the deformed flexible display unit <NUM>, and the like. Besides, the information may include various kinds of information that can be sensed owing to the curving of the flexible display unit <NUM>.

The controller <NUM> can change the information displayed on the flexible display unit <NUM> or generate a control signal for controlling a function of the mobile terminal <NUM>, based on the information related to the deformation of the flexible display unit <NUM>. Such information is typically sensed by the deformation sensing means.

The mobile terminal <NUM> according to the modified example may include a case <NUM> for accommodating the flexible display unit <NUM>. The case <NUM> can be configured deformable together with the flexible display unit <NUM> in consideration of the property of the flexible display unit <NUM>.

A battery (not shown in the drawing) provided to the mobile terminal <NUM> may be configured deformable by an external force together with the flexible display unit <NUM> in consideration of the property of the flexible display unit <NUM>. In order to embody such a battery, it is able to employ a stack and folding scheme of stacking battery cells on each other.

The state deformation of the flexible display unit <NUM> is non-limited by the case of applying the external force. For example, the flexible display unit <NUM> can be deformed into the <NUM>nd state in response a command given by a user or application when the flexible display unit <NUM> is in the <NUM>st state.

Hereinafter, embodiments related to a control method that can be implemented in a mobile terminal configured as described above will be described with reference to the accompanying drawings.

<FIG> is a block diagram including main blocks of a device according to one embodiment of the present disclosure. A device <NUM> shown in <FIG> may include the mobile terminal shown in <FIG> and <FIG> or one of a mobile device, a tablet, a laptop, a notebook, a signage, a TV and a display device of any type, equipped with a depth camera.

The device shown in <FIG> includes a depth camera <NUM>, a memory <NUM>, a display module <NUM>, and a controller <NUM>. In the memory <NUM>, data capable of executing steps of a flowchart described later in the following drawings may be included selectively or all.

According to one embodiment of the present disclosure, there are three kinds of methods for extracting a depth value. Firstly, there is a ToF method (ToF Camera), which is a method of finding a distance of each pixel through a time taken for light to return after being reflected by an object. Secondly, there is a structured IR method (Structured IR Camera), which is a method of finding a distance of each pixel by finding a distortion extend of a projected pattern. Thirdly, there is a stereo method (Stereo Camera), which is a method of finding a distance of each pixel using binocular disparity. This is possible through the depth camera <NUM> shown in <FIG>.

In summary, the memory <NUM> stores at least one command and the depth camera <NUM> captures at least one user's hand.

The controller <NUM> controls the memory <NUM>, the depth camera <NUM> and the display module <NUM>. Particularly, the controller <NUM> captures the at least one user's hand by controlling the depth camera <NUM> and outputs a visual feedback, which is changed by the captured user's hand, by controlling the display module <NUM>.

The visual feedback includes a type of mirroring the captured user's hand for example and distinctively displays an end point of a finger located in a distance closest to the device <NUM>. This will be described in detail with reference to <FIG>, <FIG>, etc..

If determining that the captured user's hand is located between a minimum reference distance and a maximum reference distance from the device, the controller <NUM> outputs the visual feedback. This will be described in detail with reference to <FIG>, etc..

The controller <NUM> is designed to change a position of a target point outputted to the display module <NUM> based on the end point of the finger located in the closest distance from the device <NUM> and a reference point of the captured user's hand. This will be described in detail with reference to <FIG>, etc..

<FIG> is a flowchart showing a method of controlling a device according to one embodiment of the present disclosure. Other embodiments may be implemented through the embodiments of <FIG> and <FIG> by those skilled in the art.

A device including a depth camera according to one embodiment of the present disclosure acquires a depth image using the depth camera [S410] and changes a state of the device from a first state into a second state by analyzing the acquired depth image by referring to a memory [S420]. Here, the first state corresponds to a not-ready state shown in <FIG> and the second state corresponds to a ready state shown in <FIG>.

Furthermore, it is determined whether a user's finger points to the device by referring to the memory [S430]. If the user's finger is determined as pointing to the device, the state of the device is changed from the second state into a third state [S440]. Here, the second state corresponds to the ready state shown in <FIG> and the third state corresponds to an active state shown in <FIG>.

An end point of the user's finger is tracked [S450], and a target point of which position is changed according to the tracked end point of the user's finger is displayed [S460].

The step S420 of changing from the first state into the second state includes a step of removing values of pixels failing to exist between a minimum reference distance and a maximum reference distance by comparing each pixel value of the depth image, a step of estimating pixels, of which top, bottom, right and left sides are attached among unremoved pixels, as one segment, a step of regarding a segment having the biggest pixel number as valid only if a plurality of segments exist, and a step of changing into a second state corresponding to a ready state if the pixel number of the regarded segment is equal to or greater than a preset threshold value. This will be described in detail with reference to <FIG>, etc..

The determining step S430 is designed to estimate a smallest value among the pixel values in the regarded segment as a pixel value closest to the device. This will be described in detail with reference to <FIG>, etc..

The determining step S430 includes a step of determining a first image including pixels located from a point estimated as the pixel value closest to the device to a first distance, a step of determining a second image including pixels located from the point estimated as the pixel value closest to the device to a second distance, and a step of determining a third image including pixels located from the point estimated as the pixel value closest to the device to a third distance, and is characterized in that the second distance is greater than the first distance and that the third distance is greater than the second distance. This will be described in detail with reference to <FIG>, etc..

Furthermore, although not shown in <FIG>, if the segment number of the second image is <NUM>, a size of the second image is smaller than a predetermined ratio of the third image, and a distance between a center point of the first image and a center point of the second image is smaller than the estimated pixel value closest to the device, a step of determining that the user's finger points to the device is further included, which falls within the scope of the present disclosure. This will be described in detail with reference to <FIG>, etc..

The displaying step S460 is characterized in changing a position of the target point based on a center point of a specific region of the acquired depth image and a fixed correction ratio. This will be described in detail with reference to <FIG>, etc..

<FIG> is a diagram to schematically describe a visual UI between a device and a user according to one embodiment of the present disclosure.

A device <NUM> according to one embodiment of the present disclosure includes a depth camera <NUM>, and moves a target point <NUM> according to a direction directed by an end point <NUM> of a finger of a user <NUM>. For more accurate detection, a corrected center point <NUM> of a hand is designed to be calculated automatically. The corrected center point <NUM> of the hand is calculated each pointing or the once-found corrected center point <NUM> of the hand continues to be used, which falls within the scope of the present disclosure.

<FIG> is a diagram showing the visual UI of <FIG> in detail. As shown in <FIG>, an overall shape of a hand captured by a depth camera of a device <NUM> is outputted as a mirroring shape <NUM> and a finger end point <NUM>, which is closest between a user and the device <NUM> and becomes a reference of pointing, is displayed in a manner of being further emphasized. And, it is designed that a position of a cursor <NUM> is moved in a manner of being linked to a motion of the finger end point <NUM>.

In summary, the present disclosure proposes a new method of enabling interaction between a user and a device through a target point indicated by a user with a finger. Here, when a user points with a finger at a display of a device, the indicated point means a point at which a straight line indicated by the finger and the display of the device meet together. The present disclosure includes a technology of recognizing a user's intention to use a pointing UI through a position and shape of a hand and a technology of finding coordinates of a target point through corrected coordinates of a finger end point and the hand. Through this, a state is separated according to user's intention and an operation and visual effect appropriate for each state are then defined. Furthermore, a method of controlling a target object through a target point is defined. First of all, a pointing UI proposed by the present disclosure is defined as one of three kinds of states. This is described in detail with reference to <FIG> as follows.

<FIG> is a diagram showing a changed state of a device according to one embodiment of the present disclosure. <FIG> is a diagram to describe a reference for changing the state shown in <FIG>.

A not-ready state <NUM> shown in <FIG> means a state that a valid segment does not exist within an interaction region <NUM> shown in <FIG>. The interaction region <NUM> means a case that a user's hand is located between a minimum distance <NUM> and a maximum distance <NUM> from a depth camera <NUM>.

A ready state <NUM> shown in <FIG> means that a valid segment exists within the interaction region <NUM> shown in <FIG>. A segment image acquired by the depth camera is processed (e.g., normalized) and then outputted through a display of a device. Thus, it is advantageous in that a user can easily recognize that the device enters a ready state now and whether a hand is located at a prescribed position within a Field Of View (FOV).

Finally, an active state <NUM> shown in <FIG> is a state of determining that a user points with a finger at a prescribed region of the display of the device. From this moment, algorithm for finding a target point operates, thereby bringing a technical effect of reducing unnecessary data processing.

Meanwhile, the state change is described in detail as follows.

Once a user's hand is recognized within an interaction region, a not-ready state is changed into a ready state. If the user's hand leaves the interaction region, the ready state is changed into the not-ready state again.

In addition, if the user's hand exists within the interaction region and a finger or the like is recognized as pointing to the display of the device, the ready state is changed into an active state. On the other hand, if the user's hand leaves the interaction region, it is changed into the not-ready state again.

<FIG> is a flowchart showing a process for switching between a not-ready state and a ready state shown in <FIG>.

A depth camera of a device according to one embodiment of the present disclosure acquires a depth image [S910]. After comparison of each pixel value of the depth image, values of pixels closer that a minimum distance or farther than a maximum distance are removed [S920].

Moreover, the remaining pixels are segmented [S930]. Namely, pixels having top, bottom, right and left sides are attached are regarded as a single segment.

Yet, if several segments exist, the segment having the biggest pixel number is left and values of the pixels of the rest of the segments are removed [S940].

It is determined whether the biggest pixel number of the segment is greater than a preset value (COUNT_THRESHOLD) [S950]. The preset value may be set or changed based on a size of a hand.

If the pixel number is greater than the preset value (COUNT_THRESHOLD) (e.g., a hand size), the state is changed into 'ready' [S960]. If the pixel number is smaller than the preset value (COUNT_THRESHOLD), the state is changed into 'not ready' [S970].

<FIG> is a flowchart showing a process for switching a ready state between an active state shown in <FIG>.

Steps S1010 to S1080 shown in <FIG> are identically described in <FIG> and redundant description will be omitted. Compared to <FIG>, <FIG> shows a process for changing into a ready state in detail.

If the pixel number schematically described in <FIG> is greater than a preset value (COUNT_THRESHOLD) (e.g., a hand size), the step S960 of changing a state into ready will be described in detail with reference to <FIG>.

As shown in <FIG>, a minimum distance is derived by deriving a smallest value from pixel values within a segment [S1061]. The minimum distance means a value of a pixel closest to a camera. The step S1061 will be described in detail with reference to <FIG> and <FIG>.

Subsequently, images A, B and C are extracted from the segment [S1062, S1063, S1064], which will be described in detail with reference to <FIG>.

Subsequently, through the steps S1062 to S1064, it is determined whether a hand before a device is valid data [S1065]. If not valid as a result of the determination, a ready state is maintained without being changed into an active state [S1060]. If valid as a result of the determination, it is changed into the active state through a step S1070. The aforementioned steps S1065 and S1060 will be described in detail with reference to <FIG>, and the aforementioned steps S1070 and S1071 will be described in detail with reference to <FIG>.

<FIG> is a flowchart showing the steps S1110 to S1160 shown in <FIG>. <FIG> shows data required for implementing the step S1110 shown in <FIG>.

As steps S1120 to S160 shown in <FIG> are identical to <FIG>, the step S1110 shown in <FIG> will be described in detail with reference to <FIG>.

<FIG> shows each pixel value of a depth image. Each pixel value indicates a distance from a depth camera of a device to each pixel.

Therefore, if the smallest value is derived from pixel values within an acquired segment, a minimum distance (i.e., a size of a pixel value closest to a camera) can be found. In the embodiment of <FIG>, the minimum distance corresponds to '<NUM>' of a smallest pixel value within a segment having a valid pixel value (not zero).

<FIG> shows data required for implementing the steps S1120 to S1140 shown in <FIG>.

As shown in <FIG>, a minimum distance means a pixel value of an end point of a finger closest to a camera of a device <NUM>.

An offset A (OFFSET_A) means a length of a fingertip and normally corresponds to about <NUM>. An offset B (OFFSET_B) means a length of two knuckles from the fingertip and an offset C (OFFSET_C) means a length from the fingertip to a hand. Moreover, at least one of the offsets A to C is variably changed to fit for a user through deep learning, which falls within the scope of the present disclosure.

An image C is found by removing all pixels except a pixel located between the offset B from the minimum distance and the offset C from the minimum distance. In order to find an image C other than a finger region, the finger region is removed through specific processing (e.g., erosion scheme). This will be described in detail with reference to <FIG>. Hence, a region C that is an outer rectangle region of the image C is defined. For reference, the image C corresponds to [<NUM>] of <FIG> and the region C corresponds to [<NUM>] of <FIG>, which is found experimentally.

Meanwhile, an image B is found by removing all pixels except a pixel located between the minimum distance and the offset B from the minimum distance only. Thereafter, a region B that is an outer rectangle region of the image B is defined. For reference, the image B corresponds to [<NUM>] of <FIG> and the region B corresponds to [<NUM>] of <FIG>, which is found experimentally.

Finally, an image A is found by removing all pixels except a pixel located between the minimum distance and the offset A from the minimum distance. Thereafter, a region A that is an outer rectangle region of the image A is defined.

<FIG> show data required for implementing steps the S1150 and S1160 shown in <FIG>.

A method of determining whether an acquired shape of a hand is valid data in the present disclosure is to determine whether a segment located within an interaction region is a hand pointing to something.

Firstly, it is determined whether the segment number of the image B (as described above, acquired by removing all pixels except a pixel located between the minimum distance and the offset B from the minimum distance) is <NUM>. As shown in <FIG>, a multitude of segments are confirmed in [<NUM>] and [<NUM>], whereas only <NUM> segment is acquired from [<NUM>] or [<NUM>]. Since [<NUM>] and [<NUM>] indicate a gesture of pointing with a finger, they should be excluded.

Secondly, it is determined whether a size of the region B is smaller than 'region C (as described above, the image C corresponding to the region C is acquired by removing all pixels except a pixel located between the minimum distance and the offset C from the minimum distance) * minimum magnification (MIN_RATIO)'. According to such calculation, [<NUM>] of <FIG> is filtered but the rest of [<NUM>], [<NUM>] and [<NUM>] are automatically excluded because of not corresponding to it. Therefore, as a gesture of pointing with a finger, [<NUM>] of <FIG> is filtered only.

Thirdly, it is determined whether a distance between a center ([<NUM>] of <FIG>) of the aforementioned region A and a center ([<NUM>] of <FIG>) of the aforementioned region B is smaller than a minimum distance (MIN_DISTANCE).

Of all of the aforementioned three conditions are met, the ready state is maintained. Therefore, as pointing tracking is performed in a state of a gesture of pointing with a finger only, there is a technical effect of minimizing unnecessary tracking. Of course, some of the three conditions are adopted according to the needs of those skilled in the art, which falls within the scope of the present disclosure.

<FIG> show data required for implementing the step S1070 shown in <FIG>.

If a pointing direction of a finger is determined with reference to a center point of a hand, it is highly probable that error will occur. Hence, after correction values crx and cry have been derived, it is necessary to change into an active state. This will be described in detail with reference to <FIG>as follows.

First of all, [<NUM>] shown in <FIG> indicates a center point of a hand region. Yet, if a direction in which a finger points to a device is determined based on the center point, there is a problem that a state of spreading out a finger should be always maintained. Hence, a technique of acquiring a correction point <NUM> shown in <FIG> is required.

In summary, as shown in <FIG>, by connecting the center point of the region A and the center point of the region B to each other, the correction point <NUM> is found. A method of finding the region A and the region B was described in the foregoing description.

First of all, an x-coordinate of the correction point is calculated as follows.

Meanwhile, a y-coordinate of the correction point is calculated as follows.

A distance calculated with reference to the x-coordinate of the correction point is represented as follows.

A distance calculated with reference to an x-coordinate of a hand center point is represented as follows.

A distance calculated with reference to the y-coordinate of the correction point is represented as follows.

A distance calculated with reference to the y-coordinate of the hand center point is represented as follows.

Hence, the correction values crx and cry may be found by the following equations. <MAT><MAT>
yet, the above equations are just exemplary, and equations of other types for deriving the result of <FIG> fall within the scope of the present disclosure.

<FIG> is a diagram to describe an embodiment of changing a target point in response to a motion of a hand. <FIG> is a diagram to describe an embodiment of using a fixed target point irrespective of a motion of a hand.

As described above, the correction point <NUM> of <FIG> may be calculated each time using a center point <NUM> of a region A and a center point <NUM> of a region B, which falls within the scope of the present disclosure. Yet, it is also intended to propose a solution for improving this in addition.

<FIG> and <FIG> are diagrams of a hand viewed in a top direction. For clarity of the description, a real hand shape is removed but informations <NUM>, <NUM> and <NUM> acquired through a depth camera are illustrated only. When a finer is moved right and left while a hand remains still, how a target point is changed is illustrated.

<FIG> shows a case of deriving a correction point <NUM> each time using a center point <NUM> of a region A and a center point <NUM> of a region B. In this case, an angle is changed greatly by variations of [<NUM>] and [<NUM>], thereby causing a problem that accuracy is lowered.

<FIG> shows a case of deriving the correction point <NUM> through a region C and a correction ratio. Since a hand remains still, a center point of the region C is identical, whereby the correction point <NUM> stays at the same position. Accordingly, accuracy is improved greatly.

In brief, after the correction point <NUM> has been found each time using the center point <NUM> of the region A and the center point <NUM> of the region B, if a target point is calculated, since a distance between [<NUM>] and [<NUM>] is very short, although one of the two is moved by <NUM> pixel only, a pointing angle is changed greatly. Thus, accuracy of the target point is considerably lowered. Yet, after the correction point <NUM> has been found using the center point of the region C, if the correction point <NUM> continues to be used, accuracy is improved.

<FIG> is a flowchart showing a process for tracking a target point in active state in detail. <FIG> shows data required for implementing a step S2011 shown in <FIG>.

As steps S2001 to S2010 shown in <FIG> are already described with reference to the previous drawings, a method of implementing a step S2011 shown in <FIG> will be described in detail with reference to <FIG>.

As described above, the correction point (i.e., [<NUM>] shown in <FIG>) is reconstructed through the correction values crx and cry. <MAT><MAT>.

Hence, through the correction point <NUM> and a ratio between a minimum distance (min_distance) and HAND_OFFSET, a target point <NUM> is extracted by the following equations. <MAT> <MAT>.

<FIG> is a flowchart to describe a process for selecting an object on a display of a device using a target point according to one embodiment of the present disclosure. <FIG> shows data required for implementing a step S2250 shown in <FIG>.

As described above, a device according to one embodiment of the present disclosure extracts a target point [S2210].

After a distance between a current point and a previous point has been calculated, it is determined whether a corresponding difference value is smaller than a preset distance reference value (DISTANCE_THRES) [S2220].

As a result of the determination [S2220], if the corresponding difference value is greater, a start time is changed into a current time [S2230]. As a result of the determination [S2220], if the corresponding difference value is smaller, a difference between the current time and the start time is calculated and it is determined whether the corresponding difference value is greater than a preset time reference value (TIME_THRES) [S2240].

As a result of the determination [S2240], if the corresponding difference value is greater, it is determined whether a target point <NUM> is located within a target region <NUM> [S2250].

As a result of the determination [S2240], if the target point <NUM> is located within the target region, it is designed to select or execute a target object <NUM> belonging to the target region <NUM> [S2260].

<FIG> is a diagram to describe visual feedback per state according to one embodiment of the present disclosure.

According to one embodiment of the present disclosure in <FIG> and the like a not-ready state, a ready state and an active state are defined. Embodiments that a pointing UI is changed per state are described with reference to <FIG>.

As shown in <FIG>, any visual feedback is not provided in a not-ready state. Yet, in a ready state, as shown in <FIG>, an object <NUM> controllable through a pointing UI is displayed. In order that a user can easily check how a hand is recognized in FOV of a depth camera of a device according to one embodiment of the present disclosure, a segment <NUM> located within an interaction region is outputted together (e.g., displaying a screen mirrored as if viewing a figure of a hand reflected through a mirror).

Furthermore, when a segment is displayed, resolution of the depth camera is matched to resolution of the display of the device. Namely, a depth image is enlarged/reduced to match the resolution of the display. When the depth image is data-processed (e.g., drawn), a depth value of each pixel is outputted (e.g., drawn) in a manner of being converted into ARGB with a big alpha value if getting closer to a minimum distance (Min_Distance) of an interaction region or ARGB with a small alpha value if getting closer to a maximum distance (Max_Distance). Furthermore, when leaving the interaction region, it is set to disappear together with blur processing.

Finally, as shown in <FIG>, a target point at which a user is pointing is outputted. And, an object region to which the target point belongs is displayed together.

<FIG> are diagrams showing a process for deleting a region corresponding to a finger in a hand related image acquired by a depth camera.

A hand image ((b) of <FIG>) can be acquired from an initially acquired original hand segment image (<NUM> shown in <FIG>) through the step <NUM> shown in <FIG>. As shown in <FIG>, the hand image consists of a finger region <NUM> and a hand <NUM>. Through the hand <NUM> resulting from removing the finger region <NUM> from the hand image <NUM> only, a specific region of the hand (<FIG>) is derived, a position of a target point can be found accurately.

An erosion scheme is used to remove the finger region. When a single pixel around is '<NUM>' only, the erosion scheme is a filter that changes a corresponding pixel value into <NUM>. Using this filter, as shown in <FIG>, it is possible to acquire an image from which the finger region is removed.

<FIG> shows a result from calculating a position of a target point <NUM> after removing a finger region and defining a hand region. On the other hand, <FIG> shows a result from calculating a position of the target point <NUM> by defining a hand region after removing a finger region. Compared to <FIG>, an embodiment of <FIG> finds a more accurate target point, which could be confirmed experimentally.

<FIG> are diagrams showing a process for controlling various functions with finger pointing according to one embodiment of the present disclosure.

<FIG> describes a case of applying a pointing UI according to one embodiment of the present disclosure in a process for communicating with an AI for a control command.

Artificial Intelligence (AI) devices may suggest next commands a user can give in advance. For example, if an AI device recognizes a user's voice command (e.g., 'I want to listen to music. ') while staying in a not-ready state [<FIG>], it displays items (e.g., "Next Song", "Another One", "Pause", "Stop", etc.) estimated as selectable next by a user [<FIG>].

In doing so, although the user may speak 'Next Song' as a voice command, as an already executed music sound is recognized as noise, error may occur or voice recognition may be unavailable. To solve such a problem, as shown in <FIG>, the corresponding command is executed by selecting 'Next Song' through the pointing UI of the present disclosure, which falls within the scope of the present disclosure.

<FIG> describes a case of applying a pointing UI according to another embodiment of the present disclosure in a process for communicating with an AI for a control command.

Artificial Intelligence (AI) devices may suggest various replies or options selectable in response to a user's request or query. For example, if an AI device recognizes a user's voice command (e.g., 'Could you recommend a quiet song?) while staying in a not-ready state [<FIG>], it displays a list of quiet songs expected to be selectable by a user [<FIG>].

In this case, the corresponding command is executed by selecting a song corresponding to 'Name C' through a pointing UI of the present disclosure, which falls within the scope of the present disclosure.

<FIG> shows a case of applying a pointing UI according to one embodiment of the present disclosure while an AI device is already outputting audio through a speaker.

For example, while a song is already executed or a search result is outputted in audio data form, if an AI device is controlled through voice, it may cause problems of inconvenience and a low recognition rate.

For example, while a device is outputting a music file, if a user speaks 'OK, LG' toward the audio played device, the device will output the audio 'I am listening. ' To the user by turning down a volume and the user may reduce the sound by speaking 'Please reduce the volume'.

Yet, in doing so, there is a problem that it is unable to listen to a song or description while such conversation is in progress. Therefore, while an AI device is outputting audio, if a pointing UI of the present disclosure is used instead of a voice command, all the above problems can be solved.

As shown in <FIG>, an AI device is reproducing a music file. In doing so, the AI device is in a not-ready state. Yet, if a user brings a hand closer to the AI device (recognized in an interaction region of the device), as shown in <FIG>, a control icon <NUM> is outputted in form of mirroring. From this time on, tracking on a user hand is performed. Namely, an active state is entered.

Subsequently, as shown in <FIG>, if a specific option (e.g., volume-up) is selected with a finger pointing <NUM>, a corresponding function is executed directly.

<FIG> shows a process for controlling a notification provided by an AI device through a pointing UI according to one embodiment of the present disclosure.

AI devices provide a user with convenient information in various forms. Yet, as described above, it is considerably inconvenient to give a voice command such as 'OK, LG' and the like or a touch with a hand each time. A pointing UI according to one embodiment of the present disclosure can solve such a problem.

As shown in <FIG>, in case of receiving a notification such as a text or the like, a screen of an AI device or the like is turned on automatically. In doing so, if a pointing <NUM> of a finger is recognized as pointing to a specific text <NUM>, a whole content <NUM> of the received text is displayed as shown in <FIG>. if a hand is not recognized for a predetermined time, as shown in <FIG>, the screen of the device is automatically turned off, whereby unnecessary battery consumption can be reduced advantageously.

<FIG> shows a process for controlling a notification provided by an AI device through a pointing UI according to another embodiment of the present disclosure.

As shown in <FIG>, in case of receiving a notification such as a text or the like, a screen of an AI device or the like is turned on automatically. In doing so, if a pointing <NUM> of a finger is recognized as pointing to a specific text <NUM>, it is estimated that a user has recognized the received text and a checked text <NUM> is not displayed any further as shown in <FIG>.

The present disclosure mentioned in the foregoing description can be implemented in a program recorded medium as computer-readable codes. The computer-readable media may include all kinds of recording devices in which data readable by a computer system are stored. The computer-readable media may include HDD (Hard Disk Drive), SSD (Solid State Disk), SDD (Silicon Disk Drive), ROM, RAM, CD-ROM, magnetic tapes, floppy discs, optical data storage devices, and the like for example and also include carrier-wave type implementations (e.g., transmission via Internet). Further, the computer may include the controller <NUM> of the terminal. The foregoing embodiments are merely exemplary and are not to be considered as limiting the present disclosure. The present teachings can be readily applied to other types of methods and apparatuses. Thus, it is intended that the present disclosure covers the modifications and variations of this disclosure that come within the scope of the appended claims.

Various embodiments for the implementation of the present disclosure are already described in detail in the previous content of BEST MODE FOR DISCLOSURE.

Claim 1:
A method of controlling a device including a depth camera (<NUM>, <NUM>, <NUM>), the method comprising:
acquiring (S410) a depth image using the depth camera (<NUM>, <NUM>, <NUM>);
analyzing the acquired depth image;
determining an image B by removing all pixels except pixels located between a minimum distance and a first offset (OFFSET_B) from the acquired depth image,
and determining an image A by removing all pixels except pixels located between the minimum distance and a second offset (OFFSET_A) from the acquired depth image;
changing (S420) the device from a first state into a second state based on the analysis;
determining (S430) whether a user's finger points to the device;
changing (S440) the device from the second state into a third state based on determining that the user's finger points to the device;
determining a center point of the image A, and
determining a center point of the image B;
determining a correction point of a user's hand by connecting the center points of the image A and the image B;
tracking (S450) an end point of the user's finger and the correction point; and
displaying a target point having a position changeable in response to the tracked end point of the user's finger and the tracked correction point.