Wearable device, method, and computer program for firmware update

Abstract

Disclosed is a wearable device. The wearable device may store a request for switching to a data transmission mode in a memory capable of communicating with an external electronic device, while receiving power from the external electronic device. The wearable device may receive firmware information of the external electronic device from the external electronic device. The wearable device may transmit, to the external electronic device, a signal for updating firmware based on the firmware information. The wearable device may receive the power from the external electronic device after transmitting the signal for updating the firmware. The request for switching to the data transmission mode may include a request for the firmware information of the external electronic device.

Description

Wearable device, method, and computer program for firmware update

[0001] The following descriptions relate to a wearable device, a method, and a non-transitory computer-readable recording medium for firmware update.

[0002] Wearable devices, such as earbuds or ring devices, can be stored within a dedicated cradle. The cradle can be used, for example, to protect or charge the stored wearable device.

[0003] A wearable device is disclosed. The wearable device may include at least one processor including a battery, an antenna, a communication circuit, and a processing circuit, and a memory storing instructions and including one or more storage media. The instructions, when individually or collectively executed by the at least one processor, may cause the wearable device to store a request for switching to a data transfer mode in the memory capable of communicating with an external electronic device while receiving power from the external electronic device. The instructions, when individually or collectively executed by the at least one processor, may cause the wearable device to receive firmware information of the external electronic device from the external electronic device. The instructions, when individually or collectively executed by the at least one processor, may cause the wearable device to transmit a signal to the external electronic device for updating firmware based on the firmware information. The instructions, when executed individually or collectively by the at least one processor, may cause the wearable device to receive power from the external electronic device after transmitting the signal for updating the firmware. The request to switch to the data transfer mode may include a request for the firmware information of the external electronic device.

[0004] A method is disclosed. The method can be performed by a wearable device including a battery, a communication circuit, and a memory. The method may include an operation of storing a request for switching to a data transmission mode in the memory capable of communicating with the external electronic device while receiving power from the external electronic device. The method may include an operation of receiving firmware information of the external electronic device from the external electronic device. The method may include an operation of transmitting a signal to the external electronic device for updating firmware based on the firmware information. The method may include an operation of receiving the power from the external electronic device after transmitting the signal for updating the firmware. The request for switching to the data transmission mode may include a request for the firmware information of the external electronic device.

[0005] A non-transitory computer-readable storage medium is disclosed. The non-transitory computer-readable storage medium may include a program comprising instructions. The instructions, when individually or collectively executed by at least one processor of a wearable device including a battery, a communication circuit, and a memory, may cause the wearable device to store a request for switching to a data transfer mode in the memory capable of communicating with the external electronic device while receiving power from the external electronic device. The instructions, when individually or collectively executed by the at least one processor, may cause the wearable device to receive firmware information of the external electronic device from the external electronic device. The instructions, when individually or collectively executed by the at least one processor, may cause the wearable device to transmit a signal to the external electronic device for updating firmware based on the firmware information. The instructions, when executed individually or collectively by the at least one processor, may cause the wearable device to receive power from the external electronic device after transmitting the signal for updating the firmware. The request to switch to the data transfer mode may include a request for the firmware information of the external electronic device.

[0006] Figure 1 is a block diagram of an electronic device within a network environment.

[0007] FIG. 2A is a diagram illustrating an exemplary wearable device.

[0008] Figure 2b is an exploded view of an exemplary wearable device.

[0009] Figure 3a is a drawing showing an open state of an electronic device.

[0010] Figure 3b is a drawing showing a closed state of an electronic device.

[0011] Figure 4a is a block diagram of a plurality of electronic devices.

[0012] FIG. 4b is a diagram illustrating data within the memory of multiple electronic devices.

[0013] Figure 5 is a flowchart illustrating an operation of a wearable device to determine whether to update the firmware of an electronic device.

[0014] Figure 6 is a flowchart illustrating an operation of a wearable device transmitting data for updating firmware of an electronic device.

[0015] Figure 7 is a flowchart illustrating an operation of an electronic device transmitting firmware version information of the electronic device.

[0016] Figure 8 is a flowchart illustrating an operation of an electronic device performing a firmware update of the electronic device.

[0017] Figure 1 is a block diagram of an electronic device (101) within a network environment (100).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0035] 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 realizing eMBB, a loss coverage (e.g., 664 dB or less) for realizing mMTC, or a U-plane latency (e.g., 0.5 ms or less for downlink (DL) and uplink (UL), or 6 ms or less for round trip) for realizing URLLC.

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

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

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

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

[0040] Figure 2a is a diagram illustrating an exemplary wearable device. Figure 2b is an exploded view of the exemplary wearable device.

[0041] The wearable device (200) can correspond to the electronic device (102) of FIG. 1.

[0042] Referring to FIG. 2A, the wearable device (200) may include a housing (210). The housing (210) may form an exterior of the wearable device (200). For example, the housing (210) may define or include a first side (200A), a second side (200B), a third side (200C), and a fourth side (200D) of the wearable device (200).

[0043] The first surface (200A) may be a surface that comes into contact with the body (e.g., a finger) of a user wearing the wearable device (200). For example, the first surface (200A) may be formed as a curved surface to correspond to the circumference shape of the finger that comes into contact. The second surface (200B) may be opposite to the first surface (200A). For example, the second surface (200B) may include a curved surface.

[0044] The third side (200C) may extend from a portion of the second side (200B) to a portion of the first side (200A). For example, the third side (200C) may extend from a first edge (E1) of the second side (200B) to a first edge (P1) of the first side (200A).

[0045] The fourth side (200D) may be opposed to the third side (200C). The fourth side (200D) may extend from another portion (or remaining portion) of the second side (200B) to another portion (or remaining portion) of the first side (200A). For example, the fourth side (200D) may extend from the second edge (E2) of the second side (200B) to the second edge (P2) of the first side (200A).

[0046] The housing (210) may include a first member (212) and a second member (214) coupled to the first member (212). The first member (212) may form a second surface (200B) of the housing (210), a first region (C1) of a third surface (200C), and a first region (D1) of a fourth surface (200D), but is not limited thereto. For example, the first region (C1) of the third surface (200C) and / or the first region (D1) of the fourth surface (200D) may be formed by the second member (214). The first region (C1) of the third surface (200C) may extend from the first edge (E1) of the second surface (200B), and the first region (D1) of the fourth surface (200D) may extend from the second edge (E2) of the second surface (200B).

[0047] The second member (214) may form, but is not limited to, the first surface (200A) of the housing (210), the second region (C2) of the third surface (200C), and the second region (D2) of the fourth surface (200D). For example, the second region (C2) of the third surface (200C) and / or the second region (D2) of the fourth surface (200D) may be formed by the first member (212). The second region (C2) of the third surface (200C) may extend from the first edge (P1) of the first surface (200A) to the first region (C1). The second region (D2) of the fourth surface (200D) may extend from the second edge (P2) of the first surface (200A) to the first region (D1).

[0048] The first member (212) may include a conductive material such as metal. For example, at least a portion of the first member (212) may be formed of the conductive material. For example, but not limited to, a portion of the first member (212) formed of metal may be used as an antenna radiator for transmitting and receiving radio frequency (RF) signals. The second member (214) may include a non-conductive portion such as plastic and / or a conductive portion formed of a conductive material such as metal.

[0049] The wearable device (200) may be referred to as an electronic device or a wearable device. The second member (214) may be referred to as an inner ring in that it forms a first surface (200A) that comes into contact with the user's body, and the first member (212) may be referred to as an outer ring in that it forms a second surface (200B) opposite the first surface (200A). The first surface (200A) may be referred to as an inner surface of the wearable device (200) (or housing (210)) in that it comes into contact with the body of the user wearing the wearable device (200), and the second surface (200B) may be referred to as an outer surface of the wearable device (200) (or housing (210)) in that it is opposite the first surface (200A). The third side (200C) and the fourth side (200D), which surround the space between the first side (200A) and the second side (200B), may be referred to as the first side and the second side, respectively, of the wearable device (200) (or housing (210)). Although the wearable device (200) has been described as being worn on a finger, it is not limited thereto. For example, the wearable device (200) may take the form of a bracelet or anklet that can be worn on a wrist or ankle.

[0050] Referring to FIG. 2b, the wearable device (200) may include a printed circuit board (250) and a battery assembly (240).

[0051] The printed circuit board (250) and the battery assembly (240) may be positioned within the housing (210). For example, the printed circuit board (250) and the battery assembly (240) may be positioned between the first member (212) and the second member (214) of the housing (210). For example, the printed circuit board (250) and the battery assembly (240) may be supported by being surrounded by the first member (212) and / or the second member (214).

[0052] Each of the printed circuit board (250) and the battery assembly (240) may be provided in a form in which at least a portion is bent or bendable so as to correspond to the shape of the wearable device (200).

[0053] Various components of the wearable device (200) may be arranged on the printed circuit board (250). A processor (e.g., 421 of FIG. 4A), a memory (e.g., 431 of FIG. 4A), a communication circuit (e.g., 441 of FIG. 4A), a wireless charging circuit (e.g., 461 of FIG. 4A), and / or a battery (e.g., 471 of FIG. 4A) may be arranged on the printed circuit board (250).

[0054] The battery assembly (240) and the printed circuit board (250) may be designed to have a curved shape according to the curved shape of the inner side of the first member (212). The battery assembly (240) may be connected to the printed circuit board (250). For example, a corresponding connector of the battery assembly (240) may be coupled to a connector portion of the printed circuit board (250). The coupled printed circuit board (250) and the battery assembly (240) may be fixed to the inner side of the first member (212). Thereafter, the second member (214) may be formed through a molding process (e.g., epoxy molding). Thereafter, a surface treatment process such as polishing may be performed.

[0055] Fig. 3a is a drawing showing an open state of an electronic device. Fig. 3b is a drawing showing a closed state of an electronic device.

[0056] Referring to FIGS. 3A and 3B, the electronic device (300) may include a body (311) and a cover (312) rotatably coupled to the body (311). The wearable device (200) stored within the electronic device (300) may be a ring device.

[0057] The main body (311) may be configured to accommodate the wearable device (200). For example, the main body (311) may include a portion for accommodating at least a portion of the wearable device (200). For example, the main body (311) may include a protrusion (316) having a shape corresponding to at least a portion of the wearable device (200). For example, the protrusion (316) may be inserted into a hollow portion of the wearable device (200).

[0058] The electronic device (300) can supply power to the wearable device (200) via a wireless charging circuit (e.g., 460 of FIG. 4A). The electronic device (300) can supply power to the wearable device (200) based on the wearable device (200) being seated within the protrusion (316). The electronic device (300) can supply power to the wearable device (200) based on the proximity of the wearable device (200). The wearable device (200) can charge a battery (e.g., battery (471) of FIG. 4A) based on receiving the supplied power.

[0059] The electronic device (300) can operate between the open state of FIG. 3a and the closed state of FIG. 3b.

[0060] The electronic device (300) may include a hinge that comes into contact with one end of the body (311) and one end of the cover (312). For example, the open state of FIG. 3A may refer to a state in which the interior of the body (311) and / or the cover (312) of the electronic device (300) is exposed based on the hinge. The open state may be referred to as an open state. The electronic device (300) may identify the open state based on at least one sensor. The electronic device (300) may distinguish between a closed state and an open state based on identifying a change in magnetism using the sensor. The electronic device (300) may identify a state change of the electronic device (300) between a closed state and an open state based on identifying a change in magnetism using the sensor.

[0061] The closed state of FIG. 3B may refer to a state in which one side of the main body (311) and one side of the cover (312) are in contact. The closed state may be referred to as a closed state. The electronic device (300) may include at least one magnetic material on one side of the main body (311) and / or one side of the cover (312). The electronic device (300) may maintain the closed state based on the at least one magnetic material of the main body (311) and the cover (312). The electronic device (300) may identify contact between the main body (311) and the cover (312) through at least one sensor.

[0062] Figure 4a is a block diagram of a plurality of electronic devices. Figure 4b is a diagram illustrating data within the memories of a plurality of electronic devices.

[0063] Referring to FIG. 4A, the electronic device (101) may correspond to the electronic device (101) of FIG. 1. For example, the electronic device (101) may be a smartphone, a laptop computer, a desktop computer, or a tablet PC. The electronic device (101), in its relationship with the wearable device (200), may be referred to as a client device, a central device, a primary device, or a main device.

[0064] The electronic device (101) can pair (or establish a communication connection) with the wearable device (200) based on an advertising signal from the wearable device (200). The advertising packet may be a packet for transmitting information related to connection or account (e.g., pairing) to surrounding electronic devices using wireless communication (e.g., Bluetooth low energy (BLE, or LE) communication).

[0065] The electronic device (101) can receive information about the electronic device (300) from the wearable device (200) (e.g., the SoC (state of charge) of the battery (470) of the electronic device (300), the charging state of the battery (470)). The electronic device (101) can display the information about the electronic device (300) received from the wearable device (200) through the display module (160).

[0066] The electronic device (101) can receive a wireless connection request from the wearable device (200). For example, the electronic device (101) can receive a wireless connection request that the wearable device (200) transmits to the electronic device (101) based on an input received from the electronic device (300) (e.g., reception of information indicating a press on the input module (410)).

[0067] The electronic device (300) can supply power to the wearable device (200) to charge the battery (471) of the wearable device (200). For example, the electronic device (300) can be a cradle that supplies the power to the wearable device (200) when the wearable device (200) is placed in a space (e.g., a protrusion (316) of FIG. 3A) provided through the housing of the electronic device (300). For example, the electronic device (300) can include a space in the housing of the electronic device (300) that is provided to insert (or surround) the wearable device (200). For example, the electronic device (300) can include a space in the housing of the electronic device (300) that is provided to place (or be loaded) the wearable device (200). The electronic device (300) may be referred to as a charging dock or a charging pad. The electronic device (300) may include various electronic devices (e.g., a mobile phone) capable of wirelessly supplying power to the wearable device (200).

[0068] Referring to FIG. 4A, the electronic device (300) may include an input module (410), a processor (420), a memory (430), a communication circuit (440), a power management circuit (450), a wireless charging circuit (460), and a battery (470). The input module (410) may correspond to the input module (150) of FIG. 1. The processor (420) may correspond to the processor (120) of FIG. 1. The memory (430) may correspond to the memory (130) of FIG. 1. The communication circuit (440) may correspond to the communication module (190) of FIG. 1. The power management circuit (450) may correspond to the power management module (188) of FIG. 1. The wireless charging circuit (460) may correspond to the antenna module (197) of FIG. 1. The battery (470) can correspond to the battery (189) of Fig. 1.

[0069] The input module (410) may be a physical button. The input module (410) may generate an electrical signal according to a press (or push) on the physical button, and may generate an electrical signal according to a release of the physical button. The input module (410) may generate an electrical signal according to a change in the state of the physical button. For example, the input module (410) may generate an electrical signal (e.g., a release signal) when it switches from a first state (e.g., a press (or push)) to a second state (e.g., a release state). For example, the input module (410) may generate an electrical signal (e.g., a press signal) when it switches from a second state (e.g., a release state) to a first state (e.g., a press (or push)). For example, a press (or push) on the physical button may be a user applying pressure to the physical button in a specified direction (e.g., toward the inside of the electronic device (300). For example, a release for a physical button may be a cessation of pressure applied by the user in a specified direction (e.g., toward the inside of the electronic device (300)) to the physical button. However, the present invention is not limited thereto. For example, the input module (410) may be a touch sensor. The input module (410) may generate an electrical signal according to a contact (or touch) of a part of the user's body to the touch sensor, and may generate an electrical signal according to a release of the contact (or touch) of a part of the user's body to the touch sensor. For example, the input module (410) may generate an electrical signal (e.g., a release signal) when transitioning from a first state (e.g., a contact (or, touch)) to a second state (e.g., a contact (or, touch) release state). For example, the input module (410) may generate an electrical signal (e.g., a touch signal or a press signal) when transitioning from a second state (e.g., a contact (or, touch) release state) to a first state (e.g., a contact (or, touch) release state).

[0070] The processor (420) can execute instructions stored in the memory (430). Operations (or functions) defined by the instructions can be performed by the electronic device (300) based on the processor (420) executing the instructions.

[0071] The memory (430) can store a bootloader (e.g., the bootloader (491) of FIG. 4B) for booting the electronic device (300). Based on loading the firmware (e.g., the cradle binary (495) of FIG. 4B) directed by the bootloader (491) into the volatile memory, the electronic device (300) can be booted.

[0072] The memory (430) may store a cradle binary (495) including instructions defining operations (or functions) of the electronic device (300). For example, the cradle binary (495) may be software for basic operation and / or basic control of components included in the electronic device (300) (e.g., input module (410), processor (420), memory (430), communication circuit (440), power management circuit (450), and wireless charging circuit (460)). The cradle binary (495) stored in the memory (430) may be updated. For example, while the electronic device (300) is in communication connection with the wearable device (200), the electronic device (300) may obtain data (e.g., the cradle binary (485) of FIG. 4B) for updating the cradle binary (495) stored in the memory (430) from the wearable device (200). The cradle binary (495) stored in the memory (430) may be updated based on the data (e.g., the cradle binary (485)) for updating the cradle binary (495) obtained from the wearable device (200).

[0073] The communication circuit (440) can wirelessly connect the electronic device (300) and the wearable device (200). The communication circuit (440) can wirelessly connect the electronic device (300) and the wearable device (200) via a designated wireless connection protocol (e.g., near field communication (NFC)). However, the present invention is not limited thereto. For example, the communication circuit (440) can wirelessly connect the electronic device (300) and the wearable device (200) via another designated wireless connection protocol (e.g., Bluetooth low energy (BLE), Bluetooth, Zigbee).

[0074] The electronic device (300) may be electrically connected to the wearable device (200) via a wireless charging circuit (460). For example, the wireless charging circuit (460) may include an antenna capable of transmitting a wireless signal (or wireless power) to the wireless charging circuit (461) of the wearable device (200).

[0075] The electronic device (300) can supply power to the wearable device (200) through the wireless charging circuit (460) while being electrically connected to the wearable device (200) through the wireless charging circuit (460). The electronic device (300) can supply power to the wearable device (200) through the wireless charging circuit (460) while the wearable device (200) is adjacent to the electronic device (300). The electronic device (300) can supply power to the wearable device (200) through the wireless charging circuit (460) while the wearable device (200) is mounted within the electronic device (300).

[0076] The electronic device (300) can supply power to the wearable device (200) based on a designated wireless connection protocol (e.g., NFC) through the wireless charging circuit (460). However, the present invention is not limited thereto. For example, the electronic device (300) can wirelessly supply power to the wearable device (200) through the wireless charging circuit (460) based on a wireless power supply technique defined in a designated wireless charging protocol (e.g., a protocol defined by the Wireless Power Consortium (WPC), the Power Matters Alliance (PMA), or the Alliance for Wireless Power (A4WP)).

[0077] The electronic device (300) can exchange data with the wearable device (200) during a communication connection with the wearable device (200) (e.g., a communication connection via a communication circuit (440)).

[0078] Below, an operation of an electronic device (300) exchanging data with a wearable device (200) can be described.

[0079] The electronic device (300) can identify that the wearable device (200) is in proximity to the electronic device (300). The electronic device (300) can identify that the wearable device (200) is in proximity to the electronic device (300) in an active state according to a protocol for a specified wireless communication (e.g., NFC) (or in a state generating a magnetic field of a specified frequency band (e.g., 13.56 MHz)). The electronic device (300) can identify that the wearable device (200) is in proximity to the electronic device (300) based on identifying a change in a magnetic field caused by the proximity of the wearable device (200) in an active state according to a protocol for a specified wireless communication (e.g., NFC).

[0080] The electronic device (300) may transmit wireless power of a designated frequency band (e.g., 13.56 MHz) to the wearable device (200) through the wireless charging circuit (460) based on identifying that the wearable device (200) is in proximity to the electronic device (300). The electronic device (300) may transmit wireless power of a designated frequency band to the wearable device (200) through the wireless charging circuit (460) during a time period in which the electronic device (300) operates in a wireless charging mode. For example, the wireless charging mode may be a mode in which the electronic device (300) wirelessly transmits power to the wearable device (200) among a plurality of modes defined in a protocol for designated wireless communication (e.g., NFC). For example, the wireless charging mode may be a mode in which a designated power (e.g., 1 Watt) can be transmitted to the wearable device (200) through the wireless charging circuit (460). For example, in a wireless charging mode, the electronic device (300) can read data (e.g., 16 bytes) from the wearable device (200) and the electronic device (300) can write data (e.g., 4 bytes) to the wearable device (200) while the electronic device (300) wirelessly transmits power to the wearable device (200).

[0081] For example, multiple modes defined in a protocol for a given wireless communication (e.g., NFC) may include a card emulation mode (or card mode), a reader / writer mode, a peer-to-peer (P2P) mode, and / or a wireless charging mode. A card emulation mode may be a mode in which an electronic device operates as a contactless card (or NFC card) (or a passive state (e.g., a state in which the electronic device is provided with a magnetic field generated by another electronic device)). For example, a card emulation mode may be a mode in which an electronic device can communicate with a reader device (or polling device). For example, in a card emulation mode, tag information written to a designated area in a memory of the electronic device may be transmitted to the reader device (or polling device). A reader / writer mode may be a mode in which an electronic device can read an NFC tag and / or write data to an NFC tag. A P2P mode may be a mode in which an electronic device exchanges data while in contact with another electronic device. Among the multiple modes, modes other than the wireless charging mode (e.g., card emulation mode, reader / writer mode, and P2P mode) may be referred to as data transfer modes.

[0082] The electronic device (300) can transmit a power control message to the wearable device (200) while providing wireless power to the wearable device (200). The wearable device (200) can transmit information about a charging state (e.g., a state of charge (SoC)) to the electronic device (300) while the electronic device (300) provides wireless power to the wearable device (200).

[0083] The electronic device (300) can periodically switch between a wireless charging mode and a data transfer mode (e.g., card emulation mode, reader / writer mode, and P2P mode). For example, the electronic device (300) can periodically switch between a wireless charging mode and a reader / writer mode.

[0084] The electronic device (300) may periodically switch between the wireless charging mode and the data transmission mode based on the fulfillment of a specified condition. For example, the electronic device (300) may determine that the specified condition is fulfilled based on a change in the charge amount of the battery (470). For example, the electronic device (300) may determine that the specified condition is fulfilled based on a change in the charge state of the battery (470). For example, a change in the charge state of the battery (470) may include receiving power from an external electronic device (e.g., a travel adapter (TA)). For example, a change in the charge state of the battery (470) may include transmitting wireless power to the wearable device (200). For example, the electronic device (300) may determine that the specified condition is fulfilled based on a press (or push) of the input module (410). For example, the electronic device (300) may determine that a specified condition has been met based on the input module (410) being pressed (or pushed) for a specified period of time (e.g., 3 seconds or 7 seconds).

[0085] The electronic device (300) can read tag information from the wearable device (200) while providing wireless power to the wearable device (200). The electronic device (300) can read tag information from the wearable device (200) via a designated wireless connection protocol (e.g., NFC). The electronic device (300) can be referred to as a poller (or initiator) from the perspective that it reads tag information from the wearable device (200) via NFC. The wearable device (200) can be referred to as a listener (or target) from the perspective that the electronic device (300) reads tag information of the wearable device (200) via NFC.

[0086] The electronic device (300) can periodically read tag information from the wearable device (200) while providing wireless power to the wearable device (200). For example, the electronic device (300) can read tag information from the wearable device (200) at a time interval determined between 128 milliseconds and 32 seconds. For example, the electronic device (300) can read tag information from the wearable device (200) based on a period that gradually becomes longer. For example, the electronic device (300) can read tag information at an interval of 128 milliseconds when the wearable device (200) is in proximity to the electronic device (300), and can read tag information at an interval longer than 128 milliseconds after a specified time.

[0087] The tag information may be data recorded by the wearable device (200) in a designated area within the memory (431). The tag information may be data recorded in a designated area within the memory (431) of the wearable device (200) that can be read by the electronic device (300) while the wearable device (200) is in a passive state and the electronic device (300) is in an active state. The tag information may be data recorded in a designated area within the memory (431) of the wearable device (200) that can be read by the electronic device (300) while in a wireless charging mode in which the wearable device (200) wirelessly receives power from the electronic device (300). However, the present invention is not limited thereto. Tag information may be data recorded in a designated area within the memory (431) of the wearable device (200) that can be read by the electronic device (300) while the wearable device (200) operates in card emulation mode and the electronic device (300) operates in reader / writer mode. For example, the tag information may be data transmitted by the wearable device (200) to the electronic device (300) while the electronic device (300) and the wearable device (200) operate in P2P mode.

[0088] The tag information may be data having a length of 10 bytes. For example, the tag information may include information about the wearable device (200) (e.g., size, generation of the wearable device (200)) and status (e.g., charging status, temperature). For example, the tag information may include a request that the wearable device (200) makes to the electronic device (300). For example, the tag information may include information that causes the wearable device (200) to change the mode of the electronic device (300). For example, the tag information may include a value (e.g., on or 1) indicating a request for transmission of version information (499) of the firmware of the electronic device (300) of the wearable device (200) (e.g., Request cradle information bit). The version information (499) may be version information of the firmware (e.g., cradle binary (495)) being used by the wearable device (200).

[0089] The electronic device (300) may transmit a read request (or read command) (or polling command) to the wearable device (200) while operating in the wireless charging mode. The electronic device (300) may receive tag information transmitted by the wearable device (200) based on the read request (or read command) (or polling command) while operating in the wireless charging mode. The electronic device (300) may receive tag information transmitted by the wearable device (200) through load modulation while operating in the wireless charging mode. Load modulation may be a modulation method that causes a change in a magnetic field generated by the electronic device (300) by changing the load of the wireless charging circuit (461) (or antenna) according to tag information recorded in a designated area in the memory (431). The tag information may include a request for switching to a data transmission mode in the memory (431) that is communicable with the electronic device (300). The fact that the memory (431) can communicate with the electronic device (300) may mean that the data stored in the memory (431) is transmitted to the electronic device (300) by being load-modulated by the data stored in the memory (431).

[0090] The electronic device (300) can establish a data communication channel between the electronic device (300) and the wearable device (200) based on the identification of the information request of the electronic device (300) in the tag information. The electronic device (300) can establish a data communication channel between the electronic device (300) and the wearable device (200) based on a designated wireless connection protocol (e.g., NFC). However, the present invention is not limited thereto. The electronic device (300) can establish a data communication channel between the electronic device (300) and the wearable device (200) based on another designated wireless connection protocol (e.g., BLE, Bluetooth, Zigbee).

[0091] The electronic device (300) can switch to data transmission mode based on the identification of an information request of the electronic device (300) in the tag information. The information request may include a request for the state of charge (SoC) of the electronic device (300), whether it is charging (e.g., whether the electronic device (300) is receiving power from an external power source wired and / or wirelessly), a battery state (e.g., a health state of the battery (470) of the electronic device (300), and / or a temperature state), a state of the input module (410) (e.g., a first state of the input module (410) (e.g., a press (or push) state), or a second state of the input module (410) (e.g., a release state)), whether it is in an open state (e.g., an open state in FIG. 3A or a closed state in FIG. 3B), version information (499) of the firmware, and / or a size of the electronic device (300) (e.g., a size of the electronic device (300) corresponding to a size of the wearable device (200) (e.g., a size of a ring according to a finger thickness)) (or a size of the protrusion (316)). The information request may include a request for a field (e.g., phm (power hold mode), phm (power hold mode) release timer). The field (e.g., phm, phm release timer) may be utilized as a field for controlling charging according to temperature. The electronic device (300) may switch to a data transmission mode based on the identification of a request for transmission of version information (499) in the tag information. During the data transmission mode of the electronic device (300), wireless power transmission from the electronic device (300) to the wearable device (200) may be stopped. However, the present invention is not limited thereto. During the data transmission mode of the electronic device (300), wireless power transmission from the electronic device (300) to the wearable device (200) may be maintained. During data transmission mode of the electronic device (300), wireless power transmission to the wearable device (200) may be stopped based on an increase in the temperature of the electronic device (300) (or the temperature exceeds a specified threshold temperature).

[0092] The electronic device (300) can perform a handshaking operation by exchanging unique information (e.g., identification information) with the wearable device (200) during the data transfer mode. The electronic device (300) can perform a handshaking operation by transmitting unique information (e.g., identification information) of the electronic device (300) to the wearable device (200) during the data transfer mode and receiving unique information (e.g., identification information) of the wearable device (200) in response thereto. During the data transfer mode, the electronic device (300) can determine that a data communication channel has been established between the electronic device (300) and the wearable device (200) based on a designated wireless connection protocol (e.g., NFC) through the handshaking operation.

[0093] The electronic device (300) may transmit data (or an NDEF (NFC data exchange format) message) including version information (499) to the wearable device (200) during a data transmission mode through a communication channel (or an NFC-based communication channel) based on a designated frequency band (e.g., 13.56 MHz). The electronic device (300) may transmit data (or an NDEF message) including version information (499) to the wearable device (200) while the electronic device (300) generates a magnetic field during the data transmission mode. The data transmission mode may include a P2P mode, a card emulation mode, and / or a reader / writer mode.

[0094] The electronic device (300) can receive a response to data (or NDEF message) including version information (499) from the wearable device (200) while the wearable device (200) generates a magnetic field in data transmission mode.

[0095] The electronic device (300) may determine whether to maintain the data transmission mode based on the response. For example, the electronic device (300) may determine to maintain the data transmission mode based on the response indicating that the firmware of the electronic device (300) is to be updated. For example, the electronic device (300) may determine not to maintain the data transmission mode based on the response indicating that the firmware of the electronic device (300) is not to be updated.

[0096] The electronic device (300) may change the data transmission mode to another mode based on the determination not to maintain the data transmission mode. The electronic device (300) may change from the data transmission mode to the wireless charging mode based on the determination not to maintain the data transmission mode. The electronic device (300) may transmit wireless power to the wearable device (200) based on the determination not to maintain the data transmission mode.

[0097] The electronic device (300) may maintain the data transmission mode based on a determination to maintain the data transmission mode. The electronic device (300) may maintain the data transmission mode while receiving data (e.g., cradle binary (485)) for updating the firmware of the electronic device (300) from the wearable device (200). The electronic device (300) may receive data (e.g., cradle binary (485)) for updating the firmware of the electronic device (300) from the wearable device (200) while in the data transmission mode.

[0098] The electronic device (300) may receive data (e.g., cradle binary (485)) for updating the firmware of the electronic device (300) from the wearable device (200) based on the information of the electronic device (300) that the electronic device (300) transmits to the wearable device (200) during the data transmission mode, indicating designated information. For example, after the electronic device (300) transmits information indicating that it is receiving power from an external power source wiredly and / or wirelessly to the wearable device (200), the electronic device (300) may receive data (e.g., cradle binary (485)) for updating the firmware of the electronic device (300) from the wearable device (200). For example, after transmitting information indicating that the electronic device (300) is in a closed state to the wearable device (200), the electronic device (300) may receive data (e.g., cradle binary (485)) for updating the firmware of the electronic device (300) from the wearable device (200).

[0099] The electronic device (300) may not maintain the data transmission mode based on the completion of receiving data (e.g., cradle binary (485)) for updating the firmware of the electronic device (300) from the wearable device (200). For example, the electronic device (300) may change from the data transmission mode to the wireless charging mode based on the completion of receiving data (e.g., cradle binary (485)) for updating the firmware of the electronic device (300) from the wearable device (200).

[0100] The electronic device (300) can update the firmware of the electronic device (300) based on the completion of receiving the cradle binary (485) from the wearable device (200). For example, the electronic device (300) can update the cradle binary (495) to the cradle binary (485) based on the completion of receiving the cradle binary (485). However, the present invention is not limited thereto. For example, the electronic device (300) can store and maintain the cradle binary (485) and the cradle binary (495) received from the wearable device (200) together in the memory (430). For example, the electronic device (300) can store the cradle binary (485) in a designated area in the memory (430). The area where the cradle binary (485) is stored in the memory (430) can be distinguished from the area where the cradle binary (495) is stored in the memory (430). The electronic device (300) can operate using one of the cradle binary (485) and the cradle binary (495) while the cradle binary (485) and the cradle binary (495) are stored simultaneously in the memory (430). For example, the electronic device (300) can operate using the latest cradle binary among the cradle binary (485) and the cradle binary (495). The electronic device (300) can check the validity of the cradle binary (485) based on the newly received cradle binary (485) while the cradle binary (495) is stored in the memory (430). The electronic device (300) can operate using the cradle binary (485) among the cradle binary (485) and the cradle binary (495) based on the confirmation of the validity of the newly received cradle binary (485). Thereafter, a cradle binary that is newer than the cradle binary (485) received later from the wearable device (200) can be stored in an area where cradle binaries that are not in use are stored (e.g., an area where the cradle binary (495) is stored).

[0101] The electronic device (300) can wirelessly transmit power back to the wearable device (200) based on firmware updates based on the cradle binary (485).

[0102] The electronic device (300) may record version information (499) of the firmware of the electronic device (300) in a designated area within the memory (430) while supplying wireless power to the wearable device (200). Thereafter, the wearable device (200) may receive the version information (499) through a magnetic field generated during the reader / writer mode. Based on the version information (499), the wearable device (200) may determine to perform a firmware update and transmit a cradle binary (485) to the electronic device (300) through a data communication channel.

[0103] The electronic device (300) may read version information (489) recorded in a designated area in the memory (431) of the wearable device (200) while supplying wireless power to the wearable device (200). The electronic device (300) may determine that the firmware of the electronic device (300) requires an upgrade based on the fact that the firmware version information (489) represents more recent version information than the firmware version information (499). The electronic device (300) may determine that the firmware of the electronic device (300) does not require an upgrade based on the fact that the firmware version information (499) is the same as or represents more recent version information than the firmware version information (489). Based on the determination that the firmware of the electronic device (300) requires an upgrade, the electronic device (300) may establish a data communication channel with the wearable device (200). The electronic device (300) can request a cradle binary (485) from the wearable device (200) through an established data communication channel. The electronic device (300) can receive the cradle binary (485) from the wearable device (200) based on the request.

[0104] The wearable device (200) may correspond to the electronic device (102) of FIG. 1. In one embodiment, the wearable device (200) may be a wearable device worn on a part of the user's body (e.g., a finger, wrist, ear, or head).

[0105] The wearable device (200) may be a ring-type device worn on the user's finger, an earring-type device worn on the user's ear, an HMD (head mounted display) device worn on the user's face, and / or headphones, earbuds, or earphones worn on the user's ear.

[0106] The wearable device (200) may be referred to as a sink ASE, a server device, a peripheral device, a secondary device, or a sub device in relation to the electronic device (101).

[0107] Referring to FIG. 4A, the wearable device (200) may include a processor (421), a memory (431), a communication circuit (441), a wireless charging circuit (461), and a battery (471). The processor (421) may correspond to the processor (120) of FIG. 1. The memory (431) may correspond to the memory (130) of FIG. 1. The communication circuit (441) may correspond to the communication module (190) of FIG. 1. The wireless charging circuit (461) may correspond to the antenna module (197) of FIG. 1. The battery (471) may correspond to the battery (189) of FIG. 1.

[0108] The processor (421) can execute instructions stored in the memory (431). Operations (or functions) defined by the instructions can be performed by the wearable device (200) based on the processor (421) executing the instructions.

[0109] The communication circuit (441) can wirelessly communicate with the wearable device (200), the electronic device (101), and / or the electronic device (300). The communication circuit (441) can wirelessly communicate with the wearable device (200), the electronic device (101), and / or the electronic device (300) through a designated wireless connection protocol (e.g., NFC). However, the present invention is not limited thereto. For example, the communication circuit (441) can wirelessly communicate with the electronic device (101) and / or the electronic device (300) through another designated wireless connection protocol (e.g., BLE (Bluetooth low energy), Bluetooth, Zigbee).

[0110] The memory (431) can store a ring binary (481) and / or a cradle binary (485). The cradle binary (485) can be received from an external server (e.g., server (108) of FIG. 1). For example, the wearable device (200) can receive the cradle binary (485) from a server (108) indirectly connected via the electronic device (101). For example, the wearable device (200) can receive the cradle binary (485) from a server (108) directly connected.

[0111] The wearable device (200) can transmit version information (489) of the cradle binary (485) in the memory (431) to the electronic device (101) (or server (103)) through the communication circuit (441) to keep the cradle binary (485) in the memory (431) up to date. After transmitting the version information (489) of the cradle binary (485) to the electronic device (101) (or server (103)), the wearable device (200) can receive the latest cradle binary (485) from the electronic device (101) (or server (103)).

[0112] The wearable device (200) may be electrically connected to the electronic device (300) via a wireless charging circuit (461). For example, the wireless charging circuit (461) may include an antenna capable of receiving a wireless signal (or wireless power) from the wireless charging circuit (460) of the electronic device (300).

[0113] The wearable device (200) can obtain power from the electronic device (300) through the wireless charging circuit (461) while being electrically connected to the electronic device (300) through the wireless charging circuit (461). The wearable device (200) can receive power from the wearable device (200) through the wireless charging circuit (461) while the wearable device (200) is adjacent to the electronic device (300). The wearable device (200) can receive power from the wearable device (200) through the wireless charging circuit (461) while the wearable device (200) is mounted within the electronic device (300).

[0114] The wearable device (200) can obtain power from the electronic device (300) based on a designated wireless connection protocol (e.g., NFC) through the wireless charging circuit (461). The wearable device (200) can charge the battery (471) based on the power from the electronic device (300). However, the present invention is not limited thereto. For example, the wearable device (200) can obtain power wirelessly from the electronic device (300) through the communication circuit (441) based on a wireless power supply technique defined in a designated protocol (e.g., a protocol defined by the Power Matters Alliance (PMA), the Wireless Power Consortium (WPC), or the Alliance for Wireless Power (A4WP)).

[0115] The wearable device (200) can exchange data with the electronic device (300) during a communication connection with the electronic device (300) (e.g., a communication connection via a communication circuit (441)).

[0116] Below, an operation of a wearable device (200) exchanging data with an electronic device (300) can be described.

[0117] The wearable device (200) can identify that it is in proximity to the electronic device (300). The wearable device (200) can identify that it is in proximity to the electronic device (300) in a wireless charging mode. For example, the wearable device (200) can identify that it is in proximity to the electronic device (300) based on a wireless signal of a frequency band (e.g., 13.56 MHz) designated through the wireless charging circuit (461). For example, the wearable device (200) can identify that it is in proximity to the electronic device (300) based on wireless power of a frequency band (e.g., 13.56 MHz) designated through the wireless charging circuit (461). For example, the wireless charging mode may be one of multiple modes defined by a protocol for a given wireless communication (e.g., NFC).

[0118] The wearable device (200) can charge the battery (471) of the wearable device (200) based on wireless power of a designated frequency band (e.g., 13.56 MHz) received through the wireless charging circuit (461).

[0119] The wearable device (200) can identify whether to perform an operation (or procedure) to determine whether an update of the firmware of the electronic device (300) is required. The wearable device (200) can identify whether to perform an operation (or procedure) to determine whether an update of the firmware of the electronic device (300) is required based on identification of proximity to the electronic device (300).

[0120] For example, the wearable device (200) can identify whether to perform an operation to determine whether an update of the firmware of the electronic device (300) is necessary based on the cradle binary (485) stored in the memory (431).

[0121] The wearable device (200) can be identified as performing an operation to determine whether an update of the firmware of the electronic device (300) is required based on the update of the cradle binary (485) stored in the memory (431). The wearable device (200) can be identified as performing an operation to determine whether an update of the firmware of the electronic device (300) is required based on the update of the cradle binary (485) stored in the memory (431) after the update of the firmware of the electronic device (300). The wearable device (200) can be identified as not performing an operation to determine whether an update of the firmware of the electronic device (300) is required based on the fact that the cradle binary (485) stored in the memory (431) is not updated after the update of the firmware of the electronic device (300).

[0122] The wearable device (200) may record a value (e.g., off or 0) that does not indicate a transmission request (e.g., Request cradle information bit) in the tag information based on identifying that it is not performing an action to determine whether an update of the firmware of the electronic device (300) is required.

[0123] The wearable device (200) may change to a mode (e.g., data transfer mode) in which the electronic device (300) can read data recorded in the wearable device (200) based on the identification that the electronic device (300) performs an operation to determine whether an update of the firmware of the electronic device (300) is necessary. The data transfer mode may include a card emulation mode, a reader / writer mode, and / or a P2P mode.

[0124] The wearable device (200) may record tag information (or an NDEF message) in an area for a designated wireless communication protocol (e.g., NFC) within the memory (431) based on identification that the wearable device (200) performs an operation to determine whether an update of the firmware of the electronic device (300) is required. For example, the tag information may be data having a length of 10 bytes. For example, the tag information may include information of the wearable device (200) (e.g., the size, generation, and status (e.g., charging status, temperature) of the wearable device (200)).

[0125] For example, the tag information may include a request that the wearable device (200) makes to the electronic device (300). For example, the tag information may include information that causes the wearable device (200) to change the mode of the electronic device (300). For example, the tag information may include a value (e.g., on or 1) indicating a request for transmission of version information (499) of firmware of the electronic device (300) of the wearable device (200) (e.g., Request cradle information bit). For example, tag information including a value (e.g., on or 1) indicating a request for transmission of version information (499) (e.g., Request cradle information bit) may be referred to as a request for switching to a data transmission mode. For example, a value (e.g., on or 1) indicating a request for transmission of version information (499) (e.g., Request cradle information bit) in the tag information may be a request for firmware information of the electronic device (300).

[0126] The wearable device (200) can receive a read request (or read command) (or polling command) from the electronic device (300) after recording tag information in an area for a designated wireless communication protocol (e.g., NFC) within the memory (431).

[0127] The wearable device (200) may transmit tag information to the electronic device (300) based on receiving a read request (or read command) (or polling command). The wearable device (200) may transmit tag information through load modulation while operating in card emulation mode. However, the present invention is not limited thereto. For example, the wearable device (200) may transmit a value (e.g., on or 1) indicating a request for transmission of version information (499) (e.g., Request cradle information bit) to the electronic device (300) after switching to data transmission mode. For example, the wearable device (200) may establish a wireless connection with the wearable device (200) through another designated wireless connection protocol (e.g., BLE, Bluetooth, Zigbee). For example, the wearable device (200) may transmit a value (e.g., on, or 1) indicating a request for transmission of version information (499) to the electronic device (300) via another designated wireless connection protocol (e.g., Request cradle information bit).

[0128] A wearable device (200) can perform a handshaking operation by exchanging unique information (e.g., identification information) with an electronic device (300). The wearable device (200) can perform a handshaking operation by transmitting tag information through load modulation and then exchanging unique information (e.g., identification information) with the electronic device (300).

[0129] The wearable device (200) can perform a handshake by receiving unique information (e.g., identification information) of the electronic device (300) and transmitting the unique information (e.g., identification information) of the wearable device (200) to the electronic device (300) in response thereto. Through the handshake, the wearable device (200) can determine that a data communication channel between the electronic device (300) and the wearable device (200) has been established based on a designated wireless connection protocol (e.g., NFC).

[0130] The wearable device (200) can receive data (or NDEF message) including version information (499) from the electronic device (300) through a communication channel (or NFC-based communication channel) based on a designated frequency band (e.g., 13.56 MHz) during data transmission mode. The wearable device (200) can receive data (or NDEF message) including version information (499) from the electronic device (300) while the electronic device (300) generates a magnetic field during data transmission mode.

[0131] The wearable device (200) can determine whether an upgrade of the firmware of the electronic device (300) is required based on the version information (499) of the firmware. For example, the wearable device (200) can determine whether an upgrade of the firmware of the electronic device (300) is required based on comparing the version information (499) of the firmware with the version information (489) of the firmware stored in the memory (431) of the wearable device (200).

[0132] The wearable device (200) can determine that the firmware of the electronic device (300) needs to be upgraded based on the fact that the firmware version information (489) indicates more recent version information than the firmware version information (499). The wearable device (200) can determine that the firmware of the electronic device (300) does not need to be upgraded based on the fact that the firmware version information (499) is the same as the firmware version information (489) or indicates more recent version information.

[0133] Based on determining that the firmware of the electronic device (300) requires an upgrade, the wearable device (200) may transmit a cradle binary (485) (or a signal for updating the firmware of the electronic device (300) based on the version information (499)) to the electronic device (300). For example, the wearable device (200) may transmit a response indicating that the firmware of the electronic device (300) requires an upgrade through data (or an NDEF message) including the version information (499) based on determining that the firmware of the electronic device (300) requires an upgrade. For example, the wearable device (200) may transmit the cradle binary (485) to the electronic device (300) in a data transfer mode after transmitting the response indicating that the firmware of the electronic device (300) requires an upgrade. The data transfer mode may include P2P mode, card emulation mode, and / or reader / writer mode.

[0134] The wearable device (200) may disconnect the wireless communication connection with the electronic device (300) based on completion of transmitting the cradle binary (485) to the electronic device (300). For example, the wearable device (200) may, based on determining that the firmware of the electronic device (300) requires an upgrade, transmit a response indicating that the firmware of the electronic device (300) does not require an upgrade via data (or an NDEF message) including version information (499). For example, the wearable device (200) may, based on determining that the firmware of the electronic device (300) requires an upgrade, transmit a response requesting the disconnection of the wireless communication connection. For example, the wearable device (200) may disconnect the wireless communication connection with the electronic device (300) after transmitting the response. After the wireless communication connection is disconnected, the wearable device (200) can again receive wireless power from the electronic device (300).

[0135] As described above, the wearable device (200) and the electronic device (300) may be small electronic devices that are difficult to incorporate numerous hardware components due to limited internal space. Accordingly, a method for updating the firmware of the electronic device (300) may be required in situations where there are no physical terminals to physically connect them.

[0136] As described above, the wearable device (200) and the electronic device (300) can overcome the limitations of internal space by performing multiple functions (e.g., wireless charging, firmware update) through designated wireless communication (e.g., NFC).

[0137] Figure 5 is a flowchart illustrating an operation of a wearable device to determine whether to update the firmware of an electronic device.

[0138] Figure 5 can be explained with reference to Figures 1 to 4b.

[0139] Referring to FIG. 5, in operation 510, the wearable device (200) can identify proximity to the electronic device (300). The wearable device (200) can identify proximity to the electronic device (300) in a wireless charging mode. For example, the wearable device (200) can identify proximity to the electronic device (300) based on a wireless signal of a frequency band (e.g., 13.56 MHz) designated through the wireless charging circuit (461). For example, the wearable device (200) can identify proximity to the electronic device (300) based on wireless power of a frequency band (e.g., 13.56 MHz) designated through the wireless charging circuit (461). For example, the wireless charging mode can be one of a plurality of modes defined in a protocol for designated wireless communication (e.g., NFC).

[0140] For example, the wearable device (200) can charge the battery (471) of the wearable device (200) based on a wireless signal received through the wireless charging circuit (461). For example, the wearable device (200) can charge the battery (471) based on a wireless signal transmitted from the electronic device (300) based on the proximity to the electronic device (300) (or the placement on the electronic device (300).

[0141] In operation 520, the wearable device (200) may record data requesting version information. Based on identifying that the wearable device (200) is in proximity to the electronic device (300), the wearable device (200) may record tag information (or an NDEF message) in an area for a designated wireless communication protocol (e.g., NFC) within the memory (431). For example, the tag information may be data having a length of 10 bytes. For example, the tag information may include information about the wearable device (200) (e.g., size, generation of the wearable device (200)) and status (e.g., charging status, temperature). For example, the tag information may include a request that the wearable device (200) makes to the electronic device (300). For example, the tag information may include information that causes the wearable device (200) to change the mode of the electronic device (300). For example, the tag information may include a value (e.g., on or 1) indicating a request for transmission (e.g., Request cradle information bit) of version information (499) of firmware of the electronic device (300) of the wearable device (200).

[0142] After recording data requesting version information, the wearable device (200) may wait until the electronic device (300) establishes a data transmission channel with the wearable device (200).

[0143] As described with reference to operation 720 of FIG. 7, the electronic device (300) can read data recorded in the memory (431) of the wearable device (200) in the wireless charging mode. The electronic device (300) can read tag information recorded in the memory (431) of the wearable device (200) while providing wireless power to the wearable device (200). The electronic device (300) can read tag information from the wearable device (200) through a designated wireless connection protocol (e.g., NFC). For example, the electronic device (300) can read tag information including a value (e.g., on or 1) indicating that the wearable device (200) requests transmission of version information (499) of the firmware of the electronic device (300) (e.g., Request cradle information bit).

[0144] The electronic device (300) can determine whether a data channel needs to be created based on tag information. Based on the determination that a data channel needs to be created based on the tag information, the electronic device (300) can switch from wireless charging mode to data transmission mode. Based on the determination that a data channel needs to be created based on the tag information, the electronic device (300) can establish a data channel with the wearable device (200).

[0145] In operation 530, the wearable device (200) can determine whether a data channel has been created. After recording a value (e.g., on or 1) indicating a request for transmission of version information (499) (e.g., Request cradle information bit), the wearable device (200) can receive a request for exchanging unique information (e.g., identification information) from the electronic device (300). The wearable device (200) can receive a message from the electronic device (300) to initiate a handshake including unique information (e.g., identification information) of the electronic device (300). Based on receiving unique information (e.g., identification information) of the electronic device (300) from the electronic device (300), the wearable device (200) can transmit unique information (e.g., identification information) of the wearable device (200) to the electronic device (300).

[0146] The wearable device (200) can determine that a data channel has been created based on completing a handshake with the electronic device (300).

[0147] Based on determining that a data channel has been created, the wearable device (200) can perform operation 540. Based on determining that a data channel has not been created, the wearable device (200) can perform operation 530 again.

[0148] In operation 540, the wearable device (200) can receive a firmware version of the electronic device (300) through a data channel. The wearable device (200) can receive data (or an NDEF message) including version information (499) from the electronic device (300) through a communication channel (or a communication channel based on NFC) based on a designated frequency band (e.g., 13.56 MHz) during a data transmission mode. The wearable device (200) can receive data (or an NDEF message) including version information (499) from the electronic device (300) while the electronic device (300) generates a magnetic field during the data transmission mode.

[0149] In operation 550, the wearable device (200) may determine whether to update the firmware of the electronic device (300) based on the firmware version.

[0150] The wearable device (200) can determine that the firmware of the electronic device (300) needs to be upgraded based on the fact that the firmware version information (489) indicates more recent version information than the firmware version information (499). The wearable device (200) can determine that the firmware of the electronic device (300) does not need to be upgraded based on the fact that the firmware version information (499) is the same as the firmware version information (489) or indicates more recent version information.

[0151] Figure 6 is a flowchart illustrating an operation of a wearable device transmitting data for updating firmware of an electronic device.

[0152] FIG. 6 may be described with reference to FIGS. 1 to 4B. Among the operations of FIG. 6, operations 610 and 620 may be included in operation 550 of FIG. 5. Operation 610 of FIG. 6 may be performed after operation 540 of FIG. 5. For example, operation 610 of FIG. 6 may be performed based on the wearable device (200) receiving a response (e.g., firmware version) to a value (e.g., on or 1) indicating a request for transmission of version information (499) (e.g., Request cradle information bit) from the electronic device (300) through a data channel.

[0153] Referring to FIG. 6, in operation 610, the wearable device (200) can compare firmware versions. The wearable device (200) can compare the version information (499) of the firmware with the version information (489) of the firmware stored in the memory (431) of the wearable device (200).

[0154] In operation 620, the wearable device (200) may determine whether a firmware update is required. The wearable device (200) may determine that the firmware of the electronic device (300) requires an upgrade based on the fact that the firmware version information (489) indicates a newer version than the firmware version information (499). The wearable device (200) may determine that the firmware of the electronic device (300) does not require an upgrade based on the fact that the firmware version information (499) is the same as the firmware version information (489) or indicates a newer version.

[0155] In operation 630, the wearable device (200) may transmit a message to the electronic device (300) via a data channel to notify the electronic device (300) of a firmware update. For example, the wearable device (200) may transmit a response indicating that the firmware of the electronic device (300) requires an upgrade via data (or an NDEF message) including version information (499) based on determining that the firmware of the electronic device (300) requires an upgrade.

[0156] In operation 640, the wearable device (200) may transmit firmware data of the electronic device (300) via a data channel. For example, the wearable device (200) may transmit a cradle binary (485) to the electronic device (300) in a data transfer mode after transmitting a response indicating that the firmware of the electronic device (300) requires an upgrade.

[0157] In operation 650, the wearable device (200) may transmit a message through the data channel that causes the data channel to be released. For example, based on determining that the firmware of the electronic device (300) requires an upgrade, the wearable device (200) may transmit a response indicating that the firmware of the electronic device (300) does not require an upgrade through data (or an NDEF message) including version information (499).

[0158] Figure 7 is a flowchart illustrating an operation of an electronic device transmitting firmware version information of the electronic device.

[0159] Figure 7 can be explained with reference to Figures 1 to 4b.

[0160] Referring to FIG. 7, in operation 710, the electronic device (300) can identify proximity to the wearable device (200). The electronic device (300) can identify proximity to the wearable device (200) in an active state (or in a state generating a magnetic field of a specified frequency band (e.g., 13.56 MHz)) according to a protocol for a specified wireless communication. The electronic device (300) can identify proximity to the wearable device (200) based on identifying a change in a magnetic field caused by proximity to the wearable device (200) in an active state according to a protocol for a specified wireless communication (e.g., NFC).

[0161] In operation 720, the electronic device (300) can transmit wireless power to the wearable device (200). The electronic device (300) can transmit wireless power of a designated frequency band (e.g., 13.56 MHz) to the wearable device (200) through the wireless charging circuit (460) based on identifying that the wearable device (200) is in proximity to the electronic device (300). While operating in a wireless charging mode, the electronic device (300) can transmit wireless power of a designated frequency band to the wearable device (200) through the wireless charging circuit (460).

[0162] In operation 730, the electronic device (300) can read data recorded in the memory (431) of the wearable device (200). The electronic device (300) can read tag information recorded in the memory (431) of the wearable device (200) while providing wireless power to the wearable device (200). The electronic device (300) can read tag information from the wearable device (200) through a designated wireless connection protocol (e.g., NFC). However, the present invention is not limited thereto. The electronic device (300) can temporarily stop providing wireless power to the wearable device (200) in order to read the tag information recorded in the memory (431) of the wearable device (200). For example, the electronic device (300) can read tag information from the wearable device (200) via a designated wireless connection protocol (e.g., NFC) while temporarily stopping providing wireless power to the wearable device (200).

[0163] In operation 740, the electronic device (300) can determine whether a data channel needs to be created. The electronic device (300) can determine whether a data channel needs to be created based on tag information read from the wearable device (200). Based on the tag information including a value (e.g., on or 1) indicating a request for transmission of version information (499) of firmware of the electronic device (300) of the wearable device (200) (e.g., Request cradle information bit), the electronic device (300) can determine that a data channel needs to be created.

[0164] Based on determining that creation of a data channel is necessary, the electronic device (300) may perform operation 750. Based on determining that creation of a data channel is not necessary, the electronic device (300) may perform operation 720 again.

[0165] In operation 750, the electronic device (300) may establish a data channel. The electronic device (300) may switch from a wireless charging mode to a data transmission mode based on the identification of an information request from the electronic device (300) in the tag information. The electronic device (300) may establish a data communication channel between the electronic device (300) and the wearable device (200) based on the identification of an information request from the electronic device (300) in the tag information. The electronic device (300) may establish a data communication channel between the electronic device (300) and the wearable device (200) based on a designated wireless connection protocol (e.g., NFC). The electronic device (300) may establish a data communication channel between the electronic device (300) and the wearable device (200) based on a designated wireless connection protocol (e.g., NFC) in the data transmission mode.

[0166] The electronic device (300) can perform a handshaking operation by exchanging unique information (e.g., identification information) with the wearable device (200) during the data transfer mode. The electronic device (300) can perform a handshaking operation by transmitting unique information (e.g., identification information) of the electronic device (300) to the wearable device (200) during the data transfer mode and receiving unique information (e.g., identification information) of the wearable device (200) in response thereto. During the data transfer mode, the electronic device (300) can determine that a data communication channel has been established between the electronic device (300) and the wearable device (200) based on a designated wireless connection protocol (e.g., NFC) through the handshaking operation.

[0167] In operation 760, the electronic device (300) may transmit a firmware version of the electronic device (300) through a data channel. The electronic device (300) may transmit data (or an NDEF (NFC data exchange format) message) including version information (499) to the wearable device (200) through a communication channel (or an NFC-based communication channel) based on a designated frequency band (e.g., 13.56 MHz) during a data transmission mode. The electronic device (300) may transmit data (or an NDEF message) including version information (499) to the wearable device (200) during the data transmission mode. Data (or NDEF message) including version information (499) may include information about the state of charge (SoC) of the electronic device (300), whether it is charged (e.g., whether the electronic device (300) is receiving power from an external power source wired and / or wirelessly), the battery status (e.g., the health status of the battery (470) of the electronic device (300), and / or the temperature status), the status of the input module (410) (e.g., the first state of the input module (410) (e.g., press (or push)), or the second state of the input module (410) (e.g., release state)), whether it is in an open state (e.g., the open state of FIG. 3A, or the closed state of FIG. 3B), the version information (499) of the firmware, and / or the size of the electronic device (300) (e.g., the size of the electronic device (300) (or the size of the protrusion (316)) corresponding to the size of the wearable device (200) (e.g., the size of a ring according to the thickness of a finger)). May include. Data (or NDEF message) including version information (499) may include fields (e.g. phm, phm release timer). Fields (e.g. phm, phm release timer) may be utilized as fields for controlling charging according to temperature.

[0168] Figure 8 is a flowchart illustrating an operation of an electronic device performing a firmware update of the electronic device.

[0169] FIG. 8 can be described with reference to FIGS. 1 to 4b. The operations of FIG. 8 can be performed subsequent to operation 760 of FIG. 7.

[0170] Referring to FIG. 8, in operation 810, the electronic device (300) may receive data indicating whether the firmware of the electronic device (300) is updated from the wearable device (200) through a data channel. The electronic device (300) may receive a response to data (or NDEF message) including version information (499) from the wearable device (200) while the wearable device (200) generates a magnetic field in the data transmission mode. The response to the data (or NDEF message) including version information (499) may indicate whether the firmware of the electronic device (300) is updated.

[0171] At operation 820, the electronic device (300) can determine whether a firmware update is in progress.

[0172] The electronic device (300) may determine that a firmware update is in progress based on the response indicating that a firmware update of the electronic device (300) is required. The electronic device (300) may determine that a firmware update is not in progress based on the response indicating that a firmware update of the electronic device (300) is not required. The electronic device (300) may determine that a firmware update is not in progress based on the response indicating that a release of the data channel is requested.

[0173] The electronic device (300) may determine that a firmware update is not in progress based on whether the information of the electronic device (300) indicates specified information while in data transfer mode. For example, the electronic device (300) may determine that a firmware update is in progress based on whether the electronic device (300) is in a closed state.

[0174] At operation 820, based on determining that the firmware update is not in progress, the electronic device (300) may perform operation 830. At operation 820, based on determining that the firmware update is in progress, the electronic device (300) may perform operation 840.

[0175] In operation 830, the electronic device (300) may release the data channel. The electronic device (300) may change from data transmission mode to wireless charging mode.

[0176] In operation 840, the electronic device (300) may receive a cradle binary (485) from the wearable device (200) via a data channel. The electronic device (300) may maintain the data channel until the cradle binary (485) from the wearable device (200) is completely received. However, the present invention is not limited thereto. For example, the electronic device (300) may request to transmit firmware data by re-establishing a data communication channel with the wearable device (200) based on the incomplete reception of the cradle binary (485) via the data channel.

[0177] In operation 850, the electronic device (300) can update the firmware via the cradle binary (485). The electronic device (300) can update the firmware of the electronic device (300) based on the completion of receiving the cradle binary (485) from the wearable device (200). For example, the electronic device (300) can update the cradle binary (495) to the cradle binary (485) based on the completion of receiving the cradle binary (485).

[0178] The electronic device (300) can wirelessly transmit power back to the wearable device (200) based on firmware updates based on the cradle binary (485).

[0179] The technical problems to be achieved in the present disclosure are not limited to the technical problems mentioned above, and other technical problems not mentioned will be clearly understood by a person having ordinary knowledge in the technical field to which the present disclosure pertains.

[0180] As described above, the wearable device (200) may include a battery (471), an antenna (461), a communication circuit (441), at least one processor (421) including a processing circuit, and a memory (431) storing instructions and including one or more storage media. The instructions, when individually or collectively executed by the at least one processor (421), may cause the wearable device (200) to transmit data to the external electronic device (300) via the first wireless communication by adjusting the load of the antenna (461) based on data requesting establishment of a second wireless communication for data communication with the external electronic device (300). The instructions, when individually or collectively executed by the at least one processor (421), may cause the wearable device (200) to receive firmware information (499) of the external electronic device (300) from the external electronic device (300) via a second wireless communication established by transmitting the data to the external electronic device (300). The instructions, when individually or collectively executed by the at least one processor (421), may cause the wearable device (200) to transmit a signal to the external electronic device (300) indicating whether to update firmware based on the firmware information (499). The external electronic device (300) may supply power for charging the battery (471) of the wearable device (200).

[0181] The instructions, when individually or collectively executed by the at least one processor (421), may cause the wearable device (200) to determine whether to update the firmware of the external electronic device (300) based on the firmware information (499). The instructions, when individually or collectively executed by the at least one processor (421), may cause the wearable device (200) to transmit a response to the firmware information (499) to the external electronic device (300) through the second wireless communication, which causes the release of the second wireless communication based on the determination that the firmware of the external electronic device (300) is not to be updated. The above instructions, when individually or collectively executed by the at least one processor (421), may cause the wearable device (200) to transmit data (485) for updating the firmware of the external electronic device (300) to the external electronic device (300) via the second wireless communication based on a determination that the firmware of the external electronic device (300) is to be updated.

[0182] The instructions, when individually or collectively executed by the at least one processor (421), may cause the wearable device (200) to determine to update the firmware of the external electronic device (300) based on the firmware information (489) stored in the memory (431) indicating newer firmware information than the firmware information (499) received from the external electronic device (300). The instructions, when individually or collectively executed by the at least one processor (421), may cause the wearable device (200) to transmit the data (485) for the firmware update via the second wireless communication based on the determination to update the firmware of the external electronic device (300).

[0183] The first wireless communication and the second wireless communication may be wireless communication based on near field communication (NFC). During the first wireless communication, the communication circuit (441) may operate in card emulation mode. During the second wireless communication, the communication circuit (441) may operate in peer-to-peer (P2P) mode.

[0184] The first wireless communication may be wireless communication based on near field communication (NFC). The second wireless communication may be wireless communication based on a different protocol than NFC.

[0185] The first wireless communication may be wireless communication based on NFC (near field communication). The instructions, when individually or collectively executed by the at least one processor (421), may cause the wearable device (200) to receive power for charging the battery (471) of the wearable device (200) from the external electronic device (300) through the first wireless communication while the first wireless communication is maintained.

[0186] The above instructions, when individually or collectively executed by the at least one processor (421), may cause the wearable device (200) to stop receiving power via the first wireless communication based on the second wireless communication being established.

[0187] The instructions, when individually or collectively executed by the at least one processor (421), may cause the wearable device (200) to identify the proximity of the external electronic device (300) through the communication circuit (441). The instructions, when individually or collectively executed by the at least one processor (421), may cause the wearable device (200) to store the data requesting establishment of the second wireless communication in an area of ​​the memory (431) that causes adjustment of the load of the antenna (461) within the memory (431) based on identifying the proximity of the external electronic device (300) to the wearable device (200).

[0188] The above instructions, when individually or collectively executed by the at least one processor (421), may cause the wearable device (200) to identify that the external electronic device (300) is in proximity to the wearable device (200) based on a magnetic field generated by the external electronic device (300) for the first wireless communication.

[0189] The wearable device (200) may be a ring-type device worn on a user's finger. The external electronic device (300) may be a cradle including a housing that accommodates the wearable device (200).

[0190] The above instructions, when individually or collectively executed by the at least one processor (421), may cause the wearable device (200) to establish the second wireless communication through handshaking with the external electronic device (300) using the communication circuit (441).

[0191] As described above, the method can be performed in a wearable device (200) including a battery (471), a communication circuit (441), and a memory (431). The method can include an operation of transmitting data to the external electronic device (300) through a first wireless communication by adjusting a load of the antenna (461) based on data requesting establishment of a second wireless communication for data communication with the external electronic device (300). The method can include an operation of storing the data in a designated area within the memory (431), and then transmitting the data stored in the designated area to the external electronic device (300) by a magnetic field of the external electronic device (300) based on the first wireless communication. The method can include an operation of receiving firmware information (499) of the external electronic device (300) from the external electronic device (300) through the second wireless communication established by transmitting the data to the external electronic device (300). The above method may include an operation of transmitting a signal indicating whether to update the firmware to the external electronic device (300) based on the firmware information (499). The external electronic device (300) may supply power to charge the battery (471) of the wearable device (200).

[0192] The method may include an operation of determining whether to update the firmware of the external electronic device (300) based on the firmware information (499). The method may include an operation of transmitting, to the external electronic device (300), a response to the firmware information (499) that causes the second wireless communication to be released based on a determination that the firmware of the external electronic device (300) is not to be updated, through the second wireless communication. The method may include an operation of transmitting, to the external electronic device (300), data for updating the firmware of the external electronic device (300) through the second wireless communication, based on a determination that the firmware of the external electronic device (300) is to be updated.

[0193] The method may include an operation of determining that the firmware of the external electronic device (300) is to be updated based on the firmware information (489) stored in the memory (431) indicating newer firmware information than the firmware information (499) received from the external electronic device (300). The method may include an operation of transmitting the data (485) for the firmware update via the second wireless communication based on the determination that the firmware of the external electronic device (300) is to be updated.

[0194] The first wireless communication and the second wireless communication may be wireless communication based on near field communication (NFC). During the first wireless communication, the communication circuit (441) may operate in card emulation mode. During the second wireless communication, the communication circuit (441) may operate in peer-to-peer (P2P) mode.

[0195] The first wireless communication may be wireless communication based on near field communication (NFC). The method may include an operation of receiving power for charging the battery (471) of the wearable device (200) from the external electronic device (300) through the first wireless communication while the first wireless communication is maintained.

[0196] The method may include an operation of identifying proximity of the external electronic device (300) through the communication circuit (441). The method may include an operation of storing the data requesting establishment of the second wireless communication in a memory (431) area that causes adjustment of the load of the antenna (461) within the memory (431) based on identifying proximity of the external electronic device (300) to the wearable device (200).

[0197] The method may include an operation of identifying that the external electronic device (300) is in proximity to the wearable device (200) based on a magnetic field generated by the external electronic device (300) for the first wireless communication.

[0198] As described above, a non-transitory computer readable storage medium may include a program including instructions. The instructions, when individually or collectively executed by at least one processor (421) of a wearable device (200) including a battery (471), a communication circuit (441), and a memory (431), may cause the wearable device (200) to transmit data to the external electronic device (300) via the first wireless communication by adjusting the load of the antenna (461) based on data requesting establishment of a second wireless communication for data communication with the external electronic device (300). The instructions, when individually or collectively executed by the at least one processor (421), may cause the wearable device (200) to receive firmware information (499) of the external electronic device (300) from the external electronic device (300) via a second wireless communication established by transmitting the data to the external electronic device (300). The instructions, when individually or collectively executed by the at least one processor (421), may cause the wearable device (200) to transmit a signal to the external electronic device (300) indicating whether to update firmware based on the firmware information (499). The external electronic device (300) may supply power for charging the battery (471) of the wearable device (200).

[0199] The instructions, when individually or collectively executed by the at least one processor (421), may cause the wearable device (200) to determine whether to update the firmware of the external electronic device (300) based on the firmware information (499). The instructions, when individually or collectively executed by the at least one processor (421), may cause the wearable device (200) to transmit a response to the firmware information (499) to the external electronic device (300) through the second wireless communication, which causes the release of the second wireless communication based on the determination that the firmware of the external electronic device (300) is not to be updated. The above instructions, when individually or collectively executed by the at least one processor (421), may cause the wearable device (200) to transmit data for updating the firmware of the external electronic device (300) to the external electronic device (300) via the second wireless communication based on a determination that the firmware of the external electronic device (300) is to be updated.

[0200] As described above, the wearable device (200) may include a battery (471); an antenna (461); a communication circuit (441); at least one processor (421) including a processing circuit; and a memory (431) storing instructions and including one or more storage media. The instructions, when individually or collectively executed by the at least one processor (421), may cause the wearable device (200) to store data in the memory (431) such that the data for requesting a transition to a data transmission mode for data communication with the external electronic device (300) while in a charging mode in which the device receives power from the external electronic device (300) is read by the external electronic device (300). The above instructions, when executed individually or collectively by the at least one processor (421), may cause the wearable device (200) to: receive firmware information (499) of the external electronic device (300) from the external electronic device (300) during the data transfer mode switched from the charging mode, and, based on the firmware information (499), transmit a signal to the external electronic device (300) indicating whether to update the firmware.

[0201] The instructions, when individually or collectively executed by the at least one processor (421), may cause the wearable device (200) to determine whether to update the firmware of the external electronic device (300) based on the firmware information (499). The instructions, when individually or collectively executed by the at least one processor (421), may cause the wearable device (200) to transmit a response to the firmware information (499) to the external electronic device (300) that causes the second wireless communication to be released during the data transfer mode based on a determination that the firmware of the external electronic device (300) is not to be updated. The above instructions, when individually or collectively executed by the at least one processor (421), may cause the wearable device (200) to transmit data (485) for updating the firmware of the external electronic device (300) to the external electronic device (300) during the data transmission mode based on a determination that the firmware of the external electronic device (300) is to be updated.

[0202] The instructions, when individually or collectively executed by the at least one processor (421), may cause the wearable device (200) to determine to update the firmware of the external electronic device (300) based on the firmware information (489) stored in the memory (431) indicating newer firmware information than the firmware information (499) received from the external electronic device (300). The instructions, when individually or collectively executed by the at least one processor (421), may cause the wearable device (200) to transmit the data (485) for the firmware update during the data transmission mode based on the determination to update the firmware of the external electronic device (300).

[0203] During the charging mode and the data transmission mode, the wearable device can perform wireless communication based on NFC (near field communication) with the external electronic device. During the data transmission mode, the communication circuit (441) can operate in a P2P (peer-to-peer) mode.

[0204] During the charging mode, the wearable device can perform wireless communication with the external electronic device based on near field communication (NFC). During the data transfer mode, the wearable device can perform wireless communication with the external electronic device based on a different protocol distinct from the NFC.

[0205] During the charging mode, the wearable device may perform wireless communication based on NFC (near field communication) with the external electronic device. The instructions, when individually or collectively executed by the at least one processor (421), may cause the wearable device (200) to receive power for charging the battery (471) of the wearable device (200) from the external electronic device (300) through the NFC-based wireless communication during the charging mode.

[0206] The above instructions, when individually or collectively executed by the at least one processor (421), may cause the wearable device (200) to stop receiving power based on the NFC while in the data transfer mode switched from the charging mode.

[0207] The instructions, when individually or collectively executed by the at least one processor (421), may cause the wearable device (200) to identify the proximity of the external electronic device (300) through the communication circuit (441). The instructions, when individually or collectively executed by the at least one processor (421), may cause the wearable device (200) to store, in the memory (431), the data requesting a transition to the data transmission mode based on identifying the proximity of the external electronic device (300) to the wearable device (200).

[0208] The instructions, when individually or collectively executed by the at least one processor (421), may cause the wearable device (200) to identify that the external electronic device (300) is in proximity to the wearable device (200) based on a magnetic field generated by the external electronic device (300) during the charging mode.

[0209] The above instructions, when individually or collectively executed by the at least one processor (421), may cause the wearable device (200) to switch from the charging mode to the data transfer mode through handshaking with the external electronic device (300) using the communication circuit (441).

[0210] The method as described above can be performed in a wearable device (200) including a battery (471), a communication circuit (441), and a memory (431). The method can include an operation of storing data in the memory (431) so that, during a charging mode in which power is received from an external electronic device (300), the data for requesting a transition to a data transmission mode for data communication with the external electronic device (300) is read by the external electronic device (300). The method can include, during the data transmission mode switched from the charging mode: an operation of receiving firmware information (499) of the external electronic device (300) from the external electronic device (300), and an operation of transmitting a signal indicating whether to update firmware to the external electronic device (300) based on the firmware information (499).

[0211] The method may include an operation of determining whether to update the firmware of the external electronic device (300) based on the firmware information (499). The method may include an operation of transmitting, to the external electronic device (300), a response to the firmware information (499) that causes the second wireless communication to be released during the data transfer mode based on a determination that the firmware of the external electronic device (300) is not to be updated. The method may include an operation of transmitting, to the external electronic device (300), data (485) for updating the firmware of the external electronic device (300) during the data transfer mode based on a determination that the firmware of the external electronic device (300) is to be updated.

[0212] The method may include an operation of determining that the firmware of the external electronic device (300) is to be updated based on the firmware information (489) stored in the memory (431) indicating newer firmware information than the firmware information (499) received from the external electronic device (300). The method may include an operation of transmitting the data (485) for the firmware update during the data transmission mode based on the determination that the firmware of the external electronic device (300) is to be updated.

[0213] During the charging mode and the data transmission mode, the wearable device can perform wireless communication based on NFC (near field communication) with the external electronic device. During the data transmission mode, the communication circuit (441) can operate in a P2P (peer-to-peer) mode.

[0214] During the charging mode, the wearable device may perform wireless communication based on near field communication (NFC) with the external electronic device. The method may include an operation of receiving power for charging the battery (471) of the wearable device (200) from the external electronic device (300) through the NFC-based wireless communication during the charging mode.

[0215] The method may include an operation of identifying the proximity of the external electronic device (300) through the communication circuit (441). The method may include an operation of storing, in the memory (431), the data requesting a transition to the data transmission mode based on identifying the proximity of the external electronic device (300) to the wearable device (200).

[0216] The method may include an operation of identifying that the external electronic device (300) is in proximity to the wearable device (200) based on a magnetic field generated by the external electronic device (300) during the charging mode.

[0217] As described above, a non-transitory computer readable storage medium may include a program including instructions. The instructions, when individually or collectively executed by at least one processor (421) of a wearable device (200) including a battery (471), a communication circuit (441), and a memory (431), may cause the wearable device (200) to store data in the memory (431) such that data for requesting a transition to a data transmission mode for data communication with the external electronic device (300) while in a charging mode in which the wearable device (200) receives power from the external electronic device (300) is read by the external electronic device (300). The above instructions, when executed individually or collectively by the at least one processor (421), may cause the wearable device (200) to: receive firmware information (499) of the external electronic device (300) from the external electronic device (300) during the data transfer mode switched from the charging mode, and, based on the firmware information (499), transmit a signal to the external electronic device (300) indicating whether to update the firmware.

[0218] The instructions, when individually or collectively executed by the at least one processor (421), may cause the wearable device (200) to determine whether to update the firmware of the external electronic device (300) based on the firmware information (499). The instructions, when individually or collectively executed by the at least one processor (421), may cause the wearable device (200) to transmit a response to the firmware information (499) to the external electronic device (300) that causes the second wireless communication to be released during the data transfer mode based on a determination that the firmware of the external electronic device (300) is not to be updated. The above instructions, when individually or collectively executed by the at least one processor (421), may cause the wearable device (200) to transmit data (485) for updating the firmware of the external electronic device (300) to the external electronic device (300) during the data transmission mode based on a determination that the firmware of the external electronic device (300) is to be updated.

[0219] As described above, the wearable device (200) may include a battery (471), an antenna (461), a communication circuit (441), at least one processor (421) including a processing circuit, and a memory (431) storing instructions and including one or more storage media. The instructions, when individually or collectively executed by the at least one processor (421), may cause the wearable device (200) to store a request for switching to a data transmission mode in the memory capable of communicating with the external electronic device (300) while receiving power from the external electronic device. The instructions, when individually or collectively executed by the at least one processor (421), may cause the wearable device (200) to receive firmware information (499) of the external electronic device from the external electronic device. The instructions, when individually or collectively executed by the at least one processor (421), may cause the wearable device (200) to transmit a signal to the external electronic device for updating firmware based on the firmware information. The instructions, when individually or collectively executed by the at least one processor (421), may cause the wearable device (200) to receive power from the external electronic device after transmitting the signal for updating the firmware. The request for switching to the data transmission mode may include a request for the firmware information of the external electronic device.

[0220] The instructions, when individually or collectively executed by the at least one processor (421), may cause the wearable device (200) to determine, based on the firmware information, whether to transmit the signal for updating the firmware. The instructions, when individually or collectively executed by the at least one processor (421), may cause the wearable device (200) to transmit a response to the firmware information, which causes the external electronic device to transmit the power to the electronic device, based on the wearable device (200) determining not to transmit the signal for updating the firmware. The instructions, when individually or collectively executed by the at least one processor (421), may cause the wearable device (200) to transmit the signal for updating the firmware to the external electronic device, based on the wearable device determining not to transmit the signal for updating the firmware.

[0221] The instructions, when individually or collectively executed by the at least one processor (421), may cause the wearable device (200) to determine that the signal for updating the firmware is transmitted based on the firmware information (489) stored in the memory indicating newer firmware information than the firmware information received from the external electronic device. The instructions, when individually or collectively executed by the at least one processor (421), may cause the wearable device (200) to transmit the signal for updating the firmware based on the determination that the signal for updating the firmware is transmitted.

[0222] The instructions, when individually or collectively executed by the at least one processor (421), may cause the wearable device (200) to receive power using wireless communication based on NFC (near field communication) with the external electronic device. The instructions, when individually or collectively executed by the at least one processor (421), may cause the wearable device (200) to transmit the signal for updating the firmware using the communication circuit (441) operating in a P2P (peer-to-peer) mode.

[0223] The instructions, when individually or collectively executed by the at least one processor (421), may cause the wearable device (200) to receive the power using wireless communication based on NFC (near field communication) with the external electronic device. The instructions, when individually or collectively executed by the at least one processor (421), may cause the wearable device (200) to transmit the signal for updating the firmware using wireless communication based on a different protocol distinct from the NFC with the external electronic device.

[0224] The instructions, when individually or collectively executed by the at least one processor (421), may cause the wearable device (200) to receive the power using near field communication (NFC)-based wireless communication with the external electronic device. The instructions, when individually or collectively executed by the at least one processor (421), may cause the wearable device (200) to store the request for switching to the data transmission mode in the memory, such that the request for switching to the data transmission mode is read by the external electronic device (300) via the NFC-based wireless communication while receiving the power.

[0225] The above instructions, when individually or collectively executed by the at least one processor (421), may cause the wearable device (200) to stop receiving the power via the NFC-based wireless communication while receiving the firmware information and transmitting the signal for updating the firmware.

[0226] The instructions, when individually or collectively executed by the at least one processor (421), may cause the wearable device (200) to identify the proximity of the external electronic device (300) through the communication circuit (441). The instructions, when individually or collectively executed by the at least one processor (421), may cause the wearable device (200) to store a request for switching to a data transfer mode in the memory based on identifying the proximity of the external electronic device (300) to the wearable device (200).

[0227] The instructions, when individually or collectively executed by the at least one processor (421), may cause the wearable device (200) to identify that the external electronic device (300) is in proximity to the wearable device (200) based on a magnetic field generated by the external electronic device (300) while the wearable device (200) receives the power.

[0228] As described above, the method may be performed by a wearable device (200) including a battery (471), a communication circuit (441), and a memory (431). The method may include an operation of storing a request for switching to a data transmission mode in the memory capable of communicating with the external electronic device (300) while receiving power from the external electronic device. The method may include an operation of receiving, from the external electronic device, firmware information (499) of the external electronic device. The method may include an operation of transmitting, to the external electronic device, a signal for updating firmware based on the firmware information. The method may include an operation of receiving the power from the external electronic device after transmitting the signal for updating the firmware. The request for switching to the data transmission mode may include a request for the firmware information of the external electronic device.

[0229] The method may include an operation of determining whether to transmit the signal for updating the firmware based on the firmware information. The method may include an operation of transmitting a response to the firmware information to the external electronic device, which causes the external electronic device to transmit the power to the electronic device, based on a determination that the signal for updating the firmware is not to be transmitted. The method may include an operation of transmitting the signal for updating the firmware to the external electronic device, based on a determination that the signal for updating the firmware is to be transmitted.

[0230] The method may include an operation of determining that the signal for updating the firmware is to be transmitted based on the determination that the firmware information (489) stored in the memory represents newer firmware information than the firmware information received from the external electronic device. The method may include an operation of transmitting the signal for updating the firmware based on the determination that the signal for updating the firmware is to be transmitted.

[0231] The method may include an operation of receiving the power using wireless communication based on NFC (near field communication) with the external electronic device. The method may include an operation of transmitting the signal for updating the firmware using the communication circuit (441) operating in a P2P (peer-to-peer) mode.

[0232] The method may include receiving the power using wireless communication based on near field communication (NFC) with the external electronic device. The method may include transmitting the signal for updating the firmware using wireless communication based on a different protocol from NFC with the external electronic device.

[0233] The method may include an operation of receiving the power using wireless communication based on near field communication (NFC) with the external electronic device. The method may include an operation of storing the request for switching to the data transmission mode in the memory so that the request for switching to the data transmission mode is read by the external electronic device (300) through the wireless communication based on NFC while receiving the power. The method may include an operation of stopping the reception of the power through the wireless communication based on NFC while receiving the firmware information and transmitting the signal for updating the firmware.

[0234] The method may include an operation of identifying the proximity of the external electronic device (300) through the communication circuit (441). The method may include an operation of storing a request for switching to a data transmission mode in the memory based on identifying the proximity of the external electronic device (300) to the wearable device (200).

[0235] As described above, a non-transitory computer readable storage medium may include a program including instructions. The instructions, when individually or collectively executed by at least one processor (421) of a wearable device (200) including a battery (471), a communication circuit (441), and a memory (431), may cause the wearable device (200) to store a request for switching to a data transmission mode in the memory capable of communicating with the external electronic device (300) while receiving power from the external electronic device. The instructions, when individually or collectively executed by the at least one processor (421), may cause the wearable device (200) to receive firmware information (499) of the external electronic device from the external electronic device. The instructions, when individually or collectively executed by the at least one processor (421), may cause the wearable device (200) to transmit a signal to the external electronic device for updating firmware based on the firmware information. The instructions, when individually or collectively executed by the at least one processor (421), may cause the wearable device (200) to receive power from the external electronic device after transmitting the signal for updating the firmware. The request for switching to the data transmission mode may include a request for the firmware information of the external electronic device.

[0236] The instructions, when individually or collectively executed by the at least one processor (421), may cause the wearable device (200) to determine, based on the firmware information, whether to transmit the signal for updating the firmware. The instructions, when individually or collectively executed by the at least one processor (421), may cause the wearable device (200) to transmit a response to the firmware information, which causes the external electronic device to transmit the power to the electronic device, based on the wearable device (200) determining not to transmit the signal for updating the firmware. The instructions, when individually or collectively executed by the at least one processor (421), may cause the wearable device (200) to transmit the signal for updating the firmware to the external electronic device, based on the wearable device determining not to transmit the signal for updating the firmware.

[0237] 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 will be clearly understood by a person having ordinary skill in the art to which the present disclosure pertains.

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

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

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

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

[0242] According to one embodiment, the method according to various embodiments 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., a compact disc read-only memory (CD-ROM)) or 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.

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

Claims

1. In a wearable device (200), Battery (471); antenna (461); Communication circuit (441); At least one processor (421) comprising a processing circuit; and A wearable device (200) comprises a memory (431) storing instructions and including one or more storage media, wherein the instructions, when individually or collectively executed by the at least one processor (421), While receiving power from an external electronic device (300), a request for switching to a data transmission mode is stored in the memory, the request being communicable from the memory to the external electronic device, and the request for switching to the data transmission mode includes a request for firmware information related to firmware of the external electronic device. From the external electronic device, the firmware information (499) of the external electronic device is received, Transmitting a signal to the external electronic device to update the firmware of the external electronic device based on the firmware information, and After transmitting the signal for updating the firmware, causing the external electronic device to continue receiving power, Wearable devices.

2. In claim 1, The above instructions, when individually or collectively executed by the at least one processor (421), cause the wearable device (200) to: Based on the above firmware information, it is determined whether to transmit the signal for updating the firmware, Based on a determination that the signal for updating the firmware is not transmitted, transmitting a response to the firmware information to the external electronic device causing the external electronic device to transmit the power to the electronic device; Based on the determination that the signal for updating the firmware is transmitted, causing the signal for updating the firmware to be transmitted to the external electronic device, Wearable devices.

3. In claim 1 or 2, The above instructions, when individually or collectively executed by the at least one processor (421), cause the wearable device (200) to: Causing to determine that the signal for updating the firmware is transmitted based on the firmware information (489) stored in the memory indicating newer firmware information than the firmware information received from the external electronic device. Wearable devices.

4. In claim 1 or 2, The above instructions, when individually or collectively executed by the at least one processor (421), cause the wearable device (200) to: By using the above external electronic device and wireless communication based on NFC (near field communication), the power is received, Using the communication circuit (441) operating in P2P (peer-to-peer) mode, causing the signal for updating the firmware to be transmitted, Wearable devices.

5. In claim 1 or 2, The above instructions, when individually or collectively executed by the at least one processor (421), cause the wearable device (200) to: By using the above external electronic device and wireless communication based on NFC (near field communication), the power is received, Causing the external electronic device to transmit the signal for updating the firmware using wireless communication based on a different protocol than the NFC, Wearable devices.

6. In claim 1, The above instructions, when individually or collectively executed by the at least one processor (421), cause the wearable device (200) to: By using the above external electronic device and wireless communication based on NFC (near field communication), the power is received, While receiving the power, the request for switching to the data transmission mode is read by the external electronic device (300) through the NFC-based wireless communication, thereby causing the memory to store the request for switching to the data transmission mode. Wearable devices.

7. In claim 6, The above instructions, when individually or collectively executed by the at least one processor (421), cause the wearable device (200) to: Causing to stop receiving the power through the NFC-based wireless communication while receiving the firmware information and transmitting the signal for updating the firmware. Wearable devices.

8. In any one of claims 1 to 7, The above instructions, when individually or collectively executed by the at least one processor (421), cause the wearable device (200) to: Identifying the proximity of the external electronic device (300) through the above communication circuit (441), Causing the external electronic device (300) to store a request for switching to a data transmission mode in the memory based on identifying that the external electronic device (300) is in proximity to the wearable device (200). Wearable devices.

9. In claim 8, The above instructions, when individually or collectively executed by the at least one processor (421), cause the wearable device (200) to: Based on the magnetic field generated by the external electronic device (300), causing the external electronic device (300) to identify proximity to the wearable device (200), Wearable devices.

10. In any one of claims 1 to 9, The above wearable device (200) is a ring worn on the user's finger, The external electronic device (300) is a cradle including a housing that stores the wearable device (200). Wearable devices.

11. In a method of operating a wearable device (200) including a battery (471), a communication circuit (441), and a memory (431), An operation of storing a request for switching to a data transmission mode in the memory while receiving power from an external electronic device (300), the request being communicable from the memory to the external electronic device, and the request for switching to the data transmission mode including a request for firmware information related to firmware of the external electronic device, An operation of receiving the firmware information (499) of the external electronic device from the external electronic device; An operation of transmitting a signal to the external electronic device to update the firmware of the external electronic device based on the firmware information, and An operation including continuing to receive power from the external electronic device after transmitting the signal for updating the firmware. method.

12. In claim 11, An operation of determining whether to transmit the signal for updating the firmware based on the above firmware information; An operation of transmitting a response to the firmware information to the external electronic device, which causes the external electronic device to transmit the power to the electronic device, based on a determination that the signal for updating the firmware is not transmitted; and An operation of transmitting the signal for updating the firmware to the external electronic device based on a determination that the signal for updating the firmware is transmitted. method.

13. In claim 11 or 12, An operation of determining that the signal for updating the firmware is transmitted based on the firmware information (489) stored in the memory indicates newer firmware information than the firmware information received from an external electronic device. method.

14. In claim 11 or 12, An operation of receiving the power using wireless communication based on NFC (near field communication) with the external electronic device, and An operation of transmitting the signal for updating the firmware using the communication circuit (441) operating in P2P (peer-to-peer) mode. method.

15. In computer programs, When executed by at least one processor (421) of a wearable device (200) including a battery (471), a communication circuit (441), and a memory (431), the wearable device (200), While receiving power from an external electronic device (300), a request for switching to a data transmission mode is stored in the memory, the request being communicable from the memory to the external electronic device, and the request for switching to the data transmission mode includes a request for firmware information related to firmware of the external electronic device. From the external electronic device, the firmware information (499) of the external electronic device is received, Transmitting a signal to the external electronic device to update the firmware of the external electronic device based on the firmware information, and After transmitting the signal for updating the firmware, causing the external electronic device to continue receiving power, Computer program.

Images