Electronic device for managing internet of things device and operation method of therefor

MYPI2025000039A0Undetermined Publication Date: 2024-02-26SAMSUNG ELECTRONICS CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
MYPI2025000039
Authority / Receiving Office
MY · MY
Patent Type
Applications
Current Assignee / Owner
Priority Date
2022-09-14
Filing Date
2023-06-29
Publication Date
2024-02-26

AI Technical Summary

Technical Problem

The existing methods for managing and onboarding Internet of Things (IoT) devices are complex and inefficient, particularly in connecting multiple IoT devices to a server through a hub device, leading to inconvenience for users and manufacturers.

Method used

An electronic device with a communication circuit and processor is configured to obtain installation data for IoT devices, perform onboarding procedures, transmit data, display installation guides, and receive onboarding results, simplifying the process of registering IoT devices with a server through a hub device.

Benefits of technology

This solution streamlines the onboarding process for IoT devices, enhancing user convenience and reducing manufacturing complexities by automating the connection and registration of multiple IoT devices to an IoT environment.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure PI2025000039_DRAWING_001
    Figure PI2025000039_DRAWING_001
  • Figure PI2025000039_DRAWING_002
    Figure PI2025000039_DRAWING_002
  • Figure PI2025000039_DRAWING_003
    Figure PI2025000039_DRAWING_003
Patent Text Reader

Abstract

Disclosed is an electronic device comprising a communication circuit and at least one processor operatively coupled to the communication circuit. The at least one processor may be configured to: obtain installation data required for a first external electronic device to register at least one second external electronic device with a server; perform a first onboarding procedure for registering the first external electronic device with the server; after performing the first onboarding procedure, transmit the installation data to the first external electronic device; display an installation guide for onboarding the at least one second external electronic device on the basis of the installation data; and receive, from the server, an onboarding result indicating that the at least one second external electronic device has been onboarded by the first external electronic device. Fig. 6
Need to check novelty before this filing date? Find Prior Art

Description

Electronic device for managing Internet of Things devices and method of operation thereof

[0001] Embodiments of the present disclosure relate to an electronic device for managing Internet of Things (IoT) devices and a method of operating the same.

[0002] The variety of services and additional features offered through user terminals, such as smartphones, is steadily increasing. 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 offering a variety of functions. Consequently, the various functions offered through these devices are also becoming increasingly sophisticated.

[0003] As wireless communication technology advances, devices utilizing artificial intelligence (AI) are becoming more widely adopted. For example, home appliances connected to the Internet of Things (IoT) can utilize AI. IoT technology can collect and analyze data generated by these devices to provide intelligent Internet technology services that create new value in human lives. 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] Meanwhile, homes are equipped with a variety of home appliances for the convenience of users, and services are being proposed that utilize IoT technology to facilitate the operation and control of these appliances. Home network technology can provide various services to users within the home via the home network. For example, users can control controlled devices (e.g., IoT-enabled home appliances) within the home network using personal electronic devices (e.g., smartphones). Users can receive various services through these controlled devices.

[0005] Embodiments of the present disclosure may onboard one or more controlled devices (e.g., IoT devices).

[0006] Embodiments of the present disclosure may provide an electronic device and a method of operating the same for onboarding one or more IoT devices to a server via a hub device.

[0007] 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 can be clearly understood by a person having ordinary skill in the technical field to which the present invention belongs from the description below.

[0008] An electronic device according to one embodiment may include a communication circuit and at least one processor operatively connected to the communication circuit. The at least one processor may be configured to obtain installation data required for a first external electronic device to register at least one second external electronic device with a server. The at least one processor may be configured to perform a first onboarding procedure for registering the first external electronic device with the server via the communication circuit. The at least one processor may be configured to transmit the installation data to the first external electronic device via the communication circuit after performing the first onboarding procedure. The at least one processor may be configured to display an installation guide for onboarding the at least one second external electronic device based on the installation data. The at least one processor may be configured to receive an onboarding result from the server via the communication circuit, the onboarding result indicating that the at least one second external electronic device has been onboarded by the first external electronic device.

[0009] A method of operating an electronic device according to one embodiment may include an operation in which a first external electronic device obtains installation data necessary for registering at least one second external electronic device with a server. The method may include an operation in which a first onboarding procedure is performed to register the first external electronic device with the server. The method may include an operation in which the installation data is transmitted to the first external electronic device after performing the first onboarding procedure. The method may include an operation in which an installation guide is displayed for onboarding the at least one second external electronic device based on the installation data. The method may include an operation in which an onboarding result indicating that the at least one second external electronic device has been onboarded by the first external electronic device is received from the server.

[0010] A non-transitory computer-readable storage medium storing one or more programs according to one embodiment, wherein the one or more programs may include instructions that, when executed by at least one processor of the electronic device, cause the electronic device to: obtain installation data required for a first external electronic device to register at least one second external electronic device with a server; perform a first onboarding procedure for registering the first external electronic device with the server; transmit the installation data to the first external electronic device after performing the first onboarding procedure; display an installation guide for onboarding the at least one second external electronic device based on the installation data; and receive an onboarding result from the server indicating that the at least one second external electronic device has been onboarded by the first external electronic device.

[0011] FIG. 1 illustrates an IoT (internet of things) system according to one embodiment.

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

[0013] FIG. 3 is a diagram illustrating a network including IoT devices according to one embodiment.

[0014] FIG. 4 is a block diagram illustrating the internal configuration of a hub device (330) according to one embodiment.

[0015] FIG. 5 is a diagram illustrating a procedure for registering IoT devices according to one embodiment.

[0016] FIG. 6 is a flowchart illustrating the operation of an electronic device for registering IoT devices according to one embodiment.

[0017] FIG. 7 is a flowchart illustrating the operation of a hub device that registers IoT devices according to one embodiment.

[0018] FIG. 8 illustrates an example of a signal flow diagram that provides fast connection of IoT devices according to one embodiment.

[0019] FIG. 9 is a flowchart illustrating the operation of a hub device that registers IoT devices according to one embodiment.

[0020] FIG. 10 illustrates an example of a signal flow diagram that provides fast connection of IoT devices according to one embodiment.

[0021] FIG. 11 is a signal flow diagram illustrating a hub onboarding procedure according to one embodiment.

[0022] FIG. 12 is a diagram for explaining an IoT environment including a hub device according to one embodiment.

[0023] FIG. 13 is a diagram for explaining an IoT environment that does not include a hub device according to one embodiment.

[0024] FIG. 1 illustrates an Internet of Things (IoT) system (100) according to one embodiment. 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0059] FIG. 3 is a diagram illustrating a network including IoT devices according to one embodiment.

[0060] Referring to FIG. 3, a network (300) may include a server (310) operating as an IoT cloud, an electronic device (201) communicating with the server (310) via network communication (e.g., the Internet), and at least one external electronic device (320) supporting IoT technology (e.g., IoT devices 320a, 320b, 320c, 320d). In one embodiment, at least one IoT device (320) may include at least one small things device (e.g., a sensor device) that can operate on a battery. In one embodiment, at least one IoT device (320) (e.g., a small things device) may use a low-power communication protocol such as Zigbee, Zwave, and / or Bluetooth low energy (BLE) instead of using Wi-Fi or Ethernet, which consumes a lot of power, for Internet connection.

[0061] In one embodiment, at least one IoT device (320) (e.g., a small object device) cannot directly access network communication (e.g., the Internet) via a low-power communication protocol (e.g., Zigbee, Zwave, and / or BLE), and may be connected to the network communication via a first external electronic device (e.g., a hub device (330)) that relays between the low-power communication protocol and the network communication. The hub device (330) may support a connection between the at least one IoT device (320) and the electronic device (201) and / or a connection between the at least one IoT device (320) and the server (310). In one embodiment, the electronic device (201) may communicate with the at least one IoT device (320) via the hub device (330), via the server (310), via long-range wireless communication (e.g., a second network (299)), or via short-range wireless communication (e.g., a first network (298)).

[0062] In one embodiment, at least one IoT device (320) can be controlled (e.g., to report status and / or perform a specific function) by a remote command (e.g., a control command of the electronic device (201)) and may include, for example, at least one of a television, an air conditioner, a refrigerator, a washing machine, a lighting device, a security camera, a sensor, or a window treatment. In one embodiment, at least one IoT device (320) may include a plurality of IoT devices (e.g., sensor devices) configured as a package (e.g., package (500)) together with a hub device (330).

[0063] In one embodiment, at least one IoT device (320) can communicate with the electronic device (201) and / or the server (310) via the hub device (330). In one embodiment, at least one IoT device (320) can be configured to communicate with the hub device (330) and / or the electronic device (201) 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, when at least one IoT device (320) is a small-scale device, at least one IoT device (320) can be connected to the hub device (330) via a low-power communication protocol and can be configured to communicate with the server (310) and / or the electronic device (201) via the hub device (330).

[0064] In one embodiment, the electronic device (201) may be a personal electronic device, such as a smart phone, tablet, or wearable device, or an electronic device having a display and user interface, such as a television or control console. The electronic device (201) may discover a hub device (330) and perform a first onboarding procedure (e.g., a hub onboarding procedure) to authenticate the discovered hub device (330) and register it with the server (310). After registering with the server (310), the hub device (330) may perform a second onboarding procedure (e.g., a device onboarding procedure) to authenticate and register at least one IoT device (320) with the server (310) to associate it with a user account. The electronic device (201) may use the user account to monitor, configure, and control at least one IoT device (320) registered with the server (310).

[0065] In one embodiment, the electronic device (201) can check the status of at least one IoT device (320) that the user will use for the IoT control service, or control at least one IoT device (320) (e.g., transmit a control command instructing to execute a specific function). In one embodiment, the electronic device (201) can be an owner device included in the network (300). In one embodiment, at least one member device including at least some functions and / or authority of the electronic device (201), although not shown, can be included in the network (300). In one embodiment, the member device cannot execute an onboarding procedure for the hub device (330) and / or at least one IoT device (320), but can execute a function of checking or controlling the status of at least one IoT device (320) registered with the server (310).

[0066] In one embodiment, the hub device (330) is an electronic device that operates an IoT control service, and may be a server or gateway located within a building (home or hotel), or a remote server located outside the building. In one embodiment, the hub device (330) may be a home appliance such as a smartphone, tablet, personal computer (PC), or TV having a hub function. The hub device (330) may execute a second onboarding procedure (e.g., a device onboarding procedure) that registers at least one IoT device (320) with the server (310) according to at least one of the embodiments described below.

[0067] In one embodiment, when at least one IoT device (320) is a sensor device, at least one IoT device (320) can report collected sensor data to the server (310) through the hub device (330) according to a specified event (e.g., periodically or upon satisfaction of a specified condition). In one embodiment, at least one IoT device (320) can execute a corresponding operation according to a control command transmitted by the electronic device (201) through the hub device (330) or through the server (310) and the hub device (330). In one embodiment, the server (310) can receive a control command generated according to a specified automation rule through the hub device (330) and execute an operation corresponding to the control command.

[0068] In one embodiment, the hub device (330) may be connected to at least one IoT device (320) using a low-power communication protocol (e.g., Zigbee, Zwave, and / or BLE) and may transmit information (e.g., sensor data) received from the at least one IoT device (320) to the server (310). In one embodiment, the hub device (330) may interpret information (e.g., sensor data or a request) received from the at least one IoT device (320) and act based on the interpretation result.

[0069] In one embodiment, the electronic device (201) may include an application (e.g., an IoT application) for communicating with a hub device (330) and / or at least one IoT device (320), and may display information (e.g., sensor data and / or status) collected by the at least one IoT device (320) by executing the IoT application on a display module (e.g., a display module (260)). In one embodiment, the electronic device (201) may transmit a control command input from a user through the IoT application to the at least one IoT device (320) through a server (310) and the hub device (330).

[0070] In one embodiment, the server (310) can store status information of at least one IoT device (320) connected via a hub device (330) and provide the status information to the electronic device (201). In one embodiment, the server (310) can transmit a control command received from the electronic device (201) to at least one IoT device (320) via the hub device (330). In one embodiment, the server (310) can store at least one automation rule for at least one IoT device (320), and can generate a control command according to the at least one automation rule and transmit the control command to at least one IoT device (320) via the hub device (330).

[0071] In one embodiment, the electronic device (201) may perform a first onboarding procedure (e.g., a hub onboarding procedure) in which a user installs an IoT application for identifying and configuring at least one IoT device (320) and registers a hub device (330) with a server (310) through the IoT application. After the hub device (330) is registered, the electronic device (201) may receive an onboarding result of at least one IoT device (320) registered with the server (310) through the device onboarding procedure from the server (310), thereby identifying, configuring, and controlling at least one IoT device (320) through the IoT application.

[0072] The electronic device (201) may display a catalog providing at least one IoT device (320) that can be connected through the IoT application in order to identify at least one IoT device (320) through the IoT application, and may receive a user input from the user for selecting at least one IoT device (320) (e.g., IoT device (320a)) to be connected through the catalog. In response to the user input, the electronic device (201) may display an installation guide for putting the IoT device (320a) into a connection mode (e.g., setup mode).

[0073] The above installation guide may include at least one of guide information requesting to capture a machine-readable indicator (e.g., a QR (quick response) code or barcode) of the IoT device (320a) through a camera (e.g., a camera module (280)) of the electronic device (201), guide information requesting to press a designated button of the IoT device (320a), guide information requesting to install a battery in the IoT device (320a), or guide information requesting to turn on the power of the IoT device (320a).

[0074] The electronic device (201) can capture a QR code of the IoT device (320a) through a camera (e.g., a camera module (280)), obtain connection information (e.g., an installation code to be used for connection with the IoT device (320a)) from the QR code, and transmit the connection information to the hub device (330). In one embodiment, the installation code can include a security key to be used by the hub device (330) to onboard the IoT device (320a). The hub device (330) can establish a connection (e.g., a Zigbee connection, a Zwave connection, or a BLE connection) with the IoT device (320a) based on the connection information.

[0075] When a connection with an IoT device (320a) is established, the hub device (330) may request the server (310) to create a device record for the IoT device (320a) and synchronize information (e.g., device ID and / or model name) of the IoT device (320a) with the server (310) to perform a device onboarding procedure for the IoT device (320a). After the device onboarding procedure is completed, the electronic device (201) may receive an onboarding result of the IoT device (320a) from the server (310) and display information notifying that the connection of the IoT device (320a) is completed through an IoT application.

[0076] In one embodiment, the hub device (330) and at least one IoT device (320) may be manufactured and sold as a package (e.g., package (500)) such as a starter kit or bundle set. The at least one IoT device (320) within the package may include multiple IoT devices, and in order to register each IoT device with the server (310) according to the procedure described above, the QR code of each IoT device must be scanned one by one through the electronic device (201), which may be inconvenient.

[0077] Embodiments of the present disclosure enable a user to simply and conveniently connect IoT devices packaged together with a hub device (330) to an IoT environment (e.g., an IoT application of an electronic device (201)) to build an IoT environment. Embodiments of the present disclosure can improve production and packaging efficiency by omitting the complex procedure of operating and connecting the hub device (330) and IoT devices when manufacturing a package including the hub device (330) and IoT devices. Embodiments of the present disclosure can reduce inconvenience for manufacturers and users in registering a plurality of IoT devices to an IoT application.

[0078] FIG. 4 is a block diagram illustrating the internal configuration of a hub device (330) according to one embodiment.

[0079] Referring to FIG. 4, the hub device (330) may be configured to connect at least one external electronic device (e.g., at least one IoT device (320)) to a server (310) via network communication (e.g., the Internet) to implement an IoT service (e.g., an event-based IoT service) in a wireless communication network (e.g., an IoT network). 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 include a communication circuit (402), a processor (404), a memory (406), an interface (408), and / or a display (410).

[0080] In one embodiment, at least one of the communication circuit (402), the processor (404), the memory (406), the interface (408), or the display (410) may be implemented similarly or substantially identically to the communication module (290), the processor (220), the memory (230), the interface (277), or the display module (260) described in FIG. 2, respectively.

[0081] In one embodiment, the hub device (330) may be a device supporting Zigbee, Z-Wave, Wi-Fi, Bluetooth Classic, and / or Bluetooth low energy (BLE). The hub device (330) may include a communication circuit (402) that transmits and receives signals using one or more antennas (401) with at least one IoT device (320), server (310), or electronic device (201).

[0082] According to one embodiment, the communication circuit (402) may include one or more communication circuits (e.g., the communication module (290) of FIG. 2), which may include communication circuits based on Zigbee, Z-Wave, Wi-Fi, Bluetooth Classic, and / or BLE. According to one embodiment, the hub device (330) may include separate communication circuits each based on Zigbee, Z-Wave, Wi-Fi, Bluetooth Classic, and / or BLE, or may include at least one communication circuit based on at least one or a combination of Zigbee, Z-Wave, Wi-Fi, Bluetooth Classic, and / or BLE.

[0083] The hub device (330) may include an interface (408) (e.g., interface (277) of FIG. 2) that provides a wired and / or wireless interface for communicating with external components. In one embodiment, at least a portion of one or more antennas (401), communication circuitry (402), or interface (408) may be implemented as at least a portion of a communication module (290) and an antenna module (298) of FIG. 2.

[0084] The hub device (330) may include a processor (404) (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 for the operation of the hub device (330).

[0085] According to one embodiment, the memory (406) may store a user interface (UI) related to an IoT application and images, user information, documents, databases, or related data for providing the UI. According to one embodiment, the display (410) (e.g., the display module (260) of FIG. 2) may display a UI related to the IoT application when the IoT application is executed under the control of the processor (404).

[0086] FIG. 5 is a diagram illustrating a procedure for registering IoT devices according to one embodiment.

[0087] Referring to FIG. 5, the server (310) may store installation data (505) necessary for onboarding at least one IoT device (320). In one embodiment, the server (310) may obtain and store the installation data (505) from a manufacturer that manufactures a package (500) including at least one IoT device (320) and a hub device (330). In one embodiment, at the time of manufacturing or selling a package (500) including at least one IoT device (320) and a hub device (330), an engineer may obtain at least one of a photo of the hub device (330), a QR code of the at least one IoT device (320), or a serial number of the hub device (330) and register the obtained information with the server (310), for example, via the web. The server (310) may configure the installation data (505) based on the obtained information. In one embodiment, the obtained information may include all information necessary to configure the installation data (505). In one embodiment, the server (310) may collect at least some information necessary to configure installation data (505) from, for example, a manufacturer server (not shown) based on the acquired information.

[0088] In one embodiment, the installation data (505) may include at least one of hub information associated with a hub device (330) or device information associated with each of at least one IoT device (320). In one embodiment, the hub information may include at least one of a hub serial number (SN), a hub ID, or a hub model name. In one embodiment, the device information may include at least one of a device model name (e.g., 'motion', 'button', 'multipurpose', or 'bulb'), a device model code, a device ID, or an installation code (505a). In one embodiment, the device ID may include a device extended unique identifier (EUI), which may be a 64-bit globally-unique value assigned by the manufacturer, owner, or each IoT device. In one embodiment, the installation code (505a) may include a security key used for encrypted communication depending on the communication protocol (e.g., Zigbee, Zwave, or BLE) used between each IoT device (320) and the hub device (330). The hub device (330) may use the installation code (505a) to onboard each IoT device (320).

[0089] below shows an example of installation data (505).

[0090] Package IDStarterKit-000001Package Model NameModel-01Hub Serial Number12345678Hub Model NameIM6001-VxxxxDevice Model CodeDevice Model NameDevice EUIDevice Installation Code 001xxx12-34-56-78-xxxxXxx04Outlet12AB34CD0001xxx12-34-56-78-xxxxXxx05Switch12AB34CD0001xxx12-34-56-78-xxxx

[0091] Referring to the above , the installation data (505) may include at least one of the following fields.

[0092] - Package ID: An ID uniquely assigned to a package (500) including at least one IoT device (320) and a hub device (330), and may be, for example, 'StarterKit-000001'.

[0093] - Package Model Name: This is the product model name of the package (500) including at least one IoT device (320) and a hub device (330), and may be, for example, 'Model-01'.

[0094] - Hub Serial Number: A unique serial number of the hub device (330), for example, '12345678'.

[0095] - Hub Model Name: The model name of the hub device (330), for example, 'IM6001-Vxxxx'.

[0096] - Device Model Code: This is the model code of each IoT device (320), and may be, for example, 'Xxx01'.

[0097] - Device Model Name: This is the model name of each IoT device (320), and may be, for example, 'Motion', 'Button', 'Bulb', 'Outlet', or 'Switch'.

[0098] - Device EUI: A unique ID for each IoT device (320), for example, '12AB34CD0001xxx'.

[0099] - Device Installation Code (e.g., installation code (505a)): This is a security key of each IoT device (320) used during device onboarding (e.g., operation 530), and the length, format, and usage method may be determined depending on the protocol used (e.g., Zigbee, Zwave, or BLE). For example, the device installation code may be '12-34-56-78-xxxx'. The device installation code of each IoT device (320) may be different or the same for each IoT device (320).

[0100] In one embodiment, the installation data (505) may include at least a hub serial number, a device ID, and an installation code (505a). In one embodiment, since a package (500) of the same model may include a hub device (e.g., hub device (330)) and IoT devices (e.g., IoT device (320)) of the same model, the installation data (505) may not include the hub model name and / or the device model name(s) instead of including the package model name.

[0101] In one embodiment, the server (310) may obtain and store the installation data (505) from a seller or a computer of a store selling a package (500) including a hub device (330) and at least one IoT device. In one embodiment, at the time of selling the package (500) including at least one IoT device (320) and a hub device (330), the seller, the user purchasing the package, or an agent may obtain at least one of a photo of the hub device (330), a QR code of the at least one IoT device (320), or a serial number of the hub device (330) and register the obtained information with the server (310), for example, via the web. In one embodiment, the obtained information may include all information necessary to configure the installation data (505). In one embodiment, the server (310) may collect at least some information necessary to configure the installation data (505), for example, from a manufacturer server (not shown), based on the obtained information.

[0102] At operation 510, the electronic device (201) may perform a first onboarding procedure (e.g., a hub onboarding procedure) to register the hub device (330) with the server (310). In one embodiment, the hub onboarding procedure of operation 510 may be performed at least prior to operation 525, for example.

[0103] In operation 515, the electronic device (201) may transmit a request message to the server (310) requesting installation data (505) related to a package (500) including a hub device (330) and at least one IoT device (320). In one embodiment, the electronic device (201) may request the installation data (505) based on a serial number of the hub device (330) or a package ID of the package (500). In one embodiment, the electronic device (201) may obtain the serial number of the hub device (330) from a QR code of the hub device (330) or a server (e.g., the server (310)). In one embodiment, the electronic device (201) may obtain the package ID from a QR code of the package (500) or may obtain the package ID printed (or attached) to the package (500), for example, through user input. In operation 520, the server (310) may transmit installation data (505) to the electronic device (201) in response to the request message.

[0104] In operation 525, the electronic device (201) may transmit installation data (505) to the hub device (330). In one embodiment, the hub device (330) has already performed the hub onboarding procedure of operation 510 through the electronic device (201) by establishing a connection (e.g., a Wi-Fi connection, a Bluetooth connection, or a BLE connection) with the electronic device (201) and is registered with the server (310), and the electronic device (201) may transmit the installation data (505) to the hub device (330) through the connection. In one embodiment, the electronic device (201) may establish a new connection for transmitting the installation data (505) while recognizing the hub device (330) through the hub onboarding procedure of operation 510.

[0105] In operation 530, the hub device (330) may perform a device onboarding procedure for each of the at least one IoT device (320) using the installation data (505). In one embodiment, the hub device (330) may establish a connection with the at least one IoT device (320) using the installation code (505a) for the at least one IoT device (320) included in the installation data (505), and perform a device onboarding procedure so that the at least one IoT device (320) may be registered with the server (310) through the connection. Through the device onboarding procedure, the server (310) may identify the at least one IoT device (320) and store device information thereof.

[0106] In operation 535, the electronic device (201) may receive an onboarding result from the server (310) indicating that onboarding of at least one IoT device (320) is completed, and may provide a notification message to the user indicating that at least one IoT device (320) has been registered through the IoT application. In one embodiment, the server (310) may recognize that onboarding of all IoT devices included in the installation data (505) is completed based on the installation data (505) and transmit the onboarding result to the electronic device (201).

[0107] FIG. 6 is a flowchart illustrating the operation of an electronic device for registering IoT devices according to one embodiment. At least one of the operations described below may be executed by the processor (220) of the electronic device (201). Depending on the embodiments, at least one of the operations described below may be omitted, modified, or the order may be changed.

[0108] Referring to FIG. 6, in operation 605, the electronic device (201) (e.g., processor (220)) may obtain installation data (e.g., installation data (505)) related to a first external electronic device (e.g., hub device (330)). In one embodiment, the installation data (505) may include an installation code (e.g., installation code (505a)) for at least one second external electronic device (e.g., at least one IoT device (320)) connectable to the hub device (330). In one embodiment, the electronic device (201) (e.g., processor (220)) may request installation data (505) from the server (310) based on a user account and identification information of the hub device (330) (e.g., hub serial number and / or hub media access control (MAC) address) or identification information of a package (e.g., package ID) including the hub device (330) and at least one IoT device (320) (e.g., package (500)), and receive the installation data (505) from the server (310).

[0109] In one embodiment, the electronic device (201) (e.g., the processor (220)) can obtain the installation data (505) based on a machine-readable indicator (e.g., a QR code or a bar code) of a package (500) including a hub device (330) and an IoT device (320). For example, a QR code may be printed or attached to a surface of the hub device (330) or a surface of the package (500), and the electronic device (201) (e.g., the processor (220)) can capture the QR code to obtain a URL address (e.g., an IP address of the server (310)), and access the URL address to obtain the installation data (505) (or at least a portion of the installation data). In one embodiment, at least a portion of the installation data (505) may be stored in the hub device (330), and the electronic device (201) (e.g., the processor (220)) may receive at least a portion of the installation data (505) (e.g., an installation guide) from the hub device (330).

[0110] In operation 610, the electronic device (201) (e.g., processor (220)) may execute a hub onboarding procedure to register the hub device (330) with the server (310). In one embodiment, the electronic device (201) (e.g., processor (220)) may obtain identification information (e.g., serial number) of the hub device (330) from a machine-readable indicator (e.g., QR code or bar code) of the hub device (330) and establish a connection (e.g., Wi-Fi connection or BLE connection) with the hub device (330) based on the identification information. The electronic device (201) (e.g., processor (220)) may authenticate the hub device (330) through the connection and provide the hub device (330) with connection information to be used in connecting to the server (310). The hub device (330) may establish a connection with the server (310) based on the connection information and may be registered with the server (310) through the connection.

[0111] In operation 615, the electronic device (201) (e.g., processor (220)) may transmit the installation data (505) acquired in operation 605 to the hub device (330). In one embodiment, the electronic device (201) (e.g., processor (220)) may confirm that the hub onboarding procedure for the hub device (330) is complete and may transmit the installation data (505) using the established connection with the hub device (330). In one embodiment, the electronic device (201) (e.g., processor (220)) may re-establish the connection for the installation data (505) with the hub device (330) and transmit the installation data (505) to the hub device (330).

[0112] In one embodiment, the hub device (330) may perform a device onboarding procedure for at least one IoT device (320) in response to receiving the installation data (505). Although not shown in one embodiment, the electronic device (201) (e.g., processor (220)) may transmit an onboarding command to the hub device (330) via the server (310) or directly, requesting the hub device (330) to perform a device onboarding procedure for at least one IoT device (320). In one embodiment, the electronic device (201) (e.g., processor (220)) may transmit the onboarding command to the hub device (330) based on a user input. In one embodiment, the hub device (330) may perform the device onboarding procedure for at least one IoT device (320) in response to the onboarding command.

[0113] In operation 620, the electronic device (201) (e.g., the processor (220)) may display an installation guide for at least one IoT device (320) through a display module (e.g., the display module (260)) based on the installation data (505). In one embodiment, the installation guide may include a message (e.g., at least one of a phrase, an image, a voice, or a sound) guiding a required user operation (e.g., a QR scan, an input of a designated button, or battery insertion) for each IoT device (320). The at least one IoT device (320) may enter a setup mode in response to a user operation based on the installation guide, and may be onboarded to the server (310) by the hub device (330) that received the installation data of operation 615.

[0114] In operation 625, the electronic device (201) (e.g., processor (220)) may receive an onboarding result from the server (310) indicating that the device onboarding procedure for at least one IoT device (320) is completed. In one embodiment, the onboarding result may include information indicating that the device onboarding procedure for all or at least some of the IoT devices (320) included in the package (500) is completed. In one embodiment, the electronic device (201) (e.g., processor (220)) may display information (e.g., device name or image) of at least one IoT device (320) for which onboarding is completed through a display module (e.g., display module (260)) according to the onboarding result.

[0115] FIG. 7 is a flowchart illustrating the operation of a hub device for registering IoT devices according to one embodiment. At least one of the operations described below may be executed by the processor (404) of the hub device (330). Depending on the embodiments, at least one of the operations described below may be omitted, modified, or the order may be changed.

[0116] Referring to FIG. 7, in operation 705, the hub device (330) (e.g., processor (404)) may receive installation data (e.g., installation data (505)) for at least one external electronic device (e.g., IoT device (320)) from the electronic device (201). In one embodiment, the hub device (330) has completed a hub onboarding procedure and may receive the installation data (505) through a connection (e.g., Wi-Fi connection or BLE connection) with the electronic device (201). The hub device (330) (e.g., processor (404)) may obtain an installation code (e.g., installation code (505a)) for each IoT device (320) from the installation data (505).

[0117] In operation 710, the hub device (330) (e.g., processor (404)) may perform a device onboarding procedure for each of at least one IoT device (320) included in the installation data (505) based on the installation data (505). In one embodiment, operation 710 may include at least one of operation 715, operation 720, operation 725, or operation 730. In one embodiment, the installation data (505) may include device identification information (e.g., at least one of a device ID, a serial number, a MAC address, a model name, or a model code) and an installation code (e.g., an installation code (505a)) of at least one IoT device (320) connectable to the hub device (330). In one embodiment, the hub device (330) may perform the device onboarding procedure of operation 710 in response to receiving the installation data (505). Although not illustrated, in one embodiment, the hub device (330) may perform the device onboarding procedure of operation 710 in response to an onboarding command received from the server (310) or directly from the electronic device (201).

[0118] In operation 715, the hub device (330) (e.g., processor (404)) may establish a connection with any one IoT device (e.g., IoT device (320a)) included in the installation data (505). In one embodiment, the hub device (330) (e.g., processor (404)) may obtain an installation code (505a) of the IoT device (320a) from the installation data (505) and establish a connection (e.g., Zigbee connection, Zwave connection, or BLE connection) with the IoT device (320a). In one embodiment, the installation code (505a) may include a security key used to perform encrypted communication with the IoT device (320a) through the connection. The IoT device (320a) may be connected to the hub device (330) that knows the installation code (505a).

[0119] In operation 720, the hub device (330) (e.g., processor (404)) may request the server (310) to create a device record associated with the IoT device (320a) with which the connection was established. In one embodiment, the hub device (330) (e.g., processor (404)) may transmit a device record creation request including device identification information of the IoT device (320a) to the server (310). The server (310) may create and store a device record for the IoT device (320a) in response to the device record creation request. In one embodiment, the device record may be used by the server (310) to store information (e.g., sensor data and / or status information) collected from the IoT device (320a) via the hub device (330) for an IoT service.

[0120] At operation 725, the hub device (330) (e.g., processor (404)) may receive an onboarding completion response from the server (310) indicating that a device record for the IoT device (320a) has been created.

[0121] At operation 730, the hub device (330) (e.g., processor (404)) may determine whether device onboarding of all IoT devices (320) included in the installation data (505) is completed based on the installation data (505). In one embodiment, the hub device (330) (e.g., processor (404)) may perform device onboarding procedures of one or more IoT devices (320) sequentially or in parallel. If device onboarding of all IoT devices (320) is not completed, the hub device (330) (e.g., processor (404)) may proceed to operation 715 to perform device onboarding of the next IoT device (e.g., IoT device (320b)). If device onboarding of all IoT devices (320) is completed, the hub device (330) (e.g., processor (404)) may proceed to operation 735. In one embodiment, the hub device (330) (e.g., processor (404)) may proceed to operation 735 if a specified amount of time has elapsed since initiating device onboarding or if an onboarding stop command is received from the electronic device (201), even if device onboarding of all IoT devices (320) has not yet been completed.

[0122] At step 735, the hub device (330) (e.g., processor (404)) may confirm that the device onboarding procedure is complete. In one embodiment, the hub device (330) (e.g., processor (404)) may provide a message to the user via a display (e.g., display (410)) or via sound informing that the IoT devices (320) of the package (500) have been registered.

[0123] FIG. 8 illustrates an example of a signal flow diagram (sequence diagram) that provides rapid connection of IoT devices according to one embodiment. Depending on the embodiments, at least one of the operations described below may be omitted, modified, or the order may be changed.

[0124] Referring to FIG. 8, in operation 702, the electronic device (201) may execute an IoT application for an IoT service. In one embodiment, the electronic device (201) may receive a user input requesting device addition through the IoT application. In one embodiment, the electronic device (201) may receive a user input requesting onboarding of a hub device (330) or onboarding of a package (500) including a hub device (330) and at least one IoT device (320) through the IoT application. The electronic device (201) may execute operation 804 or operation 812 to obtain package identification information (e.g., a hub serial number or a package ID) required for onboarding the package (500).

[0125] Operation 804 is a procedure for obtaining package identification information from the server (310), which may include, for example, at least one of operations 806, 808, or 810. In operation 806, the electronic device (201) may receive a user account ID from the user, for example, through the input module (250). In one embodiment, the electronic device (201) may obtain the user account ID from login information of an IoT application. In operation 808, the electronic device (201) may transmit a package identification request message including the user account ID to the server (310). The server (310) may store installation data (505) obtained from a manufacturer or seller of the package (500) or the hub device (330). In one embodiment, the server (310) may obtain and store the user account ID and installation data (505) of a user who purchased the package (500) or the hub device (330) from a seller after the package (500) or the hub device (330) is sold to the user, and the installation data (505) may include package identification information (e.g., hub serial number or package ID). In operation 810, the server (310) may transmit the package identification information included in the installation data (505) to the electronic device (201) based on the user account ID. The electronic device (201) may receive the package identification information corresponding to the user account ID from the server (310).

[0126] In operation 812, instead of receiving the package identification information from the server (310), the electronic device (201) may obtain the package identification information directly from the hub device (330) or the package (500). In one embodiment, the electronic device (201) may obtain the hub serial number from the QR code of the hub device (330). In one embodiment, the electronic device (201) may obtain the package ID from the QR code of the package (500). In one embodiment, the hub serial number or the package ID may be printed or attached to the surface of the hub device (330) or the packaging box of the package (500), and the electronic device (201) may receive the hub serial number or the package ID from the user. In one embodiment, operation 812 may be omitted, and the electronic device (201) may obtain the hub serial number during the hub onboarding procedure of operation 814.

[0127] In operation 814, the electronic device (201) may perform a hub onboarding procedure. In one embodiment, the electronic device (201) may verify ownership of the hub device (330) using the hub serial number obtained, for example, in operation 804 or operation 812, for the hub onboarding procedure. In one embodiment, the hub device (330) may authenticate the electronic device (201) based on the hub serial number received from the electronic device (201) and perform the hub onboarding procedure.

[0128] In one embodiment, the hub onboarding procedure may include at least one of the following: establishing a connection between the electronic device (201) and the hub device (330); transmitting connection information from the electronic device (201) to the hub device (330); connecting the hub device (330) to the server (310) using the connection information; transmitting device information of the hub device (330) to the server (310) (e.g., at least one of a device ID, a hub serial number, a hub model name, or a hub model code); or notifying the electronic device (201) of the onboarding result of the hub device (330). In one embodiment, the connection information may include access point (AP) information (e.g., a service set ID (SSID) and / or a password) for an AP (not shown) to which the hub device (330) will connect. In one embodiment, the hub onboarding procedure may include at least one of the operations illustrated in FIG. 11.

[0129] In operations 816 and 818, the electronic device (201) may obtain installation data (505) for at least one IoT device (320) from the server (310). In one embodiment, operations 816 and 818 may be performed concurrently with or at least partially overlapping the hub onboarding procedure of operation 814. In one embodiment, operations 816 and 818 may be performed before or after the hub onboarding procedure of operation 814.

[0130] In operation 816, the electronic device (201) may transmit an installation data request message to the server (310). In one embodiment, the installation data request message may include package identification information (e.g., hub serial number or package ID) and / or a user account ID. In operation 818, the server (310) may find installation data (505) based on the package identification information and / or the user account ID, and transmit the installation data (505) to the electronic device (201). In one embodiment, the installation data (505) provided by the server (310) may include at least a hub serial number, a device ID, and an installation code (505a).

[0131] In operation 820, the electronic device (201) may obtain an installation code (505a) for at least one IoT device (320) included in the installation data (505). In operation 822, the electronic device (201) may transmit at least the installation code (505a) to the hub device (330). In one embodiment, the electronic device (201) may transmit at least a portion or all of the installation data (505) to the hub device (330). In one embodiment, the electronic device (201) may transmit a device ID (e.g., device EUI) and an installation code (505a) for each of the at least one IoT device (320) included in the installation data (505) to the hub device (330). In one embodiment, at least some or all of the installation data (505) may be transmitted from the electronic device (201) directly to the hub device (330) (e.g., via a Wi-Fi connection or a BLE connection), or may be transmitted from the electronic device (201) to the hub device (330) via the server (310).

[0132] In operation 824, the electronic device (201) may display an installation guide for at least one IoT device (320) included in the installation data (505) based on the installation data (505). Although not shown, the electronic device (201) may obtain the installation guide for at least one IoT device (320) included in the installation data (505) from a server (e.g., the server (310) or a manufacturer server (not shown)) based on device information (e.g., a device model name and / or a device model code) included in the installation data (505). The electronic device (201) may display the installation guide until the completion of onboarding for at least one IoT device (320) is notified from the server (310) or for a specified period of time. A user can set at least one IoT device (320) to a state (e.g., setup mode) (e.g., state of broadcasting a beacon signal) in which the at least one IoT device (320) can be connected to a hub device (330) by operating the at least one IoT device (320) based on the installation guide (e.g., pressing a designated button, installing a battery, or turning on the power). The hub device (330) can discover the at least one IoT device (320) by receiving the beacon signal. The at least one IoT device (320) can maintain the setup mode until it is connected to the hub device (330).

[0133] At operation 826, the hub device (330) may perform a device onboarding procedure to register each of at least one IoT device (320) with the server (310) based on the installation data (505) (e.g., installation code (505a)) received at operation 822. In one embodiment, the device onboarding procedure may include at least one of operation 715, operation 720, or operation 725. In one embodiment, the hub device (330) may enter a join mode for performing the device onboarding procedure after receiving the installation data (505). In the join mode, the hub device (330) can identify at least one IoT device (320) (e.g., IoT device (320a)) based on the installation data (505) (e.g., device ID) received in operation 822, discover the IoT device (320a), and establish a connection (e.g., Zigbee connection, Zwave connection, or BLE connection) with the discovered IoT device (320a). The hub device (330) can perform encrypted communication with the discovered IoT device (320a) through the connection based on the installation code (505a).

[0134] In join mode, the hub device (330) may request the server (310) to create a device record for the discovered IoT device (320a). In one embodiment, the hub device (330) may remain in join mode until device onboarding is completed for all of at least one IoT device (320) included in the installation data (505). In one embodiment, the hub device (330) may remain in join mode for a specified period of time after initiating the device onboarding procedure. In one embodiment, the hub device (330) may remain in join mode until an onboarding stop command is received from the electronic device (201).

[0135] In operation 828, the server (310) may transmit an onboarding result to the electronic device (201) indicating that device onboarding for at least one IoT device (320) included in the installation data (505) is complete. In one embodiment, the server (310) may transmit the onboarding result when device onboarding for all of the at least one IoT device (320) included in the installation data (505) is complete. In one embodiment, the server (310) may transmit the onboarding result whenever device onboarding for any one IoT device (320) included in the installation data (505) is complete. In one embodiment, the electronic device (201) may transmit an onboarding stop command to the hub device (330) if onboarding results for all of the at least one IoT device (320) are not received from the server (310) until a specified time has elapsed since transmitting the installation data (505) in operation 822.

[0136] Once device onboarding is complete, the server (310) can manage a device record for each IoT device (320) and include information (e.g., sensor data and / or status information) of each IoT device (320) collected through the hub device (330) in the device record. In one embodiment, the server (310) can provide information (e.g., sensor data and / or status information) included in the device record to the electronic device (201) in response to a specified event or a request from the electronic device (201).

[0137] FIG. 9 is a flowchart illustrating the operation of a hub device for registering IoT devices according to one embodiment. At least one of the operations described below may be executed by the processor (404) of the hub device (330). Depending on the embodiments, at least one of the operations described below may be omitted, modified, or the order may be changed.

[0138] Referring to FIG. 9, in operation 905, a hub device (330) (e.g., processor (404)) may connect to an electronic device (201) and register with a server (310) through a hub onboarding procedure. In one embodiment, the hub device (330) (e.g., processor (404)) may perform the hub onboarding procedure according to an onboarding command from the electronic device (201).

[0139] In operation 910, the hub device (330) (e.g., processor (404)) may obtain installation data (e.g., installation data (505)) related to at least one IoT device (320) of the hub device. In one embodiment, the installation data (505) may include an installation code (505a) for at least one IoT device (320) connectable to the hub device (330). The hub device (330) (e.g., processor (404)) may obtain an installation code (e.g., installation code (505a)) for each IoT device (320) from the installation data (505).

[0140] In one embodiment, the hub device (330) (e.g., processor (404)) may request installation data (505) from the server (310) based on identification information of the hub device (330) (e.g., hub serial number) or identification information of a package (500) including the hub device (330) and at least one IoT device (320) (e.g., package ID), and receive the installation data (505) from the server (310). In one embodiment, the hub device (330) (e.g., processor (404)) may obtain the installation data (505) from a machine-readable indicator (e.g., QR code or bar code) of the package (500) including the hub device (330) and the IoT device (320).

[0141] At operation 915, the hub device (330) (e.g., processor (404)) may perform a device onboarding procedure for each of at least one IoT device (320) included in the installation data (505) based on the installation data (505). In one embodiment, operation 915 may include at least one of operation 920, operation 925, operation 930, or operation 935. In one embodiment, the installation data (505) may include device identification information (e.g., at least one of a device ID, a model name, or a model code) and an installation code (e.g., an installation code (505a)) of at least one IoT device (320) connectable to the hub device (330).

[0142] In operation 920, the hub device (330) (e.g., the processor (404)) may establish a connection with any one IoT device (e.g., the IoT device (320a)) included in the installation data (505). In one embodiment, the hub device (330) (e.g., the processor (404)) may obtain an installation code (505a) of the IoT device (320a) from the installation data (505) and establish a connection (e.g., a Zigbee connection, a Zwave connection, or a BLE connection) with the IoT device (320a). In one embodiment, the installation code (505a) may include a security key used to perform encrypted communication with the IoT device (320a) through the connection. The IoT device (320a) may be connected to the hub device (330) that knows the installation code (505a).

[0143] At step 925, the hub device (330) (e.g., processor (404)) may request the server (310) to create a device record associated with the IoT device (320a) with which the connection was established. In one embodiment, the hub device (330) (e.g., processor (404)) may transmit a device record creation request including device identification information of the IoT device (320a) to the server (310). The server (310) may create and store a device record for the IoT device (320a) in response to the device record creation request. In one embodiment, the device record may be used by the server (310) to store information (e.g., sensor data and / or status information) collected from the IoT device (320a) via the hub device (330) for an IoT service.

[0144] At operation 930, the hub device (330) (e.g., processor (404)) may receive an onboarding completion response from the server (310) indicating that a device record for the IoT device (320a) has been created.

[0145] At operation 935, the hub device (330) (e.g., processor (404)) may determine whether device onboarding of all IoT devices (320) included in the installation data (505) is completed based on the installation data (505). In one embodiment, the hub device (330) (e.g., processor (404)) may perform device onboarding procedures of one or more IoT devices (320) sequentially or in parallel. If device onboarding of all IoT devices (320) is not completed, the hub device (330) (e.g., processor (404)) may proceed to operation 920 to perform device onboarding of the next IoT device (e.g., IoT device (320b)). If device onboarding of all IoT devices (320) is completed, the hub device (330) (e.g., processor (404)) may proceed to operation 940. In one embodiment, the hub device (330) (e.g., processor (404)) may proceed to operation 735 if a specified amount of time has elapsed since initiating device onboarding or if an onboarding stop command is received from the electronic device (201), even if device onboarding of all IoT devices (320) has not yet been completed.

[0146] At step 940, the hub device (330) (e.g., processor (404)) may confirm that the device onboarding procedure is complete. In one embodiment, the hub device (330) (e.g., processor (404)) may provide a message to the user via a display (e.g., display (410)) or via sound informing that the IoT devices (320) of the package (500) have been registered.

[0147] FIG. 10 illustrates an example signal flow diagram for providing fast connection of IoT devices according to one embodiment. Depending on the embodiments, at least one of the operations described below may be omitted, modified, or the order may be changed.

[0148] Referring to FIG. 10, in operation 1002, the electronic device (201) may execute an IoT application for an IoT service. In one embodiment, the electronic device (201) may receive a user input requesting addition of a device through the IoT application. In one embodiment, the electronic device (201) may receive a user input requesting execution of onboarding of a hub device (330) or onboarding of a package (500) including the hub device (330) and at least one IoT device (320) through the IoT application.

[0149] In operation 1004, the electronic device (201) may perform a hub onboarding procedure. Although not shown, in one embodiment, the electronic device (201) may verify ownership of the hub device (330) using the hub serial number obtained, for example, in operation 804 or operation 812, for the hub onboarding procedure. In one embodiment, the hub device (330) may authenticate the electronic device (201) based on the hub serial number received from the electronic device (201) and perform the hub onboarding procedure.

[0150] In one embodiment, the hub onboarding procedure may include at least one of: establishing a connection between the electronic device (201) and the hub device (330); transmitting connection information (e.g., AP information) from the electronic device (201) to the hub device (330); connecting the hub device (330) to the server (310) using the connection information; transmitting device information (e.g., at least one of a device ID, a hub serial number, a hub model name, or a hub model code) of the hub device (330) to the server (310); or notifying the electronic device (201) of the onboarding result of the hub device (330). In one embodiment, the hub onboarding procedure may include at least one of the operations illustrated in FIG. 11.

[0151] In operation 1006, the electronic device (201) may transmit a device onboarding request to the server (310). In one embodiment, the electronic device (201) may transmit a device onboarding request for at least one IoT device (320) associated with the hub device (330) to the server (310) upon completion of the hub onboarding procedure of operation 1004. In one embodiment, the device onboarding request may include a user account ID and / or package identification information (e.g., a hub serial number or package ID).

[0152] In operation 1008, the server (310) may transmit a device onboarding command to the hub device (330) based on the device onboarding request. In one embodiment, the device onboarding command may include at least a portion or all of the installation data (505) associated with the hub device (330). In one embodiment, the device onboarding command may include at least a device ID (e.g., device EUI) and an installation code (505a) for each of at least one IoT device (320) that may be connected to the hub device (330). In one embodiment, when the device onboarding command does not include the device ID and the installation code (505a), operations 1010 and 1012 may be performed. When the device onboarding command includes the device ID and the installation code (505a), operations 1010 and 1012 may be omitted. In one embodiment, the electronic device (201) may transmit the device onboarding command directly to the hub device (330) (e.g., without going through the server (310)), and operations 1006 and 1008 may be omitted.

[0153] In operation 1010 and operation 1012, the hub device (330) may obtain at least a portion or all of the installation data (505) for at least one IoT device (320) from the server (310). In operation 1010, the hub device (330) may transmit an installation data request message to the server (310). In one embodiment, the installation data request message may include package identification information (e.g., hub serial number or package ID) and / or a user account ID. In operation 1012, the server (310) may locate the installation data (505) based on the package identification information and / or the user account ID, and transmit at least a portion or all of the installation data (505) to the hub device (330). In operation 1014, the hub device (330) may obtain an installation code (505a) for at least one IoT device (320) included in the installation data (505).

[0154] Although not shown, in one embodiment, the hub device (330) may display an installation guide for at least one IoT device (320) included in the installation data (505) on the display module (410) based on the installation data (505). Although not shown, the hub device (330) may obtain the installation guide for at least one IoT device (320) included in the installation data (505) from a server (e.g., the server (310) or a manufacturer server (not shown)) based on device information (e.g., device model name and / or device model code) included in the installation data (505). The hub device (330) may display the installation guide until device onboarding for all of the at least one IoT device (320) is completed or for a specified period of time. A user can operate at least one IoT device (320) based on the installation guide (e.g., pressing a designated button, installing a battery, or turning on the power) to put each IoT device (320) into a state (e.g., setup mode) in which it can be connected to a hub device (330) (e.g., a state in which it broadcasts a beacon signal). Each IoT device (320) can remain in setup mode until it is connected to the hub device (330).

[0155] In operation 1016, the hub device (330) may perform a device onboarding procedure to register each of at least one IoT device (320) with the server (310) based on the installation data (505) (e.g., installation code (505a)) received in operation 1008 or operation 1012. In one embodiment, the device onboarding procedure may include at least one of operation 920, operation 925, or operation 930. In one embodiment, the hub device (330) may enter a join mode to perform the device onboarding procedure after receiving the installation data (505). In the join mode, the hub device (330) can identify and discover at least one IoT device (320) (e.g., IoT device (320a)) based on the installation data (505) (e.g., device ID), and can establish a connection (e.g., Zigbee connection, Zwave connection, or BLE connection) with the discovered IoT device (320a). The hub device (330) can perform encrypted communication with the discovered IoT device (320a) based on the installation code (505a). In the join mode, the hub device (330) can request the server (310) to create a device record for the discovered IoT device (320a). In one embodiment, the hub device (330) can remain in the join mode until device onboarding is completed for all of the at least one IoT device (320) included in the installation data (505). In one embodiment, the hub device (330) may remain in join mode for a specified period of time after initiating the device onboarding procedure. In one embodiment, the hub device (330) may remain in join mode until an onboarding stop command is received from the electronic device.

[0156] In operation 1018, the server (310) may transmit an onboarding result to the electronic device (201) indicating that device onboarding for at least one IoT device (320) included in the installation data (505) is complete. In one embodiment, the server (310) may transmit the onboarding result when device onboarding for all of the at least one IoT device (320) included in the installation data (505) is complete. In one embodiment, the server (310) may transmit the onboarding result whenever device onboarding for any one IoT device (320) included in the installation data (505) is complete. In one embodiment, if the electronic device (201) does not receive an onboarding result for all of at least one IoT device (320) from the server (310) within a specified period of time after transmitting the device onboarding request in operation 1006, the electronic device (201) may transmit an onboarding stop command to the hub device (330) directly or through the server (310).

[0157] Once device onboarding is complete, the server (310) can manage a device record for each IoT device (320) and include information (e.g., sensor data and / or status information) of each IoT device (320) collected through the hub device (330) in the device record. In one embodiment, the server (310) can provide information (e.g., sensor data and / or status information) included in the device record to the electronic device (201) in response to a specified event or a request from the electronic device (201).

[0158] In one embodiment, while the device onboarding procedure is in progress in operation 826 or operation 1016, the electronic device (201) may display onboarding completion status of at least one IoT device (320) included in the installation data (505) on the display module (260). As device onboarding of at least one IoT device (320) is completed one by one, the electronic device (201) may display the onboarding completion status of the corresponding IoT device (e.g., IoT device (320a)) and may continue to display an installation guide of an IoT device (e.g., IoT device (320b)) that has not completed onboarding.

[0159] In one embodiment, the electronic device (201) may disable device onboarding of at least one IoT device (320) included in the installation data (505) (e.g., IoT device (320d)) based on user input. In one embodiment, the electronic device (201) may disable or not display the installation guide for the disabled IoT device (320d). In one embodiment, the electronic device (201) may display the IoT device (320d) as included in a device list in a “device to be added” state.

[0160] In one embodiment, the hub device (330) may not allow device onboarding of the other IoT device or may delay the device onboarding of the package (500) until the device onboarding procedure of the package (500) is completed if another IoT device is discovered while performing the device onboarding procedure of at least one IoT device (320) included in the package (500) (e.g., operation 826 or operation 1016). In one embodiment, the hub device (330) may allow device onboarding of the other IoT device if the other IoT device is discovered while performing the device onboarding procedure of at least one IoT device (320) included in the package (500) and the other IoT device does not require an installation code.

[0161] In one embodiment, after hub onboarding of the hub device (330) is completed in operation 814 or operation 1004, the electronic device (201) may request installation data (e.g., installation code) for a new IoT device not included in the package (500) to the server (310) to connect the new IoT device with the hub device (330). In one embodiment, the electronic device (201) may obtain device identification information (e.g., device serial number) of the new IoT device from a QR code of the new IoT device, and obtain an installation code for the new IoT device from the server (310) based on the device identification information.

[0162] Figure 11 is a signal flow diagram illustrating a hub onboarding procedure according to one embodiment. Depending on the embodiments, at least one of the operations described below may be omitted, modified, or the order may be changed.

[0163] Referring to FIG. 11, in operation 1102, the electronic device (201) may establish a first connection (e.g., a Wi-Fi connection, a Bluetooth connection, or a BLE connection) with the hub device (330). In one embodiment, the hub device (330) may authenticate the electronic device (201) based on a hub serial number received from the electronic device (201) through the first connection. In operation 1104, the electronic device (1104) may transmit connection information (e.g., AP information) to the hub device (330) to be used for a second connection between the server (310) and the hub device (330).

[0164] In operation 1106, the hub device (330) may establish a second connection (e.g., an Internet connection) with the server (310) using the connection information. In operation 1108, the hub device (330) may transmit an onboarding request to the server (310) via the second connection. In one embodiment, the onboarding request may include device information of the hub device (330) (e.g., at least one of a hub serial number, a hub device ID, or a hub model name). In operation 1110, the server (310) may store the device information of the hub device (330) in response to the onboarding request and transmit an onboarding response to the hub device (330). In one embodiment, the server (310) may transmit the onboarding response when device onboarding for all of at least one IoT device (320) included in the installation data (505) is completed. In one embodiment, the server (310) may transmit the onboarding response whenever device onboarding is completed for any one IoT device (320) included in the installation data (505). In one embodiment, when device onboarding is completed for all of at least one IoT device (320) included in the installation data (505), the hub device (330) may release the second connection with the server (310).

[0165] In operation 1112, the server (310) may transmit an onboarding result to the electronic device (201) based on the installation data (505) associated with the package (500), indicating that device onboarding for at least one IoT device (320) included in the installation data (505) is completed. In one embodiment, the server (310) may transmit the onboarding result when device onboarding for all of the at least one IoT device (320) included in the installation data (505) is completed. In one embodiment, the server (310) may transmit the onboarding result whenever device onboarding for any one IoT device (320) included in the installation data (505) is completed. In operation 1114, the electronic device (201) may release the first connection with the hub device (330) based on receiving the onboarding result.

[0166] FIG. 12 is a diagram for explaining an IoT environment including a hub device according to one embodiment.

[0167] Referring to FIG. 12, in an IoT environment (1200), an electronic device (201) may perform a device onboarding procedure to register at least one IoT device (320) (e.g., IoT devices (320a, 320b, 320c, 320d)) to the electronic device (201) while communicating directly with a hub device (330) through a first connection (1210) (e.g., a Wi-Fi connection or a BLE connection) instead of through a server (310). In one embodiment, the electronic device (201) may receive installation data (505) related to a package (500) including a hub device (330) and at least one IoT device (320) from a server (e.g., server (310)) (e.g., operation 818) and transmit the installation data (505) (e.g., installation code (505a)) to the hub device (330) (e.g., operation 822).

[0168] In one embodiment, the hub device (330) can perform a device onboarding procedure to register at least one IoT device (320) to the electronic device (201) based on the installation data (505) without going through a server (e.g., server (310)). In one embodiment, the hub device (330) can enter a join mode for performing the device onboarding procedure after receiving the installation data (505). In the join mode, the hub device (330) can identify at least one IoT device (320) (e.g., IoT device (320a)) based on the installation data (505) (e.g., device ID), discover the IoT device (320a), and establish a second connection (1220) (e.g., Zigbee connection, Zwave connection, or BLE connection) with the discovered IoT device (320a). The hub device (330) can perform encrypted communication with the discovered IoT device (320a) through the second connection (1220) based on the installation code (505a) obtained from the installation data (505).

[0169] In the join mode, the hub device (330) can request the electronic device (201) to create a device record for the discovered IoT device (320a) and receive an onboarding response from the electronic device (201). In one embodiment, the electronic device (201) can store and manage information (e.g., sensor data and / or status information) collected from at least one IoT device (320) in the device record created through the device onboarding procedure. In one embodiment, the electronic device (201) can share the device record created through the device onboarding procedure with the server (310).

[0170] FIG. 13 is a diagram for explaining an IoT environment that does not include a hub device according to one embodiment.

[0171] Referring to FIG. 13, in an IoT environment (1300), an electronic device (201) may perform a device onboarding procedure to register at least one IoT device (320) to the electronic device (201) through a first connection (1310) without going through a hub device (e.g., hub device (330)). In one embodiment, the electronic device (201) may receive installation data (505) related to a package (500) including at least one IoT device (320) from a server (e.g., server (310)) (e.g., operation 818).

[0172] In one embodiment, the electronic device (201) can perform a device onboarding procedure to register at least one IoT device (320) to the electronic device (201) based on the installation data (505) without going through a server (e.g., server (310)). In one embodiment, the electronic device (201) can enter a join mode for performing the device onboarding procedure after receiving the installation data (505). In the join mode, the electronic device (201) can identify at least one IoT device (320) (e.g., IoT device (320a)) based on the installation data (505) (e.g., device ID), discover the IoT device (320a), and establish a first connection (1310) (e.g., Zigbee connection, Zwave connection, or BLE connection) with the discovered IoT device (320a). The electronic device (201) can perform encrypted communication with the discovered IoT device (320a) through the first connection (1310) based on the installation code (505a) obtained from the installation data (505).

[0173] In one embodiment, in the join mode, the electronic device (201) may create a device record for the discovered IoT device (320a). In one embodiment, the electronic device (201) may store and manage information (e.g., sensor data and / or status information) collected from at least one IoT device (320) in the device record created through the device onboarding procedure. In one embodiment, the electronic device (201) may share the device record created through the device onboarding procedure with the server (310).

[0174] In one embodiment, the electronic device (201) may be configured to include the functionality of at least one of the hub device (330) or the server (310) described above. The installation data (e.g., the installation data (505)) may include information necessary to directly connect with each of at least one IoT device (320). In one embodiment, the installation data (505) may include the Wi-Fi AP SSID and / or password of each IoT device (320). In one embodiment, the installation data (505) may include identification information of each IoT device (320) (e.g., a device ID, a serial number, and / or a MAC address). In one embodiment, the installation data (505) may include device information necessary for the electronic device (201) to connect with each IoT device (320) using BLE, such as at least one of a manufacturer ID, model information (model name and / or model code), setup ID, serial number, or MAC address.

[0175] In one embodiment, the electronic device (201) can connect to each IoT device (320) based on the installation data (505). In one embodiment, at least one of the IoT devices (e.g., the IoT device (320a)) can operate as a Wi-Fi AP and broadcast a beacon signal. The electronic device (201) can discover the IoT device (320a) by receiving a beacon signal of the IoT device (320a) operating as an AP having a Wi-Fi SSID and MAC address included in the installation data (505), and can establish a Wi-Fi connection with the discovered IoT device (320a). In one embodiment, the electronic device (201) can discover the IoT device (320a) by receiving a BLE advertising signal broadcast from the IoT device (320a), and can establish a BLE connection with the discovered IoT device (320a).

[0176] In one embodiment, the electronic device (201) may transmit connection information to the IoT device (320a) to enable Internet connection via the established connection (e.g., Wi-Fi connection or BLE connection). The connection information may include at least one of a Wi-Fi AP SSID, password, or security protocol type of an AP (not shown) providing Internet connection. The IoT device (320a) may use the connection information to establish an Internet connection via the AP.

[0177] In one embodiment, the electronic device (201) may transmit server information that enables the IoT device (320a) to access the server (310) to the IoT device (320a) via the established connection (e.g., Wi-Fi connection or BLE connection). In one embodiment, the server information may include at least one of a server URL and / or a security token. The IoT device (320a) may register with the server (310) via the Internet connection using the server information. The electronic device (201) may repeat the above-described procedure for each IoT device included in the installation data (505).

[0178] An electronic device (201) according to one embodiment may include a communication circuit (290) and at least one processor (220) operatively connected to the communication circuit. The at least one processor may be configured to obtain installation data (505) necessary for a first external electronic device (330) to register at least one second external electronic device (320) with a server (310). The at least one processor may be configured to perform a first onboarding procedure for registering the first external electronic device with the server (310) via the communication circuit. The at least one processor may be configured to transmit the installation data to the first external electronic device via the communication circuit after performing the first onboarding procedure. The at least one processor may be configured to display an installation guide for onboarding the at least one second external electronic device based on the installation data. The at least one processor may be configured to receive from the server via the communication circuit an onboarding result indicating that the at least one second external electronic device has been onboarded by the first external electronic device.

[0179] In one embodiment, the installation data may include at least one of a serial number of the first external electronic device, a device identifier (ID) of each of the at least one second external electronic device, or an installation code including a security key used by the first external electronic device to onboard the at least one second external electronic device.

[0180] In one embodiment, the installation data may further include at least one of a package identifier (ID) identifying a package including the first external electronic device and the at least one second external electronic device, a product model name of the package, a device identifier (ID) of the first external electronic device, a model name of the first external electronic device, a model code of each of the at least one second external electronic device, or a model name of each of the at least one second external electronic device.

[0181] In one embodiment, the at least one processor may be configured to receive the installation data from the server or the first external electronic device based on at least one of the serial number or the package ID of the first external electronic device.

[0182] In one embodiment, the at least one processor may be configured to request the serial number of the first external electronic device from the server based on a user account identifier (ID), and to receive the serial number of the first external electronic device from the server.

[0183] In one embodiment, the at least one processor may be configured to obtain the serial number of the first external electronic device from a machine-readable indicator of the first external electronic device.

[0184] In one embodiment, the installation guide may include a message guiding a user operation to set the at least one second external electronic device into a setup mode so that the at least one second external electronic device can be connected to the first external electronic device.

[0185] In one embodiment, the message may include at least one of guide information requesting the at least one second external electronic device to capture a machine-readable indicator of the at least one second external electronic device through a camera of the electronic device, guide information requesting the at least one second external electronic device to press a designated button, guide information requesting the at least one second external electronic device to mount a battery on the at least one second external electronic device, or guide information requesting the at least one second external electronic device to power on.

[0186] In one embodiment, the at least one processor may be configured to receive the installation guide from the server based on the installation data.

[0187] In one embodiment, the at least one processor may be configured to perform a second onboarding procedure for registering the at least one second external electronic device with the server based on the installation data.

[0188] A method of operating an electronic device (201) according to one embodiment may include an operation (605) of obtaining installation data (505) required for a first external electronic device (330) to register at least one second external electronic device (320) with a server (310). The method may include an operation (610) of performing a first onboarding procedure for registering the first external electronic device with the server (310). The method may include an operation (615) of transmitting the installation data to the first external electronic device after performing the first onboarding procedure. The method may include an operation (620) of displaying an installation guide for onboarding the at least one second external electronic device based on the installation data. The method may include an operation (625) of receiving an onboarding result from the server indicating that the at least one second external electronic device has been onboarded by the first external electronic device.

[0189] In one embodiment, the installation data may include at least one of a serial number of the first external electronic device, a device identifier (ID) of each of the at least one second external electronic device, or an installation code including a security key used by the first external electronic device to onboard the at least one second external electronic device.

[0190] In one embodiment, the installation data may further include at least one of a package identifier (ID) identifying a package including the first external electronic device and the at least one second external electronic device, a product model name of the package, a device identifier (ID) of the first external electronic device, a model name of the first external electronic device, a model code of each of the at least one second external electronic device, or a model name of each of the at least one second external electronic device.

[0191] In one embodiment, the method may further include receiving the installation data from the server or the first external electronic device based on at least one of the serial number or the package ID of the first external electronic device.

[0192] In one embodiment, the method may further include an operation of requesting the serial number of the first external electronic device from the server based on a user account identifier (ID), and an operation of receiving the serial number of the first external electronic device from the server.

[0193] In one embodiment, the method may further comprise obtaining the serial number of the first external electronic device from a machine-readable indicator of the first external electronic device.

[0194] In one embodiment, the installation guide may include a message guiding a user operation to set the at least one second external electronic device into a setup mode so that the at least one second external electronic device can be connected to the first external electronic device.

[0195] In one embodiment, the message may include at least one of guide information requesting the at least one second external electronic device to capture a machine-readable indicator of the at least one second external electronic device through a camera of the electronic device, guide information requesting the at least one second external electronic device to press a designated button, guide information requesting the at least one second external electronic device to mount a battery on the at least one second external electronic device, or guide information requesting the at least one second external electronic device to power on.

[0196] In one embodiment, the method may further include receiving the installation guide from the server based on the installation data.

[0197] In one embodiment, the method may further include performing a second onboarding procedure for registering the at least one second external electronic device with the server based on the installation data.

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

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

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

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

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

[0203] 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 the electronic device (201), Communication circuit (290); and At least one processor (220) operatively connected to the communication circuit, wherein the at least one processor comprises: A first external electronic device (330) obtains installation data (505) required to register at least one second external electronic device (320) to a server (310), Performing a first onboarding procedure to register the first external electronic device (330) to the server (310) through the communication circuit; After performing the above first onboarding procedure, the installation data is transmitted to the first external electronic device through the communication circuit, Display an installation guide for onboarding at least one second external electronic device based on the above installation data, An electronic device characterized in that it is configured to receive from the server through the communication circuit an onboarding result indicating that at least one second external electronic device has been onboarded by the first external electronic device.

2. In paragraph 1, the installation data is: An electronic device characterized in that it comprises at least one of a serial number of the first external electronic device, a device identifier (ID) of each of the at least one second external electronic device, or an installation code comprising a security key used by the first external electronic device to onboard the at least one second external electronic device.

3. In the second paragraph, the installation data is A package identifier (ID) that identifies a package including the first external electronic device and the at least one second external electronic device; Product model name of the above package, A device identifier (ID) of the first external electronic device, The model name of the above first external electronic device, the model code of each of the at least one second external electronic devices, or An electronic device characterized in that it further comprises at least one model name of each of the at least one second external electronic device.

4. In the second or third paragraph, the at least one processor, An electronic device characterized in that it is configured to receive at least a portion of the installation data from the server or the first external electronic device based on at least one of the serial number or the package ID of the first external electronic device.

5. In the fourth paragraph, the at least one processor, Requesting the serial number of the first external electronic device from the server based on the user account identifier (ID), An electronic device characterized in that it is configured to receive a serial number of the first external electronic device from the server.

6. In the fourth paragraph, the at least one processor, An electronic device characterized in that it is configured to obtain at least a portion of the serial number and / or the installation data of the first external electronic device based on a machine-readable indicator of the first external electronic device.

7. In any one of paragraphs 1 to 6, the installation guide, An electronic device characterized in that it includes a message guiding a user operation to set the at least one second external electronic device into a setup mode so that the at least one second external electronic device can be connected to the first external electronic device.

8. In paragraph 7, the message, An electronic device characterized in that it comprises at least one of guide information requesting, for the at least one second external electronic device, capturing a machine-readable indicator of the at least one second external electronic device through a camera of the electronic device, guide information requesting pressing a designated button of the at least one second external electronic device, guide information requesting mounting a battery in the at least one second external electronic device, or guide information requesting turning on the at least one second external electronic device.

9. In any one of paragraphs 1 to 8, the at least one processor, An electronic device characterized in that it is configured to receive the installation guide from the server based on the installation data.

10. In any one of paragraphs 1 to 9, the at least one processor, An electronic device characterized in that it is configured to perform a second onboarding procedure for registering the at least one second external electronic device with the server based on the installation data.

11. In the operating method of an electronic device (201), An operation (605) in which a first external electronic device (330) obtains installation data (505) necessary to register at least one second external electronic device (320) with a server (310), An operation (610) of performing a first onboarding procedure for registering the first external electronic device (330) to the server (310), After performing the above first onboarding procedure, the operation (615) of transmitting the installation data to the first external electronic device; An operation (620) of displaying an installation guide for onboarding at least one second external electronic device based on the above installation data; A method characterized by comprising the action (625) of receiving an onboarding result from the server indicating that at least one second external electronic device has been onboarded by the first external electronic device.

12. In paragraph 11, the installation data is: an installation code comprising a serial number of the first external electronic device, a device identifier (ID) of each of the at least one second external electronic device, or a security key used by the first external electronic device to onboard the at least one second external electronic device; A package identifier (ID) identifying a package including the first external electronic device and the at least one second external electronic device, a product model name of the package, a device identifier (ID) of the first external electronic device, a model name of the first external electronic device, a model code of each of the at least one second external electronic device, or at least one model name of each of the at least one second external electronic device, The above method, A method further comprising an action of receiving the installation data from the server or the first external electronic device based on at least one of the serial number or the package ID of the first external electronic device.

13. In paragraph 12, An action of requesting the serial number of the first external electronic device to the server based on a user account identifier (ID) and receiving the serial number of the first external electronic device from the server, or A method further comprising the action of obtaining the serial number of the first external electronic device from a machine-readable indicator of the first external electronic device.

14. In any one of paragraphs 11 to 13, the installation guide, Including a message guiding a user operation to set the at least one second external electronic device to a setup mode so that the at least one second external electronic device can be connected to the first external electronic device; The above message is, A method characterized in that it comprises at least one of guide information requesting, for the at least one second external electronic device, capturing a machine-readable indicator of the at least one second external electronic device through a camera of the electronic device, guide information requesting pressing a designated button of the at least one second external electronic device, guide information requesting mounting a battery in the at least one second external electronic device, or guide information requesting turning on the at least one second external electronic device.

15. In any one of paragraphs 11 to 14, An action of receiving the installation guide from the server based on the installation data, and / or A method further comprising performing a second onboarding procedure for registering the at least one second external electronic device to the server based on the installation data.