Electronic device for device changing and method of operating the same

Abstract

According to one embodiment of the present disclosure, an operation method of an IoT device may include the operations of: receiving a device change request from an IoT server; in response to the received device change request, disconnecting the first device; in response to disconnecting the first device, switching to a pairing mode for establishing a wireless communication link with another device; establishing a wireless communication link with the second device while maintaining the pairing mode; identifying that the second device is a device corresponding to the device change request; and receiving information related to an access point (AP) from the second device, the AP connecting the second device to the IoT server.

Description

Technical Field

[0001] Embodiments of the present disclosure relate to an electronic device for modifying a device and a method of operating the electronic device. Background Art

[0002] With the development of IoT technology, IoT devices equipped with IoT functions (e.g., TVs, refrigerators, vacuum cleaners, washing machines, smartphones, laptops, etc.) are widely used in homes. Technology is being developed to monitor the status of various IoT devices connected inside and outside the home, and remotely control the IoT devices through user devices. To this end, a specific application is installed on the user device, and the IoT device can be remotely controlled through the application installed on the user device (e.g., welcome cooling, pre-activation of a robot vacuum cleaner, timely laundry when returning home, etc.). Therefore, in order to facilitate the control of IoT devices, IoT devices can be registered in the IoT server in association with user devices. Summary of the invention

[0003] Technical Solutions

[0004] A user who purchases an IoT device (e.g., new or second-hand) can control the purchased IoT device through a user terminal (e.g., a smartphone). The user can register the IoT device on an account of a remote control application. However, the user needs to install the corresponding application on the smartphone and needs to create an appropriate short-range wireless communication environment (e.g., Wi-Fi) at home. In addition, since the user should alternately operate the IoT device and the user device at a close distance to register the IoT device on the user account, a method for registering IoT devices that can bring a better user experience is needed.

[0005] Embodiments of the present disclosure provide a device and an operation method for registering an IoT device on a user device while minimizing the number of manipulations by the user.

[0006] Also provided is a device and an operation method for registering an IoT device on a user account by controlling the user device without manipulating both the user device and the IoT device.

[0007] A method for operating an IoT device according to an embodiment of the present disclosure may include: receiving a device change request from an IoT server. The method according to the embodiment may include: disconnecting the connection between the IoT device and the first device based on receiving the device change request. The method according to the embodiment may include: switching the operation of the IoT device to a pairing mode to establish a wireless communication link based on the disconnection of the connection between the IoT device and the first device. The method according to the embodiment may include: establishing a wireless communication link between the IoT device and a second device while the IoT device is in pairing mode. The method according to the embodiment may include: identifying whether the second device is associated with the device change request. The method according to the embodiment may include: receiving information about an access point (AP) from the second device based on the second device being identified as being associated with the device change request, the AP connecting the second device to the IoT server.

[0008] In an embodiment, the device change request may include information about the second device. The information about the second device may include: identification information about the second device and information about an account of a user of the second device.

[0009] The method according to an embodiment may further include: disconnecting the IoT server from the IoT device based on switching the operation of the IoT device to a pairing mode.

[0010] The method according to the embodiment may further include: deleting the information about the first device stored in the IoT device based on switching the operation of the IoT device to the pairing mode.

[0011] The method according to an embodiment may further include: periodically sending an advertising data packet to at least one neighboring device based on switching the operation of the IoT device to a pairing mode.

[0012] The method according to the embodiment may further include: receiving a Bluetooth connection request from the second device. The method according to the embodiment may further include: sending a Bluetooth connection acknowledgement (ACK) to the second device.

[0013] According to an embodiment, identifying whether the second device is associated with the device change request may be based on information about the second device included in the Bluetooth connection request received from the second device and information about the second device included in the device change request.

[0014] An electronic device according to an embodiment may include: a memory; a communication unit; and at least one processor electrically connected to the memory and the communication unit. The at least one processor may receive a device change request from an IoT server. The at least one processor according to the embodiment may disconnect the connection between the IoT device and the first device based on receiving the device change request. The at least one processor according to the embodiment may switch the operation of the IoT device to a pairing mode to establish a wireless communication link based on the disconnection of the connection between the IoT device and the first device. The at least one processor according to the embodiment may establish a wireless communication link between the IoT device and the second device while the IoT device is in pairing mode. The at least one processor according to the embodiment may identify whether the second device is associated with the device change request. The at least one processor according to the embodiment may receive information about an access point (AP) from the second device based on the second device being identified as being associated with the device change request, and the AP connects the second device to the IoT server.

[0015] In an embodiment, the device change request may include information about the second device. In an embodiment, the information about the second device may include: identification information about the second device and information about an account of a user of the second device.

[0016] According to the embodiment, at least one processor may disconnect the IoT server from the IoT device based on the operation of the IoT device switching to the pairing mode.

[0017] According to the embodiment, at least one processor may delete the information about the first device stored in the electronic device based on the operation of the IoT device switching to the pairing mode.

[0018] At least one processor according to an embodiment may periodically send an advertising data packet to at least one neighboring device based on the operation of the IoT device switching to a pairing mode.

[0019] The at least one processor according to an embodiment may receive a Bluetooth connection request from the second device.The at least one processor according to an embodiment may send a Bluetooth connection acknowledgement (ACK) to the second device.

[0020] At least one processor according to an embodiment may determine that the second device is associated with the device change request based on information about the second device included in the Bluetooth connection request received from the second device and information about the second device included in the device change request.

[0021] A method of operating an electronic device according to an embodiment may include: receiving a device change request from an IoT server. The method according to an embodiment may include: based on receiving the device change request, displaying a notification about the device change request. The method according to an embodiment may include: displaying a user interface including an object, the object being used to receive user input about the device change. The method according to an embodiment may include: based on receiving the user input through the object, monitoring a signal sent from an IoT device positioned adjacent to the electronic device. The method according to an embodiment may include: sending a wireless communication link formation request to the IoT device. The method according to an embodiment may include: identifying whether the IoT device is associated with the device change request. The method according to an embodiment may include: sending information about an access point (AP) that is connected to the electronic device.

[0022] Embodiments of the present disclosure may enhance user experience by simplifying the registration procedure of IoT devices.

[0023] Embodiments of the present disclosure may encourage the installation of applications to control IoT devices, thereby increasing the popularity of applications on user devices.

[0024] The effects of the present disclosure are not limited to the above, and other unmentioned effects will be apparent to those of ordinary skill in the art from the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] Figure 1a shows an example IoT environment according to an embodiment;

[0026] Figure 1b An example of user modification of an IoT device according to an embodiment is shown;

[0027] Figure 2 is a block diagram showing a configuration of an IoT device according to an embodiment;

[0028] Figure 3 is a block diagram showing a configuration of a user equipment according to an embodiment;

[0029] Figure 4 is a signaling flow chart for registering an IoT device according to an embodiment;

[0030] Figure 5 is a flowchart illustrating the operation of an IoT device according to an embodiment;

[0031] Figure 6 shows an example user interface for registering an IoT device according to an embodiment; and

[0032] Figure 7 An example user interface for registering an IoT device according to an embodiment is shown.

[0033] Throughout the specification and drawings, the same or similar reference numerals may be used to refer to the same or similar elements. DETAILED DESCRIPTION

[0034] It should be understood that the various embodiments of the present disclosure and the terms used therein are not intended to limit the technical features set forth herein to specific embodiments, and include various changes, equivalents, or replacements of the corresponding embodiments.

[0035] Regarding the description of the drawings, like reference numerals may be used to refer to like or related elements.

[0036] It should be understood that singular forms of nouns corresponding to items may include one or more items unless the relevant context clearly indicates otherwise.

[0037] As used herein, each phrase such as "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" may include all possible combinations of items listed together in the corresponding one phrase.

[0038] As used herein, terms such as “1st” and “2nd” or “first” and “second” may be used to simply distinguish corresponding components from other components, and do not limit the components in other aspects (eg, importance or order).

[0039] It should be understood that if an element (e.g., a first element) is referred to as being “coupled”, “coupled to”, “connected to” or “connected to” another element (e.g., a second element) with or without the terms “operably” or “communicatively”, it means that the element can be coupled to the other element directly (e.g., wired), wirelessly or via a third element.

[0040] It will also be understood that the terms “including” and / or “having” when used herein indicate the presence of the stated features, integers, steps, operations, elements and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components and / or combinations thereof.

[0041] It should be understood that when one component is referred to as being “connected to,” “coupled to,” “supported on,” or “in contact with” another component, the components may be connected, coupled, supported on, or in contact with each other directly or via a third component.

[0042] Throughout the specification, when a component is located 'on' another component, the first component may be directly located on the second component, or other components may be located between the first component and the second component.

[0043] The term "and / or" may mean a combination of a plurality of related components listed or any components.

[0044] Hereinafter, working principles and embodiments of the present disclosure will be described with reference to the accompanying drawings.

[0045] Figure 1a An example IoT environment is shown according to an embodiment.

[0046] The IoT device 10 according to the embodiment may be connected to another IoT device through the network NET, and may also be connected to the user device 2 and the server 3 .

[0047] The IoT device 10 according to the embodiment may include various types of home appliances. For example, the IoT device 10 may include at least one of a refrigerator 11, a dishwasher 12, an electric stove 13, an electric oven 14, an air conditioner 15, a clothing care device 16, a washing machine 17, a dryer 18, a microwave oven 19, a sweeping robot, a vacuum cleaner, and the like. The above-mentioned home appliances are only examples, and although not the above-mentioned home appliances, any device that can be connected to another home appliance, a user device, or a server through a network and can perform the following operations may be included in the IoT device 10 according to the embodiment.

[0048] The server 3 according to the embodiment may include a communication module capable of communicating with the IoT device 10 and the user device 2, at least one processor capable of processing data received from the IoT device 10 or the user device 2, and at least one memory capable of storing a program for processing data or processed data. The server 3 may be implemented as various computing devices, such as a workstation, a cloud, a data drive, and a data station.

[0049] According to an embodiment, the user device 2 may include a communication module capable of communicating with the IoT device 10 and the server 3, a user interface for receiving user input or outputting information to the user, at least one processor for controlling the operation of the user device 2, and at least one memory for storing a program for controlling the operation of the user device 2.

[0050] The user device 2 according to an embodiment of the present disclosure may be carried by a user, may be placed in the user's home or office, and may include a personal computer, a terminal, a mobile phone, a smart phone, a handheld device, a wearable device, etc.

[0051] The memory of the user device 2 according to the embodiment may store a program (i.e., an application) for controlling the IoT device 10. Such an application may or may not be installed on the user device 2 for sale. If the application is not installed on the user device 2, the user may download and install the application from an external server that provides the application.

[0052] In an embodiment, a user can control the IoT device 10 using an application installed on the user device 2. For example, a user can create an account managed by the server 3, and the user's account can be identified by an ID and a password set by the user. The IoT device 10 can be registered on the user's account according to a predetermined process. For example, when registering the home appliance 10, identification information such as a serial number or a MAC address assigned to each home appliance 10 can be used. When executing the application installed on the user device 2 and logging into the user account, the user can use the user device 2 to perform the desired control on the IoT device 10.

[0053] In an embodiment, the network NET may include both a wired network and a wireless network. The wired network may include a cable TV network, a telephone network, etc., and the wireless network may include all networks that send and receive signals via radio waves. The wired network and the wireless network may be connected to each other.

[0054] In an embodiment, the network NET may include a wide area network (WAN) such as the Internet and a local area network (LAN) formed around an access point (AP).

[0055] In an embodiment, the AP may connect a local area network (LAN) to which the IoT device 10 and the user device 2 are connected to a wide area network (WAN) to which the server 3 is connected. The IoT device 10 or the user device 2 may be connected to the server 3 through the wide area network (WAN).

[0056] In an embodiment, the AP may use wireless communication (such as Wi-Fi (Wi-Fi TM , IEEE 802.11), Bluetooth TM , IEEE 802.15.1), Zigbee (IEEE 802.15.4), etc. communicate with the IoT device 10 and the user device 2, and can access the wide area network (WAN) using wired communication.

[0057] In an embodiment, the IoT device 10 may send information about its operation or status to the server 3 via the network NET. The information may be sent when a request is received from the server 3, when a specific event occurs on the IoT device 10, or periodically or in real time. When receiving information about the operation or status from the IoT device 10, the server 3 may update the stored information and send updated information about the operation and status of the IoT device 10 to the user device 2 via the network NET.

[0058] In an embodiment, the IoT device 10 can obtain various information from the server 3 and provide the obtained information to the user. For example, the IoT device 10 can obtain information such as weather, news, recipes, washing methods, etc. from the server 3 and output the obtained information through the user interface.

[0059] In an embodiment, the IoT device 10 may operate according to a control command received from the server 3. To this end, the IoT device 10 may obtain the user's prior approval to operate according to the control command of the server 3 without user input. In addition, the IoT device 10 may provide the server 3 with information about the operation or status of the IoT device 10 according to the user's prior approval.

[0060] In an embodiment, the user device 2 may provide information about the user (eg, the user's location or health condition) to the server 3 according to the user's prior approval.

[0061] In an embodiment, the server 3 may use a technology such as artificial intelligence to process information about the operation or status of the IoT device 10 and information about the user of the user device 2, and may send a control command to the IoT device 10 based on the processing result.

[0062] Figure 1b An example of changing a user of an IoT device according to an embodiment is shown.

[0063] The IoT environment 100 according to the embodiment may include a server device 3, an IoT device 10, a first device 2-1, and a second device 2-2. Figure 1a , Figure 1b In the following description, it is assumed that the IoT device 10 is a TV or a display, but this is only an example, and the IoT device 10 may include Figure 1a Any IoT device 10 or device with IoT function.

[0064] In the embodiment, an example is described in which the IoT device 10 is moved from the first home 101 to the second home 102 through, for example, a second-hand transaction. However, this is merely an example, and the embodiment according to the present disclosure can be equally applied not only to second-hand transactions but also to the purchase of new products.

[0065] The server device 3 according to the embodiment may represent an IoT network server for managing IoT devices. The server device 3 may perform data communication with an IoT device (e.g., IoT device 10) and a user device (e.g., first device 2-1 or second device 2-2). The server device 3 may perform bidirectional communication with the IoT device and the user device in a wired and wireless manner.

[0066] The server device 3 according to the embodiment can communicate with the IoT device. Although not shown, an access point (AP) for communication between the server device 3 and the IoT device can be installed in the first home 101 and the second home 102. The IoT device can communicate with the server device 3 through the AP installed in each home.

[0067] The server device 3 according to an embodiment of the present disclosure can manage data about IoT devices present in each home. For example, the server device 3 can receive overall data about IoT devices from IoT devices (e.g., the number of IoT devices owned by each home (e.g., a total of three IoT devices, including a TV, a refrigerator, and a monitor)), types of IoT devices (e.g., three TVs, two refrigerators, two monitors, a sound bar, and a washing machine), device information about IoT devices (e.g., manufacturer, manufacturing date, software information, and identification information), connection information about IoT devices (e.g., information about external devices such as a sound bar connected to a TV), and account information about IoT devices (e.g., logged-in account information), or send specific data to IoT devices.

[0068] The first device 2 - 1 according to the embodiment may represent a user device (eg, a smartphone) for controlling IoT devices included in the first home 101 . The second device 2 - 2 according to the embodiment may represent a user device for controlling IoT devices included in the second home 102 .

[0069] In an embodiment, when the IoT device 10 is connected to the first home 101, the IoT device 10 may be controlled by the first device 2-1, and when the IoT device 10 is connected to the second home 102, the IoT device 10 may be controlled by the second device 2-2.

[0070] In an embodiment, the IoT device 10 can be controlled by registering an electronic device (e.g., the first device 2-1 or the second device 2-2) in the IoT server 3. For example, the first device 2-1 can register the IoT device 10 in the IoT server 3 through an application installed on the first device 2-1. The second device 2-2 can register the IoT device 10 in the IoT server 3 through an application installed on the second device 2-2.

[0071] In an embodiment, the IoT device 10 may be connected to an account of a specific user. For example, when the IoT device 10 is connected to the first family 101, the IoT device 10 may be connected to the account of the user of the first device 2-1. For example, when the IoT device 10 is sold from the first family 101 to the second family 102 and connected to the second family 102, the IoT device 10 may be disconnected from the account of the user of the first device 2-1 and connected to the account of the user of the second device 2-2.

[0072] Figure 2 is a block diagram showing a configuration of an IoT device according to an embodiment. Figure 2 Electronic equipment may include Figure 1a and Figure 1b An electronic device corresponding to the IoT device 10.

[0073] According to an embodiment, the IoT device 200 may include a processor 210, a memory 220, a display 240, and a communication unit 250. The IoT device 200 may further include an image input unit (not shown). The IoT device 200 may include additional components in addition to the components shown, or may omit at least one of the components shown.

[0074] According to an embodiment, the memory 220 is a storage medium used by the IoT device 200 and may store data such as at least one instruction 221 or setting information corresponding to at least one program. The program may include an operating system (OS) program and various applications.

[0075] The storage unit 220 may include at least one type of storage medium among a flash memory type, a hard disk type, a multimedia card micro type, a card type memory (e.g., an SD or XD memory card), 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.

[0076] According to an embodiment, the image input unit (not shown) may receive images and image information through a tuner (not shown), an input / output unit (not shown), or a communication unit 250. The image input unit may include at least one of a tuner and an input / output unit. The tuner may tune and select only the frequency of a broadcast channel to be received by the IoT device 200 from among a number of radio components by amplifying, mixing, and resonating a broadcast signal received by wire / wirelessly. The broadcast signal may include video, audio, and additional data (e.g., an electronic program guide (EPG)). The tuner may receive a real-time broadcast channel (or a real-time viewing image) from various broadcast sources (e.g., terrestrial broadcasting, cable broadcasting, satellite broadcasting, Internet broadcasting, etc.). The tuner may be implemented in an integrated manner with the IoT device 200, or may be implemented as a separate tuner electrically connected to the IoT device 200. The input / output unit may include at least one of a high-definition multimedia interface (HDMI) input port, a component input jack, a PC input port, and a USB input jack, and may be capable of receiving images and image information from an external device of the IoT device 200 under the control of the processor 210. It is obvious to those skilled in the art that the input / output units may be added, deleted, and / or changed according to the performance and structure of the IoT device 200 .

[0077] According to an embodiment, the display 240 may perform a function of outputting information in the form of numbers, characters, images and / or graphics. The display 240 may include at least one hardware module for output. The at least one hardware module may include, for example, at least one of a liquid crystal display (LCD), a light emitting diode (LED), a light emitting polymer display (LPD), an organic light emitting diode (OLED), an active matrix organic light emitting diode (AMOLED), or a flexible LED (FLED). The display 240 may display a screen corresponding to the data received from the processor 210. The display 240 may be referred to as an "output unit", "display unit" or other terms having equivalent technical meanings.

[0078] According to an embodiment, the communication unit 250 may provide a wired / wireless communication interface to enable communication with an external device. The communication unit 250 may include at least one of a wired Ethernet, a wireless LAN communication unit, and a short-range communication unit. The wireless LAN communication unit may include, for example, Wi-Fi, and may support the wireless LAN standard (IEEE802.11x) of the Institute of Electrical and Electronics Engineers (IEEE). The wireless LAN communication unit may be wirelessly connected to an access point (AP) under the control of the processor 210. The short-range communication unit may wirelessly perform short-range communication with an external device under the control of the processor 210. Short-range communication may include Bluetooth, low-power Bluetooth, infrared data association (IrDA), ultra-wideband (UWB), and near field communication (NFC). The external device may include a server device and a mobile terminal (e.g., a phone, a tablet, etc.) that provide, for example, an image.

[0079] According to an embodiment, the processor 210 may control at least one other component of the IoT device 200 and / or perform communication-related calculations or data processing by executing at least one command 221 stored in the memory 220. The processor 210 may include at least one of a central processing unit (CPU), a graphics processing unit (GPU), a microcontroller unit (MCU), a sensor hub, an auxiliary processor, a communication processor, an application processor, an application specific integrated circuit (ASIC), or a field programmable gate array (FPGA), and may have multiple cores.

[0080] Figure 3 is a block diagram illustrating an electronic device 301 in a network environment 300 according to various embodiments.

[0081] Reference Figure 3, the electronic device 301 in the network environment 300 may communicate with the electronic device 302 via the first network 398 (e.g., a short-range wireless communication network), or communicate with at least one of the electronic device 304 or the server 308 via the second network 399 (e.g., a long-range wireless communication network). According to an embodiment, the electronic device 301 may communicate with the electronic device 304 via the server 308. According to an embodiment, the electronic device 301 may include a processor 320, a memory 330, an input module 350, a sound output module 355, a display module 360, an audio module 370, a sensor module 376, an interface 377, a connection terminal 378, a haptic module 379, a camera module 380, a power management module 388, a battery 389, a communication module 390, a subscriber identity module (SIM) 396, or an antenna module 397. In some embodiments, at least one component (e.g., the connection terminal 378) may be omitted from the electronic device 301, or one or more other components may be added in the electronic device 301. In some embodiments, some components (eg, sensor module 376, camera module 380, or antenna module 397) may be implemented as a single component (eg, display module 360).

[0082] For example, the processor 320 may execute software (e.g., program 340) to control at least one other component (e.g., hardware or software component) of the electronic device 301 coupled to the processor 320, and may perform various data processing or calculations. According to an embodiment, as at least part of the data processing or calculation, the processor 320 may store a command or data received from another component (e.g., sensor module 376 or communication module 390) in the volatile memory 332, process the command or data stored in the volatile memory 332, and store the result data in the non-volatile memory 334. According to an embodiment, the processor 320 may include a main processor 321 (e.g., a central processing unit (CPU) or an application processor (AP)), or an auxiliary processor 323 (e.g., a graphics processing unit (GPU), a neural processing unit (NPU), an image signal processor (ISP), a sensor hub processor, or a communication processor (CP)) that is operable independently of the main processor 321 or jointly operable with the main processor 1621. For example, when the electronic device 301 includes a main processor 321 and an auxiliary processor 323, the auxiliary processor 323 may be adapted to consume less power than the main processor 321 or be dedicated to a specific function. The auxiliary processor 323 may be implemented in a separate form or as part of the main processor 321.

[0083] The auxiliary processor 323 may replace the main processor 321 when the main processor 321 is in an inactive (e.g., sleep) state, or control at least some of the functions or states related to at least one component (e.g., display module 360, sensor module 376, or communication module 390) among the components of the electronic device 301 together with the main processor 321 when the main processor 321 is in an active state (e.g., executing an application). According to an embodiment, the auxiliary processor 323 (e.g., an image signal processor or a communication processor) may be implemented as a part of another component (e.g., a camera module 380 or a communication module 390) that is functionally related to the auxiliary processor 323. According to an embodiment, the auxiliary processor 323 (e.g., a neural processing unit) may include a hardware structure designated for artificial intelligence model processing. The artificial intelligence model may be generated by machine learning. Such learning may be performed by the electronic device 301 that performs artificial intelligence, or may be performed via a separate server (e.g., server 308). The learning algorithm may include, but is not limited to, supervised learning, unsupervised learning, semi-supervised learning, or reinforcement learning. The artificial intelligence model may include multiple artificial neural network layers. The artificial neural network may be 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 thereof, but is not limited thereto. The artificial intelligence model may additionally or alternatively include a software structure in addition to a hardware structure.

[0084] The memory 330 may store various data used by at least one component (e.g., the processor 320 or the sensor module 376) of the electronic device 301. For example, the various data may include input data or output data of software (e.g., the program 340) and commands related thereto. The memory 330 may include a volatile memory 332 or a non-volatile memory 334.

[0085] The program 340 may be stored as software in the memory 330 , and may include, for example, an operating system (OS) 342 , middleware 344 , or an application 346 .

[0086] The input module 350 may receive a command or data to be used by another component (e.g., the processor 320) of the electronic device 301 from outside (e.g., a user) of the electronic device 301. The input module 350 may include, for example, a microphone, a mouse, a keyboard, a key (e.g., a button), or a digital pen (e.g., a stylus).

[0087] The sound output module 355 can output sound signals to the outside of the electronic device 301. The sound output module 355 can include, for example, a speaker or a receiver. The speaker can be used for general purposes, such as playing multimedia or playing recordings. The receiver can be used to answer calls. According to an embodiment, the earpiece can be implemented in a separate form, or as part of a speaker.

[0088] The display module 360 ​​can visually provide information to the outside of the electronic device 301 (e.g., a user). For example, the display module 360 ​​may include a display, a holographic device or a projector, and a control circuit for controlling a corresponding one of the display, the holographic device, and the projector. According to an embodiment, the display module 360 ​​may include a touch sensor suitable for detecting a touch, or a pressure sensor suitable for measuring the strength of a force generated by a touch.

[0089] The audio module 370 can convert sound into an electrical signal, and vice versa. According to an embodiment, the audio module 370 can obtain sound via the input module 350, or output sound via the sound output module 355 or an earphone of an external electronic device (e.g., electronic device 302) directly (e.g., wired) or wirelessly coupled to the electronic device 301.

[0090] The sensor module 376 may detect an operating state (e.g., power or temperature) of the electronic device 301 or an environmental state (e.g., a user's state) outside the electronic device 301, and then generate an electrical signal or data value corresponding to the detected state. According to an embodiment, the sensor module 376 may include, for example, 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 illumination sensor.

[0091] The interface 377 may support one or more designated protocols to be used for the electronic device 301 to be directly (e.g., wired) or wirelessly coupled to an external electronic device (e.g., the electronic device 302). According to an embodiment, the interface 377 may include, for example, a high-definition multimedia interface (HDMI), a universal serial bus (USB) interface, a secure digital (SD) card interface, or an audio interface.

[0092] The connection terminal 378 may include a connector via which the electronic device 301 may be physically connected to an external electronic device (e.g., the electronic device 302). According to an embodiment, the connection terminal 378 may include, for example, an HDMI connector, a USB connector, an SD card connector, or an audio connector (e.g., a headphone connector).

[0093] The haptic module 379 may convert the electrical signal into mechanical stimulation (eg, vibration or movement) or electrical stimulation that can be recognized by the user via his sense of touch or kinesthetic sense. According to an embodiment, the haptic module 379 may include, for example, a motor, a piezoelectric element, or an electrical stimulator.

[0094] The camera module 380 may capture a still image or a moving image. According to an embodiment, the camera module 380 may include one or more lenses, an image sensor, an image signal processor, or a flash.

[0095] The power management module 388 may manage power supplied to the electronic device 301. According to an embodiment, the power management module 388 may be implemented as, for example, at least a part of a power management integrated circuit (PMIC).

[0096] The battery 389 may supply power to at least one component of the electronic device 301. According to an embodiment, the battery 389 may include, for example, a non-rechargeable primary battery, a rechargeable secondary battery, or a fuel cell.

[0097] The communication module 390 may support establishing a direct (e.g., wired) communication channel or a wireless communication channel between the electronic device 301 and an external electronic device (e.g., electronic device 302, electronic device 304, or server 308), and perform communication via the established communication channel. The communication module 390 may include one or more communication processors that may operate independently of the processor 320 (e.g., an application processor (AP)) and support direct (e.g., wired) communication or wireless communication. According to an embodiment, the communication module 390 may include a wireless communication module 392 (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 394 (e.g., a local area network (LAN) communication module or a power line communication (PLC) module). A corresponding one of these communication modules can communicate with an external electronic device via a first network 398 (e.g., a short-range communication network such as Bluetooth™, Wireless Fidelity (Wi-Fi) Direct, or Infrared Data Association (IrDA)) or a second network 399 (e.g., a long-range communication network such as a traditional cellular network, a 5G network, a next-generation communication network, the Internet, or a computer network (e.g., a LAN or a wide area network (WAN)). These various types of communication modules can be implemented as a single component (e.g., a single chip), or can be implemented as multiple components separated from each other (e.g., multiple chips). The wireless communication module 392 can identify and authenticate the electronic device 301 in a communication network (e.g., the first network 398 or the second network 399) using user information (e.g., an International Mobile Subscriber Identity (IMSI)) stored in the user identification module 396.

[0098] The wireless communication module 392 can support 5G networks and next-generation communication technologies following the 4G network, such as new radio (NR) access technology. NR access technology can support enhanced mobile broadband (eMBB), massive machine type communication (mMTC), or ultra-reliable low latency communication (URLLC). The wireless communication module 392 can support high frequency bands (e.g., millimeter wave bands) to achieve, for example, high data transmission rates. The wireless communication module 392 can support various technologies for ensuring performance on high frequency bands, such as beamforming, massive multiple input multiple output (massive MIMO), full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, or large-scale antennas. The wireless communication module 392 can support various requirements specified in the electronic device 301, an external electronic device (e.g., an electronic device 304), or a network system (e.g., a second network 399). According to an embodiment, the wireless communication module 392 can support a peak data rate for implementing eMBB (e.g., 20 Gbps or higher), a loss coverage ratio for implementing mMTC (e.g., 164 dB or lower), or a U-plane delay for implementing URLLC (e.g., 0.5 ms or lower for each downlink (DL) and uplink (UL), or 1 ms or lower for a round trip).

[0099] The antenna module 397 may transmit a signal or power to the outside of the electronic device 301 (e.g., an external electronic device) or receive a signal or power from the outside of the electronic device 1601. According to an embodiment, the antenna module 397 may include an antenna including a radiation element composed of a conductive material or a conductive pattern, the radiation element being formed in or on a substrate (e.g., a printed circuit board (PCB)). According to an embodiment, the antenna module 397 may include a plurality of antennas (e.g., an array antenna). In this case, for example, the communication module 390 (e.g., the wireless communication module 392) may select at least one antenna suitable for a communication scheme used in a communication network (e.g., the first network 398 or the second network 399) from the plurality of antennas. Then, a signal or power may be transmitted or received between the communication module 390 and the external electronic device via the selected at least one antenna. According to an embodiment, another component (e.g., a radio frequency integrated circuit (RFIC)) other than the radiation element may be additionally formed as a part of the antenna module 397. According to various embodiments, the antenna module 397 may form a millimeter wave antenna module. According to an embodiment, the millimeter wave antenna module may include a printed circuit board, an RFIC disposed on a first surface (e.g., a bottom surface) or adjacent to the first surface of the printed circuit board and capable of supporting a specified high frequency band (e.g., a millimeter wave frequency band), and a plurality of antennas (e.g., array antennas) disposed on a second surface (e.g., a top surface or a side surface) of the printed circuit board or adjacent to the second surface and capable of sending or receiving signals in the specified high frequency band.

[0100] At least some of the above components may be coupled to each other and transmit signals (e.g., commands or data) therebetween via an inter-peripheral communication scheme (e.g., a bus, a general purpose input and output (GPIO), a serial peripheral interface (SPI), or a mobile industry processor interface (MIPI)).

[0101] According to an embodiment, a command or data may be sent or received between the electronic device 301 and the external electronic device 304 via a server 308 coupled to the second network 399. Each of the electronic devices 302 or 304 may be a device of the same type or a different type as the electronic device 301. According to an embodiment, all operations or some operations to be performed at the electronic device 301 may be performed at one or more of the external electronic devices 302, 304, or 308. For example, if the electronic device 301 should automatically or in response to a request from a user or another device to perform a function or service, instead of performing the function or service, or in addition to performing the function or service, the electronic device 301 may request one or more external electronic devices to perform at least a portion of the function or service. The one or more external electronic devices that receive the request may perform at least a portion of the requested function or service or an additional function or additional service related to the request, and transmit the result of the execution to the electronic device 301. The electronic device 301 may provide the result as at least a part of the reply to the request with or without further processing the result. To this end, for example, cloud computing, distributed computing, mobile edge computing (MEC), or client-server computing technology may be used. The electronic device 301 may provide ultra-low latency services using, for example, distributed computing or mobile edge computing. In another embodiment, the external electronic device 304 may include an Internet of Things (IoT) device. The server 308 may be an intelligent server using machine learning and / or neural networks. Depending on the embodiment, the external electronic device 304 or the server 308 may be included in the second network 399. The electronic device 301 may be applied to intelligent services (e.g., smart homes, smart cities, smart cars, or healthcare) based on 5G communication technology or IoT-related technologies.

[0102] Figure 4 is a signaling flow chart for registering an IoT device according to an embodiment. Figure 4 IoT devices can be represented with Figure 1a and Figure 1b IoT devices 10 and Figure 2 Device corresponding to the IoT device 200. Figure 4 The first device 401 and the second device 407 may represent Figure 1a and Figure 1b User device 2 and Figure 3The first device 401 may correspond to the first device 2-1 and may refer to a terminal of a first user who previously owned an IoT device. The second device 407 may correspond to the second device 2-2 and may refer to a terminal of a second user who newly purchased an IoT device. Figure 4 The IoT server 405 may represent Figure 1a and Figure 1b The device corresponding to server 3.

[0103] According to an embodiment, in operation 410 , the first device 401 may receive a user input for requesting a change of a device through a user interface (UI).

[0104] In an embodiment, the UI displayed on the first device 401 may represent a screen of an application for managing IoT devices connected to the user device.

[0105] In an embodiment, the UI displayed on the first device 401 may include an object (eg, an icon, a button, or a pop-up window) for requesting to change the user of the IoT device 403 .

[0106] In an embodiment, the UI displayed on the first device 401 may include an object for inputting information about the device (i.e., the second device 407) of the new owner of the IoT device 403. For example, the UI displayed on the first device 401 may include a window for receiving account information (e.g., email address, ID, etc.) about the second device 407, or an object for receiving a phone number.

[0107] In an embodiment, the UI displayed on the first device 401 may include an object for selecting the IoT device 403 to be changed.

[0108] In an embodiment, when a user input (eg, touch, long press, double click, etc.) is received through an object of a UI displayed on the first device 401 , the first device 401 may initiate a process of changing a device.

[0109] According to an embodiment, in operation 412 , the first device 401 may send a device change request to the IoT server 405 in response to receiving a user input for requesting a device change through the UI.

[0110] In an embodiment, the device change request may include information about the second device 407 (eg, account information, email information, phone number, etc.) input through the UI of the first device 401 .

[0111] In an embodiment, the device change request may include information about the IoT device 405 .

[0112] According to an embodiment, in operation 414 , the IoT server 405 may send a disconnection request to the IoT device 403 .

[0113] In an embodiment, the IoT server 405 may send a disconnect request to the IoT device 403 in response to receiving a device change request from the first device 401 .

[0114] In an embodiment, the IoT server 405 may identify the IoT device to which the disconnection request is to be sent based on the information about the IoT device 403 included in the device change request received from the first device 401 .

[0115] In an embodiment, the disconnection request may include information about the second device 407. For example, the disconnection request may include information about an account of a user of the second device 407, information about a phone number, and the like.

[0116] According to an embodiment, in operation 416 , the IoT server 405 may send a device change request including information about the IoT device 403 to the second device 407 in response to receiving the device change request.

[0117] In an embodiment, the information about the IoT device 405 may include information about a serial number (S / N), identification information, a model, a media access control (MAC) address, etc. of the IoT device 405 .

[0118] In an embodiment, when the IoT device 403 does not have a memory, the IoT server 405 may delete the information received from the first device 401 .

[0119] According to an embodiment, in operation 418 , in response to receiving the disconnection request, the IoT device 403 may be disconnected from the first device 401 , and a mode of the device may be switched to a pairing mode.

[0120] In an embodiment, the IoT device 403 may be disconnected from the IoT server 405. For example, when there is a currently connected AP, the IoT device 403 may be disconnected from the AP.

[0121] In an embodiment, when there is a wireless communication link established with the first device 401, the IoT device 403 may release the wireless communication link.

[0122] In an embodiment, when the first user is registered as a connected user, the IoT device 403 may release the registration.

[0123] In an embodiment, the IoT device 403 may delete the information about the first user stored in the IoT device 403 .

[0124] In an embodiment, the IoT device 403 may switch to a pairing mode to establish a wireless communication link with another device present nearby. For example, the IoT device 403 may switch to a pairing mode to periodically send a Bluetooth Low Energy (BLE) advertising data packet to a neighboring device. For example, the IoT device 403 may monitor whether a request to establish a wireless communication link is received from a neighboring device. For example, the IoT device 403 may activate a SoftAP.

[0125] In an embodiment, when the disconnection request sent in operation 414 includes information about the second device 407, the IoT device 403 may store the received information about the second device 407 in the memory. For example, the received information about the user account of the second device 407 may be overwritten in the memory.

[0126] According to an embodiment, in operation 420, the second device 407 may display a notification related to the device change. The second device 407 may display a notification about the device change in response to receiving the information about the IoT device.

[0127] In an embodiment, the second device 407 may display a UI indicating that a device change request has been received. For example, the second device 407 may display a screen (e.g., a pop-up window, a text message, or a virtual card in an application) indicating that a device change request has been received. For example, when an application for an IoT service is not installed on the second device 407, a pop-up window including a URL for installing the application may be displayed.

[0128] According to an embodiment, in operation 422, the second device 407 may switch to a pairing mode.

[0129] In an embodiment, the second device 407 may monitor whether there is an advertisement data packet received from a neighboring device.

[0130] In an embodiment, when there is a received advertising data packet, the second device 407 may determine whether the second device 407 is a device corresponding to an IoT device included in the information about IoT devices received from the IoT server 405 based on the device information included in the data packet.

[0131] According to an embodiment, in operation 424 , the second device 407 may send a wireless communication link establishment request to the IoT device 403 .

[0132] In an embodiment, when the second device 407 determines that the second device 407 is a device corresponding to the IoT device included in the information about the IoT device received from the IoT server 405 based on the device information included in the advertising data packet received in pairing mode, the second device 407 can send a wireless communication link establishment request to the IoT device.

[0133] According to an embodiment, in operation 426 , the IoT device 403 may establish a wireless communication link with the second device 407 .

[0134] According to an embodiment, in operation 428 , at least one of the IoT device 403 , the IoT server 405 , or the second device 407 may identify whether the IoT device 403 matches the second user who is a user of the second device 407 .

[0135] In an embodiment, the IoT device 403 may determine whether the device establishing the wireless communication link is a device corresponding to the device change request based on the information about the second device included in the disconnection request. For example, when the information about the second device included in the disconnection request is information about the second device 407, the second device 407 may be determined as a device corresponding to the device change request. For example, when it is determined that the second device is not a device corresponding to the device change request, a user authentication request may be sent to the second device.

[0136] In an embodiment, the second device 407 may determine whether the IoT device corresponds to a device that is a device change target based on the information about the IoT device received in operation 416. For example, when the device included in the received information about the IoT device matches the IoT device discovered in pairing mode and that sent a wireless communication link establishment request, the second device 407 may determine that the IoT device is a device corresponding to the device change request. For example, when it is determined that the IoT device is not a device corresponding to the device change request, the second device 407 may send a device authentication request to the IoT device requesting to establish a wireless communication link.

[0137] In an embodiment, although not shown in the figure, before a wireless communication link is established between the second device 407 and the IoT device 403, the IoT server 405 may receive a signal from the second device 407 for requesting identification of whether the IoT device 403 is in a state of being temporarily connected to the IoT server 405. If the IoT device 403 is in a state of being temporarily connected to the IoT server 405, the IoT server 405 may determine that the second device 407 matches the IoT device 403. If the IoT device 403 is not in a state of being temporarily connected to the IoT server 405, the IoT server 405 may determine that the second device 407 does not match the IoT device 403. When it is determined that the IoT device 403 does not match the second device 407, the second device 407 may notify the second device 407 that the IoT device 403 does not match, and in response thereto, the second device 407 may request the IoT device 403 to perform a user identity authentication process.

[0138] According to an embodiment, in operation 428 , the second device 407 may transmit information about an access point (AP) (eg, a Wi-Fi address, etc.) to the IoT device 403 , and the second device 407 uses the AP to communicate with the IoT server 405 .

[0139] Figure 5 is a flowchart showing the operation of an IoT device according to an embodiment. Figure 5 IoT devices can be connected with Figure 1a and Figure 1b IoT devices 10. Figure 2 200 IoT devices and Figure 4 The device corresponding to the IoT device 403. Figure 5 The first device may be Figure 1b User device 2-1 and Figure 4 A device corresponding to the first device 401. Figure 5 The second device can be Figure 1b User equipment 2-2 and Figure 4 A device corresponding to the second device 407. Figure 5 The IoT server can be connected with Figure 1a and Figure 1b Server 3 and Figure 4 The device corresponding to the IoT server 405. Figure 4 The same or overlapping content can be combined in Figure 5 Omitted from the description.

[0140] According to an embodiment, in operation 510, the IoT device may receive a device change request from the IoT server. The operation of the IoT device receiving the device change request from the IoT server may be the same as Figure 4The operation corresponds to operation 412.

[0141] In an embodiment, the device change request may include information about the second device (eg, account information, email information, phone number, etc.) input through the UI of the first device.

[0142] In an embodiment, the device change request may include information about the IoT device, such as the serial number S / N, MAC address, etc. of the IoT device.

[0143] According to an embodiment, in operation 520, the IoT device may disconnect from the first device in response to receiving the device change request. Operation 520 may indicate that Figure 4 The operation corresponds to operation 418.

[0144] In an embodiment, the IoT device can be disconnected from the IoT server. For example, when there is an AP currently connected, the IoT device can be disconnected from the AP.

[0145] In an embodiment, when there is a wireless communication link established with the first device, the IoT device may release the wireless communication link.

[0146] In an embodiment, when the first user is registered as a connected user, the IoT device may release the registration.

[0147] In an embodiment, the IoT device may delete the information about the first user stored in the IoT device.

[0148] According to an embodiment, in operation 530, the IoT device may switch to a pairing mode to form a wireless communication link with another device in response to disconnecting from the first device. Operation 530 may indicate that the IoT device is disconnected from the first device. Figure 4 The operation corresponds to operation 418.

[0149] In an embodiment, the IoT device may switch to pairing mode to establish a wireless communication link with another device present nearby. For example, the IoT device may switch to pairing mode to periodically send a Bluetooth Low Energy (BLE) advertising data packet to a neighboring device. For example, the IoT device may monitor whether a request to establish a wireless communication link is received from a neighboring device. For example, the IoT device 403 may activate a SoftAP.

[0150] According to an embodiment, in operation 540 , the IoT device may form a wireless communication link with the second device while maintaining the pairing mode. Figure 5 Operation 540 may indicate that Figure 4 The operation corresponds to operation 426.

[0151] According to an embodiment, in operation 550, the IoT device may identify that the second device establishing the wireless communication link is the device corresponding to the device change request. Operation 550 may indicate that Figure 4 The operation corresponds to operation 428.

[0152] In an embodiment, the IoT device may identify whether the second device is a device corresponding to the device change request based on the information about the second device received from the IoT server.

[0153] In an embodiment, the IoT device may receive a signal from the second device or the IoT server indicating that the IoT device matches the second device, and may identify that the second device corresponds to the device change request based on the signal.

[0154] According to an embodiment, in operation 560, the IoT device may receive information about an AP from the second device, the AP connecting the second device to the IoT server. Operation 560 may indicate that Figure 4 The operation corresponds to operation 430.

[0155] Figure 6 An example user interface for registering an IoT device according to an embodiment is shown. Figure 6 The user interface can be Figure 4 An example of a user interface displayed in operation 410 of the first device 401.

[0156] According to an embodiment, the user interface 600 may be a user interface displayed when an application using an IoT service is executed on a user device (eg, a smartphone).

[0157] In an embodiment, user interface 600 may include user interface 610 , user interface 620 , user interface 630 , and user interface 640 .

[0158] In an embodiment, the user interface 610 may include a first object (e.g., an icon or FAB) indicating at least one IoT device currently communicating with the electronic device. For example, the user interface 610 may include an object 602 indicating an IoT device currently communicating with the electronic device. When a user input is received through the object 602, the IoT device communicating with the electronic device may be controlled (e.g., configured to be turned on or off or to operate at a predetermined time).

[0159] In an embodiment, when a user input 604 indicating an object of an IoT device to be sold or removed is received from among the first object 602 of the user interface 610, the electronic device may display a user interface 620. For example, when the user of the electronic device intends to sell an air conditioner, the user input 604 may be recognized by the object 602 indicating the air conditioner. The user input may include various types of input (e.g., click, double click, long press).

[0160] In an embodiment, when the electronic device recognizes the user input 604 through the first object 602, the electronic device may display the second object 612 on the user interface 620. The second object 612 may represent an object for receiving user input related to whether to send a device change request to the IoT server.

[0161] In an embodiment, when receiving a user input 614 through the second object 612, the electronic device may display a user interface 630. The user input 614 may refer to a user input for releasing the registration (intercommunication) of an IoT device currently registered (intercommunication) in the electronic device and allowing another device to initiate a process of registering an IoT device.

[0162] In an embodiment, the user interface 630 may include third objects 632 and 634 for inputting information about the user's device (e.g., the second device 407) to receive an IoT device. For example, the third object 632 may represent an object for receiving information about the user's account to receive an IoT device. For example, the third object 634 may represent an object for receiving identification information (e.g., a phone number) of the user's device to receive an IoT device.

[0163] In an embodiment, when the electronic device receives information about the user or the user's device through the third objects 632 and 634 displayed on the user interface 630 , the electronic device may display the user interface 640 .

[0164] In an embodiment, the user interface 640 may display information 642 indicating that the IoT device is registered and released in a portion corresponding to the IoT device selected to release the registration of the first object 602 .

[0165] Figure 7 An example user interface for registering an IoT device according to an embodiment is shown. Figure 7 The user interface can be Figure 4 An example of a user interface displayed in operation 420 of the second device 402. Figure 7 The user interface shown in FIG. 1 may represent a Figure 6 The user interface corresponding to the application shown in FIG. Figure 6 Related description.

[0166] According to an embodiment, the user interface 700 may be a user interface displayed when an application using an IoT service is executed on a user device (eg, a smartphone).

[0167] In an embodiment, user interface 700 may include user interface 710 , user interface 720 , and user interface 730 .

[0168] In an embodiment, when the electronic device receives a device change request from the IoT server (operation 416), the user interface 710 may display a first object 712 indicating that the device change request has been received. For example, the first object 712 may be displayed in the form of a text message, a pop-up window, etc.

[0169] In an embodiment, although not shown in the figure, if the application for the IoT service is not installed on the electronic device, the first object 712 may display a URL address for guiding the installation of the application.

[0170] In an embodiment, when the electronic device recognizes a user input through the first object 712 , the electronic device may display a user interface 720 .

[0171] In an embodiment, the user interface 720 may include a second object 722 indicating an IoT device corresponding to the device change request.

[0172] In an embodiment, when the electronic device receives a user input through the second object 722, the electronic device may perform an operation for registering the IoT device (eg, Figure 4 Operations 420, 422, 424, 428 and 430).

[0173] In an embodiment, when the registration of the IoT device is completed, the electronic device may display a user interface 730 .

[0174] In an embodiment, the user interface 730 may include a third object 734 indicating a registered IoT device and a fourth object 732 for receiving a user input to guide the use of the registered IoT device.

[0175] The electronic device according to various embodiments may be one of various types of electronic devices. For example, the electronic device may include a portable communication device (e.g., a smart phone), a computer device, a portable multimedia device, a portable medical device, a camera, a wearable device, or a home appliance. According to an embodiment of the present disclosure, the electronic device is not limited to the above-mentioned devices.

[0176] When used in conjunction with various embodiments of the present disclosure, the term "module" may include a unit implemented in hardware, software, or firmware, and may be used interchangeably with other terms such as logic, logic block, component, or circuit. A module may be a single integrated component or its smallest unit or a portion thereof that is suitable for performing one or more functions. For example, according to an embodiment, a module may be implemented in the form of an application specific integrated circuit (ASIC).

[0177] The various embodiments described herein may be implemented as software (e.g., program 340) including one or more instructions stored in a storage medium (e.g., internal memory 336 or external memory 338) readable by a machine (e.g., electronic device 301). For example, a processor (e.g., processor 320) of a machine (e.g., electronic device 301) may call at least one of the one or more instructions stored in the storage medium, and execute it with or without one or more other components under the control of the processor. This allows the machine to operate to perform at least one function according to at least one instruction called. 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. Among them, the term "non-transitory" only means that the storage medium is a tangible device and does not include signals (e.g., electromagnetic waves), but the term does not distinguish between the case where data is semi-permanently stored in the storage medium and the case where data is temporarily stored in the storage medium.

[0178] According to an embodiment, the method according to various embodiments of the present disclosure may be included and provided in a computer program product. The computer program product may be traded as a product between a seller and a buyer. The computer program product may be distributed in the form of a machine-readable storage medium (e.g., a compact disc read-only memory (CD-ROM)), or via an application store (e.g., PlayStore). TM ) online distribution (e.g., downloading or uploading), or directly between two user devices (e.g., smartphones). If distributed online, at least a portion of the computer program product may be temporarily generated or at least temporarily stored in a machine-readable storage medium (e.g., a manufacturer's server, an application store's server, or a memory of a relay server).

[0179] According to various embodiments, each of the above-mentioned components (e.g., a module or a program) may include a single entity or multiple entities, and some of the multiple entities may be separately set in different components. According to various embodiments, one or more of the above-mentioned components may be omitted, or one or more other components may be added. Alternatively or additionally, multiple components (e.g., modules or programs) may be integrated into a single component. In this case, according to various embodiments, the integrated component may still perform one or more functions of each of the multiple components in the same or similar manner as performed by a corresponding one of the multiple components before integration. According to various embodiments, the operations performed by a module, a program or another component may be performed sequentially, in parallel, repeatedly or heuristically, or one or more of the operations may be performed in a different order or omitted, or one or more other operations may be added.

Claims

1. A method for operating an IoT device, the method comprising: Receive device change request from IoT server; Disconnecting the connection between the IoT device and the first device based on receiving the device change request; Based on the disconnection of the connection between the IoT device and the first device, switching the operation of the IoT device to a pairing mode to establish a wireless communication link; While the IoT device is in the pairing mode, establishing a wireless communication link between the IoT device and a second device; identifying whether the second device is associated with the device change request; as well as Based on the second device being identified as being associated with the device change request, information about an access point AP is received from the second device, and the AP connects the second device with the IoT server.

2. The method according to claim 1, wherein: The device change request includes information about the second device, and The information about the second device includes: identification information about the second device and information about a user account of the second device.

3. The method according to claim 2, further comprising: The IoT device is switched to the pairing mode based on the operation of the IoT device, and the IoT server is disconnected from the IoT device.

4. The method according to claim 3, further comprising: Based on the operation of the IoT device, the pairing mode is switched to the pairing mode, and the information about the first device stored in the IoT device is deleted.

5. The method according to claim 3, further comprising: Based on the operation of the IoT device switching to the pairing mode, an advertising data packet is periodically sent to at least one neighboring device.

6. The method according to claim 1, further comprising: receiving a Bluetooth connection request from the second device; as well as A Bluetooth connection acknowledgement ACK is sent to the second device.

7. The method according to claim 6, wherein: Identifying whether the second device is associated with the device change request is based on information about the second device included in the Bluetooth connection request received from the second device and information about the second device included in the device change request.

8. An IoT device, comprising: Memory; Communication unit; at least one processor capable of being electrically connected to the memory and the communication unit, wherein the at least one processor is configured to: Receive device change request from IoT server; Disconnecting the connection between the IoT device and the first device based on receiving the device change request; Based on the disconnection of the connection between the IoT device and the first device, switching the operation of the IoT device to a pairing mode to establish a wireless communication link; While the IoT device is in the pairing mode, establishing a wireless communication link between the IoT device and a second device; identifying whether the second device is associated with the device change request; and Based on the second device being identified as being associated with the device change request, information about an access point AP is received from the second device, and the AP connects the second device with the IoT server.

9. The IoT device according to claim 8, wherein: The device change request includes information about the second device, and The information about the second device includes: identification information about the second device and information about a user account of the second device.

10. The IoT device according to claim 9, wherein: The at least one processor is configured to disconnect the IoT server from the IoT device based on the operation of the IoT device switching to the pairing mode.

11. The IoT device according to claim 10, wherein: The at least one processor is configured to: based on the operation of the IoT device switching to the pairing mode, delete the information about the first device stored in the electronic device.

12. The IoT device according to claim 10, wherein: The at least one processor is configured to periodically send an advertising data packet to at least one neighboring device based on the operation of the IoT device switching to the pairing mode.

13. The IoT device according to claim 8, wherein: The at least one processor is configured to: receiving a Bluetooth connection request from the second device; and A Bluetooth connection acknowledgement ACK is sent to the second device.

14. The IoT device according to claim 13, wherein: The at least one processor is configured to identify whether the second device is associated with the device change request based on information about the second device included in the Bluetooth connection request received from the second device and information about the second device included in the device change request.

15. A method of operating an electronic device, the method comprising: Receive device change request from IoT server; Based on receiving the device change request, displaying a notification regarding the device change request; displaying a user interface including an object for receiving user input regarding a device change; Based on receiving the user input through the object, monitoring a signal transmitted from an IoT device positioned adjacent to the electronic device; Sending a wireless communication link formation request to the IoT device; Identifying whether the IoT device is associated with the device change request; as well as Information about an access point AP, to which the electronic device is connected, is transmitted.

Images