Electronic device, method, and non-transitory computer-readable storage medium for authenticating user in relation to wearable device

Abstract

This electronic device may comprise: at least one processor including a processing circuit; a communication circuit; and a memory for storing one or more programs configured to be individually or collectively executed by the at least one processor, and including one or more storage media, wherein the one or more programs include instructions which cause the electronic device to: authenticate a user in relation to the electronic device while a communication link between the electronic device and a wearable device is established; operate a timer for authenticating the user in relation to the wearable device on the basis of authenticating the user in relation to the electronic device; receive, from the wearable device through the communication link by using the communication circuit, a request for authenticating the user in relation to the wearable device; and on the basis of receiving the request before expiration of the timer, transmit a signal indicating that the user has been authenticated in relation to the wearable device to the wearable device through the communication link by using the communication circuit.

Description

Electronic device, method, and non-transient computer-readable storage medium for authenticating a user with respect to a wearable device

[0001] The present disclosure relates to an electronic device, a method, and a non-transient computer-readable storage medium for authenticating a user with respect to a wearable device.

[0002] Portable electronic devices, such as smartphones, laptop computers, tablets, and / or smartwatches, may be used for digital wallet services provided through user authentication based on interworking with external electronic devices. For example, a user may provide privacy information to the external electronic device associated with the gate based on authenticating the user using the electronic device to pass through the gate. For example, a user may transmit a command to the external electronic device inside the vehicle based on authenticating the user using the electronic device to open the door of the vehicle or start the vehicle.

[0003] The information described above may be provided as related art for the purpose of aiding understanding of the present disclosure. No claim or determination is made as to whether any of the foregoing may be applied as prior art related to the present disclosure.

[0004] An electronic device is described. The electronic device may include at least one processor comprising a processing circuit, a communication circuit, and a memory comprising one or more storage media configured to store one or more programs configured to be executed individually or collectively by the at least one processor. The one or more programs may include instructions that cause the electronic device to authenticate a user with respect to the electronic device while a communication link between the electronic device and a wearable device is established using the communication circuit. The one or more programs may include instructions that cause the electronic device to run a timer for authenticating the user with respect to the wearable device based on authenticating the user with respect to the electronic device. The one or more programs may include instructions that cause the electronic device to receive a request to authenticate the user with respect to the wearable device from the wearable device via the communication link using the communication circuit. The above one or more programs may include instructions that cause the electronic device to transmit a signal indicating that the user is authenticated with respect to the wearable device via the communication link using the communication circuit, based on receiving the request before the expiration of the timer.

[0005] A method is described. The method may be performed within an electronic device comprising a communication circuit. The method may include an operation of authenticating a user with respect to the electronic device while a communication link between the electronic device and a wearable device is established using the communication circuit. The method may include an operation of running a timer for authenticating the user with respect to the wearable device based on authenticating the user with respect to the electronic device. The method may include an operation of receiving a request to authenticate the user with respect to the wearable device from the wearable device via the communication link using the communication circuit, based on receiving the request before the expiration of the timer. The method may include an operation of transmitting a signal to the wearable device via the communication link using the communication circuit, indicating that the user is authenticated with respect to the wearable device, based on receiving the request before the expiration of the timer.

[0006] A non-transient computer-readable storage medium is described. The non-transient computer-readable storage medium may store one or more programs. The one or more programs may include instructions that cause the electronic device to authenticate a user with respect to the electronic device while a communication link between the electronic device and a wearable device is established using the communication circuit when executed by the electronic device having a communication circuit. The one or more programs may include instructions that cause the electronic device to run a timer for authenticating the user with respect to the wearable device based on authenticating the user with respect to the electronic device when executed by the electronic device. The one or more programs may include instructions that cause the electronic device to receive a request to authenticate the user with respect to the wearable device from the wearable device via the communication link using the communication circuit when executed by the electronic device. The above one or more programs may include instructions that cause the electronic device to transmit a signal indicating that the user is authenticated with respect to the wearable device via the communication link using the communication circuit, based on receiving the request before the expiration of the timer when executed by the electronic device.

[0007] FIG. 1 illustrates an example of authenticating a user with respect to a wearable device.

[0008] FIG. 2 is a simplified block diagram of an exemplary electronic device and a wearable device.

[0009] FIG. 3 is a signal flow diagram between an exemplary electronic device and a wearable device for driving a timer for user authentication regarding a wearable device.

[0010] FIG. 4a illustrates an example of authenticating a user with respect to an electronic device.

[0011] FIG. 4b illustrates an example of a timer time that varies depending on the hand on which the wearable device is worn.

[0012] FIGS. 5A, FIGS. 5B, FIGS. 5C, FIGS. 5D, FIGS. 5E, FIGS. 5F, and FIGS. 5G are flowcharts illustrating exemplary operations of an electronic device for increasing or decreasing the time of a timer for user authentication with respect to a wearable device.

[0013] FIG. 6 is a signal flow diagram between an exemplary electronic device and a wearable device for authenticating a user with respect to a wearable device.

[0014] FIGS. 7A and FIGS. 7B illustrate examples of setting a timer for user authentication with respect to a wearable device.

[0015] FIG. 7c illustrates an example of a user gesture received with respect to the finger of a user wearing a wearable device.

[0016] FIG. 7d illustrates an example of authenticating a user regarding an electronic device for an electronic wallet service.

[0017] FIG. 8 is a block diagram of an electronic device in a network environment according to various embodiments.

[0018] FIG. 9a shows a perspective view of an exemplary electronic device according to one embodiment.

[0019] FIG. 9b is an example of a partial cross-sectional view of an electronic device according to one embodiment.

[0020] Hereinafter, embodiments of the present disclosure are described in detail with reference to the drawings so that those skilled in the art can easily practice them. However, the present disclosure may be embodied in various different forms and is not limited to the embodiments described herein. In relation to the description of the drawings, the same or similar reference numerals may be used for identical or similar components. Furthermore, in the drawings and related descriptions, descriptions of well-known functions and configurations may be omitted for clarity and brevity.

[0021] FIG. 1 illustrates an example of authenticating a user with respect to a wearable device.

[0022] Referring to FIG. 1, the wearable device (110) may be described as a device available for a service provided through user authentication. For example, the wearable device (110) may be a wearable device (e.g., having a ring shape, a wireless earphone shape, an HMD (head mounted display) shape, a glasses shape, a pen shape, a bracelet shape, a belt shape, an earring shape, or a necklace shape) that includes circuits (or circuitry) for providing an operation for a service provided through user authentication.

[0023] For example, the wearable device (110) may include a near field communication (NFC) circuit (e.g., the NFC circuit (235) of FIG. 2). In state (105), the wearable device (110) may perform a service provided through user authentication using the NFC circuit. For example, the service may include a service for performing a payment using the wearable device (110). The wearable device (110) may perform the service by transmitting information about the user's credit card of the wearable device (110) to an external electronic device (120) tagged (or in contact) with the wearable device (110) using the NFC circuit. For example, since the service requires the use of privacy information such as information about the user's credit card of the wearable device (110), the service may be provided through user authentication regarding the wearable device (110).

[0024] For example, methods for authenticating a user may include a method of authenticating a user by entering a password registered through user input, a method of authenticating a user by entering a pattern registered through user input, and a method of authenticating a user by entering fingerprint information registered through user input. Since the wearable device (110) has a relatively small size, the wearable device (110) may not include a display for authenticating a user regarding the wearable device (110). An error may occur when a wearable device (110) that does not include a display authenticates a user regarding the wearable device (110).

[0025] To authenticate a user with respect to a wearable device (110), an electronic device (100) including a display (e.g., the display (230) of FIG. 2) may be used. For example, the electronic device (100) may be one of various types of mobile devices such as smartphones having various form factors including a display (e.g., a bar-type smartphone, a foldable-type smartphone, or a rollable-type smartphone), a tablet, a wearable device, a cellular phone, a personal computer (PC) (e.g., a laptop and / or desktop), and / or other similar computing devices. The electronic device (100) may authenticate a user with respect to the wearable device (110) by entering a registered password (or entering a registered pattern, or entering registered fingerprint information) through the display (230) while a communication link (115) between the electronic device (100) and the wearable device (110) is established.

[0026] A wearable device (110) may request an electronic device (100) to authenticate a user regarding the wearable device (110) in order to perform a service provided through user authentication. Authentication of a user regarding the wearable device (110) through the electronic device (100) every time the wearable device (110) performs a service provided through user authentication may cause inconvenience to the user. A solution may be required to resolve the inconvenience of the user having to repeatedly authenticate the user through the electronic device (100).

[0027] To resolve this inconvenience, the electronic device (100) may operate a timer for authenticating a user regarding the wearable device (110) based on authenticating a user regarding the electronic device (100). The electronic device (100) may transmit a signal to the wearable device (110) indicating that a user is authenticated regarding the wearable device (110) based on receiving a request from the wearable device (110) to authenticate a user regarding the wearable device (110) before the expiration of the timer. The wearable device (110) may perform a service provided through user authentication based on receiving the signal from the electronic device (100). The electronic device (100) and the wearable device (110) may execute operations exemplified in the description of FIGS. 3 to 7b to authenticate a user regarding the wearable device (110). The electronic device (100) and the wearable device (110) may include components for performing the above operations. The components may be exemplified within the description of FIG. 2.

[0028] FIG. 2 is a simplified block diagram of an exemplary electronic device and a wearable device.

[0029] Referring to FIG. 2, the electronic device (200) may be one of various types of mobile devices, such as smartphones having various form factors (e.g., bar-type smartphones, foldable-type smartphones, or rollable-type smartphones), tablets, wearable devices, cellular phones, personal computers (PCs) (e.g., laptops and / or desktops), and / or other similar computing devices. For example, the electronic device (200) may be referred to as a central device, a client device, a primary device, or a main device. For example, the electronic device (200) may include or correspond to the electronic device (100) of FIG. 1. For example, the electronic device (200) may include at least a part of the electronic device (801) of FIG. 8 or correspond to at least a part of the electronic device (801) of FIG. 8. For example, the electronic device (200) may include at least one processor (210) (e.g., processor (820) of FIG. 8), memory (220) (e.g., memory (830) of FIG. 8), display (230) (e.g., display module (860) of FIG. 8), and / or communication circuit (240) (e.g., communication module (890) of FIG. 8).

[0030] At least one processor (210) may include a processing circuit. For example, at least one processor (210) may include a CPU (central processing unit) (e.g., including a processing circuit). For example, at least one processor (210) may include a GPU (graphic processing unit) (e.g., including a processing circuit) and / or an NPU (neural processing unit) (e.g., including a processing circuit). For example, at least one processor (210) may be described as an application processor. For example, at least one processor (210) may be configured to control a memory (220), a display (230), and / or a communication circuit (240). At least one processor (210) may be configured to execute instructions stored in memory (220) individually or collectively to cause an electronic device (200) (or electronic device (100)) to perform at least some of the operations illustrated in the description of FIG. 1. At least one processor (210) may be configured to execute instructions stored in memory (220) to cause the electronic device (200) to perform at least some of the operations illustrated in the description of FIGS. 3 through 7b.

[0031] For example, the term “processor” as used herein, including in the claims, may include various processing circuits comprising at least one processor, and one or more of said at least one processor may be configured to perform the various functions described below in a distributed manner, individually and / or collectively. As used below, where “processor,” “at least one processor,” and “one or more processors” are described as being configured to perform various functions, these terms encompass, for example, but not limited to, situations where one processor performs some of the cited functions and another processor(s) perform other parts of the cited functions, and also situations where one processor can perform all of the cited functions. Additionally, said at least one processor may include a combination of processors that perform the enumerated / disclosed various functions, for example, in a distributed manner. At least one processor may execute program instructions to achieve or perform the various functions.

[0032] The memory (220) may include one or more storage media. For example, the memory (220) may store various data used by at least one component of the electronic device (200) (e.g., at least one processor (210), display (230), and / or communication circuit (240)). For example, the data may include input data or output data for software and related commands. The memory (220) may include volatile memory or non-volatile memory.

[0033] A display (230) can output visualized information under the control of at least one processor (210). For example, the display (230) may include a flat panel display (FPD) and / or electronic paper. The FPD may include a liquid crystal display (LCD), a plasma display panel (PDP), and / or one or more light emitting diodes (LEDs). For example, the LEDs may include organic LEDs (OLEDs). The display (230) may include a touch sensor configured to detect a touch, or a pressure sensor configured to measure the intensity of the force generated by the touch. For example, the display (230) may be configured to display information. For example, the display (230) may be configured to receive user input. For example, a display (230) that supports touch functions may be referred to as a touchscreen.

[0034] The communication circuit (240) may include hardware components to support the transmission and / or reception of signals between the electronic device (200) and the wearable device (205). For example, the communication circuit (240) may include at least one of a modem, an antenna, and an O / E (optic / electronic) converter. The communication circuit (240) may support wireless communication such as cellular communication. The communication circuit (240) may support the transmission and / or reception of electrical signals based on various types of protocols such as Ethernet, LAN (local area network), WAN (wide area network), Wi-Fi (wireless-fidelity), Bluetooth, BLE (bluetooth low energy), Zigbee, LTE (long term evolution), and 5G NR (new radio). For example, the communication circuit (240) may be used to establish a communication link between the electronic device (200) and the wearable device (205). For example, the communication circuit (240) may be used to receive a request from the wearable device (205). For example, the communication circuit (240) may be used to transmit a signal to the wearable device (205).

[0035] The wearable device (205) may be one of wearable devices having various form factors. For example, the wearable device (205) may include a smart ring, a smart watch, a smart band, and / or smart glasses, but is not limited thereto. For example, the wearable device (205) may be referred to as a peripheral device, a secondary device, and / or a sub device. For example, the wearable device (205) may include or correspond to the wearable device (110) of FIG. 1. For example, the wearable device (205) may include or correspond to at least a part of the electronic device (804) of FIG. 8. For example, the wearable device (205) may include at least one processor (215) (e.g., processor (820) of FIG. 8), memory (225) (e.g., memory (830) of FIG. 8), NFC (near field communication) circuit (235), and / or communication circuit (245) (e.g., communication module (890) of FIG. 8).

[0036] At least one processor (215) may include a processing circuit. For example, at least one processor (215) may include a CPU (central processing unit) (e.g., including a processing circuit). For example, at least one processor (215) may include a GPU (graphic processing unit) (e.g., including a processing circuit) and / or an NPU (neural processing unit) (e.g., including a processing circuit). For example, at least one processor (215) may be described as an application processor. For example, at least one processor (215) may be configured to control a memory (225), an NFC circuit (235), and / or a communication circuit (245). At least one processor (215) may be configured to execute instructions stored in memory (225) individually or collectively to cause the wearable device (205) (or wearable device (110)) to perform at least some of the operations illustrated in the description of FIG. 1. At least one processor (215) may be configured to execute instructions stored in memory (225) to cause the wearable device (205) to perform at least some of the operations illustrated in the description of FIGS. 3 through 7b.

[0037] The memory (225) may include one or more storage media. For example, the memory (225) may store various data used by at least one component of the wearable device (205) (e.g., at least one processor (215), NFC circuit (235), and / or communication circuit (245)). For example, the data may include input data or output data for software and related commands. The memory (225) may include volatile memory or non-volatile memory.

[0038] The NFC circuit (235) may be configured to perform NFC. For example, NFC may be described as a wireless communication technology that enables two devices to recognize each other and exchange data in a band of about 13.56 MHz (e.g., from about 13.56 MHz to 13.57 MHz). For example, the NFC circuit (235) may be configured to receive a signal (or data) from an external electronic device or to transmit a signal (or data) to an external electronic device.

[0039] The communication circuit (245) may include hardware components to support the transmission and / or reception of signals between the electronic device (200) and the wearable device (205). For example, the communication circuit (245) may include at least one of a modem, an antenna, and an O / E (optic / electronic) converter. The communication circuit (245) may support wireless communication such as cellular communication. The communication circuit (245) may support the transmission and / or reception of electrical signals based on various types of protocols such as Ethernet, LAN (local area network), WAN (wide area network), Wi-Fi (wireless-fidelity), Bluetooth, BLE (bluetooth low energy), Zigbee, LTE (long term evolution), and 5G NR (new radio). For example, the communication circuit (245) may be used to establish a communication link between the electronic device (200) and the wearable device (205). For example, the communication circuit (245) may be used to receive a signal from the electronic device (200). For example, the communication circuit (245) may be used to send a request to the electronic device (200).

[0040] The electronic device (200) can be connected to the wearable device (205) via direct wireless communication (250). For example, direct wireless communication (250) may include wireless communication based on a short-range communication network (or, for example, a first network (e.g., the first network (898) of FIG. 8 (e.g., Bluetooth, BLE (Bluetooth Low Energy), Wi-Fi, Wi-Fi Direct, UWB (Ultra-wide Band), and / or IrDA (Infrared Data Association))). For example, direct wireless communication (250) may be described as wireless communication in which wireless signals between an electronic device (200) and a wearable device (205) do not pass through another device (e.g., a server and / or an access point). For example, the electronic device (200) may be connected to the wearable device (205) via direct wireless communication (250) by establishing a communication link with the wearable device (205) using a communication circuit (240).

[0041] The electronic device (200) and wearable device (205) illustrated in the description of FIG. 2 may perform at least some of the operations illustrated in the descriptions of FIG. 3 through 7b. For example, the operations illustrated in the descriptions of FIG. 3 through 7b may be caused by (or within) the electronic device (200) (or wearable device (205)) under the control of at least one processor (210) (or at least one processor (215)).

[0042] FIG. 3 is a signal flow diagram between an exemplary electronic device and a wearable device for driving a timer for user authentication regarding a wearable device.

[0043] Referring to FIG. 3, in operation 300, at least one processor (210) of the electronic device (200) can establish a communication link between the electronic device (200) and the wearable device (205) using a communication circuit (240). The communication link between the electronic device (200) and the wearable device (205) can be described as a communication link for direct wireless communication (250) of FIG. 2. For example, at least one processor (215) of the wearable device (205) can advertise (or broadcast) an advertising packet using a communication circuit (245). At least one processor (210) can receive the advertised (or broadcast) advertising packet from the wearable device (205) using a communication circuit (240). At least one processor (210) may transmit a connection request to a wearable device (205) using a communication circuit (240) based on receiving an advertising packet. At least one processor (215) may receive a connection request from an electronic device (200) using a communication circuit (245). At least one processor (215) may establish the communication link using a communication circuit (245) based on receiving a connection request from the electronic device (200). At least one processor (210) may establish the communication link using a communication circuit (240) based on transmitting a connection request. For example, at least one processor (210) may perform the following operations (e.g., operations 310 and 320) while the communication link is established.

[0044] In operation 310, at least one processor (210) may authenticate a user with respect to the electronic device (200) while the communication link is established. For example, at least one processor (210) may authenticate a user to perform unlocking of the electronic device (200), or to authenticate a user to run an application, or to authenticate a user for a service provided through user authentication. However, it is not limited thereto. At least one processor (210) may authenticate a user with respect to the electronic device (200) based on various authentication methods. For example, the above authentication methods may include a method of authenticating the user by entering a password registered through user input, a method of authenticating the user by entering a passcode registered through user input, a method of authenticating the user by entering a pattern registered through user input, a method of authenticating the user by entering fingerprint information registered through user input, a method of authenticating the user by entering face information registered through user input, a method of authenticating the user by entering iris information registered through user input, and a method of authenticating the user by entering voice information registered through user input. The user inputs may be performed through a display (230), or through a camera (not shown) of the electronic device (200), or through a microphone (not shown) of the electronic device (200). However, they are not limited thereto. Authentication of the user with respect to the electronic device (200) will be exemplified in the description of FIG. 4a.

[0045] In operation 320, at least one processor (210) may drive (or start, or activate) a timer for user authentication regarding the wearable device (205) based on user authentication regarding the electronic device (200). For example, the timer may be driven to measure the time during which user authentication regarding the wearable device (205) is valid. For example, the time of the timer may be described as the time during which user authentication regarding the wearable device (205) is valid. For example, the time of the timer may be predetermined or set (or changed) by the user. For example, the timer may be driven at the time when the user is authenticated regarding the electronic device (200). The time of the timer may be decreased as time elapses while the timer is driven. The timer may expire as the time of the timer decreases.

[0046] According to one embodiment, at least one processor (210) may pause the operation of a timer while the electronic device (200) is in an unlocked state (or in a state where the electronic device (200) is in use). As the operation of the timer is paused, the time of the timer may not decrease and may be maintained. Based on transitioning from the unlocked state of the electronic device (200) to the locked state of the electronic device (200), at least one processor (210) may resume the operation of the timer. As the operation of the timer is resumed, the time of the timer may decrease.

[0047] According to one embodiment, at least one processor (210) may display the time of a timer through a display (230) to indicate the time when user authentication is valid for the wearable device (205). According to one embodiment, at least one processor (210) may display the time when user authentication is valid for the wearable device (205) on a lock screen as the timer operation resumes. Displaying the time of a timer is illustrated in the description of FIG. 4a, but is not limited thereto.

[0048] FIG. 4a illustrates an example of authenticating a user with respect to an electronic device.

[0049] Referring to FIG. 4a, the state (400) can be described as a locked state of the electronic device (200). In the state (400), at least one processor (210) can authenticate a user with respect to the electronic device (200) to unlock the electronic device (200). For example, at least one processor (210) can receive a user input (405) for inputting fingerprint information through a display (230). At least one processor (210) can identify the fingerprint information input through the user input (405). At least one processor (210) can compare the fingerprint information input through the user input (405) with registered fingerprint information. At least one processor (210) can unlock the electronic device (200) based on the fingerprint information input through the user input (405) corresponding to the registered fingerprint information. In FIG. 4a, authentication of a user to perform unlocking is illustrated as an example, but this may be replaced with authentication of a user to run an application or authentication of a user for a service provided through user authentication. In FIG. 4a, a method of authenticating a user by inputting registered fingerprint information through user input (405) is illustrated as an example, but this may be replaced with a method of authenticating the user by inputting a registered passcode through user input, a method of authenticating the user by inputting a registered pattern through user input, a method of authenticating the user by inputting registered fingerprint information through user input, a method of authenticating the user by inputting registered face information through user input, a method of authenticating the user by inputting registered iris information through user input, or a method of authenticating the user by inputting registered voice information through user input.

[0050] According to one embodiment, in state (400), at least one processor (215) of the wearable device (205) can transmit a signal to the electronic device (200) via an NFC circuit (235). For example, at least one processor (210) can identify the wearable device (205) in contact with the electronic device (200) based on receiving a signal from the wearable device (205) via an NFC circuit (not shown). Based on identifying the wearable device (205) in contact with the electronic device (200), at least one processor (210) can drive a timer for user authentication with respect to the wearable device (205). For example, at least one processor (210) may reset the timer or increase the time of the timer based on identifying the wearable device (205) in contact with the electronic device (200) while driving a timer for user authentication with respect to the wearable device (205).

[0051] Based on user input (405), the electronic device (200) may transition from state (400) (e.g., first state) to state (410) (e.g., second state) or state (420) (e.g., third state). In state (410), at least one processor (210) may drive a timer for user authentication with respect to the wearable device (205) based on user input (405). For example, the time of the timer may vary depending on the method of authenticating the user with respect to the electronic device (200). For example, a timer driven by authenticating the user according to a high-security-level user authentication method (e.g., a user authentication method using biometric information) may have a relatively long time, and a timer driven by authenticating the user according to a relatively low-security-level user authentication method (e.g., a user authentication method using a passcode) may have a relatively short time. However, it is not limited thereto. For example, at least one processor (210) may display the time of the timer through the display (230). The time of the timer may be described as the time during which user authentication is valid with respect to the wearable device (205). By displaying the time of the timer, at least one processor (210) may notify the user of the time during which user authentication is valid with respect to the wearable device (205). The time of the timer may decrease as time elapses. At least one processor (210) may display the decreased time of the timer through the display (230) as the time of the timer decreases.

[0052] For example, at least one processor (210) can display information (415) for a wearable device (205) connected to an electronic device (200) in conjunction with the time of a timer through a display (230). At least one processor (210) can notify the user of the wearable device (205) connected to the electronic device (200) by displaying the information (415). At least one processor (210) can notify the user of the wearable device (205) having a valid user authentication time by displaying the information (415) in conjunction with the time of a timer.

[0053] In state (420), at least one processor (210) may drive a timer for user authentication with respect to the wearable device (205) based on user input (405). For example, at least one processor (210) may display the time of the timer on a status bar (or top bar) via a display (230). As the time of the timer is displayed on the status bar (or top bar), the time of the timer may be displayed simultaneously with the screen (425) of the application running in the foreground.

[0054] FIG. 4b illustrates an example of a timer time that varies depending on the hand on which the wearable device is worn.

[0055] Referring to FIG. 4b, a state (410) can be described as a state in which a wearable device (205) is worn by a user. In the state (410), the wearable device (205) may be worn on different hands of the user (e.g., right hand or left hand) or on different fingers (e.g., index finger, middle finger, or ring finger). For example, at least one processor (210) may identify user input indicating the hand (or finger) on which the wearable device (205) is worn. Based on the user input, at least one processor (210) may identify the hand (or finger) on which the wearable device (205) is worn.

[0056] As another example, at least one processor (215) of the wearable device (205) can identify the hand (or finger) on which the wearable device (205) is worn by using a sensor (not shown) of the wearable device (205) (e.g., a gyroscope or an accelerometer). At least one processor (215) can transmit a signal indicating the hand (or finger) on which the wearable device (205) is worn to an electronic device (200) via a communication link using a communication circuit (245). At least one processor (210) can receive a signal indicating the hand (or finger) on which the wearable device (205) is worn from the wearable device (205) via a communication link using a communication circuit (240). At least one processor (210) can identify the hand (or finger) on which the wearable device (205) is worn based on the signal received from the wearable device (205).

[0057] As another example, at least one processor (210) can receive a user's biometric data from a wearable device (205) via a communication link using a communication circuit (240). At least one processor (210) can further establish other communication links between the electronic device (200) and another wearable device (not shown) (e.g., a smart watch). At least one processor (210) can receive other biometric data from another wearable device (not shown) via another communication link using a communication circuit (240). At least one processor (210) can identify the hand (or finger) on which the wearable device (205) is worn based on the biometric data received from the wearable device (205) and the biometric data received from another wearable device (not shown). However, it is not limited thereto.

[0058] For example, the timer for user authentication with respect to the wearable device (205) may be set differently depending on the hand (or finger) on which the wearable device (205) is worn. For example, for a right-handed user, performing a payment using the wearable device (205) worn on the user's left hand may take relatively longer than performing a payment using the wearable device (205) worn on the user's right hand. The timer for user authentication with respect to the wearable device (205) on the user's left hand may be longer than the timer for user authentication with respect to the wearable device (205) worn on the user's right hand. However, it is not limited thereto. According to one embodiment, at least one processor (210) may change the account of payment using the wearable device (205) or change whether payment using the wearable device (205) is allowed, depending on the hand (or finger) on which the wearable device (205) is worn. However, it is not limited thereto.

[0059] For example, at least one processor (210) may cause a user to perform user input to increase the time of the timer, or to reset the timer, or to re-start the timer by displaying the time of the timer. Increasing the time of the timer or decreasing the time of the timer is exemplified in the description of FIGS. 5a through 5f.

[0060] FIGS. 5A, FIGS. 5B, FIGS. 5C, FIGS. 5D, FIGS. 5E, FIGS. 5F, and FIGS. 5G are flowcharts illustrating exemplary operations of an electronic device for increasing or decreasing the time of a timer for user authentication with respect to a wearable device.

[0061] Referring to FIG. 5a, in operation 500, at least one processor (210) may authenticate a user with respect to the electronic device (200) after the timer is activated. Authentication of a user with respect to the electronic device (200) after the timer is activated may be performed while a communication link between the electronic device (200) and the wearable device (205) is established. For example, the user authentication method with respect to the electronic device (200) after the timer is activated may correspond to the user authentication method with respect to the electronic device (200) before the timer is activated, or may be different from the user authentication method with respect to the electronic device (200) before the timer is activated. As an example, but not limited to, at least one processor (210) may authenticate a user to execute an application after authenticating a user to perform unlocking of the electronic device (200), or authenticate a user for a service provided through user authentication, or authenticate a user again to perform unlocking of the electronic device (200). However, it is not limited thereto.

[0062] In operation 505, authentication of the user with respect to the electronic device (200) after the timer has been driven may be performed before the timer expires or after the timer expires. For example, whether authentication of the user with respect to the electronic device (200) was performed before the timer expires may be determined based on the time when the user was authenticated with respect to the electronic device (200) and the time when the timer expires.

[0063] In operation 510, at least one processor (210) may increase the time of the timer (or decrease the time of the timer slowly) based on authenticating a user regarding the electronic device (200) before the timer expires. For example, the increase in the time of the timer may be described as an increase in the time during which the authentication of the user regarding the wearable device (205) is valid. For example, as the user regarding the electronic device (200) is authenticated before the timer expires, the user of the electronic device (200) may be described as being retained. For example, the user authenticated regarding the electronic device (200) may be included among the users registered with the electronic device (200). As the user authenticated regarding the electronic device (200) is retained, the security of the electronic device (200) may be maintained. As the security of the electronic device (200) is maintained, at least one processor (210) may increase the time of the timer (or decrease the time of the timer slowly). As the timer time increases (the timer time decreases slowly), the convenience of authenticating the user with respect to the wearable device (205) for the service provided through user authentication may increase.

[0064] For example, the duration of the incremented timer may be predetermined or set (or changed) by the user. For example, the duration of the incremented timer may vary depending on the user authentication method. For example, it may be more difficult for another user not registered in the electronic device (200) to authenticate the user in the electronic device (200) using the biometric information (e.g., fingerprint information, iris information, and / or voice information) of the user registered in the electronic device (200) than it is to authenticate the user in the electronic device (200) using a password (or passcode, or pattern) registered in the electronic device (200). For example, the duration of the incremented timer may be greater than the duration of the incremented timer when authenticating the user in the electronic device (200) using a password (or passcode, or pattern). For example, the duration of the incremented timer may vary depending on the applications executed through user authentication. For example, the time of a timer increased upon user authentication to run a high-security application (e.g., a banking application) may be longer than the time of a timer increased upon user authentication to run a low-security application.

[0065] According to one embodiment, at least one processor (210) can identify the state of charge (SoC) of a rechargeable battery (not shown) of an electronic device (200). For example, at least one processor (210) can identify that the SoC of the rechargeable battery (not shown) is less than a threshold SoC. Even if at least one processor (210) authenticates a user regarding the electronic device (200) before the timer expires, if the SoC of the rechargeable battery (not shown) is less than a threshold SoC, the timer may be refrained from increasing.

[0066] In operation 515, at least one processor (210) may restart (or start, or activate) the timer based on authenticating a user with respect to the electronic device (200) after the timer expires. Restarting the timer may correspond to operation 320 of FIG. 3.

[0067] Referring to FIG. 5b, in operation 520, at least one processor (210) can identify that user authentication for the electronic device (200) has failed before the expiration of the timer. At least one processor (210) can compare information entered via user input (fingerprint information, iris information, voice information, password, passcode, and / or pattern) with registered information. At least one processor (210) can identify that user authentication for the electronic device (200) has failed based on the entered information which is different from the registered information. At least one processor (210) can identify that the number of times user authentication for the electronic device (200) has failed exceeds (or reaches) a reference number. For example, the reference number may be predetermined or set (or changed) by the user.

[0068] In operation 525, at least one processor (210) may expire a timer, or decrease the time of a timer, or rapidly decrease the time of a timer based on the number of times the number of failures to authenticate a user regarding the electronic device (200) exceeds (or reaches) a reference number. For example, the decrease in the time of a timer may be described as a decrease in the time during which the authentication of a user regarding the wearable device (205) is valid. For example, the decreased time of a timer may be predetermined or set (or changed) by the user. For example, as the authentication of a user regarding the electronic device (200) fails before the timer expires, the security of the electronic device (200) may not be maintained. As the security of the electronic device (200) is not maintained, at least one processor (210) may expire a timer or decrease the time of a timer. As the timer expires, or the time of the timer decreases, or the time of the timer decreases rapidly, it may be required to authenticate the user again regarding the electronic device (200) in order to authenticate the user regarding the wearable device (205). For example, at least one processor (210) can increase the security of the wearable device (205) by expiring the timer, or decreasing the time of the timer, or rapidly decreasing the time of the timer.

[0069] Referring to FIG. 5c, in operation 530, at least one processor (210) can identify that the communication link between the electronic device (200) and the wearable device (205) has been released before the expiration of the timer. For example, the communication link may be released normally (or regularly). For example, at least one processor (210) (or at least one processor (215)) may release the communication link normally (or regularly) based on user input.

[0070] For example, a link supervision timeout (LSTO) occurring within an electronic device (200) can be described as a link loss that occurs when no packet is received from a wearable device (205) for a certain time (certain time or certain time duration) without normally (or regularly) releasing the communication link. For example, at least one processor (210) can transmit a first packet to the wearable device (205) via the communication link using a communication circuit (240). At least one processor (215) can successfully receive the first packet from the electronic device (200) via the communication link using a communication circuit (245). The successfully received first packet can be described as a packet in which the payload header check of the first packet and the cyclic redundancy check (CRC) of the first packet have been successfully performed.

[0071] For example, at least one processor (215) may transmit an acknowledgment packet to an electronic device (200) via the communication link using a communication circuit (245) based on receiving a first packet. At least one processor (210) may receive an acknowledgment packet from a wearable device (205) via the communication link using a communication circuit (240). At least one processor (210) may identify that the first packet has been successfully received by the wearable device (205) based on receiving an acknowledgment packet from the wearable device (205).

[0072] For example, the transmission power of the acknowledgment packet may be relatively lower than the transmission power of the first packet. Because the transmission power of the acknowledgment packet is relatively low, at least one processor (210) may not receive the acknowledgment packet from the wearable device (205). For example, a reception synchronization timeout may occur within the electronic device (200) as a result of failing to receive the acknowledgment packet. At least one processor (210) may drive (or start, or activate) the LSTO timer of the electronic device (200) in accordance with the reception synchronization timeout. The LSTO timer of the electronic device (200) may be described as a timer used by the electronic device (200) to detect the occurrence of an LSTO.

[0073] Since at least one processor (210) does not receive an acknowledgment packet, it may use a communication circuit (240) to transmit a second packet (e.g., a retransmission packet) to the wearable device (205) via the communication link. At least one processor (215) may use a communication circuit (245) to receive a second packet from the electronic device (200) via the communication link. Based on receiving a second packet from the electronic device (200), at least one processor (215) may use a communication circuit (245) to transmit an acknowledgment packet to the electronic device (200) via the communication link.

[0074] The size of the wearable device (205) may be smaller than the size of the electronic device (200). Because the size of the wearable device (205) is smaller than the size of the electronic device (200), the capacity of the rechargeable battery of the wearable device (205) may be less than the capacity of the rechargeable battery of the electronic device (200). Due to the relatively smaller capacity of the rechargeable battery of the wearable device (205) compared to the rechargeable battery of the electronic device (200), the communication circuit (245) of the wearable device (205) may be deactivated based on a period. For example, the period during which the communication circuit (245) of the wearable device (205) is deactivated (or activated) may be reduced based on authenticating a user with respect to the electronic device (200). For example, the communication circuit (245) of the wearable device (205) may be disabled based on a first period (e.g., 10 seconds) before authenticating the user with respect to the electronic device (200), and the communication circuit (245) of the wearable device (205) may be disabled based on a second period (e.g., 1 second) after authenticating the user with respect to the electronic device (200). However, it is not limited thereto. For example, while the communication circuit (245) of the wearable device (205) is disabled, at least one processor (215) may not be able to send an acknowledgment packet to the electronic device (200). At least one processor (210) may not successfully receive an acknowledgment packet from the wearable device (205). As the at least one processor (210) fails to successfully receive an acknowledgment packet, it may continue to drive the LSTO timer of the electronic device (200).

[0075] For example, because the transmission power of the acknowledgment packet is relatively low, at least one processor (210) may not successfully receive the acknowledgment packet from the wearable device (205). As the at least one processor (210) fails to successfully receive the acknowledgment packet, it may continue to drive the LSTO timer of the electronic device (200).

[0076] At least one processor (210) can receive an acknowledgment packet from a wearable device (205) via the communication link using a communication circuit (240). At least one processor (210) can identify a CRC error that occurred while performing a CRC on the acknowledgment packet received from the wearable device (205). At least one processor (210) can maintain driving an LSTO timer of an electronic device (200) according to the CRC error.

[0077] For example, the LSTO timer of the electronic device (200) may expire according to the receive synchronization timeout. At least one processor (210) may identify the expiration of the LSTO timer of the electronic device (200) by identifying that the LSTO timeout period has elapsed. At least one processor (210) may release the communication link based on the expiration of the LSTO timer.

[0078] In operation 535, at least one processor (210) may expire a timer or decrease the time of a timer based on identifying that the communication link has been disconnected. For example, the decrease in the time of a timer may be described as the time during which user authentication regarding the wearable device (205) is valid being reduced. For example, the reduced time of a timer may be predetermined or set (or changed) by a user. For example, as the communication link is disconnected, services provided through user authentication regarding the wearable device (205) by a user of the electronic device (200) and another user may be performed. For example, as the communication link is disconnected, the security of the wearable device (205) may not be maintained. Because the security of the wearable device (205) is not maintained, at least one processor (210) may expire a timer or decrease the time of a timer. As the timer expires or the time of the timer decreases, it may be required to authenticate the user again regarding the electronic device (200) in order to authenticate the user regarding the wearable device (205). For example, at least one processor (210) can increase the security of the wearable device (205) by expiring the timer or decreasing the time of the timer.

[0079] According to one embodiment, at least one processor (210) can identify the strength of a signal (or the strength of a radio wave, or the strength of a communication) received from a wearable device (205) while the communication link is established. Based on identifying the strength of a signal (or the strength of a radio wave, or the strength of a communication) received from a wearable device (205) that is smaller than a reference size, the at least one processor (210) may expire a timer or decrease the time of a timer. For example, the reference size may be predetermined or set (or changed) by a user. For example, if the strength of a signal received from a wearable device (205) is smaller than the reference size, the distance between the electronic device (200) and the wearable device (205) may be relatively far. For example, a service provided through user authentication regarding the wearable device (205) by a user of the electronic device (200) and another user may be performed. For example, if the distance between the electronic device (200) and the wearable device (205) is relatively far, the security of the wearable device (205) may not be maintained. Because the security of the wearable device (205) is not maintained, at least one processor (210) may expire the timer or decrease the time of the timer. As the timer expires or the time of the timer decreases, it may be required to authenticate the user again regarding the electronic device (200) in order to authenticate the user regarding the wearable device (205). For example, at least one processor (210) may increase the security of the wearable device (205) by expiring the timer or decreasing the time of the timer.

[0080] Referring to FIG. 5d, in operation 540, at least one processor (215) can identify that the user is in a sleep state by using at least one sensor (not shown) of the wearable device (205). For example, at least one sensor may include at least one of an accelerometer, a gyroscope, a photoplethysmography (PPG) sensor, a barometric pressure sensor, an electrode sensor, a body temperature sensor, a heart rate variability (HRV) sensor, and a blood glucose sensor. Based on the identification, at least one processor (215) can transmit a signal indicating that the user is in a sleep state to the electronic device (200) via the communication link using the communication circuit (245). At least one processor (210) can receive a signal indicating that the user is in a sleep state from the wearable device (205) via the communication link using the communication circuit (240).

[0081] In operation 545, at least one processor (210) may maintain the time of the timer or slow down the time of the timer based on receiving a signal from the wearable device (205) indicating that the user is in a sleep state before the timer expires. For example, maintaining the time of the timer may be described as maintaining the time during which the user's authentication with respect to the wearable device (205) is valid. For example, slowing down the time of the timer may be described as maintaining the time during which the user's authentication with respect to the wearable device (205) is valid for a relatively long period. For example, while the user is in a sleep state, the user of the electronic device (200) may be maintained. For example, the user authenticated with respect to the electronic device (200) may be included among the users registered with the electronic device (200). As the user authenticated with respect to the electronic device (200) is maintained, the security of the electronic device (200) may be maintained. As the security of the electronic device (200) is maintained, at least one processor (210) may maintain the time of the timer (or slowly decrease the time of the timer). As the time of the timer is maintained (or slowly decreases the time of the timer), the convenience of authenticating the user with respect to the wearable device (205) for services provided through user authentication may be increased.

[0082] According to one embodiment, at least one processor (210) may expire the timer based on receiving a signal from the wearable device (205) indicating that the user is in a sleep state before the timer expires. However, it is not limited thereto.

[0083] Referring to FIG. 5e, in operation 550, at least one processor (215) can acquire a user’s biometric data using at least one sensor (not shown) of the wearable device (205). For example, at least one sensor (not shown) may include at least one of an accelerometer, a gyroscope, a PPG sensor, a pressure sensor, an electrode sensor, a body temperature sensor, an HRV sensor, and a blood glucose sensor. By example, without limitation, the user’s biometric data may include data on the user’s condition, data on the user’s movement (e.g., step count data for the user), and / or data on the user’s heart rate. The user’s biometric data may include the regularity or variability of the user’s heart rate, the user’s pulse (or change in blood volume within the blood vessels), the skin temperature of a part of the user’s body, the user’s electrodermal activity (EDA), the user’s blood glucose level, atmospheric pressure around the wearable device (205), the acceleration of the wearable device (205), and / or the angular velocity of the wearable device (205). However, it is not limited to this.

[0084] At least one processor (215) can transmit the user's biometric data to the electronic device (200) via the communication link using the communication circuit (245). At least one processor (210) can receive the user's biometric data from the wearable device (205) via the communication link using the communication circuit (240).

[0085] In operation 555, at least one processor (210) can compare the user's biometric data received from the wearable device (205) before the expiration of the timer with other biometric data of the user obtained within the electronic device (200). The electronic device (200) may further include at least one sensor (not shown). For example, at least one sensor (not shown) may include at least one of an accelerometer, a gyroscope, a PPG sensor, a pressure sensor, an electrode sensor, a body temperature sensor, an HRV sensor, and a blood glucose sensor. At least one processor (210) can obtain other biometric data of the user using at least one sensor (not shown). At least one processor (210) can identify whether the user's biometric data corresponds to other biometric data of the user by comparing the user's biometric data with other biometric data of the user.

[0086] In operation 560, at least one processor (210) may increase the time of the timer based on identifying that the user's biometric data corresponds to other biometric data of the user before the timer expires. For example, the increase in the time of the timer may be described as an increase in the time during which the user's authentication is valid with respect to the wearable device (205). For example, the increased time of the timer may be predetermined or set (or changed) by the user. For example, as the biometric data received from the wearable device (205) corresponds to other biometric data obtained within the electronic device (200), the user of the wearable device (205) may correspond to the user of the electronic device (200). As the user authenticated with respect to the electronic device (200) corresponds to the user of the wearable device (205), the security of the electronic device (200) may be maintained. As the security of the electronic device (200) is maintained, at least one processor (210) may increase the time of the timer. As the time of the timer increases, the convenience of authenticating the user with respect to the wearable device (205) for the service provided through user authentication may increase.

[0087] In operation 565, at least one processor (210) may expire the timer or decrease the time of the timer based on identifying that the user's biometric data is different from other biometric data of the user before the timer expires. For example, the decrease in the time of the timer may be described as a decrease in the time during which the user's authentication is valid with respect to the wearable device (205). For example, the time of the decreased timer may be predetermined or set (or changed) by the user. For example, if the biometric data received from the wearable device (205) is different from other biometric data obtained within the electronic device (200), the user of the wearable device (205) may be different from the user of the electronic device (200). For example, if the user of the wearable device (205) is different from the user of the electronic device (200), the security of the wearable device (205) may not be maintained. As the security of the wearable device (205) is not maintained, at least one processor (210) may expire the timer or decrease the time of the timer. As the timer expires or the time of the timer decreases, it may be required to authenticate the user again regarding the electronic device (200) in order to authenticate the user regarding the wearable device (205). For example, at least one processor (210) may increase the security of the wearable device (205) by expiring the timer or decreasing the time of the timer.

[0088] Referring to FIG. 5f, in operation 570, at least one processor (215) can identify whether the wearable device (205) is worn by a user by using at least one sensor (not shown). For example, the at least one sensor may include at least one of a gesture sensor, a barometric pressure sensor, a proximity sensor, a magnetic sensor, an accelerometer, a grip sensor, a color sensor, an IR (infrared) sensor, a biosensor, a temperature sensor, a humidity sensor, and an illuminance sensor.

[0089] In operation 575, at least one processor (215) may, based on identifying that the wearable device (205) is worn by a user, transmit a signal to the electronic device (200) via the communication link using the communication circuit (245) indicating that the wearable device (205) is worn by a user. At least one processor (210) may, using the communication circuit (240), receive a signal from the wearable device (205) via the communication link indicating that the wearable device (205) is worn by a user.

[0090] In operation 580, at least one processor (210) may increase the time of the timer based on receiving a signal from the wearable device (205) indicating that the wearable device (205) is worn by a user before the timer expires. For example, the increase in the time of the timer may be described as an increase in the time during which the user's authentication is valid with respect to the wearable device (205). For example, the increased time of the timer may be predetermined or set (or changed) by the user. For example, as the wearable device (205) is worn by the user, an authenticated user with respect to the electronic device (200) may be maintained. As an authenticated user with respect to the electronic device (200) is maintained, the security of the electronic device (200) may be maintained. As the security of the electronic device (200) is maintained, at least one processor (210) may increase the time of the timer. As the time of the timer increases, the convenience of authenticating the user with respect to the wearable device (205) for the service provided through user authentication may increase.

[0091] According to one embodiment, at least one processor (210) can identify the state of charge (SoC) of a rechargeable battery (not shown) of an electronic device (200). For example, at least one processor (210) can identify that the SoC of the rechargeable battery (not shown) is less than a threshold SoC. Even if at least one processor (210) receives a signal from the wearable device (205) indicating that the wearable device (205) is being worn by a user before the timer expires, if the SoC of the rechargeable battery (not shown) is less than a threshold SoC, the processor (210) may refrain from increasing the time of the timer.

[0092] In operation 585, at least one processor (215) may, based on identifying that the wearable device (205) is not worn by a user, transmit a signal to the electronic device (200) via the communication link using the communication circuit (245) indicating that the wearable device (205) is not worn by a user. At least one processor (210) may, using the communication circuit (240), receive a signal from the wearable device (205) via the communication link indicating that the wearable device (205) is not worn by a user.

[0093] In operation 590, based on receiving a signal from the wearable device (205) indicating that the wearable device (205) is not being worn by a user before the timer expires, the timer may be expired or the timer may be reduced. For example, the reduction of the timer may be described as the time during which the user's authentication regarding the wearable device (205) is valid being reduced. For example, the reduced timer may be predetermined or set (or changed) by the user. For example, as the wearable device (205) is not being worn by a user, the user authenticated regarding the electronic device (200) may change. For example, as the user authenticated regarding the electronic device (200) changes, the security of the wearable device (205) may not be maintained. As the security of the wearable device (205) is not maintained, at least one processor (210) may expire the timer or reduce the timer. As the timer expires or the time of the timer decreases, it may be required to authenticate the user again regarding the electronic device (200) in order to authenticate the user regarding the wearable device (205). For example, at least one processor (210) can increase the security of the wearable device (205) by expiring the timer or decreasing the time of the timer.

[0094] Referring to FIG. 5g, in operation 595, the electronic device (200) may be connected to an external electronic device (e.g., a charging device) through a port (not shown) of the electronic device (200), or may be wirelessly connected to an external electronic device (e.g., a wireless charging device) that is in contact (or separated) from the electronic device (200). For example, at least one processor (210) may charge the electronic device (200) based on receiving external power from an external electronic device (e.g., a charging device or a wireless charging device) connected to the electronic device (200). At least one processor (210) may identify that the electronic device (200) is connected to an external electronic device (e.g., a charging device or a wireless charging device).

[0095] In operation 596, at least one processor (210) may maintain the time of the timer or slow down the time of the timer based on identifying that the electronic device (200) is connected to an external electronic device (e.g., a charging device or a wireless charging device) before the timer expires. For example, maintaining the time of the timer may be described as maintaining the time during which user authentication regarding the wearable device (205) is valid. For example, slow down the time of the timer may be described as maintaining the time during which user authentication regarding the wearable device (205) is valid for a relatively long period. For example, while the electronic device (200) is being charged, the user of the electronic device (200) may be maintained. For example, the user authenticated regarding the electronic device (200) may be included among the users registered with the electronic device (200). As the user authenticated regarding the electronic device (200) is maintained, the security of the electronic device (200) may be maintained. As the security of the electronic device (200) is maintained, at least one processor (210) may maintain the time of the timer (or slowly decrease the time of the timer). As the time of the timer is maintained (or slowly decreases the time of the timer), the convenience of authenticating the user with respect to the wearable device (205) for services provided through user authentication may be increased.

[0096] According to one embodiment, at least one processor (210) may expire a timer based on identifying that the electronic device (200) is connected to an external electronic device (e.g., a charging device or a wireless charging device). However, it is not limited thereto.

[0097] At least one processor (215) may authenticate a user with respect to a wearable device (205) in order to perform a service provided through user authentication. At least one processor (215) may request an electronic device (200) to authenticate a user with respect to the wearable device (205) in order to authenticate a user with respect to the wearable device (205). Whether a user is authenticated with respect to the wearable device (205) may be determined by whether the request is received before the expiration of a timer. Authentication of a user with respect to the wearable device (205) is exemplified in the description of FIG. 6.

[0098] FIG. 6 is a signal flow diagram between an exemplary electronic device and a wearable device for authenticating a user with respect to a wearable device.

[0099] Referring to FIG. 6, the wearable device (205) may be tagged (or in contact) with an external electronic device to perform services provided through user authentication via a near-field communication method (e.g., NFC method or MST (magnetic secure transmission) method). For example, the services provided through user authentication may include an electronic wallet service provided based on linkage with the external electronic device, a service of performing payment using the wearable device (205) by providing information about the user's credit card to the external electronic device, a service of opening the gate of a secure area using the wearable device (205) by providing the user's identification information to the external electronic device, a service of opening the door of the vehicle or starting the engine of the vehicle using the wearable device (205) by providing the user's vehicle information to the external electronic device, or a service of performing a bank transfer using the wearable device (205) by providing information about the user's account to the external electronic device. However, it is not limited to this.

[0100] At least one processor (215) can detect an external magnetic field using an NFC circuit (235) (or an MST circuit (not shown)) based on an external electronic device tagged (or in contact) with the wearable device (205). For example, the service may be provided by the wearable device (205) emitting information for the service externally (or transmitting it to the external electronic device) using the NFC circuit (235). For example, since the service requires the use of privacy information such as information about the credit card, identification information, vehicle information, or account information, the service may be provided through user authentication. For example, the user authentication may be performed using an electronic device (200) connected to the wearable device (205).

[0101] In operation 610, at least one processor (215) may request the electronic device (200) to authenticate a user regarding the wearable device (205) via the communication link using the communication circuit (245) based on detecting an external magnetic field. At least one processor (210) may receive a request to authenticate a user regarding the wearable device (205) from the wearable device (205) via the communication link using the communication circuit (240).

[0102] In operation 620, at least one processor (210) can identify whether the request was received from the wearable device (205) before the timer expires. For example, the time of the timer may decrease as time elapses. For example, at least one processor (210) can identify whether the timer has expired by identifying the time of the timer.

[0103] In operation 630, at least one processor (210) may, based on receiving the request from the wearable device (205) before the timer expires, use the communication circuit (240) to transmit a signal indicating that a user is authenticated with respect to the wearable device (205) via the communication link. If the request is received from the wearable device (205) before the timer expires, the time when the wearable device (205) requests user authentication and the time when the user is authenticated with respect to the electronic device (200) may be relatively close. For example, if the request is received from the wearable device (205) before the timer expires, the security of the wearable device (205) can be maintained even if a user is authenticated with respect to the wearable device (205). At least one processor (215) can receive a signal indicating that a user is authenticated with respect to the wearable device (205) from the electronic device (200) via the communication link using the communication circuit (245). According to one embodiment, at least one processor (210) can increase the time of a timer based on transmitting a signal indicating that a user is authenticated with respect to the wearable device (205) using the communication circuit (240).

[0104] In operation 640, at least one processor (215) may authenticate a user regarding the wearable device (205) based on receiving a signal from the electronic device (200) indicating that a user is authenticated regarding the wearable device (205). Based on authenticating a user regarding the wearable device (205), at least one processor (215) may use an NFC circuit (235) to emit information for the service externally (or transmit to an external electronic device tagged (or in contact) with the wearable device (205). For example, the information for the service may include information regarding the credit card, identification information, vehicle information, and / or information regarding the account. At least one processor (215) may enhance the convenience of user authentication by authenticating a user regarding the wearable device (205) without receiving an input for user authentication (or without an input for user authentication regarding the wearable device (205).

[0105] In operation 650, at least one processor (210) may, based on receiving the request from the wearable device (205) after the expiration of the timer, use the communication circuit (240) to transmit a signal indicating that the user is not authenticated with respect to the wearable device (205) via the communication link. When the request is received from the wearable device (205) after the expiration of the timer, the time when the wearable device (205) requests user authentication and the time when the user is authenticated with respect to the electronic device (200) may be relatively far apart. For example, when the request is received from the wearable device (205) after the expiration of the timer, the security of the wearable device (205) may be maintained by refraining from authenticating the user with respect to the wearable device (205). At least one processor (215) may receive a signal indicating that a user is not authenticated with respect to the wearable device (205) from the electronic device (200) via the communication link using the communication circuit (245). Based on receiving the signal indicating that a user is not authenticated with respect to the wearable device (205), at least one processor (215) may fail to authenticate a user with respect to the wearable device (205). For example, based on failing to authenticate a user with respect to the wearable device (205), at least one processor (215) may refrain from releasing information for the service to the outside.

[0106] According to one embodiment, at least one processor (210) may refrain from (or stop, or skip, or bypass, or not transmit) a signal indicating that a user is authenticated with respect to the wearable device (205) based on receiving the request from the wearable device (205) before the expiration of the timer. At least one processor (215) may fail to authenticate a user with respect to the wearable device (205) based on not receiving a signal indicating that a user is authenticated with respect to the wearable device (205) from the electronic device (200). For example, at least one processor (215) may fail to authenticate a user with respect to the wearable device (205) based on not receiving a signal indicating that a user is authenticated with respect to the wearable device (205) from the electronic device (200) within a reference time from the time the request was transmitted to the electronic device (200).

[0107] In operation 660, at least one processor (210) may display information through the display (230) indicating that the user is not authenticated with respect to the wearable device (205) based on receiving the request from the wearable device (205) before the timer expires. For example, at least one processor (210) may inform the user that authentication of the user with respect to the wearable device (205) has failed by displaying the information. For example, at least one processor (210) may further display other information through the display (230) guiding the user to authenticate the user with respect to the electronic device (200) in order to authenticate the user with respect to the wearable device (205). At least one processor (210) may guide the user to authenticate the user with respect to the electronic device (200) in order to perform the service provided through user authentication using the wearable device (205) by displaying the other information. For example, at least one processor (210) may perform operation 660 after performing operation 650, or perform operation 650 after performing operation 660. At least one processor (210) may perform operation 660 while performing operation 650, or perform operation 650 while performing operation 660. However, it is not limited thereto. According to one embodiment, based on at least one processor (210) receiving the request from the wearable device (205) before the expiration of the timer, information indicating that the user is not authenticated with respect to the wearable device (205) via the display (230) may include information guiding the at least one processor (210) to authenticate the user with respect to the electronic device (200) via the display (230) to authenticate the user with respect to the wearable device (205).

[0108] For example, at least one processor (210) may enable (or disable) user authentication regarding the wearable device (205) based on user input. For example, at least one processor (210) may set (or change) the time of a timer for user authentication regarding the wearable device (205) based on user input. Setting a timer for user authentication regarding the wearable device (205) is illustrated in the description of FIGS. 7a and 7b.

[0109] FIGS. 7A and FIGS. 7B illustrate examples of setting a timer for user authentication with respect to a wearable device.

[0110] Referring to FIG. 7a, the state (700) may be described as a state for establishing user authentication with respect to the wearable device (205). In the state (700), at least one processor (210) may display a user interface (UI) (705) for establishing user authentication with respect to the wearable device (205) via a display (230). For example, the UI (705) may be displayed via an application for configuring the electronic device (200). For example, the UI (705) may include a toggle button (or radio button, or check box) (710) for setting whether to enable user authentication with respect to the wearable device (205). At least one processor (210) may enable or disable user authentication for the wearable device (205) based on user input to the toggle button (710) in the UI (705). For example, user input to the toggle button (710) may include touch input having a contact point on the toggle button (710), input using an external electronic device (e.g., a mouse) connected to the electronic device (200), or voice input (or speech input) through a microphone (not shown) of the electronic device (200). However, it is not limited thereto.

[0111] For example, the UI (705) may include a toggle button (or radio button, or check box) (715) for setting whether to enable a timer for user authentication with respect to the wearable device (205). At least one processor (210) may enable or disable the timer based on user input to the toggle button (715) in the UI (705). For example, user input to the toggle button (715) may include a touch input having a contact point on the toggle button (715), input using an external electronic device (e.g., a mouse) connected to the electronic device (200), or voice input (or verbal input) through a microphone (not shown) of the electronic device (200). However, it is not limited thereto.

[0112] Referring to FIG. 7b, the state (720) may be described as a state for setting the time of a timer for user authentication with respect to the wearable device (205). In the state (720), at least one processor (210) may display a UI (725) for setting the time of the timer through a display (230). For example, the UI (725) may be displayed through an application for setting the electronic device (200). For example, the UI (725) may include UI objects (730) that indicate the time of the timer. At least one processor (210) may set (or change) the time of the timer based on user input regarding the UI objects (730) that indicate the time of the timer within the UI (725). For example, user input to UI objects (730) may include touch input having a contact point on the UI objects (730), input using an external electronic device (e.g., a mouse) connected to the electronic device (200), or voice input (or verbal input) through a microphone (not shown) of the electronic device (200). However, it is not limited thereto.

[0113] FIG. 7c illustrates an example of a user gesture received with respect to the finger of a user wearing a wearable device.

[0114] Referring to FIG. 7c, state (735) may be described as a state in which a user gesture is received with respect to the finger of a user wearing the wearable device (205). In state (735), at least one processor (215) of the wearable device (205) may identify the user gesture through a sensor (not shown) of the wearable device (205). For example, the user gesture may include a pinch gesture, a double pinch gesture, an unpinch gesture, and / or a finger snap gesture, but is not limited thereto.

[0115] For example, at least one processor (215) may, based on detecting an external magnetic field after receiving a user gesture, request the electronic device (200) to authenticate the user regarding the wearable device (205) via a communication link using a communication circuit (245). For example, at least one processor (215) may refrain from (or stop, or skip, or bypass, or not request) the electronic device (200) to authenticate the user regarding the wearable device (205) based on detecting an external magnetic field without receiving a user gesture. For example, if the wearable device (205) comes into contact with an external electronic device (e.g., a payment terminal) contrary to the user's intention while the timer is running, a payment using the wearable device (205) may be performed. For example, to resolve a payment made using a wearable device (205) that is performed differently from the user's intention, at least one processor (215) may request the electronic device (200) to authenticate the user regarding the wearable device (205) via a communication link using a communication circuit (245) for a payment request, based on detecting an external magnetic field after receiving a user gesture. For example, a user gesture to allow a payment made using the wearable device (205) may be set (or changed) by the user.

[0116] FIG. 7d illustrates an example of authenticating a user regarding an electronic device for an electronic wallet service.

[0117] Referring to FIG. 7d, the state (740) can be described as a state in which the electronic device (200) performs an electronic wallet service. In the state (740), at least one processor (210) can display a user interface (UI) (745) for the electronic wallet service through a display (230). For example, while displaying the UI (745), at least one processor (210) can receive a user input (750) for inputting fingerprint information through the display (230). At least one processor (210) can identify the fingerprint information input through the user input (750). At least one processor (210) can compare the fingerprint information input through the user input (405) with the registered fingerprint information. At least one processor (210) can allow payment using the electronic device (200) based on the fingerprint information input through the user input (405) corresponding to the registered fingerprint information.

[0118] For example, while payment using the electronic device (200) is allowed, at least one processor (210) may not allow payment using the wearable device (205) even if the timer is running in order to prevent duplicate payments. For example, while payment using the electronic device (200) is allowed, at least one processor (210) may refrain (or stop, or skip, or bypass, or not transmit) a signal to the wearable device (205) indicating that a user is authenticated regarding the wearable device (205) based on a request for user authentication regarding the wearable device (205) received from the wearable device (205).

[0119] For example, at least one processor (210) may expire the timer based on allowing payment using the electronic device (200). For example, at least one processor (210) may restart the timer based on the termination of allowing payment using the electronic device (200). For example, the time of the timer may be preset (or predetermined) or set (or changed) by the user. However, it is not limited thereto.

[0120] According to one embodiment, the state (755) may be described as a state in which a user is authenticated with respect to the electronic device (200) for an electronic wallet service. In the state (755), at least one processor (210) may display a UI object (760) indicating the electronic device (200) and a UI object (765) indicating the wearable device (205) through a display (230) based on authenticating the user with respect to the electronic device (200) for an electronic wallet service.

[0121] For example, at least one processor (210) may allow payment using the electronic device (200) among the electronic device (200) and the wearable device (205) based on identifying user input to the UI object (760). For example, at least one processor (210) may stop the time of a timer based on identifying user input to the UI object (760). For example, at least one processor (210) may allow payment using the wearable device (205) among the electronic device (200) and the wearable device (205) based on identifying user input to the UI object (765). For example, at least one processor (210) may increase the time of a timer based on identifying user input to the UI object (765). For example, at least one processor (210) can prevent duplicate payments by allowing payment of one of the electronic devices (200) and the wearable device (205).

[0122] FIG. 8 is a block diagram of an electronic device in a network environment according to various embodiments.

[0123] Referring to FIG. 8, in a network environment (800), an electronic device (801) may communicate with an electronic device (802) through a first network (898) (e.g., a short-range wireless communication network) or with at least one of an electronic device (804) or a server (808) through a second network (899) (e.g., a long-range wireless communication network). According to one embodiment, the electronic device (801) may communicate with the electronic device (804) through a server (808). According to one embodiment, the electronic device (801) may include a processor (820), memory (830), input module (850), sound output module (855), display module (860), audio module (870), sensor module (876), interface (877), connection terminal (878), haptic module (879), camera module (880), power management module (888), battery (889), communication module (890), subscriber identification module (896), or antenna module (897). In some embodiments, at least one of these components (e.g., connection terminal (878)) may be omitted from the electronic device (801), or one or more other components may be added. In some embodiments, some of these components (e.g., sensor module (876), camera module (880), or antenna module (897)) may be integrated into a single component (e.g., display module (860)).

[0124] The processor (820) can control at least one other component (e.g., a hardware or software component) of the electronic device (801) connected to the processor (820) by executing software (e.g., a program (840)), for example, and can perform various data processing or operations. According to one embodiment, as at least part of the data processing or operations, the processor (820) can store commands or data received from other components (e.g., a sensor module (876) or a communication module (890)) in volatile memory (832), process the commands or data stored in volatile memory (832), and store the resulting data in non-volatile memory (834). According to one embodiment, the processor (820) may include a main processor (821) (e.g., a central processing unit or an application processor) or an auxiliary processor (823) that can operate independently or together with it (e.g., a graphics processing unit, a neural processing unit (NPU), an image signal processor, a sensor hub processor, or a communication processor). For example, if the electronic device (801) includes a main processor (821) and an auxiliary processor (823), the auxiliary processor (823) may be configured to use lower power than the main processor (821) or to be specialized for a designated function. The auxiliary processor (823) may be implemented separately from the main processor (821) or as part thereof.

[0125] The auxiliary processor (823) may control at least some of the functions or states associated with at least one component of the electronic device (801) (e.g., display module (860), sensor module (876), or communication module (890)) on behalf of the main processor (821) while the main processor (821) is in an inactive (e.g., sleep) state, or together with the main processor (821) while the main processor (821) is in an active (e.g., application execution) state. According to one embodiment, the auxiliary processor (823) (e.g., image signal processor or communication processor) may be implemented as part of another functionally related component (e.g., camera module (880) or communication module (890)). According to one embodiment, the auxiliary processor (823) (e.g., neural network processing unit) may include a hardware structure specialized for processing an artificial intelligence model. The artificial intelligence model may be generated through machine learning. Such learning may be performed, for example, on the electronic device (801) itself where the artificial intelligence model is executed, or through a separate server (e.g., server (808)). The learning algorithm may 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 may include a plurality of artificial neural network layers.An artificial neural network may be 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 the hardware structure, the artificial intelligence model may include a software structure, either additionally or substantially.

[0126] The memory (830) can store various data used by at least one component of the electronic device (801) (e.g., processor (820) or sensor module (876)). The data may include, for example, software (e.g., program (840)) and input or output data for related commands. The memory (830) may include volatile memory (832) or non-volatile memory (834).

[0127] The program (840) may be stored as software in memory (830) and may include, for example, an operating system (842), middleware (844), or an application (846).

[0128] The input module (850) can receive commands or data to be used for a component of the electronic device (801) (e.g., processor (820)) from outside the electronic device (801) (e.g., user). The input module (850) may include, for example, a microphone, a mouse, a keyboard, a key (e.g., a button), or a digital pen (e.g., a stylus pen).

[0129] The sound output module (855) can output a sound signal to the outside of the electronic device (801). The sound output module (855) may include, for example, a speaker or a receiver. The speaker may be used for general purposes, such as multimedia playback or recording playback. The receiver may be used to receive incoming calls. According to one embodiment, the receiver may be implemented separately from the speaker or as part thereof.

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

[0131] The audio module (870) can convert sound into an electrical signal or, conversely, convert an electrical signal into sound. According to one embodiment, the audio module (870) can acquire sound through the input module (850) or output sound through the sound output module (855) or an external electronic device (e.g., electronic device (802)) (e.g., speaker or headphones) connected directly or wirelessly to the electronic device (801).

[0132] The sensor module (876) can detect the operating state of the electronic device (801) (e.g., power or temperature) or the external environmental state (e.g., user state) and generate an electrical signal or data value corresponding to the detected state. According to one embodiment, the sensor module (876) may include, for example, a gesture sensor, a gyroscope sensor, a barometric pressure sensor, a magnetic sensor, an accelerometer sensor, a grip sensor, a proximity sensor, a color sensor, an IR (infrared) sensor, a biosensor, a temperature sensor, a humidity sensor, or an illuminance sensor.

[0133] The interface (877) may support one or more specified protocols that can be used for the electronic device (801) to be connected directly or wirelessly to an external electronic device (e.g., electronic device (802)). According to one embodiment, the interface (877) may include, for example, a high definition multimedia interface (HDMI), a universal serial bus (USB) interface, an SD card interface, or an audio interface.

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

[0135] The haptic module (879) can convert an electrical signal into a mechanical stimulus (e.g., vibration or movement) or an electrical stimulus that the user can perceive through tactile or kinesthetic senses. According to one embodiment, the haptic module (879) may include, for example, a motor, a piezoelectric element, or an electric stimulation device.

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

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

[0138] The battery (889) can supply power to at least one component of the electronic device (801). According to one embodiment, the battery (889) may include, for example, a non-rechargeable primary battery, a rechargeable secondary battery, or a fuel cell.

[0139] The communication module (890) can support the establishment of a direct (e.g., wired) communication channel or a wireless communication channel between an electronic device (801) and an external electronic device (e.g., electronic device (802), electronic device (804), or server (808)), and the performance of communication through the established communication channel. The communication module (890) may include one or more communication processors that operate independently of the processor (820) (e.g., application processor) and support direct (e.g., wired) communication or wireless communication. According to one embodiment, the communication module (890) may include a wireless communication module (892) (e.g., cellular communication module, short-range wireless communication module, or GNSS (global navigation satellite system) communication module) or a wired communication module (894) (e.g., LAN (local area network) communication module, or power line communication module). The corresponding communication module among these communication modules can communicate with an external electronic device (804) via a first network (898) (e.g., a short-range communication network such as Bluetooth, Wi-Fi (wireless fidelity) direct, or IrDA (infrared data association)) or a second network (899) (e.g., 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 may 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 (892) can identify or authenticate the electronic device (801) within a communication network such as the first network (898) or the second network (899) using subscriber information (e.g., International Mobile Subscriber Identifier (IMSI)) stored in the subscriber identification module (896).

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

[0141] An antenna module (897) can transmit a signal or power to or from an external source (e.g., an external electronic device). According to one embodiment, the antenna module (897) may include an antenna comprising a radiator made of a conductor or a conductive pattern formed on a substrate (e.g., a PCB). According to one embodiment, the antenna module (897) 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 a first network (898) or a second network (899), may be selected from the plurality of antennas, for example, by a communication module (890). A signal or power may be transmitted or received between the communication module (890) and an external electronic device through the selected at least one antenna. According to some embodiments, in addition to the radiator, other components (e.g., a radio frequency integrated circuit (RFIC)) may be additionally formed as part of the antenna module (897).

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

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

[0144] According to one embodiment, commands or data may be transmitted or received between the electronic device (801) and an external electronic device (804) through a server (808) connected to a second network (899). Each of the external electronic devices (802, or 804) may be the same or a different type of device as the electronic device (801). According to one embodiment, all or part of the operations performed on the electronic device (801) may be performed on one or more of the external electronic devices (802, 804, or 808). For example, if the electronic device (801) needs to perform a function or service automatically or in response to a request from a user or another device, the electronic device (801) may request one or more external electronic devices to perform at least part of the function or service instead of performing the function or service itself or additionally. One or more external electronic devices that receive the above request may execute at least part of the requested function or service, or additional function or service related to the request, and transmit the result of the execution to the electronic device (801). The electronic device (801) may provide the result as is or additionally processed as at least part of the response to the request. For this purpose, for example, cloud computing, distributed computing, mobile edge computing (MEC), or client-server computing technology may be used. The electronic device (801) may provide ultra-low latency services using, for example, distributed computing or mobile edge computing. In one embodiment, the external electronic device (804) may include an Internet of Things (IoT) device. The server (808) may be an intelligent server using machine learning and / or neural networks. According to one embodiment, the external electronic device (804) or the server (808) may be included within the second network (899).The electronic device (801) 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.

[0145] The electronic device according to the various embodiments disclosed in this document may be of various forms. The electronic device may include, for example, a portable communication device (e.g., a smartphone), a computer device, a portable multimedia device, a portable medical device, a camera, a wearable device, or a consumer electronics device. The electronic device according to the embodiments of this document is not limited to the devices described above.

[0146] The various embodiments of this document and the terms used therein are not intended to limit the technical features described in this document to specific embodiments, and should be understood to include various modifications, equivalents, or substitutions of said 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 said items unless the relevant context clearly indicates otherwise. In this document, phrases such as "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" may each include any one of the items listed together in the corresponding phrase, or all possible combinations thereof. Terms such as "first," "second," or "first" or "second" may be used simply to distinguish said components from other said components and do not limit said components in any other aspect (e.g., importance or order). Where any (e.g., 1st) component is referred to as "coupled" or "connected" to another (e.g., 2nd) component, with or without the terms "functionally" or "communicationly," it means that said any component may be connected to said other component directly (e.g., via a wire), wirelessly, or through a third component.

[0147] The term “module” as used in the 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, for example. A module may be a component formed integrally, or a minimum unit of said component or a part thereof 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).

[0148] Various embodiments of the present document may be implemented as software (e.g., program (840)) comprising one or more instructions stored in a storage medium (e.g., internal memory (836) or external memory (838)) readable by a machine (e.g., electronic device (801)). For example, a processor (e.g., processor (820)) of the machine (e.g., electronic device (801)) may call at least one of the one or more instructions stored in the storage medium and execute it. This enables the machine to operate to perform at least one function according to the at least one called instruction. The one or more instructions may include code generated by a compiler or code that can be executed by an interpreter. The storage medium readable by the machine may be provided in the form of a non-transitory storage medium. Here, 'non-transient' simply 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.

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

[0150] According to various embodiments, each component (e.g., module or program) of the components described above may include a singular or multiple entities, and some of the multiple entities may be separated and placed in other components. According to various embodiments, one or more of the components or operations of the aforementioned components may be omitted, or one or more other components or operations may be added. Generally or additionally, multiple components (e.g., module or program) may be integrated into a single component. In this case, the integrated component may perform one or more functions of each of the multiple components in the same or similar manner as those performed by the corresponding component among the multiple components prior to integration. According to various embodiments, operations performed by the module, program, or other components 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.

[0151] FIG. 9a shows a perspective view of an exemplary electronic device according to one embodiment.

[0152] Referring to FIG. 9a, a wearable device (900) (e.g., the wearable device (205) of FIG. 2) may include a housing (901) comprising a first surface (911) facing a part of the user's body (e.g., a finger) and a second surface (912) opposite to the first surface (911). For example, the wearable device (900) may include a ring-shaped housing (901). For example, the wearable device (900) may be configured in a ring shape.

[0153] For example, the wearable device (900) may be referred to as a wearable device that can be worn by a user. The wearable device (900) may be worn on a part of the user's body (e.g., a finger). For example, the wearable device (900) may be worn on a part of the user's body. For example, the wearable device (900) may be fastened to a part of the user's body. For example, the wearable device (900) may be detachable from a part of the user's body. For example, the wearable device (900) may have a shape corresponding to a part of the user's body in order to be worn on a part of the user's body.

[0154] For example, the wearable device (900) may come into contact with a part of the user's body by being worn by the user. For example, the wearable device (900) may be configured to obtain information about the user through a part of the user's body by being worn by the user. For example, the information about the user may include the user's health information. However, it is not limited thereto. For example, the wearable device (900) may provide information about the user through the wearable device (900) and / or an external electronic device connected to the wearable device (900). However, it is not limited thereto.

[0155] For example, at least a portion of the first surface (911) may come into contact with a portion of the user's body when the wearable device (900) is worn by the user. For example, the first surface (911) may surround a portion of the user's body where the wearable device (900) is worn. For example, the first surface (911) may cover a portion of the user's body where the wearable device (900) is worn. For example, the first surface (911) may be configured so that the wearable device (900) is fastened to a portion of the body by pressurizing a portion of the user's body when the wearable device (900) is worn by the user. For example, the first surface (911) may be deformable by a portion of the user's body. For example, the wearable device (900) can provide information about the user through the first surface (911) based on haptic technology.

[0156] For example, the second surface (912) can form the exterior of the wearable device (900) together with the first surface (911). For example, the second surface (912) can form a ring-shaped housing (901) together with the first surface (911). For example, the second surface (912) may be a surface spaced apart from a part of the user's body when the wearable device (900) is worn by the user. For example, the first surface (911) may be referred to as the inner circumference surface of the housing (901). The second surface (912), opposite to the first surface (911), may be referred to as the outer circumference surface of the housing (901).

[0157] For example, the second surface (912) may be exposed to the outside while the wearable device (900) is worn by the user. The second surface (912) may be composed of at least one of titanium, stainless steel, and ceramic. The second surface (912) may be composed of a material for protection against external impact and / or scratches. For example, the second surface (912) may be coated with an additional material to protect the color and / or appearance of the wearable device (900).

[0158] For example, the first surface (911) may be composed of the same and / or similar material as the second surface (912). For example, at least a portion of the first surface (911) may be composed of at least one of a molding material for acquiring data, a transparent plastic, and / or glass. For example, at least a portion of the first surface (911) may be composed of a metal for identifying biosignals.

[0159] For example, the wearable device (900) may further include a hole (970) formed by a first surface (911) to allow a part of the user's body to pass through when the wearable device (900) is worn by the user. For example, the hole (970) may be penetrated by a part of the user's body when the wearable device (900) is worn by the user. The wearable device (900) may be configured to be fastened to a part of the user's body when the user wears the wearable device (900) by including a hole (970) configured to allow said part of the user's body to pass through.

[0160] For example, the wearable device (900) may further include one or more components between the first surface (911) and the second surface (912). For example, the wearable device (900) may include a communication circuit, one or more sensors, and / or a processor between the first surface (911) and the second surface (912). The arrangement of one or more components will be described later in FIG. 9b.

[0161] FIG. 9b is an example of a partial cross-sectional view of an electronic device according to one embodiment.

[0162] Referring to FIG. 9b, the wearable device (900) may be formed in a ring shape. For example, the housing (901) of the wearable device (900) may be formed in the shape of a ring that can be worn on a user's finger. FIGS. 9a and 9b illustrate a wearable device (900) in the shape of a ring with a smooth surface as an example, but are not limited thereto. For example, the wearable device (900) may be implemented as a housing comprising a plurality of planes. For example, a wearable device (900) in the shape of a ring with a non-smooth surface may also be understood as an embodiment of the present disclosure.

[0163] For example, the ring-shaped housing (901) may include a first surface (911) that contacts the user's body when worn by the user, a second surface (912) that is exposed to the outside, and a side between the first surface (911) and the second surface (912). For example, the space between the first surface (911) and the second surface (912) may include a space for including (or placing) at least one component (e.g., at least one processor (910), memory (940), communication circuit (920), first sensor (931), and second sensor (932)).

[0164] For example, a PCB may be placed between the first surface (911) and the second surface (912) of the wearable device (900). For example, at least one processor (910), a communication circuit (920), an accelerometer, a gyroscope, a PPG sensor, a temperature sensor (934), a memory (940), and / or a PMIC (954) may be placed on the PCB (951). For example, the PCB (951) may be composed of a rigid region and a flexible region. For example, the rigid region may be referred to as a rigid flexible printed circuit board (RFPCB). For example, the flexible region may be referred to as a flexible printed circuit board (FPCB).

[0165] For example, the PPG sensor may include one or more light-emitting circuits (933-1), one or more light-receiving circuits (933-2), and a control circuit (933-3). For example, one or more light-emitting circuits (933-1) and one or more light-receiving circuits (933-2) may be positioned toward a first surface (911). For example, the control circuit (933-3) may be positioned toward a second surface (912).

[0166] For example, the PMIC (954) may be used to manage the power of the wearable device (900). The PMIC (954) may be used to provide (or distribute) power to components in the wearable device (900) that require power. The PMIC (954) may support a wired charging method (e.g., terminal, pogo pin) or a wireless charging method (e.g., WPC (wireless power consortium), NFC) for charging the wearable device (900) through the charging interface (953).

[0167] For example, a battery (952) may be disposed between a first surface (911) and a second surface (912) of a wearable device (900). The battery (952) may consist of at least one battery (or battery pack). For example, the battery (952) may be configured such that at least one battery is connected in series and / or parallel. For example, the battery (952) may consist of a flexible battery pack. For example, the battery (952) may be charged and / or discharged as a secondary battery. For example, the material constituting the battery (952) may be configured in various ways. For example, the material constituting the battery (952) may include at least one of lithium ion and mercury.

[0168] For example, an antenna (955) may be positioned between the first surface (911) and the second surface (912) of the wearable device (900). For example, the antenna (955) may consist of a single antenna and / or multiple segmented antennas. For example, the antenna (955) may be formed as part of the housing (901) of the wearable device (900). For example, the antenna (955) may be electrically connected to a communication circuit (920) via a PCB (951).

[0169] Although not illustrated, the wearable device (900) may include various additional components in addition to the illustrated components. For example, the wearable device (900) may include a display. The display may be placed on the outer surface of the housing (901).

[0170] The technical problems to be solved in this disclosure are not limited to those mentioned above, and other technical problems not mentioned will be clearly understood by those skilled in the art to which this disclosure pertains.

[0171] The electronic device described above (e.g., the electronic device (200) of FIG. 2) may include at least one processor (e.g., at least one processor (210) of FIG. 2) comprising a processing circuit, a communication circuit (e.g., the communication circuit (240) of FIG. 2), and a memory (e.g., the memory (220) of FIG. 2) comprising one or more storage media configured to store one or more programs configured to be executed individually or collectively by the at least one processor. The one or more programs may include instructions that cause the electronic device to authenticate a user with respect to the electronic device while a communication link between the electronic device and a wearable device (e.g., the wearable device (205) of FIG. 2) is established using the communication circuit. The one or more programs may include instructions that cause the electronic device to run a timer for authenticating the user with respect to the wearable device based on authenticating the user with respect to the electronic device. The one or more programs above may include instructions that cause the electronic device to receive a request to authenticate the user with respect to the wearable device from the wearable device via the communication link using the communication circuit. The one or more programs above may include instructions that cause the electronic device to transmit a signal indicating that the user is authenticated with respect to the wearable device via the communication link using the communication circuit, based on receiving the request before the expiration of the timer.

[0172] For example, the above one or more programs may include instructions that cause the electronic device to transmit another signal indicating that the user is not authenticated with respect to the wearable device via the communication link using the communication circuit, based on receiving the request after the expiration of the timer.

[0173] For example, the one or more programs may include instructions that cause the electronic device to authenticate the user with respect to the electronic device while the timer is running. The one or more programs may include instructions that cause the electronic device to reset or increase the time of the timer based on authenticating the user with respect to the electronic device before the expiration of the timer.

[0174] For example, the above one or more programs may include instructions that cause the electronic device to decrease the time of the timer based on identifying that the number of times the user has failed to authenticate the electronic device before the expiration of the timer exceeds a reference number.

[0175] For example, the above one or more programs may include instructions that cause the electronic device to expire the timer based on identifying that the number of times the user has failed to authenticate the electronic device before the expiration of the timer exceeds a reference number.

[0176] For example, the above one or more programs may include instructions that cause the electronic device to expire the timer based on identifying that the communication link was released before the expiration of the timer.

[0177] For example, the one or more programs may include instructions that cause the electronic device to transmit a packet to the wearable device via the communication link using the communication circuit. The one or more programs may include instructions that cause the electronic device to release the communication link based on identifying that an acknowledgment packet is not received from the wearable device within a reference time from the time the packet was transmitted.

[0178] For example, the one or more programs may include instructions that cause the electronic device to receive biometric data for the user from the wearable device via the communication link using the communication circuit. The one or more programs may include instructions that cause the electronic device to compare the biometric data with other biometric data for the user obtained with respect to the electronic device based on receiving the biometric data before the expiration of the timer. The one or more programs may include instructions that cause the electronic device to increase the time of the timer based on the biometric data corresponding to the other biometric data.

[0179] For example, the above one or more programs may include instructions that cause the electronic device to decrease the time of the timer based on the other biometric data and the other biometric data.

[0180] For example, the above one or more programs may include instructions that cause the electronic device to expire the timer based on the other biometric data and the other biometric data.

[0181] For example, the biometric data may include heart rate data for the user, pulse rate data for the user, and / or step count data for the user.

[0182] For example, the one or more programs may include instructions that cause the electronic device to receive, via the communication link, another signal indicating whether the wearable device has been worn by the user before the expiration of the timer, from the wearable device using the communication circuit. The one or more programs may include instructions that cause the electronic device to increase the time of the timer based on the other signal indicating that the wearable device has been worn by the user. The one or more programs may include instructions that cause the electronic device to decrease the time of the timer based on the other signal indicating that the wearable device has not been worn by the user.

[0183] For example, the above one or more programs may include instructions that cause the electronic device to decrease the time of the timer based on identifying the strength of another signal received from the wearable device that is smaller than a reference size before the expiration of the timer.

[0184] For example, the one or more programs may include instructions that cause the electronic device to receive another signal indicating that the user is in a sleep state from the wearable device via the communication link using the communication circuit. The one or more programs may include instructions that cause the electronic device to keep the timer running based on receiving the other signal before the expiration of the timer.

[0185] For example, the electronic device may further include a display. The one or more programs may include instructions that cause the electronic device to display the time of the timer through the display, based on driving the timer.

[0186] For example, the time of the above timer may be displayed in conjunction with information for the wearable device connected to the electronic device.

[0187] For example, the electronic device may further include a display. The one or more programs may include instructions that cause the electronic device to display information indicating that the user is authenticated with respect to the wearable device through the display, based on receiving the request before the expiration of the timer.

[0188] For example, the electronic device may further include a display. The one or more programs may include instructions that cause the electronic device to display information indicating that the user is not authenticated with respect to the wearable device through the display, based on receiving the request after the expiration of the timer.

[0189] For example, the above one or more programs may include instructions that cause the electronic device to transmit information about the user's credit card to the wearable device along with the signal via the communication link using the communication circuit, based on receiving the request before the expiration of the timer.

[0190] The electronic device described above may include at least one processor comprising a processing circuit, a communication circuit, and a memory comprising one or more storage media configured to store one or more programs configured to be executed individually or collectively by the at least one processor. The one or more programs may include instructions that cause the electronic device to establish a wireless connection with a wearable device through the communication circuit. The one or more programs may include instructions that cause the electronic device to authenticate a user with respect to the electronic device. The one or more programs may include instructions that cause the electronic device to transmit first information to the wearable device through the wireless connection, wherein the wearable device enables payment during a first time period. The one or more programs may include instructions that cause the electronic device to receive user input authenticating the user. The above one or more programs may include instructions that cause the electronic device to transmit second information to the wearable device via the wireless connection, thereby enabling the wearable device to make the payment during the second period, based at least in part on a decision that the user input is received during the first period.

[0191] For example, the above one or more programs may include instructions that cause the electronic device to transmit third information that reduces the second period to the wearable device via the wireless connection, based at least in part on a decision that another authentication corresponding to the user input fails.

[0192] For example, the above one or more programs may include instructions that cause the electronic device to transmit a fourth information to the wearable device via the wireless connection, thereby disabling the payment, based at least in part on a determination that the number of times authentication corresponding to the user input fails exceeds a predetermined number.

[0193] For example, the one or more programs may include instructions that cause the electronic device to receive the user's biometric data from the wearable device via the wireless connection. The one or more programs may include instructions that cause the electronic device to perform the transmission of the second information based on at least some of the biometric data.

[0194] For example, the one or more programs may include instructions that cause the electronic device to perform the transmission of the second information based at least partially on a decision in which the biometric data corresponds to the predetermined biometric data. The one or more programs may include instructions that cause the electronic device to transmit third information to the wearable device via the wireless connection, in which the wearable device reduces the second period, based at least partially on a decision in which the biometric data does not correspond to the predetermined biometric data.

[0195] For example, the one or more programs may include instructions that cause the electronic device to perform the transmission of the second information based at least partially on a decision in which the biometric data corresponds to the predetermined biometric data. The one or more programs may include instructions that cause the electronic device to transmit a fourth information to the wearable device via the wireless connection, in which the wearable device disables the payment, based at least partially on a decision in which the biometric data does not correspond to the predetermined biometric data.

[0196] The above method as described above may be performed within an electronic device including a communication circuit. The method may include an operation of authenticating a user with respect to the electronic device while a communication link between the electronic device and a wearable device is established using the communication circuit. The method may include an operation of running a timer for authenticating the user with respect to the wearable device based on authenticating the user with respect to the electronic device. The method may include an operation of receiving a request to authenticate the user with respect to the wearable device from the wearable device via the communication link using the communication circuit, based on receiving the request before the expiration of the timer. The method may include an operation of transmitting a signal to the wearable device via the communication link using the communication circuit, indicating that the user has been authenticated with respect to the wearable device, based on receiving the request before the expiration of the timer.

[0197] For example, the above method may include an operation of transmitting another signal to the wearable device via the communication link using the communication circuit, based on receiving the request after the expiration of the timer, indicating that the user is not authenticated with respect to the wearable device. The above method may include an operation of authenticating the user with respect to the electronic device while the timer is running. The above method may include an operation of resetting or increasing the time of the timer based on authenticating the user with respect to the electronic device before the expiration of the timer.

[0198] For example, the above method may include an operation to decrease the time of the timer based on identifying that the number of times the user has failed to authenticate the electronic device before the expiration of the timer exceeds a reference number.

[0199] For example, the above method may include an operation to expire the timer based on identifying that the number of times the user has failed to authenticate the electronic device before the expiration of the timer exceeds a reference number.

[0200] For example, the above method may include an operation to expire the timer based on identifying that the communication link has been released before the expiration of the timer.

[0201] For example, the above method may include the operation of transmitting a packet to the wearable device through the communication link using the communication circuit. The above method may include the operation of releasing the communication link based on identifying that an acknowledgment packet is not received from the wearable device within a reference time from the time the packet was transmitted.

[0202] For example, the above method may include the operation of receiving biometric data for the user from the wearable device via the communication link using the communication circuit. The above method may include the operation of comparing the biometric data with other biometric data for the user obtained with respect to the electronic device based on receiving the biometric data before the expiration of the timer. The above method may include the operation of increasing the time of the timer based on the biometric data corresponding to the other biometric data.

[0203] For example, the above method may include an operation to decrease the time of the timer based on the other biodata and the biodata different from the above.

[0204] For example, the above method may include an operation to expire the timer based on the other biometric data and the biometric data different from the above.

[0205] For example, the biometric data may include heart rate data for the user, pulse rate data for the user, and / or step count data for the user.

[0206] For example, the above method may include the operation of receiving, via the communication link, another signal from the wearable device using the communication circuit, indicating whether the wearable device has been worn by the user before the expiration of the timer. The above method may include the operation of increasing the time of the timer based on the other signal indicating that the wearable device has been worn by the user. The above method may include the operation of decreasing the time of the timer based on the other signal indicating that the wearable device has not been worn by the user.

[0207] For example, the above method may include an operation to decrease the time of the timer based on identifying the strength of another signal received from the wearable device, which is smaller than a reference size, before the expiration of the timer.

[0208] For example, the above method may include the operation of receiving another signal indicating that the user is in a sleep state from the wearable device via the communication link using the communication circuit. The above method may include the operation of maintaining the timer based on receiving the other signal before the expiration of the timer.

[0209] For example, the electronic device may further include a display. The method may include an operation of displaying the time of the timer through the display based on driving the timer.

[0210] For example, the time of the above timer may be displayed in conjunction with information for the wearable device connected to the electronic device.

[0211] For example, the electronic device may further include a display. The method may include an operation of displaying information indicating that the user is authenticated with respect to the wearable device through the display, based on receiving the request before the expiration of the timer.

[0212] For example, the electronic device may further include a display. The method may include an operation of displaying information through the display indicating that the user is not authenticated with respect to the wearable device, based on receiving the request after the expiration of the timer.

[0213] For example, the above method may include instructions that cause the electronic device to transmit information about the user's credit card to the wearable device along with the signal via the communication link using the communication circuit, based on receiving the request before the expiration of the timer.

[0214] The above-described method may be performed within an electronic device including a communication circuit. The method may include an operation of establishing a wireless connection with a wearable device through the communication circuit. The method may include an operation of authenticating a user with respect to the electronic device. The method may include an operation of driving a timer based at least partially on the authentication. The method may include an operation of transmitting first information to the wearable device via the wireless connection, wherein the wearable device enables payment during a first time period. The method may include an operation of receiving user input that authenticates the user. The method may include an operation of transmitting second information to the wearable device via the wireless connection, wherein the wearable device enables payment during a second period, wherein the wearable device enables payment during a second period, wherein the user input is received during the first period, at least partially based on the determination.

[0215] For example, the above method may include the operation of transmitting third information to the wearable device via the wireless connection, wherein the wearable device reduces the second period, based at least in part on a decision that another authentication corresponding to the user input fails.

[0216] For example, the above method may include an operation of transmitting a fourth information to the wearable device via the wireless connection, wherein the wearable device disables the payment, based at least in part on a determination that the number of times authentication corresponding to the user input fails exceeds a predetermined number.

[0217] For example, the above method may include an operation of receiving the user's biometric data from the wearable device through the wireless connection. The above method may include an operation of transmitting the second information based on at least a portion of the biometric data.

[0218] For example, the above method may include an operation of performing the transmission of the second information based at least partially on a decision in which the biometric data corresponds to the predetermined biometric data. The above method may include an operation of transmitting third information to the wearable device via the wireless connection, in which the wearable device reduces the second period, based at least partially on a decision in which the biometric data does not correspond to the predetermined biometric data.

[0219] For example, the above method may include an operation of performing the transmission of the second information based at least partially on a decision in which the biometric data corresponds to the predetermined biometric data. The above method may include an operation of transmitting a fourth information to the wearable device via the wireless connection in which the wearable device disables the payment, based at least partially on a decision in which the biometric data does not correspond to the predetermined biometric data.

[0220] The above-described non-transient computer-readable storage medium may store one or more programs. The one or more programs may include instructions that cause the electronic device to authenticate a user with respect to the electronic device while a communication link between the electronic device and a wearable device is established using the communication circuit when executed by the electronic device having a communication circuit. The one or more programs may include instructions that cause the electronic device to run a timer for authenticating the user with respect to the wearable device based on authenticating the user with respect to the electronic device when executed by the electronic device. The one or more programs may include instructions that cause the electronic device to receive a request to authenticate the user with respect to the wearable device from the wearable device via the communication link using the communication circuit when executed by the electronic device. The above one or more programs may include instructions that cause the electronic device to transmit a signal indicating that the user is authenticated with respect to the wearable device via the communication link using the communication circuit, based on receiving the request before the expiration of the timer when executed by the electronic device.

[0221] For example, the above one or more programs may include instructions that cause the electronic device to transmit another signal indicating that the user is not authenticated with respect to the wearable device via the communication link using the communication circuit, based on receiving the request after the expiration of the timer when executed by the electronic device.

[0222] For example, the one or more programs may include instructions that cause the electronic device to authenticate the user with respect to the electronic device while the timer is running when executed by the electronic device. The one or more programs may include instructions that cause the electronic device to reset or increase the time of the timer based on authenticating the user with respect to the electronic device before the expiration of the timer when executed by the electronic device.

[0223] For example, the above one or more programs may include instructions that cause the electronic device to decrease the time of the timer based on identifying that the number of times the user has failed to authenticate the electronic device before the expiration of the timer exceeds a reference number when executed by the electronic device.

[0224] For example, the above one or more programs may include instructions that cause the electronic device to expire the timer based on identifying that the number of times the user has failed to authenticate the electronic device before the expiration of the timer exceeds a reference number when executed by the electronic device.

[0225] For example, the one or more programs may include instructions that cause the electronic device to expire the timer based on identifying that the communication link was released before the expiration of the timer when executed by the electronic device.

[0226] For example, the one or more programs may include instructions that cause the electronic device to transmit a packet to the wearable device via the communication link using the communication circuit when executed by the electronic device. The one or more programs may include instructions that cause the electronic device to release the communication link based on identifying that an acknowledgment packet is not received from the wearable device within a reference time from the time the packet is transmitted when executed by the electronic device.

[0227] For example, the one or more programs may include instructions that cause the electronic device to receive biometric data for the user from the wearable device via the communication link using the communication circuit when executed by the electronic device. The one or more programs may include instructions that cause the electronic device to compare the biometric data with other biometric data for the user obtained with respect to the electronic device based on receiving the biometric data before the expiration of the timer when executed by the electronic device. The one or more programs may include instructions that cause the electronic device to increase the time of the timer based on the biometric data corresponding to the other biometric data when executed by the electronic device.

[0228] For example, the above one or more programs may include instructions that cause the electronic device to decrease the time of the timer based on the other biometric data and the other biometric data when executed by the electronic device.

[0229] For example, the above one or more programs may include instructions that cause the electronic device to expire the timer based on the other biometric data and the biometric data different from the other biometric data when executed by the electronic device.

[0230] For example, the biometric data may include heart rate data for the user, pulse rate data for the user, and / or step count data for the user.

[0231] For example, the one or more programs may include instructions that cause the electronic device to receive, when executed by the electronic device, another signal from the wearable device via the communication link using the communication circuit, indicating whether the wearable device has been worn by the user before the expiration of the timer. The one or more programs may include instructions that cause the electronic device to increase the time of the timer based on the other signal indicating that the wearable device has been worn by the user when executed by the electronic device. The one or more programs may include instructions that cause the electronic device to decrease the time of the timer based on the other signal indicating that the wearable device has not been worn by the user when executed by the electronic device.

[0232] For example, the above one or more programs may include instructions that cause the electronic device to decrease the time of the timer based on identifying the strength of another signal received from the wearable device that is smaller than a reference size before the expiration of the timer when executed by the electronic device.

[0233] For example, the one or more programs may include instructions that cause the electronic device to receive another signal indicating that the user is in a sleep state from the wearable device via the communication link using the communication circuit when executed by the electronic device. The one or more programs may include instructions that cause the electronic device to maintain the timer based on receiving the other signal before the expiration of the timer when executed by the electronic device.

[0234] For example, the electronic device may further include a display. The one or more programs may include instructions that cause the electronic device to display the time of the timer through the display, based on driving the timer when executed by the electronic device.

[0235] For example, the time of the above timer may be displayed in conjunction with information for the wearable device connected to the electronic device.

[0236] For example, the electronic device may further include a display. The one or more programs may include instructions that cause the electronic device to display information indicating that the user is authenticated with respect to the wearable device through the display, based on receiving the request before the expiration of the timer when executed by the electronic device.

[0237] For example, the electronic device may further include a display. The one or more programs may include instructions that cause the electronic device to display information indicating that the user is not authenticated with respect to the wearable device through the display, based on receiving the request after the expiration of the timer when executed by the electronic device.

[0238] For example, the above one or more programs may include instructions that cause the electronic device to transmit information about the user's credit card to the wearable device along with the signal via the communication link using the communication circuit, based on receiving the request before the expiration of the timer when executed by the electronic device.

[0239] The above-described non-transient computer-readable storage medium may store one or more programs. The one or more programs may include instructions that cause the electronic device to establish a wireless connection with a wearable device through the communication circuit when executed by the electronic device having a communication circuit. The one or more programs may include instructions that cause the electronic device to authenticate a user with respect to the electronic device when executed by the electronic device. The one or more programs may include instructions that cause the electronic device to drive a timer based at least partially on the authentication when executed by the electronic device. The one or more programs may include instructions that cause the electronic device to transmit first information to the wearable device through the wireless connection when executed by the electronic device, wherein the wearable device enables payment during a first time period. The above one or more programs may include instructions that cause the electronic device to receive user input that authenticates the user when executed by the electronic device. The above one or more programs may include instructions that cause the electronic device to transmit second information to the wearable device via the wireless connection, which enables the wearable device to make a payment during a second period, based at least in part on a determination that the user input is received during the first period when executed by the electronic device.

[0240] For example, the above one or more programs may include instructions that cause the electronic device to transmit third information that reduces the second period to the wearable device via the wireless connection, based at least in part on a decision that another authentication corresponding to the user input fails when executed by the electronic device.

[0241] For example, the above one or more programs may include instructions that cause the electronic device to transmit a fourth information to the wearable device via the wireless connection, wherein the wearable device disables the payment, based at least in part on a determination that the number of times authentication corresponding to the user input fails when executed by the electronic device exceeds a predetermined number.

[0242] For example, the one or more programs may include instructions that cause the electronic device to receive the user's biometric data from the wearable device via the wireless connection when executed by the electronic device. The one or more programs may include instructions that cause the electronic device to perform the transmission of the second information based at least partially on the biometric data when executed by the electronic device.

[0243] For example, the above one or more programs may include instructions that cause the electronic device to perform the transmission of the second information based at least partially on a decision in which the biometric data corresponds to the predetermined biometric data when executed by the electronic device. The above one or more programs may include instructions that cause the electronic device to transmit third information to the wearable device via the wireless connection, in which the wearable device reduces the second period, based at least partially on a decision in which the biometric data does not correspond to the predetermined biometric data when executed by the electronic device.

[0244] For example, the one or more programs may include instructions that cause the electronic device to perform the transmission of the second information, based at least in part on a decision in which the biometric data corresponds to the predetermined biometric data when executed by the electronic device. The one or more programs may include instructions that cause the electronic device to transmit a fourth information to the wearable device via the wireless connection, in which the wearable device disables the payment, based at least in part on a decision in which the biometric data does not correspond to the predetermined biometric data when executed by the electronic device.

[0245] The effects obtainable from the present disclosure are not limited to those mentioned above, and other unmentioned effects will be clearly understood by those skilled in the art to which the present disclosure belongs.

Claims

1. In an electronic device, At least one processor including a processing circuit; Communication circuit; and Memory comprising one or more programs configured to be executed individually or collectively by at least one processor, and including one or more storage media, The above one or more programs are: While a communication link between the electronic device and the wearable device is established using the above communication circuit, the user is authenticated with respect to the electronic device; Based on authenticating the user with respect to the electronic device, a timer for authenticating the user with respect to the wearable device is run; Using the above communication circuit, receiving a request from the wearable device to authenticate the user with respect to the wearable device via the above communication link; and Based on receiving the request before the expiration of the timer, using the communication circuit, transmit a signal to the wearable device via the communication link indicating that the user is authenticated with respect to the wearable device. Instructions including those that cause the above electronic device Electronic device.

2. In Claim 1, The above one or more programs are: Based on receiving the request after the expiration of the above timer, using the communication circuit, to transmit another signal to the wearable device via the communication link indicating that the user is not authenticated with respect to the wearable device, Instructions including those that cause the above electronic device Electronic device.

3. In Claim 1, The above one or more programs are: While the above timer is running, authenticate the user with respect to the electronic device; and Based on authenticating the user with respect to the electronic device before the expiration of the above timer, to reset or increase the time of the above timer, Instructions including those that cause the above electronic device Electronic device.

4. In Claim 1, The above one or more programs are: Based on identifying that the number of times the user has failed to authenticate the electronic device before the expiration of the timer exceeds a reference number, the time of the timer is to be reduced. Instructions including those that cause the above electronic device Electronic device.

5. In Claim 1, The above one or more programs are: To expire the timer based on identifying that the number of times the user has failed to authenticate the electronic device before the expiration of the timer exceeds a reference number, Instructions including those that cause the above electronic device Electronic device.

6. In Claim 1, The above one or more programs are: Based on identifying that the communication link was released before the expiration of the above timer, to expire the timer, Instructions including those that cause the above electronic device Electronic device.

7. In Claim 6, The above one or more programs are: Using the above communication circuit, transmit a packet to the wearable device through the above communication link; and Based on identifying that an acknowledgment packet is not received from the wearable device within a reference time from the time the above packet is transmitted, to release the communication link, Instructions including those that cause the above electronic device Electronic device.

8. In Claim 1, The above one or more programs are: Using the above communication circuit, receiving biometric data for the user from the wearable device through the above communication link; Based on receiving the biometric data before the expiration of the above timer, comparing the biometric data with other biometric data for the user obtained with respect to the electronic device; and Based on the biodata corresponding to the other biodata mentioned above, to increase the time of the timer, Instructions including those that cause the above electronic device Electronic device.

9. In Claim 8, The above one or more programs are: Based on the above other biometric data and the above biometric data different from the above, to decrease the time of the above timer, Instructions including those that cause the above electronic device Electronic device.

10. In claim 8, The above one or more programs are: Based on the above other biometric data and the above biometric data different from the above, to expire the timer, Instructions including those that cause the above electronic device Electronic device.

11. In Claim 8, The above biometric data is, including heart rate data for the user, pulse rate data for the user, and / or step count data for the user, Electronic device.

12. In Claim 1, The above one or more programs are: Using the above communication circuit, receiving another signal from the wearable device via the communication link indicating whether the wearable device has been worn by the user before the expiration of the timer; Based on the other signal indicating that the wearable device is worn by the user, the time of the timer is increased; and Based on the other signal indicating that the wearable device is not worn by the user, the time of the timer is to be decreased. Instructions including those that cause the above electronic device Electronic device.

13. In Claim 1, The above one or more programs are: Based on identifying the strength of another signal received from the wearable device that is smaller than the reference size before the expiration of the timer, to decrease the time of the timer. Instructions including those that cause the above electronic device Electronic device.

14. In Claim 1, The above one or more programs are: Based on receiving the request before the expiration of the timer, using the communication circuit, to transmit information about the user's credit card to the wearable device via the communication link along with the signal, Instructions including those that cause the above electronic device Electronic device.

15. In electronic devices, At least one processor including a processing circuit; Touchscreen display; Communication circuit; and Memory comprising one or more programs configured to be executed individually or collectively by at least one processor, and including one or more storage media, The above one or more programs are: Establish a wireless connection with a wearable device through the above communication circuit; Authenticate the user regarding the above electronic device; Driving a timer based on at least part of the above authentication; Through the above wireless connection, the wearable device transmits first information to the wearable device that enables payment during a first time period; Receiving user input that authenticates the above user; and Based at least in part on the determination that the above user input is received during the first period, the wearable device transmits, via the wireless connection, second information to which the wearable device enables the payment during the second period. Instructions including those that cause the above electronic device Electronic device.

Images