Wearable electronic device for performing reset and electronic device connected to wearable electronic device

Abstract

A wearable electronic device is disclosed. The wearable electronic device may: establish a wireless communication connection to an external electronic device; when a request message for an authentication request—the request message including information on an action designated for authentication—is received from the external electronic device or the wireless communication connection to the external electronic device is established, determine the action on the basis of state information of the wearable electronic device, and determine whether the action has occurred; determine that the authentication has been successful when occurrence of the action has been determined by detecting at least one of the wearable electronic device being charged by another external electronic device and the presence or absence of a user input being performed for the other external electronic device; transmit a response message indicating the success of the authentication to the external electronic device; after transmitting the response message, receive a reset request from the external electronic device; and perform a reset on the basis of the received reset request.

Description

Wearable electronic device performing reset and electronic device connected thereto

[0001] The embodiment relates to a wearable electronic device performing a reset and an electronic device connected thereto.

[0002] Ring-type wearable electronic devices are worn on a part of the user's body (e.g., a finger) and can perform various functions. For example, ring-type wearable electronic devices can utilize at least one sensor to monitor the user's health status (e.g., heart rate, sleep patterns, activity level, and / or stress level).

[0003] Ring-type wearable electronic devices may not include interfaces capable of input and output (e.g., a touch display). Certain operations (e.g., initialization operations) may require user confirmation (or consent). However, ring-type wearable electronic devices may lack interfaces capable of input and output, making it difficult to obtain user confirmation (or consent) and guide (or induce) the user through the initialization process.

[0004] In one embodiment, authentication may be performed on the wearable electronic device, and guidance (or induction) for initialization of the wearable electronic device may be performed on an external electronic device.

[0005] According to one embodiment, a wearable electronic device may include at least one processor including a processing circuit and a memory storing instructions. The instructions, when individually or collectively executed by the at least one processor, may cause the wearable electronic device to establish a wireless communication connection with an external electronic device. The instructions, when individually or collectively executed by the at least one processor, may cause the wearable electronic device to receive a request message for an authentication request, the request message including information about an action designated for authentication, from the external electronic device or to determine the action based on status information of the wearable electronic device. The instructions, when individually or collectively executed by the at least one processor, may cause the wearable electronic device to determine whether the action has occurred. The instructions, when individually or collectively executed by the at least one processor, may cause the wearable electronic device to determine that the authentication is successful and transmit a response message indicating the success of the authentication to the external electronic device when the wearable electronic device determines that the action has occurred by detecting at least one of whether the wearable electronic device is being charged by another external electronic device and whether a user input has been performed to the another external electronic device. The instructions, when individually or collectively executed by the at least one processor, may cause the wearable electronic device to receive a reset request from the external electronic device after transmitting the response message. The instructions, when individually or collectively executed by the at least one processor, may cause the wearable electronic device to perform a reset operation based on the received reset request.

[0006] According to one embodiment, an electronic device may include at least one processor including a processing circuit and a memory storing instructions. The instructions, when individually or collectively executed by the at least one processor, may cause the electronic device to establish a wireless communication connection with a wearable electronic device. The instructions, when individually or collectively executed by the at least one processor, may cause the electronic device to transmit a request message indicating an authentication request to the wearable electronic device, the request message including information about an action determined by the electronic device based on state information of the wearable electronic device for authentication, or to receive information about the action determined by the wearable electronic device from the wearable electronic device. The instructions, when individually or collectively executed by the at least one processor, may cause the electronic device to provide guidance regarding the action to a user. The instructions, when individually or collectively executed by the at least one processor, may cause the electronic device to receive a response message from the wearable electronic device indicating that the action has occurred and the authentication has succeeded. The instructions, when individually or collectively executed by the at least one processor, may cause the electronic device to transmit a reset request to the wearable electronic device based on the response message. The action may include at least one of an action in which the wearable electronic device is charged by another electronic device and an action in which a user input is generated for the another electronic device.

[0007] FIG. 1 is a block diagram of an electronic device within a network environment according to one embodiment.

[0008] FIG. 2 is a drawing illustrating an example of the structure of a wearable electronic device according to one embodiment.

[0009] FIGS. 3A and 3B are diagrams illustrating examples of the operation of a wearable electronic device according to one embodiment.

[0010] FIGS. 4A and 4B are flowcharts illustrating examples of operations of a wearable electronic device and an external electronic device according to one embodiment.

[0011] FIGS. 5A and 5B are drawings illustrating a wearable electronic device and a cradle according to one embodiment.

[0012] FIG. 6 is a drawing illustrating an example of a search operation of an external electronic device according to one embodiment.

[0013] FIG. 7 is a drawing illustrating an example of a guide operation of an external electronic device according to one embodiment.

[0014] FIG. 8 is a drawing illustrating an example of a pop-up screen of an external electronic device according to one embodiment.

[0015] FIG. 9 is a block diagram illustrating an example of a wearable electronic device according to one embodiment.

[0016] FIG. 10 is a block diagram illustrating an example of an electronic device according to one embodiment.

[0017] FIG. 11 is a flowchart illustrating another example of the operation of a wearable electronic device and an external electronic device according to one embodiment.

[0018] FIG. 12 is a diagram illustrating an example of the operation of a wearable electronic device and a plurality of electronic devices according to one embodiment.

[0019] Hereinafter, embodiments will be described in detail with reference to the attached drawings. In the description with reference to the attached drawings, identical components are assigned the same reference numerals regardless of the drawing numbers, and redundant descriptions thereof will be omitted.

[0020] FIG. 1 is a block diagram of an electronic device within a network environment according to one embodiment.

[0021] 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 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)).

[0022] The processor (120) may control at least one other component (e.g., a hardware or software component) of the electronic device (101) connected to the processor (120) by executing, for example, software (e.g., a program (140)), and may perform various data processing or calculations. According to one embodiment, as at least a part of the data processing or calculation, the processor (120) may store a command or data received from another component (e.g., a sensor module (176) or a communication module (190)) in a volatile memory (132), process the command or data stored in the volatile memory (132), and store the resulting 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 a secondary 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 therewith. For example, if the electronic device (101) includes a main processor (121) and a secondary processor (123), the secondary processor (123) may be configured to use less power than the main processor (121) or to be specialized for a specified function. The secondary processor (123) may be implemented separately from the main processor (121) or as a part thereof.

[0023] The auxiliary processor (123) may control at least a part 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.

[0024] 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).

[0025] 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).

[0026] 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).

[0027] 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. According to one embodiment, the receiver can be implemented separately from the speaker or as part of the speaker.

[0028] 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.

[0029] 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).

[0030] 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.

[0031] 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.

[0032] 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).

[0033] A 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.

[0034] 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.

[0035] 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).

[0036] 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.

[0037] 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).

[0038] 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) may support a peak data rate (e.g., 20 Gbps or more) for eMBB realization, a loss coverage (e.g., 164 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 1 ms or less for round trip) for URLLC realization.

[0039] The antenna module (197) can transmit or receive signals or power to or from an external device (e.g., an external electronic device). According to 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). According to 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 selected at least one antenna. According to 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).

[0040] In one embodiment, 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.

[0041] 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)).

[0042] 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.

[0043]

[0044] FIG. 2 is a drawing illustrating an example of the structure of a wearable electronic device according to one embodiment.

[0045] Referring to FIG. 2, a cross-sectional view (201) and a side perspective view (202) of a wearable electronic device (200) (e.g., the electronic device (102) of FIG. 1) are illustrated. The wearable electronic device (200) can be worn on a user's finger. The wearable electronic device (200) can be a ring-shaped electronic device or a smart ring. The wearable electronic device (200) can be designed to have a hole in the center. The wearable electronic device (200) can be formed of an outer portion and an inner portion. The outer portion of the wearable electronic device (200) can be implemented to withstand external impact and scratches. The outer portion of the wearable electronic device (200) can be implemented with a material capable of implementing design elements (e.g., titanium, stainless steel, and / or ceramic). The inner portion of the wearable electronic device (200) can be a portion that comes into contact with a finger. The interior of the wearable electronic device (200) may be implemented with the same material as the exterior or with a material for sensing (e.g., molding material, transparent plastic, glass, and / or metal material).

[0046] According to one embodiment, a wearable electronic device (200) may include a communication circuit (210), an antenna (211), a processor (220), a memory (230), a flexible printed circuit board (FPCB) (240), a battery (250), a charging interface (251), a power management integrated circuit (PMIC) (252), an inertial sensor (260), a photoplethysmogram (PPG) sensor (270), and a temperature sensor (280). Depending on the implementation, at least some of the sensors (260, 270, and 280) may be omitted from the wearable electronic device (200).

[0047] According to one embodiment, the communication circuit (210) may support the establishment of a direct (e.g., wired) communication channel or a wireless communication channel between the wearable electronic device (200) and an external electronic device (e.g., the electronic device (101) of FIG. 1). The communication circuit (210) may support communication based on the established communication channel. The communication circuit (210) may support various communication methods (e.g., Bluetooth, BLE (Bluetooth Low Energy), ZigBee, ANT+, Wi-Fi, Cellular (LTE, 5G, 6G, NB-IoT), NFC (near field communication), RFID (radio-frequency identification), UWB (ultra wide band), and / or GNSS (global navigation satellite system)). The communication circuit (210) may operate independently from the processor (220), or may be implemented in an integrated form with the processor (220). The antenna (211) may be an antenna for wireless communication. The antenna (211) may be implemented as a single antenna or multiple antennas. The antenna (211) may also be implemented as part of the exterior of the wearable electronic device (200).

[0048] According to one embodiment, the processor (220) can perform various data processing or calculations. The processor (220) can store commands or data received from other components (e.g., sensors (e.g., 260, 270, and / or 280) or communication circuits (210)) in the memory (230), process the commands or data stored in the memory (230), and store result data in the memory (230). According to one embodiment, the processor (220) can include a main processor (e.g., a central processing unit or an application processor) or an auxiliary processor (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 therewith. The processor (220) can be implemented in an integrated form with other components (e.g., sensors (e.g., 260, 270, and / or 280) and / or the communication circuits (210)).

[0049] According to one embodiment, the memory (230) may store various data used by at least one component (e.g., processor (220) and / or sensors (e.g., 260, 270, and / or 280)) of the wearable electronic device (200). The data may include, for example, software (e.g., a program). The data may include input data or output data for commands related to the software.

[0050] According to one embodiment, the FPCB (240) may be an electrical circuit board having flexible characteristics. Components (e.g., a processor (220), a memory (230), a sensor (e.g., 260, 270, and / or 280), and / or a battery (250)) may be placed on the FPCB (240). The components placed on the FPCB (240) may be electrically connected.

[0051] According to one embodiment, the battery (250) can store energy to power the wearable electronic device (200). The battery (250) can be charged and discharged and can be formed of various materials (e.g., lithium ion, mercury, or dry cell). The battery (250) can be equipped with a flexible battery pack to be placed inside the wearable electronic device (200). The charging interface (251) can support various charging methods (e.g., wired charging method and / or wireless charging method) of the wearable electronic device (200). The PMIC (252) can manage power of the wearable electronic device (200). The PMIC (252) can appropriately distribute power to components (e.g., processor (220) or sensors (e.g., 260, 270, and / or 280)).

[0052] According to one embodiment, the inertial sensor (260) may be a sensor that detects the inertia of the wearable electronic device (200). The inertial sensor (260) may include an acceleration sensor and / or a gyroscope sensor. The inertial sensor (260) may be implemented as a three-axis sensor, including a three-axis acceleration sensor. The inertial sensor (260) may be implemented as a six-axis sensor, including a three-axis acceleration sensor and a three-axis gyro sensor. The inertial sensor (260) may sense motion, gesture, impact, posture, and / or activity of the wearable electronic device (200) (or a wearer of the wearable electronic device (200)). The inertial sensor (260) may monitor shaking information of the wearable electronic device (200). A wearable electronic device (200) may include a location measurement circuit (e.g., a GPS circuit) (or a GPS sensor). Through the location measurement circuit (e.g., a GPS circuit) (or a GPS sensor), the wearable electronic device (200) may obtain its own location information.

[0053] According to one embodiment, the PPG sensor (270) can irradiate light onto a living body (e.g., a wearer's body). The PPG sensor (270) can receive light that is absorbed, scattered, and / or reflected. The PPG sensor (270) can include an emitter (271), a light receiver (272), and a control unit (273).

[0054] According to one embodiment, the PPG sensor (270) can irradiate light to a living body (e.g., a wearer's body) (e.g., a blood vessel) through a light-emitting unit (271). The light-emitting unit (271) can emit light of various bands. For example, the first light-emitting unit (271-1) can emit light of an infrared wavelength, the second light-emitting unit (271-2) can emit green light of a visible light wavelength, and the third light-emitting unit (271-3) can emit red light of a visible light wavelength. The first to third light-emitting units (271-1, 271-2, 271-3) can be implemented with various elements (e.g., a light-emitting diode (LED), a laser, or a vertical cavity surface emitting laser (VCSEL)).

[0055] According to one embodiment, the PPG sensor (270) can receive light absorbed, scattered, and / or reflected through the light receiving unit (272). The light receiving unit (272) can receive the result of the reflected or transmitted light. The light receiving unit (272) can be implemented as a photodiode and / or a complementary metal-oxide semiconductor (CMOS)-based image sensor. The light receiving unit (272) can convert the received light based on an analog to digital converter (ADC). The light receiving unit (272) can store the result of converting the received light in a memory (e.g., the memory (230) of FIG. 2) or a sensor buffer (not shown).

[0056] According to one embodiment, the PPG sensor (270) can control the light emitting unit (271) and the light receiving unit (272) through the control unit (273). The control unit (273) can process data (e.g., convert the received light and store the converted result in the memory (230)).

[0057] According to one embodiment, the temperature sensor (280) may be a sensor that measures the temperature of a living body or a component. The temperature sensor (280) may measure the temperature in a contact or non-contact manner. The temperature sensor (280) may store the measured temperature value in the memory (230). The temperature sensor (280) may transmit the measured temperature value to the processor (220), thereby allowing the processor (220) to estimate the skin temperature. The wearable electronic device (200) may include a sensor that detects the user's finger (e.g., a sensor that detects whether the device is being worn).

[0058] According to one embodiment, the sensors (e.g., 260, 270, 280, and / or the wearing detection sensor) may be selectively activated depending on the operating mode of the wearable electronic device (200). For example, in a mode (e.g., health tracking mode) in which the wearable electronic device (200) is worn on a user's finger to track health status and / or activity information of the user (e.g., the wearer of the wearable electronic device (200)), the sensors (e.g., 260, 270, 280, and the wearing detection sensor) may be activated. For example, when the user's finger is not detected, at least some of the sensors (e.g., 260, 270, and 280) may be deactivated and the wearing detection sensor may be activated.

[0059]

[0060] FIGS. 3A and 3B are diagrams illustrating examples of the operation of a wearable electronic device according to one embodiment.

[0061] In the examples illustrated in FIGS. 3A and 3B, a wearable electronic device (300) according to one embodiment (e.g., the wearable electronic device (200) of FIG. 2) may not have an interface capable of input and output (e.g., a touch display).

[0062] The wearable electronic device (300) of FIG. 3A may not have an interface (e.g., a touch display) capable of input and output, so it may be difficult for the wearable electronic device (300) to obtain user confirmation (or user consent) from the user for resetting the wearable electronic device (300). According to one embodiment, the electronic device (305) (e.g., the electronic device (101) of FIG. 1) may induce the user to reset the wearable electronic device (300) by providing the user with a guide for a specified action, and may obtain user confirmation (or user consent) for resetting the wearable electronic device (300).

[0063] In the example illustrated in FIG. 3B, a wireless communication connection (e.g., BLE connection) between the wearable electronic device (300) and the first electronic device (310) may be disconnected. If the wireless communication connection is disconnected, the wearable electronic device (300) may operate in an automatic connection mode. The automatic connection mode may refer to a mode in which the wearable electronic device (300) is automatically connected to an electronic device (hereinafter, referred to as an “existing electronic device”) (e.g., the first electronic device (310)) to which it was previously connected, since wireless communication connection information (e.g., BLE connection information) remains unreset.

[0064] A user of a wearable electronic device (300) may not use the first electronic device (310) and may use the second electronic device (320). The second electronic device (320) may be an electronic device that has never been connected to the wearable electronic device (300). If the wearable electronic device (300) is not reset, the wearable electronic device (300) may only attempt to automatically form a connection with the first electronic device (310) in an automatic connection mode and may not attempt to automatically form a connection with the second electronic device (320). Since the wearable electronic device (300) does not have an interface (e.g., a touch display) capable of input and output, it may be difficult for the wearable electronic device (300) to obtain user confirmation (or user consent) from the user for resetting the wearable electronic device (300). According to one embodiment, the second electronic device (320) can induce the user to reset the wearable electronic device (300) by providing the user with a guide for a designated action and obtain user confirmation (or user consent) for resetting the wearable electronic device (300).

[0065]

[0066] FIGS. 4A and 4B are flowcharts illustrating examples of operations of a wearable electronic device and an external electronic device according to one embodiment.

[0067] Referring to FIG. 4A, in operation 411, the wearable electronic device (400) (e.g., the wearable electronic device (200) of FIG. 2, the wearable electronic device (300) of FIG. 3) may operate in a first mode. The first mode may represent, for example, an automatic connection mode, but is not limited thereto. The first mode may represent a mode other than a setup mode, which will be described later. According to one embodiment, the first mode may be changed to the first mode when the wearable electronic device (400) enters a charging state. According to another embodiment, the wearable electronic device (400) may operate in the first mode when a wireless communication connection with an existing electronic device (e.g., the first electronic device (310) of FIG. 3B) is lost.

[0068] In operation 413, the wearable electronic device (400) may perform advertising. For example, the wearable electronic device (400) may broadcast a first advertising message. The first advertising message may include information indicating that the wearable electronic device (400) is in a first mode and a device identifier of the wearable electronic device (400). In operation 413, the wearable electronic device (400) may perform advertising at a speed faster than a predetermined speed.

[0069] In operation 415, an external electronic device (401) (e.g., electronic device (305) of FIG. 3A, second electronic device (320) of FIG. 3B) may perform a search (or scanning). Through the search (or scanning), the external electronic device (401) may find a wearable electronic device (400) broadcasting a first advertising message.

[0070] In operation 417, the external electronic device (401) may determine the wearable electronic device (400) as a connection target among one or more devices in the search results. For example, the external electronic device (401) may identify one or more devices connectable to the external electronic device (401) through a search (or scanning) and display a list including one or more devices connectable to the external electronic device (401) on the display. The list may include the wearable electronic device (400). If there is a selection input for the wearable electronic device (400) in the list, the external electronic device (401) may determine the wearable electronic device (400) as a connection target.

[0071] According to one embodiment, when the wearable electronic device (400) is determined as a connection target, the external electronic device (401) can identify the device identifier of the wearable electronic device (400) through the first advertising message of the wearable electronic device (400), and can identify the device type (e.g., watch type, glasses type, or ring type) of the wearable electronic device (400) through the device identifier. When the wearable electronic device (400) corresponds to a device type (e.g., ring type) that cannot visually provide a reset induction to the user, the external electronic device (401) can perform an induction operation for reset (e.g., operations 425 and 427 to be described below). When the wearable electronic device (400) corresponds to a device type (e.g., watch type) that can visually provide a reset induction to the user, the external electronic device (401) may not perform operations 425 and 427 to be described below.

[0072] In operation 419, the wearable electronic device (400) and the external electronic device (401) may form a wireless communication connection (e.g., a BLE GATT (general attribute profile) connection). For example, if the external electronic device (401) determines the wearable electronic device (400) as a connection target, the external electronic device (401) may transmit a wireless communication connection request (e.g., a BLE GATT connection request) to the wearable electronic device (400). If the wearable electronic device (400) receives the wireless communication connection request (e.g., a BLE connection request), the wearable electronic device (400) may form a wireless communication connection (e.g., a BLE GATT connection) with the external electronic device (401).

[0073] In operation 421, an external electronic device (401) may request status information from a wearable electronic device (400).

[0074] In operation 423, the wearable electronic device (400) may transmit status information of the wearable electronic device (400) to an external electronic device (401). The status information of the wearable electronic device (400) may include at least one of a status of whether the wearable electronic device (400) is being charged, a status of whether the wearable electronic device (400) is being worn, or a status of whether an external input (e.g., a physical input) is being applied to the wearable electronic device (400).

[0075] For example, the wearable electronic device (400) can transmit status information indicating a charging status to an external electronic device (401) when the wearable electronic device (400) is being charged. The wearable electronic device (400) can transmit status information indicating a wearing status to the external electronic device (401) when the wearable electronic device (400) is being worn by a user. The wearable electronic device (400) can transmit status information indicating a non-charging status and a non-wearing status to the external electronic device (401) when the wearable electronic device (400) is not being charged and is not being worn by a user. The wearable electronic device (400) can transmit status information indicating that an external input is being applied to the external electronic device (401) when a physical input is being applied to the wearable electronic device (400) by an external element.

[0076] In operation 425, the external electronic device (401) may determine an action for authentication (or an action related to authentication) based on the status information of the wearable electronic device (400). The action may include, for example, an action (or event) desired to occur (or be performed) in the wearable electronic device (400) for authentication.

[0077] According to one embodiment, the status information and actions of the wearable electronic device (400) may be mapped in advance. Table 1 below shows examples of actions, and Table 2 below shows examples of mapping between the status information and actions of the wearable electronic device (400).

[0078]

[0079]

[0080] For example, when the status information of the wearable electronic device (400) indicates an uncharged state and an unworn state, the external electronic device (401) may determine at least one of the actions (e.g., the first action, the second action, and the sixth action) mapped to the “uncharged state and unworn state” as an action desired to be generated from the wearable electronic device (400).

[0081] According to another embodiment, the external electronic device (401) may randomly determine (or select) at least one action from among a plurality of actions (e.g., the first to seventh actions of Table 1 above) using status information of the wearable electronic device (400).

[0082] In operation 427, the external electronic device (401) may provide the user with guidance regarding the determined action. For example, the external electronic device (401) may display a guide screen regarding the determined action on the display of the external electronic device (401). The guide screen will be described later with reference to FIG. 7.

[0083] In operation 429, the external electronic device (401) may transmit a request message for authentication to the wearable electronic device (400). The request message may specify a determined action or include information indicating the determined action. For example, if the external electronic device (401) determines a first action, the request message may specify the first action or include information indicating the first action.

[0084] When the wearable electronic device (400) receives a request message, the wearable electronic device (400) can determine whether an action specified in the request message (e.g., at least one of the first to seventh actions of Table 1 above) has occurred in operation 431. For example, when the first action is specified in the request message (or when the request message includes information indicating the first action), the wearable electronic device (400) can determine whether the wearable electronic device (400) is being charged by a charging device (e.g., whether it is housed in a cradle and is being charged by the cradle). The charging device may include, but is not limited to, a cradle as described below with reference to FIGS. 5A and 5B .

[0085] If the wearable electronic device (400) determines that the action specified in the request message has occurred within a predetermined time period (operation 431 - Yes), the wearable electronic device (400) may determine that the authentication has been successful, and may transmit a response message indicating the success of the authentication to the external electronic device (401) in operation 433. For example, a first action may be specified in the request message, and the wearable electronic device (400) may be accommodated in the cradle and charged by the cradle within a predetermined time period. In this case, the wearable electronic device (400) may determine that the first action has occurred and may determine that the authentication has been successful. The wearable electronic device (400) may transmit a response message indicating the success of the authentication (or a response message including information indicating that the specified action has occurred) to the external electronic device (401).

[0086] If the wearable electronic device (400) determines that the action specified in the request message has not occurred within a given time (operation 431-No), in operation 435, the wearable electronic device (400) may transmit an error message indicating that the action specified in the request message has not occurred (or an error message indicating authentication failure) to the external electronic device (401). If the external electronic device (401) receives the error message from the wearable electronic device (400), the external electronic device (401) may output an error screen on the display and re-perform operation 425 or operation 427.

[0087] According to one embodiment, the wearable electronic device (400) may perform authentication (e.g., user authentication) by determining whether information (e.g., device information and / or user information) received from an external electronic device (401) matches information stored in the wearable electronic device (400). For example, the external electronic device (401) may access the server with a user account used by an existing electronic device (e.g., the first electronic device (310) of FIG. 3B) to access the server. The external electronic device (401) may receive information (e.g., device information and / or user information) of the existing electronic device from the server or from the existing electronic device. The wearable electronic device (400) may store information (e.g., device information and / or user information) of the existing electronic device. When a wireless communication connection is established with the wearable electronic device (400), the external electronic device (401) can transmit information (e.g., device information and / or user information of an existing electronic device) received by the wearable electronic device (400). The wearable electronic device (400) can determine whether the information (e.g., device information and / or user information of an existing electronic device) received from the external electronic device (401) matches information (e.g., device information and / or user information of an existing electronic device) stored in the wearable electronic device (400). When the wearable electronic device (400) determines that the received information and the stored information match, the wearable electronic device (400) can determine that the user of the existing electronic device and the user of the external electronic device (401) are the same, and thus determine that authentication (e.g., user authentication) is successful. The wearable electronic device (400) can transmit a response message indicating successful authentication to the external electronic device (401). Transmission and reception of information of an existing electronic device and authentication based on information of an existing electronic device may be performed in parallel with operations 425, 427, 429, and 431 of FIG. 4a or may be performed instead of operations 425, 427, 429, and 431 of FIG. 4a.

[0088] Moving on to FIG. 4B, according to one embodiment, in operation 437, when the external electronic device (401) receives a response message, it may provide the user with guidance on additional actions for additional authentication. The additional actions may be, for example, predetermined. For example, a first action may be determined in operation 425. In this case, the additional action for additional authentication may be predetermined, for example, a second action. The present invention is not limited thereto, and after the external electronic device (401) receives a response message from the wearable electronic device (400), it may determine an additional action based on the status information of the wearable electronic device (400). For example, when the status information of the wearable electronic device (400) indicates an uncharged state and an unworn state, the external electronic device (401) may determine the first action in operation 425, and may determine one of the second action and the sixth action mapped to the status information (e.g., an uncharged state and an unworn state) as the additional action.

[0089] In operation 439, the external electronic device (401) may transmit an additional request message for an additional authentication request to the wearable electronic device (400). The additional request message may specify an additional action or include information indicating the additional action.

[0090] In operation 441, the wearable electronic device (400) can determine whether an additional action specified in the additional request message has occurred. For example, if a second action is specified in the additional request message (or additional authentication request), the wearable electronic device (400) can determine whether a user input (e.g., a button) has been performed on the cradle while the wearable electronic device (400) is housed in the cradle and being charged. For example, if a second action is specified in the additional request message (or additional authentication request), the wearable electronic device (400) can determine whether a button mounted on the cradle has been pressed or a touch has been performed on a touchpad mounted on the cradle while the wearable electronic device (400) is housed in the cradle and being charged.

[0091] If the wearable electronic device (400) determines that the additional action specified in the additional request message has not occurred within a set time (operation 441-No), in operation 443, the wearable electronic device (400) may transmit an error message indicating that the additional action specified in the additional request message has not occurred (or an error message indicating a failure of additional authentication) to the external electronic device (401).

[0092] If the wearable electronic device (400) determines that the additional action specified in the additional request message has occurred within a predetermined time period (operation 441 - Yes), the wearable electronic device (400) may determine that the additional authentication has succeeded, and may transmit an additional response message indicating the success of the additional authentication to the external electronic device (401) in operation 445. For example, a second action may be specified in the additional authentication request, and the wearable electronic device (400) may receive an event indicating that a button on the cradle has been pressed within a predetermined time period. In this case, the wearable electronic device (400) may determine that the additional action (e.g., the second action) has occurred, and may determine that the additional authentication has succeeded. The wearable electronic device (400) may transmit an additional response message indicating the success of the additional authentication (or an additional response message including information indicating that the additional action has occurred) to the external electronic device (401).

[0093] Depending on the embodiment, actions related to additional authentication (e.g., actions 437, 439, 441, 443, 445) may be omitted.

[0094] When the external electronic device (401) receives a response message from the wearable electronic device (400), the external electronic device (401) may transmit a reset request to the wearable electronic device (400) in operation 447. According to an embodiment, when operations related to additional authentication are performed, the external electronic device (401) may transmit a reset request to the wearable electronic device (400) when the wearable electronic device (400) receives an additional response message.

[0095] When a wearable electronic device (400) receives a reset request from an external electronic device (401), the wearable electronic device (400) may determine whether there is result information indicating the success of authentication (or the occurrence of an action) in operation 449. According to an embodiment, when operations related to additional authentication are performed, the wearable electronic device (400) may check (or determine) whether there is result information indicating the success of authentication (or the occurrence of an action) and result information indicating the success of additional authentication (or the occurrence of an additional action) in operation 449.

[0096] If the wearable electronic device (400) checks that there is result information indicating success of authentication (or success of each of authentication and additional authentication) (operation 449 - Yes), the wearable electronic device (400) can perform a reset in operation 453. If the wearable electronic device (400) checks that there is no result information indicating success of authentication (or success of each of authentication and additional authentication) (operation 449 - No), the wearable electronic device (400) can transmit an error message indicating that it is not authenticated to the external electronic device (401) in operation 451. If the external electronic device (401) receives an error message indicating that it is not authenticated, the external electronic device (401) can re-perform operation 421 or operation 425.

[0097] When the wearable electronic device (400) performs a reset, the wireless communication connection (e.g., BLE GATT connection) between the wearable electronic device (400) and the external electronic device (401) may be disconnected. Connection information between the wearable electronic device (400) and the existing electronic device (e.g., the first electronic device (310) of FIG. 3b) may be deleted by the reset.

[0098] The wearable electronic device (400) may change the mode from the first mode to the second mode (e.g., setup mode) in operation 455 when a reset is performed.

[0099] The wearable electronic device (400) may perform advertising in operation 457 when the mode is changed from the first mode to the second mode. For example, the wearable electronic device (400) may broadcast a second advertising message. The second advertising message may include information indicating that the wearable electronic device (400) is in the second mode and a device identifier of the wearable electronic device (400).

[0100] In operation 459, the external electronic device (401) may perform a search (or scanning). Through the search, the external electronic device (401) may find the wearable electronic device (400) that is in the second mode after being reset.

[0101] In operation 461, the wearable electronic device (400) and the external electronic device (401) may establish a wireless communication connection (e.g., a BLE connection). For example, if the external electronic device (401) finds the wearable electronic device (400) in the second mode after being reset, the external electronic device (401) may transmit a pairing request to the wearable electronic device (400). The external electronic device (401) may display a pop-up screen (e.g., a pop-up screen described later with reference to FIG. 8) on the display to receive user confirmation regarding pairing between the external electronic device (401) and the wearable electronic device (400). When the external electronic device (401) receives user confirmation, pairing between the external electronic device (401) and the wearable electronic device (400) can be completed, and after pairing is completed, a wireless communication connection (e.g., BLE connection) can be formed between the wearable electronic device (400) and the external electronic device (401).

[0102]

[0103] FIGS. 5A and 5B are drawings illustrating a wearable electronic device and a cradle according to one embodiment.

[0104] Referring to FIG. 5A, an example of a wearable electronic device (500) (e.g., the wearable electronic device (200) of FIG. 2, the wearable electronic device (300) of FIGS. 3A and 3B, and the wearable electronic device (400) of FIG. 4) and an example of a cradle (510) capable of accommodating the wearable electronic device (500) are illustrated.

[0105] According to one embodiment, the cradle (510) may include a button (511) and a wireless communication circuit (e.g., an NFC circuit, a BLE circuit, a communication circuit supporting Zigbee, or a communication circuit supporting Z-wave). When the wearable electronic device (500) is accommodated in the cradle (510), the wearable electronic device (500) and the cradle (510) may form a wireless communication connection (e.g., an NFC connection, a BLE connection, a Zigbee connection, or a Z-wave connection). According to an embodiment, the wearable electronic device (500) may receive wireless power from the cradle (510). The wearable electronic device (500) and the cradle (510) may communicate through a frequency (or an in-band frequency) used for transmitting and receiving wireless power. According to another embodiment, the wearable electronic device (500) and the cradle (510) may be wired connected and perform wired communication.

[0106] According to one embodiment, the wearable electronic device (500) may receive a request message for authentication request from an external electronic device (e.g., the external electronic device (401) of FIG. 4).

[0107] For example, the wearable electronic device (500) may receive a request message from an external electronic device, which indicates an authentication request and specifies a first action. The external electronic device may provide a guide for the first action to the user. The user may place the wearable electronic device (500) in a cradle (510) according to the guide for the first action. When the wearable electronic device (500) is placed in the cradle (510), the wearable electronic device (500) may be charged (e.g., wirelessly charged or wired charged) by the cradle (510). In this case, the wearable electronic device (500) may determine that the first action has occurred and may determine that authentication (e.g., user authentication or authentication that the user has the wearable electronic device (500)) has been successful. The wearable electronic device (500) may transmit a response message to the external electronic device indicating that the authentication has been successful (or indicating that the first action has occurred).

[0108] For another example, the wearable electronic device (500) may receive a request message from an external electronic device, which indicates an authentication request and specifies a second action. The external electronic device may provide a guide for the second action to the user. The user may place the wearable electronic device (500) in a cradle (510) and press a button (511) of the cradle (510) according to the guide for the second action. In this case, the cradle (510) may transmit an event indicating that the button (511) has been pressed to the wearable electronic device (500) using a wireless communication module. When the wearable electronic device (500) receives an event indicating that the button (511) has been pressed from the cradle (510), the wearable electronic device (500) may determine that the second action has occurred and determine that authentication has been successful. The wearable electronic device (500) can transmit a response message indicating the success of authentication (or indicating that a second action has occurred) to the external electronic device. Although the wearable electronic device (500) has been described as transmitting a response message indicating the success of authentication (or indicating that a second action has occurred) to the external electronic device, this is merely exemplary, and the cradle (510) can form a wireless communication connection (e.g., BLE connection) with the external electronic device and transmit a response message indicating the success of authentication (or indicating that a second action has occurred) to the external electronic device.

[0109] According to one embodiment, the wearable electronic device (500) may receive an additional request message for additional authentication request from an external electronic device if authentication is successful.

[0110] For example, if a first action occurs and authentication is successful, the wearable electronic device (500) may receive an additional request message from an external electronic device, indicating an additional authentication request and specifying an additional action (e.g., a second action). The external electronic device may provide a guide for the second action to the user. The user may press a button (511) of a cradle (510) containing the wearable electronic device (500) according to the guide for the second action. In this case, the cradle (510) may transmit an event indicating that the button (511) has been pressed to the wearable electronic device (500) using a wireless communication module. If the wearable electronic device (500) receives an event indicating that the button (511) has been pressed from the cradle (510), the wearable electronic device (500) may determine that the second action has occurred and determine that the additional authentication has been successful. The wearable electronic device (500) may transmit an additional response message to the external electronic device indicating the success of the additional authentication (or indicating that a second action has occurred).

[0111] For another example, if a second action occurs and authentication is successful, the wearable electronic device (500) may receive an additional request message from an external electronic device, indicating an additional authentication request and specifying an additional action (e.g., a sixth action). The external electronic device may provide a guide for the sixth action to the user. The user may wear the wearable electronic device (500) according to the guide for the sixth action. The wearable electronic device (500) may determine that the sixth action has occurred when the wearable electronic device (500) changes from an unworn state to a worn state, and may determine that the additional authentication has been successful. The wearable electronic device (500) may transmit an additional response message to the external electronic device, indicating the success of the additional authentication (or indicating that the sixth action has occurred).

[0112]

[0113] FIG. 6 is a drawing illustrating an example of a search operation of an external electronic device according to one embodiment.

[0114] Referring to FIG. 6, an external electronic device (600) according to an embodiment (e.g., the electronic device (305) of FIG. 3A, the second electronic device (320) of FIG. 3B, and the external electronic device (401) of FIGS. 4A and 4B) may perform a search (or scanning) in operation 415 of FIG. 4A. The electronic device may perform the search and display a list (610) including one or more devices connectable to the external electronic device on a display.

[0115] According to one embodiment, the external electronic device (600) may receive a selection input from the user for a wearable electronic device (e.g., Galaxy ring of FIG. 6) (611) (e.g., wearable electronic device (200) of FIG. 2, wearable electronic device (300) of FIGS. 3A and 3B, wearable electronic device (400) of FIG. 4) among the devices on the list (610).

[0116] According to one embodiment, when there is a selection input for a wearable electronic device (611) on the list (610), the external electronic device (600) may determine the wearable electronic device (611) as a connection target and transmit a wireless communication connection request (e.g., a BLE GATT connection request) to the wearable electronic device (611).

[0117]

[0118] FIG. 7 is a drawing illustrating an example of a guide operation of an external electronic device according to one embodiment.

[0119] Referring to FIG. 7, an example of a guide screen of an external electronic device (600) according to one embodiment is illustrated.

[0120] In the example illustrated in FIG. 7, an external electronic device (600) may transmit a request message to a wearable electronic device (611). The request message may indicate an authentication request from the external electronic device (600), and the request message may specify an action for authentication (e.g., a first action). Since the wearable electronic device (611) may not have an interface capable of input and output (e.g., a touch display), the external electronic device (600) may provide a user with a guide related to the first action. For example, the external electronic device (600) may display a guide screen (710) on the display. The guide screen (710) may include at least one of a guide phrase (711) that can guide the user to perform a first action (e.g., put the ring in the case and charge it) or an image (712) that can guide the user to keep the wearable electronic device (611) housed in a cradle (or case) (e.g., the cradle (510) of FIG. 5A).

[0121] According to one embodiment, the wearable electronic device (611) can determine whether a first action has occurred, and if it determines that the first action has occurred, it can determine that authentication has been successful. The external electronic device (600) can receive a response message from the wearable electronic device (611) indicating that the first action has occurred (or indicating that authentication has been successful).

[0122] According to one embodiment, when the external electronic device (600) receives a response message from the wearable electronic device (611), it may transmit an additional request message to the wearable electronic device (611). The additional request message may indicate an additional authentication request from the external electronic device (600), and the additional request message may specify an additional action (e.g., a second action) for the additional authentication. The external electronic device (600) may provide a guide related to the second action to the user. For example, the external electronic device (600) may display a guide screen (720) on the display. The guide screen (720) may include at least one of a guide phrase (721) that may guide the user to perform the second action (e.g., press the button on the case for reset) or an image (722) that may guide the user to press a button on the cradle (or case) (e.g., button (511) of FIG. 5B ).

[0123] According to one embodiment, the wearable electronic device (611) may determine whether a second action has occurred, and if it determines that the second action has occurred, it may determine that additional authentication has been successful. The external electronic device (600) may receive an additional response message from the wearable electronic device (611) indicating that the second action has occurred (or indicating that additional authentication has been successful).

[0124] In one embodiment, the above-described authentication (+additional authentication) may represent authenticating a user so that a reset of the wearable electronic device (611) can be performed. When a specified action occurs and the user's authentication (+additional authentication) is successful, a reset of the wearable electronic device (611) may be performed.

[0125] According to one embodiment, when the external electronic device (600) receives an additional response message from the wearable electronic device (611), it may recognize that the additional authentication has been successful and transmit a reset request to the wearable electronic device (611). When the reset request is transmitted, the external electronic device (600) may display a screen (730) on the display indicating that the wearable electronic device (611) is being reset.

[0126]

[0127] FIG. 8 is a drawing illustrating an example of a pop-up screen of an external electronic device according to one embodiment.

[0128] In the example illustrated in FIG. 8, the external electronic device (600) can perform a search (or scanning) (e.g., the search of operation 459 of FIG. 4b) to find the wearable electronic device (611) in the second mode.

[0129] According to one embodiment, when the external electronic device (600) finds a wearable electronic device (611) in the second mode, the external electronic device (600) may transmit a pairing request to the wearable electronic device (611). The external electronic device (600) may display a pop-up screen (810) on the display to receive user confirmation for pairing between the external electronic device (600) and the wearable electronic device (411). When the external electronic device (600) receives user confirmation through the pop-up screen (810), pairing between the external electronic device (600) and the wearable electronic device (611) may be completed.

[0130]

[0131] FIG. 9 is a block diagram illustrating an example of a wearable electronic device according to one embodiment.

[0132] Referring to FIG. 9, a wearable electronic device (900) according to an embodiment (e.g., the wearable electronic device (200) of FIG. 2, the wearable electronic device (300) of FIGS. 3A and 3B, and the wearable electronic device (400) of FIG. 4) may include a communication circuit (910) (e.g., the communication circuit (210) of FIG. 2), at least one processor (920) (e.g., the processor (220) of FIG. 2), and a memory (930) (e.g., the memory (230) of FIG. 2).

[0133] According to one embodiment, the wearable electronic device (900) may operate in a first mode. The first mode may represent a mode other than a setup mode. The first mode may include, but is not limited to, an automatic connection mode, for example.

[0134] According to one embodiment, the memory (930) may store instructions. The instructions stored in the memory (930) may be individually or collectively executed by the processor (920) to cause the wearable electronic device (900) to perform operations described with reference to FIG. 9.

[0135] According to one embodiment, the processor (920) may be operatively connected to the communication circuit (910) and the memory (930). The processor (920) may include a processing circuit.

[0136] According to one embodiment, the processor (920) may establish a wireless communication connection (e.g., a BLE GATT connection) with an external electronic device (e.g., the electronic device (305) of FIG. 3A, the second electronic device (320) of FIG. 3B, the external electronic device (401) of FIGS. 4A and 4B, and the external electronic device (600) of FIG. 6) via the communication circuit (910). For example, the processor (920) may broadcast a first advertising message including information indicating a first mode via the communication circuit (910). The external electronic device may find the wearable electronic device (900) broadcasting the first advertising message and transmit a wireless communication connection request (e.g., a BLE GATT request) to the wearable electronic device (900). The processor (920) can form a wireless communication connection (e.g., a BLE GATT connection) with an external electronic device after receiving a wireless communication connection request (e.g., a BLE GATT request) through the communication circuit (910).

[0137] According to one embodiment, the processor (920) may receive a status information request from an external electronic device via the communication circuit (910). The processor (920) may transmit status information of the wearable electronic device (900) to the external electronic device via the communication circuit (910). The external electronic device may designate (or determine) an action (e.g., one of the actions in Table 1) desired to occur in the wearable electronic device (900) based on the status information of the wearable electronic device (900).

[0138] According to one embodiment, the processor (920) may receive a request message for an authentication request from an external electronic device through the communication circuit (910). The request message may include an action designated or information indicating the designated action. For example, if the first action in Table 1 above is designated (or determined), the request message may include information (e.g., a number "1") indicating the first action designated for authentication. If the second action in Table 1 above is designated (or determined), the request message may include information (e.g., a number "2") indicating the second action designated for authentication. Depending on the implementation, the processor (920) may determine an action for authentication (e.g., one of the actions in Table 1) based on status information of the wearable electronic device (900) when a wireless communication connection is established between the wearable electronic device (900) and the external electronic device.

[0139] According to one embodiment, the actions for authentication are not limited to the actions in Table 1 above. For example, the actions for authentication may include at least one of an action of connecting to another external electronic device (e.g., the first electronic device (310) of FIG. 3B or the cradle (510) of FIG. 5A) and an action of pressing a button on another external electronic device.

[0140] According to one embodiment, the processor (920) may determine whether an action (e.g., an action specified in a request message or an action determined by the processor (920)) has occurred. The processor (920) may determine that an action has occurred when it detects at least one of the following: that the wearable electronic device (900) is connected to another external electronic device (e.g., the first electronic device (310) of FIG. 3B or the cradle (510) of FIG. 5A) and that a button on the other external electronic device is pressed. For example, the processor (920) may determine that an action has occurred when the wearable electronic device (900) is connected to the cradle and is being charged (e.g., when it detects the first action of Table 1 above) and / or when a button on the cradle is pressed (e.g., when it detects the second action of Table 1 above). For another example, the processor (920) may determine that an action has occurred when the wearable electronic device (900) is wirelessly connected to an existing electronic device, e.g., the first electronic device (310) of FIG. 3B, and / or when a button on the existing electronic device (e.g., a physical button on the existing electronic device or a button displayed on the screen of the existing electronic device) is pressed.

[0141] According to one embodiment, the processor (920) may determine that authentication is successful when it determines that an action has occurred, and may transmit a response message indicating successful authentication to the external electronic device.

[0142] According to one embodiment, the processor (920) may receive a reset request from an external electronic device that has received a response message through the communication circuit (910). The processor (920) may perform a reset based on the received reset request. According to an embodiment, when the processor (920) receives a reset request from the external electronic device, the processor (920) may check whether there is result information indicating successful authentication (or result information indicating the occurrence of a specified action). If the processor (920) determines that there is result information indicating successful authentication, the processor (920) may perform a reset.

[0143] According to one embodiment, the processor (920) may receive an additional request message for additional authentication from an external electronic device after transmitting a response message indicating successful authentication. At this time, the additional request message may specify additional authentication or include information about the additional authentication. Alternatively, the processor (920) may determine an additional action for additional authentication after transmitting the response message. The processor (920) may determine whether an additional action (e.g., an additional action specified in the additional request message or an additional action determined by the processor (920)) has occurred. If the processor (920) determines that an additional action has occurred, the processor may determine that the additional authentication has been successful and may transmit an additional response message indicating the success of the additional authentication to the external electronic device. If the external electronic device receives an additional response message from the wearable electronic device (900), the external electronic device may transmit a reset request to the wearable electronic device (900).

[0144] According to one embodiment, when the processor (920) performs a reset, the mode of the wearable electronic device (900) may be changed from the first mode to the second mode (e.g., setup mode). The processor (920) may broadcast a second advertising message including information indicating the second mode. An external electronic device may find the wearable electronic device (900) broadcasting the second advertising message and transmit a pairing request to the wearable electronic device (900). When the processor (920) receives the pairing request through the communication circuit (910), the processor (920) may establish a wireless communication connection (e.g., BLE connection) with the external electronic device.

[0145] According to one embodiment, the memory (930) may store instructions. The instructions, when executed by the processor (920), may cause the wearable electronic device (900) to perform operations of the wearable electronic device (900). For example, the instructions, when executed by the processor (920), cause the wearable electronic device (900) to (i) establish a wireless communication connection (e.g., a BLE GATT connection) with an external electronic device, (ii) receive a request message for authentication from the external electronic device (wherein the request message may include information about an action designated for authentication) or determine an action for authentication based on status information of the wearable electronic device (900), (iii) determine whether an action has occurred, and (iv) determine that authentication is successful if the wearable electronic device (900) determines that an action has occurred by detecting at least one of the following: that the wearable electronic device (900) is connected to another external electronic device (e.g., the first electronic device (310) of FIG. 3B or the cradle (510) of FIG. 5A) and that a button on the other external electronic device (e.g., a physical button (or a button on the screen) of the first electronic device (310) or a button of the cradle (510)) is pressed, and indicate that the authentication is successful. The operation may be performed to: (v) transmit a response message to an external electronic device; (vi) receive a reset request from the external electronic device after transmitting the response message; and (vi) perform a reset based on the received reset request.

[0146] The embodiments of the wearable electronic device described through FIGS. 1 to 8 can be applied to the wearable electronic device (900) of FIG. 9.

[0147]

[0148] FIG. 10 is a block diagram illustrating an example of an electronic device according to one embodiment.

[0149] Referring to FIG. 10, an electronic device (1000) (e.g., the electronic device (101) of FIG. 1, the electronic device (305) of FIG. 3A, the second electronic device (320) of FIG. 3B, the external electronic device (401) of FIGS. 4A and 4B, and the external electronic device (600) of FIG. 6) may include a communication circuit (1010) (e.g., the communication module (190) of FIG. 1), a processor (1020) (e.g., the processor (120) of FIG. 1), a memory (1030) (e.g., the memory (130) of FIG. 1), and a display (1040) (e.g., the display module (160) of FIG. 1).

[0150] According to one embodiment, the processor (1020) may be operatively connected to a communication circuit (1010), a memory (1030), and a display (1040). The processor (1020) may include a processing circuit.

[0151] According to one embodiment, the memory (1030) may store instructions. The instructions stored in the memory (1030) may be individually or collectively executed by the processor (1020) to cause the electronic device (1000) to perform operations described with reference to FIG. 10.

[0152] According to one embodiment, the communication circuit (1010) may support a wireless communication method (e.g., BLE).

[0153] According to one embodiment, the processor (1020) may form a wireless communication connection with a wearable electronic device (e.g., the wearable electronic device (200) of FIG. 2, the wearable electronic device (300) of FIGS. 3A and 3B, the wearable electronic device (400) of FIG. 4, and the wearable electronic device (900) of FIG. 9) via the communication circuit (1010). For example, the processor (1020) may form a wireless communication connection (e.g., a BLE GATT connection) with a wearable electronic device in a first mode (e.g., an automatic connection mode) via the communication circuit (1010).

[0154] According to one embodiment, the processor (1020) may receive status information of the wearable electronic device from the wearable electronic device through the communication circuit (1010).

[0155] According to one embodiment, the processor (1020) may determine an action for authentication (e.g., one of the actions in Table 1) based on state information of the wearable electronic device.

[0156] According to one embodiment, when the processor (1020) determines an action for authentication, it may transmit a request message for authentication to the wearable electronic device via the communication circuit (1010). The request message may specify the determined action.

[0157] According to one embodiment, the processor (1020) may provide a user with guidance regarding a determined action. For example, the processor (1020) may display a guide screen regarding the determined action (e.g., the guide screen (710) of FIG. 7) on the display (1040).

[0158] According to one embodiment, the processor (1020) may receive a response message from the wearable electronic device via the communication circuit (1010) indicating that a determined action occurred in the wearable electronic device and authentication was successful.

[0159] According to one embodiment, the processor (1020) may transmit a reset request to the wearable electronic device through the communication circuit (1010) based on the response message.

[0160] According to one embodiment, the processor (1020) may perform a search (or scanning) when a reset request is transmitted. The processor (1020) may receive a second advertising message from the wearable electronic device in a second mode (e.g., setup mode) after being reset. When the processor (1020) receives the second advertising message, the processor (1020) may transmit a pairing request to the wearable electronic device through the communication circuit (1010). When the processor (1020) transmits the pairing request, the processor (1020) may establish a wireless communication connection (e.g., BLE connection) with the wearable electronic device.

[0161] The embodiments of the electronic device described through FIGS. 1 to 8 can be applied to the electronic device (1000) of FIG. 10.

[0162]

[0163] FIG. 11 is a flowchart illustrating another example of the operation of a wearable electronic device and an external electronic device according to one embodiment.

[0164] Referring to FIG. 11, in operation 1111 (e.g., operation 411), a wearable electronic device (1100) (e.g., the wearable electronic device (200) of FIG. 2, the wearable electronic device (300) of FIGS. 3A and 3B, the wearable electronic device (400) of FIG. 4, and the wearable electronic device (900) of FIG. 9) may operate in a first mode.

[0165] In operation 1113 (e.g., operation 413), the wearable electronic device (1100) may perform advertising.

[0166] In operation 1115 (e.g., operation 415), an external electronic device (1101) (e.g., the electronic device (101) of FIG. 1 , the electronic device (305) of FIG. 3A , the second electronic device (320) of FIG. 3B , the external electronic device (401) of FIGS. 4A and 4B , the external electronic device (600) of FIG. 6 , and the electronic device (1000) of FIG. 10 ) may perform a search (or scanning).

[0167] In operation 1117 (e.g., operation 417), the external electronic device (1101) may determine the wearable electronic device (1100) as a connection target among one or more devices in the search results.

[0168] In operation 1119 (e.g., operation 419), the wearable electronic device (1100) and the external electronic device (1101) may form a wireless communication connection (e.g., a BLE GATT connection).

[0169] In operation 1121, the wearable electronic device (1100) may determine an action for authentication (e.g., one of the actions in Table 1) based on state information of the wearable electronic device (1100).

[0170] In operation 1123, the wearable electronic device (1100) may transmit information about the action to an external electronic device (1101). For example, if the wearable electronic device (1100) determines a first action in operation 1111, the wearable electronic device (1100) may transmit information about the first action (or information indicating the first action) to the external electronic device (1101) in operation 1113.

[0171] In operation 1125 (e.g., operation 427), the external electronic device (1101) may provide a guide for an action to the user. For example, when the external electronic device (1101) receives information about a first action (or information indicating the first action) from the wearable electronic device (1100), the external electronic device (1101) may display a guide screen (e.g., guide screen (710) of FIG. 7) regarding the first action on the display.

[0172] In operation 1127, the wearable electronic device (1100) may determine whether an action (e.g., the action determined in operation 1121) has occurred.

[0173] If the wearable electronic device (1100) determines that the action occurred within a predetermined time period (operation 1127 - Yes), it may determine that the authentication was successful, and may transmit a response message indicating the success of the authentication to the external electronic device (1101) in operation 1129 (e.g., operation 433). If the wearable electronic device (100) determines that the action did not occur within a predetermined time period (operation 1127 - No), it may transmit an error message indicating that the action did not occur (or an error message indicating an authentication failure) to the external electronic device (1101) in operation 1131 (e.g., operation 435).

[0174] According to one embodiment, if the wearable electronic device (1100) transmits a response message, the wearable electronic device (1100) may determine an additional action for additional authentication in operation 1133. For example, a first action may be determined in operation 1121. The additional action for additional authentication may be predetermined, for example, as a second action. In this case, the wearable electronic device (1100) may determine the second action as the additional action for additional authentication in operation 1133. The present invention is not limited thereto, and the wearable electronic device (1100) may determine an additional action based on status information of the wearable electronic device (1100). For example, if the status information of the wearable electronic device (1100) indicates an uncharged state and an unworn state, the wearable electronic device (1100) may determine a first action in operation 1121, and may determine one of the second action and the sixth action mapped to the status information (e.g., the uncharged state and the unworn state) as an additional action.

[0175] At operation 1135, the wearable electronic device (1100) may transmit information about additional actions.

[0176] When the external electronic device (1101) receives information about an additional action from the wearable electronic device (1100), in operation 1137, the external electronic device (1101) may provide a guide for the additional action to the user. For example, when the second action is determined to be the additional action, the external electronic device (1101) may display a guide screen (e.g., guide screen (720) of FIG. 7) regarding the second action on the display.

[0177] If the wearable electronic device (1100) transmits information about an additional action, the wearable electronic device (1100) can determine whether an additional action has occurred in operation 1139. If the additional action has occurred within a set time, the wearable electronic device (1100) can transmit an additional response message of operation 445 of FIG. 4B to the external electronic device (1101), and if the additional action has not occurred within the set time, the wearable electronic device (1100) can transmit an error message of operation 443 of FIG. 4B to the external electronic device (1101).

[0178] According to an embodiment, in FIG. 11, operations related to additional authentication (e.g., operations 1133, 1135, 1137, 1139) may be omitted.

[0179] The external electronic device (1101) may perform operation 447 of FIG. 4 when receiving a response message (or additional response message). The wearable electronic device (1100) may perform operation 451 when checking that there is no result information indicating successful authentication in operation 449 of FIG. 4B. The wearable electronic device (1100) may perform operations 453, 455, and 457 when checking that there is result information indicating successful authentication in operation 449 of FIG. 4B. The external electronic device (1101) may perform operation 459 of FIG. 4B. The wearable electronic device (1100) and the external electronic device (1101) may perform operation 461 of FIG. 4.

[0180] The embodiments described through FIGS. 1 to 10 can be applied to the wearable electronic device (1100) and external electronic device (1101) of FIG. 11.

[0181]

[0182] FIG. 12 is a diagram illustrating an example of the operation of a wearable electronic device and a plurality of electronic devices according to one embodiment.

[0183] In FIG. 12, a wearable electronic device (1200), a first electronic device (1210), and a second electronic device (1220) according to an embodiment are illustrated.

[0184] The wearable electronic device (1200) may correspond to, for example, the wearable electronic device (200) of FIG. 2, the wearable electronic device (300) of FIGS. 3A and 3B, the wearable electronic device (400) of FIG. 4, the wearable electronic device (900) of FIG. 9, or the wearable electronic device (1100) of FIG. 11.

[0185] The first electronic device (1210) may be, for example, an existing electronic device that was previously connected to the wearable electronic device (1200) (or an existing electronic device that has a history of being connected to the wearable electronic device (1200). The first electronic device may correspond to the first electronic device (310) of FIG. 3B.

[0186] The second electronic device (1220) may be an electronic device that has never been connected to the wearable electronic device (1200). The second electronic device (1220) may correspond to, for example, the electronic device (305) of FIG. 3A, the second electronic device (320) of FIG. 3B, the external electronic device (401) of FIGS. 4A and 4B, the external electronic device (600) of FIG. 6, the electronic device (1000) of FIG. 10, or the external electronic device (1101) of FIG. 11.

[0187] According to one embodiment, the wearable electronic device (1200) may transmit information about an action to the first electronic device (1210) in operation 1231.

[0188] For example, the second electronic device (1220) may determine an action for authentication (e.g., at least one of an action for connecting an existing electronic device and a wearable electronic device (1200), an action for pressing a button (e.g., a physical button or a button displayed on a screen) of the existing electronic device, or an action for entering a password on a screen of the existing electronic device) and transmit a request message including information about the action to the wearable electronic device (1200). At this time, the second electronic device (1220) may display a guide screen regarding the action (e.g., at least one of a guide screen indicating a connection between the existing electronic device and the wearable electronic device (1200), a guide screen indicating pressing a button of the existing electronic device, or a guide screen indicating entering a password on the screen of the existing electronic device) on the display of the second electronic device (1220). The wearable electronic device (1200) may transmit information about the action in the request message to the first electronic device (1210).

[0189] For another example, when the wearable electronic device (1200) performs operation 419 of FIG. 4A to form a wireless communication connection (e.g., a BLE GATT connection) with the second electronic device (1220), the wearable electronic device (1200) may determine an action for authentication (e.g., at least one of an action of connecting the existing electronic device and the wearable electronic device (1200), an action of pressing a button of the existing electronic device (e.g., a physical button or a button displayed on a screen), or an action of entering a password on the screen of the existing electronic device), and may transmit information about the action to the first electronic device (1210) and the second electronic device (1220). At this time, the second electronic device (1220) may display a guide screen regarding an action (e.g., at least one of a guide screen indicating a connection between an existing electronic device and a wearable electronic device (1200), a guide screen indicating to press a button of the existing electronic device, or a guide screen indicating to enter a password on the screen of the existing electronic device) on the display of the second electronic device (1220).

[0190] According to one embodiment, when the first electronic device (1210) receives information about an action (e.g., at least one of an action of connecting an existing electronic device and the wearable electronic device (1200), an action of pressing a button (e.g., a physical button or a button displayed on a screen) of the existing electronic device, or an action of entering a password on a screen of the existing electronic device) from the wearable electronic device (1200), the first electronic device (1210) may display a screen (e.g., a screen displaying a button or a screen for receiving a password from a user) that enables the action to occur on the display of the first electronic device (1210). The password may include, but is not limited to, a password for unlocking the first electronic device (1210). When there is a user input matching the action, the first electronic device (1210) may transmit a message indicating that there is a user input matching the action (or a message indicating that the action has occurred) to the wearable electronic device (1200) in operation 1233. For example, the first electronic device (1210) may determine that a user input matches an action if a password entered by the user matches a true password (e.g., a password to unlock the first electronic device (1210)) or if a button (e.g., an on-screen button or a physical button on the first electronic device (1210)) is pressed, and may transmit a message to the wearable electronic device (1200) indicating that there is a user input that matches the action.

[0191] According to one embodiment, when the wearable electronic device (1200) receives a message indicating that there is a user input matching an action (or a message indicating that an action has occurred) from the first electronic device (1210), the wearable electronic device (1200) may transmit a response message indicating successful authentication (or a response message indicating that an action has occurred) to the second electronic device (1220) in operation 1235.

[0192] According to one embodiment, when the second electronic device (1220) receives a response message from the wearable electronic device (1200), the second electronic device (1220) may transmit a reset request to the wearable electronic device (1200) in operation 1237.

[0193] Depending on the implementation, unlike the example illustrated in FIG. 12, the first electronic device (1210) may transmit a message indicating that there is a user input matching the action to the second electronic device (1220) when there is a user input matching the action. The second electronic device (1220) may transmit a reset request to the wearable electronic device (1200) when it receives a message indicating that there is a user input matching the action from the first electronic device (1210).

[0194] In the example illustrated in FIG. 12, the wearable electronic device (1200) can determine whether an additional action for additional authentication (e.g., one of the actions in Table 1 above) has occurred. For example, the wearable electronic device (1200) can receive an additional request message (e.g., the additional request message of operation 439 of FIG. 4B) including information about the additional action from the second electronic device (1220) and determine whether the additional action in the additional request message has occurred. For another example, when the wearable electronic device (1200) transmits a response message of operation 1235, the wearable electronic device (1200) can determine an additional action for additional authentication (e.g., one of the actions in Table 1 above) and determine whether the additional action has occurred. The wearable electronic device (1200) may transmit an additional response message indicating the success of the additional authentication to the second electronic device (1220) when an additional action occurs and may receive a reset request from the second electronic device (1220).

[0195] The embodiments described through FIGS. 1 to 11 can be applied to the wearable electronic device (1200), the first electronic device (1210), and the second electronic device (1220) of FIG. 12.

[0196]

[0197] According to one embodiment, a wearable electronic device may include at least one processor including a processing circuit and a memory storing instructions. The instructions, when individually or collectively executed by the at least one processor, may cause the wearable electronic device to perform the following actions: establishing a wireless communication connection with an external electronic device; receiving a request message for an authentication request, the request message including information about an action designated for authentication, from the external electronic device or determining the action based on status information of the wearable electronic device; determining whether the action has occurred; determining that the authentication is successful if it is determined that the action has occurred by detecting at least one of whether the wearable electronic device is being charged by another external electronic device and whether a user input has been performed to the another external electronic device; and transmitting a response message indicating the success of the authentication to the external electronic device; receiving a reset request from the external electronic device after transmitting the response message; and performing a reset based on the received reset request.

[0198] Charging the wearable electronic device by another external electronic device may include, for example, charging the wearable electronic device by a cradle. Performing a user input to the other external electronic device may include, for example, pressing a button (e.g., a physical button or an on-screen button) on the existing electronic device or pressing a button on the cradle.

[0199] According to one embodiment, the wearable electronic device is charged by a cradle that accommodates the wearable electronic device, a button of the cradle is pressed while the wearable electronic device is being charged by the cradle, and the operation of determining whether the action has occurred may include an operation of determining that the action has occurred when at least one of the following is detected: the wearable electronic device being charged changes to an uncharged state, the wearable electronic device being charged changes to an uncharged state and then is charged again, the wearable electronic device being worn changes to an unworn state, the wearable electronic device being unworn changes to a worn state, or the wearable electronic device being worn spins on a finger.

[0200] According to one embodiment, the operation of determining whether the action has occurred may include an operation of transmitting information about the action to another external electronic device (e.g., the first electronic device (310) of FIG. 3B, the first electronic device (1210) of FIG. 12) that has a connection history with the wearable electronic device, and an operation of determining that the action has occurred when a message indicating that there is a user input matching the action is received from the other external electronic device.

[0201] According to one embodiment, the instructions, when individually or collectively executed by the at least one processor, may cause the wearable electronic device to perform an operation of transmitting status information of the wearable device to the external electronic device.

[0202] According to one embodiment, the instructions, when individually or collectively executed by the at least one processor, may further cause the wearable electronic device to: receive an additional request message for an additional authentication request from the external electronic device after transmitting the response message, the additional request message including information about an additional action designated for additional authentication, or determine the additional action; determine whether the additional action has occurred; and determine that the additional authentication is successful and transmit an additional response message indicating the success of the additional authentication to the external electronic device.

[0203] According to one embodiment, the instructions, when individually or collectively executed by the at least one processor, may cause the wearable electronic device to perform an operation of transmitting information about the action to the external electronic device when the wearable electronic device determines the action based on the state information.

[0204] According to one embodiment, the operation of performing the reset may include an operation of checking whether there is result information indicating success of the authentication when the reset request is received, and an operation of performing the reset when it is checked that there is result information.

[0205] According to one embodiment, the act of forming a wireless communication connection with the external electronic device may include an act of the wearable electronic device broadcasting a first advertising message including information indicating the first mode in a first mode, and an act of forming the wireless communication connection with the external electronic device that has received the first advertising message.

[0206] According to one embodiment, the instructions, when individually or collectively executed by the at least one processor, may cause the wearable electronic device to perform: changing a mode of the wearable electronic device from the first mode to a second mode when the reset is performed, and broadcasting a second advancing message including information indicating the second mode.

[0207] According to one embodiment, an electronic device may include at least one processor including a processing circuit and a memory storing instructions. The instructions, when individually or collectively executed by the at least one processor, may cause the electronic device to perform the following actions: establishing a wireless communication connection with a wearable electronic device; transmitting a request message indicating an authentication request to the wearable electronic device, the request message including information about an action determined by the electronic device based on status information of the wearable electronic device for authentication, or receiving information about the action determined by the wearable electronic device from the wearable electronic device; providing a guide regarding the action to a user; receiving a response message from the wearable electronic device indicating that the action has occurred and the authentication has been successful; and transmitting a reset request to the wearable electronic device based on the response message. The action may include at least one of an action in which the wearable electronic device is charged by another electronic device or an action in which a user input is generated for the other electronic device.

[0208] According to one embodiment, the instructions, when individually or collectively executed by the at least one processor, may cause the electronic device to perform the following actions: when the response message is received, transmitting an additional request message for an additional authentication request to the wearable electronic device, the additional request message including information about an additional action determined for additional authentication, or receiving information about the additional action determined by the wearable electronic device from the wearable electronic device, providing a guide regarding the additional action to the user; and when an additional response message indicating that the additional action has occurred and the additional authentication has succeeded is received from the wearable electronic device, transmitting the reset request.

[0209] According to one embodiment, a method for operating a wearable electronic device may include: forming a wireless communication connection with an external electronic device; receiving a request message for an authentication request, the request message including information on an action designated for authentication, from the external electronic device or determining the action based on status information of the wearable electronic device when forming the wireless communication connection with the external electronic device; determining whether the action has occurred; determining that the authentication is successful when it is determined that the action has occurred by detecting that the wearable electronic device is being charged by a cradle that accommodates the wearable electronic device and that a button of the cradle is pressed while the wearable electronic device is being charged by the cradle, and transmitting a response message indicating the success of the authentication to the external electronic device; receiving a reset request from the external electronic device after transmitting the response message; and performing a reset based on the received reset request.

[0210] According to one embodiment, a method of operating an electronic device may include: forming a wireless communication connection with a wearable electronic device; transmitting a request message indicating an authentication request to the wearable electronic device, the request message including information on an action determined by the electronic device based on status information of the wearable electronic device for authentication; or receiving information on the action determined by the wearable electronic device from the wearable electronic device; providing a guide regarding the action to a user; receiving a response message from the wearable electronic device indicating that the action has occurred and the authentication has succeeded; and transmitting a reset request to the wearable electronic device based on the response message.

[0211]

[0212] 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.

[0213] 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 (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.

[0214] 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).

[0215] Various embodiments of the present document may be implemented as software (e.g., a program) including one or more instructions stored in a storage medium (e.g., built-in memory or external memory) readable by a machine (e.g., an electronic device). For example, a processor (e.g., a processor) of the machine (e.g., an electronic device) 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 instruction called up. 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' only means that the storage medium is a tangible device and does not contain a signal (e.g., electromagnetic waves), and this term does not distinguish between cases where data is stored semi-permanently and cases where it is stored temporarily in the storage medium.

[0216] According to one embodiment, the method according to various embodiments disclosed in the present 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., compact disc read only memory (CD-ROM)), or may be distributed online (e.g., downloaded or uploaded) via 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.

[0217] 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.

[0218]

[0219] - Explanation of the symbol

[0220] 900: Wearable Electronic Devices

[0221] 910: Communication circuit

[0222] 920: Processor

[0223] 930: Memory

Claims

1. In a wearable electronic device (900), At least one processor (920) including a processing circuit; and Memory for storing commands (930) Including, The above instructions, when individually or collectively executed by the at least one processor, cause the wearable electronic device to: The act of forming a wireless communication connection with an external electronic device; An action of receiving a request message for an authentication request, wherein the request message includes information about an action designated for authentication, from the external electronic device or determining the action based on status information of the wearable electronic device; An action that determines whether the above action has occurred, An action of determining that the authentication is successful when the wearable electronic device determines that the action has occurred by detecting at least one of being charged by another external electronic device and performing a user input to the other external electronic device, and transmitting a response message indicating the success of the authentication to the external electronic device; An action of receiving a reset request from the external electronic device after transmitting the above response message, and An action to perform a reset based on the reset request received above. to do, Wearable electronic devices.

2. In paragraph 1, The action to determine whether the above action has occurred is: An action that determines that the action has occurred when at least one of the following is detected: a button of the cradle is pressed while the wearable electronic device is being charged by the cradle that accommodates the wearable electronic device; the wearable electronic device being charged changes to an uncharged state; the wearable electronic device being charged changes to an uncharged state and then is then charged again; the wearable electronic device being worn changes to an unworn state; the wearable electronic device being unworn changes to a worn state; or the wearable electronic device being worn spins on a finger. including, Wearable electronic devices.

3. In any one of paragraphs 1 and 2, The action to determine whether the above action has occurred is: An action of transmitting information about said action to said other external electronic device, and An action that determines that the action has occurred when a message indicating that there is a user input matching the action is received from the other external electronic device. including, Wearable electronic devices.

4. In any one of paragraphs 1 to 3, The above instructions, when individually or collectively executed by the at least one processor, cause the wearable electronic device to transmit status information of the wearable electronic device to the external electronic device. Wearable electronic devices.

5. In any one of paragraphs 1 to 4, The above instructions, when individually or collectively executed by the at least one processor, cause the wearable electronic device to: After transmitting the above response message, an action of receiving an additional request message for an additional authentication request from the external electronic device, the additional request message including information on an additional action specified for the additional authentication, or determining the additional action; An action to determine whether the above additional action has occurred, and If it is determined that the above additional action has occurred, the above additional authentication is determined to be successful, and an action is taken to transmit an additional response message indicating the success of the above additional authentication to the external electronic device. to do, Wearable electronic devices.

6. In any one of paragraphs 1 to 5, The above instructions, when individually or collectively executed by the at least one processor, cause the wearable electronic device to transmit information about the action to the external electronic device when the wearable electronic device determines the action based on the state information. to do, Wearable electronic devices.

7. In any one of paragraphs 1 to 6, The action of performing the above reset is: An action to check whether there is result information indicating success of the authentication when the above reset request is received, and If the above result information is checked, the action of performing the above reset is performed. including, Wearable electronic devices.

8. In any one of paragraphs 1 to 7, The operation of forming a wireless communication connection with the above external electronic device is: An operation in which the wearable electronic device broadcasts a first advertizing message including information indicating the first mode in a first mode, and An operation of forming a wireless communication connection with the external electronic device that has received the first advancing message. Including, The above instructions, when executed by the at least one processor, cause the wearable electronic device to: When the above reset is performed, an operation of changing the mode of the wearable electronic device from the first mode to the second mode, and An operation of broadcasting a second advertizing message including information indicating the second mode. to do, Wearable electronic devices.

9. In the electronic device (1000), At least one processor (1020) including a processing circuit; and Memory for storing commands (1030) Including, The above instructions, when individually or collectively executed by the at least one processor, cause the electronic device to: An action that forms a wireless communication connection with a wearable electronic device; An action of transmitting to the wearable electronic device a request message indicating an authentication request, the request message including information about an action determined by the electronic device based on state information of the wearable electronic device for authentication, or receiving from the wearable electronic device information about the action determined by the wearable electronic device; Actions that provide guidance to the user regarding the above actions; An action of receiving a response message from the wearable electronic device indicating that the above action has occurred and the above authentication has been successful, and An action of transmitting a reset request to the wearable electronic device based on the response message. and make it happen, The above action includes at least one of an action in which the wearable electronic device is charged by another electronic device or an action in which a user input is generated for the other electronic device. Electronic devices.

10. In paragraph 9, The above instructions, when individually or collectively executed by the at least one processor, cause the electronic device to: When the above response message is received, an action of transmitting an additional request message for an additional authentication request, the additional request message including information about an additional action determined for the additional authentication, to the wearable electronic device or receiving information about the additional action determined by the wearable electronic device from the wearable electronic device; Actions that provide guidance to the user regarding the above additional actions, and An action of transmitting the reset request when the additional action occurs and an additional response message indicating that the additional authentication is successful is received from the wearable electronic device. to do, Electronic devices.

Images