Electronic device and method for managing internet-of-things device

Abstract

This electronic device may comprise: a communication circuit; a memory for storing instructions; a wireless charging circuit; and a processor. The instructions, when executed by the processor, may instruct the electronic device to: receive a wireless signal including a device ID from a hub device through the wireless charging circuit while the electronic device is being charged from the hub device through the wireless charging circuit; transmit the device ID and location information of the hub device to a server through the communication circuit, wherein the location information of the hub device includes location information of the electronic device; receive information about a connection state between the hub device and the server from the server through the communication circuit; and display, on the basis of the information about the connection state, information related to a location change of the hub device and information related to an online / offline status of at least one of the hub device or one or more IoT devices operatively coupled to the hub device through a display.

Description

Electronic devices and methods for managing Internet of Things devices

[0001] Embodiments of the present disclosure relate to electronic devices and methods for managing Internet of Things (IoT) devices.

[0002] The services and additional features provided through user terminals, such as smartphones, are gradually expanding in response to technological advancements and user demands. To enhance the utility of these electronic devices and satisfy the diverse needs of users, telecommunications service providers and electronic device manufacturers are competitively developing electronic devices that offer a variety of functions and services. Consequently, the functions provided through these devices are also becoming increasingly sophisticated.

[0003] IoT (Internet of Things) technology can provide intelligent Internet technology services that create new value in human life by collecting and analyzing data generated by devices. Through the convergence and integration of existing Internet technologies with various industries, IoT technology can be applied to areas such as smart homes, smart buildings, smart cities, smart cars, and smart appliances.

[0004] Homes, offices, and lodging facilities are equipped with a variety of home appliances for the convenience of users. Accordingly, various services are being proposed that utilize IoT technology to facilitate the operation and control of these appliances. For example, users can control various controlled devices (e.g., IoT-enabled home appliances or small electronic devices) that make up a home network using personal electronic devices (e.g., smartphones) or hubs. Users may desire a wider range of services and a more convenient user experience for controlling these controlled devices. Accordingly, there is a growing demand for the development of various technologies that manage controlled devices in a way that reflects user intent.

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

[0006] Embodiments of the present disclosure may provide an electronic device and method for controlling controlled devices (e.g., IoT devices) through a hub device.

[0007] Embodiments of the present disclosure may provide an electronic device and method for managing movement of a hub device.

[0008] Embodiments of the present disclosure can provide an electronic device and method for managing the status of controlled devices according to a change in the position of a hub device.

[0009] 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 skill in the technical field to which the present invention pertains from the description below.

[0010] An electronic device according to one embodiment of the present disclosure may include a communication circuit, a memory storing instructions, a wireless charging circuit, and a processor connected to the communication circuit, the memory, and the wireless charging circuit. The instructions, when executed by the processor, may cause the electronic device to receive a wireless signal including a device identifier (ID) from a hub device through the wireless charging circuit while the electronic device is being charged from the hub device through the wireless charging circuit. The instructions, when executed by the processor, may cause the electronic device to transmit the device ID and location information of the hub device to a server through the communication circuit, wherein the location information of the hub device may include location information of the electronic device. The instructions, when executed by the processor, may cause the electronic device to receive information on a connection status between the hub device and the server from the server through the communication circuit. The above instructions, when executed by the processor, may cause the electronic device to display, through a display, information related to a change in location of the hub device and information related to online / offline status of at least one of the hub device or one or more IoT devices operatively coupled with the hub device, based on the information about the connection status.

[0011] A hub device according to one embodiment of the present disclosure may include a communication circuit, a memory storing instructions, a wireless charging circuit, and a processor connected to the communication circuit, the memory, and the wireless charging circuit. The instructions, when executed by the processor, may cause the hub device to detect, through the communication circuit, that the hub device is in an offline state where the connection with the server is lost after onboarding to a server. The instructions, when executed by the processor, may cause the hub device to transmit, through the wireless charging circuit, a first wireless signal including a user ID acquired through the onboarding to the electronic device in the offline state based on detecting that the electronic device is being charged using the wireless charging function of the hub device. The instructions, when executed by the processor, may cause the hub device to receive, through the wireless charging circuit, a second wireless signal including a device ID request from the electronic device. The instructions, when executed by the processor, may cause the hub device to transmit, through the wireless charging circuit, a third wireless signal including a device ID of the hub device to the electronic device. The instructions, when executed by the processor, may cause the hub device to transmit a fourth wireless signal including information of the user input to the electronic device through the wireless charging circuit based on identifying that the electronic device receives a user input through an input module of the hub device in the offline state while the electronic device is being charged from the hub device through the wireless charging circuit of the hub device.

[0012] A method of operating an electronic device according to one embodiment of the present disclosure may include receiving a wireless signal including a device identifier (ID) from a hub device through a wireless charging circuit while the electronic device is being charged from the hub device through the wireless charging circuit. The method may include transmitting the device ID and location information of the hub device to a server through a communication circuit, and the location information of the hub device may include location information of the electronic device. The method may include receiving information on a connection status between the hub device and the server from the server through the communication circuit. The method may include displaying, based on the information on the connection status, information related to a change in the location of the hub device and information related to online / offline status of at least one of the hub device or one or more IoT devices operatively coupled with the hub device through a display.

[0013] A method for operating a hub device according to one embodiment of the present disclosure may include detecting, through a communication circuit, that the hub device is in an offline state where it is disconnected from the server after onboarding to a server. The method may include transmitting, to the electronic device through a wireless charging circuit, a first wireless signal including a user ID acquired through the onboarding in the offline state, based on detecting that the electronic device is charging using a wireless charging function of the hub device. The method may include receiving, from the electronic device through the wireless charging circuit, a second wireless signal including a device ID request. The method may include transmitting, to the electronic device through the wireless charging circuit, a third wireless signal including a device ID of the hub device. The method may include transmitting, to the electronic device through the wireless charging circuit, a fourth wireless signal including information of the user input, based on identifying that the electronic device receives a user input through an input module of the hub device in the offline state while being charged from the hub device through the wireless charging circuit of the hub device.

[0014] A non-transitory computer-readable storage medium storing one or more programs according to one embodiment of the present disclosure may include instructions that, when executed by at least one processor of an electronic device, cause the electronic device to receive a wireless signal including a device ID from a hub device through a wireless charging circuit while the electronic device is being charged from the hub device through the wireless charging circuit, transmit the device ID and location information of the hub device to a server through a communication circuit, the location information of the hub device including the location information of the electronic device, receive information on a connection status between the hub device and the server from the server through the communication circuit, and display information related to a change in the location of the hub device and information related to an online / offline status of at least one of the hub device or one or more IoT devices operatively coupled with the hub device through a display based on the information on the connection status.

[0015] The above and other aspects, features and advantages of specific embodiments of the present disclosure will become more apparent from the following description taken in conjunction with the accompanying drawings.

[0016] FIG. 1 illustrates an IoT (internet of things) system according to various embodiments.

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

[0018] FIG. 3A is a diagram illustrating a network including controlled devices according to one embodiment of the present disclosure.

[0019] FIG. 3b is a drawing for explaining movement of a hub device according to one embodiment of the present disclosure.

[0020] FIG. 4A is a block diagram illustrating the configuration of an electronic device performing IoT control according to one embodiment of the present disclosure.

[0021] FIG. 4b is a block diagram illustrating the configuration of a hub device according to one embodiment of the present disclosure.

[0022] FIG. 5 is a flowchart illustrating the operation of an electronic device for notifying movement of a hub device according to one embodiment of the present disclosure.

[0023] FIG. 6 is a flowchart illustrating the operation of an electronic device that manages automation routines according to movement of a hub device according to one embodiment of the present disclosure.

[0024] FIG. 7 is a sequence diagram illustrating a procedure for notifying movement of a hub device according to one embodiment of the present disclosure.

[0025] FIG. 8 illustrates a sequence diagram illustrating a procedure for executing an automation routine in an offline state of a hub device according to one embodiment of the present disclosure.

[0026] FIG. 9 illustrates a sequence diagram illustrating a procedure for keeping a hub device online through tethering according to one embodiment of the present disclosure.

[0027] FIG. 10 illustrates a sequence diagram illustrating a procedure for notifying a change in an automation routine in a hub device according to one embodiment of the present disclosure.

[0028] FIG. 11 illustrates a sequence diagram illustrating a procedure for activating or deactivating a location-specific automation routine according to one embodiment of the present disclosure.

[0029] FIG. 12 illustrates a sequence diagram illustrating a procedure for setting up a location-specific automation routine according to one embodiment of the present disclosure.

[0030] FIGS. 13a, 13b, 13c, and 13d illustrate examples of a user interface for notifying offline status of a hub device according to one embodiment of the present disclosure.

[0031] FIGS. 14A, 14B, 14C, and 14D illustrate examples of a user interface for notifying deactivation of a location-specific automation routine according to one embodiment of the present disclosure.

[0032] FIG. 1 illustrates an Internet of Things (IoT) system (100) according to various embodiments. Meanwhile, at least some of the components of FIG. 1 may be omitted, and the system may be implemented to include additional components not shown.

[0033] Referring to FIG. 1, an IoT system (100) according to one embodiment includes a plurality of electronic devices connectable to a data network (116 or 146). For example, the IoT system (100) may include at least one of a first IoT server (110), a first node (120), a voice assistance server (130), a second IoT server (140), a second node (150), or devices (121, 122, 123, 124, 125, 136, 137, 151, 152, 153).

[0034] According to one embodiment, the first IoT server (110) may include at least one of a communication interface (111), a processor (112), or a storage (113). The second IoT server (140) may include at least one of a communication interface (141), a processor (142), or a storage (143). The “IoT server” in this document may remotely control and / or monitor one or more devices (e.g., devices (121, 122, 123, 124, 125, 151, 152, 153)) via a relay device (e.g., the first node (120) or the second node (150)) or directly without a relay device, for example, based on a data network (e.g., the data network (116) or the data network (146)). Here, a "device" is not limited to a sensor, home appliance, office electronic device, or process-performing device that is deployed (or located) within a local environment, such as a home, office, factory, building, external branch, or other type of site. A device that receives a control command and performs an action corresponding to the control command may be referred to as a "target device." An IoT server may also be referred to as a central server, as it selects a target device from among multiple devices and provides control commands.

[0035] According to one embodiment, the first IoT server (110) may communicate with devices (121, 122, 123) via a data network (116). The data network (116) may mean a network for long-distance communication, such as the Internet or a computer network (e.g., a LAN or WAN), or may include a cellular network.

[0036] According to one embodiment, the first IoT server (110) may be connected to a data network (116) via a communication interface (111). The communication interface (111) may include a communication device (or communication module) for supporting communication of the data network (116), and may be integrated into a single component (e.g., a single chip) or implemented as a plurality of separate components (e.g., multiple chips). The first IoT server (110) may communicate with devices (121, 122, 123) via a first node (120). The first node (120) may receive data from the first IoT server (110) via the data network (116) and transmit the received data to at least some of the devices (121, 122, 123). Alternatively, the first node (120) may receive data from at least some of the devices (121, 122, 123) and transmit the received data to the first IoT server (110) via the data network (116). The first node (120) may function as a bridge between the data network (116) and the devices (121, 122, 123). Meanwhile, although FIG. 1 illustrates one first node (120), this is merely exemplary and there is no limitation on the number.

[0037] A "node" in this document may be an edge computing system or a hub device. According to one embodiment, the first node (120) supports wired and / or wireless communication with the data network (116), and may also support wired and / or wireless communication with devices (121, 122, 123). For example, the first node (120) may be connected to the devices (121, 122, 123) via a short-range communication network such as at least one of Bluetooth, Wi-Fi, Wi-Fi direct, Z-wave, Zig-bee, INSETEON, X10, or IrDA (infrared data association), but there is no limitation on the type of communication. The first node (120) may be deployed (or located) within an environment such as, for example, a home, an office, a factory, a building, an external branch, or other types of sites. Accordingly, the devices (121, 122, 123) may be monitored and / or controlled by services provided by the first IoT server (110), and the devices (121, 122, 123) may not be required to have the capability of full network communication (e.g., Internet communication) for direct connection to the first IoT server (110). The devices (121, 122, 123) are illustrated as being implemented as electronic devices within a home environment, such as light switches, proximity sensors, temperature sensors, etc., but this is by way of example only and is not limiting.

[0038] According to one embodiment, the first IoT server (110) may support direct communication with devices (124, 125). Here, "direct communication" may mean communication that does not pass through an intermediary device, such as the first node (120), for example, communication via a cellular communication network and / or a data network.

[0039] According to one embodiment, the first IoT server (110) may transmit a control command to at least some of the devices (121, 122, 123, 124, 125). Here, the “control command” may mean data that causes a controllable device to perform a specific operation, and the specific operation is an operation performed by the device, and may include outputting information, sensing information, reporting information, and managing (e.g., deleting or creating) information, and there is no limitation on its type. For example, the processor (112) may obtain information (or a request) for generating a control command from an external source (e.g., a voice assistant server (130), the second IoT server (140), an external system (160), or at least some of the devices (121, 122, 123, 124, 125)), and generate the control command based on the obtained information. Alternatively, the processor (112) may generate a control command based on whether the monitoring results of at least some of the devices (121, 122, 123, 124, 125) satisfy a specified condition. The processor (112) may control the communication interface (111) to transmit the control command to the target device.

[0040] According to one embodiment, the processor (112), or the processor (132), or the processor (142) may be implemented as a combination of one or more of a general-purpose processor such as a central processing unit (CPU), a digital signal processor (DSP), an application processor (AP), or a communication processor (CP), a graphics-only processor such as a graphical processing unit (GPU), a vision processing unit (VPU), or an artificial intelligence-only processor such as a neural processing unit (NPU). The above-described processing units are merely exemplary, and those skilled in the art will understand that the processor (112) is not limited to any computational means that can execute instructions stored in the memory (113), for example, and output the executed results.

[0041] According to one embodiment, the processor (112) may configure a web-based interface based on the API (114) or expose resources managed by the first IoT server (110) to the outside. The web-based interface may, for example, support communication between the first IoT server (110) and an external web service. The processor (112) may also allow, for example, an external system (160) to control and / or access the devices (121, 122, 123). The external system (160) may be an independent system that is not associated with or is not a part of the system (100), for example. The external system (160) may be, for example, an external server or a website. However, security is required for access to the devices (121, 122, 123) or the resources of the first IoT server (110) from the external system (160). According to one embodiment, the processor (112) may externally expose an API endpoint (e.g., a URL (universal resource locator)) based on the API (114) of the automation application. As described above, the first IoT server (110) may transmit a control command to a target device among the devices (121, 122, 123). Meanwhile, the description of the communication interface (141), the processor (142), the API (144) of the storage (143), and the database (145) of the second IoT server (140) may be substantially the same as the description of the communication interface (111), the processor (112), the API (114) of the storage (113), and the database (115) of the first IoT server (110). In addition, the description of the second node (150) may be substantially the same as the description of the first node (120). The second IoT server (140) can transmit control commands to a target device among the devices (151, 152, 153).The first IoT server (110) and the second IoT server (140) may be operated by the same service provider in one embodiment, but may be operated by different service providers in another embodiment.

[0042] According to one embodiment, the voice assistant server (130) can transmit and receive data with the first IoT server (110) via a data network (116). The voice assistant server (130) according to one embodiment can include at least one of a communication interface (131), a processor (132), or a storage (133). The communication interface (131) can communicate with a smart phone (136) or an AI speaker (137) via a data network (not shown) and / or a cellular network (not shown). The smart phone (136) or the AI ​​speaker (137) can include a microphone, acquire a user voice, convert it into a voice signal, and transmit the voice signal to the voice assistant server (130). The processor (132) can receive a voice signal from the smart phone (136) or the AI ​​speaker (137) via the communication interface (131). The processor (132) can process the received voice signal based on the stored model (134). The processor (132) can generate (or confirm) a control command using the processing result based on information stored in the database (135).According to one embodiment, the storage (113, 133, 143) may include a non-transitory storage medium of at least one type among a flash memory type, a hard disk type, a multimedia card micro type, a card type memory (e.g., SD or XD memory, etc.), a random access memory (RAM), a static random access memory (SRAM), a read-only memory (ROM), an electrically erasable programmable read-only memory (EEPROM), a programmable read-only memory (PROM), a magnetic memory, a magnetic disk, or an optical disk, and the type thereof is not limited.

[0043] In various embodiments, at least one device (e.g., device (124)) communicating with the first IoT server (110) may be a smartphone (e.g., electronic device (201) of FIG. 2) within a network environment.

[0044] FIG. 2 is a block diagram of an electronic device (201) within a network environment (200) according to various embodiments.

[0045] Referring to FIG. 2, in a network environment (200), an electronic device (201) may communicate with an electronic device (202) via a first network (298) (e.g., a short-range wireless communication network), or may communicate with at least one of an electronic device (204) or a server (208) via a second network (299) (e.g., a long-range wireless communication network). According to one embodiment, the electronic device (201) may communicate with the electronic device (204) via the server (208). According to one embodiment, the electronic device (201) may include a processor (220), a memory (230), an input module (250), an audio output module (255), a display module (260), an audio module (270), a sensor module (276), an interface (277), a connection terminal (278), a haptic module (279), a camera module (280), a power management module (288), a battery (289), a communication module (290), a subscriber identification module (296), or an antenna module (297). In some embodiments, the electronic device (201) may omit at least one of these components (e.g., the connection terminal (278)), or may have one or more other components added. In some embodiments, some of these components (e.g., the sensor module (276), the camera module (280), or the antenna module (297)) may be integrated into one component (e.g., the display module (260)).

[0046] The processor (220) may, for example, execute software (e.g., a program (240)) to control at least one other component (e.g., a hardware or software component) of the electronic device (201) connected to the processor (220) and perform various data processing or operations. According to one embodiment, as at least a part of the data processing or operations, the processor (220) may store commands or data received from other components (e.g., a sensor module (276) or a communication module (290)) in a volatile memory (232), process the commands or data stored in the volatile memory (232), and store result data in a non-volatile memory (234). According to one embodiment, the processor (220) may include a main processor (221) (e.g., a central processing unit or an application processor) or an auxiliary processor (223) (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 (221). For example, when the electronic device (201) includes the main processor (221) and the auxiliary processor (223), the auxiliary processor (223) may be configured to use less power than the main processor (221) or to be specialized for a given function. The auxiliary processor (223) may be implemented separately from the main processor (221) or as a part thereof.

[0047] The auxiliary processor (223) may control at least a portion of functions or states associated with at least one component (e.g., a display module (260), a sensor module (276), or a communication module (290)) of the electronic device (201), for example, on behalf of the main processor (221) while the main processor (221) is in an inactive (e.g., sleep) state, or together with the main processor (221) while the main processor (221) is in an active (e.g., application execution) state. In one embodiment, the auxiliary processor (223) (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 (280) or a communication module (290)). In one embodiment, the auxiliary processor (223) (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 (201) itself where the artificial intelligence model is executed, or can be performed through a separate server (e.g., server (208)). 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.

[0048] The memory (230) can store various data used by at least one component (e.g., the processor (220) or the sensor module (276)) of the electronic device (201). The data can include, for example, software (e.g., the program (240)) and input data or output data for commands related thereto. The memory (230) can include a volatile memory (232) or a non-volatile memory (234).

[0049] The program (240) may be stored as software in the memory (230) and may include, for example, an operating system (242), middleware (244), or an application (246).

[0050] The input module (250) can receive commands or data to be used in a component of the electronic device (201) (e.g., a processor (220)) from an external source (e.g., a user) of the electronic device (201). The input module (250) 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).

[0051] The audio output module (255) can output audio signals to the outside of the electronic device (201). The audio output module (255) 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.

[0052] The display module (260) can visually provide information to an external party (e.g., a user) of the electronic device (201). The display module (260) may include, for example, a display, a holographic device, or a projector and a control circuit for controlling the device. In one embodiment, the display module (260) 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.

[0053] The audio module (270) can convert sound into an electrical signal, or vice versa, convert an electrical signal into sound. According to one embodiment, the audio module (270) can acquire sound through the input module (250), output sound through the sound output module (255), or an external electronic device (e.g., electronic device (202)) (e.g., speaker or headphone) directly or wirelessly connected to the electronic device (201).

[0054] The sensor module (276) can detect the operating status (e.g., power or temperature) of the electronic device (201) 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 (276) 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.

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

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

[0057] A haptic module (279) 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 (279) can include, for example, a motor, a piezoelectric element, or an electrical stimulation device.

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

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

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

[0061] The communication module (290) may support the establishment of a direct (e.g., wired) communication channel or a wireless communication channel between the electronic device (201) and an external electronic device (e.g., electronic device (202), electronic device (204), or server (208)), and the performance of communication through the established communication channel. The communication module (290) may operate independently from the processor (220) (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 (290) may include a wireless communication module (292) (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 (294) (e.g., a local area network (LAN) communication module, or a power line communication module). Any of these communication modules may communicate with an external electronic device (204) via a first network (298) (e.g., a short-range communication network such as Bluetooth, wireless fidelity (WiFi) direct, or infrared data association (IrDA)) or a second network (299) (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 may be integrated into a single component (e.g., a single chip) or implemented as multiple separate components (e.g., multiple chips). The wireless communication module (292) may use subscriber information (e.g., an international mobile subscriber identity (IMSI)) stored in the subscriber identification module (296) to verify or authenticate the electronic device (201) within a communication network such as the first network (298) or the second network (299).

[0062] The wireless communication module (292) 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 (292) can support, for example, a high-frequency band (e.g., mmWave band) to achieve a high data transmission rate. The wireless communication module (292) 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 (292) can support various requirements specified in the electronic device (201), an external electronic device (e.g., the electronic device (204)), or a network system (e.g., the second network (299)). According to one embodiment, the wireless communication module (292) can support a peak data rate (e.g., 20 Gbps or more) for realizing eMBB, a loss coverage (e.g., 164 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 1 ms or less for round trip) for realizing URLLC.

[0063] The antenna module (297) 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 (297) 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 (297) 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 (298) or the second network (299), may be selected from the plurality of antennas, for example, by the communication module (290). A signal or power may be transmitted or received between the communication module (290) 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 (297).

[0064] According to various embodiments, the antenna module (297) 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.

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

[0066] According to one embodiment, commands or data may be transmitted or received between the electronic device (201) and an external electronic device (204) via a server (208) connected to a second network (299). Each of the external electronic devices (202 or 204) may be the same or a different type of device as the electronic device (201). According to one embodiment, all or part of the operations executed in the electronic device (201) may be executed in one or more of the external electronic devices (202, 204, or 208). For example, when the electronic device (201) is to perform a certain function or service automatically or in response to a request from a user or another device, the electronic device (201) 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 (201). The electronic device (201) 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 (201) may provide an ultra-low latency service by using distributed computing or mobile edge computing, for example. In another embodiment, the external electronic device (204) may include an Internet of Things (IoT) device. The server (208) may be an intelligent server utilizing machine learning and / or a neural network. According to one embodiment, the external electronic device (204) or the server (208) may be included in the second network (299).The electronic device (201) 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.

[0067] FIG. 3A is a diagram illustrating a network including controlled devices according to one embodiment of the present disclosure.

[0068] Referring to FIG. 3A, a network (300) (e.g., an IoT network) may include a server (350) operating as an IoT cloud, an electronic device (310) (e.g., an electronic device (201)) capable of communicating with the server (350) via long-range wireless communication (e.g., a second network (299)), and one or more controlled devices (e.g., IoT devices (320a, 320b, 320c, and 320d)) within a local network (345) (e.g., a home) that supports IoT technology and can connect to an access point (AP) (340) using short-range wireless communication (e.g., Bluetooth or Wi-Fi) and communicate with the server (350) via the AP (350).

[0069] A hub device (330) (e.g., a wireless charger, a TV, a home automation panel, a personal computer (PC), a smartphone, or a tablet) configured to manage the connection and status of IoT devices (320a, 320b, 320c, and 320d) may be included in the local network (345). The hub device (330) may be onboarded by registering with the server (350) similarly to the IoT devices (320a, 320b, 320c, and 320d), connect to the AP (340) via short-range wireless communication (e.g., Bluetooth or Wi-Fi), and communicate with the server (350) via the AP (340). The hub device (330) may allow at least one of the IoT devices (320a, 320b, 320c, and 320d) to connect to the server (350) via the AP (340). The hub device (330) can control at least one of the IoT devices (320a, 320b, 320c, and 320d) directly (e.g., without going through an electronic device (310), an AP (340), or a server (350)).

[0070] The electronic device (310) can communicate with (e.g., control or manage) IoT devices (320a, 320b, 320c, 320d) via a server (350), via long-range wireless communication (e.g., a second network (299)), or via short-range wireless communication (e.g., a first network (298)).

[0071] The IoT devices (320a, 320b, 320c, 320d) can be controlled (e.g., to report status and / or perform specified actions) by remote commands (e.g., control commands from an electronic device (310), a server (350), or a hub device (330)) and may include, for example, at least one of a television, an air conditioner, an air purifier, a refrigerator, a washing machine, a light (bulb), a security camera, a sensor, or a window treatment. IoT devices (320a, 320b, 320c, 320d) may communicate with the electronic device (310) via a hub device (330) or an AP (340) within a local network (345), communicate with the electronic device (310) via a server (350), communicate directly with the electronic device (310) (e.g., without going through the server (350), the AP (340), or the hub device (330)), or communicate directly with the hub device (330) (e.g., without going through the server (350), the AP (340), or the electronic device (310)).

[0072] In one embodiment, the IoT devices (320a, 320b, 320c, 320d) may be configured to communicate with the electronic device (310) or the hub device (330) via long-range wireless communication (e.g., the second network (299)) or via short-range wireless communication (e.g., the first network (298)). In one embodiment, the IoT devices (320a, 320b, 320c, 320d) may be configured to communicate with the server (350) via long-range wireless communication (e.g., the second network (299)) or via short-range wireless communication (e.g., the first network (298)).

[0073] In one embodiment, the electronic device (310) may be a personal electronic device, such as a smart phone or tablet, or an electronic device having a display and user interface, such as a television or a control console. In one embodiment, the electronic device (310) may be connected to (e.g., paired with) at least one external electronic device (305) (e.g., a tablet or a wearable device such as a smart watch) that is configured to perform at least some of the functions described below of the electronic device (310) directly or through the electronic device (310).

[0074] In one embodiment, the electronic device (310) can discover at least one of the IoT devices (320a, 320b, 320c, 320d) (e.g., the IoT device (320a)) or a second electronic device (e.g., the hub device (330)) and can execute a registration procedure (e.g., onboarding) to register the discovered IoT device (320a) or the hub device (330) with the server (350). The IoT devices (320a, 320b, 320c, 320d) and the hub device (330) can be registered with the server (350) to be associated with a user account. The electronic device (310) can monitor and control the status (e.g., connection status) of IoT devices (320a, 320b, 320c, 320d) and hub device (330) registered in the server (350) based on a user account.

[0075] The electronic device (310) can check the status of IoT devices (320a, 320b, 320c, 320d) and the hub device (330) to be used by the user for the IoT service, or control the IoT devices (320a, 320b, 320c, 320d) and the hub device (330) (for example, transmit a control command instructing to perform a specific action or set an automation routine). In one embodiment, the automation routine can include execution conditions and actions related to at least one IoT device among the IoT devices (320a, 320b, 320c, 320d). In one embodiment, the electronic device (310) can generate at least one automation routine related to at least one IoT device among the IoT devices (320a, 320b, 320c, 320d). Information on the generated at least one automation routine can be stored in the server (350) and / or the hub device (330).

[0076] The electronic device (310) may be an owner device of the local network (350). At least one member device (e.g., an external electronic device (305), a tablet, another smartphone, or a wearable device) that includes at least some capabilities and / or control rights of the electronic device (310) may be included in the network (300). In one embodiment, the member device (e.g., the external electronic device (305)) may not perform a registration procedure for the IoT devices (320a, 320b, 320c, 320d) or the hub device (330), but may perform a function of checking or controlling the status of the IoT devices (320a, 320b, 320c, 320d) and / or the hub device (330) registered with the server (350). In one embodiment, a member device (e.g., an external electronic device (305)) may be associated with the same user account as an electronic device (310), IoT devices (320a, 320b, 320c, 320d), and / or a hub device (330).

[0077] FIG. 3b is a drawing for explaining movement of a hub device according to one embodiment of the present disclosure.

[0078] Referring to FIG. 3B, the hub device (330) can be used as a hub in a fixed location (e.g., a local network (345) or a home (360)) when connected to an AP (340). For example, the hub device (330) can include a wireless charger (e.g., a wireless charging circuit (418)), and a user can move around with the hub device (330) to use the wireless charging function or the hub function in a new location (e.g., an office (365)).

[0079] At least one IoT device (e.g., IoT device (320a and / or 320b)) among the IoT devices (320a, 320b, 320c, 320d) can be connected to the server (350) via the AP (340) and can be controlled by the electronic device (310), the server (350), and / or the hub device (330). At least one IoT device (e.g., IoT device (320c or 320d)) among the IoT devices (320a, 320b, 320c, 320d) can be a hub-connected type device that is directly connected to the hub device (330) (e.g., via Bluetooth, Wi-Fi, or Zigbee). The IoT device (320c or 320d) can be controlled by the hub device (330) according to a request of the electronic device (310) and / or the server (350). When the hub device (330) is disconnected from the server (350) (e.g., goes offline) as it leaves the local network (345), at least one IoT device (e.g., a hub-connected IoT device (320c or 320d)) may also go offline.

[0080] In one embodiment, a user may take the hub device (330) to a new location (e.g., office (365)) other than the local network (345) (e.g., home (360)) while traveling or on a business trip. When the hub device (330) goes offline upon moving to the office (365), information or status of at least one IoT device (e.g., hub-connected IoT device (320c or 320d)) cannot be updated to the server (350), and thus the user (e.g., electronic device (310) or external electronic device (305)) cannot intuitively know why the hub device (330) or at least one IoT device (e.g., hub-connected IoT device (320c or 320d)) has gone offline.

[0081] In one embodiment, when a hub device (330) including a wireless charging function is disconnected from a server (350) (e.g., offline) due to leaving a local network (345), the electronic device (310) may report to the server (350) the location (e.g., geolocation: geo) of the electronic device (310) identified by the electronic device (310) while being wirelessly charged via the hub device (330) so that the location may be utilized as the location of the hub device (330). The electronic device (310) may identify the geographic location (e.g., routing address or latitude and longitude) of the electronic device (310) via a global positioning system (GPS) or a long-range wireless communication system.

[0082] In one embodiment, the server (330) may update the connection status (e.g., online or offline) of the IoT devices (320a, 320b, 320c, and 320d) using the location of the hub device (310) (e.g., the geographic location of the charging electronic device (310). In one embodiment, the server (330) may notify devices associated with the user account (e.g., the electronic device (310) and / or the external electronic device (305)) that the IoT devices (320a, 320b, 320c, and 320d) have gone offline due to movement of the hub device (310). In one embodiment, the server (330) may notify devices associated with the user account (e.g., the electronic device (310) and / or the external electronic device (305)) that an automated routine assigned to the hub device (310) may be deactivated due to movement of the hub device (310).

[0083] In one embodiment, the hub device (330) may include an input module (e.g., input module (420)) including at least one button, and may execute a pre-designated automation routine based on identifying a user input (e.g., a button pressed or a button double pressed) through the input module (420). In one embodiment, the hub device (330) may directly transmit a control command to at least one IoT device according to the designated automation routine, or may request the server (350) to execute the designated automation routine. When a hub device (330) including a wireless charging function is disconnected from a server (350) (e.g., offline) due to leaving a local network (345), the electronic device (310) can receive a wireless signal containing information of a user input (e.g., a button press or two button presses) detected by the hub device (330) while wirelessly charging through the hub device (330) through the wireless charging circuit (408) of the electronic device (310) that is in contact with (or in proximity to) the hub device (330).

[0084] In one embodiment, the electronic device (310) can transmit information on user input received via the wireless signal to the server (350), thereby causing the server (350) to execute a designated automation routine for the user input.

[0085] In one embodiment, when a hub device (330) including a wireless charging function is disconnected from a server (350) (e.g., offline) due to leaving a local network (345), the electronic device (310) may provide a wireless communication connection (e.g., a tethering connection) between the electronic device (310) and the hub device (330) so that the hub device (330) may access an external network (e.g., the Internet) through the electronic device (310) while wirelessly charging through the hub device (330). For example, when the electronic device (310) operates as a mobile hotspot, the hub device (330) may connect to the server (350) and become online through the tethering connection between the electronic device (310) and the hub device (330).

[0086] In one embodiment, a user may take at least one IoT device (e.g., a hub-connected IoT device (320d)) connected to a hub device (330) to an office (365) together with the hub device (330). The hub device (330) may manage the status of the IoT device (320d) or control the IoT device (320d) while maintaining a connection with the IoT device (320d). The hub device (330) may notify the electronic device (310) or the server (350) of the connection status information of the IoT device (320d) (e.g., an online status) and the new geographic location of the IoT device (320d) (e.g., the office (365)). Based on the notification, the electronic device (310) or the server (350) may deactivate an automation routine at a previous location (e.g., home) associated with the IoT device (320d).

[0087] In one embodiment, the hub device (330) can be brought online by connecting to the server (350) via a tethered connection of the electronic device (310) or a new AP (not shown) at a new location (e.g., office (365)). In one embodiment, the hub device (330) can be directly connected (e.g., via Bluetooth, Wi-Fi, or Zigbee) to new IoT devices (e.g., IoT devices 320d, 320e) at the new location (e.g., office (365)). In one embodiment, the IoT devices (320d, 320e) can be hub-connected IoT devices. The electronic device (310) can generate an automation routine associated with one or more IoT devices (e.g., IoT device 320d and / or IoT devices 320d, 320e) that are connectable to the hub device (330) at the new location (e.g., office (365)).

[0088] In one embodiment, the electronic device (310) may generate automation routines (e.g., an automation routine for a home and an automation routine for an office) for each location where the hub device (330) is located, and transmit a routine generation request to the hub device (330) and / or the server (350). For example, the automation routine for a home may include execution conditions and control commands related to IoT devices (320a, 320b, 320c, 320d) located in the home (e.g., a local network (345)). For example, the automation routine for an office may include execution conditions and control commands related to IoT devices (320d, 320f, 320e) located in the home (e.g., a local network (345)).

[0089] In one embodiment, the hub device (330) and / or the server (350) may execute a corresponding location-specific automation routine depending on the current location of the hub device (330). In one embodiment, information about the current location of the hub device (330) may be transmitted from the electronic device (310) being wirelessly charged or the hub device (330) to the server (350) via the hub device (330). In one embodiment, the hub device (330) and / or the server (350) may execute different automation routines depending on the current location of the hub device (330) for the same user input received by the hub device (330) (e.g., a button press or two button presses).

[0090] In one embodiment, the electronic device (310), the hub device (330), or the server (350) can change the operating mode of the IoT devices (320a, 320b, 320c, 320d) associated with the hub device (330) based on the movement of the hub device (330). In one embodiment, based on identifying that the hub device (330) is out of the home (e.g., local network (345)), the electronic device (310) can manage the IoT devices (320a, 320b, 320c, 320d) located in the home into a designated power saving mode and / or a designated security enhancement mode.

[0091] In one embodiment, the electronic device (310), the hub device (330), or the server (350) may activate or deactivate at least one of the automation routines assigned to the hub device (330) based on movement of the hub device (330). In one embodiment, based on identifying that the hub device (330) has moved away from the home (e.g., the local network (345)), the electronic device (310), the hub device (330), or the server (350) may deactivate at least one automation routine associated with at least one of the IoT devices (320a, 320b, 320c, 320d) located in the home. In one embodiment, among the IoT devices (320a, 320b, 320c, 320d) located in the home, an automation routine associated with at least one IoT device that has come online via another hub device or network connection may remain activated without being deactivated.

[0092] FIG. 4A is a block diagram illustrating the configuration of an electronic device performing IoT control according to one embodiment of the present disclosure.

[0093] Referring to FIG. 4A, the electronic device (310) may be a device that implements an IoT service (e.g., an event-based IoT service) in an IoT network (e.g., the network (300)). For example, the IoT network may be a smart home network, and the IoT service may be an automation service. The electronic device (310) may include a processor (402) (e.g., the processor (220)), a communication circuit (404) (e.g., the communication module (290)), a memory (406) (e.g., the memory (230)), a wireless charging circuit (408), and / or a display (410) (e.g., the display module (260)).

[0094] The electronic device (310) may include a communication circuit (404) (e.g., the communication module (290) of FIG. 2) that transmits and receives signals using one or more antennas (not shown) with an external electronic device (e.g., at least one of the server (350), AP (340), IoT devices (320a, 320b, 320c, 320d), or hub device (330) of FIG. 3a). In one embodiment, the one or more antennas may be implemented as part of the antenna module (297) of FIG. 2. The first electronic device (310) may support at least one of long term evolution (LTE), 5G / NR (new radio), Zigbee, Z-Wave, ultra wide-band (UWB), Wi-Fi, or Bluetooth (e.g., Bluetooth legacy (BT) and / or Bluetooth low energy (BLE)) via a communication circuit (404). The communication circuit (404) may include one or more communication circuits based on LTE, 5G / NR, Zigbee, Z-Wave, UWB, Wi-Fi, BT, and / or BLE.

[0095] The electronic device (310) may include a display (410) for interfacing with a user (e.g., the display module (260) of FIG. 2). The first electronic device (310) may display information related to an IoT service (e.g., status of the IoT devices (320a, 320b, 320c, 320d) and / or the hub device (330) and / or control objects of the IoT devices (320a, 320b, 320c, 320d) and the hub device (330)) through the display (410), and / or receive user input related to an IoT service (e.g., commands for controlling the IoT devices (320a, 320b, 320c, 320d) and / or the hub device (330)). In one embodiment, the electronic device (310) may receive the user input via the display (410) or may receive voice user input via an audio module (not shown).

[0096] The electronic device (310) may include a processor (402) (e.g., processor (220) of FIG. 2) that may be implemented as one or more single-core processors or one or more multi-core processors, and a memory (406) (e.g., memory (230) of FIG. 2) that stores instructions and data for the operation of the first electronic device (310). The memory (406) may store a client application, user information, device information, connection information, or related data for executing an IoT service.

[0097] The processor (402) manages the status and operation of controlled devices (e.g., IoT devices (320a, 320b, 320c, 320d)) and / or the hub device (330) related to the IoT service, and can transmit a control command for at least one controlled device based on a user input to the at least one controlled device directly through the communication circuit (404) or through the server (340), AP (340), or hub device (330).

[0098] At least one of the IoT devices (320a, 320b, 320c, 320d) or the hub device (330) registered to the server (350) can periodically or aperiodically report its status information to the server (350), the electronic device (310), and / or the hub device (330). The electronic device (310) can output (e.g., display) the status information of at least one IoT device through the display (410).

[0099] In one embodiment, the electronic device (310) may be configured to execute a client application for an IoT service by the processor (402). In one embodiment, the client application may include a function to execute a designated action of the IoT devices (320a, 320b, 320c, and 320d) or the hub device (330) and a function to display information related to the status of the IoT devices (320a, 320b, 320c, and 320d) or the hub device (330). In one embodiment, the client application may include a function to generate an automation routine including an execution condition and an action related to at least one of the IoT devices (320a, 320b, 320c, and 320d) and register the automation routine with the hub device (330) or the server (350).

[0100] In one embodiment, the processor (402) can discover an IoT device (e.g., at least one of the IoT devices (320a, 320b, and 320c)) or a hub device (330) by receiving advertising data (e.g., a BLE advertising (ADV) signal) via the communication circuit (404) while a client application is running, and control the display (410) to output information (e.g., a device name, a model name, and / or a device image) of the IoT devices (320a, 320b, and 320c) or the hub device (330). The processor (402) can onboard at least one of the IoT devices (320a, 320b, and 320c) or the hub device (330) to the server (350) through the displayed information.

[0101] In one embodiment, the wireless charging circuit (408) may be configured to charge a battery (e.g., battery 289) of the electronic device (310) with power received from an external electronic device (e.g., a hub device (330) having a wireless charging function) via a wired charging signal and / or a wireless charging signal. In one embodiment, the wireless charging circuit (408) may receive a wireless charging signal generated by the wireless charging circuit (418) of the hub device (330) while the electronic device (310) is in contact with (or in proximity to) the external electronic device (e.g., a hub device (330) having a wireless charging function). In one embodiment, the wireless charging signal may include information that the hub device (330) wishes to transmit (e.g., a user ID, a device ID, and / or user input information). The processor (402) may obtain the information from the wireless charging signal received by the wireless charging circuit (408). In one embodiment, the processor (402) may transmit a wireless charging signal to the hub device (330) via the wireless charging circuit (408) that includes information that the electronic device (310) wishes to transmit (e.g., a user ID, a device ID, and / or user input information).

[0102] FIG. 4b is a block diagram illustrating the configuration of a hub device that performs IoT control according to one embodiment of the present disclosure.

[0103] Referring to FIG. 4B, the hub device (330) may be a device that manages an IoT service (e.g., an event-based IoT service) in an IoT network (e.g., the network (300)). For example, the IoT network may be a smart home network, and the IoT service may be an automation service. The hub device (330) may be located within a local network (345) or in an external network (e.g., the Internet). The hub device (330) may include a processor (412), a communication circuit (414), a memory (416), a wireless charging circuit (418), and / or an input module (420).

[0104] The hub device (310) may include a communication circuit (404) that transmits and receives signals using one or more antennas (not shown) with an external electronic device (e.g., at least one of the electronic device (310), server (350), AP (340), and / or IoT devices (320a, 320b, 320c, 320d) of FIG. 3a). The hub device (330) may support at least one of a designated wireless communication technology (e.g., Zigbee, Z-Wave, ultra wide-band (UWB), Wi-Fi, or Bluetooth (e.g., Bluetooth legacy (BT) and / or Bluetooth low energy (BLE)) via a communication circuit (414). The communication circuit (414) may include one or more communication circuits based on Zigbee, Z-Wave, UWB, Wi-Fi, BT, and / or BLE.

[0105] The hub device (330) may include an input module (420) for interfacing with a user. In one embodiment, the input module (420) may include at least one button, and the processor (412) may detect a pressed or double pressed of the button via the input module (420).

[0106] The hub device (330) may include a processor (412) that may be implemented as one or more single-core processors or one or more multi-core processors, and a memory (416) that stores instructions and data for the operation of the hub device (330). The memory (406) may store applications (e.g., widgets) for executing an IoT service, user information, device information, connection information, or related data. In one embodiment, the memory (416) may store automation routines related to controlled devices (e.g., IoT devices (320a, 320b, 320c, 320d)) related to the IoT service.

[0107] The processor (412) can manage the status and operation of controlled devices (e.g., IoT devices (320a, 320b, 320c, 320d)) related to the IoT service. The processor (412) can receive command information related to the control of at least one of the controlled devices (e.g., IoT device (320a)) from the electronic device (310) and / or the server (350), and transmit a control command generated based on the command information to at least one of the controlled devices (e.g., IoT device (320a)) through the communication circuit (414). In one embodiment, the control command can be transmitted to the corresponding controlled device (e.g., IoT device (320a)) through the AP (340) or directly (e.g., through D2D communication). The above command information may instruct an action to be executed by the IoT device (320a) as instructed by the user input, or an automation routine generated by the electronic device (310) or server (350). In one embodiment, the automation routine may include execution conditions and actions related to at least one of the IoT devices (320a, 320b, 320c, and 320d).

[0108] IoT devices (320a, 320b, 320c, 320d) registered with the server (350) can periodically or aperiodically report their status information to the server (350), the electronic device (310), and / or the hub device (330). The hub device (330) can periodically or aperiodically report its status information to the server (350) or the electronic device (310).

[0109] In one embodiment, the wireless charging circuit (418) may be configured to provide power to an external electronic device (e.g., an electronic device having a wireless charging function (310)) via a wireless charging signal to charge a battery (e.g., a battery (289)) of the electronic device (310). In one embodiment, the wireless charging circuit (418) may transmit the wireless charging signal while the hub device (310) is in contact with (or in proximity to) the external electronic device (e.g., an electronic device having a wireless charging function (310)). In one embodiment, the wireless charging signal may include information that the hub device (330) wishes to transmit (e.g., a user ID, a device ID, and / or user input information). The processor (412) may include the information in the wireless charging signal by the wireless charging circuit (408). In one embodiment, the processor (412) may receive, via the wireless charging circuit (418), a wireless charging signal that includes information that the electronic device (310) wishes to transmit (e.g., a user ID, a device ID, and / or user input information).

[0110] FIG. 5 is a flowchart illustrating an operation of an electronic device that notifies movement of a hub device according to an embodiment of the present disclosure. According to embodiments, at least one of the operations described below may be executed by the processor (402) of the electronic device (310). According to embodiments, the memory (406) of the electronic device (310) may store instructions that, when executed by the processor (402), cause the electronic device (310) to perform at least one of the operations described below. According to embodiments, at least one of the operations described below may be omitted, modified, or executed in a different order.

[0111] Referring to FIG. 5, in operation 502, the electronic device (310) (e.g., processor (402)) may detect that wireless charging has started. In one embodiment, the electronic device (310) (e.g., processor (402)) may determine that wireless charging has started based on receiving a wireless charging signal through the wireless charging circuit (408). In one embodiment, the electronic device (310) may start wireless charging by coming into contact with (or in proximity to) a hub device having a wireless charging function (e.g., hub device (330)).

[0112] In operation 504, the electronic device (310) (e.g., processor (402)) may authenticate a user ID (e.g., user account information) of the hub device (330) via the wireless charging circuit (408). In one embodiment, the electronic device (310) (e.g., processor (402)) may perform user ID authentication by confirming that the hub device (330) shares the same user ID as the electronic device (310). In one embodiment, the electronic device (310) (e.g., processor (402)) may identify that a wireless signal received from the hub device (330) via the wireless charging circuit (408) includes a user ID, and may perform user ID authentication for the hub device (330) based on the user ID being identical to the user ID of the electronic device (310). In one embodiment, operation 504 may be omitted, and the electronic device (310) (e.g., processor (402)) may proceed to operation 506 after wireless charging has begun.

[0113] In operation 506, the electronic device (310) (e.g., processor (402)) may obtain a device ID of the hub device (330) from a wireless signal received from the hub device (330) via the wireless charging circuit (408). In one embodiment, the electronic device (310) (e.g., processor (402)) may transmit a wireless signal including a device ID request to the hub device (330) via the wireless charging circuit (408). In one embodiment, the electronic device (310) (e.g., processor (402)) may receive a wireless signal including a device ID of the hub device (330) via the wireless charging circuit (408) as a response to the device ID request.

[0114] In operation 508, the electronic device (310) (e.g., processor (402)) may transmit a device ID authentication request including the device ID to the server (350) via the communication circuit (404). When the server (350) receives the device ID authentication request, the server (350) may check whether the hub device (330) corresponding to the device ID is registered with the server (350) for the same user account as the electronic device (310). The electronic device (310) (e.g., processor (402)) may receive a device ID authentication response corresponding to the device ID authentication request from the server (350) via the communication circuit (404).

[0115] At step 510, the electronic device (310) (e.g., processor (402)) may determine whether the hub device (330) has been successfully authenticated based on a device ID authentication response received from the server (350). In one embodiment, the device ID authentication response may include information indicating that the hub device (330) has been successfully authenticated if the server (350) verifies that the hub device (330) is registered with the server (350) for the same user account as the electronic device (310). If the device ID authentication response indicates that the hub device (330) has been authenticated, the electronic device (310) (e.g., processor (402)) may proceed to step 512. If the device ID authentication response does not indicate that the hub device (330) has been authenticated, for example, if the hub device (330) is not registered with the server (350) for the same user account as the electronic device (310), the electronic device (310) (e.g., processor (402)) may terminate the operations.

[0116] In one embodiment, if the electronic device (310) authenticates the hub device (330) through the user ID in operation 504, operations 508 and 510 may be omitted, and the electronic device (310) (e.g., processor (402)) may proceed to operation 512 after obtaining the device ID of the hub device (330) from device 506.

[0117] In operation 512, the electronic device (310) (e.g., processor (402)) may transmit to the server (350) a hub ID including the device ID acquired in operation 506 and location information indicating a current location (e.g., geographic location (geo)) of the electronic device (310), such that the server (350) may determine that the hub device (330) is present in the same geographic location as the electronic device (310). In one embodiment, the geographic location may include at least one routing address or latitude and longitude.

[0118] In one embodiment, the server (350) can identify that the hub device (330) has moved based on the hub ID and location information. Based on identifying that the hub device (330) has moved, the server (350) can identify that the hub device (330) and at least one IoT device (e.g., hub-connected IoT devices (320c and / or 320d)) connected to the hub device (330) have gone offline. In one embodiment, the server (350) can transmit connection status information notifying that the hub device (330) and at least one IoT device connected to the hub device (330) have gone offline to at least one electronic device (e.g., electronic device (310) and / or external electronic device (305)) that shares the same user ID as the hub device (330). In one embodiment, the connection status information may include an offline reason for the hub device (330) (e.g., information indicating that the hub device (330) and at least one IoT device connected to the hub device (330) are offline due to movement of the hub device (330)) (e.g., offline reason information (1310) of FIG. 13a).

[0119] In one embodiment, the server (350) may identify that at least one automation routine associated with the hub device (330) and at least one IoT device connected to the hub device (330) is deactivated based on identifying that the hub device (330) is moved. In one embodiment, the server (350) may transmit deactivation information notifying that the at least one automation routine is deactivated to at least one electronic device (e.g., the electronic device (310) and / or the external electronic device (305)) that shares the same user ID as the hub device (330). In one embodiment, the deactivation information may include a reason for deactivation of the at least one automation routine (e.g., information notifying that the hub device (330) and at least one IoT device connected to the hub device (330) are offline due to movement of the hub device (330)) (e.g., deactivation reason information (1322) of FIG. 13B).

[0120] At step 514, the electronic device (310) (e.g., processor (402)) may receive a wireless signal including user input information from the hub device (330) while charging via the hub device (330). In one embodiment, the electronic device (310) (e.g., processor (402)) may identify that the wireless signal received via the wireless charging circuit (408) includes user input information. At step 516, the electronic device (310) (e.g., processor (402)) may transmit the user input information to the server (350) together with the hub ID, thereby causing the server (350) to execute an automated routine corresponding to the user input information.

[0121] In operation 518, the electronic device (310) (e.g., processor (402)) may determine whether connection status information and / or deactivation information indicating an online / offline status of the hub device (330) is received from the server (350) via the communication circuit (404). If the connection status information and / or deactivation information is not received, the electronic device (310) (e.g., processor (402)) may terminate operations. If the connection status information and / or deactivation information is received, the electronic device (310) (e.g., processor (402)) may proceed to operation 520.

[0122] In one embodiment, the connection status information may include information related to online or offline status of at least one of the hub device (330) or one or more IoT devices operatively coupled with the hub device (330) (e.g., hub-connected IoT devices (320d, 320e, 230f)). In one embodiment, the connection status information may include information related to movement of the hub device (330) (e.g., a change in the charging position of the hub device (330). In one embodiment, the electronic device (310) (e.g., the processor (402)) may receive a wireless signal including the connection status information from an offline hub device (330) through the wireless charging circuit (408).

[0123] In operation 520, the electronic device (310) (e.g., the processor (402)) may display, through the display (410), offline reason information (e.g., offline reason information (1310) of FIG. 13A) indicating that the hub device (330) and / or at least one IoT device has become offline due to movement of the hub device (330) based on the connection status information and / or the deactivation information. And / or the electronic device (310) (e.g., the processor (402)) may display, through the display (410), deactivation reason information (e.g., deactivation reason information (1322) of FIG. 13B) indicating that at least one automation routine associated with the hub device (330) and / or at least one IoT device has been deactivated based on the deactivation information.

[0124] FIG. 6 is a flowchart illustrating an operation of an electronic device that manages automated routines according to movement of a hub device according to an embodiment of the present disclosure. According to embodiments, at least one of the operations described below may be executed by the processor (402) of the electronic device (310). According to embodiments, the memory (406) of the electronic device (310) may store instructions that, when executed by the processor (402), cause the electronic device (310) to perform at least one of the operations described below. According to embodiments, at least one of the operations described below may be omitted, modified, or executed in a different order.

[0125] Referring to FIG. 6, in operation 602, the electronic device (310) (e.g., processor (402)) may receive a notification indicating hub movement from the server (350). In one embodiment, the notification indicating hub movement may include information indicating that the hub device (330) has moved to a new location, information about the new location to which the hub device (330) has moved, information indicating that the location of the IoT device (320) has changed, and / or information indicating that the IoT device (320) has been newly connected. In operation 604, the electronic device (310) (e.g., processor (402)) may display hub movement information.

[0126] In one embodiment, the electronic device (310) may display information indicating hub movement (e.g., a pop-up notification), execute a client application for an IoT service based on receiving a user input (e.g., a touch) through the information, and display the hub movement information through the client application. In one embodiment, the pop-up notification may be displayed while the client application is not running or is running in the background. In one embodiment, the hub movement information may include a guidance text, "The hub has come online at a different location." In one embodiment, the hub movement information may include a guidance text, "IoT device XXX has connected to the hub at a new location."

[0127] In operation 606, the electronic device (310) (e.g., processor (402)) may obtain an automation list including one or more automation routines registered by a user from a server (350). In one embodiment, the automation list may include one or more automation routines that may be executed via a hub device (330). In one embodiment, the automation list may include one or more automation routines that include execution conditions and / or actions related to at least one IoT device (e.g., a hub-connected IoT device) directly connected to the hub device (330).

[0128] In operation 608, the electronic device (310) (e.g., processor (402)) may display information of the automation list (e.g., information (1324) of FIG. 13B) through the display (410). In one embodiment, the information of the automation list may indicate, for each automation routine included in the automation list, a name, at least one associated IoT device, an execution condition, and / or an action.

[0129] In operation 610, the electronic device (310) (e.g., processor (402)) may determine whether there is at least one IoT device among one or more IoT devices associated with the automation list that has gone offline due to movement of the hub device (330). In one embodiment, the electronic device (310) (e.g., processor (402)) may identify at least one IoT device (e.g., IoT devices (320a, 320b, 320c, and 320d)) among a plurality of IoT devices located in a local network (345) (e.g., a house) that can no longer connect to the hub device (330) after the hub device (330) has moved (e.g., IoT devices (320a, 320b)), and determine that the identified at least one IoT device is offline. If there is at least one IoT device that is offline, the electronic device (310) (e.g., processor (402)) may proceed to operation 612. If there is no at least one IoT device that is offline, the electronic device (310) (e.g., processor (402)) may terminate operations.

[0130] The electronic device (310) (e.g., processor (402)) may determine that at least one automation routine, among one or more automation routines included in the automation list, that includes an execution condition and / or an action related to at least one IoT device that is offline, is deactivated. In one embodiment, the electronic device (310) (e.g., processor (402)) may include information indicating activation or deactivation of each automation routine in the information of the automation list (e.g., information (1422) of FIG. 14B or information (1442) of FIG. 14D). In one embodiment, the electronic device (310) (e.g., processor (402)) may display information (e.g., shading) indicating that a specific automation routine related to at least one IoT device directly connected to the hub device (330) is deactivated together with the information of the automation list based on hub movement information.

[0131] In one embodiment, a first automation routine generated for a local network (340) may include an execution condition in which a user presence is detected by an IoT device (320d) (e.g., a temperature sensor) and an action in which an IoT device (320b) (e.g., an air conditioner) is activated. When the IoT device (320d) is a hub-connected device directly connected to a hub device (330), when the IoT device (320d) moves, the IoT device (320d) may go offline, and the electronic device (310) may decide to deactivate the first automation routine.

[0132] In operation 612, the electronic device (310) (e.g., processor (402)) may display information suggesting a new automation routine associated with at least one IoT device (e.g., IoT devices (320c, 320d)) connected to the hub device (330) after the move, and receive user input selecting to activate the new automation routine. In one embodiment, the electronic device (310) (e.g., processor (402)) may generate a second automation routine including execution conditions and / or actions associated with the IoT devices (320c, 320d) that moved with the hub device (330) and / or additional IoT devices (e.g., IoT devices (320e, 320f)) connected at the new location, and display information suggesting the second automation routine (e.g., information (1332)). The information may indicate a routine name, an execution condition, and / or an action of the proposed second automation routine.

[0133] At step 614, the electronic device (310) (e.g., processor (402)) may transmit a routine creation request representing the new automated routine to a server (350) based on receiving user input selecting to activate the new automated routine (e.g., a second automated routine). The routine creation request may include information representing the routine name, execution conditions, and actions of the new automated routine.

[0134] In operation 616, the electronic device (310) (e.g., processor (402)) may receive a user input selecting to activate or deactivate at least one automation routine based on displaying information in the automation list. In one embodiment, the electronic device (310) (e.g., processor (402)) may receive a user input selecting at least one automation routine from among one or more automation routines included in the automation list to be kept activated, deleted, or deactivated.

[0135] In operation 618, the electronic device (310) (e.g., processor (402)) may transmit an activation request, a deletion request, or a deactivation request for the at least one selected automation routine to the server (350).

[0136] FIG. 7 illustrates a sequence diagram illustrating a procedure for notifying movement of a hub device according to one embodiment of the present disclosure. According to embodiments, at least one of the operations described below may be omitted, modified, or executed in a different order.

[0137] Referring to FIG. 7, in operation 702, a hub device (330) (e.g., a hub device having a wireless charging function) may be onboarded (e.g., registered with a server (350)). In one embodiment, the hub device (330) may connect to an AP (340) using a communication circuit (414) and then register with the server (350) via the AP (340). In one embodiment, the hub device (330) may perform a registration procedure for the server (350) after connecting to the AP (340) based on connection information provided from the electronic device (310). In one embodiment, the hub device (330) may be registered with the server (350) to be associated with a user ID (e.g., a user account). The hub device (330) may receive a user ID from the server (350) during the registration procedure and store the user ID in the memory (416).

[0138] In one embodiment, the hub device (330) may periodically or aperiodically transmit the connection status (e.g., online status) and location information (e.g., network ID, IP address, and / or geographic location) of the hub device (330) to the server (350) while connected to the server (350) (e.g., online status). In one embodiment, the hub device (330) may control (e.g., transmit a control command) at least one IoT device (e.g., IoT devices 320a, 320b, 320c, and / or 320d)) at the request of the electronic device (310) and / or the server (350) while online. In one embodiment, the hub device (330) may control at least one IoT device according to a designated automation routine while online.

[0139] In operation 704, the hub device (330) may detect a state in which the connection with the server (350) is lost (e.g., offline) through the communication circuit (414). In one embodiment, the hub device (330) may be disconnected from the server (350) and become offline when the user moves the hub device (330) to a new location (e.g., office). In one embodiment, the server (350) may detect that the hub device (330) is offline based on the fact that information indicating the connection state is not received from the hub device (330), and may notify information indicating the connection state (e.g., offline) of the hub device (330) to at least one user device (e.g., the electronic device (310)). The electronic device (310) may identify that the hub device (330) is offline based on the notification from the server (350).

[0140] In operation 706, the hub device (330) may identify that wireless charging of the electronic device (310) has begun by detecting that any external electronic device (e.g., the electronic device (310)) has come into contact with the hub device (330). In one embodiment, the hub device (330) may detect that wireless charging of the electronic device (310) has begun through the wireless charging circuit (418). Similarly, the electronic device (310) may detect that wireless charging of the electronic device (310) has begun through the wireless charging circuit (408).

[0141] In operation 708, the electronic device (310) may authenticate a user ID of the hub device (330). In one embodiment, the hub device (330) may include the user ID of the hub device (330) in a wireless signal transmitted through the wireless charging circuit (418) after wireless charging of the electronic device (310) has begun. The user ID may be pre-stored or may be obtained from the server (350) during an onboarding procedure. In one embodiment, the electronic device (310) may determine that the hub device (330) is authenticated based on the user ID of the hub device (330) received through the wireless charging circuit (408) being identical to the user ID of the electronic device (310). In one embodiment, the electronic device (310) may include a user ID request in a wireless signal transmitted through the wireless charging circuit (408) while wireless charging is in progress. The hub device (330) may, in response to the user ID request, include the user ID of the hub device (330) in a wireless signal transmitted through the wireless charging circuit (418). In one embodiment, operation 708 may be omitted.

[0142] In steps 710 and 712, the electronic device (310) may obtain a device ID (e.g., hub ID) of the hub device (330) via the wireless charging circuit (408). In one embodiment, in step 710, the electronic device (310) may transmit a wireless signal including a device ID request to the hub device (330) via the wireless charging circuit (408). In step 712, the hub device (330) may transmit a wireless signal including a device ID response including the device ID (e.g., hub ID) of the hub device (330) to the electronic device (310) via the wireless charging circuit (418). In one embodiment, the hub device (330) may include the hub ID in the wireless signal and transmit it to the electronic device (310) via the wireless charging circuit (418) without a request from the electronic device (310).

[0143] In operation 714, the electronic device (310) may transmit a device ID authentication request including the device ID to the server (350) via the communication circuit (404). The server (350) may authenticate the device ID based on the device ID being previously registered with the server (350) for the same user account as the electronic device (310). In operation 716, the server (350) may transmit a device ID authentication response indicating that the device ID has been successfully authenticated to the electronic device (310). In one embodiment, the device ID authentication response includes information (e.g., a model name) indicating that the hub device (330) corresponding to the device ID is a wireless charging hub, and the electronic device (310) may regard the device ID as a hub ID.

[0144] In operation 718, the electronic device (310) may transmit location information indicating the device ID (e.g., hub ID) and the current location (e.g., geographic location (geo)) of the electronic device (310) to the server (350). The server (350) may determine the received location information as the current location of the hub device (330). The server (350) may identify that the hub device (330) has moved based on the difference between the received location information and the previously stored location information of the hub device (330).

[0145] In operation 720, the server (350) may determine connection status information and deactivation information related to the hub device (330) based on identifying that the hub device (330) has moved. In one embodiment, the server (350) may update the connection status of the hub device (330) and at least one IoT device (e.g., at least one of the IoT devices (320a, 320b, 320c, and / or 320d)) related to the hub device (330) to an offline state. In one embodiment, the server (350) may determine the hub device (330) to be offline and determine the hub-connected IoT devices (e.g., the IoT devices (320c and / or 320d)) related to the hub device (330) to be offline. In one embodiment, the server (350) may store the offline reason of the hub device (330) and at least one IoT device related to the hub device (330) as being offline due to the movement of the hub device (330).

[0146] In one embodiment, the server (350) may determine, based on identifying that the hub device (330) has moved, to retrieve at least one automation routine associated with the hub device (330) and at least one IoT device, and to deactivate the at least one automation routine. In one embodiment, the server (350) may determine that the hub device (330) is offline, and may deactivate at least one automation routine associated with the hub device (330) and / or a hub-connected IoT device (e.g., IoT devices (320c and / or 320d)). In one embodiment, the server (350) may store the reason for deactivation of the at least one automation routine as deactivation due to movement of the hub device (330).

[0147] In operation 722, the server (350) may transmit connection status information to at least one external electronic device (e.g., external electronic device (305) and / or electronic device (310)) associated with a user ID of the hub device (330). The connection status information may include a connection status of the hub device (330) (e.g., offline status) and / or offline reason information identified by the server (350) (e.g., movement of the hub device (330). In operation 724, the external electronic device (305) (and / or electronic device (310)) may display information of the offline hub device (330) (e.g., device name and / or device image) and / or offline reason information (e.g., offline reason information (1310) of FIG. 13A)) by receiving the connection status information. In one embodiment, the external electronic device (305) (and / or electronic device (310)) may display a pop-up notification indicating receipt of the connection status information, execute a client application in response to user input, and display information about the offline hub device (330) and / or offline reason information through the client application.

[0148] At step 726, the server (350) may transmit deactivation information to at least one external electronic device (e.g., the external electronic device (305) and / or the electronic device (310)) associated with the user ID of the hub device (330). The deactivation information may include deactivation reason information (e.g., movement of the hub device (330)) identified by the server (350). At step 728, the external electronic device (305) (and / or the electronic device (310)) may display information of at least one deactivated automation routine (e.g., automation routine name and / or content) (e.g., information (1324) of FIG. 13b)) and deactivation reason information (e.g., deactivation reason information (1322) of FIG. 13b)) by receiving the deactivation information. In one embodiment, the external electronic device (305) (and / or electronic device (310)) may display a pop-up notification indicating receipt of the deactivation information, execute a client application in response to user input, and display, through the client application, information about the at least one deactivated automation routine and / or information about the reason for the deactivation.

[0149] FIG. 8 illustrates a sequence diagram illustrating a procedure for executing an automated routine in an offline state of a hub device according to one embodiment of the present disclosure. According to embodiments, at least one of the operations described below may be omitted, modified, or executed in a different order.

[0150] Referring to FIG. 8, in operation 802, the electronic device (310) may generate an automation routine for at least one IoT device (e.g., at least one of the IoT devices (320a, 320b, 320c, and 320d)) and transmit information of the automation routine to a server (350). The automation routine may include an execution condition and an action (e.g., a control command) for controlling the at least one IoT device. In one embodiment, the execution condition may include a user input1 (e.g., pressing a button) through an input module (420) of the hub device (330). In one embodiment, the action may include a control command for turning off at least one smart light (e.g., the IoT device (320c)). In one embodiment, when the hub device (330) is online and the button of the hub device (330) is pressed once, the hub device (330) can transmit information indicating that user input 1 has been received to the server (350), thereby causing the server (350) to turn off the smart light.

[0151] In operation 804, the electronic device (310) may transmit a Find My Device routine to the server (350) to find at least one user device (e.g., the electronic device (310) and / or the external electronic device (305)) registered for a user ID. The Find My Device routine may include an execution condition and an action. In one embodiment, the execution condition may include a user input 2 (e.g., pressing a button twice) via the input module (420) of the hub device (330). In one embodiment, the action may include a control command to ring a sound at the at least one registered user device. In one embodiment, when the hub device (330) is online and the button of the hub device (330) is pressed twice, the hub device (330) may transmit information indicating that the user input 2 is received to the server (350) to cause the server (350) to ring the at least one user device.

[0152] In operation 806, the hub device (330) may detect, via the communication circuit (414), that the connection with the server (350) is lost (e.g., offline). In one embodiment, the hub device (330) may lose connection with the server (350) and become offline when a user moves the hub device (330) to a new location (e.g., an office).

[0153] In operation 808, the hub device (330) may identify that wireless charging of the electronic device (310) has begun by detecting that any external electronic device (e.g., the electronic device (310)) has come into contact with the hub device (330). In one embodiment, the hub device (330) may detect that wireless charging of the electronic device (310) has begun through the wireless charging circuit (418).

[0154] In one embodiment, the hub device (330) may transmit a first wireless signal including a user ID acquired through onboarding to the electronic device (310) via the wireless charging circuit (418) while the electronic device (310) is being wirelessly charged using the wireless charging function of the hub device (330) (e.g., operation 708). The hub device (330) may receive a second wireless signal including a device ID request from the electronic device (310) via the wireless charging circuit (418) (e.g., operation 710) and transmit a third wireless signal including a device ID of the hub device (330) to the electronic device (310) via the wireless charging circuit (418) (e.g., operation 712). The electronic device (310) may perform authentication of the hub device (330) based on the device ID (e.g., operations 714 and 716) and transmit the device ID (e.g., hub ID) and location information of the hub device (330) to the server (350) via the communication circuit (404) (e.g., operation 718).

[0155] In operation 810, the hub device (330) may receive user input 1. In one embodiment, the user input 1 may include an operation of pressing at least one button included in the input module (420) once. In operation 812, the hub device (330) may include information of the user input 1 in a wireless signal (e.g., a fourth wireless signal) and transmit the same to the electronic device (310) through the wireless charging circuit (418) based on the user input 1 being received in an offline state while the electronic device (310) is being wirelessly charged through the hub device (330). The electronic device (310) may identify the user input 1 from the wireless signal received through the wireless charging circuit (408). In operation 814, the electronic device (310) may transmit the hub ID of the hub device (330) and the user input 1 to the server (350). The above hub ID may be obtained from the hub device (330) via a wireless signal after the electronic device (310) starts wireless charging.

[0156] In operation 816, the server (350) may execute a pre-stored automation routine corresponding to the user input 1 based on receiving the user input 1. In operation 818, the server (350) may transmit a control command to cause a designated IoT device (e.g., at least one smart light) according to the automation routine to execute a designated action (e.g., turning off the light).

[0157] In operation 820, the hub device (330) may receive user input 2. In one embodiment, user input 1 may include an operation of pressing at least one button included in the input module (420) twice in succession. In operation 822, the hub device (330) may, based on receiving user input 2 in an offline state, include the user input 2 in a wireless signal and transmit the wireless signal to the electronic device (310) through the wireless charging circuit (418). The electronic device (310) may identify the user input 2 from the wireless signal received through the wireless charging circuit (408). In operation 824, the electronic device (310) may transmit the hub ID of the hub device (330) and the user input 2 to the server (350). The hub ID may be obtained from the hub device (330) through a wireless signal after the electronic device (310) starts wireless charging.

[0158] In operation 826, the server (350) may execute a Find My Device routine corresponding to the user input 2 based on receiving the user input 2. In operation 828, the server (350) may transmit a control command (e.g., a ring instruction) to cause a designated user device (e.g., an external electronic device (305)) according to the Find My Device routine to execute a designated action (e.g., a ring).

[0159] FIG. 9 illustrates a sequence diagram illustrating a procedure for keeping a hub device online through tethering according to one embodiment of the present disclosure. According to embodiments, at least one of the operations described below may be omitted, modified, or executed in a different order.

[0160] Referring to FIG. 9, in operation 902, the hub device (330) may detect a state in which the connection with the server (350) is lost (e.g., offline) through the communication circuit (414). In one embodiment, the hub device (330) may lose connection with the server (350) and become offline when a user moves the hub device (330) to a new location (e.g., an office).

[0161] At operation 904, the hub device (330) may identify that wireless charging of the electronic device (310) has begun by detecting that any external electronic device (e.g., the electronic device (310)) has come into contact with the hub device (330). In one embodiment, the hub device (330) may detect that wireless charging of the electronic device (310) has begun via the wireless charging circuit (418). While performing wireless charging via the hub device (330), the electronic device (310) may perform user ID authentication (e.g., operation 708) and / or device ID authentication (e.g., operations 710, 712, 714, and 716) for the hub device (330).

[0162] In operation 906, the electronic device (310) may establish a wireless communication connection (e.g., a tethering connection) with the hub device (330). In one embodiment, establishing the tethering connection may include an operation in which the electronic device (310) operates in a mobile hotspot mode while broadcasting a beacon signal, and the hub device (330) discovers the electronic device (310) by receiving the beacon signal and establishes a Wi-Fi connection with the electronic device (310). In one embodiment, the electronic device (310) may provide network connection information (e.g., a service set identifier (SSID) and a password) used by the electronic device (310) in the mobile hotspot mode to the hub device (330) using a wireless signal through the wireless charging circuit (408) for the tethering connection. The hub device (330) can obtain an SSID and password from a wireless signal received through the wireless charging circuit (418) and establish a tethering connection with the electronic device (310) using the SSID and password.

[0163] In operation 908, the hub device (330) may be brought online by connecting to the server (350) via a tethering connection with the electronic device (310). While remaining online using the tethering connection, the hub device (330) may control or monitor the status of at least one IoT device (e.g., IoT device (320)). The hub device (330) may use the tethering connection to report the connection status (e.g., online) and location information of the hub device (330) to the server (350), and / or may report status information of at least one IoT device (e.g., IoT device (320) directly connected to the hub device (330)) to the server (350).

[0164] At step 910, the hub device (330) may receive a status report (e.g., sensor data) from the IoT device (320). In one embodiment, the IoT device (320) may transmit the status report to the hub device (330) via a D2D connection or a local network. At steps 912 and 914, the hub device (330) may transmit the status report to the server (350) via the electronic device (310) using a tethering connection.

[0165] In steps 916 and 918, the hub device (330) may receive a control command for the IoT device (320) from the server (350) via the electronic device (310) using a tethering connection. In step 920, the hub device (330) may transmit the control command to the IoT device (320). In one embodiment, the hub device (330) may transmit the control command to the IoT device (320) via a D2D connection with the IoT device (320) or a local network.

[0166] FIG. 10 illustrates a sequence diagram illustrating a procedure for notifying a change in an automated routine in a hub device according to one embodiment of the present disclosure. According to embodiments, at least one of the operations described below may be omitted, modified, or executed in a different order.

[0167] Referring to FIG. 10 , in operation 1002, the hub device (330) may be disconnected from the server (350) and may become offline by moving to a new location (e.g., an office) other than the local network (345) (e.g., a home). In operation 1004, the hub device (330) may establish a D2D connection with at least one IoT device (e.g., a hub-connected IoT device (320)). In one embodiment, the IoT device (320) may be a device that has moved with the hub device (330) in the local network (345) (e.g., IoT devices 320c, 320d)) or a newly discovered device (e.g., IoT devices 320e, 320f)) in a new location (e.g., an office).

[0168] In operation 1006, the hub device (330) may be brought online by connecting to the server (350) using short-range wireless communication technology or long-range wireless communication technology at a new location (e.g., an office). In one embodiment, the hub device (330) may establish a Wi-Fi connection with an AP at the new location and connect to the server (350) through the AP. In one embodiment, the hub device (330) may obtain user authentication of the electronic device (310) through the wireless charging circuit (418) while the electronic device (310) is being charged through the hub device (330) and may be brought online through a tethering connection provided by the electronic device (310).

[0169] In operation 1008, the hub device (330) may periodically or aperiodically transmit the connection status (e.g., online status) and / or location information (e.g., network ID, IP address, and / or geographic location) of the hub device (330) to the server (350) while it is connected to the server (350) (e.g., online status). In operation 1010, the hub device (330) may transmit the connection status (e.g., online status) and / or location information (e.g., network ID, IP address, and / or geographic location) of an IoT device (320) directly connected to the hub device (330) to the server (350). In one embodiment, the hub device (330) may update the server (350) with information (e.g., connection status and / or location information) of at least one newly discovered IoT device (e.g., IoT device (320)) in a new location (e.g., office).

[0170] In operation 1012, the server (350) may notify the electronic device (310) of the movement of the hub device (330) and / or the change in location of the IoT device (320). In one embodiment, the server (350) may transmit to the electronic device (310) information indicating that the hub device (330) has moved to a new location (e.g., an office), location information indicating the new location to which the hub device (330) has moved, information indicating that the location of the IoT device (320) has changed, and / or information indicating that the IoT device (320) is newly connected.

[0171] In operation 1014, the electronic device (310) may display hub movement information through the display (410) based on a notification from the server (350). In one embodiment, the electronic device (310) may display information indicating hub movement (e.g., a pop-up notification) and execute a client application for an IoT service based on receiving a user input (e.g., a touch) through the information. The electronic device (310) may display the hub movement information through the client application. In one embodiment, the hub movement information may include a guidance phrase, "Hub xxx has come online at a different location." In one embodiment, the hub movement information may include a guidance phrase, "IoT device xyz has connected to hub xxx at a new location."

[0172] In operation 1016, the electronic device (310) may transmit an automation list request to the server (350). In operation 1018, the electronic device (310) may receive an automation list including one or more automation routines registered by the user from the server (350). In one embodiment, the automation list may include one or more automation routines generated via the hub device (330).

[0173] In operation 1020, the electronic device (310) may display information of the automation list (e.g., information (1324) of FIG. 13B) through the display (410). In one embodiment, the information of the automation list may indicate the name, execution condition, and / or action of each automation routine. In operation 1022, the electronic device (310) may compare the previously stored location of the hub device (330) with the location information of the hub device (330) received in operation 1012 to determine whether the hub device (330) has moved. If it is determined that the hub device (330) has moved and if the new location of the hub device (330) has not been previously stored in the electronic device (310), operation 1024 may be performed.

[0174] Action 1024 may include actions 1024a and 1024b. In action 1024a, the electronic device (310) may display information suggesting a new automation routine associated with at least one connectable IoT device at a new location (e.g., an office) of the hub device (330) and receive user input for selecting the new automation routine. In one embodiment, the electronic device (310) may determine a new automation routine that includes execution conditions and actions associated with the hub-connected IoT devices that have moved with the hub device (330) and the newly connected IoT devices at the new location of the hub device (330). In action 1024b, the electronic device (310) may transmit a routine creation request representing the new automation routine to the server (350). The routine creation request may include information representing a routine name, execution conditions, and actions of the new automation routine.

[0175] If the hub device (330) has not moved or if the new location of the hub device (330) has been previously stored in the electronic device (310), operation 1026 may be performed. Operation 1026 may include operations 1026a and 1026b. In operation 1026a, the electronic device (310) may display information indicating at least one automation routine available at the current location of the hub device (330) (e.g., an office) and receive a user input selecting to activate the at least one automation routine. In one embodiment, the electronic device (310) may display information of at least one automation routine associated with at least one IoT device that is connectable to or connected to the hub device (330) at the current location of the hub device (330) among a plurality of automation routines previously registered through the hub device (330). In operation 1026b, the electronic device (310) may transmit a routine activation request to the server (350) requesting activation of the selected automation routine. The routine creation request may include information indicating the routine name of the automation routine to be activated.

[0176] FIG. 11 illustrates a sequence diagram illustrating a procedure for activating or deactivating a location-specific automation routine according to one embodiment of the present disclosure. According to embodiments, at least one of the operations described below may be omitted, modified, or executed in a different order.

[0177] Referring to FIG. 11, in operation 1102, the hub device (330) may be disconnected from the server (350) and may become offline by moving to a new location (e.g., an office) other than the local network (345) (e.g., a home). In operation 1104, the hub device (330) may establish a D2D connection with at least one IoT device (e.g., a hub-connected IoT device (320)). In one embodiment, the IoT device (320) may be a device that has moved with the hub device (330) in the local network (345), or may be a newly discovered device in a new location (e.g., an office).

[0178] In operation 1106, the hub device (330) may be brought online by connecting to the server (350) using short-range wireless communication technology or long-range wireless communication technology at a new location (e.g., an office). In one embodiment, the hub device (330) may establish a Wi-Fi connection with an AP at the new location and connect to the server (350) through the AP. In one embodiment, the hub device (330) may be brought online by obtaining user authentication of the electronic device (310) through the wireless charging circuit (418) while the electronic device (310) is being charged through the hub device (330) and connecting to the server (350) through a tethering connection provided by the electronic device (310).

[0179] In operation 1108, the hub device (330) may periodically or aperiodically transmit the connection status (e.g., online status) and / or location information (e.g., network ID, IP address, and / or geographic location) of the hub device (330) to the server (350) while it is connected to the server (350) (e.g., online status). In operation 1110, the hub device (330) may transmit the connection status (e.g., online status) and / or location information (e.g., network ID, IP address, and / or geographic location) of an IoT device (320) directly connected to the hub device (330) to the server (350). In one embodiment, the hub device (330) may update the server (350) with information (e.g., connection status and / or location information) of at least one newly discovered IoT device (e.g., IoT device (320)) in a new location (e.g., office).

[0180] In operation 1112, the server (350) may generate at least one automation routine available at a new location (e.g., an office) of the hub device (330) based on identifying movement of the hub device (330) and / or change in location of the IoT device (320). In one embodiment, the server (350) may generate at least one new automation routine associated with at least one IoT device connectable at the new location (e.g., an office) of the hub device (330). In one embodiment, the server (350) may determine to activate a pre-registered automation routine (e.g., inactivated) if one is stored for the new location.

[0181] In operation 1114, the server (350) may determine to deactivate at least one automation routine associated with a previous location (e.g., home) of the hub device (330) among a plurality of previously registered automation routines. In one embodiment, the server (350) may deactivate at least one automation routine associated with at least one IoT device that has gone offline due to movement of the hub device (330).

[0182] In operation 1116, the server (350) may transmit an automation list including at least one new automation routine and at least one deactivated automation routine to the hub device (330). In one embodiment, the automation list may include newly created automation routines, activated automation routines, and / or deactivated automation routines. The hub device (330) may store the automation list and control a related IoT device (e.g., IoT device (320)) according to at least one automation routine included in the automation list.

[0183] In operation 1118, the server (350) may transmit an automation list including the at least one new automation routine and the at least one disabled automation routine to the electronic device (310). In operation 1120, the electronic device (310) may display information of the automation list through the display (410). In one embodiment, the electronic device (310) (e.g., the processor (402)) may include information indicating activation or deactivation of each automation routine in the information of the automation list (e.g., information (1422) of FIG. 14B or information (1442) of FIG. 14D). In one embodiment, the electronic device (310) (e.g., the processor (402)) may display information (e.g., shading) indicating that a specific automation routine associated with at least one IoT device directly connected to the hub device (330) is disabled, together with the information of the automation list, based on hub movement information.

[0184] In one embodiment, the electronic device (310) may display information (e.g., information (1420) of FIG. 14c) of at least one deactivated automation routine based on the automation list. In one embodiment, the electronic device (310) may display information (e.g., information (1422) of FIG. 14b) indicating that at least one IoT device (e.g., IoT device (320)) has been moved based on the automation list. In one embodiment, the electronic device (310) may display information (e.g., information (1430) of FIG. 14c) of at least one automation routine that is available at a new location (e.g., an office) of the hub device (330) based on the automation list.

[0185] FIG. 12 illustrates a sequence diagram illustrating a procedure for setting up a location-specific automation routine according to one embodiment of the present disclosure. According to embodiments, at least one of the operations described below may be omitted, modified, or executed in a different order.

[0186] Referring to FIG. 12, in operation 1202, the hub device (330) may be brought online after being onboarded (e.g., registered with the server (350)). In operation 1204, the hub device (330) may periodically or aperiodically transmit the connection status (e.g., online) and location information of the hub device (330) to the server (350) while in the online state. In one embodiment, the hub device (330) may report the connection status (e.g., online) and location information (e.g., home) of at least one IoT device (e.g., hub-connected IoT devices (320c, 320d)) connected to the hub device (330) while in the online state to the server (350). The server (350) may manage the connection status and location information of the hub device (330) and each IoT device.

[0187] In operation 1206, a user device (e.g., electronic device (310)) may transmit a routine generation request including information of an automation routine (e.g., a home automation routine) to be used at a current location (e.g., home) of the hub device (330) to a server (350) via the hub device (330). In one embodiment, the electronic device (310) may generate an automation routine including execution conditions and actions related to at least one IoT device (e.g., IoT devices (320a, 320b)) installed at a current location (e.g., home) of the hub device (330) and / or at least one IoT device (e.g., IoT devices (320c, 320d)) directly connected to the hub device (330).

[0188] In operation 1208, the server (350) may store the automation routine (e.g., a home automation routine) based on the routine creation request and transmit information of the automation routine to the hub device (330). The hub device (330) may store the automation routine (e.g., execution conditions and actions). In one embodiment, the execution conditions may include a specified user input1 (e.g., pressing a button) via the input module (420) of the hub device (330), and the action may include a control command for at least one IoT device (e.g., IoT device1 (320c)) within the current location.

[0189] In operation 1210, the hub device (330) may receive user input 1 (e.g., button pressing) specified by the execution condition while being online. In operation 1212, the hub device (330) may transmit a hub ID identifying the hub device (330) and information on the user input 1 to the server (350). Based on the fact that the current location of the hub device (330) is home, the server (350) may identify an action of an IoT device (e.g., IoT device 1 (320c) located at home) corresponding to the user input 1 from information on an automation routine set for the home (e.g., a home automation routine) in operation 1206. In one embodiment, instead of transmitting information on the user input 1 in operation 1212, the hub device (330) may identify an action of the IoT device 1 (320c) corresponding to the user input 1 based on the home automation routine and transmit information on the identified action to the server (350).

[0190] In operation 1214, the server (350) may transmit a control command instructing the IoT device 1 (320c) to execute the above action. In one embodiment, the server (350) may receive an execution result according to the control command from the IoT device 1 (320c) and transmit the execution result to the hub device (330) and / or the electronic device (310). In one embodiment, the IoT device 1 (320c) is a smart light, and the control command may instruct a light-off action.

[0191] In operation 1216, the hub device (330) may be brought online by moving to a new location (e.g., an office) other than the local network (345) (e.g., a home) and connecting to the server (350) using short-range wireless communication technology or long-range wireless communication technology at the new location. In one embodiment, the hub device (330) may establish a Wi-Fi connection with an AP at the new location and connect to the server (350) through the AP. In one embodiment, the hub device (330) may be brought online by obtaining user authentication of the electronic device (310) through the wireless charging circuit (418) while the electronic device (310) is being charged through the hub device (330) and connecting to the server (350) through a tethering connection provided by the electronic device (310).

[0192] In operation 1218, the hub device (330) may transmit the connection status (e.g., online) and location information (e.g., office) of the hub device (330) in a new location to the server (350). The hub device (330) may report the connection status (e.g., online) and location information (e.g., office) of at least one IoT device (e.g., hub-connected IoT devices (320c, 320d)) connected to the hub device (330) while in an online state to the server (350). The server (350) may manage the connection status (e.g., online) and location information (e.g., office) of the hub device (330) and each IoT device.

[0193] In operation 1220, a user device (e.g., electronic device (310)) may transmit a routine generation request including information of an automation routine (e.g., an office automation routine) to be used at a new location (e.g., an office) of the hub device (330) to a server (350) via the hub device (330). In one embodiment, the electronic device (310) may generate the automation routine including execution conditions and actions related to at least one IoT device (e.g., IoT devices (320e, 320f)) installed at the new location (e.g., an office) of the hub device (330) and at least one IoT device (e.g., IoT devices (320c, 320d)) directly connected to the hub device (330).

[0194] In operation 1222, the server (350) may store the automation routine (e.g., office automation routine) based on the routine creation request and transmit information of the automation routine to the hub device (330). The hub device (330) may store the automation routine (e.g., execution conditions and actions). In one embodiment, the execution conditions may include a specified user input1 (e.g., pressing a button) via the input module (420) of the hub device (330), and the action may include a control command for at least one IoT device (e.g., IoT device2 (320e)) within the new location (e.g., office).

[0195] In operation 1224, the hub device (330) may receive user input 1 (e.g., button pressing) specified by the execution condition while being online. In operation 1226, the hub device (330) may transmit a hub ID identifying the hub device (330) and information on the user input 1 to the server (350). Based on the fact that the current location of the hub device (330) is an office, the server (350) may identify an action of an IoT device (e.g., an IoT device 2 (320e) located in an office) corresponding to the user input 1 from information on an automation routine (e.g., an office automation routine) set for an office in operation 1220. In one embodiment, instead of transmitting information on the user input 1 in operation 1226, the hub device (330) may identify an action of an IoT device 2 (320e) corresponding to the user input 1 based on an office automation routine and transmit information on the identified action to the server (350).

[0196] In operation 1228, the server (350) may transmit a control command instructing the IoT device 2 (320e) to execute the above action. In one embodiment, the server (350) may receive an execution result according to the control command from the IoT device 2 (320e) and transmit the execution result to the hub device (330) and / or the electronic device (310). In one embodiment, the IoT device 1 (320c) is a PC, and the control command may instruct power on / off.

[0197] In one embodiment, the server (350) may receive the same user input 1 information from the hub device (330) in operations 1210 and 1224, but may determine to control different IoT devices (e.g., IoT device 1 (320c) or IoT device 2 (320e)) depending on the current location (home or office) of the hub device (330). In one embodiment, the hub device (330) may receive the same user input 1 in operations 1210 and 1224, but may request the server (350) to control different IoT devices (e.g., IoT device 1 (320c) or IoT device 2 (320e)) depending on the current location (home or office) of the hub device (330).

[0198] In operation 1230, the hub device (330) may return to the local network (345) (e.g., home) and then become online by connecting to the server (350) via the AP (340) in the local network (345). In operation 1232, the hub device (330) may transmit the connection status (e.g., online) and location information (e.g., home) of the hub device (330) in the local network (345) to the server (350).

[0199] In operation 1234, the hub device (330) may select automation routines to activate and / or deactivate based on its connection to an AP (340) of a local network (345). In one embodiment, the hub device (330) may select at least one automation routine to activate and / or at least one automation routine to deactivate based on the current location of the hub device (330). In one embodiment, the hub device (330) may determine to deactivate an office automation routine and activate a home automation routine within the local network (345). In one embodiment, the hub device (330) may determine to deactivate an office automation routine and activate a home automation routine based on a user input via an electronic device (310). In one embodiment, the electronic device (310) may transmit information to the hub device (330) via the wireless charging circuit (408) to instruct the hub device (330) to deactivate the office automation routine and activate the home automation routine based on authenticating the hub device (330) and detecting movement of the hub device (330).

[0200] At operation 1236, the hub device (330) may transmit a routine activation / deactivation request indicating the deactivated office automation routine and / or the activated home automation routine to the server (350). The server (350) may store the deactivated office automation routine and / or the activated home automation routine based on the received information. At operation 1238, the server (350) may transmit a routine activation / deactivation notification indicating the deactivated office automation routine and / or the activated home automation routine to a user device (e.g., electronic device (310)).

[0201] FIGS. 13a, 13b, 13c, and 13d illustrate examples of a user interface for notifying offline status of a hub device according to one embodiment of the present disclosure.

[0202] Referring to FIG. 13A, the electronic device (310) may display offline reason information (1310) of the hub device (330) through the display (410) based on detecting movement of the hub device (330) having a wireless charging function through the wireless charging circuit (408). In one embodiment, the electronic device (310) may receive connection status information of the hub device (330) from the server (350) and display offline reason information (1310) based on the connection status information including an offline reason (e.g., movement of the hub device (330). In one embodiment, the offline reason information (1310) may include a guidance phrase indicating movement of the hub device (330), for example, "The hub has moved to another location, so IoT devices cannot connect."

[0203] Referring to FIG. 13B, the electronic device (310) may display a screen (1320) including routine deactivation information (1322) and information (1324) of an automation list received from a server (350) through the display (410) based on identifying movement of the hub device (330). In one embodiment, the routine deactivation information (1322) may include a guidance phrase indicating that at least one automation routine is deactivated due to movement of the hub device (330), for example, “The routine (automation) may be deactivated because the hub has moved to another location.” In one embodiment, the information (1324) of the automation list may include a list of at least one automation routine that can be executed through the hub device (330) (for example, a routine name, an execution condition, and / or an action). The electronic device (310) may receive a user input for selecting activation or deactivation of each automation routine through the information (1324) of the list.

[0204] Referring to FIG. 13C, the electronic device (310) may display information (1330) suggesting at least one new automation routine executable at a new location of the hub device (330) based on identifying movement of the hub device (330) and information (1332) of an automation list including the at least one new automation routine. In one embodiment, the information (1330) may include guidance text notifying that routines are added or activated due to the movement of the hub device (330), for example, “The hub has moved to a different location. A new routine may be added, or the routines below may be activated.” In one embodiment, the information (1332) of the automation list may include at least one new automation routine (e.g., “water leak alarm”) suggested by the electronic device (310) for the new location of the hub device (330).

[0205] Referring to FIG. 13d, the electronic device (310) may display information (1340) guiding an automation routine configured for each location based on identifying movement of the hub device (330) and information (1342) indicating at least one IoT device (e.g., IoT devices (320c, 320d, 320e, 320f)) connectable at the new location of the hub device (330). In one embodiment, the information (1340) may include a guidance phrase notifying that there is an IoT device connectable at the moved location, for example, “Create automation using devices connected at the moved location.” In one embodiment, the information (1342) may include a device name, a model name, and / or a device image of at least one IoT device connectable with the hub device (330) at the new location (330).

[0206] FIGS. 14A, 14B, 14C, and 14D illustrate examples of a user interface for notifying deactivation of a location-specific automation routine according to one embodiment of the present disclosure.

[0207] Referring to FIG. 14A, the electronic device (310) may display device list information (1410) for a first location (e.g., home) of the hub device (330). In one embodiment, the device list information (1410) may include a list (1412) of one or more IoT devices available at the first location, e.g., a hub, a multi-purpose sensor, an arrival sensor, a dome valve, and a living room light. The electronic device (310) may display the status of each IoT device through each of the objects, and / or receive a user input to execute an action.

[0208] Referring to FIG. 14B, the electronic device (310) may display deactivated device list information (1420) to indicate that automation of the first location is deactivated based on identifying that the hub device (330) has moved from a first location (e.g., home) to a second location (e.g., office). In one embodiment, the deactivated device list information (1420) may include shaded objects of each of one or more IoT devices. In one embodiment, the deactivated device list information (1420) may include device movement information (1422) indicating that at least one IoT device (e.g., hub, multi-purpose sensor, and arrival sensor) has moved. In one embodiment, the device movement information (1422) may include a guidance phrase indicating that each IoT device has moved, for example, "Moved."

[0209] Referring to FIG. 14C, the electronic device (310) may display device list information (1430) for the second location based on identifying that the hub device (330) has moved from a first location (e.g., home) to a second location (e.g., office). In one embodiment, the device list information (1430) may include a list (1432) of one or more IoT devices available at the second location, such as a hub, a multi-purpose sensor, an arrival sensor, a dome valve, and a living room light. The electronic device (310) may display the status of each IoT device through each of the objects, and / or receive user input to execute an action.

[0210] Referring to FIG. 14D , the electronic device (310) may display device list information (1440) to indicate that automation of the first location is partially disabled based on identifying that the hub device (330) has moved from a first location (e.g., home) to a second location (e.g., office). In one embodiment, the device list information (1440) may include a list (1442) of objects of one or more IoT devices that are available or unavailable at the first location, such as a hub, a multi-purpose sensor, an arrival sensor, a dome valve, and a living room light. In one embodiment, the electronic device (310) may include device movement information (1442) of at least one IoT device (e.g., the hub, the multi-purpose sensor, and the arrival sensor) that has gone offline due to movement. In one embodiment, the device movement information (1442) may include a shaded object of at least one IoT device that has gone offline. In one embodiment, the device movement information (1442) may include a guidance phrase indicating that each IoT device has moved, for example, “Moved.”

[0211] An electronic device (310) according to one embodiment of the present disclosure may include a communication circuit (404), a memory (406) for storing instructions, a wireless charging circuit (408), and a processor (402) connected to the communication circuit, the memory, and the wireless charging circuit. The instructions, when executed by the processor, may cause the electronic device to receive a wireless signal including a device identifier (ID) from a hub device (330) through the wireless charging circuit while the electronic device is being charged from the hub device through the wireless charging circuit. The instructions, when executed by the processor, may cause the electronic device to transmit the device ID and location information of the hub device to a server through the communication circuit. The location information of the hub device may include location information of the electronic device. The instructions, when executed by the processor, may cause the electronic device to receive information on a connection status between the hub device and the server from the server through the communication circuit. The above instructions, when executed by the processor, may cause the electronic device to display, through the display (410), information related to a change in the location of the hub device and information related to the online / offline status of at least one of the hub device or one or more Internet of Things (IoT) devices operatively coupled with the hub device, based on the information about the connection status.

[0212] In one embodiment, the instructions, when executed by the processor, may cause the electronic device to display a pop-up notification indicating that the hub device or at least one of the one or more IoT devices is offline due to movement of the hub device.

[0213] In one embodiment, the instructions, when executed by the processor, may cause the electronic device to transmit a device ID authentication request including the device ID to the server via the communication circuitry, and to receive a device ID authentication response from the server via the communication circuitry, the device ID authentication response indicating that the hub device has been authenticated.

[0214] In one embodiment, the instructions, when executed by the processor, may cause the electronic device to identify at least one hub-connected Internet of Things (IoT) device connected to the hub device, identify that the at least one hub-connected IoT device is offline based on a change in location of the hub device, identify that at least one automation routine associated with the at least one hub-connected IoT device is deactivated, and display deactivation reason information indicating that the at least one automation routine is deactivated due to a change in location of the hub device.

[0215] In one embodiment, the instructions, when executed by the processor, may cause the electronic device to receive, from the hub device through the wireless charging circuit, user input information indicating that the hub device has received a user input related to a designated action of at least one IoT device while the electronic device is being charged from the hub device through the wireless charging circuit, and to transmit the device ID and the user input information to the server through the communication circuit so as to cause the server to control the at least one IoT device to perform the designated action.

[0216] In one embodiment, the instructions, when executed by the processor, may cause the electronic device to establish a wireless communication connection between the electronic device and the hub device through the communication circuit while the electronic device is being charged from the hub device through the wireless charging circuit, such that the hub device connects to the server using the wireless communication connection.

[0217] In one embodiment, information related to a change in the location of the hub device indicates that the hub device has moved, and the one or more IoT devices may include hub-connected devices that are directly connected to the hub device wirelessly or by wire.

[0218] In one embodiment, the instructions, when executed by the processor, may cause the electronic device to update or generate at least one automated routine, each of which includes an execution condition and an action associated with at least one IoT device, based on a change in the location of the hub device.

[0219] A hub device (330) according to one embodiment of the present disclosure may include a communication circuit (414), a memory (416) for storing instructions, a wireless charging circuit (418), and a processor (412) connected to the communication circuit, the memory, and the wireless charging circuit. The instructions, when executed by the processor, may cause the hub device to detect, through the communication circuit, that the hub device is in an offline state where it is disconnected from a server (350) after onboarding to the server. The instructions, when executed by the processor, may cause the hub device to transmit, through the wireless charging circuit, a first wireless signal including a user ID acquired through the onboarding to the electronic device (310) in the offline state based on detecting that the electronic device (310) is being charged using the wireless charging function of the hub device (330). The instructions, when executed by the processor, may cause the hub device to receive, through the wireless charging circuit, a second wireless signal including a device ID request from the electronic device. The instructions, when executed by the processor, may cause the hub device to transmit a third wireless signal including a device ID of the hub device to the electronic device via the wireless charging circuit. The instructions, when executed by the processor, may cause the hub device to transmit a fourth wireless signal including information of the user input to the electronic device via the wireless charging circuit based on identifying that the electronic device receives a user input via an input module of the hub device in the offline state while the electronic device is being charged from the hub device via the wireless charging circuit of the hub device.

[0220] In one embodiment, the instructions, when executed by the processor, may cause the hub device to store in the memory an automation routine including execution conditions and actions related to at least one IoT device, detect movement of the hub device, determine whether the automation routine is available at a new location to which the hub device has moved, and if the automation routine is not available, transmit information to the server indicating that the automation routine is deactivated.

[0221] A method of operating an electronic device (310) according to an embodiment of the present disclosure may include an operation (506) of receiving a wireless signal including a device identifier (ID) from a hub device (330) through a wireless charging circuit (408) while the electronic device is being charged from the hub device (330) through the wireless charging circuit. The method may include an operation (512) of transmitting the device ID and location information of the hub device to a server through a communication circuit, wherein the location information of the hub device may include location information of the electronic device. The method may include an operation (518) of receiving information on a connection status between the hub device and the server from the server through the communication circuit. The method may include an operation (520) of displaying, through a display (410), information related to a change in location of the hub device and information related to online / offline status of at least one of the hub device or one or more IoT devices operatively coupled with the hub device, based on the information on the connection status.

[0222] In one embodiment, the method may include displaying a pop-up notification indicating that the hub device or at least one of the one or more IoT devices is offline due to movement of the hub device.

[0223] In one embodiment, the method may include transmitting a device ID authentication request including the device ID to the server via the communication circuit, and receiving a device ID authentication response from the server via the communication circuit indicating that the hub device has been authenticated.

[0224] In one embodiment, the method may include identifying at least one hub-connected internet of things (IoT) device connected to the hub device, identifying that the at least one hub-connected IoT device is offline based on a change in location of the hub device, identifying that at least one automation routine associated with the at least one hub-connected IoT device is deactivated, and displaying deactivation reason information indicating that the at least one automation routine is deactivated due to a change in location of the hub device.

[0225] In one embodiment, the method may include receiving user input information from the hub device through the wireless charging circuit, wherein the hub device has received a user input related to a designated action of at least one IoT device while the electronic device is being charged from the hub device through the wireless charging circuit, and transmitting the device ID and the user input information to the server through the communication circuit so as to cause the server to control the at least one IoT device to perform the designated action.

[0226] In one embodiment, the method may establish a wireless communication connection between the electronic device and the hub device through the communication circuit while the electronic device is being charged from the hub device through the wireless charging circuit, thereby allowing the hub device to connect to the server using the wireless communication connection.

[0227] In one embodiment, information related to a change in the location of the hub device indicates that the hub device has moved, and the one or more IoT devices may include hub-connected devices that are directly connected to the hub device wirelessly or by wire.

[0228] In one embodiment, the method may include updating or generating at least one automated routine, each of which includes an execution condition and an action associated with at least one IoT device, based on a change in the location of the hub device.

[0229] A method of operating a hub device (330) according to one embodiment of the present disclosure may include an operation (704) of detecting, through a communication circuit (414), that the hub device is in an offline state where it is disconnected from the server (350) after onboarding to the server. The method may include an operation (708) of transmitting a first wireless signal including a user ID acquired through the onboarding to the electronic device through a wireless charging circuit (418). The method may include an operation (710) of receiving a second wireless signal including a device ID request from the electronic device through the wireless charging circuit. The method may include an operation (712) of transmitting a third wireless signal including a device ID of the hub device to the electronic device through the wireless charging circuit. The method may include an operation (812) of transmitting a fourth wireless signal including information of the user input to the electronic device through the wireless charging circuit, based on identifying that the electronic device receives a user input through an input module of the hub device in the offline state while being charged from the hub device through the wireless charging circuit of the hub device.

[0230] In one embodiment of the present disclosure, a non-transitory computer-readable storage medium storing one or more programs may be provided, wherein the one or more programs, when executed by at least one processor (402) of an electronic device (310), cause the electronic device to receive a wireless signal including a device identifier (ID) from the hub device (330) through the wireless charging circuit (408) while the electronic device is being charged from the hub device (330) through the wireless charging circuit, authenticate the hub device based on the device ID, receive location information of the hub device including location information of the electronic device, receive information on a connection status between the hub device and the server from the server through the communication circuit, and display, based on the information on the connection status, information related to a change in the location of the hub device and information related to an online / offline status of at least one of the hub device or one or more IoT devices operatively coupled with the hub device through a display (410).

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

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

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

[0234] Various embodiments of the present document may be implemented as software (e.g., a program (240)) including one or more instructions stored in a storage medium (e.g., an internal memory (236) or an external memory (238)) readable by a machine (e.g., an electronic device (201)). For example, a processor (e.g., a processor (220)) of the machine (e.g., an electronic device (201)) 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.

[0235] 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., compact disc read-only memory (CD-ROM)) or may be provided through an application store (e.g., Play Store). TM ) or directly between two user devices (e.g., smart phones), online distribution (e.g., downloading or uploading). In the case of online distribution, at least a portion of the computer program product may be at least temporarily stored or temporarily created in a machine-readable storage medium, such as the memory of a manufacturer's server, an application store's server, or an intermediary server.

[0236] 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 an electronic device (310), Communication circuit (404); Memory (406) for storing instructions; Wireless charging circuit (408); and At least one processor (402) connected to the communication circuit, the memory and the wireless charging circuit, wherein the instructions, when individually or collectively executed by the at least one processor, cause the electronic device to: While the electronic device is being charged from the hub device (330) through the wireless charging circuit, a wireless signal including a device ID (identifier) ​​is received from the hub device through the wireless charging circuit, The device ID and the location information of the hub device are transmitted to the server (350) through the communication circuit, and the location information of the hub device includes the location information of the electronic device. Receive information about the connection status between the above hub device and the above server from the server through the communication circuit, An electronic device that displays, based on information about the connection status, information related to a change in the location of the hub device and information related to online / offline status of at least one of the hub device or one or more IoT (internet of things) devices operatively coupled with the hub device through a display (410).

2. In the first paragraph, the instructions, when individually or collectively executed by the at least one processor, cause the electronic device to: An electronic device that causes the hub device or at least one of the one or more IoT devices to display a pop-up notification indicating that the hub device is offline due to movement of the hub device.

3. In the first or second paragraph, the instructions, when individually or collectively executed by the at least one processor, cause the electronic device to: Transmitting a device ID authentication request including the above device ID to the server through the above communication circuit, An electronic device that receives a device ID authentication response from the server via the communication circuit indicating that the hub device has been authenticated.

4. In any one of paragraphs 1 to 3, the instructions, when individually or collectively executed by the at least one processor, cause the electronic device to: Identifying at least one hub-connected Internet of Things (IoT) device connected to said hub device; Identifying that at least one hub-connected IoT device is offline based on a change in the location of said hub device, Identifying that at least one automation routine associated with said at least one hub-connected IoT device is disabled; An electronic device that displays deactivation reason information indicating that at least one automated routine is deactivated due to a change in the position of said hub device.

5. In any one of paragraphs 1 to 4, the instructions, when individually or collectively executed by the at least one processor, cause the electronic device to: While the electronic device is being charged from the hub device through the wireless charging circuit, the hub device receives user input information from the hub device through the wireless charging circuit, indicating that the hub device has received a user input related to a designated action of at least one IoT device; An electronic device that transmits the device ID and the user input information to the server through the communication circuit so as to cause the server to control the at least one IoT device to perform the designated action.

6. In any one of paragraphs 1 to 5, the instructions, when individually or collectively executed by the at least one processor, cause the electronic device to: An electronic device that establishes a wireless communication connection between the electronic device and the hub device through the communication circuit while the electronic device is being charged from the hub device through the wireless charging circuit, thereby allowing the hub device to connect to the server using the wireless communication connection.

7. An electronic device according to any one of claims 1 to 6, wherein the information related to the change in position of the hub device indicates that the hub device has moved, and wherein the one or more IoT devices include hub-connected devices that are directly connected to the hub device wirelessly or by wire.

8. In any one of paragraphs 1 to 7, the instructions, when individually or collectively executed by the at least one processor, cause the electronic device to: An electronic device that updates or generates at least one automated routine, each of which includes an execution condition and an action associated with at least one IoT device, based on a change in the location of the hub device.

9. In the hub device (330), Communication circuit (414); Memory (416) for storing commands; Wireless charging circuit (418); and At least one processor (412) connected to the communication circuit, the memory and the wireless charging circuit, wherein the instructions, when individually or collectively executed by the at least one processor, cause the hub device to: After onboarding to the server (350), the hub device detects through the communication circuit that it is in an offline state with the connection with the server disconnected, Based on detecting that the electronic device (310) is being charged using the wireless charging function of the hub device (330), a first wireless signal including the user ID acquired through the onboarding in the offline state is transmitted to the electronic device through the wireless charging circuit, receiving a second wireless signal including a device ID request from the electronic device through the wireless charging circuit; Transmitting a third wireless signal including a device ID of the hub device to the electronic device through the wireless charging circuit; A hub device that, based on identifying that a user input is received through an input module of the hub device in the offline state while the electronic device is being charged from the hub device through the wireless charging circuit of the hub device, transmits a fourth wireless signal including information of the user input to the electronic device through the wireless charging circuit.

10. In the 9th paragraph, the instructions, when individually or collectively executed by the at least one processor, cause the hub device to: storing in said memory an automation routine including execution conditions and actions related to at least one IoT device; Detecting movement of the above hub device, Determine whether said automation routine is available at the new location to which said hub device has moved; A hub device that transmits information to the server indicating that the automation routine is disabled when the automation routine is not available.

11. In the operating method of an electronic device (310), An operation of receiving a wireless signal including a device ID (identifier) ​​from the hub device (330) through the wireless charging circuit (506) while the electronic device is being charged from the hub device (330) through the wireless charging circuit (502); An operation (512) of transmitting the device ID and location information of the hub device to a server through a communication circuit, the location information of the hub device including location information of the electronic device; An operation (518) of receiving information on the connection status between the hub device and the server from the server through the communication circuit; and A method comprising the operation (520) of displaying, through a display (410), information related to a change in location of the hub device and information related to online / offline status of at least one of the hub device or one or more IoT devices operatively coupled with the hub device, based on information about the connection status.

12. In paragraph 11, A method comprising the action of displaying a pop-up notification indicating that at least one of the hub device or the one or more IoT devices is offline due to movement of the hub device.

13. In clause 11 or 12, An operation of transmitting a device ID authentication request including the device ID to the server through the communication circuit; and A method comprising the action of receiving a device ID authentication response from the server via the communication circuit indicating that the hub device has been authenticated.

14. In any one of paragraphs 11 to 13, An action to identify at least one hub-connected internet of things (IoT) device connected to said hub device; An action of identifying that at least one hub-connected IoT device is offline based on a change in location of said hub device; An action to identify that at least one automation routine associated with said at least one hub-connected IoT device is disabled; and A method comprising the action of displaying deactivation reason information indicating that at least one automated routine is deactivated due to a change in the position of the hub device.

15. In the operating method of the hub device (330), After onboarding to the server (350), the operation of detecting through the communication circuit (414) that the hub device is in an offline state where the connection with the server is lost; An operation of transmitting a first wireless signal including a user ID acquired through the onboarding in the offline state to the electronic device (310) through the wireless charging circuit (418) based on detecting that the electronic device (310) is being charged using the wireless charging function of the hub device (330); An operation of receiving a second wireless signal from the electronic device via the wireless charging circuit, the second wireless signal including a device ID request; An operation of transmitting a third wireless signal including a device ID of the hub device to the electronic device through the wireless charging circuit; A method comprising: transmitting a fourth wireless signal including information of the user input to the electronic device through the wireless charging circuit, based on identifying that the electronic device receives a user input through an input module of the hub device in the offline state while the electronic device is being charged from the hub device through the wireless charging circuit of the hub device.

Images