Patent Description:
With the development of information technology (IT), the Internet of things (IoT) technology (or smart home technology) that connects electronic devices such as household appliances including a television (TV), an air conditioner, or a refrigerator energy consumption devices, such as water, electricity, air conditioning and heating, and security devices, such as a door lock, a surveillance camera, a motion detection sensor, an opening/closing detection sensor, and a siren to a single communication network have appeared. The IoT technology may monitor and control the electronic devices over the single communication network.

A user may control things in the house with simple manipulation of an electronic device, such as a mobile device, through the IoT technology. For example, the user may control a curtain and may adjust the brightness of the lighting, by manipulating the electronic device. Alternatively, the user may also adjust the room temperature by manipulating the electronic device.

Known in the art is <CIT> which discloses a system and method for virtualizing Internet of Things (IoT) devices and hubs. For example, one embodiment of a system comprises: a primary Internet of Things (IoT) cloud service to register IoT devices owned by users who have subscribed with the primary IoT cloud service; IoT device management logic on the primary IoT cloud service to provide access to data generated by the primary IoT devices and to control the IoT devices responsive to user input; the IoT device management logic to establish a communication channel with an external IoT cloud service responsive to a user registering one or more external IoT devices controlled by the external IoT cloud service; and wherein upon the external IoT cloud service providing the IoT device management logic with access to the one or more external IoT devices, the IoT device management logic to generate virtual representations of the one or more external IoT devices to allow user access to information generated by the external IoT devices and to allow the user to control the external IoT devices through the virtual representations.

Also known in the art is <CIT> which discloses a method of operating a hub used in an internet of things (IoT) network system which includes a first controller and an IoT device is provided. The method includes: performing secure pairing with the first controller using a first communication, receiving first information related to the IoT device from the first controller paired with the hub, authenticating the first controller using the first information, and performing secure pairing with the IoT device using a second communication.

As described above, it may be necessary for an operation of connecting each of IoT devices to a server, to build a smart home using the IoT technology. For example, a user may connect the TV to the server, may connect an air conditioner to the server, and then may connect lighting to the server, via an electronic device.

However, as described above, the conventional manner for connecting IoT devices to the server is complex and time-consuming. In addition, as the number of IoT devices for building the smart home increases, the time required to build the smart home may further increase. It is time-consuming and inconvenient for a user to connect each of a plurality of IoT devices to the server. Accordingly, there is a need in the art for a more efficient, convenient, and user-friendly manner of connecting such IoT devices to a server.

Accordingly, an aspect of the disclosure is to provide an electronic device providing a more efficient and convenient manner of connecting IoT devices to a server.

In accordance with an aspect of the disclosure, an electronic device is provided according to appended claim <NUM>.

In accordance with another aspect of the disclosure, a smart home system is provided according to the corresponding independent apparatus claim. Preferred embodiments are covered by the dependent claims.

According to embodiments, an operation of connecting a plurality of IoT devices to a server may be simplified. A user may save the time required to build a smart home and the user's convenience may be enhanced. A variety of effects directly or indirectly understood through this disclosure may be provided.

Hereinafter, embodiments of the disclosure will be described with reference to accompanying drawings. Detailed descriptions of known functions and configurations incorporated here will be omitted for the sake of clarity and conciseness.

The electronic device according to embodiments may be a smart phone, a computer device, a portable multimedia device, a portable medical device, a camera, a wearable device, or a home appliance, but the electronic devices are not limited to those described above.

The terms used herein are not intended to limit the technological features set forth herein to particular embodiments and include various changes, equivalents, or replacements for a corresponding embodiment.

As used herein, such terms as "1st" and "2nd," or "first" and "second" may be used to distinguish a corresponding component from another, and do not limit the components in importance or order. It is to be understood that if a first element is referred to, with or without the term "operatively" or "communicatively", as "coupled [EDIT1]with,""coupled to," "connected with", or "connected to" a second element, the element may be coupled with the other element wiredly, wirelessly, or via a third element.

<FIG> illustrates a smart home implemented by connecting a plurality of IoT devices to a server through a hub, according to an embodiment.

Referring to <FIG>, a smart home <NUM> may include a plurality of IoT devices <NUM>, a hub <NUM>, a server <NUM>, and an electronic device <NUM>, but are not limited to that illustrated in <FIG> and may further include a sub hub that connects the hub <NUM> to the plurality of IoT devices <NUM>.

The plurality of IoT devices <NUM> may include a TV <NUM>, a refrigerator <NUM>, a tablet <NUM>, a notebook <NUM>, and/or an air conditioner <NUM>. The plurality of IoT devices <NUM> may include electronic devices such as a sensor, a washer, an electric heater, a telephone, a door lock, or a surveillance camera, or may include devices that control water, electricity, air conditioning and heating.

The plurality of IoT devices <NUM> may be connected to the server <NUM> through the hub <NUM>. Device identifiable information respectively corresponding to the plurality of IoT devices <NUM> may be transmitted to the server <NUM> by the electronic device <NUM>. Each of the plurality of IoT devices <NUM> may be connected to the hub <NUM> corresponding to hub identifiable information registered in the server <NUM> after being paired with the hub <NUM>. The plurality of IoT devices <NUM> may communicate with the server <NUM> via the connection to the hub <NUM>.

At least one bar code, such as a one-dimensional bar code or a two-dimensional bar code (or QR code) or at least one serial number including the device identifiable information of each IoT device may be attached to each of the plurality of IoT devices <NUM>.

For example, the single bar code or the single serial number may be attached to a package or a box including the plurality of IoT devices <NUM>, and may include device identifiable information about the plurality of IoT devices <NUM> included in the package or the box. Alternatively, bar codes or serial numbers including device identifiable information may be attached to the plurality of IoT devices <NUM>, respectively.

The hub <NUM> may relay the connection between the plurality of IoT devices <NUM> and the server <NUM>, and may perform the function of a router, a bridge, or an access point.

The hub <NUM> may perform low-power communication with the plurality of IoT devices <NUM>, such as through one of a Bluetooth®, ZigBee®, or wireless highway addressable remote transducer (HART) communication scheme.

The hub <NUM> may communicate with the server <NUM> through one of a wireless fidelity (Wi-Fi), Wi-Fi direct, global system for mobile communications (GSM), high-speed downlink packet access (HSDPA), long-term evolution (LTE), LTE advanced (LTE-A), code division multiple access (CDMA), CDMA2000, or wireless broadband (WiBro) communication schemes.

The server <NUM> may include a processor and a wireless communication circuit. The processor may control overall operations of the server <NUM>. The server <NUM> may communicate with the hub <NUM> using the wireless communication circuit or may communicate with the plurality of IoT devices <NUM> via the hub <NUM>.

The server <NUM> may register a user account based on user information received through the electronic device <NUM>. The user account may include at least one of the user's name, the user's email address, the user's identifiable information, the registered hub, or the registered IoT devices.

Identifiable information about the hub <NUM> and the plurality of IoT devices <NUM>, which are used by the user, may be added to the user account. For example, the user may transmit hub identifiable information to the server <NUM> through the electronic device <NUM>. The hub identifiable information may be added to the account of the user. Alternatively, the user may transmit device identifiable information to the server <NUM> through the electronic device <NUM>, and the device identifiable information may be added to the account of the user.

The hub <NUM> corresponding to hub identifiable information and the plurality of IoT devices <NUM> corresponding to device identifiable information, which are added to one user account are devices capable of being paired with each other. The server <NUM> may enable the plurality of IoT devices <NUM> and the hub <NUM> to be paired with each other, by transmitting the device identifiable information to the hub <NUM> corresponding to the hub identifiable information.

The electronic device <NUM> may include a processor and a wireless communication circuit. The processor may control overall operations of the electronic device <NUM>. The electronic device <NUM> may communicate with the server <NUM>, using the wireless communication circuit. The electronic device <NUM> may further include a display, a camera, or an input/output module, and may include a configuration that is the same as or similar to the configuration of an electronic device <NUM> illustrated in <FIG>.

The electronic device <NUM> transmits identifiable information such that the plurality of IoT devices <NUM>, the hub <NUM>, and the server <NUM> communicate with one another. For example, the electronic device <NUM> may transmit the device identifiable information about the plurality of IoT devices <NUM> and the hub identifiable information about the hub <NUM>, to the server <NUM> through a specified application. As such, the server <NUM> may recognize the plurality of IoT devices <NUM> and the hub <NUM> as a target for communication.

The electronic device <NUM> may obtain the hub identifiable information about the hub <NUM> and then may transmit the hub identifiable information to the server <NUM>. For example, the electronic device <NUM> may obtain the hub identifiable information from a user input through an input module and may transmit the hub identifiable information to the server <NUM>, using the wireless communication circuit.

The electronic device <NUM> may obtain device identifiable information about the plurality of IoT devices <NUM>, at one time or sequentially, through a bar code or a serial number including the device identifiable information.

For example, the electronic device <NUM> may obtain an image associated with the bar code or the serial number, using a camera and then may obtain the device identifiable information, using the obtained image. Alternatively, the electronic device <NUM> may obtain a user input associated with the serial number via an input module and may obtain the device identifiable information, using the obtained serial number.

The electronic device <NUM> may obtain a single bar code or a single serial number including the device identifiable information, and may obtain the device identifiable information using the obtained single bar code or single serial number.

Alternatively, the electronic device <NUM> may sequentially obtain a single bar code or a single serial number including the single device identifiable information to obtain a plurality of bar codes or a plurality of serial numbers, and may obtain the device identifiable information using the sequentially obtained plurality of bar codes or plurality of serial numbers.

The electronic device <NUM> may transmit the device identifiable information obtained as described above, to the server <NUM> by using a wireless communication circuit.

After obtaining identifiable information about at least one device of the plurality of IoT devices <NUM>, the electronic device <NUM> may register the at least one device in the server <NUM>, and may provide a user with a guide for registering the remaining IoT devices other than the at least one device among the plurality of IoT devices <NUM>, in the server <NUM>. The guide may be based on information, which has been stored in the server <NUM>. The user may register the remaining IoT devices in the server <NUM> based on the guide displayed in the electronic device <NUM>. The guide may include information about how to apply power to the plurality of IoT devices <NUM>, or information about how the plurality of IoT devices <NUM> enters a pairing mode.

<FIG> illustrates an operation of connecting a plurality of IoT devices to a server through a hub, according to an embodiment.

In the following description, the operation of each of the plurality of IoT devices <NUM>, the hub <NUM>, the server <NUM>, and the electronic device <NUM> is performed by the processor included in each device, and an operation in which data or information is transmitted among the devices is performed by the wireless communication circuit controlled by the processor.

Steps <NUM> to <NUM> may not be limited to the order illustrated in <FIG>. For example, steps <NUM> to <NUM> may be simultaneously performed with steps <NUM> to <NUM>. Alternatively, steps <NUM> to <NUM> may be performed after steps <NUM> to <NUM> are performed.

In step <NUM>, the electronic device <NUM> may transmit user information to the server <NUM>. For example, the user information may include identifiable information of the electronic device <NUM> for registering the user account, or identifiable information of a user.

In step <NUM>, the server <NUM> may register a user account based on the user information received in step <NUM>. The identifiable information about the electronic device <NUM> may be added to the user account. When the user account is registered in the server <NUM>, the electronic device <NUM> may access the server <NUM> through the user account. Various IoT devices used by the user, such as a TV, a refrigerator, or a computer may be registered in the user account.

In step <NUM>, the electronic device <NUM> may attempt to obtain hub identifiable information about the hub <NUM>. For example, the electronic device <NUM> may capture a bar code including the hub identifiable information, through a camera, or may obtain a serial number including the hub identifiable information, through a user input.

In step <NUM>, the electronic device <NUM> may obtain the hub identifiable information through the image of the bar code or the serial number obtained in step <NUM>.

In step <NUM>, the electronic device <NUM> may transmit the hub identifiable information obtained in step <NUM>, to the server <NUM>.

In step <NUM>, the server <NUM> may add the hub identifiable information received from the electronic device <NUM> to the user account registered in step <NUM>. Because the electronic device <NUM> is added to the user account, the server <NUM> may recognize that a hub corresponding to the hub identifiable information added to the user account is a device of the user without a separate authentication procedure. When adding the hub identifiable information to the user account, the server <NUM> may make a request for a separate authentication procedure to the electronic device <NUM>.

In step <NUM>, the electronic device <NUM> may attempt to obtain device identifiable information about the plurality of IoT devices <NUM>. For example, the electronic device <NUM> may capture a bar code including the device identifiable information, through a camera, or may obtain a serial number including the device identifiable information, through a user input.

At least a piece of device identifiable information may be included in the bar code or the serial number. The electronic device <NUM> may attempt to obtain the device identifiable information, by capturing at least one bar code in one instance or in several instances or by obtaining at least one serial number.

In step <NUM>, the electronic device <NUM> may obtain device identifiable information through the image of the bar code or the serial number obtained in step <NUM>. Because the image of the bar code or the serial number includes at least one device identifiable information, the user may easily obtain device identifiable information through the image of the bar code or the serial number in a simplified procedure.

In step <NUM>, the electronic device <NUM> may transmit the device identifiable information obtained in step <NUM>, to the server <NUM>, in one instance or in several instances.

The electronic device <NUM> may transmit only the part of the obtained device identifiable information, to the server <NUM>. For example, the electronic device may output a specified message for displaying the obtained device identifiable information, on a display, and may obtain a user input and may select a part of the device identifiable information based on the obtained user input.

In step <NUM>, the server <NUM> may add the device identifiable information received from the electronic device <NUM> to the user account registered in step <NUM>. Because the electronic device <NUM> is added to the user account, the server <NUM> may recognize that the plurality of IoT devices <NUM>, the device identifiable information of each of which is received through the electronic device <NUM>, are devices of the user without a separate authentication procedure. When adding the device identifiable information to the user account, the server <NUM> may make a request for a separate authentication procedure to the electronic device <NUM>.

In step <NUM>, the server <NUM> and the hub <NUM> may be electrically connected to each other. Because the hub identifiable information is added to the user account registered in the server <NUM> in step <NUM>, the server <NUM> may recognize the hub <NUM> as the authenticated device and may communicate with the hub <NUM>. The server <NUM> and the hub <NUM> may transmit specified data or the specified signal to each other through a wireless communication circuit of each other.

In step <NUM>, the server <NUM> may transmit the device identifiable information added to the user account, to the hub <NUM>. Because a plurality of IoT devices corresponding to the device identifiable information correspond to the authenticated devices added to the user account, the IoT devices may be allowed to connect to the hub <NUM>.

In step <NUM>, the hub <NUM> may make a request for pairing to a plurality of IoT devices corresponding to device identifiable information received from the server <NUM>. Because the plurality of IoT devices <NUM> are devices added to the user account, the hub <NUM> may make a request for pairing, without a separate authentication procedure.

In step <NUM>, the plurality of IoT devices <NUM> may accept the pairing in response to the request for the pairing of the hub <NUM> performed in step <NUM>. The plurality of IoT devices <NUM> may communicate with the hub <NUM> and may communicate with the server <NUM> through the hub <NUM>.

<FIG> illustrates an operation in which an electronic device connects a plurality of IoT devices to a server, according to an embodiment.

In step <NUM>, the electronic device <NUM> may transmit user information to the server <NUM>. The user information may be information for the server <NUM> to register a user account. For example, the user information may include identifiable information, such as a device serial number of the electronic device <NUM> or identifiable information, such as an ID, a password, or a name of the user.

In step <NUM>, the electronic device <NUM> may transmit hub identifiable information to the server <NUM>, such as the serial number, manufacture number, model name, or ID of the hub <NUM>.

The hub identifiable information may be obtained through the bar code or the serial number attached to the hub <NUM>. For example, the electronic device <NUM> may obtain an image associated with the bar code or the serial number, through a camera. The processor included in the electronic device <NUM> may analyze the image to obtain hub identifiable information. Alternatively, the electronic device <NUM> may obtain the serial number through a user input and then may obtain the hub identifiable information through the serial number.

The hub identifiable information may be added to the user account registered in the server <NUM>. The hub <NUM> corresponding to the hub identifiable information is authenticated as the user's device when the hub identifiable information is added to the user account.

In step <NUM>, the electronic device <NUM> may obtain device identifiable information, which may include the serial number of the IoT device, the type of the IoT device, or the model name of the IoT device.

The device identifiable information may be obtained through the bar code or the serial number attached to a plurality of IoT devices. For example, the electronic device <NUM> may obtain an image associated with a single bar code or a single serial number including device identifiable information, through a camera. The processor included in the electronic device <NUM> may analyze the image to obtain device identifiable information. Alternatively, the electronic device <NUM> may obtain the serial number through a user input and then may obtain the device identifiable information through the serial number.

Alternatively, the electronic device <NUM> may obtain the device identifiable information through a plurality of bar codes or a plurality of serial numbers. For example, the electronic device <NUM> may obtain first device identifiable information through the bar code or the serial number attached to a single IoT device, may obtain second device identifiable information through another bar code or another serial number attached to another IoT device, and may sequentially obtain device identifiable information through the procedure.

In step <NUM>, the electronic device <NUM> may transmit the device identifiable information obtained in step <NUM>, to the server <NUM>. The device identifiable information may be added to the user account registered in the server <NUM>. It may be understood that IoT devices corresponding to the device identifiable information are authenticated as the user's device when the device identifiable information is added to the user account.

When both the hub identifiable information and the device identifiable information are transmitted from the electronic device <NUM> to the server <NUM>, the server <NUM> may be electrically connected to the hub <NUM> and may be electrically connected to the plurality of IoT devices <NUM> through the hub <NUM>.

<FIG> illustrates an operation in which an electronic device connects a plurality of IoT devices to a server, according to another embodiment.

Referring to <FIG>, steps <NUM> to <NUM> may be the same as or similar to steps <NUM> to <NUM> illustrated in <FIG>. For example, in steps <NUM> to <NUM>, the electronic device <NUM> may transmit user information for registering a user account and hub identifiable information about the hub <NUM>, to the server <NUM> and may obtain device identifiable information.

In step <NUM>, the electronic device <NUM> may identify hub identifiable information added to the user account, through the server <NUM>.

In step <NUM>, the electronic device <NUM> may determine whether the result in step <NUM> indicates that there is hub identifiable information added to the user account. When there is no hub identifiable information added to the user account, the electronic device <NUM> may perform step <NUM>. When determining that the hub identifiable information is added to the user account, the electronic device <NUM> may perform step <NUM>.

In step <NUM>, the electronic device <NUM> may output a specified message for transmitting the hub identifiable information to the server <NUM>, on a display. For example, when there is no registered hub identifiable information, the electronic device <NUM> may output a specified message or a pop-up window for requesting a user to install the hub <NUM> or to transmit hub identifiable information, on the display.

In step <NUM>, the electronic device <NUM> may determine whether the result in step <NUM> indicates that there is hub identifiable information added to the user account and indicating one hub. When hub identifiable information added to the user account indicates a plurality of hubs, the electronic device <NUM> may perform step <NUM>. When there is one piece of hub identifiable information added to the user account, the electronic device <NUM> may perform step <NUM>.

In step <NUM>, the electronic device <NUM> may output a specified message to the display such that the user selects hub identifiable information, which corresponds to the hub <NUM> to be connected to an IoT device, from among hub identifiable information. For example, the electronic device <NUM> may output the identified hub identifiable information, to the display and may output a specified message or a pop-up window for making a request for the selection of the user.

In step <NUM>, the electronic device <NUM> may obtain a user input corresponding to the specified message output in step <NUM>. For example, the electronic device <NUM> may obtain the user input to select one of the hub identifiable information.

In step <NUM>, the electronic device <NUM> may transmit hub identifiable information, which is selected by the user, from among hub identifiable information to the server <NUM>.

In step <NUM>, the electronic device <NUM> may transmit the device identifiable information obtained in step <NUM>, to the server <NUM>. The device identifiable information may be added to the user account registered in the server <NUM>. IoT devices corresponding to the device identifiable information are authenticated as the user's device when the device identifiable information is added to the user account.

Steps <NUM> and <NUM> to step <NUM> may be performed simultaneously, or any one of steps <NUM> and <NUM> to step <NUM> may be performed first. When both the hub identifiable information and the device identifiable information are transmitted from the electronic device <NUM> to the server <NUM>, the server <NUM> may be electrically connected to the single hub <NUM> and may be electrically connected to the plurality of IoT devices <NUM> through the hub <NUM>.

<FIG> illustrates an operation of a server, to which a plurality of IoT devices are connected, according to an embodiment.

In step <NUM>, the server <NUM> may receive user information from the electronic device <NUM>, which may include identifiable information, such as a device serial number of the electronic device <NUM> or identifiable information, such as an ID, a password, or a name of the user.

In step <NUM>, the server <NUM> may register a user account based on the user information received in step <NUM>.

In step <NUM>, the server <NUM> may receive hub identifiable information from the electronic device <NUM>.

In step <NUM>, the server <NUM> may add the hub identifiable information received from the electronic device <NUM>, to the user account. The server <NUM> may communicate with the hub <NUM> corresponding to the hub identifiable information, by adding the hub identifiable information to the user account. There may be hub identifiable information added to the user account.

In step <NUM>, the server <NUM> may receive device identifiable information from the electronic device <NUM> in several instances.

The server <NUM> may receive, from the electronic device <NUM>, a request for not only the device identifiable information but also hub identifiable information registered in the user account. The server <NUM> may transmit the hub identifiable information added to the user account to the electronic device <NUM>, in response to the request of the electronic device <NUM>. When there is no hub identifiable information added to the user account, the server <NUM> may make a request for the hub identifiable information to the electronic device <NUM>, in response to the request of the electronic device <NUM>. When hub identifiable information added to the user account are present, the server <NUM> may make a request for the selection one of the hub identifiable information, to the electronic device <NUM>, in response to the request of the electronic device <NUM>.

In step <NUM>, the server <NUM> may add the device identifiable information received from the electronic device <NUM>, to the user account. The server <NUM> may perform the authentication of an IoT device corresponding to the device identifiable information, by adding the device identifiable information to the user account. In other words, the server <NUM> may authenticate that the IoT device is the user's device, such that the hub <NUM> is paired with the IoT device.

The server <NUM> may connect the received device identifiable information to at least a piece of hub identifiable information added to the user account. For example, when the hub identifiable information added to the user account includes first hub identifiable information and second hub identifiable information, the server <NUM> may connect the received device identifiable information to the first hub identifiable information and may not connect the received device identifiable information to the second hub identifiable information. In this case, the plurality of IoT devices <NUM> corresponding to the received device identifiable information may be allowed to be paired with a first hub corresponding to the first hub identifiable information and may not be allowed to be paired with a second hub corresponding to the second hub identifiable information.

In step <NUM>, the server <NUM> may transmit the received device identifiable information to the hub <NUM> corresponding to hub identifiable information to which the device identifiable information are connected, and the hub <NUM> may attempt to pair the plurality of IoT devices <NUM> corresponding to the device identifiable information.

Steps <NUM> to <NUM> and steps <NUM> to <NUM> may be performed simultaneously, or any one of steps <NUM> to <NUM> and steps <NUM> to <NUM> may be performed first. The server <NUM> may be electrically connected to at least one the hub <NUM> through the operations and may be electrically connected to the plurality of IoT devices <NUM> through the hub <NUM>.

Referring to <FIG>, the electronic device <NUM> in the network environment <NUM> may communicate with an electronic device <NUM> via a first network <NUM>, such as a short-range wireless communication network, or an electronic device <NUM> or a server <NUM> via a second network <NUM>, such as a long-range wireless communication network, and may communicate with the electronic device <NUM> via the server <NUM>.

The electronic device <NUM> may include a processor <NUM>, memory <NUM>, an input device <NUM>, a sound output device <NUM>, a display device <NUM>, an audio module <NUM>, a sensor module <NUM>, an interface <NUM>, a haptic module <NUM>, a camera module <NUM>, a power management module <NUM>, a battery <NUM>, a communication module <NUM>, a subscriber identification module (SIM) <NUM>, or an antenna module <NUM>. At least one of the components may be omitted from the electronic device <NUM>, or one or more other components may be added in the electronic device <NUM>. Some of the components may be implemented as single integrated circuitry. For example, the sensor module <NUM> may be implemented as embedded in the display device <NUM>.

The processor <NUM> may execute a program <NUM> to control at least one other hardware or software component of the electronic device <NUM> coupled with the processor <NUM>, and may perform various data processing or computation. As at least part of the data processing or computation, the processor <NUM> may load a command or data received from another component in volatile memory <NUM>, process the command or the data stored in the volatile memory <NUM>, and store resulting data in non-volatile memory <NUM>. The processor <NUM> may include a main processor <NUM>, such as a central processing unit (CPU) or an application processor (AP), and an auxiliary processor <NUM>, such as a graphics processing unit (GPU), an image signal processor (ISP), a sensor hub processor, or a communication processor (CP), that is operable independently from, or in conjunction with, the main processor <NUM>. Additionally or alternatively, the auxiliary processor <NUM> may be adapted to consume less power than the main processor <NUM>, or to be specific to a specified function, and may be implemented as separate from, or as part of the main processor <NUM>.

The auxiliary processor <NUM> may control at least some of functions or states related to at least one component among the components of the electronic device <NUM>, instead of the main processor <NUM> while the main processor <NUM> is in an inactive (e.g., sleep) state, or together with the main processor <NUM> while the main processor <NUM> is in an active state. The auxiliary processor <NUM> may be implemented as part of another component functionally related to the auxiliary processor <NUM>.

The memory <NUM> may store various data used by at least one component of the electronic device <NUM>. The various data may include the program <NUM> and input data or output data for a command related thereto.

The program <NUM> may be stored in the memory <NUM> as software, and may include an operating system (OS) <NUM>, middleware <NUM>, and an application <NUM>.

The input device <NUM> may receive a command or data to be used by other component of the electronic device <NUM>, from the outside (e.g., a user) of the electronic device <NUM>, and may include a microphone, a mouse, or a keyboard, for example.

The sound output device <NUM>, such as a speaker or a receiver, may output sound signals to the outside of the electronic device <NUM>. The receiver may be implemented as separate from, or as part of the speaker.

The display device <NUM> may visually provide information to the user of the electronic device <NUM> and may include a display, a hologram device, or a projector and control circuitry to control a corresponding one of the display, hologram device, and projector. The display device <NUM> may include touch circuitry adapted to detect a touch, or a pressure sensor adapted to measure the intensity of force incurred by the touch.

The audio module <NUM> may obtain the sound via the input device <NUM>, or output the sound via the sound output device <NUM> or a headphone of an external electronic device <NUM> wiredly or wirelessly coupled with the electronic device <NUM>.

The sensor module <NUM> may detect an operational state of the electronic device <NUM> or an environmental state external to the electronic device <NUM>, and then generate an electrical signal or data value corresponding to the detected state. The sensor module <NUM> may include a gesture sensor, a gyro sensor, an atmospheric pressure sensor, a magnetic sensor, an acceleration sensor, a grip sensor, a proximity sensor, a color sensor, an infrared (IR) sensor, a biometric sensor, a temperature sensor, a humidity sensor, or an illuminance sensor.

The interface <NUM> may support one or more specified protocols to be used for the electronic device <NUM> to be coupled with the external electronic device <NUM> wiredly or wirelessly. The interface <NUM> may include a high definition multimedia interface (HDMI), a universal serial bus (USB) interface, a secure digital (SD) card interface, or an audio interface.

A connecting terminal <NUM> may include a connector via which the electronic device <NUM> may be physically connected with the external electronic device <NUM> and may include an HDMI connector, a USB connector, a SD card connector, or an audio connector.

The haptic module <NUM> may convert an electrical signal into a vibration or a movement or electrical stimulus which may be recognized by a user via his tactile sensation or kinesthetic sensation, and may include a motor, a piezoelectric element, or an electric stimulator.

The camera module <NUM> may capture a still image or moving images and may include one or more lenses, image sensors, image signal processors, or flashes.

The power management module <NUM> may manage power supplied to the electronic device <NUM>, and may be implemented as at least part of a power management integrated circuit (PMIC).

The battery <NUM> may supply power to at least one component of the electronic device <NUM> and may include a primary cell which is not rechargeable, a secondary cell which is rechargeable, or a fuel cell.

The communication module <NUM> may support establishing a wired or wireless communication channel between the electronic device <NUM> and the external electronic device and performing communication via the established communication channel. The communication module <NUM> may include one or more communication processors that are operable independently from the processor <NUM> and supports a wired or a wireless communication. The communication module <NUM> may include a wireless communication module <NUM>, such as a cellular communication module, a short-range wireless communication module, or a global navigation satellite system (GNSS) communication module, or a wired communication module <NUM>, such as a local area network (LAN) communication module or a power line communication (PLC) module.

A corresponding one of these communication modules may communicate with the external electronic device via the first network <NUM>, such as a short-range communication network, such as Bluetooth®, wireless-fidelity (Wi-Fi) direct, or infrared data association (IrDA), or the second network <NUM>, such as a long-range communication network including a cellular network, the Internet, or a LAN or wide area network (WAN). These various types of communication modules may be implemented as a single chip or as multi chips separate from each other. The wireless communication module <NUM> may identify and authenticate the electronic device <NUM> in a communication network, such as the first network <NUM> or the second network <NUM>, using subscriber information, such as an international mobile subscriber identity (IMSI) stored in the subscriber identification module <NUM>.

The antenna module <NUM> may transmit or receive a signal or power to or from an external electronic device of the electronic device <NUM>, may include one or more antennas, and, therefrom, at least one antenna appropriate for a communication scheme used in the communication network, such as the first network <NUM> or the second network <NUM>, may be selected by the communication module <NUM>.

At least some of the above-described components may be coupled mutually and communicate signals therebetween via an inter-peripheral communication scheme, such as a bus, general purpose input and output (GPIO), serial peripheral interface (SPI), or mobile industry processor interface (MIPI)).

To that end, a cloud, distributed, or client-server computing technology may be used, for example.

According to embodiments, an operation of connecting a plurality of IoT devices to a server may be simplified. A user may save the time required to build a smart home, thus enhancing the user's convenience.

According to an embodiment, an electronic device includes a wireless communication circuit communicating with a server, a memory storing instructions, and at least one processor electrically connected to the wireless communication circuit and the memory. The at least one processor may execute the stored instructions to transmit user information for registering a user account in the server, to the server, to transmit hub identifiable information to the server, using the wireless communication circuit to add the hub identifiable information corresponding to a hub to the user account registered in the server, to obtain device identifiable information corresponding to a plurality of IoT devices, and to transmit the device identifiable information to the server to add the device identifiable information to the user account registered in the server. The device identifiable information added to the user account may be used such that the hub corresponding to the hub identifiable information added to the user account and the plurality of IoT devices are paired with each other.

The at least one processor may execute the stored instructions to obtain at least one serial number including the device identifiable information, from a user input and to obtain the device identifiable information, using the obtained at least one serial number.

The electronic device may include a camera. The at least one processor may execute the stored instructions to obtain an image corresponding to at least one bar code including the device identifiable information, using the camera and to obtain the device identifiable information, using the obtained image.

The plurality of IoT devices may include a type of at least one of a sensor, a TV, a refrigerator, a tablet, a notebook, an air conditioner, a washer, an electric heater, a computer, a telephone, a dryer, a vacuum cleaner, a speaker, a dishwasher, a door lock, and a surveillance camera.

The wireless communication circuit may be configured to communicate with the server, using one of a Bluetooth®, ZigBee®, wireless highway addressable remote transducer (HART), Wi-Fi, Wi-Fi direct, GSM, HSDPA, LTE, LTE-A, CDMA, CDMA2000, WiBro, OFDMA, non-orthogonal multiple access (NOMA), or new radio access technology (NRAT) communication scheme.

The electronic device may further include a display. The at least one processor may execute the stored instructions to identify the hub identifiable information added to the user account from the server and to output a specified message to the display so as to transmit the hub identifiable information to the server when the identified result indicates that there is no hub identifiable information added to the user account.

The electronic device may further include a display. The at least one processor may execute the stored instructions to identify the hub identifiable information added to the user account from the server and to output a specified message for making a request for a user input to select a piece of hub identifiable information among the hub identifiable information, to the display when the identified result indicates that there are hub identifiable information added to the user account.

The at least one processor may execute the stored instructions to transmit the piece of hub identifiable information selected based on the user input, to the server.

According to an embodiment, a server includes a wireless communication circuit communicating with an external electronic device, a memory storing instructions, and at least one processor electrically connected to the wireless communication circuit. The at least one processor may execute the stored instructions to receive user information from the external electronic device, using the wireless communication circuit, to register a user account based on the received user information, to receive hub identifiable information about a hub from the external electronic device, using the wireless communication circuit to add the hub identifiable information about the hub to the user account, to receive device identifiable information about a plurality of IoT devices from the external electronic device, using the wireless communication circuit to add the device identifiable information about the plurality of IoT devices to the user account, and to transmit the device identifiable information to the hub corresponding to the hub identifiable information added to the user account. The device identifiable information may be used such that the hub and the plurality of IoT devices are paired with each other.

The at least one processor executes the stored instructions to transmit the hub identifiable information added to the user account to the external electronic device in response to a request of the external electronic device.

The at least one processor executes the stored instructions to make a request for the hub identifiable information to the external electronic device, when the hub identifiable information added to the user account is not present.

The at least one processor executes the stored instructions to request the external electronic device to select one of the hub identifiable information, when there are hub identifiable information added to the user account.

The plurality of IoT devices may include at least one of a sensor, a TV, a refrigerator, a tablet, a notebook, an air conditioner, a washer, an electric heater, a computer, a telephone, a door lock, and a surveillance camera.

The wireless communication circuit may communicate with the hub, using a Wi-Fi, Wi-Fi direct, GSM, HSDPA, LTE, LTE-A, CDMA, a CDMA2000, or WiBro communication scheme.

The at least one processor executes the stored instructions to communicate with the plurality of IoT devices paired with the hub, using the wireless communication circuit through the hub.

According to an embodiment, a smart home system includes a hub, a server, and an electronic device communicating with the server. The electronic device may be configured to transmit user information to the server such that a user account is registered in the server, to obtain hub identifiable information corresponding to the hub, to transmit the hub identifiable information to the server such that the hub identifiable information is added to the user account, to obtain device identifiable information corresponding to a plurality of IoT devices, and to transmit the device identifiable information to the server such that the device identifiable information are added to the user account. The server may be configured to transmit the device identifiable information added to the user account to the hub, and the hub may be paired with the plurality of IoT devices corresponding to the device identifiable information transmitted from the server.

The electronic device may be configured to obtain at least one serial number including the device identifiable information, from a user input and to obtain the device identifiable information, using the obtained at least one serial number.

The electronic device may include a camera. The electronic device may be configured to obtain an image corresponding to at least one bar code including the device identifiable information, using the camera and to obtain the device identifiable information, using the obtained image.

The hub may be configured to communicate with the plurality of IoT devices corresponding to the device identifiable information transmitted from the server, through a low-power communication scheme.

The low-power communication scheme may include one communication scheme of a Bluetooth® communication scheme, a ZigBee® communication scheme, or a HART communication scheme.

As used herein, the term "module" may include a unit implemented in hardware, software, or firmware, and may interchangeably be used with other terms such as "logic," "logic block," "part," or "circuitry". A module may be a single integral component, or a minimum unit or part thereof, adapted to perform one or more functions, and may be implemented in a form of an application-specific integrated circuit (ASIC).

Embodiments as set forth herein may be implemented as software including one or more instructions that are stored in a storage medium that is readable by a machine. For example, a processor of the machine may invoke at least one of the one or more instructions stored in the storage medium, and execute it, with or without using one or more other components under the control of the processor, thus enabling the machine to be operated to perform at least one function according to the at least one instruction invoked. Wherein, the term "non-transitory" indicates that the storage medium is a tangible device, and does not include a signal, but this term does not differentiate between where data is semi-permanently stored in the storage medium and where the data is temporarily stored in the storage medium.

According to an embodiment, a method may be included and provided in a computer program product, which may be traded as a product between a seller and a buyer, and may be distributed in the form of a machine-readable storage medium, such as a compact disc read only memory (CD-ROM), or downloaded or uploaded online via an application store or between two user devices directly.

Each component of the above-described components may include a single entity or multiple entities. One or more of the above-described components may be omitted, or one or more other components may be added. Alternatively or additionally, a plurality of components 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 in the same or similar manner as they are performed by a corresponding one of the plurality of components before the integration. Operations performed by the module, the program, or another component may be carried out sequentially, in parallel, repeatedly, or heuristically, or one or more of the operations may be executed in a different order or omitted, or one or more other operations may be added.

Claim 1:
An electronic device (<NUM>) comprising:
a display;
a wireless communication circuit configured to communicate with a server;
a memory configured to store instructions; and
at least one processor electrically connected to the wireless communication circuit and the memory,
wherein the at least one processor executes the stored instructions to:
transmit (<NUM>), to the server, user information for registering (<NUM>) a user account in the server;
obtain (<NUM>) hub identifiable information corresponding to a hub;
transmit (<NUM>) the hub identifiable information to the server, using the wireless communication circuit to add (<NUM>) the hub identifiable information to the user account registered in the server;
obtain (<NUM>) device identifiable information corresponding to a plurality of Internet of Things, IoT, devices;
output a specified message for displaying, on the display, the obtained device identifiable information;
obtain a user input and, based thereon, select a part of the device identifiable information corresponding to at least one IoT device of the plurality of IoT-devices;
transmit (<NUM>) the selected part of the device identifiable information to the server to add (<NUM>) the device identifiable information to the user account registered in the server; and
enable the hub corresponding to the hub identifiable information added to the user account and the at least one IoT device corresponding to the at least part of the device identifiable information to be paired with each other.