Method and apparatus for electronic payment authentication service using accessory electronic device

Abstract

An electronic device according to one embodiment may be configured to: generate a first authentication token through a device manager associated with an accessory electronic device on the basis of detecting that the accessory electronic device is being worn during pairing with the accessory electronic device; transmit the generated first authentication token to an electronic payment application stored in a memory; if an electronic payment service request is received from the electronic payment application, request an authentication token from the accessory electronic device and receive a second authentication token from the accessory electronic device or the device manager; if the first authentication token stored in the electronic payment application is identical to the second authentication token transmitted from the accessory electronic device or the device manager, request user authentication for electronic payment to the accessory electronic device; and determine whether the user authentication is successful on the basis of user authentication information received from the accessory electronic device.

Description

Method and device for electronic payment authentication service using an accessory electronic device

[0001] The present invention relates to a method and device for an electronic payment authentication service using an accessory electronic device.

[0002] As internet penetration expands, interest in technologies that enable users to make payments using their electronic devices, both offline and online, is growing. For example, electronic devices support electronic payment services / functions (e.g., simple payment) that enable payments to be made upon completion of authentication (e.g., password entry) using the electronic device.

[0003] Electronic payment services are available not only online but also at offline stores, so many users are using them.

[0004] These electronic payment services require an authentication process before they can perform payment functions. Authentication methods include, for example, PIN authentication, which involves entering a password on a keypad, or biometric authentication, which utilizes biometric information like fingerprints or irises.

[0005] The above information may be provided as background art to aid in understanding the present disclosure. No claim or determination is made as to whether any of the above-described matters constitute prior art related to the present disclosure.

[0006] The authentication process for electronic payment services may require the user to interact with their electronic device (e.g., using the device's screen or performing an authentication gesture). However, this can be inconvenient in situations where it's difficult for the user to interact with the electronic device (e.g., when the device is stored in a bag or being used for another purpose).

[0007] Accordingly, technologies are being developed to support electronic payment services using other devices that communicate with electronic devices (e.g., accessory electronic devices, wearable electronic devices).

[0008] Various embodiments provide a payment authentication service method and device that enable a user to use an electronic payment service more conveniently by replacing the user authentication process with an accessory electronic device that is linked to the electronic device in situations where it is difficult for the user to operate the electronic device during an electronic payment service.

[0009] The technical tasks to be achieved in this document are not limited to the technical tasks mentioned above, and other technical tasks not mentioned will be clearly understood by those with ordinary skill in the technical field to which this document pertains from the description below.

[0010] However, the problem to be solved in this disclosure is not limited to the problem mentioned above, and may be expanded in various ways without departing from the spirit and scope of this disclosure.

[0011] An electronic device according to one embodiment may include a communication module. The electronic device according to one embodiment may include a memory storing executable instructions and a processor accessing the memory to execute the instructions. The instructions according to one embodiment may cause the electronic device to generate a first authentication token through an accessory electronic device manager based on detection of wearing of the accessory electronic device when paired with the accessory electronic device. The instructions according to one embodiment may cause the electronic device to transmit the generated first authentication token to an electronic payment application stored in the memory. The instructions according to one embodiment may cause the electronic device to request an authentication token from the accessory electronic device when an electronic payment service request is received from the electronic payment application and to receive a second authentication token from the accessory electronic device or the accessory electronic device manager. The instructions according to one embodiment may cause the electronic device to request user authentication for electronic payment from the accessory electronic device if the first authentication token stored in the electronic payment application is the same as the second authentication token transmitted from the accessory electronic device or the accessory electronic device manager. The instructions according to one embodiment may cause the electronic device to determine whether user authentication is successful based on user authentication information received from the accessory electronic device.

[0012] An accessory electronic device according to one embodiment may include at least one sensor. An accessory electronic device according to one embodiment may include a communication module. An accessory electronic device according to one embodiment may include a memory storing executable instructions and a processor accessing the memory to execute the instructions. Instructions according to one embodiment may cause the accessory electronic device to generate a first authentication token based on detection of wearing of the accessory electronic device when pairing with the electronic device through the communication module, store the generated first authentication token in the memory, and simultaneously transmit the first authentication token to the electronic device through the communication module. Instructions according to one embodiment may cause the accessory electronic device to, when receiving a second authentication token for an electronic payment request from the electronic device, notify user authentication request information for the electronic payment request based on the first authentication token stored in the memory and the second authentication token transmitted from the electronic device being identical. Instructions according to one embodiment may cause the accessory electronic device to determine whether user authentication is successful based on received user authentication information detected through the at least one sensor. Instructions according to one embodiment may cause the accessory electronic device to transmit user authentication success information for an electronic payment request to the electronic device through the communication module when the user authentication is successful, or to transmit user authentication failure information to the electronic device through the communication module when the user authentication fails.

[0013] According to one embodiment, a method for providing an electronic payment service using an accessory electronic device may include an operation in which, when pairing with an accessory electronic device through a communication module, the electronic device generates a first authentication token through a device manager associated with the accessory electronic device based on detection of wearing of the accessory electronic device. According to one embodiment, the method may include an operation in which the generated first authentication token is transmitted to an electronic payment application. According to one embodiment, the method may include an operation in which, when an electronic payment service request is received from the electronic payment application, the method may include an operation in which the accessory electronic device is requested to provide an authentication token and a second authentication token is received from the accessory electronic device or the device manager. According to one embodiment, the method may include an operation in which, when the first authentication token stored in the electronic payment application and the second authentication token transmitted from the accessory electronic device or the device manager are identical, the method may include an operation in which the accessory electronic device is requested to provide user authentication for electronic payment through the communication module. According to one embodiment, the method may include an operation in which the success or failure of user authentication is determined based on user authentication information received from the accessory electronic device.

[0014] An electronic device according to one embodiment may include a computer-readable recording medium having recorded thereon a program for implementing an electronic payment authentication service method using an accessory electronic device.

[0015] An electronic device and method according to various embodiments can provide a system that enables electronic payment without operating an electronic device by completing user authentication through an accessory electronic device through comparison of an authentication token through communication with an accessory electronic device when using an electronic payment service.

[0016] Electronic devices and methods according to various embodiments can implement success / failure of user authentication of electronic payment depending on whether an accessory electronic device is attached / detached.

[0017] Electronic devices and methods according to various embodiments can prevent electronic payments from being misused when the accessory electronic device is lost, since the accessory electronic device does not have actual payment information.

[0018] Electronic devices and methods according to various embodiments can perform a simple payment service using an accessory electronic device when making offline electronic payments.

[0019] The effects that can be obtained from the present disclosure are not limited to the effects mentioned above, and other effects that are not mentioned can be clearly understood by a person having ordinary skill in the art to which the present disclosure belongs from the description below.

[0020] In connection with the description of the drawings, the same or similar reference numerals may be used for the same or similar components.

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

[0022] FIG. 2 illustrates a configuration of an accessory electronic device according to various embodiments of the present disclosure.

[0023] FIG. 3 illustrates an example of an authentication means setting screen related to an electronic payment service of an electronic device according to one embodiment.

[0024] FIG. 4 is a diagram illustrating an online payment system using an electronic device and an accessory electronic device according to one embodiment.

[0025] FIGS. 5A and 5B illustrate a method for setting an accessory electronic device as an authentication means for an electronic payment service of an electronic device according to one embodiment.

[0026] FIGS. 6A and 6B illustrate an electronic payment authentication service method of an electronic device using an accessory electronic device according to one embodiment.

[0027] FIGS. 7A and 7B illustrate an electronic payment authentication service method of an electronic device using an accessory electronic device according to one embodiment.

[0028] FIG. 8 illustrates an example of authentication means setting screens related to an electronic payment service of an electronic device according to one embodiment.

[0029] FIG. 9 is a diagram illustrating an offline payment system using an electronic device and an accessory electronic device according to one embodiment.

[0030] FIG. 10 illustrates a method for setting up an accessory electronic device as an authentication and payment means for an electronic payment service of an electronic device according to one embodiment.

[0031] FIG. 11 illustrates an offline electronic payment service method of an electronic device using an accessory electronic device according to one embodiment.

[0032] FIG. 12 illustrates an offline electronic payment service method of an electronic device using an accessory electronic device according to one embodiment.

[0033] FIG. 13 illustrates an example of an electronic payment service method of an electronic device using an accessory electronic device according to one embodiment.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0058] An electronic device (101) according to one embodiment may include a communication module (190). An electronic device (101) according to one embodiment may include a memory (130) that stores executable instructions and a processor (120) that accesses the memory and executes the instructions. The instructions according to one embodiment may cause the electronic device (101) to generate a first authentication token through a device manager associated with the accessory electronic device (201) based on detection of wearing of the accessory electronic device (201) when pairing with the accessory electronic device (201). The instructions according to one embodiment may cause the electronic device (101) to transmit the generated first authentication token to an electronic payment application stored in the memory (130). The instructions according to one embodiment may cause the electronic device (101) to request an authentication token from the accessory electronic device (201) and receive a second authentication token from the accessory electronic device (201) or the device manager when an electronic payment service request is received from the electronic payment application. The instructions according to one embodiment may cause the electronic device (101) to request user authentication for electronic payment from the accessory electronic device (201) when the first authentication token stored in the electronic payment application and the second authentication token transmitted from the accessory electronic device (201) or the device manager are the same. The instructions according to one embodiment may cause the electronic device (101) to determine whether user authentication is successful based on user authentication information received from the accessory electronic device (201).

[0059] According to one embodiment, the memory (130) may further include instructions for causing the electronic device (101) to generate a third authentication token based on the detection of detachment of the accessory electronic device (2010) using the device manager, and to update the first authentication token with the third authentication token.

[0060] According to one embodiment, the memory (130) may further include an instruction that causes the electronic device (101) to display authentication failure information on a display through the electronic payment application when the first authentication token stored in the electronic payment application and the second authentication token transmitted from the device manager are different.

[0061] According to one embodiment, the memory (130) may further include instructions for causing the electronic device (101) to stop user authentication requested from the accessory electronic device (201) and request user authentication using the electronic payment application when the first authentication token stored in the electronic payment application and the second authentication token transmitted from the device manager are different.

[0062] According to one embodiment, the first authentication token and the second authentication token may include at least one of token data, device identification information, and personal recognition information.

[0063] According to one embodiment, the user authentication may be characterized by one of biometric information and a password.

[0064] According to one embodiment, when the device manager is programmed to the memory of the electronic device, the memory (130) may further include instructions for causing the electronic device (101) to transmit the generated first authentication token to the electronic payment application and the accessory electronic device, and to compare the first authentication token with the second authentication token through the electronic payment application or the device manager to determine whether they are the same.

[0065] According to one embodiment, when the device manager is programmed into the memory (130) of the electronic device (101), the memory (130) may further include instructions for causing the electronic device (101) to receive the first authentication token or the third authentication token generated through the device manager from the accessory electronic device (201) through the communication module (190), and to transmit the first authentication token or the third authentication token transmitted from the accessory electronic device (201) through the communication module (190) to the electronic payment application.

[0066] According to one embodiment, the memory (130) may further include instructions for allowing the electronic device (101) to proceed with the electronic payment service when the user authentication information transmitted from the accessory electronic device (201) is identical to the user authentication information transmitted to the electronic device (101).

[0067] FIG. 2 illustrates a configuration of an accessory electronic device according to various embodiments of the present disclosure.

[0068] Referring to FIG. 2, according to one embodiment, an accessory electronic device (201) that is connected to an electronic device (101) supports biometric information sensing functions, touch functions, and wireless communication functions, and may refer to an electronic device that can be worn on a user's body. The accessory electronic device (201) may also be referred to as a wearable electronic device.

[0069] The accessory electronic device (201) illustrated in FIG. 2 is illustrated as a ring type (e.g., a smart ring) worn by a user on a finger, but is not limited thereto, and may be implemented as another type of accessory electronic device, such as a watch type (e.g., a smart watch) or a band type (e.g., a smart band).

[0070] An accessory electronic device (201) according to one embodiment may include a first annular housing (2001) (e.g., an outer ring housing, a first ring housing, or a first housing portion) and a second annular housing (2002) (e.g., an inner ring housing, a second ring housing, or a second housing portion) coupled to the first housing (2001) and including an opening (2003). The opening (2003) may be formed to a size such that a user's finger can be inserted therein. For example, the first housing (2001) may be formed of a material that is resistant to external impact or scratches, such as a metal material, ceramic, or stainless steel. A separate fixing or coating process may be performed on the first housing (2001) to implement color. For example, the second housing (2002) may be formed of the same material as the first housing (2001), or may be formed of a material such as a molding material for sensing, plastic, or glass. The second housing (2002) may also be formed of at least a portion of a metal material for biometric measurement.

[0071] An accessory electronic device (201) according to one embodiment may include a processor (210), a memory (220), an antenna (225), a communication module (235), a battery (240), a charging interface (245), at least one biometric sensor (250), a touch sensor (260), an inertial sensor (270), a temperature sensor (280), and / or a power management integrated circuit (PMIC) (290) disposed in a space between a first housing (2001) and a second housing (2002). Some of the components may be disposed on a substrate (295) (e.g., FPCB, flexible printed circuit board) having flexibility to correspond to the curvature of the accessory electronic device (201).

[0072] According to some embodiments, the accessory electronic device (201) may further include other components (e.g., a display, an ultrasonic sensor, an audio output device) in addition to the components illustrated.

[0073] A communication module (235) according to one embodiment may include various hardware and / or software configurations for supporting wireless communication with an external electronic device (hereinafter, electronic device (101) of FIG. 1). The wearable electronic device (201) may transmit and receive various data or control commands with the electronic device (101) via the communication module (235) via wired / wireless communication. In one embodiment, the communication module (235) may support short-range wireless communication. For example, short-range wireless communication may include, but is not limited to, at least one of Bluetooth, BLE (Bluetooth Low Energy), ZigBee, ANT+, Wi-Fi, Cellular (LTE, 5G, 6G, NB-IoT), NFC (near field communication), RFID (radio frequency identification), UWB (ultra wide band), GNSS (global navigation satellite system) and / or MST (magnetic secure transmission). According to some embodiments, the communication module (235) may be implemented in an integrated form with the processor (210).

[0074] According to one embodiment, the antenna (225) may be connected to the communication module (235) via the substrate (295). The wearable electronic device (201) may transmit or receive communication signals / data to the outside via the antenna (225). The antenna (225) may include a single or multiple antennas. In some embodiments, a part of the first housing (2001) (e.g., a metal member) may be designed to be used as the antenna (225).

[0075] According to one embodiment, the battery (240) may be formed in a curved shape to have a curvature corresponding to the curvature of the space between the first housing (2001) and the second housing (2002). For example, the battery (240) may be configured such that multiple battery packs are separately arranged. The battery (240) may be connected to a charging interface (245).

[0076] According to one embodiment, a charging interface (245) may be electrically connected to a PMIC (290) mounted on a substrate (295) via the substrate (295). For example, the charging interface (245) may support wired charging (terminal) or wireless charging (WPC, NFC) methods for charging.

[0077] At least one biometric sensor (250) according to one embodiment can obtain various biometric information of a user using an optical signal. For example, the biometric sensor (250) may be a photoplethysmogram (PPG) sensor or an optical sensor that can obtain various biometric information such as heart rate and blood circulation by measuring a plethysmogram according to an optical signal, but is not limited thereto. The biometric sensor (250) can obtain biometric information such as heart rate (HR), blood pressure, saturation of percutaneous oxygen (SpO2), galvanic skin response (GSR), electrocardiography (ECG), blood flow velocity, and / or bioelectrical impedance, but is not limited thereto.

[0078] In some embodiments, the biometric sensor (250) may include a fingerprint sensor.

[0079] A biometric sensor (250) according to one embodiment may include a sensor controller (250a), a plurality of emitters (250b) for outputting optical signals, and a plurality of receivers (250c) for receiving optical signals. The emitters (250b) may include light-emitting elements that emit light of various wavelengths or colors (e.g., green, red) to measure a biometric signal. For example, the emitters (250b) may be formed of at least one of a light-emitting diode (LED), a semiconductor laser diode (LD), an infrared (IR) diode, and a VCSEL. For example, the receivers (250c) may be formed of a photodiode (PD) or a complementary metal-oxide-semiconductor (CMOS) camera. The receivers (250c) may convert a received optical signal through an analog-to-digital converter (ADC) and store the converted signal in a processor (210) or a memory (220). The sensor controller (250a) can control the light emitting unit (250b) and the light receiving unit (250c).

[0080] A touch sensor (260) according to one embodiment can detect a touch signal of a user touching a wearable electronic device (201). The touch sensor (260) can be formed using at least one of a pressure type, an electrostatic type, an optical type, or an ultrasonic type, for example.

[0081] In some embodiments, the touch sensor (260) may be omitted.

[0082] An inertial sensor (270) according to one embodiment can obtain movement information of a wearable electronic device (201). For example, the inertial sensor (270) can detect motion, gesture, impact, posture, and / or activity (e.g., sedentary, moving, sports). For example, the inertial sensor (270) may be formed as a 3-axis accelerometer, but is not limited thereto, and may also be formed as a 6-axis sensor including an accelerometer and a gyroscope.

[0083] According to one embodiment, a temperature sensor (280) can measure the body temperature of a user or the temperature of a component (e.g., an electronic component) included in a wearable electronic device (201). The temperature sensor (280) can be formed in a contact or non-contact manner and may vary depending on the design. For example, the wearable electronic device (201) can record temperature information recorded through the temperature sensor (280) in memory or, under processor control, use it to measure the body temperature of the user, estimate skin temperature, or estimate situational awareness.

[0084] According to one embodiment, a PMIC (290) can manage power delivered from a battery (240) to each component of a wearable electronic device (201).

[0085] The memory (220) according to one embodiment may store various instructions that may be performed by the processor (210). Such instructions may include arithmetic and logical operations, data movement, or control commands such as input / output that may be processed by the processor (210).

[0086] According to one embodiment, the processor (210) is a configuration capable of performing calculations or data processing related to control and / or communication of each component of the accessory electronic device (200), and may be formed of one or more processors. The calculation and data processing functions that the processor (210) may implement on the accessory electronic device (201) are not limited, but in this document, it may process various operations to support electronic payment services related to user authentication required for electronic payment services in conjunction with the electronic device (101).

[0087] An accessory electronic device (201) according to one embodiment may include at least one sensor (250, 270, 280). An accessory electronic device (201) according to one embodiment may include a communication module (230). An accessory electronic device (201) according to one embodiment may include a memory (220) that stores executable instructions and a processor (210) that accesses the memory (220) and executes the instructions. The instructions according to one embodiment may cause the accessory electronic device (201) to generate a first authentication token based on detection of wearing of the accessory electronic device (201) when pairing with the electronic device (101) through the communication module, store the generated first authentication token in the memory (220), and simultaneously transmit the generated first authentication token to the electronic device (101) through the communication module (230). Instructions according to one embodiment may cause the accessory electronic device (201) to notify user authentication request information for the electronic payment request based on the first authentication token stored in the memory (220) being the same as the second authentication token transmitted from the electronic device (101), when a second authentication token for the electronic payment request is received from the electronic device (101). Instructions according to one embodiment may cause the accessory electronic device (201) to determine whether user authentication is successful based on received user authentication information detected through the at least one sensor. Instructions according to one embodiment may cause the accessory electronic device (201) to transmit user authentication success information for the electronic payment request to the electronic device (101) through the communication module (230) when the user authentication is successful, or to transmit user authentication failure information to the electronic device (101) through the communication module (230) when the user authentication fails.

[0088] FIG. 3 illustrates an example of an authentication means setting screen related to an electronic payment service of an electronic device according to one embodiment.

[0089] Referring to FIG. 3, an electronic device (101) according to one embodiment may support a function of pre-setting (or initially registering) an accessory electronic device (201) to be used as a user authentication means for an electronic payment service.

[0090] According to one embodiment, the electronic device (101) may display a setting user interface (UI) screen (310) related to an authentication means of an electronic payment service on a display (e.g., a display module (160) of FIG. 1) as illustrated. The electronic device (101) may provide a function of using an external electronic device (e.g., an accessory electronic device (201) of FIG. 2) as an authentication means in place of the electronic device (101) when providing an electronic payment service. The setting UI screen (310) may be used to set or de-set a function of authenticating a user using the accessory electronic device (201) as an authentication means. For example, the setting UI screen (310) may include an item (320) for selecting the accessory electronic device (201) as an authentication means, and a toggle item (325) for setting / de-setting. In the example of FIG. 3, items such as a face or a password are included as authentication means, but in some cases, settings for other authentication means such as a fingerprint, a pattern, or an iris may also be included.

[0091] According to one embodiment, when the accessory electronic device (201) is set as an authentication means for an electronic payment service through the setting UI screen (310) illustrated in FIG. 3, the electronic device (101) can perform the authentication registration and token exchange procedures of FIGS. 5a / 5b whenever the accessory electronic device (201) is paired (e.g., via Bluetooth connection). Hereinafter, the authentication registration and token exchange procedures will be described with reference to FIGS. 5a / 5b.

[0092] Referring to FIG. 4, an online payment system (400) using an accessory electronic device (201) as an authentication means according to one embodiment may include an electronic device (101), an accessory electronic device (201), an app server (e.g., an application server) (410), a payment gateway (e.g., a payment gateway) (420), and / or a store server (e.g., an online store) (430).

[0093] The electronic device (101) may include an electronic payment application (or payment app, hereinafter, electronic payment app) (401) that supports electronic payment services, and / or a device manager (402) that controls / manages an accessory electronic device (201).

[0094] In some embodiments, the device manager (402) may operate in integration with an electronic payment app (401).

[0095] For example, a user of an electronic device (101) can access a store server (430) via a store app to purchase items online. After selecting an item to purchase via the store app, the user of the electronic device (101) can select an electronic payment service (e.g., simple payment, pay payment) as a means of payment for the purchase.

[0096] For example, the store server (430) may transmit a payment request including information about the electronic device (101) requesting payment and payment information to a payment gateway (e.g., payment gateway) (420) (or payment server) (e.g., card company server). The payment gateway (e.g., payment gateway) (420) may transmit the payment request to an app server (410) (e.g., Samsung Pay server, Naver Pay server) that provides an electronic payment service.

[0097] The app server (410) can transmit a payment request to the electronic payment app (401) of the electronic device (101) to confirm payment for the purchase with the electronic device (101).

[0098] The electronic payment app (401) of the electronic device (101) can display payment card and amount information on the display. For example, the electronic device (101) may be configured with an accessory electronic device (201) as a user authentication means for an electronic payment service.

[0099] An electronic payment app (401) of an electronic device (101) may request user authentication for electronic payment from a device manager (402) for user authentication. The device manager (402) may request user authentication from an accessory electronic device (201) paired with the electronic device.

[0100] The accessory electronic device (201) can perform a set user authentication procedure (e.g., obtaining fingerprint information). The accessory electronic device (201) can transmit user authentication information to the electronic device (101).

[0101] If user authentication is successful based on user authentication information transmitted from the accessory electronic device (201), the device manager (402) of the electronic device (101) can transmit authentication completion information to the electronic payment app (402) of the electronic device (101).

[0102] The electronic payment app (401) of the electronic device (101) can transmit payment completion information based on successful user authentication to the app server (410). The app server (410) can transmit the payment completion information to the pay gateway (420), and the pay gateway (420) can transmit the payment completion information to the store server (430) to complete payment for an online purchase.

[0103] FIGS. 5A and 5B illustrate a method for setting an accessory electronic device as an authentication means for an electronic payment service of an electronic device according to one embodiment. Each operation of FIGS. 5A and 5B is performed through the interaction of a processor and a memory, and may be operated through software modules (e.g., components implemented on a framework) implemented in relation to each operation. For example, the software structure of the electronic device (101) may include an electronic payment application (hereinafter, electronic payment app (401)) of the electronic device (101) and / or a device manager (402). The electronic payment app (401) and the device manager (402) may operate under the control of the processor (120) of the electronic device (101).

[0104] In one embodiment, the electronic device (101) may initiate a registration procedure to register the accessory electronic device (201) as an authentication means through an electronic payment service (e.g., an electronic payment app). Although not illustrated in the drawing, the accessory electronic device (201) may be a device authenticated through pairing to communicate with the electronic device (101).

[0105] According to one embodiment, the accessory electronic device (201) can detect whether the accessory electronic device (201) is mounted / demounted, and based on the detected mounting state, can be connected to an authenticated electronic device (101) via short-range communication (e.g., Bluetooth communication). The electronic device (101) can perform the authentication registration procedures for FIGS. 5a / 5b whenever a registered accessory electronic device (201) is connected via short-range communication.

[0106] <Example 1>

[0107] Referring to FIG. 5a, in operation 510, the pay app (401) of the electronic device (101) may request an authentication registration request to a device manager (e.g., ring manager) (402) to use the accessory electronic device (201) as an authentication means for an electronic payment service.

[0108] In operation 511, the device manager (402) of the electronic device (101) may transmit an authentication registration request to an accessory electronic device (201) connected to the electronic device (101).

[0109] In operation 512, the accessory electronic device (201) can check whether the accessory electronic device (201) is in a wearing state and, based on the fact that the accessory electronic device (101) is in a wearing state, can notify the electronic device (101) of the wearing state information. For example, the accessory electronic device (201) can detect whether the accessory electronic device (201) is in a wearing state based on at least one sensor (e.g., the biometric sensor (250) or the temperature sensor (280) of FIG. 2).

[0110] For example, when the accessory electronic device (201) is set as an authentication means for an electronic payment service of the electronic device (101), it may be implemented to perform an authentication token generation / update procedure depending on whether the accessory electronic device (201) is mounted / demounted.

[0111] As another example, the device manager (402) of the electronic device (101) may request mounting / demounting information from the accessory electronic device (201) and receive mounting / demounting information of the accessory electronic device (101) in response to the request signal.

[0112] In operation 513, the device manager (402) of the electronic device (101) may generate an authentication token (e.g., first authentication token, 0x01) based on the accessory electronic device (201) being detected as mounted.

[0113] In operation 514, the state manager (402) of the electronic device (101) may transmit the generated authentication token (e.g., first authentication token, 0x01) to the accessory electronic device (201) through a communication module (e.g., communication module (190) of FIG. 1 or communication module (235) of FIG. 2).

[0114] In operation 515, the accessory electronic device (201) may store the first authentication token (e.g., 0x01) transmitted from the electronic device (101) in the accessory electronic device memory (e.g., memory (220) of FIG. 2).

[0115] In operation 516, independently or in parallel with operation 514, the device manager (402) of the electronic device (101) may transmit the generated first authentication token (e.g., 0x01) to the electronic payment app (401).

[0116] In operation 517, the electronic payment app (401) of the electronic device (101) may store the first authentication token (e.g., 0x01) transmitted from the device manager (402) in the memory of the electronic device (101) (e.g., the memory (130) of FIG. 1).

[0117] According to one embodiment, when the accessory electronic device (201) changes to a detachable state, operations 518 to 521 may be performed.

[0118] In operation 518, the accessory electronic device (201) can transmit detachment status information to the device manager (402) of the electronic device (101) through the communication module based on the change of the accessory electronic device (201) to the detachment status.

[0119] In operation 519, the device manager (402) of the electronic device (101) may generate a second authentication token (e.g., 0x02) based on the detachment status information of the accessory electronic device (201) and update the first authentication token to the second authentication token (e.g., 0x02).

[0120] In operation 520, the device manager (402) of the electronic device (101) may transmit an updated second authentication token (e.g., 0x02) to the accessory electronic device (201) via the communication module.

[0121] In operation 521, the accessory electronic device (201) may update the first authentication token stored in the memory (e.g., accessory electronic device memory (220)) with the second authentication token (e.g., 0x02) based on the second authentication token (e.g., 0x02) transmitted from the electronic device (101).

[0122] <Example 2>

[0123] Referring to FIG. 5b, in operation 550, the electronic payment app (401) of the electronic device (101) may request an authentication registration request to the device manager (e.g., ring manager) (402) of the electronic device (101) to use the accessory electronic device (201) as an authentication means for the electronic payment service.

[0124] In operation 551, the device manager (402) of the electronic device (101) may transmit an authentication registration request to the device manager (403) of the accessory electronic device (201) connected to the electronic device (101). For example, the device manager (403) of the accessory electronic device (201) may be installed in the accessory electronic device (201) as a software module for compatibility and connection with the accessory electronic device (201) and other electronic devices (e.g., the electronic device (101) of FIG. 1).

[0125] In operation 552, the device manager (403) of the accessory electronic device (201) can detect whether the accessory electronic device (201) is in a wearing state and confirm that the accessory electronic device (201) is in a mounted state. For example, the accessory electronic device (201) can detect whether the accessory electronic device (201) is in a wearing state based on at least one sensor (e.g., the biometric sensor (250) of FIG. 2 or the temperature sensor (280)).

[0126] In operation 553, the device manager (403) of the accessory electronic device (201) may generate a first authentication token (e.g., 0x01) based on the detected mounting status of the accessory electronic device (201).

[0127] In operation 554, the device manager (403) of the accessory electronic device (201) may store the generated first authentication token (e.g., 0x01) in memory (e.g., memory (220) of the accessory electronic device (201) of FIG. 2).

[0128] In operation 555, the device manager (403) of the accessory electronic device (201) may transmit the generated first authentication token (e.g., 0x01) to the device manager (402) of the electronic device (101).

[0129] In operation 556, the device manager (402) of the electronic device (401) may transmit the first authentication token (e.g., 0x01) transmitted from the accessory electronic device (201) to the electronic payment app (401).

[0130] According to another embodiment, the device manager (201) of the electronic device (101) may store the first authentication token within the device manager (201) without transmitting it to the electronic payment app (401).

[0131] In operation 557, the electronic payment app (401) of the electronic device (101) may store the first authentication token (e.g., 0x01) transmitted from the device manager (402) in memory (e.g., memory (130) of FIG. 1).

[0132] According to one embodiment, when the accessory electronic device (201) changes to a detachable state, operations 558 to 560 may be performed.

[0133] In operation 558, the device manager (403) of the accessory electronic device (201) can check the detachment status of the accessory electronic device (101).

[0134] In operation 559, the device manager (403) of the accessory electronic device (201) may generate a second authentication token (e.g., 0x02) based on the change in the detached state of the accessory electronic device (101).

[0135] In operation 560, the device manager (403) of the accessory electronic device (201) may update the first authentication token stored in the memory (e.g., accessory electronic device memory (220)) with the second authentication token (e.g., 0x02) based on the second authentication token (e.g., 0x02).

[0136] FIGS. 6A and 6B illustrate an electronic payment authentication service method of an electronic device using an accessory electronic device according to one embodiment. The embodiment of FIGS. 6A and 6B may represent an example in which the electronic device (101) acts as an entity that compares authentication tokens.

[0137] Referring to FIGS. 6A and 6B , in operation 610, the electronic payment app (401) of the electronic device (101) may perform the operations of FIGS. 5A / 5B to store an authentication token (e.g., a first authentication token, 0x01). In operation 611, the accessory electronic device (201) may also perform the operations of FIGS. 5A / 5B to store an authentication token (e.g., a first authentication token, 0x01).

[0138] As illustrated in FIG. 6A, when the accessory electronic device (101) is mounted, the payment processor can, in operation 612, request a payment request for the purchase of an item selected on the electronic device to the electronic payment app (401) of the electronic device (101).

[0139] In operation 613, the electronic payment app (401) of the electronic device (101) can check whether an authentication means (e.g., accessory electronic device authentication) is set for the payment request.

[0140] In operation 614, when the electronic payment app (401) of the electronic device (101) is set as an external device (e.g., an accessory electronic device (201)), it may transmit an authentication request (e.g., a user authentication request) to the device manager (402). The user authentication request may be transmitted together with an authentication token (e.g., a first authentication token, 0x01) stored in the electronic payment app (401) of the electronic device (101).

[0141] In operation 615, the device manager (402) of the electronic device (101) may transmit an authentication request to the accessory electronic device (201).

[0142] In operation 616, the accessory electronic device (201) may transmit an authentication token (e.g., a second authentication token, 0x01) stored in the accessory electronic device (201) to the device manager (402) of the electronic device (101) through the communication module in response to an authentication request from the electronic device (101).

[0143] In operation 617, the device manager (402) of the electronic device (101) can compare the authentication token (e.g., second authentication token, 0x01) received from the accessory electronic device (201) with the authentication token (e.g., first authentication token, 0x01) stored in the electronic payment app (401) of the electronic device (101).

[0144] In operation 618, the device manager (402) of the electronic device (101) may request user authentication to the accessory electronic device (201) if the authentication token (e.g., first authentication token, 0x01) stored in the electronic payment app of the electronic device and the authentication token stored in the accessory electronic device (e.g., second authentication token, 0x01) are the same.

[0145] For example, the accessory electronic device (201) may output an input alarm for a user authentication request (e.g., "There is a payment request. Please input your fingerprint (or gesture, touch)"). The input alarm may be, but is not limited to, sound output, vibration generation, or LED lamp blinking.

[0146] In operation 619, the accessory electronic device (201) may obtain user authentication information (e.g., fingerprint information or fingerprint value) for a user input and transmit the recognized user authentication information (e.g., fingerprint information) to the device manager (402) of the electronic device (101).

[0147] For example, user authentication for electronic payments may be specified by user-identifiable biometric information (e.g., fingerprints, blood flow, hand wrinkles, or PPG signals), as well as touch gestures or motion actions.

[0148] In operation 620, the device manager (402) of the electronic device (101) can transmit user authentication information to the electronic payment app (401).

[0149] In operation 621, the electronic payment app (401) of the electronic device (101) can transmit user authentication information to the electronic payment server (410).

[0150] For example, the electronic payment server (410) can compare the user authentication information transmitted from the electronic device (101) with the pre-stored user authentication information of the electronic device (101) to determine whether authentication is successful.

[0151] In operation 622, if user authentication is successful, the electronic payment server (410) can transmit user authentication success information to the electronic payment app (401).

[0152] In some embodiments, operations 621 and 622 may be performed in an electronic payment app (401).

[0153] In operation 623, the electronic payment app (401) of the electronic device (101) may transmit a payment approval request for the purchase of goods to the store server (430) (e.g., store app) based on successful user authentication.

[0154] In operation 624, the store server (430) may request confirmation by transmitting payment information for payment approval to the electronic payment server (410).

[0155] In operation 625, the electronic payment server (410) can transmit payment success information regarding payment approval in the electronic payment app (401) of the electronic device to the store server (430).

[0156] In operation 626, the store server (430) can perform payment completion based on payment success information transmitted from the electronic payment server (410).

[0157] As illustrated in FIG. 6B, when the accessory electronic device (201) is in a detached state, the payment processor may, in operation 650, detect the detached state of the accessory electronic device (201). In operation 651, the accessory electronic device (201) may update the authentication token stored in the memory of the accessory electronic device based on the detached state (e.g., second authentication token, 0x02). For example, in operation 651, the accessory electronic device (101) may also perform the operations of FIGS. 5A / 5B to update the authentication token (e.g., second authentication token, 0x02).

[0158] In operation 652, the store server (430) (and the store app) may request a payment request for the purchase of an item selected from the electronic device (101) to the electronic payment app (401) of the electronic device (101).

[0159] In operation 653, the electronic payment app (401) of the electronic device (101) can check whether an authentication means (e.g., accessory electronic device (201) authentication) is set for the payment request.

[0160] In operation 654, when the electronic payment app (401) of the electronic device (101) is set as an external device (e.g., an accessory electronic device (201)), it may transmit an authentication request (e.g., user authentication) to the device manager (402). The user authentication request may be transmitted together with an authentication token (e.g., a first authentication token, 0x01) stored in the electronic payment app (401) of the electronic device (101).

[0161] In operation 655, the device manager (402) of the electronic device (101) may transmit an authentication request to the accessory electronic device (201).

[0162] In operation 656, the accessory electronic device (201) may transmit an authentication token (e.g., a second authentication token, 0x02) stored in the accessory electronic device (201) to the device manager (402) of the electronic device (101) through the communication module in response to an authentication request of the electronic device (201).

[0163] In operation 657, the device manager (402) of the electronic device (101) can compare the authentication token (e.g., second authentication token, 0x02) received from the accessory electronic device (201) with the authentication token (e.g., first authentication token, 0x01) received from the electronic payment app (401) of the electronic device (101).

[0164] In operation 658, the device manager (402) of the electronic device (101) may transmit a failure event to the electronic payment app (401) if the authentication token (e.g., first authentication token, 0x01) received from the electronic payment app (401) of the electronic device (101) is different from the authentication token received from the accessory electronic device (e.g., second authentication token, 0x02).

[0165] In operation 659, the electronic payment app (401) of the electronic device (101) may display a user authentication request using the electronic payment app (401) on the display in response to a failure event. For example, the electronic payment app (401) may display a configured user authentication (e.g., fingerprint, iris, or pattern) input UI screen on the display.

[0166] In operation 660, the electronic payment app (401) of the electronic device (101) may receive user authentication information. The user authentication information may be set user authentication information. For example, if user authentication is set to fingerprint, the user authentication information may refer to fingerprint information.

[0167] In operation 661, the electronic payment app (401) of the electronic device (101) can transmit recognized user authentication information (e.g., fingerprint information) to the electronic payment server (410). The electronic payment server (410) can compare the user authentication information transmitted from the electronic device (101) with the stored user authentication information of the electronic device (101) to determine whether authentication is successful.

[0168] In operation 662, if user authentication is successful, the electronic payment server (410) can transmit user authentication success information to the electronic payment app (401).

[0169] In some embodiments, operations 661 and 662 may be performed in an electronic payment app (401).

[0170] In operation 663, the electronic payment app (401) of the electronic device (101) may transmit a payment approval request for the purchase of goods to the store server (430) (e.g., store app) based on successful user authentication.

[0171] In operation 664, the store server (430) may request confirmation by transmitting payment information for payment approval to the electronic payment server (624).

[0172] In operation 665, the electronic payment server (410) can transmit payment success information regarding payment approval in the electronic payment app (401) of the electronic device to the store server (625).

[0173] In operation 666, the store server (430) can complete payment based on payment success information transmitted from the electronic payment server (410).

[0174] FIGS. 7A and 7B illustrate an electronic payment authentication service method of an electronic device using an accessory electronic device according to one embodiment. The embodiment of FIGS. 7A / 7B may refer to an example in which the accessory electronic device (201) acts as a subject that compares authentication tokens. FIGS. 7A and 7B illustrate that the accessory electronic device (201) includes a device manager (403), but the electronic device (101) may include a device manager (e.g., the device manager (402) of FIG. 4), and the electronic payment app (401) and the accessory electronic device (201) may exchange signals / data through the device manager of the electronic device (101).

[0175] Referring to FIGS. 7A and 7B, in operation 710, the electronic device (101) and the accessory electronic device (201) may be in a paired state. The accessory electronic device (201) may refer to an electronic device pre-registered with the electronic device (101) as an authentication means when providing an electronic payment service.

[0176] As illustrated in FIG. 7A, when the accessory electronic device (201) is in a mounted state, the payment processor can be described. In operation 711, the device manager (403) of the accessory electronic device (201) can detect the mounted state of the accessory electronic device (201).

[0177] In operation 712, the device manager (403) of the accessory electronic device (201) may generate an authentication token (e.g., a second authentication token, 0x01) based on detection of the mounting state.

[0178] In operation 713, the device manager (403) of the accessory electronic device (201) may store the generated authentication token in memory (e.g., memory (220) of FIG. 2).

[0179] In operation 714, the device manager (403) of the accessory electronic device (201) may transmit the generated authentication token (e.g., first authentication token, 0x01) to the electronic device (101).

[0180] In operation 715, the electronic device (101) or the electronic payment app (401) may store an authentication token (e.g., a first authentication token, 0x01) transmitted from the accessory electronic device (201) in a memory (e.g., memory (130) of FIG. 1).

[0181] In operation 716, the electronic payment app (401) of the electronic device (101) can receive a payment request for an online purchase item from the server (104) through the communication module.

[0182] In the drawings of FIGS. 7A and 7B, the server (104) is depicted as being integrated into one, but the server (104) may have a structure in which the electronic payment server (410) and the store server (430) are separated, as shown in FIGS. 6A and 6B. According to another embodiment, a payment request may be transmitted to the electronic payment app via the store server (430).

[0183] In operation 717, the electronic payment app (401) of the electronic device (101) can check whether an authentication means (e.g., accessory electronic device (201) authentication) is set for the payment request.

[0184] In operation 718, when the electronic payment app (401) of the electronic device (101) is set to an external device (e.g., an accessory electronic device (201)), the electronic payment app (401) may transmit a user authentication request (e.g., a user authentication request) to the accessory electronic device (201). The user authentication request may be transmitted together with an authentication token (e.g., a first authentication token, 0x01) stored in the electronic payment app (401) of the electronic device (101).

[0185] In operation 719, the accessory electronic device (201) can compare an authentication token (e.g., a first authentication token, 0x01) received from the electronic device (101) with an authentication token (e.g., a second authentication token, 0x01) stored in the accessory electronic device (201).

[0186] In operation 720, the accessory electronic device (201) may request user authentication input if the authentication token (e.g., first authentication token, 0x01) received from the electronic device (101) and the authentication token (e.g., second authentication token, 0x01) stored in the accessory electronic device (201) are the same.

[0187] In some embodiments, operation 720 may be omitted.

[0188] In operation 721, the accessory electronic device (201) may receive (or obtain) user authentication information (e.g., fingerprint information, fingerprint value) for user input.

[0189] In operation 722, the accessory electronic device (201) can transmit recognized user authentication information (e.g., fingerprint information) to the electronic device (101) or the electronic payment app (401).

[0190] In operation 723, the electronic payment app (401) of the electronic device (101) may transmit user authentication information transmitted from the accessory electronic device (201) to the server (104) (e.g., the electronic payment server (410)). For example, the server (104) (e.g., the electronic payment server (410)) may compare the user authentication information transmitted from the electronic device (101) with the stored user authentication information of the electronic device (101) to determine whether authentication is successful.

[0191] As another example, operation 723 may be omitted, and the electronic payment app (401) may determine whether authentication is successful by comparing the user authentication information transmitted from the accessory electronic device (201) with the user authentication information of the pre-stored electronic device (101).

[0192] In operation 724, the electronic payment app (401) of the electronic device (101) may transmit payment approval for the payment request to the server (104) based on successful user authentication.

[0193] In operation 725, the server (104) can perform payment completion according to payment approval.

[0194] In another embodiment, when the server (104) includes an electronic payment server (410) and a store server (430) as in FIG. 6A, operations 723 to 725 may be replaced with operations 621 to 626.

[0195] As illustrated in FIG. 7b, when the payment processor describes that the accessory electronic device (201) is in a detached state, in operation 751, the device manager (403) of the accessory electronic device (201) can detect the detached state of the accessory electronic device (201).

[0196] In operation 751, the device manager (403) of the accessory electronic device (201) may generate a new authentication token (e.g., a second authentication token, 0x02) based on detection of the detachment state.

[0197] In operation 752, the device manager (403) of the accessory electronic device (201) may update the authentication token stored in the memory (e.g., memory (220) of FIG. 2) with the newly generated authentication token (e.g., second authentication token, 0x01 → 0x02).

[0198] In operation 753, the electronic payment app (401) of the electronic device (101) can receive a payment request for an online purchase item from the server (104) through the communication module.

[0199] In operation 754, the electronic payment app (401) of the electronic device (101) can check whether an authentication means (e.g., accessory electronic device authentication) is set for the payment request.

[0200] In operation 755, when the electronic payment app (401) of the electronic device (101) is set to an external device (e.g., an accessory electronic device (201)), the electronic payment app (401) may transmit a user authentication request (e.g., a user authentication request) to the accessory electronic device (201). The user authentication request may be transmitted together with an authentication token (e.g., a first authentication token, 0x01) stored in the electronic payment app (401) of the electronic device (101).

[0201] In operation 756, the accessory electronic device (201) can compare an authentication token (e.g., a first authentication token, 0x01) received from the electronic device (101) with an authentication token (e.g., a second authentication token, 0x02) stored in the accessory electronic device (201).

[0202] In operation 757, if the authentication token (e.g., first authentication token, 0x01) received from the electronic device (101) and the authentication token (e.g., second authentication token, 0x01) stored in the accessory electronic device (201) are different, the accessory electronic device (201) may transmit a failure event to the electronic device (101) or the electronic payment app (401) through the communication module.

[0203] In operation 758, the electronic payment app (401) of the electronic device (101) may display a user authentication request using the electronic payment app (401) on the display in response to a failure event. For example, the electronic payment app (401) may display a configured user authentication (e.g., fingerprint, iris, or pattern) input UI screen on the display.

[0204] In operation 759, the electronic payment app (401) of the electronic device (101) may receive (or acquire) user authentication information (e.g., fingerprint information, or fingerprint value) for user input.

[0205] In operation 760, the electronic payment app (401) of the electronic device (101) may transmit user authentication information authenticated through the electronic device (101) to a server (104) (e.g., an electronic payment server (410)). For example, the server (104) (e.g., an electronic payment server (410)) may compare the user authentication information transmitted from the electronic device (101) with the stored user authentication information of the electronic device (101) to determine whether authentication is successful.

[0206] As another example, operation 760 may be omitted, in which case the electronic payment app (401) may determine whether authentication is successful by comparing the entered user authentication information with the stored user authentication information of the electronic device (101).

[0207] In operation 761, the electronic payment app (401) of the electronic device (101) may transmit payment approval for the payment request to the server (104) based on successful user authentication.

[0208] In operation 762, the server (104) can perform payment completion according to payment approval.

[0209] In another embodiment, when the server (104) includes an electronic payment server (410) and a store server (430) as in FIG. 6b, operations 760 to 762 may be replaced with operations 661 to 666.

[0210] FIG. 8 illustrates an example of authentication means setting screens related to an electronic payment service of an electronic device according to one embodiment.

[0211] Referring to FIG. 8, an electronic device (101) according to one embodiment can support an offline easy payment (e.g., electronic payment) service function using an external electronic device.

[0212] According to one embodiment, the electronic device (101) <801> As illustrated, a first UI screen (810) for confirming user consent to use an accessory electronic device (201) as a user authentication means in a simple payment service may be displayed on a display (e.g., a display module (160) of FIG. 1). The first UI screen (810) may include guidance information for simple payment and an agreement item (815) for settings. When the user selects an agreement item (815), the electronic device (101) <802> As illustrated, a second UI screen (820) for setting authentication input items in the accessory electronic device (201) may be displayed. The second UI screen (820) may include items for fingerprint, gesture, or touch settings as user authentication input using the accessory electronic device (201). The user input is only an example and is not limited to the examples of the second UI screen (820). For example, when the user selects touch settings in the second UI screen (820), the electronic device (101) <803> As shown in , a third UI screen (830) for setting touch input with user authentication can be displayed. After the touch input setting is completed, the electronic device (101) <804> As illustrated, a fourth UI screen (840) for selecting a card to be used for simple payment can be displayed. The user can select a card (850) to be used for simple payment among the cards registered in the electronic device (101) through the fourth UI screen (840). <805> As shown, the electronic device (101) may display a fifth UI screen (850) requesting guidance information and approval input (e.g., fingerprint input item (860)) to proceed with electronic payment through the selected card (855) when user authentication is completed based on the accessory electronic device (201).When a user performs fingerprint authentication on the 5th UI screen (850), user authentication can be performed based on user authentication information entered in the accessory electronic device (201) during simple payment.

[0213] FIG. 9 is a diagram illustrating an offline payment system using an electronic device and an accessory electronic device according to one embodiment.

[0214] Referring to FIG. 9, an offline payment system (900) using an accessory electronic device as an authentication means according to one embodiment may include an electronic device (101), an accessory electronic device (201), an app server (410), a card company server (920), and a payment device (920) (e.g., a POS device) of an offline store.

[0215] The accessory electronic device (201) can enter an electronic payment mode based on the detection of a preset gesture for electronic payment. The accessory electronic device (201) can request payment card information and token information for payment from the electronic device (101). The accessory electronic device (201) can receive payment card information and token information from the electronic device (101). The accessory electronic device (201) can emit a payment request signal including the received payment card information and token information to the outside through a short-range communication module (e.g., NFC, MST communication). The payment device (920) can complete payment based on the payment request signal received from the outside through the short-range communication module.

[0216] The payment device (920) can transmit payment completion approval information to the card company server (910). The card company server (910) can transmit the payment completion approval information to an electronic payment server (410) that provides electronic payment services (e.g., Samsung Pay server or Naver Pay server). The electronic payment server (410) can transmit the payment completion approval information to the electronic device (101). The electronic device (101) can notify / inform the user about the electronic payment approval information.

[0217] According to one embodiment, the electronic device (101) may transmit information on whether payment has been completed to the accessory electronic device (201). For example, the electronic device (101) may output information on payment success or failure on the display of the electronic device (101), or transmit information on payment success or failure to the accessory electronic device (201) so as to notify whether payment has been successful or failed through the accessory electronic device (201).

[0218] According to one embodiment, the electronic device (101) can perform a registration procedure for registering the accessory electronic device (201) as a payment means (or authentication means) when making an offline or online electronic payment through the operations illustrated in FIG. 10.

[0219] FIG. 10 illustrates a method for setting up an accessory electronic device as an authentication and payment means for an electronic payment service of an electronic device according to one embodiment.

[0220] Referring to FIG. 10, according to one embodiment, the electronic payment app (401) of the electronic device (101) can confirm that external simple payment has been set up in relation to the electronic payment service in operation 1010. For example, a user can proceed with simple payment setup using an external electronic device (e.g., an accessory electronic device (201)) through the UI screens illustrated in FIG. 8.

[0221] In operation 1011, the electronic payment app (401) of the electronic device (101) may request pairing by including identification information (e.g., electronic device id) of the electronic device (101) to the device manager (403) of the accessory electronic device (201) through the communication module.

[0222] The accessory electronic device (201) can determine whether the electronic device (101) is a registered electronic device (101) based on the identification information of the electronic device (101). For example, the identification information of the electronic device (101) may refer to a unique value generated when the electronic device (101) and the accessory electronic device (201) are initially connected. The electronic device (101) and the accessory electronic device (201) may each store device identification information (e.g., electronic device ID, accessory device ID) when the initial connection is established, and may be configured to exchange device identification information during pairing so that, if the device identification information is different, the pairing procedure is not performed and the initial registration procedure is performed again.

[0223] For another example, the electronic device (201) can check whether the electronic device (101) is a registered electronic device that has a record of being paired with the accessory electronic device (201).

[0224] In operation 1012, the device manager (403) of the accessory electronic device (201) can detect whether the accessory electronic device (201) is in a mounted state by checking whether the accessory electronic device (201) is in a worn state. For example, the accessory electronic device (201) can detect whether the accessory electronic device (201) is in a mounted state based on at least one sensor (e.g., a biometric sensor (250) or a temperature sensor (280) of FIG. 2).

[0225] In operation 1013, the device manager (403) of the accessory electronic device (201) may generate an authentication token (e.g., second authentication token, 0x01) based on the accessory electronic device (201) being detected as being mounted.

[0226] In operation 1014, the device manager (403) of the accessory electronic device (201) may transmit at least one of the generated authentication token and / or personal identification information (or personal recognition information) to the electronic payment app (401) of the electronic device (101) via the communication module.

[0227] Personal identification information (PII) can refer to a unique value generated to identify a user using biometric information acquired from an accessory electronic device. PII can be generated based on biometric information, such as fingerprint information, blood flow, hand wrinkles, pulse, or skin temperature. In some cases, PII may be omitted.

[0228] In operation 1015, the electronic payment app (401) of the electronic device (101) may request simple payment approval input using the accessory electronic device (201). For example, the user may perform authentication input settings, card selection, and approval input based on the screen UIs of FIG. 8.

[0229] In operation 1016, the electronic payment app (401) of the electronic device (101) may generate a device token for pairing connection upon authorization input.

[0230] In operation 1017, the electronic payment app (401) of the electronic device (101) may store an authentication token (e.g., a first authentication token, 0x01) transmitted from the accessory electronic device (201).

[0231] In operation 1018, the electronic payment app (401) of the electronic device (101) may transmit successful pairing connection information for payment, including a device token and an authentication token, to the accessory electronic device (201).

[0232] In operation 1019, the device manager (403) of the accessory electronic device (201) may store the generated authentication token (e.g., second authentication token, 0x01) if the authentication token generated during pairing connection and the authentication token transmitted from the electronic device are the same.

[0233] In operation 1020, the device manager (403) of the accessory electronic device (201) can detect the detachment status of the accessory electronic device (201).

[0234] In operation 1021, the device manager (403) of the accessory electronic device (201) may generate a new authentication token (e.g., 0x02) based on the detection of the attachment / detachment status based on the attachment / detachment status information of the accessory electronic device (201) and update the authentication token stored in the memory (e.g., the memory (220) of FIG. 2) (e.g., a second authentication token, 0x01 → 0x02).

[0235] FIG. 11 illustrates an electronic payment service method of an electronic device using an accessory electronic device according to one embodiment.

[0236] Referring to FIG. 11, an accessory electronic device (201) according to one embodiment may support a function of performing user authentication for simple payment when providing an offline simple payment service of the electronic device (101).

[0237] In operation 1110, the pay app (401) of the electronic device (101) may perform the operations of FIG. 10 to store an authentication token (e.g., a first authentication token, 0x01). In operation 1112, the accessory electronic device (201) may also perform the operations of FIG. 10 to store an authentication token (e.g., a second authentication token, 0x01).

[0238] In operation 1113, the accessory electronic device (201) may detect a designated action for payment. For example, the electronic device may set a gesture action (e.g., double-tap) to enter the simple payment mode as shown in FIG. 8.

[0239] In operation 1114, the accessory electronic device (201) may request payment information from the electronic payment app (401) of the electronic device via the communication module. For example, the payment information request may include an authentication token (e.g., a second authentication token) stored in the accessory electronic device (201) and personal identification information.

[0240] In operation 1115, when the electronic payment app (401) of the electronic device (101) is set to an external device (e.g., an accessory electronic device (201)), it can be confirmed that the authentication means is set to the device manager (402).

[0241] In operation 1116, the electronic payment app (401) of the electronic device (101) may transmit an authentication token (e.g., a first authentication token, 0x01) stored in the electronic payment app to the device manager (402).

[0242] In operation 1117, the device manager (402) of the electronic device (101) can compare the authentication token (e.g., second authentication token, 0x01) received from the accessory electronic device (201) with the authentication token (e.g., first authentication token, 0x01) stored in the electronic payment app (401) of the electronic device (101).

[0243] In operation 1118, the device manager (402) of the electronic device (101) may transmit the result of comparing an authentication token (e.g., first authentication token, 0x01) stored in the electronic payment app of the electronic device and an authentication token (e.g., second authentication token, 0x01) stored in the accessory electronic device (201) to the electronic payment app (401).

[0244] In operation 1119, the electronic payment app (401) of the electronic device (101) may transmit payment information to the accessory electronic device based on the same authentication cotton. The payment information may include, for example, a device token and disposable card information for payment.

[0245] In operation 1120, the accessory electronic device (201) can perform payment using short-range communication (e.g., a tag for NFC or MST payment) using payment information transmitted from the electronic payment app (401) of the electronic device (101). The payment signal using short-range communication can be transmitted externally via the short-range communication module. For example, the payment signal using short-range communication can include a device token and disposable card information for payment.

[0246] In operation 1121, the accessory electronic device (201) can output a notification informing that payment is being made using short-range communication.

[0247] In some embodiments, operation 1121 may be omitted.

[0248] In operation 1122, the accessory electronic device (201) can receive a payment signal using short-range communication.

[0249] In operation 1123, the payment device (1101) can complete payment approval based on the payment signal received using short-range communication.

[0250] In operation 1124, the electronic device (101) can receive payment completion information from the electronic payment server (410).

[0251] FIG. 12 illustrates an offline electronic payment service method using an accessory electronic device according to one embodiment.

[0252] Referring to FIG. 12, an accessory electronic device (201) according to one embodiment may detect, in operation 1210, a payment gesture operation designated for payment (e.g., a gesture operation while wearing the accessory electronic device).

[0253] In operation 1220, the accessory electronic device (201) can determine whether there is an electronic device (101) connected (or paired) with the accessory electronic device (201).

[0254] In operation 1230, if there is an electronic device connected to the accessory electronic device (201) (yes in operation 1220), the accessory electronic device (201) may transmit at least one of a device token and personal identification information to the electronic device (101) via the communication module. The device token may refer to a token value (or device identification information) exchanged between the electronic device (101) and the accessory electronic device (201) to identify the devices during pairing. The personal identification information may refer to a unique value generated to identify the user using the user's personal biometric information acquired by the accessory electronic device (201).

[0255] In operation 1225, the accessory electronic device (201) may output payment failure information (e.g., vibration or sound) if there is no electronic device (101) connected to the accessory electronic device (201) (no in operation 1220).

[0256] In operation 1240, the electronic device (101) can determine whether the device token transmitted from the accessory electronic device (201) is the same as the device token stored when pairing with the accessory electronic device (201).

[0257] In operation 1250, if the device token transmitted from the accessory electronic device (201) and the device token stored in the electronic device (101) are the same (yes in operation 1240), the electronic device (101) may transmit an authentication token (e.g., a first authentication token) stored in the electronic device (101) and card information for payment (e.g., a disposable card number) to the accessory electronic device (201).

[0258] In operation 1255, if the device token transmitted from the accessory electronic device (201) and the device token stored in the electronic device (101) are different (no in operation 1240), the electronic device (101) may display a payment failure message on the display and transmit payment failure information to the accessory electronic device (201).

[0259] In operation 1260, the accessory electronic device (201) can determine whether an authentication token (e.g., a first authentication token) transmitted from the electronic device (101) and an authentication token (e.g., a second authentication token) stored in the accessory electronic device (201) are the same.

[0260] In operation 1270, if the authentication token (e.g., first authentication token) transmitted from the electronic device (101) and the authentication token (e.g., second authentication token) stored in the accessory electronic device (201) are the same (yes in operation 1260), the accessory electronic device (201) can switch to payment mode and transmit the card information received from the electronic device (101) to a payment device (e.g., POS device).

[0261] In operation 1265, if the authentication token (e.g., first authentication token) transmitted from the electronic device (101) is different from the authentication token (e.g., second authentication token) stored in the accessory electronic device (201) (no in operation 1260), the accessory electronic device (201) may transmit a payment failure message to the electronic device (101).

[0262] FIG. 13 illustrates an example of an electronic payment service method of an electronic device using an accessory electronic device according to one embodiment.

[0263] Referring to FIG. 13, an electronic device (101) according to one embodiment may be implemented as an electronic device (101) that supports XR content (e.g., augmented reality content). For example, the electronic device (101) <1301> As shown in , an augmented reality image (1310) through a camera can be displayed on the display. The electronic device (101) can display payment information (1320) for an offline store by overlaying it on the augmented reality image (1310). If the electronic device (101) is set as an authentication means for electronic payment, <1230> As illustrated, request guide information (1330) guiding easy payment with an accessory electronic device (201) can be superimposed on an augmented reality image (1310) and displayed. A user can check the request guide information (1330) and perform offline electronic payment using the accessory electronic device (201).

[0264] According to one embodiment, a method for providing an electronic payment service using an accessory electronic device may include an operation in which, when pairing with an accessory electronic device through a communication module, the electronic device generates a first authentication token through a device manager associated with the accessory electronic device based on detection of wearing of the accessory electronic device. According to one embodiment, the method may include an operation in which the generated first authentication token is transmitted to an electronic payment application. According to one embodiment, the method may include an operation in which, when an electronic payment service request is received from the electronic payment application, the method may include an operation in which the accessory electronic device is requested to provide an authentication token and a second authentication token is received from the accessory electronic device or the device manager. According to one embodiment, the method may include an operation in which, when the first authentication token stored in the electronic payment application and the second authentication token transmitted from the accessory electronic device or the device manager are identical, the method may include an operation in which the accessory electronic device is requested to provide user authentication for electronic payment through the communication module. According to one embodiment, the method may include an operation in which the success or failure of user authentication is determined based on user authentication information received from the accessory electronic device.

[0265] The method according to one embodiment may further include the electronic device generating a third authentication token based on detection of detachment of the accessory electronic device through the device manager, and updating the first authentication token with the third authentication token.

[0266] The method according to one embodiment may further include an action of displaying authentication failure information on a display through the electronic payment application when the first authentication token stored in the electronic payment application and the second authentication token transmitted from the device manager are different.

[0267] A method according to one embodiment may include, after receiving the second authentication token, if the first authentication token stored in the electronic payment application and the second authentication token transmitted from the device manager are different, an operation of stopping the user authentication requested to the accessory electronic device and requesting user authentication through the electronic payment application.

[0268] According to one embodiment, when the device manager is programmed to the memory of the electronic device, the operation of transmitting the first authentication token to the electronic payment application may further include the operation of transmitting the generated first authentication token to the electronic payment application and the accessory electronic device, and comparing the first authentication token and the second authentication token through the electronic payment application or the device manager to determine whether they are the same.

[0269] A method according to one embodiment may further include receiving, from the accessory electronic device through the communication module, the first authentication token or the third authentication token generated through the device manager when the device manager is programmed to a memory of the accessory electronic device, and transmitting, to the electronic payment application, the first authentication token or the third authentication token transmitted from the accessory electronic device through the communication module.

[0270] The operation of determining whether the user authentication is successful according to one embodiment may further include an operation of proceeding with the electronic payment service if the user authentication information transmitted from the accessory electronic device is identical to the user authentication information transmitted to the electronic device.

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

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

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

[0274] According to one embodiment, the method according to one embodiment disclosed in this document may be provided as a computer program product. The computer program product may be traded between sellers and buyers 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 may be provided through an application store (e.g., Play Store). TM ) or directly between two user devices (e.g., smart phones), online distribution (e.g., downloading or uploading). In the case of online distribution, at least a portion of the computer program product may be at least temporarily stored or temporarily created in a machine-readable storage medium, such as the memory of a manufacturer's server, an application store's server, or an intermediary server.

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

Claims

1. In electronic devices, A communication module comprising at least one communication circuit; A memory (130) storing executable instructions and Contains a processor, The above instructions, when executed by the processor, cause the electronic device to: Based on the information that the wearing of the accessory electronic device is detected while paired with the accessory electronic device registered in the memory through the communication module, a first authentication token is generated through a device manager related to the accessory electronic device, and the generated first authentication token is transmitted to an electronic payment application stored in the memory. When an electronic payment service request is received from the electronic payment application, an authentication token is requested from the accessory electronic device and a second authentication token is received from one of the accessory electronic device or the device manager. If the first authentication token stored in the electronic payment application and the second authentication token transmitted from one of the accessory electronic device or the device manager are the same, request user authentication for electronic payment to the accessory electronic device, An electronic device that determines whether user authentication is successful based on user authentication information received from the above accessory electronic device.

2. In paragraph 1, The above instructions cause the electronic device to: An electronic device that generates a third authentication token based on receiving information that the detachment of the accessory electronic device has been detected from the accessory electronic device after storing the first authentication token in the memory, and updates the first authentication token with the third authentication token.

3. In paragraph 2 The above instructions cause the electronic device to An electronic device that displays authentication failure information on a display through the electronic payment application when the first authentication token stored in the electronic payment application and the second authentication token transmitted from the device manager are different.

4. In paragraph 2 The above instructions cause the electronic device to: An electronic device that, if the first authentication token stored in the electronic payment application and the second authentication token transmitted from the device manager are different, suspends user authentication requested from the accessory electronic device and requests user authentication using the electronic payment application.

5. In paragraph 3 or 4, An electronic device wherein the first authentication token and the second authentication token include at least one of token data, device identification information, and personal identification information.

6. In paragraph 5, An electronic device, wherein the user authentication is one of biometric information or a password.

7. In paragraph 2, If the above device manager is programmed to the memory of the electronic device, the instructions cause the electronic device to: Transmitting said first authentication token to said electronic payment application and said accessory electronic device; An electronic device further comprising instructions for comparing the first authentication token and the second authentication token to determine whether they are identical through the electronic payment application or the device manager.

8. In paragraph 2, If the above device manager is programmed to the memory of the accessory electronic device, the instructions cause the electronic device to: Receive the first authentication token or the third authentication token generated through the device manager from the accessory electronic device through the communication module, An electronic device further comprising instructions for transmitting the first authentication token or the third authentication token transmitted from the accessory electronic device through the communication module to the electronic payment application.

9. In paragraph 2, The above instructions cause the electronic device to: An electronic device that allows the electronic payment service to proceed when the user authentication information transmitted from the accessory electronic device is identical to the user authentication information transmitted to the electronic device.

10. In accessory electronic devices, At least one sensor; A communication module comprising at least one communication circuit; Memory that stores executable instructions and Contains a processor, The above instructions, when executed by the processor, cause the accessory electronic device to: Pairing with the electronic device through the communication module, generating a first authentication token based on detecting wearing of the accessory electronic device based on the at least one sensor, storing the first authentication token in the memory, and transmitting the first authentication token to the electronic device through the communication module, When a second authentication token for an electronic payment request is received from the electronic device, user authentication request information for the electronic payment request is notified based on the first authentication token and the second authentication token being identical, Determining whether user authentication is successful based on user authentication information detected through at least one of the above sensors, An accessory electronic device that transmits user authentication success information for an electronic payment request to the electronic device through the communication module when the user authentication is successful, or transmits user authentication failure information to the electronic device through the communication module when the user authentication fails.

11. In a method for providing electronic payment service for an electronic device using an accessory electronic device, An operation of generating a first authentication token through a device manager associated with the accessory electronic device based on pairing the accessory electronic device with the electronic device and receiving information from the accessory electronic device that wearing of the accessory electronic device has been detected; An action of transmitting the first authentication token generated above to an electronic payment application; When an electronic payment service request is received from the electronic payment application, an operation of requesting an authentication token from the accessory electronic device and receiving a second authentication token from either the accessory electronic device or the device manager; An operation of requesting user authentication for electronic payment to the accessory electronic device through the communication module when the first authentication token stored in the electronic payment application and the second authentication token transmitted from one of the accessory electronic device or the device manager are identical; and A method comprising: performing an operation for determining whether user authentication is successful based on user authentication information received from the accessory electronic device.

12. In paragraph 11, A method further comprising: generating a third authentication token based on information received from the accessory electronic device that the detachment of the accessory electronic device has been detected after storing the first authentication token in the memory; and updating the first authentication token with the third authentication token.

13. In Article 11 A method further comprising an action of displaying authentication failure information on a display through the electronic payment application when the first authentication token stored in the electronic payment application and the second authentication token transmitted from the device manager are different.

14. In Article 11 After receiving the above second authentication token, A method further comprising: if the first authentication token stored in the electronic payment application and the second authentication token transmitted from the device manager are different, an action of stopping the user authentication requested to the accessory electronic device and requesting user authentication through the electronic payment application.

15. In paragraph 13 or 14, A method wherein the first authentication token and the second authentication token include token data, device identification information and personal identification information.

Images