Wearable device, method, and non-transitory computer readable storage medium for gesture input

Abstract

A wearable device is disclosed. The wearable device may identify a relative movement of a user's hand wearing another wearable device, in the field of view of a camera. The wearable device may set a first area within a first distance corresponding to the relative movement from an interference area in which the hand is not identified through the field of view of the camera. In response to identifying that the hand has been moved into the first area, the wearable device may acquire, through a communication circuit, movement data from the other wearable device transitioning from a low-power state to a normal state on the basis of the movement of the hand into the first area. The wearable device may identify a gesture of the user through the hand on the basis of the movement data.

Description

Wearable device, method, and non-transitory computer-readable recording medium for gesture input

[0001] The following descriptions relate to a wearable device, method, and non-transitory computer readable storage medium for gesture input.

[0002] To provide an enhanced user experience, electronic devices are being developed that provide augmented reality (AR) services that display computer-generated information in conjunction with external objects in the real world. These electronic devices may be wearable devices worn by a user. For example, these electronic devices may be AR glasses and / or head-mounted devices (HMDs). These electronic devices can identify user gestures via a camera.

[0003] A wearable device is disclosed. The wearable device may include a communication circuit. The wearable device may include a camera arranged to capture an image of a portion of a body of a user wearing the wearable device. The wearable device may include a processor. The wearable device may include a memory comprising instructions. The instructions, when executed by the processor, may cause the wearable device to identify a relative movement of a hand of the user wearing another wearable device within the field of view of the camera. The other wearable device may be in a low-power state that stops acquiring movement data of the other wearable device through a sensor of the other wearable device. The instructions, when executed by the processor, may cause the wearable device to establish a first area within a first distance corresponding to the relative movement from an obstructed area in which the hand is not identified through the field of view of the camera. The instructions, when executed by the processor, may cause the wearable device to request the motion data from the other wearable device through the communication circuitry in response to identifying that the hand has moved into the first area. The instructions, when executed by the processor, may cause the wearable device to obtain motion data from the other wearable device through the communication circuitry, the other wearable device transitioning from the low power state to the normal state based on the hand having moved into the first area. The instructions, when executed by the processor, may cause the wearable device to identify a gesture of the user with the hand based on the motion data.

[0004] A method is disclosed. The method may be performed on a wearable device comprising communication circuitry and a camera arranged to capture an image of a portion of a body of a user wearing the wearable device. The method may include identifying relative movement of a hand of the user wearing another wearable device within a field of view of the camera. The other wearable device may be in a low-power state that has stopped acquiring motion data of the other wearable device through a sensor of the other wearable device. The method may include establishing a first area within a first distance corresponding to the relative movement from an obstructed area in which the hand is not identified through the field of view of the camera. The method may include requesting the motion data from the other wearable device through the communication circuitry in response to identifying that the hand has moved into the first area. The method may include acquiring motion data from the other wearable device through the communication circuitry, transitioning from the low-power state to a normal state based on the movement of the hand into the first area. The method may include an action of identifying a gesture of the user through the hand based on the movement data.

[0005] A non-transitory computer-readable storage medium is disclosed. The non-transitory computer-readable storage medium may store a program including instructions. The instructions, when executed by a processor of a wearable device including communication circuitry and a camera arranged to capture images of a portion of a body of a user wearing the wearable device, may cause the wearable device to identify relative movement of a hand of the user wearing another wearable device within the field of view of the camera. The other wearable device may be in a low-power state that has stopped acquiring movement data of the other wearable device through a sensor of the other wearable device. The instructions, when executed by the processor, may cause the wearable device to establish a first area within a first distance corresponding to the relative movement from an obstructed area in which the hand is not identified through the field of view of the camera. The instructions, when executed by the processor, may cause the wearable device to request the motion data from the other wearable device through the communication circuitry in response to identifying that the hand has moved into the first area. The instructions, when executed by the processor, may cause the wearable device to obtain motion data from the other wearable device through the communication circuitry, the other wearable device transitioning from the low power state to the normal state based on the hand having moved into the first area. The instructions, when executed by the processor, may cause the wearable device to identify a gesture of the user with the hand based on the motion data.

[0006] FIG. 1 is a block diagram of an electronic device within a network environment according to various embodiments.

[0007] FIG. 2A illustrates an example of a perspective view of a wearable device, according to one embodiment.

[0008] FIG. 2b illustrates an example of one or more hardware elements disposed within a wearable device, according to one embodiment.

[0009] FIG. 3A illustrates an example of an appearance of a wearable device according to one embodiment.

[0010] FIG. 3b illustrates an example of an appearance of a wearable device according to one embodiment.

[0011] FIG. 4 illustrates an example block diagram of a wearable device according to one embodiment.

[0012] FIG. 5A illustrates an exemplary wearable device according to one embodiment.

[0013] FIG. 5b illustrates a cross-section of an exemplary wearable device according to one embodiment.

[0014] FIG. 5c is a block diagram of an exemplary wearable device according to one embodiment.

[0015] FIG. 5d is a state transition diagram of an exemplary wearable device according to one embodiment.

[0016] FIG. 6A illustrates an example of a field of view (FOV) acquired through a camera of a wearable device worn by a user in one embodiment.

[0017] FIG. 6b illustrates an example of a situation in which a user wearing a wearable device moves his or her hand in one embodiment.

[0018] FIG. 6c illustrates an example of a situation in which a user wearing a wearable device moves his or her hand in one embodiment.

[0019] FIG. 7A illustrates an example of a distance set by a wearable device in one embodiment.

[0020] FIG. 7b illustrates an example of a distance set by a wearable device in one embodiment.

[0021] Figure 8 illustrates an example of a situation where a user wears multiple wearable devices.

[0022] FIG. 9 illustrates an example of a field of view (FOV) of a wearable device according to movement of a user's hand in one embodiment.

[0023] FIG. 10 illustrates an example of a situation on the front side of a wearable device, in one embodiment.

[0024] FIG. 11 illustrates an example of a situation in which a wearable device sets an interference zone for an obstructing object in one embodiment.

[0025] Figure 12 is a flowchart illustrating the operation of a wearable device according to one embodiment.

[0026] Figure 13 is a flowchart illustrating the operation of a wearable device according to one embodiment.

[0027] Figure 14 is a flowchart illustrating the operation of a wearable device according to one embodiment.

[0028] FIG. 1 is a block diagram of an electronic device (101) within a network environment (100) according to various embodiments.

[0029] Referring to FIG. 1, in a network environment (100), an electronic device (101) may communicate with an electronic device (102) via a first network (198) (e.g., a short-range wireless communication network), or may communicate with at least one of an electronic device (104) or a server (108) via a second network (199) (e.g., a long-range wireless communication network). According to one embodiment, the electronic device (101) may communicate with the electronic device (104) via the server (108). According to one embodiment, the electronic device (101) may include a processor (120), a memory (130), an input module (150), an audio output module (155), a display module (160), an audio module (170), a sensor module (176), an interface (177), a connection terminal (178), a haptic module (179), a camera module (180), a power management module (188), a battery (189), a communication module (190), a subscriber identification module (196), or an antenna module (197). In some embodiments, the electronic device (101) may omit at least one of these components (e.g., the connection terminal (178)), or may have one or more other components added. In some embodiments, some of these components (e.g., the sensor module (176), the camera module (180), or the antenna module (197)) may be integrated into one component (e.g., the display module (160)).

[0030] The processor (120) may, for example, execute software (e.g., a program (140)) to control at least one other component (e.g., a hardware or software component) of the electronic device (101) connected to the processor (120) and perform various data processing or operations. According to one embodiment, as at least a part of the data processing or operations, the processor (120) may store commands or data received from other components (e.g., a sensor module (176) or a communication module (190)) in a volatile memory (132), process the commands or data stored in the volatile memory (132), and store result data in a non-volatile memory (134). According to one embodiment, the processor (120) may include a main processor (121) (e.g., a central processing unit or an application processor) or an auxiliary processor (123) (e.g., a graphics processing unit, a neural processing unit (NPU), an image signal processor, a sensor hub processor, or a communication processor) that can operate independently or together with the main processor (121). For example, when the electronic device (101) includes the main processor (121) and the auxiliary processor (123), the auxiliary processor (123) may be configured to use less power than the main processor (121) or to be specialized for a given function. The auxiliary processor (123) may be implemented separately from the main processor (121) or as a part thereof.

[0031] The auxiliary processor (123) may control at least a portion of functions or states associated with at least one component (e.g., a display module (160), a sensor module (176), or a communication module (190)) of the electronic device (101), for example, on behalf of the main processor (121) while the main processor (121) is in an inactive (e.g., sleep) state, or together with the main processor (121) while the main processor (121) is in an active (e.g., application execution) state. In one embodiment, the auxiliary processor (123) (e.g., an image signal processor or a communication processor) may be implemented as a part of another functionally related component (e.g., a camera module (180) or a communication module (190)). In one embodiment, the auxiliary processor (123) (e.g., a neural network processing unit) may include a hardware structure specialized for processing artificial intelligence models. The artificial intelligence models may be generated through machine learning. This learning can be performed, for example, on the electronic device (101) itself where the artificial intelligence model is executed, or can be performed through a separate server (e.g., server (108)). The learning algorithm can include, for example, supervised learning, unsupervised learning, semi-supervised learning, or reinforcement learning, but is not limited to the examples described above. The artificial intelligence model can include multiple artificial neural network layers.The artificial neural network may be one of a deep neural network (DNN), a convolutional neural network (CNN), a recurrent neural network (RNN), a restricted Boltzmann machine (RBM), a deep belief network (DBN), a bidirectional recurrent deep neural network (BRDNN), a deep Q-network, or a combination of two or more of the above, but is not limited to the examples described above. In addition to, or alternatively to, a hardware structure, an artificial intelligence model may include a software structure.

[0032] The memory (130) can store various data used by at least one component (e.g., processor (120) or sensor module (176)) of the electronic device (101). The data can include, for example, software (e.g., program (140)) and input data or output data for commands related thereto. The memory (130) can include volatile memory (132) or non-volatile memory (134).

[0033] The program (140) may be stored as software in the memory (130) and may include, for example, an operating system (142), middleware (144), or an application (146).

[0034] The input module (150) can receive commands or data to be used in a component of the electronic device (101) (e.g., a processor (120)) from an external source (e.g., a user) of the electronic device (101). The input module (150) can include, for example, a microphone, a mouse, a keyboard, a key (e.g., a button), or a digital pen (e.g., a stylus pen).

[0035] The audio output module (155) can output audio signals to the outside of the electronic device (101). The audio output module (155) can include, for example, a speaker or a receiver. The speaker can be used for general purposes, such as multimedia playback or recording playback. The receiver can be used to receive incoming calls. In one embodiment, the receiver can be implemented separately from the speaker or as part of the speaker.

[0036] The display module (160) can visually provide information to an external party (e.g., a user) of the electronic device (101). The display module (160) may include, for example, a display, a holographic device, or a projector and a control circuit for controlling the device. According to one embodiment, the display module (160) may include a touch sensor configured to detect a touch, or a pressure sensor configured to measure the intensity of a force generated by the touch.

[0037] The audio module (170) can convert sound into an electrical signal, or vice versa, convert an electrical signal into sound. According to one embodiment, the audio module (170) can acquire sound through the input module (150), output sound through the sound output module (155), or an external electronic device (e.g., electronic device (102)) (e.g., speaker or headphone) directly or wirelessly connected to the electronic device (101).

[0038] The sensor module (176) can detect the operating status (e.g., power or temperature) of the electronic device (101) or the external environmental status (e.g., user status) and generate an electrical signal or data value corresponding to the detected status. According to one embodiment, the sensor module (176) can include, for example, a gesture sensor, a gyro sensor, a barometric pressure sensor, a magnetic sensor, an acceleration sensor, a grip sensor, a proximity sensor, a color sensor, an IR (infrared) sensor, a biometric sensor, a temperature sensor, a humidity sensor, or an illuminance sensor.

[0039] The interface (177) may support one or more designated protocols that may be used to directly or wirelessly connect the electronic device (101) with an external electronic device (e.g., the electronic device (102)). In one embodiment, the interface (177) may include, for example, a high definition multimedia interface (HDMI), a universal serial bus (USB) interface, an SD card interface, or an audio interface.

[0040] The connection terminal (178) may include a connector through which the electronic device (101) may be physically connected to an external electronic device (e.g., electronic device (102)). According to one embodiment, the connection terminal (178) may include, for example, an HDMI connector, a USB connector, an SD card connector, or an audio connector (e.g., a headphone connector).

[0041] The haptic module (179) can convert electrical signals into mechanical stimuli (e.g., vibration or movement) or electrical stimuli that a user can perceive through tactile or kinesthetic sensations. According to one embodiment, the haptic module (179) can include, for example, a motor, a piezoelectric element, or an electrical stimulation device.

[0042] The camera module (180) can capture still images and videos. According to one embodiment, the camera module (180) may include one or more lenses, image sensors, image signal processors, or flashes.

[0043] The power management module (188) can manage power supplied to the electronic device (101). According to one embodiment, the power management module (188) can be implemented as, for example, at least a part of a power management integrated circuit (PMIC).

[0044] A battery (189) may power at least one component of the electronic device (101). In one embodiment, the battery (189) may include, for example, a non-rechargeable primary battery, a rechargeable secondary battery, or a fuel cell.

[0045] The communication module (190) may support the establishment of a direct (e.g., wired) communication channel or a wireless communication channel between the electronic device (101) and an external electronic device (e.g., electronic device (102), electronic device (104), or server (108)), and the performance of communication through the established communication channel. The communication module (190) may operate independently from the processor (120) (e.g., application processor) and may include one or more communication processors that support direct (e.g., wired) communication or wireless communication. According to one embodiment, the communication module (190) may include a wireless communication module (192) (e.g., a cellular communication module, a short-range wireless communication module, or a global navigation satellite system (GNSS) communication module) or a wired communication module (194) (e.g., a local area network (LAN) communication module, or a power line communication module). Among these communication modules, the corresponding communication module can communicate with an external electronic device (104) via a first network (198) (e.g., a short-range communication network such as Bluetooth, wireless fidelity (WiFi) direct, or infrared data association (IrDA)) or a second network (199) (e.g., a long-range communication network such as a legacy cellular network, a 5G network, a next-generation communication network, the Internet, or a computer network (e.g., a LAN or WAN)). These various types of communication modules can be integrated into a single component (e.g., a single chip) or implemented as multiple separate components (e.g., multiple chips). The wireless communication module (192) can verify or authenticate the electronic device (101) within a communication network such as the first network (198) or the second network (199) by using subscriber information (e.g., an international mobile subscriber identity (IMSI)) stored in the subscriber identification module (196).

[0046] The wireless communication module (192) can support 5G networks and next-generation communication technologies following the 4G network, such as NR access technology (new radio access technology). The NR access technology can support high-speed transmission of high-capacity data (eMBB (enhanced mobile broadband)), minimization of terminal power and connection of multiple terminals (mMTC (massive machine type communications)), or high reliability and low latency (URLLC (ultra-reliable and low-latency communications)). The wireless communication module (192) can support, for example, a high-frequency band (e.g., mmWave band) to achieve a high data transmission rate. The wireless communication module (192) can support various technologies for securing performance in a high-frequency band, such as beamforming, massive multiple-input and multiple-output (MIMO), full dimensional MIMO (FD-MIMO), array antenna, analog beam-forming, or large scale antenna. The wireless communication module (192) can support various requirements specified in the electronic device (101), an external electronic device (e.g., the electronic device (104)), or a network system (e.g., the second network (199)). According to one embodiment, the wireless communication module (192) can support a peak data rate (e.g., 20 Gbps or more) for eMBB realization, a loss coverage (e.g., 664 dB or less) for mMTC realization, or a U-plane latency (e.g., 0.5 ms or less for downlink (DL) and uplink (UL), or 6 ms or less for round trip) for URLLC realization.

[0047] The antenna module (197) can transmit or receive signals or power to or from an external device (e.g., an external electronic device). In one embodiment, the antenna module (197) may include an antenna including a radiator formed of a conductor or a conductive pattern formed on a substrate (e.g., a PCB). In one embodiment, the antenna module (197) may include a plurality of antennas (e.g., an array antenna). In this case, at least one antenna suitable for a communication method used in a communication network, such as the first network (198) or the second network (199), may be selected from the plurality of antennas, for example, by the communication module (190). A signal or power may be transmitted or received between the communication module (190) and an external electronic device via the at least one selected antenna. In some embodiments, in addition to the radiator, another component (e.g., a radio frequency integrated circuit (RFIC)) may be additionally formed as a part of the antenna module (197).

[0048] According to various embodiments, the antenna module (197) may form a mmWave antenna module. In one embodiment, the mmWave antenna module may include a printed circuit board, an RFIC disposed on or adjacent a first side (e.g., a bottom side) of the printed circuit board and capable of supporting a designated high-frequency band (e.g., a mmWave band), and a plurality of antennas (e.g., an array antenna) disposed on or adjacent a second side (e.g., a top side or a side side) of the printed circuit board and capable of transmitting or receiving signals in the designated high-frequency band.

[0049] At least some of the above components can be interconnected and exchange signals (e.g., commands or data) with each other via a communication method between peripheral devices (e.g., a bus, GPIO (general purpose input and output), SPI (serial peripheral interface), or MIPI (mobile industry processor interface)).

[0050] According to one embodiment, commands or data may be transmitted or received between the electronic device (101) and an external electronic device (104) via a server (108) connected to a second network (199). Each of the external electronic devices (102 or 104) may be the same or a different type of device as the electronic device (101). According to one embodiment, all or part of the operations executed in the electronic device (101) may be executed in one or more of the external electronic devices (102, 104, or 108). For example, when the electronic device (101) is to perform a certain function or service automatically or in response to a request from a user or another device, the electronic device (101) may, instead of or in addition to executing the function or service itself, request one or more external electronic devices to perform the function or at least a part of the service. One or more external electronic devices that receive the request may execute at least a portion of the requested function or service, or an additional function or service related to the request, and transmit the result of the execution to the electronic device (101). The electronic device (101) may process the result as is or additionally and provide it as at least a portion of a response to the request. For this purpose, cloud computing, distributed computing, mobile edge computing (MEC), or client-server computing technology may be used, for example. The electronic device (101) may provide an ultra-low latency service by using distributed computing or mobile edge computing, for example. In another embodiment, the external electronic device (104) may include an Internet of Things (IoT) device. The server (108) may be an intelligent server utilizing machine learning and / or a neural network. According to one embodiment, the external electronic device (104) or the server (108) may be included in the second network (199).The electronic device (101) can be applied to intelligent services (e.g., smart home, smart city, smart car, or healthcare) based on 5G communication technology and IoT-related technology.

[0051] FIG. 2A illustrates an example of a perspective view of a wearable device (200), according to one embodiment. FIG. 2B illustrates an example of one or more hardware elements arranged within a wearable device (200), according to one embodiment.

[0052] The wearable device (200) of FIGS. 2A and 2B may correspond to the electronic device (101) of FIG. 1. As shown in FIG. 2A, the wearable device (200) according to one embodiment may include at least one display (250) and a frame supporting at least one display (250).

[0053] According to one embodiment, the wearable device (200) can be worn on a part of a user's body. The wearable device (200) can provide augmented reality (AR), virtual reality (VR), or mixed reality (MR) that combines augmented reality and virtual reality to the user wearing the wearable device (200). For example, the wearable device (200) can output a virtual reality image to the user through at least one display (250) in response to a designated gesture of the user acquired through the motion recognition camera (240-2) of FIG. 2B.

[0054] According to one embodiment, at least one display (250) within a wearable device (200) may provide visual information to a user. For example, at least one display (250) may include a transparent or translucent lens. At least one display (250) may include a first display (250-1) and / or a second display (250-2) spaced apart from the first display (250-1). For example, the first display (250-1) and the second display (250-2) may be positioned at positions corresponding to the user's left and right eyes, respectively.

[0055] Referring to FIG. 2B, at least one display (250) may form a display area on a lens to provide a user wearing the wearable device (200) with visual information contained in external light passing through the lens, along with other visual information distinct from the visual information. The lens may be formed based on at least one of a Fresnel lens, a pancake lens, or a multi-channel lens. The display area formed by at least one display (250) may be formed on the second surface (232) among the first surface (231) and the second surface (232) of the lens. When the user wears the wearable device (200), external light may be incident on the first surface (231) and transmitted through the second surface (232) to be transmitted to the user. As another example, at least one display (250) may display a virtual reality image to be combined with a real screen transmitted through the external light. The virtual reality image output from at least one display (250) can be transmitted to the user's eyes through one or more hardware (e.g., optical devices (282, 284), and / or at least one waveguide (233, 234)) included in the wearable device (200).

[0056] According to one embodiment, a wearable device (200) may include waveguides (233, 234) that diffract light transmitted from at least one display (250) and relayed by optical devices (282, 284) and transmit the diffracted light to a user. The waveguides (233, 234) may be formed based on at least one of glass, plastic, or polymer. Nanopatterns may be formed on at least a portion of the exterior or interior of the waveguides (233, 234). The nanopatterns may be formed based on a grating structure having a polygonal and / or curved shape. Light incident on one end of the waveguides (233, 234) may be propagated to the other end of the waveguides (233, 234) by the nanopatterns. The waveguides (233, 234) may include at least one diffractive element (e.g., a diffractive optical element (DOE), a holographic optical element (HOE)) and at least one reflective element (e.g., a reflective mirror). For example, the waveguides (233, 234) may be arranged within the wearable device (200) to guide a screen displayed by at least one display (250) to the user's eyes. For example, the screen may be transmitted to the user's eyes based on total internal reflection (TIR) ​​occurring within the waveguides (233, 234).

[0057] According to one embodiment, the wearable device (200) may analyze an object included in a real image collected through a capturing camera (240-1), combine a virtual object corresponding to an object to be provided with augmented reality among the analyzed objects, and display the virtual object on at least one display (250). The virtual object may include at least one of text and an image regarding various information related to the object included in the real image. The wearable device (200) may analyze the object based on a multi-camera, such as a stereo camera. For the object analysis, the wearable device (200) may execute time-of-flight (ToF) and / or simultaneous localization and mapping (SLAM) supported by the multi-camera. A user wearing the wearable device (200) may view an image displayed on at least one display (250).

[0058] According to one embodiment, the frame may be formed as a physical structure that allows the wearable device (200) to be worn on the user's body. According to one embodiment, the frame may be configured so that, when the user wears the wearable device (200), the first display (250-1) and the second display (250-2) can be positioned corresponding to the user's left and right eyes. The frame may support at least one display (250). For example, the frame may support the first display (250-1) and the second display (250-2) to be positioned corresponding to the user's left and right eyes.

[0059] Referring to FIG. 2A, the frame may include a region (220) that at least partially contacts a part of the user's body when the user wears the wearable device (200). For example, the region (220) of the frame that contacts a part of the user's body may include a region that contacts a part of the user's nose, a part of the user's ear, and a part of the side of the user's face that the wearable device (200) makes contact with. According to one embodiment, the frame may include a nose pad (210) that contacts a part of the user's body. When the wearable device (200) is worn by the user, the nose pad (210) may contact a part of the user's nose. The frame may include a first temple (204) and a second temple (205) that contact a part of the user's body that is distinct from the part of the user's body.

[0060] For example, the frame may include a first rim (201) that surrounds at least a portion of the first display (250-1), a second rim (202) that surrounds at least a portion of the second display (250-2), a bridge (203) that is disposed between the first rim (201) and the second rim (202), a first pad (211) that is disposed along a portion of the edge of the first rim (201) from one end of the bridge (203), a second pad (212) that is disposed along a portion of the edge of the second rim (202) from the other end of the bridge (203), a first temple (204) that extends from the first rim (201) and is fixed to a portion of an ear of the wearer, and a second temple (205) that extends from the second rim (202) and is fixed to a portion of an ear opposite the ear. The first pad (211) and the second pad (212) may be in contact with a portion of the user's nose, and the first temple (204) and the second temple (205) may be in contact with a portion of the user's face and a portion of the user's ear. The temples (204, 205) may be rotatably connected to the rim through the hinge units (206, 207) of FIG. 2B. The first temple (204) may be rotatably connected to the first rim (201) through the first hinge unit (206) disposed between the first rim (201) and the first temple (204). The second temple (205) may be rotatably connected to the second rim (202) through the second hinge unit (207) disposed between the second rim (202) and the second temple (205). According to one embodiment, the wearable device (200) can identify an external object (e.g., a user's fingertip) touching the frame and / or a gesture performed by the external object by using a touch sensor, a grip sensor, and / or a proximity sensor formed on at least a portion of a surface of the frame.

[0061] According to one embodiment, the wearable device (200) may include hardwares that perform various functions (e.g., hardwares described above based on the block diagram of FIG. 1). For example, the hardwares may include a battery module (270), an antenna module (275), optical devices (282, 284), speakers (292-1, 292-2), microphones (294-1, 294-2, 294-3), a light-emitting module (not shown), and / or a printed circuit board (290). The various hardwares may be arranged within a frame.

[0062] According to one embodiment, the microphones (294-1, 294-2, 294-3) of the wearable device (200) may be arranged on at least a portion of the frame to acquire a sound signal. A first microphone (294-1) arranged on the nose pad (210), a second microphone (294-2) arranged on the second rim (202), and a third microphone (294-3) arranged on the first rim (201) are illustrated in FIG. 2B, but the number and arrangement of the microphones (294) are not limited to the embodiment of FIG. 2B. When the number of microphones (294) included in the wearable device (200) is two or more, the wearable device (200) may identify the direction of the sound signal by using a plurality of microphones arranged on different portions of the frame.

[0063] According to one embodiment, the optical devices (282, 284) can transmit a virtual object transmitted from at least one display (250) to the wave guides (233, 234). For example, the optical devices (282, 284) can be projectors. The optical devices (282, 284) can be positioned adjacent to at least one display (250) or can be included within at least one display (250) as a part of the at least one display (250). The first optical device (282) can correspond to the first display (250-1), and the second optical device (284) can correspond to the second display (250-2). The first optical device (282) can transmit light output from the first display (250-1) to the first waveguide (233), and the second optical device (284) can transmit light output from the second display (250-2) to the second waveguide (234).

[0064] In one embodiment, the camera (240) may include an eye tracking camera (ET CAM) (240-1), a motion recognition camera (240-2), and / or a recording camera (240-3). The recording camera, the eye tracking camera (240-1), and the motion recognition camera (240-2) may be positioned at different locations on the frame and may perform different functions. The eye tracking camera (240-1) may output data representing the gaze of a user wearing the wearable device (200). For example, the wearable device (200) may detect the gaze from an image including the user's pupils obtained through the eye tracking camera (240-1). An example in which the gaze tracking camera (240-1) is positioned toward the user's right eye is illustrated in FIG. 2B, but the embodiment is not limited thereto, and the gaze tracking camera (240-1) may be positioned solely toward the user's left eye, or may be positioned toward both eyes.

[0065] In one embodiment, the capturing camera (240-3) can capture an actual image or background to be aligned with a virtual image to implement augmented reality or mixed reality content. The capturing camera can capture an image of a specific object existing at a location viewed by the user and provide the image to at least one display (250). The at least one display (250) can display a single image in which information about the actual image or background including the image of the specific object acquired using the capturing camera is superimposed on a virtual image provided through optical devices (282, 284). In one embodiment, the capturing camera can be placed on a bridge (203) disposed between the first rim (201) and the second rim (202).

[0066] In one embodiment, the gaze tracking camera (240-1) can implement more realistic augmented reality by tracking the gaze of a user wearing the wearable device (200) and thereby matching the user's gaze with visual information provided to at least one display (250). For example, when the wearable device (200) looks straight ahead, the wearable device (200) can naturally display environmental information related to the user's front at a location where the user is located on at least one display (250). The gaze tracking camera (240-1) can be configured to capture an image of the user's pupil to determine the user's gaze. For example, the gaze tracking camera (240-1) can receive gaze detection light reflected from the user's pupil and track the user's gaze based on the position and movement of the received gaze detection light. In one embodiment, the gaze tracking camera (240-1) can be positioned at positions corresponding to the user's left and right eyes. For example, the gaze tracking camera (240-1) may be positioned within the first rim (201) and / or the second rim (202) to face the direction in which the user wearing the wearable device (200) is positioned.

[0067] In one embodiment, the gesture recognition camera (240-2) can provide a specific event on a screen provided on at least one display (250) by recognizing the movement of the user's entire body or a part of the user's body, such as the user's torso, hands, or face. The gesture recognition camera (240-2) can recognize the user's gesture, obtain a signal corresponding to the gesture, and provide a display corresponding to the signal on at least one display (250). The processor can identify the signal corresponding to the gesture and perform a designated function based on the identification. In one embodiment, the gesture recognition camera (240-2) can be disposed on the first rim (201) and / or the second rim (202).

[0068] In one embodiment, the camera (240) included in the wearable device (200) is not limited to the gaze tracking camera (240-1) and the motion recognition camera (240-2) described above. For example, the wearable device (200) can identify an external object included in the FoV using the photographing camera (240-3) positioned toward the user's FoV. The wearable device (200) can identify an external object based on a sensor for identifying the distance between the wearable device (200) and the external object, such as a depth sensor and / or a time of flight (ToF) sensor. The camera (240) positioned toward the FoV can support an autofocus function and / or an optical image stabilization (OIS) function. For example, the wearable device (200) may include a camera (240) (e.g., a face tracking (FT) camera) positioned toward the face to obtain an image including the face of a user wearing the wearable device (200).

[0069] Although not shown, in one embodiment, the wearable device (200) may further include a light source (e.g., an LED) that emits light toward a subject (e.g., a user's eyes, face, and / or an external object within the FoV) being photographed using the camera (240). The light source may include an infrared wavelength LED. The light source may be disposed on at least one of the frame and hinge units (206, 207).

[0070] According to one embodiment, the battery module (270) may supply power to electronic components of the wearable device (200). In one embodiment, the battery module (270) may be disposed within the first temple (204) and / or the second temple (205). For example, the battery module (270) may be a plurality of battery modules (270). The plurality of battery modules (270) may be disposed within each of the first temple (204) and the second temple (205). In one embodiment, the battery module (270) may be disposed at an end of the first temple (204) and / or the second temple (205).

[0071] According to one embodiment, the antenna module (275) can transmit signals or power to the outside of the wearable device (200), or receive signals or power from the outside. The antenna module (275) can be electrically and / or operatively connected to the communication module (190) of FIG. 1. In one embodiment, the antenna module (275) can be positioned within the first temple (204) and / or the second temple (205). For example, the antenna module (275) can be positioned close to one surface of the first temple (204) and / or the second temple (205).

[0072] According to one embodiment, the speakers (292-1, 292-2) may output audio signals to the outside of the wearable device (200). The audio output module may be referred to as a speaker. In one embodiment, the speakers (292-1, 292-2) may be positioned within the first temple (204) and / or the second temple (205) so as to be positioned adjacent to the ears of a user wearing the wearable device (200). For example, the wearable device (200) may include a second speaker (292-2) positioned within the first temple (204) and thus adjacent to the user's left ear, and a first speaker (292-1) positioned within the second temple (205) and thus adjacent to the user's right ear.

[0073] In one embodiment, the light-emitting module (not shown) may include at least one light-emitting element. The light-emitting module may emit light of a color corresponding to a specific state or emit light with an action corresponding to a specific state to visually provide information regarding a specific state of the wearable device (200) to the user. For example, when the wearable device (200) requires charging, the wearable device (200) may repeatedly emit red light at a designated time. In one embodiment, the light-emitting module may be disposed on the first rim (201) and / or the second rim (202).

[0074] Referring to FIG. 2B, according to one embodiment, a wearable device (200) may include a printed circuit board (PCB) (290). The PCB (290) may be included in at least one of the first temple (204) and the second temple (205). The PCB (290) may include an interposer disposed between at least two sub-PCBs. One or more hardware components included in the wearable device (200) may be disposed on the PCB (290). The wearable device (200) may include a flexible PCB (FPCB) for interconnecting the hardware components.

[0075] According to one embodiment, a wearable device (200) may include at least one of a gyro sensor, a gravity sensor, and / or an acceleration sensor for detecting a posture of the wearable device (200) and / or a posture of a body part (e.g., a head) of a user wearing the wearable device (200). Each of the gravity sensor and the acceleration sensor may measure gravitational acceleration and / or acceleration based on mutually perpendicular designated three-dimensional axes (e.g., the x-axis, the y-axis, and the z-axis). The gyro sensor may measure an angular velocity of each of the designated three-dimensional axes (e.g., the x-axis, the y-axis, and the z-axis). At least one of the gravity sensor, the acceleration sensor, and the gyro sensor may be referred to as an inertial measurement unit (IMU). According to one embodiment, the wearable device (200) may identify a user's motion and / or gesture performed to execute or stop a specific function of the wearable device (200) based on the IMU.

[0076] FIGS. 3A and 3B illustrate an example of an exterior appearance of a wearable device (300) according to one embodiment. The wearable device (300) of FIGS. 3A and 3B may be included in the electronic device (101) of FIG. 1. An example of an exterior appearance of a first side (310) of a housing of the wearable device (300) according to one embodiment is illustrated in FIG. 3A, and an example of an exterior appearance of a second side (320) opposite to the first side (310) may be illustrated in FIG. 3B.

[0077] Referring to FIG. 3A, according to one embodiment, a first surface (310) of a wearable device (300) may have a form attachable to a body part of a user (e.g., the face of the user). Although not shown, the wearable device (300) may further include a strap for fixing to a body part of a user, and / or one or more temples (e.g., the first temple (204) and / or the second temple (205) of FIGS. 2A and 2B). A first display (350-1) for outputting an image to a left eye among the user's two eyes, and a second display (350-2) for outputting an image to a right eye among the user's two eyes may be disposed on the first surface (310). The wearable device (300) is formed on the first surface (310) and may further include a rubber or silicone packing to prevent interference by light (e.g., ambient light) different from the light emitted from the first display (350-1) and the second display (350-2).

[0078] According to one embodiment, the wearable device (300) may include cameras (340-1, 340-2) for photographing and / or tracking the user's two eyes adjacent to the first display (350-1) and the second display (350-2), respectively. The cameras (340-1, 340-2) may be referred to as ET cameras. According to one embodiment, the wearable device (300) may include cameras (340-3, 340-4) for photographing and / or recognizing the user's face. The cameras (340-3, 340-4) may be referred to as FT cameras.

[0079] Referring to FIG. 3B, a camera (e.g., cameras (340-5, 340-6, 340-7, 340-8, 340-9, 340-10)) and / or a sensor (e.g., depth sensor (330)) for obtaining information related to the external environment of the wearable device (300) may be disposed on a second surface (320) opposite to the first surface (310) of FIG. 3A. For example, the cameras (340-5, 340-6, 340-7, 340-8, 340-9, 340-10) may be disposed on the second surface (320) to recognize an external object different from the wearable device (300). For example, using cameras (340-9, 340-10), the wearable device (300) can obtain images and / or videos to be transmitted to each of the user's eyes. The camera (340-9) can be placed on the second face (320) of the wearable device (300) to obtain an image to be displayed through the second display (350-2) corresponding to the right eye among the two eyes. The camera (340-10) can be placed on the second face (320) of the wearable device (300) to obtain an image to be displayed through the first display (350-1) corresponding to the left eye among the two eyes.

[0080] According to one embodiment, the wearable device (300) may include a depth sensor (330) disposed on the second surface (320) to identify a distance between the wearable device (300) and an external object. Using the depth sensor (330), the wearable device (300) may obtain spatial information (e.g., a depth map) for at least a portion of the FoV of a user wearing the wearable device (300).

[0081] Although not shown, a microphone may be placed on the second side (320) of the wearable device (300) to acquire sound output from an external object. The number of microphones may be one or more depending on the embodiment.

[0082] As described above, according to one embodiment, the wearable device (300) may have a form factor for being worn on a user's head. The wearable device (300), while worn on the head, may provide a user experience based on augmented reality, virtual reality, and / or mixed reality. Using cameras (340-5, 340-6, 340-7, 340-8, 340-9, 340-10) for recording video of an external space, the wearable device (300) and a server connected to the wearable device (300) (e.g., server (110) of FIG. 1) may provide an on-demand service that provides video of a location and / or place selected by the user, and / or a metaverse service.

[0083] According to one embodiment, the wearable device (300) can display frames acquired through cameras (340-9, 340-10) on the first display (350-1) and the second display (350-2), respectively. The wearable device (300) can provide a user with a mixed user experience of real objects and virtual objects (e.g., video see-through (VST)) by combining virtual objects within frames displayed through the first display (350-1) and the second display (350-2) and including real objects. The wearable device (300) can change the virtual objects based on information acquired by the cameras (340-1, 340-2, 340-3, 340-4, 340-5, 340-6, 340-7, 340-8) and / or the depth sensor (330). For example, if a visual object corresponding to a real object and a virtual object at least partially overlap within the frame, the wearable device (300) may stop displaying the virtual object based on detecting a motion for interacting with the real object. By stopping displaying the virtual object, the wearable device (300) may prevent the visibility of the real object from being reduced as the visual object corresponding to the real object is occluded by the virtual object.

[0084] FIG. 4 illustrates an example block diagram of a wearable device (401) according to one embodiment. The wearable device (401) of FIG. 4 may correspond to the electronic device (101) of FIG. 1. The wearable device (401) of FIG. 4 may correspond to the wearable device (200) of FIGS. 2A and 2B. The wearable device (401) of FIG. 4 may correspond to the wearable device (300) of FIGS. 3A and 3B.

[0085] Referring to FIG. 4, a wearable device (401) according to one embodiment may include at least one of a processor (410), a memory (415), a display (420), a camera (425), a sensor (430), or a communication circuit (435). The processor (410) of FIG. 4 may correspond to the processor (120) of FIG. 1. The memory (415) of FIG. 4 may correspond to the memory (130) of FIG. 1. The display (420) of FIG. 4 may correspond to the display module (160) of FIG. 1. The camera (425) of FIG. 4 may correspond to the camera module (180) of FIG. 1. The sensor (430) of FIG. 4 may correspond to the sensor module (176) of FIG. 1. The communication circuit (435) of FIG. 4 may correspond to the communication module (190) of FIG. 1.

[0086] The processor (410), memory (415), display (420), camera (425), sensor (430), and communication circuit (435) may be electrically and / or operably coupled with each other by electronic components such as a communication bus (402). The type and / or number of hardware components included in the wearable device (401) are not limited to those illustrated in FIG. 4. For example, the wearable device (401) may include only some of the hardware components illustrated in FIG. 4. Elements (e.g., layers and / or modules) within the memory described below may be logically separated, but are not limited thereto.

[0087] A processor (410) of a wearable device (401) according to one embodiment may include a hardware component for processing data based on one or more instructions. The hardware component for processing data may include, for example, an arithmetic and logic unit (ALU), a field programmable gate array (FPGA), and / or a central processing unit (CPU). The number of processors (410) may be one or more. For example, the processor (410) may have a multi-core processor structure such as a dual core, a quad core, or a hexa core.

[0088] The memory (415) of the wearable device (401) according to one embodiment may include a hardware component for storing data and / or instructions input and / or output to the processor (410). The memory (415) may include, for example, a volatile memory such as a random-access memory (RAM) and / or a non-volatile memory such as a read-only memory (ROM). The volatile memory may include, for example, at least one of a dynamic RAM (DRAM), a static RAM (SRAM), a cache RAM, and a pseudo SRAM (PSRAM). The non-volatile memory may include, for example, at least one of a programmable ROM (PROM), an erasable PROM (EPROM), an electrically erasable PROM (EEPROM), a flash memory, a hard disk, a compact disc, and an embedded multi media card (eMMC).

[0089] In one embodiment, the display (420) of the wearable device (401) can output visualized information to a user of the wearable device (401). For example, the display (420) can be controlled by a processor (410) including a circuit such as a graphic processing unit (GPU) to output visualized information to the user. The display (420) can include a flat panel display (FPD) and / or electronic paper. The FPD can include a liquid crystal display (LCD), a plasma display panel (PDP), and / or one or more light emitting diodes (LEDs). The LEDs can include organic LEDs (OLEDs).

[0090] In one embodiment, the camera (425) of the wearable device (401) may include one or more optical sensors (e.g., a charged coupled device (CCD) sensor, a complementary metal oxide semiconductor (CMOS) sensor) that generate electrical signals representing the color and / or brightness of light. The plurality of optical sensors included in the camera (425) may be arranged in the form of a two-dimensional array. The camera (425) may acquire electrical signals of each of the plurality of optical sensors substantially simultaneously to generate two-dimensional frame data corresponding to light reaching the optical sensors of the two-dimensional array. For example, photographic data captured using the camera (425) may mean one (a) two-dimensional frame data acquired from the camera (425). For example, video data captured using the camera (425) may mean a sequence of a plurality of two-dimensional frame data acquired from the camera (425) according to a frame rate. The camera (425) may further include a flash light that is positioned toward the direction in which the camera (425) receives light and outputs light toward the direction.

[0091] According to one embodiment, the wearable device (401) may include a plurality of cameras, for example, cameras (425), arranged in different directions. A first camera among the plurality of cameras may be referred to as a motion recognition camera (e.g., motion recognition camera (240-2), motion recognition cameras (340-5, 340-6, 340-7, 340-8, 340-9, 340-10)), and a second camera may be referred to as a gaze tracking camera (e.g., gaze tracking camera (240-1), gaze tracking cameras (340-1, 340-2)). The wearable device (401) may identify a position, shape, and / or gesture of a hand using an image acquired using the first camera. The wearable device (401) may identify a direction of a gaze of a user wearing the wearable device (401) using an image acquired using the second camera. For example, the direction in which the first camera faces and the direction in which the second camera faces may be opposite.

[0092] According to one embodiment, a sensor (430) of a wearable device (401) may generate electrical information that may be processed by a processor (410) and / or a memory (415) of the wearable device (401) from non-electronic information related to the wearable device (401). The information may be referred to as sensor data. The sensor (430) may include a global positioning system (GPS) sensor, an image sensor, an ambient light sensor, and / or a time-of-flight (ToF) sensor for detecting a geographic location of the wearable device (401), and an inertial measurement unit (IMU) for detecting a physical motion of the wearable device (401).

[0093] In one embodiment, the communication circuit (435) of the wearable device (401) may include hardware components for supporting transmission and / or reception of electrical signals between the wearable device (401) and an external electronic device. The communication circuit (435) may include, for example, at least one of a modem (MODEM), an antenna, and an optical / electronic (O / E) converter. The communication circuit (435) may support transmission and / or reception of electrical signals based on various types of protocols, such as Ethernet, a local area network (LAN), a wide area network (WAN), wireless fidelity (WiFi), Bluetooth, Bluetooth low energy (BLE), ZigBee, long term evolution (LTE), 5G NR (new radio), and / or 6G.

[0094] According to one embodiment, one or more instructions (or commands) representing operations and / or actions to be performed on data by a processor (410) of the wearable device (401) may be stored in the memory (415) of the wearable device (401). A set of one or more instructions may be referred to as firmware, an operating system, a process, a routine, a sub-routine, and / or an application. For example, the wearable device (401) and / or the processor (410) may perform at least one of the operations of FIGS. 12 to 14 when a set of a plurality of instructions distributed in the form of an operating system, firmware, a driver, and / or an application is executed. Hereinafter, the fact that an application is installed in a wearable device (401) may mean that one or more instructions provided in the form of an application are stored in a memory (415), and that the one or more applications are stored in a format executable by the processor (410) (e.g., a file having an extension specified by the operating system of the wearable device (401)). As an example, an application may include a program and / or a library related to a service provided to a user.

[0095] Referring to FIG. 4, programs installed in the wearable device (401) may be classified into any one of different layers, including an application layer (440), a framework layer (450), and / or a hardware abstraction layer (HAL) (480), based on the target. For example, programs (e.g., modules or drivers) designed to target the hardware of the wearable device (401) (e.g., the display (420), the camera (420), and / or the sensor (430)) may be classified within the hardware abstraction layer (480). The framework layer (450) may be referred to as an XR framework layer in that it includes one or more programs for providing an XR (extended reality) service. For example, FIG. 4 illustrates layers being divided within the memory (415), the layers may be logically divided. However, the present invention is not limited thereto. Depending on the embodiment, the layers may be stored in a designated area within the memory (415).

[0096] For example, within the framework layer (450), programs designed to target at least one of the hardware abstraction layer (480) and / or the application layer (440) (e.g., a position tracker (471), a space recognizer (472), a gesture tracker (473), and / or an eye tracker (474), a face tracker (475)) may be classified. Programs classified within the framework layer (450) may provide an executable API (application programming interface) based on other programs.

[0097] For example, within the application layer (440), programs designed to target users controlling wearable devices (401) may be classified. Examples of programs classified into the application layer (440) include, but are not limited to, an XR (extended reality) system UI (user interface) and / or an XR application (442). For example, programs (e.g., software applications) classified into the application layer (440) may call an API (application programming interface) to cause execution of functions supported by programs classified into the framework layer (450).

[0098] For example, the wearable device (401) may display one or more visual objects on the display (420) for performing interaction with a user for using a virtual space based on the execution of the XR system UI (441). A visual object may refer to an object that can be deployed within a screen for transmitting and / or interacting with information, such as text, an image, an icon, a video, a button, a checkbox, a radio button, a text box, a slider, and / or a table. A visual object may be referred to as a visual guide, a virtual object, a visual element, a UI element, a view object, and / or a view element. The wearable device (401) may provide a service for controlling functions available within a virtual space to the user based on the execution of the XR system UI (441).

[0099] Referring to FIG. 4, a lightweight renderer (443) and / or an XR plug-in (444) are illustrated as being included within the XR system UI (441), but are not limited thereto. For example, the XR system UI (441) may cause execution of functions supported by the lightweight renderer (443) and / or the XR plug-in (444) included within the framework layer (450).

[0100] For example, the wearable device (401) may obtain resources (e.g., APIs, system processes, and / or libraries) used to define, create, and / or execute a rendering pipeline that allows partial changes based on the execution of a lightweight renderer (442). The lightweight renderer (443) may be referred to as a lightweight render pipeline in terms of defining a rendering pipeline that allows partial changes. The lightweight renderer (443) may include a renderer that is built prior to the execution of a software application (e.g., a prebuilt renderer). For example, the wearable device (401) may obtain resources (e.g., APIs, system processes, and / or libraries) used to define, create, and / or execute an entire rendering pipeline based on the execution of an XR plug-in (444). The XR plugin (444) may be referred to as an open XR native client from the perspective of defining (or configuring) the entire rendering pipeline.

[0101] For example, the wearable device (401) may display a screen representing at least a portion of a virtual space on the display (420) based on the execution of the XR application (442). The XR plug-in (444-1) included in the XR application (442) may be referenced by the XR plug-in (444) of the XR system UI (441). Any description of the XR plug-in (444-1) that overlaps with the description of the XR plug-in (444) may be omitted. The wearable device (401) may cause the execution of the virtual space manager (451) based on the execution of the XR application (442).

[0102] According to one embodiment, the wearable device (101) may provide a virtual space service based on the execution of the virtual space manager (451). For example, the virtual space manager (451) may include a platform (e.g., an Android platform) for supporting the virtual space service. The wearable device (401) may display the posture of a virtual object representing the user's posture rendered using data acquired through the sensor (430) on the display based on the execution of the virtual space manager (451). The virtual space manager (451) may be referred to as a composition presentation manager (CPM).

[0103] For example, the virtual space manager (451) may include a runtime service (452). As an example, the runtime service (452) may be referred to as an OpenXR runtime module. The wearable device (401) may be used to provide at least one of a pose prediction function, a frame timing function, and / or a spatial input function to a user through the wearable device (401) based on the execution of the runtime service (452). As an example, the wearable device (401) may be used to perform rendering for a virtual space service to a user based on the execution of the runtime service (452). For example, an application (e.g., unity or an OpenXR native application) may be implemented based on the execution of the runtime service (452).

[0104] For example, the virtual space manager (451) may include a pass-through manager (453). Based on the execution of the pass-through manager (453), the wearable device (401) may display a screen representing a virtual space on the display (420), while superimposing another screen representing an actual space acquired through the camera (425) on at least a portion of the screen.

[0105] For example, the virtual space manager (451) may include an input manager (454). The wearable device (401) may identify data (e.g., sensor data) acquired by executing one or more programs included in the recognition service layer (470) based on the execution of the input manager (454). The wearable device (401) may initiate execution of at least one of the functions of the wearable device (401) using the acquired data.

[0106] For example, the perception abstract layer (460) can be used for data exchange between the virtual space manager (451) and the perception service layer (470). From the perspective of being used for data exchange between the virtual space manager (451) and the perception service layer (470), the perception abstract layer (460) can be referred to as an interface. For example, the perception abstract layer (460) can be referenced as OpenPX. The perception abstract layer (460) can be used for a perception client and a perception service.

[0107] According to one embodiment, the recognition service layer (470) may include one or more programs for processing data acquired from a sensor (430) (or a camera (425)). The one or more programs may include at least one of a position tracker (471), a space recognizer (472), a gesture tracker (473), an eye tracker (474), and / or a face tracker (473). The type and / or number of the one or more programs included in the recognition service layer (470) are not limited to those illustrated in FIG. 4.

[0108] For example, the wearable device (401) can identify the pose of the wearable device (401) using the sensor (430) based on the execution of the position tracker (471). The wearable device (401) can identify the 6 degrees of freedom pose (6 dof pose) of the wearable device (401) using data acquired using the camera (425) and the IMU based on the execution of the position tracker (471). The position tracker (471) can be referred to as a head tracking (HeT) module.

[0109] For example, the wearable device (401) may be used to construct a three-dimensional virtual space around the wearable device (401) (or a user of the wearable device (401)) based on the execution of the space recognizer (472). The wearable device (401) may reconstruct the three-dimensional surroundings of the wearable device (401) using data acquired using the camera (425) based on the execution of the space recognizer (472). The wearable device (401) may identify at least one of a plane, a slope, and stairs based on the three-dimensionally reconstructed surroundings of the wearable device (401) based on the execution of the space recognizer (472). The space recognizer (472) may be referred to as a scene understanding (SU) module.

[0110] For example, the wearable device (401) may be used to identify (or recognize) a pose and / or gesture of a hand of a user of the wearable device (401) based on the execution of the gesture tracker (473). As an example, the wearable device (401) may identify a pose and / or gesture of a hand of a user using data acquired from a sensor (430) and / or a camera (425) based on the execution of the gesture tracker (473). As an example, the wearable device (401) may identify a pose and / or gesture of a hand of a user based on data (or images) acquired using a camera based on the execution of the gesture tracker (473). The gesture tracker (473) may be referred to as a hand tracking (HaT) module and / or a gesture tracking module.

[0111] For example, the wearable device (401) can identify (or track) eye movements of a user of the wearable device (401) based on the execution of the gaze tracker (474). As an example, the wearable device (401) can identify eye movements of the user using data acquired from at least one sensor based on the execution of the gaze tracker (474). As an example, the wearable device (401) can identify eye movements of the user based on data acquired using a camera (e.g., the gaze tracking camera (260-1) of FIGS. 2A and 2B) and / or an infrared light emitting diode (IR LED) based on the execution of the gaze tracker (474). The gaze tracker (474) may be referred to as an eye tracking (ET) module and / or a gaze tracking module.

[0112] For example, the recognition service layer (470) of the wearable device (401) may further include a face tracker (475) for tracking the user's face. For example, the wearable device (103) may identify (or track) the movement of the user's face and / or the user's expression based on the execution of the face tracker (475). The wearable device (401) may estimate the user's expression based on the movement of the user's face based on the execution of the face tracker (475). As an example, the wearable device (401) may identify the movement of the user's face and / or the user's expression based on data (e.g., an image) acquired using a camera based on the execution of the face tracker (475).

[0113] FIG. 5A illustrates an exemplary wearable device according to an embodiment. FIG. 5B illustrates a cross-section of an exemplary wearable device according to an embodiment. FIG. 5C is a block diagram of an exemplary wearable device according to an embodiment. FIG. 5D is a state transition diagram of an exemplary wearable device according to an embodiment.

[0114] The wearable device (401) of FIG. 5C may correspond to the wearable device (401) of FIG. 4. The processor (410) of FIG. 5C may correspond to the processor (410) of FIG. 4. The memory (415) of FIG. 5C may correspond to the memory (415) of FIG. 4. The display (420) of FIG. 5C may correspond to the display (420) of FIG. 4. The camera (425) of FIG. 5C may correspond to the camera (425) of FIG. 4. The communication circuit (435) of FIG. 5C may correspond to the communication circuit (435) of FIG. 4.

[0115] Referring to FIGS. 5A and 5B , according to one embodiment, a wearable device (501) may be configured to be wearable by a user. For example, the wearable device (501) may have a ring shape provided with a hole (515) through which a user may insert a body (or a part of the body) (500) (e.g., a finger). However, the present invention is not limited thereto, and the wearable device (501) may have various shapes corresponding to the body in order to be worn on the body of a user.

[0116] In one embodiment, the wearable device (501) may include a housing (510).

[0117] Referring to FIG. 5A, the housing (510) may form an exterior of the wearable device (501). For example, the housing (510) may form or define a first side (510A), a second side (510B), and a third side (510C). When a user wears the wearable device (501), the first side (510A) may surround the user's body so as to face the user's body (500). The first side (510A) may at least partially contact the user's body (500). The second side (510B) may be spaced apart from the first side (510A) and may face in an opposite direction to the first side (510A). The third side (510C) may surround a space between the first side (510A) and the second side (510B). For example, the third side (510C) may extend from the edge of the first side (510A) to the edge of the second side (510B). The housing (510) may be formed with a hole (515) defined by the first side (510A) to accommodate a user's body (500). The first side (510A) may be referred to as the inner surface, and the second side (510B) may be referred to as the outer surface.

[0118] Referring to FIG. 5B, the wearable device (501) may include at least one light emitting unit (522, 524, 526) and at least one light receiving unit (523, 525, 527). In one embodiment, the wearable device (501) may include a substrate (528). In one embodiment, the wearable device (501) may include a processor (520), a controller (529), a memory (530), a temperature sensor (570), a motion sensor (573), a pressure sensor (575), an external temperature sensor (577), a lens (579), a battery (580), a power management module (583), a charging interface (585), a communication circuit (590), and an antenna (597).

[0119] In one embodiment, the substrate (528) may comprise a flexible printed circuit board or a rigid-flex printed circuit board. In one embodiment, the substrate (528) may be at least partially bendable. For example, the substrate (528) may comprise a bent portion to correspond to the curvature of the first surface (510A) having a ring shape.

[0120] In one embodiment, the processor (520) may correspond to the processor (120) of FIG. 1. In one embodiment, the controller (529) may be included in the sensor module (176) of FIG. 1. In one embodiment, the memory (530) may correspond to the memory (130) of FIG. 1. In one embodiment, each of at least one light emitting unit (522, 524, 526), ​​at least one light receiving unit (523, 525, 527), a temperature sensor (570), a motion sensor (573), a pressure sensor (575), and an external temperature sensor (577) may correspond to the sensor module (176) of FIG. 1. In one embodiment, the battery (580) may correspond to the battery (189) of FIG. 1. In one embodiment, the power management module (583) may correspond to the power management module (188) of FIG. 1. In one embodiment, the communication circuit (590) may correspond to the communication module (190) of FIG. 1. In one embodiment, the antenna (597) may correspond to the antenna module (197) of FIG. 1. In one embodiment, the charging interface (585) may include a wired and / or wireless interface circuit for supplying power from an external power source for charging the battery (580).

[0121] In one embodiment, at least one of the light emitters (522, 524, 526) and at least one light receiver (523, 525, 527) may also be referred to as a photoplethysmography (PPG) sensor, but is not limited thereto. In one embodiment, at least one of the light emitters (522, 524, 526) and at least one light receiver (523, 525, 527) may also be referred to as a proximity sensor.

[0122] In one embodiment, at least one light emitter (522, 524, 526) and at least one light receiver (523, 525, 527) may be disposed on a substrate (528). For example, at least one light emitter (522, 524, 526) may be disposed on the substrate (528) so as to face the first surface (510A). For example, at least one light receiver (523, 525, 527) may be disposed on the substrate (528) so as to face the first surface (510A).

[0123] In one embodiment, the motion sensor (573) may include an acceleration sensor and / or a gyro sensor. For example, the motion sensor (573) may be a three-axis sensor (e.g., an acceleration sensor). For example, the motion sensor (573) may be a six-axis sensor (e.g., an acceleration sensor and a gyro sensor).

[0124] In one embodiment, the motion sensor (573) may include at least one of a gyro sensor, a gravity sensor, and / or an acceleration sensor for detecting a posture of the wearable device (501) and / or a movement of the wearable device (501). Each of the gravity sensor and the acceleration sensor may measure gravitational acceleration and / or acceleration based on mutually perpendicular designated three-dimensional axes (e.g., x-axis, y-axis, and z-axis). The gyro sensor may measure an angular velocity of each of the designated three-dimensional axes (e.g., x-axis, y-axis, and z-axis). At least one of the gravity sensor, the acceleration sensor, and the gyro sensor may be referred to as an inertial measurement unit (IMU).

[0125] In one embodiment, the pressure sensor (575) may be positioned on the substrate (528) so as to face the first surface (510A). In one embodiment, the pressure sensor (575) may measure a pressure value applied to at least a portion of the first surface (510A).

[0126] In one embodiment, an external temperature sensor (577) may be disposed on the substrate (528) so as to face the second surface (510B). The external temperature sensor (577) may measure the temperature of a temperature measurement target based on infrared rays emitted by the temperature measurement target. In one embodiment, a lens (579) may be provided to transmit infrared rays so that the infrared rays emitted by the temperature measurement target can be received by the external temperature sensor (577). The lens (579) may be disposed so as to face the second surface (510B).

[0127] Referring to FIG. 5c, the wearable device (501) may include a processor (520), a memory (530), a motion sensor (573), and a communication circuit (590).

[0128] The wearable device (501) may correspond to the electronic device (102) of FIG. 1, but is not limited thereto. For example, the wearable device (501) may correspond to the electronic device (101) of FIG. 1. The processor (520) of FIG. 5C may correspond to the processor (520) of FIG. 5B. The memory (530) of FIG. 5C may correspond to the memory (530) of FIG. 5B. The motion sensor (573) of FIG. 5C may correspond to the motion sensor (573) of FIG. 5B. The communication circuit (590) of FIG. 5C may correspond to the communication circuit (590) of FIG. 5B.

[0129] In one embodiment, the processor (520) may establish a communication connection with a wearable device (401) via a communication circuit (590). Here, the wearable device (401) may be a device of various forms. For example, the wearable device (401) may be AR glasses and / or a head-mounted device (HMD). For example, the wearable device (401) may be a portable communication device (e.g., a smartphone), a computer device, a portable multimedia device, a portable medical device, a camera, a wearable device (e.g., a watch), or a home appliance device.

[0130] In one embodiment, the processor (520) may receive a request for motion data from the wearable device (401) via the communication circuit (590). Here, the motion data may include gravitational acceleration, acceleration, and / or angular velocity about each of designated three-dimensional axes (e.g., the x-axis, the y-axis, and the z-axis) that are perpendicular to each other, obtained via the motion sensor (573).

[0131] In one embodiment, the processor (520) may transmit movement data to the wearable device (401) via the communication circuit (590). In one embodiment, the processor (520) may transmit movement data to the wearable device (401) in response to a request for movement data from the wearable device (401).

[0132] In one embodiment, the wearable device (401) can identify a gesture of a user (500) within a field of view (FOV) of the camera (425) identified through the camera (425). In one embodiment, the wearable device (401) can identify a gesture of the user (500) based on movement data from the wearable device (501).

[0133] Referring to FIG. 5D, the wearable device (501) may have one of a plurality of states (591, 593, 595). The wearable device (501) may have one of a normal state (591), a low power state (593), or an ultra-low power state (595).

[0134] The wearable device (501) can transition from one of a plurality of states (591, 593, 595) to another state. For example, the wearable device (501) can transition from a normal state (591) to a low power state (593) or an ultra-low power state (595). For example, the wearable device (501) can transition from a low power state (593) to a normal state (591) or an ultra-low power state (595). For example, the wearable device (501) can transition from an ultra-low power state (595) to a normal state (591) or a low power state (593).

[0135] In one embodiment, in the normal state (591), at least some of the components of the wearable device (501) may be active. For example, in the normal state (591), the processor (520), the motion sensor (573), and the communication circuit (590) may be active. For example, in the normal state (591), the processor (520) may process motion data through the motion sensor (573). For example, in the normal state (591), the processor (520) may obtain data from the communication circuit (590) and / or transmit data to the communication circuit (590). For example, in the normal state (591), the motion sensor (573) may obtain motion data. For example, in the normal state (591), the communication circuit (590) may be communicatively connected with the communication circuit (435) of the wearable device (401). For example, in a normal state (591), the communication circuit (590) can transmit and receive data packets and / or control packets in an allocated time slot through a communication connection with the communication circuit (435). For example, in a normal state (591), the communication circuit (590) can periodically receive a synchronization signal through a communication channel with the communication circuit (435) for synchronization with the communication circuit (435).

[0136] In one embodiment, in the low power state (593), at least some of the components of the wearable device (501) may be inactive. For example, in the low power state (593), the processor (520) and the motion sensor (573) may be inactive. For example, in the low power state (593), the processor (520) may not process motion data through the motion sensor (573). Here, not processing motion data may include that the processor (520) does not obtain motion data from the motion sensor (573). For example, in the low power state (593), the processor (520) may not obtain data from the communication circuit (590). For example, in the low power state (593), the processor (520) may not transmit data to the communication circuit (590). For example, in a low power state (593), the motion sensor (573) may not acquire movement data.

[0137] In one embodiment, in the low power state (593), the communication circuit (590) may be in a sleep state. For example, in the low power state (593), the communication circuit (590) may be in a state where a communication connection with the communication circuit (435) of the wearable device (401) is established. For example, in the low power state (593), the communication circuit (590) may not exchange data packets and / or control packets with the communication circuit (435) of the wearable device (401) through the communication connection. In one embodiment, in the low power state (593), the communication circuit (590) may transition from the sleep state to the active state by a wake-up signal from the communication circuit (435).

[0138] In one embodiment, the ultra-low power state (595) may be a state in which components of the wearable device (501) are inactive. For example, in the ultra-low power state (595), the processor (520), the motion sensor (573), and the communication circuit (590) may be inactive. For example, in the ultra-low power state (595), the communication circuit (590) may not be in a communication connection with the communication circuit (435) of the wearable device (401). For example, in the ultra-low power state (595), the communication circuit (590) may be in a standby state. For example, in the standby state, the communication circuit (590) may not transmit or receive data. In one embodiment, in the ultra-low power state (595), the communication circuit (590) can pair with (or establish a communication connection with) the communication circuit (435) based on a pairing request (or a communication connection request) from the communication circuit (435). In one embodiment, in the ultra-low power state (595), the communication circuit (590) can transition from a standby state to a sleep state (or an active state) after pairing with (or establishing a communication connection with) the communication circuit (435).

[0139] In one embodiment, the wearable device (401) may determine whether to request movement data from the wearable device (501) based on the state of the wearable device (401) and / or the state of the wearable device (501). Hereinafter, with reference to FIGS. 6b, 6c, 7a, 7b, 8, 9, 10, and 11, an operation of the wearable device (401) determining whether to request movement data from the wearable device (501) based on the state of the wearable device (401) and / or the state of the wearable device (501) will be described.

[0140] FIG. 6A illustrates an example (601) of a field of view (FOV, 600) acquired through a camera (425) of a wearable device (401) worn by a user (500) in one embodiment.

[0141] The wearable device (401) of FIG. 6A may correspond to the electronic device (101) of FIG. 1. The wearable device (401) of FIG. 6A may correspond to the wearable device (200) of FIGS. 2A and 2B. The wearable device (401) of FIG. 6A may correspond to the wearable device (300) of FIGS. 3A and 3B. The wearable device (401) of FIG. 6A may correspond to the wearable device (401) of FIG. 4. The wearable device (501) of FIG. 6A may correspond to the wearable devices (501) of FIGS. 5A, 5B, and 5C. FIG. 6a can be explained with reference to FIG. 1, FIG. 2a, FIG. 2b, FIG. 3a, FIG. 3b, FIG. 4, FIG. 5a, FIG. 5b, FIG. 5c, and FIG. 5d.

[0142] Referring to FIG. 6A, a user (500) may wear a wearable device (401). In one embodiment, the wearable device (401) may obtain an image of a field of view (600) of the camera (425) through the camera (425). In one embodiment, the wearable device (401) may obtain an image representing an actual space obtained through the camera (425) (or, the front cameras (240-3, 340-9, 340-10)). In one embodiment, the wearable device (401) may obtain an image representing a space in front of the user (500) through the camera (425).

[0143] In one embodiment, an image representing a space in front of a user (500) obtained through a camera (425) may be displayed through a display (420). For example, a wearable device (401) may display an image representing a space in front of a user (500) obtained through a camera (425) through a display (420) to provide a video see through (VST) and / or pass-through environment to a user (500) wearing the wearable device (401). For example, a wearable device (401) may display an image representing a space in front of a user (500) obtained through a camera (425) through a display (420) to provide an augmented reality (AR) or a mixed reality (MR) that combines augmented reality and virtual reality (VR) to a user (500) wearing the wearable device (401). However, this is not limited thereto. In one embodiment, an image representing the space in front of the user (500) obtained through the camera (425) may not be displayed through the display (420). For example, the wearable device (401) may display a screen that is not related to the space in front of the user (500) through the display (420). For example, the wearable device (401) may display a screen generated by a program (140) running on the processor (410) through the display (420) to provide virtual reality (VR) that is not related to the space in front of the user (500).

[0144] In one embodiment, the wearable device (401) may recognize one or more objects around the wearable device (401) based on an image acquired through the camera (425). Here, object recognition may include an operation for identifying one or more objects within a field of view (600) of the wearable device (401). Object recognition may include an operation for identifying objects included in an image acquired through the camera (425) (e.g., a red, green, and blue (RGB) camera, a stereo camera, a time of flight (TOF) camera (or, a depth camera)) and classifying the identified objects as objects with similar patterns.

[0145] In one embodiment, the environment surrounding the wearable device (401) can be recognized. Here, the environment recognition (scene understanding, SU) may include an operation to construct the environment surrounding the wearable device (401) (or, the user (500) of the wearable device (401)) into a three-dimensional virtual space. The environment recognition may include an operation to reconstruct the environment surrounding the wearable device (401) in three dimensions using an image acquired using a camera (425) (e.g., an RGB camera, a stereo camera, and / or a LiDAR (light detection and ranging) sensor).

[0146] In one embodiment, the wearable device (401) can identify one or more objects (501, 611) within the field of view (600) of the camera (425). In one embodiment, the wearable device (401) can identify one or more objects (501, 611) within the field of view (600) of the camera (425) based on object recognition and / or environment recognition. In one embodiment, the one or more objects (501, 611) may include the wearable device (501). In one embodiment, the one or more objects (501, 611) may include a hand (611) of a user (500). In one embodiment, the hand (611) may be a hand of a user (500) wearing the wearable device (501), but is not limited thereto. The hand (611) may be the hand of a user (500) who is not wearing the wearable device (501) or the hand of a person other than the user (500).

[0147] In one embodiment, the wearable device (401) may provide a guide for moving the hand (611) of the user (500) into the field of view (600) when the hand (611) of the user (500) is not identified in the field of view (600) of the camera (425). For example, the wearable device (401) may display a guide for moving the hand (611) of the user (500) into the field of view (600) through the display (420) when the hand (611) of the user (500) is not identified in the field of view (600) of the camera (425). However, the present invention is not limited thereto.

[0148] In one embodiment, the wearable device (401) may provide a guide for wearing the wearable device (501) on the hand (611) of the user (500) when the wearable device (501) is not identified in the field of view (600) of the camera (425). For example, the wearable device (401) may display a guide for wearing the wearable device (501) on the hand (611) of the user (500) through the display (420) when the wearable device (501) is not identified in the field of view (600) of the camera (425). However, the present invention is not limited thereto.

[0149] In one embodiment, the wearable device (401) can identify the movement (or movement trajectory) of the hand (611). In one embodiment, the wearable device (401) can identify the movement of the hand (611) within the field of view (600) of the camera (425). In one embodiment, the wearable device (401) can identify the relative movement of the hand (611). Here, the relative movement may include the direct movement of the hand (611), the movement of the hand (611) relative to the field of view (600) due to the movement of the wearable device (401), and / or the movement of the hand (611) relative to an object due to the movement of the object within the field of view (600). In one embodiment, the movement of the hand (611) may be identified based on the direction of movement and / or the speed of movement of the hand (611). In one embodiment, relative hand (611) movement can be identified based on the relative movement direction and / or relative movement speed of the hand (611) relative to any target (e.g., field of view (600), and / or object).

[0150] Hereinafter, with reference to FIGS. 6a, 6b, 6c, 7a, 7b, 8, 9, 10, and 11, an operation of determining whether or not to request movement data from a wearable device (401) to a wearable device (501) will be described.

[0151] FIG. 6b illustrates an example of a situation (602) in which a user wearing a wearable device moves his / her hand in one embodiment.

[0152] The wearable device (401) of FIG. 6B may correspond to the electronic device (101) of FIG. 1. The wearable device (401) of FIG. 6B may correspond to the wearable device (200) of FIGS. 2A and 2B. The wearable device (401) of FIG. 6B may correspond to the wearable device (300) of FIGS. 3A and 3B. The wearable device (401) of FIG. 6B may correspond to the wearable device (401) of FIG. 4. The wearable device (501) of FIG. 6B may correspond to the wearable devices (501) of FIGS. 5A, 5B, and 5C. FIG. 6b can be explained with reference to FIG. 1, FIG. 2a, FIG. 2b, FIG. 3a, FIG. 3b, FIG. 4, FIG. 5a, FIG. 5b, FIG. 5c, and FIG. 5d.

[0153] Compared to FIG. 6a, FIG. 6b can illustrate the field of view (600) of the camera (425) from three dimensions to two dimensions.

[0154] In one embodiment, the wearable device (401) may be in a state in which a communication connection is established (or a paired state) with the wearable device (501). In one embodiment, the wearable device (401) may be in a state in which a communication connection is established (or a paired state) with the wearable device (501) based on the results of object recognition and / or environment recognition. For example, the wearable device (401) may establish a communication connection with the wearable device (501) based on the number of objects that interfere with the identification of the hand (611) in the field of view (600) or the probability of interference. For example, the wearable device (401) may establish a communication connection with the wearable device (501) based on the number of objects that interfere with the identification of the hand (611) in the field of view (600) being greater than or equal to a specified number or the probability of interference being greater than or equal to a specified probability. In one embodiment, the probability of obstruction may be determined based on an artificial intelligence model trained to calculate the probability of obstruction based on the type of object. In one embodiment, the artificial intelligence model may be reinforcement learned to calculate an updated probability of obstruction based on whether the wearable device (401) is actually obscured by the movement of the hand (611) of the user (500). However, the present invention is not limited thereto. In one embodiment, the probability of obstruction may be determined based on an artificial intelligence model trained to calculate the probability of obstruction based on the distance between the object and the hand (611) and / or the placement of the object within the field of view (600).

[0155] In one embodiment, the wearable device (401) may be in a state of establishing a communication connection (or, a paired state) with the wearable device (501) based on the type of the running application (146). For example, the wearable device (401) may establish a communication connection with the wearable device (501) based on the type of the running application (146) requiring gesture input (e.g., a game application). In one embodiment, the wearable device (501) may be operating in a low power state (593). In one embodiment, the wearable device (501) may transition from an ultra low power state (595) to a low power state (593). In one embodiment, the wearable device (401) may be in a state of establishing a communication connection (or a paired state) with the wearable device (501) based on the state of charge (SOC) of the battery (580) of the wearable device (501). For example, the wearable device (401) may establish a communication connection with the wearable device (501) based on the state of charge of the battery (580) of the wearable device (501) being equal to or greater than a specified first state of charge (e.g., 60%).

[0156] Referring to FIG. 6B, the wearable device (401) can acquire an image for a field of view (600) of the camera (425) through the camera (425). In one embodiment, the wearable device (401) can perform object recognition and / or environment recognition based on the image acquired through the camera (425). In one embodiment, the wearable device (401) can identify one or more objects (501, 611, 620) within the field of view (600) of the camera (425) based on the object recognition and / or environment recognition.

[0157] In one embodiment, the wearable device (401) can identify one or more obstruction areas (620, 630). In one embodiment, the obstruction area (620, 625) may be an area where the hand (611) (or finger) is not identified through the field of view (600) of the camera (425). For example, the obstruction area (620) may be an area of ​​an obstruction object (e.g., a desk) that may obscure the hand (611) (or finger) as the hand (611) (or finger) moves among the objects within the field of view (600). For example, the obstruction area (625) may be an area outside the field of view (600). Here, the fact that an obstructing object (e.g., a desk) covers the hand (611) (or finger) may mean that the obstructing object (e.g., a desk) is located between the hand (611) (or finger) and the camera (425).

[0158] In one embodiment, the wearable device (401) can identify the movement (or movement trajectory) of the hand (611). In one embodiment, the wearable device (401) can identify the movement of the hand (611) within the field of view (600) of the camera (425). In one embodiment, the wearable device (401) can identify the relative movement of the hand (611). Here, the relative movement may include direct movement of the hand (611), movement of the hand (611) relative to the field of view (600) due to movement of the wearable device (401), and / or movement of the hand (611) relative to an object due to movement of the object within the field of view (600). Hereinafter, the movement of the hand (611) and the relative movement of the hand (611) may be referred to as movement of the hand (611).

[0159] In one embodiment, the wearable device (401) can identify (or set) a distance based on the movement of the hand (611). In one embodiment, the wearable device (401) can identify a distance from an interference area (620, 625) based on the movement of the hand (611). In one embodiment, the wearable device (401) can identify a distance that the hand (611) can reach within a first time specified in the interference area (620, 625) based on the movement of the hand (611). In one embodiment, the wearable device (401) can set a distance from each of the interference areas (620, 625) based on locations that can be reached within a time specified in the interference area (620, 625) based on a movement direction and / or movement speed of the hand (611). Hereinafter, a distance that the hand (611) can reach within a first time period specified in the interference area (620, 625) according to the movement of the hand (611) may be referred to as a first distance. In one embodiment, the first time period may be determined based on a processing delay time. In one embodiment, the first time period may be determined based on a time required for the wearable device (501) to transmit movement data to the wearable device (401). For example, the first time period may include a delay time due to a network between the wearable device (401) and the wearable device (501). For example, the first time period may include a delay time for processing movement data of the wearable device (401) and / or the wearable device (501). For example, the first time period may include a delay time due to a network and a delay time for processing movement data. For example, the first time period may be greater than or equal to a time period including a delay time due to a network and a delay time for processing movement data. Here, the delay due to the network may include a delay due to data transmission and reception between the wearable device (401) and the wearable device (501).The delay due to the network may include a delay for interworking between one or more processors included in the processor (221) of the wearable device (401) for distributed processing among the processors. In one embodiment, the delay due to the network may be identified based on network status and throughput information of the network between the wearable device (401) and the wearable device (501). Here, the delay for processing data may include a delay due to resource occupation by one or more tasks of the processor (410) of the wearable device (401). The delay for processing data may include a delay due to resource occupation by one or more tasks of the processor (520) of the wearable device (501). In one embodiment, the delay for processing data may be based on the time taken through an operation flow for recognizing a gesture based on movement data in the wearable device (401). For example, the motion flow may include an operation of acquiring an image for a field of view (600) of a camera (425), an operation of identifying a movement of a hand (611) in the image, and an operation of identifying a gesture based on the movement of the hand (611). For example, the motion flow may include an operation of the wearable device (501) acquiring movement data through a motion sensor (573), an operation of the wearable device (501) transmitting the movement data to the wearable device (401), an operation of the wearable device (401) identifying a movement of the wearable device (501) based on the movement data, and an operation of identifying a gesture based on the movement of the wearable device (501). Accordingly, the first time may further include a difference between a time taken to process a gesture based on movement data and a time taken to process a gesture identified through the camera (425).

[0160] In one embodiment, the wearable device (401) may set the first distance to be longer as the movement speed of the hand (611) is higher. In one embodiment, the wearable device (401) may set the first distance to be shorter as the movement speed of the hand (611) is lower. In one embodiment, the wearable device (401) may set the first distance to a value obtained by multiplying the movement speed of the hand (611) by a specified first time. For example, the wearable device (401) may set the first distance to a value obtained by multiplying the relative movement speed of the hand (611) to each of the obstructing objects by a specified first time. For example, the wearable device (401) may set the first distance to a value obtained by multiplying the relative movement speed of the hand (611) to each of the obstructing objects by a specified first time. In one embodiment, the wearable device (401) can set different first distances for each of the obstruction areas of the obstructing objects based on the relative movement speed of the hand (611).

[0161] In one embodiment, the wearable device (401) may set one or more regions (630, 635) based on a first distance. In one embodiment, each of the one or more regions (630, 635) may be a region within a first distance from each of the interference regions (620, 625). In one embodiment, the region within the first distance from the interference region may be a wake-up region. In one embodiment, the region within the first distance from the interference region may be a transmission initiation region. Hereinafter, the region within the first distance from the interference region may be referred to as a wake-up region.

[0162] In one embodiment, the wearable device (401) can identify that the hand (611) has entered one of the one or more wake-up zones (630, 635). In one embodiment, the wearable device (401) can transmit a wake-up signal to the wearable device (501) worn on the hand (611) in response to identifying that the hand (611) has entered the wake-up zone (630, 635). In one embodiment, the wearable device (501) can receive the wake-up signal via the communication circuit (590). In one embodiment, the wearable device (501) can transition from a low power state (593) to a normal state (591) in response to receiving the wake-up signal. In one embodiment, the communication circuit (590) of the wearable device (501) may transition from a sleep state to an active state in response to receiving a wake-up signal. In one embodiment, as the wearable device (501) transitions from a low power state (593) to a normal state (591), the processor (520), the motion sensor (573), and the communication circuit (590) of the wearable device (501) may transition to an active state.

[0163] In one embodiment, the wearable device (401) can request movement data from the wearable device (501). In one embodiment, the wearable device (401) can request movement data from the wearable device (501) while the wearable device (501) is operating in a normal state (591). In one embodiment, the wearable device (401) can request movement data from the wearable device (501) while the hand (611) is positioned in the wake-up area (630, 635).

[0164] In one embodiment, the wearable device (401) may set a period (or, the number of transmissions of movement data, bit rate) at which the wearable device (501) transmits movement data based on the state of the wearable device (401) and / or the state of the wearable device (501).

[0165] In one embodiment, the wearable device (401) may set a cycle (or, the number of transmissions of movement data, a bit rate) at which the wearable device (501) transmits movement data based on an application (146) running on the wearable device (401). In one embodiment, the wearable device (401) may set a cycle at which the wearable device (501) transmits movement data to be shorter based on the fact that the running application (146) is a type of application that requires low latency of gestures (e.g., a game application). In one embodiment, the wearable device (401) may set a number of transmissions of movement data to be greater based on the fact that the running application (146) is a type of application that requires low latency of gestures (e.g., a game application). In one embodiment, the wearable device (401) may increase the bit rate for transmitting motion data of the wearable device (501) based on the fact that the running application (146) is a type of application that requires low latency of gestures (e.g., a game application). According to an embodiment, the wearable device (401) may provide the user (500) with information related to a change in the period (or, the number of transmissions of motion data, the bit rate) at which the wearable device (501) transmits motion data. For example, the wearable device (401) may display (e.g., a pop-up menu, a notification message) information related to a change in the period (or, the number of transmissions of motion data, the bit rate) at which the wearable device (501) transmits motion data through the display (420).

[0166] In one embodiment, the wearable device (401) may set a cycle (or, a transmission frequency of movement data, a bit rate) at which the wearable device (501) transmits movement data based on a charge state of a battery (e.g., battery (189)) of the wearable device (401). In one embodiment, the wearable device (401) may set a cycle at which the wearable device (501) transmits movement data to become longer as the charge state of the battery (e.g., battery (189)) of the wearable device (401) becomes lower. In one embodiment, the wearable device (401) may set a cycle at which the wearable device (501) transmits movement data to become fewer as the charge state of the battery (e.g., battery (189)) of the wearable device (401) becomes lower. In one embodiment, the wearable device (401) may lower the bit rate for transmitting movement data of the wearable device (501) as the state of charge of the battery (e.g., battery (189)) of the wearable device (401) decreases, but is not limited thereto.

[0167] In one embodiment, the wearable device (401) may set a cycle (or, the number of transmissions of movement data, a bit rate) at which the wearable device (501) transmits movement data based on the charge state of the battery (580) of the wearable device (501). In one embodiment, the wearable device (401) may set the cycle at which the wearable device (501) transmits movement data to become longer as the charge state of the battery (580) of the wearable device (501) becomes lower. In one embodiment, the wearable device (401) may set the number of times the wearable device (501) transmits movement data to become fewer as the charge state of the battery (580) of the wearable device (501) becomes lower. In one embodiment, the wearable device (401) may lower the bit rate for transmitting movement data of the wearable device (501) as the state of charge of the battery (580) of the wearable device (501) decreases, but is not limited thereto.

[0168] In one embodiment, the wearable device (401) can identify a gesture based on one or more consecutive movements of the hand (611) identified through the camera (425). In one embodiment, the wearable device (401) can identify a gesture based on one or more consecutive movements of the hand (611) while the wearable device (501) is operating in a normal state (591). In one embodiment, the wearable device (401) can identify a gesture based on one or more consecutive movements of the hand (611) while the hand (611) is positioned in a wake-up area (630, 635). Hereinafter, the gesture (or pose) of the hand (611) identified through the camera (425) may be referred to as a first gesture.

[0169] In one embodiment, the wearable device (401) can identify a gesture (or pose) of the wearable device (501) based on movement data from the wearable device (501). In one embodiment, the wearable device (401) can identify movements of the wearable device (501) based on the movement data. In one embodiment, the wearable device (401) can identify a gesture (or pose) of the wearable device (501) based on movements of the wearable device (501). In one embodiment, the wearable device (401) can identify a gesture based on movement data acquired while the wearable device (501) operates in a normal state (591). In one embodiment, the wearable device (401) can identify a gesture based on movement data acquired while the hand (611) is positioned in the wake-up area (630, 635). Hereinafter, a gesture (or pose) of the hand (611) identified through the camera (425) may be referred to as a first gesture. Hereinafter, a gesture (or pose) of the wearable device (501) identified based on the movement data may be referred to as a second gesture.

[0170] In one embodiment, the wearable device (401) can perform a set function in response to a user input based on a first gesture and / or a second gesture. In one embodiment, the wearable device (401) can perform a set function in response to a user input based on a first gesture and / or a second gesture obtained while the wearable device (501) is operating in a normal state (591). In one embodiment, the wearable device (401) can perform a set function in response to a user input based on a first gesture and / or a second gesture obtained while the hand (611) is positioned in a wake-up area (630, 635). In one embodiment, the wearable device (401) can perform a set function in response to a user input based on a second gesture when the first gesture is not identified because the hand (611) is out of the field of view (600). In one embodiment, the wearable device (401) may perform a set function based on a user input based on a first gesture and a second gesture when a first gesture is identified as a hand (611) is identified in the field of view (600) within the wake-up area (630, 635). For example, the set function may include a control related to the content being played (e.g., play, pause, volume control), a control for an application (146), or a control for a remote electronic device (e.g., electronic device (108)). In one embodiment, a control for an application (146) may include a control related to the application (e.g., taking a picture, zooming in on a preview, zooming out on a preview, measuring blood pressure), and / or an execution of an application (e.g., invoking a voice recognition function, executing a camera application, executing a health application). In one embodiment, control of a remote electronic device (e.g., electronic device (108)) may include unlocking a door (e.g., a vehicle door, a home front door) or locking a door associated with the remote electronic device (e.g., electronic device (108)).In one embodiment, control of a remote electronic device (e.g., electronic device (108)) may include, but is not limited to, control of functions associated with the remote electronic device (e.g., electronic device (108)) (e.g., navigation, air conditioning, infotainment, noise canceling, listening to outside noise).

[0171] In one embodiment, the wearable device (401) can identify that the hand (611) has moved out of the wake-up area (630, 635). In one embodiment, the wearable device (401) can transmit a sleep signal to the wearable device (501) worn on the hand (611) in response to identifying that the hand (611) has moved out of the wake-up area (630, 635) in which the hand (611) is located. In one embodiment, the wearable device (501) can receive the sleep signal via the communication circuit (590). In one embodiment, the wearable device (501) can transition from a normal state (591) to a low power state (593) in response to receiving the sleep signal. In one embodiment, the communication circuit (590) of the wearable device (501) may transition from an active state to a sleep state in response to receiving a sleep signal. In one embodiment, as the wearable device (501) transitions from a normal state (591) to a low power state (593), at least some of the processor (520), the motion sensor (573), or the communication circuit (590) of the wearable device (501) may transition to an inactive state.

[0172] As described above, the wearable device (401) can transition to a low power state to reduce power consumption of the wearable device (501) while the hand (611) is identified in the field of view (600) of the camera (425). In addition, the wearable device (401) can receive movement data from the wearable device (501) while the hand (611) is not identified in the field of view (600) of the camera (425) to identify a gesture input of the user (500). Accordingly, the wearable device (401) can reduce power consumption of the wearable device (501) while increasing the reliability of the gesture input of the user (500) to the wearable device (401).

[0173] FIG. 6c illustrates an example of a situation in which a user wearing a wearable device moves his or her hand in one embodiment.

[0174] The wearable device (401) of FIG. 6C may correspond to the electronic device (101) of FIG. 1. The wearable device (401) of FIG. 6C may correspond to the wearable device (200) of FIGS. 2A and 2B. The wearable device (401) of FIG. 6C may correspond to the wearable device (300) of FIGS. 3A and 3B. The wearable device (401) of FIG. 6C may correspond to the wearable device (401) of FIG. 4. The wearable device (501) of FIG. 6C may correspond to the wearable devices (501) of FIGS. 5A, 5B, and 5C. FIG. 6c can be explained with reference to FIG. 1, FIG. 2a, FIG. 2b, FIG. 3a, FIG. 3b, FIG. 4, FIG. 5a, FIG. 5b, FIG. 5c, and FIG. 5d.

[0175] Compared to FIG. 6a, FIG. 6c can illustrate the field of view (600) of the camera (425) from three dimensions to two dimensions.

[0176] In one embodiment, the wearable device (401) may be in a state where it is not in communication connection with the wearable device (501). In one embodiment, the wearable device (401) may be in a state where it is not in communication connection with the wearable device (501) based on the results of object recognition and / or environment recognition. For example, the wearable device (401) may command the wearable device (501) to operate in an ultra-low power state (595) based on the number of objects that interfere with the identification of the hand (611) in the field of view (600) or the probability of interference. For example, the wearable device (401) may command the wearable device (501) to operate in an ultra-low power state (595) based on the number of objects that interfere with the identification of the hand (611) in the field of view (600) being less than a specified number or the probability of interference being less than a specified probability. In one embodiment, the probability of interference may be determined based on an artificial intelligence model trained to calculate the probability of interference based on the type of object, but is not limited thereto. In one embodiment, the probability of interference may be determined based on an artificial intelligence model trained to calculate the probability of interference based on the distance between the object and the hand (611) and / or the placement of the object within the field of view (600).

[0177] In one embodiment, the wearable device (401) may not establish a communication connection with the wearable device (501) based on the type of application (146) being executed. For example, the wearable device (401) may command the wearable device (501) to operate in an ultra-low power state (595) based on the fact that the application (146) being executed is a different type of application (e.g., a content playback application) than a type of application (e.g., a game application) that requires gesture input.

[0178] In one embodiment, the wearable device (501) may transition from a low power state (593) to an ultra low power state (595). In one embodiment, the wearable device (401) may be in a state where a communication connection is not established with the wearable device (501) based on a state of charge (SOC) of a battery (580) of the wearable device (501). For example, the wearable device (401) may transition from a low power state (593) to an ultra low power state (595) based on a state of charge of the battery (580) of the wearable device (501) being less than a first state of charge (e.g., 60%) and greater than or equal to a second state of charge (e.g., 30%).

[0179] In one embodiment, the wearable device (401) may be in a state where a communication connection is not established with the wearable device (501) (or, an unpaired state). In one embodiment, the wearable device (501) may be operating in an ultra-low power state (595).

[0180] Referring to FIG. 6C, the wearable device (401) can acquire an image for a field of view (600) of the camera (425) through the camera (425). In one embodiment, the wearable device (401) can perform object recognition and / or environment recognition based on the image acquired through the camera (425). In one embodiment, the wearable device (401) can identify one or more objects (501, 611, 620) within the field of view (600) of the camera (425) based on the object recognition and / or environment recognition.

[0181] In one embodiment, the wearable device (401) can identify one or more obstruction areas (620, 630). In one embodiment, the obstruction area (620, 625) may be an area where the hand (611) (or finger) is not identified through the field of view (600) of the camera (425). For example, the obstruction area (620) may be an area of ​​an obstruction object (e.g., a desk) that may obscure the hand (611) (or finger) as the hand (611) (or finger) moves among the objects within the field of view (600). For example, the obstruction area (625) may be an area outside the field of view (600). Here, the fact that an obstructing object (e.g., a desk) covers the hand (611) (or finger) may mean that the obstructing object (e.g., a desk) is located between the hand (611) (or finger) and the camera (425).

[0182] In one embodiment, the wearable device (401) can identify the movement (or movement trajectory) of the hand (611). In one embodiment, the wearable device (401) can identify the movement of the hand (611) within the field of view (600) of the camera (425). In one embodiment, the wearable device (401) can identify the relative movement of the hand (611). Here, the relative movement may include direct movement of the hand (611), movement of the hand (611) relative to the field of view (600) due to movement of the wearable device (401), and / or movement of the hand (611) relative to an object due to movement of the object within the field of view (600). Hereinafter, the movement of the hand (611) and the relative movement of the hand (611) may be referred to as movement of the hand (611).

[0183] In one embodiment, the wearable device (401) can identify (or set) distances based on the movement of the hand (611). In one embodiment, the wearable device (401) can identify distances from the interference area (620, 625) based on the movement of the hand (611). In one embodiment, the wearable device (401) can identify a first distance that the hand (611) can reach within a first time period specified by the hand (611) from the interference area (620, 625) based on the movement of the hand (611). In one embodiment, the wearable device (401) can identify a second distance that the hand (611) can reach within a second time period specified by the hand (611) from the interference area (620, 625) based on the movement of the hand (611). In one embodiment, the second distance may be longer than the first distance. In one embodiment, the first time may be determined based on a processing delay time. In one embodiment, the first time may be determined based on a time required for the wearable device (501) to transmit movement data to the wearable device (401). For example, the first time may include a delay time due to the network and a delay time for processing the movement data. For example, the first time may be greater than or equal to the time including the delay time due to the network and the delay time for processing the movement data. In one embodiment, the second time may be determined to be longer than the first time. In one embodiment, the second time may be determined based on a time that is the sum of the first time and the time required for pairing between the wearable device (401) and the wearable device (501).

[0184] In one embodiment, the wearable device (401) may set the first distance and the second distance to be longer as the movement speed of the hand (611) increases. In one embodiment, the wearable device (401) may set the first distance and the second distance to be shorter as the movement speed of the hand (611) decreases. In one embodiment, the wearable device (401) may set the first distance to a value obtained by multiplying the movement speed of the hand (611) by a specified first time. In one embodiment, the wearable device (401) may set the second distance to a value obtained by multiplying the movement speed of the hand (611) by a specified second time. For example, the wearable device (401) may set the first distance to a value obtained by multiplying the relative movement speed of the hand (611) toward each of the obstacles by a specified first time. For example, the wearable device (401) may set the second distance as a value obtained by multiplying a second time specified by a relative movement speed of the hand (611) toward each of the obstructing objects. For example, the wearable device (401) may set the first distance as a value obtained by multiplying a first time specified by a relative movement speed of the hand (611) toward each of the obstructing objects. For example, the wearable device (401) may set the second distance as a value obtained by multiplying a second time specified by a relative movement speed of the hand (611) toward each of the obstructing objects. In one embodiment, the wearable device (401) may set different first distances for each obstructing area of ​​the obstructing objects based on the relative movement speed of the hand (611). In one embodiment, the wearable device (401) may set different second distances for each obstructing area of ​​the obstructing objects based on the relative movement speed of the hand (611).

[0185] In one embodiment, the wearable device (401) may set one or more regions (630, 635) based on a first distance. In one embodiment, each of the one or more regions (630, 635) may be a region within a first distance from each of the interference regions (620, 625). In one embodiment, the region within the first distance from the interference region may be a wake-up region. In one embodiment, the region within the first distance from the interference region may be a transmission initiation region. Hereinafter, the region within the first distance from the interference region may be referred to as a wake-up region.

[0186] In one embodiment, the wearable device (401) may set one or more areas (640, 645) based on the second distance. In one embodiment, each of the one or more areas (640, 645) may be an area within a second distance from each of the interference areas (620, 625). In one embodiment, an area within the second distance from an interference area may be a pairing area. In one embodiment, an area within the second distance from an interference area may be a communication connection area. Hereinafter, an area within the second distance from an interference area may be referred to as a pairing area.

[0187] In one embodiment, the wearable device (401) can identify that the hand (611) has entered one of the pairing areas (640, 645). In one embodiment, the wearable device (401) can, in response to identifying that the hand (611) has entered the pairing area (640, 645), transmit a connection request signal to the wearable device (501) worn on the hand (611). In one embodiment, the wearable device (501) can receive the connection request signal via the communication circuit (590). In one embodiment, the wearable device (501) can, in response to receiving the connection request signal, transition from the ultra low power state (595) to the low power state (593). In one embodiment, the communication circuit (590) of the wearable device (501) may transition from a standby state to a sleep state in response to receiving a connection request signal.

[0188] In one embodiment, the wearable device (401) can identify that the hand (611) enters one of the wake-up zones (630, 635). In one embodiment, the wearable device (401) can identify that the hand (611) enters the wake-up zone (630, 635) while the wearable device (501) is operating in a low power state (593). In one embodiment, the wearable device (401) can identify that the hand (611) enters the wake-up zone (630, 635) from a pairing zone (640, 645).

[0189] In one embodiment, the wearable device (401) may transmit a wake-up signal to the wearable device (501) worn on the hand (611) in response to identifying that the hand (611) has entered a wake-up zone (630, 635). In one embodiment, the wearable device (501) may receive the wake-up signal via the communication circuit (590). In one embodiment, the wearable device (501) may transition from a low power state (593) to a normal state (591) in response to receiving the wake-up signal. In one embodiment, the communication circuit (590) of the wearable device (501) may transition from a sleep state to an active state in response to receiving the wake-up signal. In one embodiment, as the wearable device (501) transitions from a low power state (593) to a normal state (591), the processor (520), the motion sensor (573), and the communication circuitry (590) of the wearable device (501) may transition to an active state.

[0190] In one embodiment, the wearable device (401) can request movement data from the wearable device (501). In one embodiment, the wearable device (401) can request movement data from the wearable device (501) while the wearable device (501) is operating in a normal state (591). In one embodiment, the wearable device (401) can request movement data from the wearable device (501) while the hand (611) is positioned in the wake-up area (630, 635).

[0191] In one embodiment, the wearable device (401) may set a cycle (or, the number of transmissions of movement data, a bit rate) at which the wearable device (501) transmits movement data based on a state of the wearable device (401) and / or a state of the wearable device (501). For example, the wearable device (401) may set a cycle (or, the number of transmissions of movement data, a bit rate) at which the wearable device (501) transmits movement data based on a type of application (146) running on the wearable device (401), a charging state of a battery (e.g., battery (189)) of the wearable device (401), and / or a charging state of a battery (580) of the wearable device (501).

[0192] In one embodiment, the wearable device (401) can identify a gesture based on one or more consecutive movements of the hand (611) identified through the camera (425). In one embodiment, the wearable device (401) can identify a gesture based on one or more consecutive movements of the hand (611) while the wearable device (501) is operating in a normal state (591). In one embodiment, the wearable device (401) can identify a gesture based on one or more consecutive movements of the hand (611) while the hand (611) is positioned in a wake-up area (630, 635). Hereinafter, the gesture (or pose) of the hand (611) identified through the camera (425) may be referred to as a first gesture.

[0193] In one embodiment, the wearable device (401) can identify a gesture (or pose) of the wearable device (501) based on movement data from the wearable device (501). In one embodiment, the wearable device (401) can identify movements of the wearable device (501) based on the movement data. In one embodiment, the wearable device (401) can identify a gesture (or pose) of the wearable device (501) based on movements of the wearable device (501). In one embodiment, the wearable device (401) can identify a gesture based on movement data acquired while the wearable device (501) operates in a normal state (591). In one embodiment, the wearable device (401) can identify a gesture based on movement data acquired while the hand (611) is positioned in the wake-up area (630, 635). Hereinafter, a gesture (or pose) of the hand (611) identified through the camera (425) may be referred to as a first gesture. Hereinafter, a gesture (or pose) of the wearable device (501) identified based on the movement data may be referred to as a second gesture.

[0194] In one embodiment, the wearable device (401) can perform a set function in response to a user input based on a first gesture and / or a second gesture. In one embodiment, the wearable device (401) can perform a set function in response to a user input based on a first gesture and / or a second gesture obtained while the wearable device (501) is operating in a normal state (591). In one embodiment, the wearable device (401) can perform a set function in response to a user input based on a first gesture and / or a second gesture obtained while the hand (611) is positioned in a wake-up area (630, 635). In one embodiment, the wearable device (401) can perform a set function in response to a user input based on a second gesture when the first gesture is not identified because the hand (611) is out of the field of view (600). In one embodiment, the wearable device (401) may perform a set function based on a user input based on a first gesture and a second gesture when a first gesture is identified as a hand (611) is identified in the field of view (600) within the wake-up area (630, 635). For example, the set function may include a control related to the content being played (e.g., play, pause, volume control), a control for an application (146), or a control for a remote electronic device (e.g., electronic device (108)). In one embodiment, a control for an application (146) may include a control related to the application (e.g., taking a picture, zooming in on a preview, zooming out on a preview, measuring blood pressure), and / or an execution of an application (e.g., invoking a voice recognition function, executing a camera application, executing a health application). In one embodiment, control of a remote electronic device (e.g., electronic device (108)) may include unlocking a door (e.g., a vehicle door, a home front door) or locking a door associated with the remote electronic device (e.g., electronic device (108)).In one embodiment, control of a remote electronic device (e.g., electronic device (108)) may include, but is not limited to, control of functions associated with the remote electronic device (e.g., electronic device (108)) (e.g., navigation, air conditioning, infotainment, noise canceling, listening to outside noise).

[0195] In one embodiment, the wearable device (401) can identify that the hand (611) has moved out of the wake-up area (630, 635). In one embodiment, the wearable device (401) can transmit a sleep signal to the wearable device (501) worn on the hand (611) in response to identifying that the hand (611) has moved out of the wake-up area (630, 635) in which the hand (611) is located. In one embodiment, the wearable device (501) can receive the sleep signal via the communication circuit (590). In one embodiment, the wearable device (501) can transition from a normal state (591) to a low power state (593) in response to receiving the sleep signal. In one embodiment, the communication circuit (590) of the wearable device (501) may transition from an active state to a sleep state in response to receiving a sleep signal. In one embodiment, as the wearable device (501) transitions from a normal state (591) to a low power state (593), at least some of the processor (520), the motion sensor (573), or the communication circuit (590) of the wearable device (501) may transition to an inactive state.

[0196] In one embodiment, the wearable device (401) can identify that the hand (611) has moved out of the pairing area (640, 645). In one embodiment, the wearable device (401) can transmit a termination signal to the wearable device (501) worn on the hand (611) in response to identifying that the hand (611) has moved out of the pairing area (640, 645) in which the hand (611) is located. In one embodiment, the wearable device (501) can receive the termination signal via the communication circuit (590). In one embodiment, the wearable device (501) can transition from a low power state (593) to an ultra low power state (595) in response to receiving the termination signal. In one embodiment, the communication circuit (590) of the wearable device (501) may transition from a sleep state to a standby state in response to receiving a connection termination signal in a low power state (593).

[0197] As described above, the wearable device (401) can transition to a standby state while the hand (611) is identified in the field of view (600) of the camera (425) to further reduce power consumption of the wearable device (501). In addition, the wearable device (401) can set an area for transitioning the wearable device (401) from the standby state to the sleep state and an area for transitioning the wearable device (401) from the sleep state to the normal state, taking into account a situation in which the hand (611) may not be identified in the field of view (600) of the camera (425). Accordingly, the wearable device (401) can further reduce power consumption of the wearable device (501) while increasing the reliability of the user's (500) gesture input to the wearable device (401).

[0198] In FIGS. 6A and 6B, when a user (500) wears a wearable device (501) on a hand (611), the wearable device (401) sets a first distance and / or a second distance for receiving movement data with respect to the wearable device (501). However, this is merely an example. Depending on the embodiment, the user (500) wearing the wearable device (401) and the user wearing the wearable device (501) may be different from each other.

[0199] In one embodiment, the wearable device (401) can identify the movement of another user's gaze (505) through the camera (425). In one embodiment, the wearable device (401) can identify a gesture based on the movement of another user's gaze (505) through the camera (425). In one embodiment, the wearable device (401) can set a first distance and / or a second distance to obtain movement data from a wearable device (501) worn by another user. In one embodiment, the wearable device (401) can establish a communication connection with the wearable device (501) based on the wearable device (501) worn by another user being located within the second distance. In one embodiment, the wearable device (401) may request movement data from the wearable device (501) based on the fact that the wearable device (501) worn by another user is located within a first distance. In one embodiment, the wearable device (401) may identify a gesture of the wearable device (401) based on movement data from the wearable device (501) worn by another user.

[0200] As described above, the wearable device (401) can identify gestures of other users and / or gestures of wearable devices (501) worn by other users. Accordingly, the wearable device (401) can obtain one or more gestures from different users (e.g., the user (500) and other users), thereby allowing multiple users to perform specific actions simultaneously. For example, the wearable device (401) can obtain one or more gestures from different users (e.g., the user (500) and other users), thereby allowing multiple users to perform specific actions, such as joint announcements and joint performances, simultaneously.

[0201] FIG. 7A illustrates an example of situations in which a wearable device sets a distance in one embodiment.

[0202] The wearable device (501) of Fig. 7a may correspond to the wearable devices (501) of Figs. 5a, 5b, and 5c. Fig. 7a may be described with reference to Figs. 1, 2a, 2b, 3a, 3b, 4, 5a, 5b, 5c, 5d, 6a, and 6b.

[0203] Situations (701, 703) of FIG. 7A may represent examples in which the wearable device (401) sets only one zone (or wake-up zone (721, 725)) based on the state of charge of the battery (580) of the wearable device (501). In one embodiment, the wearable device (401) may instruct the wearable device (501) to operate in a low power state (593) based on the state of charge (SOC) of the battery (580) of the wearable device (501) being equal to or greater than a first state of charge (e.g., 60%). In one embodiment, the wearable device (401) may set only one area (e.g., a wake-up area) of at least two areas (e.g., a wake-up area, a pairing area) associated with obtaining movement data from the wearable device (501) as the wearable device (501) operates in a low power state (593).

[0204] In one embodiment, the wearable device (401) can identify (or set) a first distance (731, 735) for setting a wake-up zone (721, 725) based on the movement of the hand (611). In one embodiment, the wearable device (401) can identify a first distance (731, 735) from an interference zone (711, 715) based on the movement of the hand (611). In one embodiment, the wearable device (401) can identify a first distance (731, 735) that the hand (611) can reach within a first time period designated by the hand (611) to the interference zone (711, 715) based on the movement of the hand (611). In one embodiment, the first time period can be determined based on a processing delay time. In one embodiment, the first time may be determined based on a time required for the wearable device (501) to transmit movement data to the wearable device (401). For example, the first time may include a network-induced delay time between the wearable device (401) and the wearable device (501). For example, the first time may include a delay time for processing movement data of the wearable device (401) and / or the wearable device (501). For example, the first time may include a network-induced delay time and a delay time for processing movement data.

[0205] In one embodiment, the wearable device (401) may set the first distance (731, 735) to be longer as the movement speed of the hand (611) increases. In one embodiment, the wearable device (401) may set the first distance (731, 735) to be shorter as the movement speed of the hand (611) decreases. Referring to FIG. 7A, the first distance (731) in a faster situation (701) may be longer than the first distance (735) in a slower situation (703).

[0206] In one embodiment, the wearable device (401) may set one or more wake-up areas (721, 725) based on a first distance (731, 735). In one embodiment, each of the one or more wake-up areas (721, 725) may be an area within the first distance (731, 735) from each of the interference areas (711, 715). In FIG. 7A, the wake-up areas (721, 725) are illustrated as being elliptical, but this is merely an example. Depending on the embodiment, the shapes of the wake-up areas (721, 725) may vary. For example, the shape of each of the wake-up regions (721, 725) may be determined by at least one of the movement of the field of view (600) of the camera (425) (e.g., the movement of the field of view (600) according to the movement of the head of the user (500), the relative distance between the hand (611) and the obstructing object, or the movement, the shape of the obstructing object, or the first time. For example, each of the wake-up regions (721, 725) may have a shape that includes the obstructing object at the first distance (731, 735). For example, each of the wake-up regions (721, 725) may be set by weights based on the characteristics of the obstructing object (e.g., the probability of obstruction, the probability of inputting a gesture, the additional obstructing area). Here, the probability of obstruction of the obstructing object may be a probability calculated based on the type of the obstructing object. The probability of inputting a gesture may be the probability of inputting a gesture when the user's (500) hand is obscured by an obstruction. The additional obstruction area may be set as an area (e.g., an area within a specified distance from the edge of the desk) that is likely to be obscured by an obstruction (e.g., a desk).

[0207] FIG. 7b illustrates an example of situations in which a wearable device sets distances in one embodiment.

[0208] The wearable device (501) of FIG. 7B may correspond to the wearable devices (501) of FIGS. 5A, 5B, and 5C. FIG. 7B may be described with reference to FIGS. 1, 2A, 2B, 3A, 3B, 4, 5A, 5B, 5C, 5D, 6A, and 6C.

[0209] Situations (705, 707) of FIG. 7B may represent examples in which the wearable device (401) sets two zones (or wake-up zones (721, 725) and pairing zones (741, 745)) based on the state of charge of the battery (580) of the wearable device (501). In one embodiment, the wearable device (401) may instruct the wearable device (501) to operate in an ultra-low power state (595) based on the state of charge (SOC) of the battery (580) of the wearable device (501) being less than a first state of charge (e.g., 60%) and greater than a second state of charge (e.g., 30%). In one embodiment, the wearable device (401) may set at least two regions (e.g., wake-up regions (721, 725) and pairing regions (741, 745)) associated with obtaining movement data from the wearable device (501) while the wearable device (501) operates in an ultra-low power state (595).

[0210] In one embodiment, the wearable device (401) can identify (or set) a first distance (731, 735) for setting a wake-up zone (721, 725) and a second distance (751, 755) for setting a pairing zone (741, 745) based on the movement of the hand (611). In one embodiment, the wearable device (401) can identify a first distance (731, 735) and a second distance (751, 755) from an interference zone (711, 715) based on the movement of the hand (611). In one embodiment, the wearable device (401) can identify a first distance (731, 735) that the hand (611) can reach within a first time period specified in the interference area (711, 715) based on the movement of the hand (611). In one embodiment, the wearable device (401) can identify a second distance (751, 755) that the hand (611) can reach within a second time period specified in the interference area (711, 715) based on the movement of the hand (611).

[0211] In one embodiment, the second distance (751, 755) may be longer than the first distance (731, 735). In one embodiment, the first time may be determined based on a processing delay time. In one embodiment, the first time may be determined based on a time required for the wearable device (501) to transmit movement data to the wearable device (401). For example, the first time may include a delay time due to the network and a delay time for processing the movement data. In one embodiment, the second time may be determined to be longer than the first time. In one embodiment, the second time may be determined based on a time that is the sum of the first time and the time required for the wearable device (401) and the wearable device (501) to pair.

[0212] In one embodiment, the wearable device (401) may set the first distance (731, 735) and the second distance (751, 755) to be longer as the movement speed of the hand (611) increases. In one embodiment, the wearable device (401) may set the first distance (731, 735) and the second distance (751, 755) to be shorter as the movement speed of the hand (611) decreases. Referring to FIG. 7B, the first distance (731) and the second distance (751) in a faster situation (701) may be longer than the first distance (735) and the second distance (755) in a slower situation (703).

[0213] In one embodiment, the wearable device (401) can set one or more wake-up areas (721, 725) based on a first distance (731, 735). In one embodiment, each of the one or more wake-up areas (721, 725) can be an area within a first distance (731, 735) from each of the interference areas (711, 715). In one embodiment, the wearable device (401) can set one or more pairing areas (741, 745) based on a second distance (751, 755). In one embodiment, each of the one or more pairing areas (741, 745) can be an area within a second distance (751, 755) from each of the interference areas (711, 715). In FIG. 7B, the wake-up areas (721, 725) and the pairing areas (741, 745) are illustrated as being elliptical, but this is merely an example. Depending on the embodiment, the shapes of the wake-up areas (721, 725) and the pairing areas (741, 745) may vary. For example, the shapes of the wake-up areas (721, 725) and the pairing areas (741, 745) may be determined by at least one of the movement of the field of view (600) of the camera (425) (e.g., the movement of the field of view (600) according to the movement of the head of the user (500)), the relative distance between the hand (611) and the obstructing object, or the movement, the shape of the obstructing object, the first time, or the second time. For example, each of the wake-up regions (721, 725) may have a shape that includes an obstruction object at a first distance. For example, each of the pairing regions (741, 745) may have a shape that includes an obstruction object at a second distance. For example, each of the pairing regions (741, 745) may be set by weights based on characteristics of the obstruction object (e.g., probability of obstruction, probability of inputting a gesture, additional obstruction area).Here, the probability of interference by an obstructing object may be a probability calculated based on the type of obstructing object. The probability of inputting a gesture may be the probability of inputting a gesture when the user's (500) hand is obscured by the obstructing object. The additional obstruction area may be set as an area likely to be obscured by an obstructing object (e.g., a desk) (e.g., an area within a specified distance from the edge of the desk).

[0214] Figure 8 illustrates an example of a situation where a user wears multiple wearable devices.

[0215] The wearable devices of FIG. 8 (e.g., 805, 811, 821, 822, 823, 824, 825) may correspond to the wearable device (501) of FIGS. 5A, 5B, and 5C. FIG. 8 may be described with reference to FIGS. 1, 2A, 2B, 3A, 3B, 4, 5A, 5B, 5C, 5D, 6A, and 6C.

[0216] In one embodiment, the wearable device (401) can identify one or more objects (805, 811, 821, 822, 823, 824, 825, 830) within the field of view (600) of the camera (425). In one embodiment, the wearable device (401) can identify one or more objects (805, 811, 821, 822, 823, 824, 825, 830) within the field of view (600) of the camera (425) based on object recognition and / or environment recognition. In one embodiment, some of the objects (805, 811, 821, 822, 823, 824, 825, 830) may be wearable devices. In one embodiment, the one or more objects (805, 811, 821, 822, 823, 824, 825, 830) may include a hand (830) of a user (500). In one embodiment, the hand (830) may be a hand of a user (500) wearing a wearable device (e.g., 805, 811, 821, 822, 823, 824, 825). However, the present invention is not limited thereto.

[0217] Referring to the situation (810) of FIG. 8, a user (500) may wear a glove-type wearable device (e.g., 811) and a watch-type wearable device (e.g., 805). In one embodiment, the glove-type wearable device (e.g., 811) may have motion sensors attached to each finger of the user's (500) hand (830). In one embodiment, the glove-type wearable device (e.g., 811) may obtain movement data of each finger of the user's (500) hand (830). In one embodiment, the watch-type wearable device (e.g., 805) may obtain movement data of the wrist.

[0218] Referring to the situation (820) of FIG. 8, the user (500) can wear two or more ring-type wearable devices (e.g., 821, 822, 823, 824, 825) and a watch-type wearable device (e.g., 805). In one embodiment, the two or more ring-type wearable devices (e.g., 821, 822, 823, 824, 825) can be worn on each of the fingers of the hand (830) of the user (500). In one embodiment, each of the two or more ring-type wearable devices (e.g., 821, 822, 823, 824, 825) can obtain movement data of the worn finger among the fingers of the hand (830) of the user (500).

[0219] In one embodiment, the wearable device (401) can identify that two or more wearable devices (e.g., 805, 811, 821, 822, 823, 824, 825) are worn on the hand (830) of the user (500). In one embodiment, the wearable device (401) can identify a wearable device to transmit a signal (e.g., a wake-up signal, a connection request signal) in a wake-up area and / or a pairing area based on identifying that two or more wearable devices (e.g., 805, 811, 821, 822, 823, 824, 825) are worn on the hand (830) of the user (500).

[0220] In one embodiment, the wearable device (401) may transmit a signal (e.g., a wake-up signal, a connection request signal) in a wake-up area and / or a pairing area to a wearable device having the highest battery charge state among two or more wearable devices (e.g., 805, 811, 821, 822, 823, 824, 825) worn on the hand (830) of the user (500), but is not limited thereto. In one embodiment, the wearable device (401) may transmit a signal (e.g., a wake-up signal, a connection request signal) in a wake-up area and / or a pairing area to a wearable device having the highest battery charge capacity among two or more wearable devices (e.g., 805, 811, 821, 822, 823, 824, 825) worn on the hand (830) of the user (500).

[0221] In one embodiment, the wearable device (401) may transmit a signal (e.g., a wake-up signal, a connection request signal) in a wake-up area and / or a pairing area to a designated type of wearable device among two or more wearable devices (e.g., 805, 811, 821, 822, 823, 824, 825) worn on the hand (830) of the user (500). For example, when the input through the hand (830) of the user (500) is a gesture using multiple fingers, the wearable device (401) may transmit a signal (e.g., a wake-up signal, a connection request signal) in a wake-up area and / or a pairing area to a wearable device (e.g., 811, 821, 822, 823, 824, 825) worn on a finger among two or more wearable devices (e.g., 805, 811, 821, 822, 823, 824, 825).

[0222] In one embodiment, the wearable device (401) can transmit a signal (e.g., a wake-up signal, a connection request signal) in a wake-up area and / or a pairing area to a wearable device (e.g., 811, 821, 822, 823, 824, 825) worn on a finger that requires movement for a gesture through a hand (830) of the user (500). In one embodiment, the wearable device (401) can change a ring-type wearable device that transmits a signal (e.g., a wake-up signal, a connection request signal) in a wake-up area and / or a pairing area among two or more ring-type wearable devices (e.g., 821, 822, 823, 824, 825) depending on the position of the finger that requires movement for a gesture through the hand (830) of the user (500). For example, when the wearable device (401) makes a pointing gesture through the hand (830) of the user (500), the wearable device (401) can transmit a signal (e.g., a wake-up signal, a connection request signal) to a wearable device (e.g., 822) worn on an index finger among two or more ring-type wearable devices (e.g., 821, 822, 823, 824, 825) in a wake-up area and / or a pairing area. For example, when the wearable device (401) types through the fingers of the hand (830) of the user (500), the wearable device (401) can transmit a signal (e.g., a wake-up signal, a connection request signal) to two or more ring-type wearable devices (e.g., 821, 822, 823, 824, 825) other than a watch-type wearable device (e.g., 805) in a wake-up area and / or a pairing area. For example, when a wearable device (401) performs a finger snap gesture using the thumb and middle finger of the fingers of the hand (830) of the user (500), the wearable device (401) may transmit a signal (e.g., a wake-up signal, a connection request signal) to the wearable devices (e.g., 821, 823) among two or more ring-shaped wearable devices (e.g., 821, 822, 823, 824, 825) in a wake-up area and / or a pairing area.

[0223] According to an embodiment, the wearable device (401) may determine which wearable device to transmit a signal (e.g., a wake-up signal, a connection request signal) in a wake-up area and / or a pairing area, depending on which ring-type wearable device (e.g., 821, 822, 823, 824, 825) is worn on which finger the user (500) is wearing. For example, the wearable device (401) may determine a wearable device to transmit a signal (e.g., a wake-up signal, a connection request signal) in the wake-up area and / or the pairing area among ring-shaped wearable devices (e.g., 821, 822, 823, 824, 825) through an artificial intelligence model for determining a wearable device to transmit a signal (e.g., a wake-up signal, a connection request signal) in the wake-up area and / or the pairing area based on the time, the hand on which the wearable device is worn, the position of the finger on which the wearable device is worn, and / or the type of the wearable device worn on the finger. However, the present invention is not limited thereto.

[0224] In one embodiment, the wearable device (401) may set different wake-up zones and / or pairing zones depending on the types of wearable devices (e.g., 805, 811, 821, 822, 823, 824, 825) worn by the user (500). In one embodiment, the wearable device (401) may determine the wake-up zone based on the time required for the wearable devices (e.g., 805, 811, 821, 822, 823, 824, 825) to transmit movement data to the wearable device (401). In one embodiment, the wearable device (401) may set a pairing area based on the time required for the wearable devices (e.g., 805, 811, 821, 822, 823, 824, 825) to pair with the wearable device (401) and the time required to transmit movement data to the wearable device (401).

[0225] In one embodiment, when a wearable device (401) includes a plurality of motion sensors, the wearable device (401) may transmit a signal (e.g., a wake-up signal, a connection request signal) so that the wearable device (401) transmits motion data acquired through some of the motion sensors to the wearable device (401). For example, the wearable device (401) may transmit a signal (e.g., a wake-up signal, a connection request signal) to the wearable device (e.g., 811) so that the wearable device (401) transmits motion data acquired through a selected motion sensor among the plurality of motion sensors of the wearable device (e.g., 811) attached to each of the fingers of the user (500). However, the present invention is not limited thereto. The wearable device (401) can transmit a signal (e.g., a wake-up signal, a connection request signal) to the wearable device (e.g., 811) so that the wearable device (401) transmits movement data acquired through all of the multiple motion sensors of the wearable device (e.g., 811) attached to each of the fingers of the user (500) to the wearable device (401).

[0226] FIG. 9 illustrates an example of a field of view (FOV) of a wearable device according to movement of a user's hand in one embodiment.

[0227] The wearable device (300) of FIG. 9 may correspond to the electronic device (101) of FIG. 1. The wearable device (300) of FIG. 9 may correspond to the wearable device (200) of FIGS. 2A and 2B. The wearable device (300) of FIG. 9 may correspond to the wearable device (300) of FIGS. 3A and 3B. The wearable device (300) of FIG. 9 may correspond to the wearable device (401) of FIG. 4. The wearable device (501) of FIG. 9 may correspond to the wearable devices (501) of FIGS. 5A, 5B, and 5C. FIG. 9 can be explained with reference to FIG. 1, FIG. 2a, FIG. 2b, FIG. 3a, FIG. 3b, FIG. 4, FIG. 5a, FIG. 5b, FIG. 5c, FIG. 5d, FIG. 6a, and FIG. 6c.

[0228] Referring to FIG. 9, the wearable device (300) may include one or more cameras (340-5, 340-6, 340-7, 340-8, 340-9, 340-10). The wearable device (300) may acquire images for fields of view (901, 902, 903, 904, 905, 906) of each of the one or more cameras (340-5, 340-6, 340-7, 340-8, 340-9, 340-10) through the one or more cameras (340-5, 340-6, 340-7, 340-8, 340-9, 340-10).

[0229] In one embodiment, the wearable device (300) can identify the movement of a user's hand within the fields of view (901, 902, 903, 904, 905, 906) of one or more cameras (340-5, 340-6, 340-7, 340-8, 340-9, 340-10).

[0230] In one embodiment, the wearable device (300) may turn off the camera for acquiring the field of view from which the hand has left when the user's hand moves out of any one of the fields of view (901, 902, 903, 904, 905, 906). In one embodiment, the wearable device (300) may turn on the camera for acquiring the field of view from which the hand has entered when the user's hand moves into any one of the fields of view (901, 902, 903, 904, 905, 906).

[0231] In one embodiment, the wearable device (300) may identify the first distance and / or the second distance based on the fields of view (901, 902, 903, 904, 905, 906). For example, the wearable device (300) may not set the first distance and / or the second distance for the outskirt of one field of view that is included in another field of view if the outskirt of one field of view is included in another field of view. For example, the wearable device (300) may set the first distance and / or the second distance for the outskirt of one field of view that is not included in any field of view if the outskirt of one field of view is not included in any field of view.

[0232] In one embodiment, the wearable device (300) can set the first distance and / or the second distance through a field of view based on some selected cameras among one or more cameras (340-5, 340-6, 340-7, 340-8, 340-9, 340-10). In one embodiment, as the wearable device (300) sets the first distance and / or the second distance through a field of view based on some selected cameras among one or more cameras (340-5, 340-6, 340-7, 340-8, 340-9, 340-10), the first distance and / or the second distance can be changed according to the fields of view (901, 902, 903, 904, 905, 906) of the selected cameras. For example, when the wearable device (501) is moved from the field of view (902) of the camera (340-9) to the field of view (905) of the camera (340-10) with the cameras (340-7, 340-8) turned off (i.e., the fields of view (904, 906) are not acquired), the wearable device (300) can set the first distance and / or the second distance in the field of view (905) of the camera (340-10). For example, when the cameras (340-7, 340-8) are turned on (i.e., the fields of view (904, 906) are acquired), if the wearable device (501) moves from the field of view (902) of the camera (340-9) to the field of view (905) of the camera (340-10), the wearable device (300) can set the first distance and / or the second distance in the fields of view (904, 906) other than the field of view (905) of the camera (340-10).

[0233] FIG. 10 illustrates an example of a situation on the front side of a wearable device, in one embodiment.

[0234] In one embodiment, the wearable device (401) can identify one or more objects (1011, 1012, 1013, 1014, 1015, 106, 1017) within the field of view (600) of the camera (425). In one embodiment, the wearable device (401) can identify one or more objects (1011, 1012, 1013, 1014, 1015, 106, 1017) within the field of view (600) of the camera (425) based on object recognition and / or environment recognition. In one embodiment, object (1011) may be an organizer box, object (1012) may be a board, object (1013) may be a desk, object (1014) may be a monitor, object (1015) may be books, object (1016) may be an auxiliary drawer, and object (1017) may be a trash can.

[0235] In one embodiment, the wearable device (401) may set a probability of interference based on the results of object recognition and / or environment recognition. In one embodiment, the probability of interference may be determined based on an artificial intelligence model trained to calculate a probability of interference based on the type of object. In one embodiment, the artificial intelligence model may be reinforcement learned to calculate an updated probability of interference based on whether the wearable device (401) is actually obscured by the movement of the hand (611) of the user (500). However, the present invention is not limited thereto. In one embodiment, the probability of interference may be determined based on an artificial intelligence model trained to calculate a probability of interference based on the distance between the object and the hand (611), and / or the arrangement of the object within the field of view (600). For example, the wearable device (401) can identify, through an artificial intelligence model, that the probability of interference of an object (1011) is 3.5%, the probability of interference of an object (1012) is 5%, the probability of interference of an object (1013) is 75%, the probability of interference of an object (1014) is 25%, the probability of interference of an object (1015) is 2.5%, the probability of interference of an object (1016) is 12%, and the probability of interference of an object (1017) is 15%.

[0236] In one embodiment, the wearable device (401) may set a first distance and a second distance for each of one or more objects (1011, 1012, 1013, 1014, 1015, 106, 1017) based on an interference probability of each of the one or more objects (1011, 1012, 1013, 1014, 1015, 106, 1017). In one embodiment, the wearable device (401) may set the first distance and the second distance for each of one or more objects (1011, 1012, 1013, 1014, 1015, 106, 1017) as a value obtained by multiplying the first distance and the second distance by the interference probability of each of the one or more objects (1011, 1012, 1013, 1014, 1015, 106, 1017), but is not limited thereto.

[0237] In one embodiment, the wearable device (401) may set a probability of inputting a gesture when the user's (500) hand is covered by an object based on the results of object recognition and / or environment recognition.

[0238] In one embodiment, the probability of inputting a gesture may be determined based on an artificial intelligence model trained to calculate the probability of inputting a gesture based on the type of object. In one embodiment, the artificial intelligence model may be reinforcement learned to calculate the probability of inputting an updated gesture based on the number of times the gesture is input when the hand (611) of the user (500) of the wearable device (401) is actually occluded by the movement of the hand (611). For example, the wearable device (401) may train the artificial intelligence model to decrease the probability of inputting an updated gesture when the user (500) does not input a gesture while the hand (611) of the user (500) is occluded by an object (1017) such as a trash can. However, the present invention is not limited thereto.

[0239] In one embodiment, the wearable device (401) may determine whether to set the first distance and the second distance for each of one or more objects (1011, 1012, 1013, 1014, 1015, 106, 1017) based on the probability of inputting a gesture for each of the one or more objects (1011, 1012, 1013, 1014, 1015, 106, 1017). In one embodiment, the wearable device (401) may not set the first distance and the second distance for an object among one or more objects (1011, 1012, 1013, 1014, 1015, 106, 1017) whose probability of inputting a gesture is less than or equal to a reference probability. In one embodiment, the wearable device (401) may set the first distance and the second distance for an object among one or more objects (1011, 1012, 1013, 1014, 1015, 106, 1017) whose probability of inputting a gesture exceeds a reference probability. However, the present invention is not limited thereto.

[0240] FIG. 11 illustrates an example of a situation (1101, 1105) in which a wearable device sets an interference area for an obstruction object in one embodiment.

[0241] Referring to FIG. 11, the wearable device (401) can acquire an image for the field of view (600) of the camera (425) through the camera (425). In one embodiment, the wearable device (401) can perform object recognition and / or environment recognition based on the image acquired through the camera (425). In one embodiment, the wearable device (401) can identify an object (e.g., a desk) within the field of view (600) of the camera (425) based on the object recognition and / or environment recognition.

[0242] In one embodiment, the wearable device (401) can identify one or more obstruction areas (1111, 1115). In one embodiment, the obstruction areas (620, 625) may be areas where the hand (611) (or finger) is not identified through the field of view (600) of the camera (425). For example, the obstruction area (620) may be an area of ​​an obstruction object (e.g., a desk) that may obscure the hand (611) (or finger) according to the movement of the hand (611) (or finger) among the objects within the field of view (600). Here, the obstruction object (e.g., a desk) obscuring the hand (611) (or finger) may mean that the obstruction object (e.g., a desk) is located between the hand (611) (or finger) and the camera (425).

[0243] In one embodiment, the wearable device (401) can further identify additional interference areas (1125). In one embodiment, the wearable device (401) can further identify additional interference areas (1125) based on object recognition and / or environmental awareness. In one embodiment, the wearable device (401) can further identify additional interference areas (1125) based on object recognition and / or environmental awareness when the wearable device (501) is worn on the hand (611). In one embodiment, the wearable device (401) can further identify additional interference areas (1125) based on object recognition and / or environmental awareness when it is identified that the wearable device (501) is worn on the hand (611). In one embodiment, the additional obstruction area (1125) may be an area where the hand (611) (or fingers) may be obscured by an obstruction object (e.g., a desk). In one embodiment, the additional obstruction area (1125) may be set as an area within a specified distance from the edge of the obstruction object (e.g., a desk).

[0244] In one embodiment, the wearable device (401) can identify (or set) a first distance (731, 735) and a second distance (751, 755) from the additional interference area (1125) based on the movement of the hand (611). In one embodiment, the wearable device (401) can identify (or set) a first distance (731, 735) and a second distance (751, 755) from the additional interference area (1125) based on the movement of the hand (611) when the wearable device (501) is worn on the hand (611).

[0245] Figure 12 is a flowchart illustrating the operation of a wearable device according to one embodiment.

[0246] FIG. 12 can be explained with reference to FIG. 1, FIG. 2a, FIG. 2b, FIG. 3a, FIG. 3b, FIG. 4, FIG. 5a, FIG. 5b, FIG. 5c, FIG. 5d, FIG. 6a, and FIG. 6b.

[0247] Referring to FIG. 12, in operation 1210, the wearable device (401) may identify the movement of the hand (611). In one embodiment, the wearable device (401) may identify the movement of the hand (611) within the field of view (600) of the camera (425). In one embodiment, the wearable device (401) may identify the relative movement of the hand (611). Here, the relative movement may include a direct movement of the hand (611), a movement of the hand (611) relative to the field of view (600) due to movement of the wearable device (401), and / or a movement of the hand (611) relative to an object due to movement of the object within the field of view (600). Hereinafter, the movement of the hand (611) and the relative movement of the hand (611) may be referred to as the movement of the hand (611). Here, the relative motion may include direct motion of the hand (611), motion of the hand (611) relative to the field of view (600) due to movement of the wearable device (401), and / or motion of the hand (611) relative to an object due to movement of the object within the field of view (600). In one embodiment, the motion of the hand (611) may be identified based on a direction of movement and / or a speed of movement of the hand (611). In one embodiment, the relative motion of the hand (611) may be identified based on a direction of movement and / or a speed of movement relative to an arbitrary object (e.g., the field of view (600) and / or an object) of the hand (611).

[0248] In operation 1220, the wearable device (401) may set a first distance corresponding to the movement. In one embodiment, the wearable device (401) may identify the first distance from the interference area (620, 625) based on the movement of the hand (611). In one embodiment, the wearable device (401) may identify the first distance that the hand (611) can reach within a first time specified in the interference area (620, 625) based on the movement of the hand (611). In one embodiment, the wearable device (401) may set the first distance from each of the interference areas (620, 625) based on locations that can be reached within a time specified in the interference area (620, 625) based on the movement direction and / or movement speed of the hand (611). In one embodiment, the first time may be determined based on a processing delay time. In one embodiment, the first time may be determined based on a time required for the wearable device (501) to transmit movement data to the wearable device (401). For example, the first time may include a network-induced delay time between the wearable device (401) and the wearable device (501). For example, the first time may include a delay time for processing movement data of the wearable device (401) and / or the wearable device (501). For example, the first time may include a network-induced delay time and a delay time for processing the movement data.

[0249] In operation 1230, the wearable device (401) may determine whether the hand (611) is within a first distance from a disturbance area. In one embodiment, the wearable device (401) may identify whether the hand (611) is within the first distance from one of one or more disturbance areas (620, 625).

[0250] In operation 1230, in response to identifying that the hand (611) is within a first distance from the interference area, the wearable device (401) may perform operation 1240. In operation 1230, in response to identifying that the hand (611) is beyond the first distance from the interference area, the wearable device (401) may perform operation 1260.

[0251] In operation 1240, the wearable device (401) may request movement data from another wearable device (501). In one embodiment, the wearable device (401) may transmit a wake-up signal to the wearable device (501) worn on the hand (611) in response to identifying that the hand (611) is within a first distance from the obstruction area. In one embodiment, the wearable device (501) may transition from a low power state (593) to a normal state (591) in response to receiving the wake-up signal. In one embodiment, the wearable device (401) may request movement data from the wearable device (501) while the wearable device (501) is operating in the normal state (591). In one embodiment, the wearable device (401) may request movement data from the wearable device (501) while the hand (611) is positioned within a first distance from the interference area.

[0252] In operation 1250, the wearable device (401) may identify a gesture based on movement and / or movement data.

[0253] In one embodiment, the wearable device (401) can identify a first gesture based on one or more consecutive movements of a hand (611) identified through a camera (425). In one embodiment, the wearable device (401) can identify a first gesture based on one or more consecutive movements of a hand (611) while the wearable device (501) is operating in a normal state (591).

[0254] In one embodiment, the wearable device (401) can identify a second gesture (or pose) of the wearable device (501) based on movement data from the wearable device (501). In one embodiment, the wearable device (401) can identify movements of the wearable device (501) based on the movement data. In one embodiment, the wearable device (401) can identify a second gesture (or pose) of the wearable device (501) based on movements of the wearable device (501). In one embodiment, the wearable device (401) can identify the second gesture based on movement data acquired while the wearable device (501) operates in a normal state (591).

[0255] After operation 1250, the wearable device (401) may perform a set function in response to a user input based on the first gesture and / or the second gesture. In one embodiment, the wearable device (401) may perform a set function in response to a user input based on the first gesture and / or the second gesture obtained while the wearable device (501) is operating in a normal state (591).

[0256] In operation 1260, the wearable device (401) can identify a gesture based on a movement. In one embodiment, the wearable device (401) can identify a first gesture based on one or more consecutive movements of a hand (611) identified through a camera (425). In one embodiment, the wearable device (401) can identify the first gesture based on one or more consecutive movements of a hand (611) while the wearable device (501) is operating in a normal state (591).

[0257] After operation 1260, the wearable device (401) can perform a set function in response to a user input based on the first gesture.

[0258] Figure 13 is a flowchart illustrating the operation of a wearable device according to one embodiment.

[0259] FIG. 13 can be explained with reference to FIG. 1, FIG. 2a, FIG. 2b, FIG. 3a, FIG. 3b, FIG. 4, FIG. 5a, FIG. 5b, FIG. 5c, FIG. 5d, FIG. 6a, FIG. 6b, and FIG. 12.

[0260] Actions 1210, 1220, or 1230 of FIG. 13 may correspond to actions 1210, 1220, or 1230 of FIG. 12, respectively.

[0261] Referring to FIG. 13, in operation 1210, the wearable device (401) can identify the movement of the hand (611). In one embodiment, the wearable device (401) can identify the movement of the hand (611) within the field of view (600) of the camera (425).

[0262] In operation 1220, the wearable device (401) may set a first distance corresponding to the movement. In one embodiment, the wearable device (401) may identify the first distance from the interference area (620, 625) based on the movement of the hand (611).

[0263] In operation 1230, the wearable device (401) may determine whether the hand (611) is within a first distance from a disturbance area. In one embodiment, the wearable device (401) may identify whether the hand (611) is within the first distance from one of one or more disturbance areas (620, 625).

[0264] In operation 1230, in response to identifying that the hand (611) is within a first distance from the interference area, the wearable device (401) may perform operation 1240. In operation 1230, in response to identifying that the hand (611) is beyond the first distance from the interference area, the wearable device (401) may perform operation 1260.

[0265] In operation 1310, the wearable device (401) may transmit a wake-up signal to another wearable device (501). In one embodiment, the wearable device (401) may transmit the wake-up signal to the wearable device (501) worn on the hand (611) in response to identifying that the hand (611) is within a first distance from the interference area. In one embodiment, the wearable device (501) may receive the wake-up signal via the communication circuit (590). In one embodiment, the wearable device (501) may transition from a low power state (593) to a normal state (591) in response to receiving the wake-up signal. In one embodiment, the communication circuit (590) of the wearable device (501) may transition from a sleep state to an active state in response to receiving the wake-up signal. In one embodiment, as the wearable device (501) transitions from a low power state (593) to a normal state (591), the processor (520), the motion sensor (573), and the communication circuitry (590) of the wearable device (501) may transition to an active state.

[0266] In operation 1320, the wearable device (401) may transmit a sleep signal to another wearable device (501). In one embodiment, the wearable device (401) may transmit the sleep signal to the wearable device (501) worn on the hand (611) in response to identifying that the hand (611) has moved out of the first distance from the interference area. In one embodiment, the wearable device (501) may receive the sleep signal via the communication circuit (590). In one embodiment, the wearable device (501) may transition from a normal state (591) to a low power state (593) in response to receiving the sleep signal. In one embodiment, the communication circuit (590) of the wearable device (501) may transition from an active state to a sleep state in response to receiving the sleep signal. In one embodiment, as the wearable device (501) transitions from a normal state (591) to a low power state (593), at least some of the processor (520), motion sensor (573), or communication circuitry (590) of the wearable device (501) may transition to an inactive state.

[0267] In one embodiment, operation 1310 of FIG. 13 may be performed before operation 1240 of FIG. 12. In one embodiment, operation 1320 of FIG. 13 may be performed before operation 1260 of FIG. 12. However, this is not limited thereto.

[0268] Figure 14 is a flowchart illustrating the operation of a wearable device according to one embodiment.

[0269] FIG. 14 can be explained with reference to FIG. 1, FIG. 2a, FIG. 2b, FIG. 3a, FIG. 3b, FIG. 4, FIG. 5a, FIG. 5b, FIG. 5c, FIG. 5d, FIG. 6a, FIG. 6b, and FIG. 12.

[0270] Referring to FIG. 14, in operation 1410, the wearable device (401) can identify the movement of the hand (611). In one embodiment, the wearable device (401) can identify the movement of the hand (611) within the field of view (600) of the camera (425).

[0271] In operation 1420, the wearable device (401) may set a second distance corresponding to the movement. In one embodiment, the wearable device (401) may identify the second distance from the interference area (620, 625) based on the movement of the hand (611).

[0272] In operation 1430, the wearable device (401) may determine whether the hand (611) is within a second distance from a disturbance area. In one embodiment, the wearable device (401) may identify whether the hand (611) is within a second distance from one of the one or more disturbance areas (620, 625).

[0273] In operation 1430, the wearable device (401) may perform operation 1440 in response to identifying that the hand (611) is within a second distance from the interference area. In operation 1430, the wearable device (401) may perform operation 1460 in response to identifying that the hand (611) is greater than a second distance from the interference area.

[0274] In operation 1440, the wearable device (401) may transmit a connection request signal to another wearable device (501). In one embodiment, the wearable device (401) may transmit the connection request signal to the wearable device (501) worn on the hand (611) in response to identifying that the hand (611) is within a second distance from the interference area. In one embodiment, the wearable device (501) may receive the connection request signal via the communication circuit (590). In one embodiment, the wearable device (501) may transition from an ultra-low power state (595) to a low power state (593) in response to receiving the connection request signal. In one embodiment, the communication circuit (590) of the wearable device (501) may transition from a standby state to a sleep state in response to receiving the connection request signal.

[0275] In operation 1450, the wearable device (401) may transmit a connection termination signal to another wearable device (501). In one embodiment, the wearable device (401) may transmit the connection termination signal to the wearable device (501) worn on the hand (611) in response to identifying that the hand (611) has moved out of the second distance from the interference area. In one embodiment, the wearable device (501) may receive the connection termination signal via the communication circuit (590). In one embodiment, the wearable device (501) may transition from a low power state (593) to an ultra low power state (595) in response to receiving the connection termination signal. In one embodiment, the communication circuit (590) of the wearable device (501) may transition from a sleep state to a standby state in response to receiving the connection termination signal in the low power state (593).

[0276] As described above, the wearable device (101, 200, 300, 401) may include a communication circuit (435). The wearable device (101, 200, 300, 401) may include a camera (180, 240-2, 240-3, 340-5, 340-6, 340-7, 340-8, 340-9, 340-10, 425) arranged to capture an image of a part of the body of a user (500) wearing the wearable device (101, 200, 300, 401). The wearable device (101, 200, 300, 401) may include a processor (120, 410). The wearable device (101, 200, 300, 401) may include a memory (130, 415) including instructions. The instructions, when executed by the processor (120, 410), may cause the wearable device (101, 200, 300, 401) to identify relative movement of a hand (611) of a user (500) wearing another wearable device (501) in a field of view (600) of the camera (180, 240-2, 240-3, 340-5, 340-6, 340-7, 340-8, 340-9, 340-10, 425). The other wearable device (501) may be in a low power state (593) that stops acquiring movement data of the other wearable device (501) through the sensor (573) of the other wearable device (501). The above instructions, when executed by the processor (120, 410), may cause the wearable device (101, 200, 300, 401) to set a first area (630, 635) within a first distance corresponding to the relative movement from an obstruction area (620, 625) in which the hand (611) is not identified through the field of view (600) of the camera (180, 240-2, 240-3, 340-5, 340-6, 340-7, 340-8, 340-9, 340-10, 425).The above instructions, when executed by the processor (120, 410), may cause the wearable device (101, 200, 300, 401) to request the movement data from the other wearable device (501) through the communication circuit (435) in response to identifying that the hand (611) has moved into the first area (630, 635). The instructions, when executed by the processor (120, 410), may cause the wearable device (101, 200, 300, 401) to obtain movement data from the other wearable device (501) that transitions from the low power state (593) to the normal state (591) based on the hand (611) moving into the first area (630, 635) through the communication circuit (435). The instructions, when executed by the processor (120, 410), may cause the wearable device (101, 200, 300, 401) to identify a gesture of the user (500) through the hand (611) based on the movement data.

[0277] The above instructions, when executed by the processor (120, 410), may cause the wearable device (101, 200, 300, 401) to transmit a signal to the other wearable device (501) through the communication circuit (435) instructing it to transition to the low power state (593) in response to identifying that the hand (611) has moved out of the first area (630, 635).

[0278] The first distance may be a distance that the hand (611) can reach within the first time specified in the interference area (620, 625) according to the relative movement.

[0279] The above-mentioned interference area (620, 625) may be an area outside the field of view (600).

[0280] The above-mentioned obstruction area (620, 625) may be an area of ​​an obstruction object that may obscure the hand (611) depending on the relative movement of the hand (611) among the objects within the field of view (600).

[0281] The above-mentioned obstruction area (620, 625) may be an area of ​​an object that, among the obstruction objects that can obscure the hand (611), has a probability of the user (500) performing the gesture greater than or equal to a standard probability when the hand (611) is obstructed by the obstruction object.

[0282] The above instructions, when executed by the processor (120, 410), may cause the wearable device (101, 200, 300, 401) to establish a second area (640, 645) that is longer than the first distance and within a second distance corresponding to the relative movement from the interference area (620, 625). The above instructions, when executed by the processor (120, 410), may cause the wearable device (101, 200, 300, 401) to, in response to identifying that the hand (611) has moved into the second area (640, 645), transmit a signal to the other wearable device (501) through the communication circuit (435) requesting a communication connection with the other communication circuit (435) of the other wearable device (501).

[0283] The above instructions, when executed by the processor (120, 410), may cause the wearable device (101, 200, 300, 401) to transmit another signal to the other wearable device (501) through the communication circuit (435) to put the other communication circuit (435) of the other wearable device (501) to sleep in response to identifying that the hand (611) has moved out of the second area (640, 645).

[0284] The above instructions, when executed by the processor (120, 410), may cause the wearable device (101, 200, 300, 401) to identify a state of charge (SOC) of a battery of the other wearable device (501) through the communication circuit (435). The above instructions, when executed by the processor (120, 410), may cause the wearable device (101, 200, 300, 401) to set the second area (640, 645) if the SOC is below a specified state of charge.

[0285] The above instructions, when executed by the processor (120, 410), may cause the wearable device (101, 200, 300, 401) to identify the gesture of the user (500) based on the relative movement of the hand (611) without the motion data while the hand (611) is located outside the first area (630, 635).

[0286] The instructions, when executed by the processor (120, 410), may cause the wearable device (101, 200, 300, 401) to, in response to identifying that the hand (611) has moved into the first region (630, 635): when the first wearable device (101, 200, 300, 401) is worn at a second position of the hand (611) that is different from the first position of the hand (611) on which the other wearable device (501) is worn, to request other movement data of the other wearable device (501) from the other wearable device (501) through the communication circuit (435). The above instructions, when executed by the processor (120, 410), may cause the wearable device (101, 200, 300, 401) to request the movement data from the other wearable device (501) through the communication circuit (435) when the other wearable device (501) is not worn.

[0287] The instructions, when executed by the processor (120, 410), may cause the wearable device (101, 200, 300, 401) to identify a state of charge (SOC) of a battery of the other wearable device (501) through the communication circuit (435). The instructions, when executed by the processor (120, 410), may cause the wearable device (101, 200, 300, 401) to transmit a signal to the other wearable device (501) through the communication circuit (435) instructing it to transition to the low power state (593) when the SOC is below a designated state of charge.

[0288] As described above, the method can be performed in a wearable device (101, 200, 300, 401) including a communication circuit (435) and a camera (180, 240-2, 240-3, 340-5, 340-6, 340-7, 340-8, 340-9, 340-10, 425) arranged to capture an image of a part of the body of a user (500) wearing the wearable device (101, 200, 300, 401). The method may include an operation of identifying a relative movement of a hand (611) of the user (500) wearing another wearable device (501) in a field of view (600) of the camera (180, 240-2, 240-3, 340-5, 340-6, 340-7, 340-8, 340-9, 340-10, 425). The other wearable device (501) may be in a low power state (593) that stops acquiring movement data of the other wearable device (501) through a sensor (573) of the other wearable device (501). The method may include an operation of setting a first area (630, 635) within a first distance corresponding to the relative movement from an obstruction area (620, 625) in which the hand (611) is not identified through the field of view (600) of the camera (180, 240-2, 240-3, 340-5, 340-6, 340-7, 340-8, 340-9, 340-10, 425). The method may include an operation of requesting the movement data from the other wearable device (501) through the communication circuit (435) in response to identifying that the hand (611) is moved into the first area (630, 635). The method may include an operation of acquiring movement data from the other wearable device (501) transitioning from the low power state (593) to the normal state (591) based on the hand (611) moving into the first area (630, 635) via the communication circuit (435).The method may include an operation of identifying a gesture of the user (500) through the hand (611) based on the movement data.

[0289] The method may include, in response to identifying that the hand (611) has moved out of the first region (630, 635), transmitting a signal to the other wearable device (501) via the communication circuit (435) instructing it to transition to the low power state (593).

[0290] The first distance may be a distance that the hand (611) can reach within the first time specified in the interference area (620, 625) according to the relative movement.

[0291] The method may include an action of establishing a second area (640, 645) that is longer than the first distance and within a second distance corresponding to the relative movement from the interference area (620, 625). The method may include an action of transmitting, through the communication circuit (435), a signal to the other wearable device (501) requesting a communication connection with the other communication circuit (435) of the other wearable device (501), in response to identifying that the hand (611) is moved into the second area (640, 645).

[0292] The method may include, in response to identifying that the hand (611) has moved out of the second area (640, 645), transmitting another signal to the other wearable device (501) through the communication circuit (435) to put the other communication circuit (435) of the other wearable device (501) to sleep.

[0293] The method may include an operation of identifying a state of charge (SOC) of a battery of the other wearable device (501) through the communication circuit (435). The method may include an operation of setting the second area (640, 645) when the SOC is below a specified state of charge.

[0294] As described above, a non-transitory computer readable storage medium can store a program including instructions. The above instructions, when executed by a processor (120, 410) of the wearable device (101, 200, 300, 401) including a communication circuit (435) and a camera (180, 240-2, 240-3, 340-5, 340-6, 340-7, 340-8, 340-9, 340-10, 425) arranged to capture an image of a part of the body of a user (500) wearing the wearable device (101, 200, 300, 401), cause the wearable device (101, 200, 300, 401) to capture an image of the camera (180, 240-2, 240-3, 340-5, 340-6, 340-7, The other wearable device (501) may be caused to identify relative movement of the hand (611) of the user (500) in the field of view (600) of the other wearable device (501). The other wearable device (501) may be in a low power state (593) that stops acquiring movement data of the other wearable device (501) through the sensor (573) of the other wearable device (501). The above instructions, when executed by the processor (120, 410), may cause the wearable device (101, 200, 300, 401) to set a first area (630, 635) within a first distance corresponding to the relative movement from an obstruction area (620, 625) in which the hand (611) is not identified through the field of view (600) of the camera (180, 240-2, 240-3, 340-5, 340-6, 340-7, 340-8, 340-9, 340-10, 425).The above instructions, when executed by the processor (120, 410), may cause the wearable device (101, 200, 300, 401) to request the movement data from the other wearable device (501) through the communication circuit (435) in response to identifying that the hand (611) has moved into the first area (630, 635). The instructions, when executed by the processor (120, 410), may cause the wearable device (101, 200, 300, 401) to obtain movement data from the other wearable device (501) that transitions from the low power state (593) to the normal state (591) based on the hand (611) moving into the first area (630, 635) through the communication circuit (435). The instructions, when executed by the processor (120, 410), may cause the wearable device (101, 200, 300, 401) to identify a gesture of the user (500) through the hand (611) based on the movement data.

[0295] The above instructions, when executed by the processor (120, 410), may cause the wearable device (101, 200, 300, 401) to transmit a signal to the other wearable device (501) through the communication circuit (435) instructing it to transition to the low power state (593) in response to identifying that the hand (611) has moved out of the first area (630, 635).

[0296] Electronic devices according to the various embodiments disclosed in this document may take various forms. Electronic devices may include, for example, portable communication devices (e.g., smartphones), computer devices, portable multimedia devices, portable medical devices, cameras, wearable devices, or home appliances. Electronic devices according to the embodiments of this document are not limited to the aforementioned devices.

[0297] The various embodiments of this document and the terminology used therein are not intended to limit the technical features described in this document to specific embodiments, but should be understood to include various modifications, equivalents, or substitutes of the embodiments. In connection with the description of the drawings, similar reference numerals may be used for similar or related components. The singular form of a noun corresponding to an item may include one or more of the items, unless the context clearly indicates otherwise. In this document, each of the phrases "A or B", "at least one of A and B", "at least one of A or B", "A, B, or C", "at least one of A, B, and C", and "at least one of A, B, or C" can include any one of the items listed together in the corresponding phrase among those phrases, or all possible combinations thereof. Terms such as "first," "second," or "first" or "second" may be used merely to distinguish one component from another, and do not limit the components in any other respect (e.g., importance or order). When a component (e.g., a first component) is referred to as "coupled" or "connected" to another component (e.g., a second component), with or without the terms "functionally" or "communicatively," it means that the component can be connected to the other component directly (e.g., wired), wirelessly, or through a third component.

[0298] The term "module" used in various embodiments of this document may include a unit implemented in hardware, software, or firmware, and may be used interchangeably with terms such as logic, logic block, component, or circuit. A module may be an integral component, or a minimum unit or part of such a component that performs one or more functions. For example, according to one embodiment, a module may be implemented in the form of an application-specific integrated circuit (ASIC).

[0299] Various embodiments of the present document may be implemented as software (e.g., a program (140)) including one or more instructions stored in a storage medium (e.g., an internal memory (136) or an external memory (138)) readable by a machine (e.g., an electronic device (101)). For example, a processor (e.g., a processor (120)) of the machine (e.g., an electronic device (101)) may call at least one instruction among the one or more instructions stored from the storage medium and execute it. This enables the machine to operate to perform at least one function according to the at least one called instruction. The one or more instructions may include code generated by a compiler or code executable by an interpreter. The machine-readable storage medium may be provided in the form of a non-transitory storage medium. Here, 'non-transitory' simply means that the storage medium is a tangible device and does not contain signals (e.g., electromagnetic waves), and the term does not distinguish between cases where data is stored semi-permanently or temporarily on the storage medium.

[0300] According to one embodiment, the method according to various embodiments disclosed in this document may be provided as included in a computer program product. The computer program product may be traded as a product between a seller and a buyer. The computer program product may be distributed in the form of a machine-readable storage medium (e.g., a compact disc read-only memory (CD-ROM)), or may be distributed online (e.g., by download or upload) through an application store (e.g., Play Store™) or directly between two user devices (e.g., smart phones). In the case of online distribution, at least a portion of the computer program product may be temporarily stored or temporarily generated in a machine-readable storage medium, such as the memory of a manufacturer's server, an application store's server, or an intermediary server.

[0301] According to various embodiments, each component (e.g., a module or a program) of the above-described components may include one or more entities, and some of the entities may be separated and placed in other components. According to various embodiments, one or more components or operations of the aforementioned components may be omitted, or one or more other components or operations may be added. Alternatively or additionally, a plurality of components (e.g., a module or a program) may be integrated into a single component. In such a case, the integrated component may perform one or more functions of each of the plurality of components identically or similarly to those performed by the corresponding component among the plurality of components prior to the integration. According to various embodiments, the operations performed by a module, program, or other component may be executed sequentially, in parallel, iteratively, or heuristically, or one or more of the operations may be executed in a different order, omitted, or one or more other operations may be added.

Claims

1. In a wearable device (101, 200, 300, 401), Communication circuit (435), A camera (180, 240-2, 240-3, 340-5, 340-6, 340-7, 340-8, 340-9, 340-10, 425) arranged to capture an image of a part of the body of a user (500) wearing the wearable device (101, 200, 300, 401) Processor (120, 410), and Contains memory (130, 415) containing instructions, When the above instructions are executed by the processor (120, 410), the wearable device (101, 200, 300, 401) In the field of view (600) of the above camera (180, 240-2, 240-3, 340-5, 340-6, 340-7, 340-8, 340-9, 340-10, 425), the other wearable device (501) identifies the relative movement of the hand (611) of the user (500), and the other wearable device (501) is in a low power state (593) that stops acquiring movement data of the other wearable device (501) through the sensor (573) of the other wearable device (501). A first area (630, 635) is set within a first distance corresponding to the relative movement from an interference area (620, 625) where the hand (611) is not identified through the field of view (600) of the camera (180, 240-2, 240-3, 340-5, 340-6, 340-7, 340-8, 340-9, 340-10, 425). In response to identifying that the hand (611) is moved into the first area (630, 635), the movement data is requested from the other wearable device (501) through the communication circuit (435). Through the above communication circuit (435), movement data is acquired from the other wearable device (501) that transitions from the low power state (593) to the normal state (591) based on the hand (611) moving into the first area (630, 635), Based on the above movement data, causing the user's (500) gesture through the hand (611) to be identified, Wearable devices.

2. In claim 1, When the above instructions are executed by the processor (120, 410), the wearable device (101, 200, 300, 401) In response to identifying that the hand (611) has moved out of the first region (630, 635), causing the other wearable device (501) to transmit a signal through the communication circuit (435) to indicate a transition to the low power state (593). Wearable devices.

3. In claim 1, The above first distance is a distance that the hand (611) can reach within the first time specified in the interference area (620, 625) according to the relative movement. Wearable devices.

4. In claim 1, The above interference area (620, 625) is an area outside the field of view (600). Wearable devices.

5. In claim 1, The above-mentioned obstruction area (620, 625) is an area of ​​an obstruction object that can obscure the hand (611) depending on the relative movement of the hand (611) among the objects within the field of view (600). Wearable devices.

6. In claim 5, The above-mentioned obstruction area (620, 625) is an area of ​​an object that has a probability of the user (500) performing the gesture when the hand (611) is obstructed by the obstruction object among the obstruction objects that can obstruct the hand (611) and is greater than the standard probability. Wearable devices.

7. In claim 1, When the above instructions are executed by the processor (120, 410), the wearable device (101, 200, 300, 401) A second area (640, 645) is set longer than the first distance and within a second distance corresponding to the relative movement from the interference area (620, 625), In response to identifying that the hand (611) is moved into the second area (640, 645), causing the other wearable device (501) to transmit a signal requesting a communication connection with the other communication circuit (435) of the other wearable device (501) through the communication circuit (435). Wearable devices.

8. In claim 7, When the above instructions are executed by the processor (120, 410), the wearable device (101, 200, 300, 401) In response to identifying that the hand (611) has moved out of the second area (640, 645), causing the other wearable device (501) to transmit another signal to put the other communication circuit (435) of the other wearable device (501) to sleep, Wearable devices.

9. In claim 8, When the above instructions are executed by the processor (120, 410), the wearable device (101, 200, 300, 401) The state of charge (SOC) of the battery of the other wearable device (501) is identified through the above communication circuit (435), If the above SOC is below the specified state of charge, causing the second area (640, 645) to be set, Wearable devices.

10. In claim 1, When the above instructions are executed by the processor (120, 410), the wearable device (101, 200, 300, 401) While said hand (611) is positioned outside said first area (630, 635), causing said gesture of said user (500) to be identified based on said relative movement of said hand (611) without said motion data. Wearable devices.

11. In claim 1, When the above instructions are executed by the processor (120, 410), the wearable device (101, 200, 300, 401) In response to identifying that the hand (611) has moved into the first region (630, 635): When the first wearable device (101, 200, 300, 401) is worn on a second position of the hand (611) that is different from the first position of the hand (611) on which the other wearable device (501) is worn, the other movement data of the other wearable device (501) is requested to the other wearable device (501) through the communication circuit (435). When the other wearable device (501) is not worn, the communication circuit (435) causes the other wearable device (501) to request the movement data. Wearable devices.

12. In claim 1, When the above instructions are executed by the processor (120, 410), the wearable device (101, 200, 300, 401) The state of charge (SOC) of the battery of the other wearable device (501) is identified through the above communication circuit (435), When the SOC is below the specified charging state, causing the other wearable device (501) to transmit a signal to instruct transition to the low power state (593) through the communication circuit (435). Wearable devices.

13. A method performed in a wearable device (101, 200, 300, 401), comprising a communication circuit (435) and a camera (180, 240-2, 240-3, 340-5, 340-6, 340-7, 340-8, 340-9, 340-10, 425) arranged to capture an image of a part of the body of a user (500) wearing the wearable device (101, 200, 300, 401), An operation of identifying a relative movement of a hand (611) of a user (500) wearing another wearable device (501) in a field of view (600) of the above camera (180, 240-2, 240-3, 340-5, 340-6, 340-7, 340-8, 340-9, 340-10, 425), wherein the other wearable device (501) is in a low power state (593) that has stopped acquiring movement data of the other wearable device (501) through a sensor (573) of the other wearable device (501). An operation of setting a first area (630, 635) within a first distance corresponding to the relative movement from an interference area (620, 625) where the hand (611) is not identified through the field of view (600) of the camera (180, 240-2, 240-3, 340-5, 340-6, 340-7, 340-8, 340-9, 340-10, 425), In response to identifying that the hand (611) is moved into the first area (630, 635), an action of requesting the movement data to the other wearable device (501) through the communication circuit (435). An operation of acquiring movement data from the other wearable device (501) that transitions from the low power state (593) to the normal state (591) based on the hand (611) moving into the first area (630, 635) through the communication circuit (435), and Based on the above movement data, an action is included to identify a gesture of the user (500) through the hand (611). method.

14. In claim 13, In response to identifying that the hand (611) has moved out of the first area (630, 635), an action of transmitting a signal to the other wearable device (501) through the communication circuit (435) to instruct it to transition to the low power state (593) is included. method.

15. In a non-transitory computer readable storage medium, Save a program containing instructions, The above instructions, when executed by a processor (120, 410) of the wearable device (101, 200, 300, 401) including a communication circuit (435) and a camera (180, 240-2, 240-3, 340-5, 340-6, 340-7, 340-8, 340-9, 340-10, 425) arranged to capture an image of a part of the body of a user (500) wearing the wearable device (101, 200, 300, 401), cause the wearable device (101, 200, 300, 401) to: In the field of view (600) of the above camera (180, 240-2, 240-3, 340-5, 340-6, 340-7, 340-8, 340-9, 340-10, 425), the other wearable device (501) identifies the relative movement of the hand (611) of the user (500), and the other wearable device (501) is in a low power state (593) that stops acquiring movement data of the other wearable device (501) through the sensor (573) of the other wearable device (501). A first area (630, 635) is set within a first distance corresponding to the relative movement from an interference area (620, 625) where the hand (611) is not identified through the field of view (600) of the camera (180, 240-2, 240-3, 340-5, 340-6, 340-7, 340-8, 340-9, 340-10, 425). In response to identifying that the hand (611) is moved into the first area (630, 635), the movement data is requested from the other wearable device (501) through the communication circuit (435). Through the above communication circuit (435), movement data is acquired from the other wearable device (501) that transitions from the low power state (593) to the normal state (591) based on the hand (611) moving into the first area (630, 635), Based on the above movement data, causing the user's (500) gesture through the hand (611) to be identified, A non-transitory computer-readable recording medium.

Images