Electronic device for transferring ownership of internet-of-things device, and operating method thereof

Abstract

Disclosed is an electronic device comprising a memory for storing instructions, a communication circuit, and at least one processor. The instructions can instruct a second electronic device to: receive an ownership transfer request message requesting the ownership transfer of an IoT device, registered in a server, from a first user to a second user; receive a user input agreeing to the transfer of ownership of the IoT device; on the basis of the user input, transmit, to the server, a request message for requesting the transfer of ownership of the IoT device; after transmitting the request message, receive, from the server, ownership transfer information required to process the transfer of ownership of the IoT device; establish a D2D connection with the IoT device on the basis of the ownership transfer information; and transmit, to the IoT device through the D2D connection, network connection information to be used for the IoT device to connect to the server.

Description

Electronic device for transferring ownership of Internet of Things devices and method of operation thereof

[0001] The present disclosure relates to an electronic device for transferring ownership of an Internet of Things (IoT) device and a method of operating the same.

[0002] The variety of services and additional features offered through user terminals, such as smartphones, is steadily increasing. To enhance the utility of these electronic devices and satisfy the diverse needs of users, telecommunications service providers and electronic device manufacturers are competitively developing electronic devices offering a variety of functions. Consequently, the various functions offered through these devices are also becoming increasingly sophisticated.

[0003] As wireless communication technology advances, devices utilizing artificial intelligence (AI) are becoming more widely adopted. For example, home appliances connected to the Internet of Things (IoT) can utilize AI. IoT technology can collect and analyze data generated by these devices to provide intelligent Internet technology services that create new value in human lives. Through the convergence and integration of existing Internet technologies with various industries, IoT technology can be applied to areas such as smart homes, smart buildings, smart cities, smart cars, and smart appliances.

[0004] Meanwhile, homes are equipped with a variety of home appliances for the convenience of users. Various services are being proposed to utilize IoT technology to facilitate the operation and control of home appliances. Home network technology can provide various services to users within the home via the home network. For example, users can control various controlled devices (e.g., IoT-enabled home appliances) that make up the home network using personal electronic devices (e.g., smartphones). Users may desire a wider range of services to control these controlled devices. Accordingly, there is a growing demand for the development of various technologies that manage controlled devices in a way that reflects user intent.

[0005] Embodiments of the present disclosure can provide Internet of Things (IoT) services.

[0006] Embodiments of the present disclosure relate to an electronic device for transferring ownership of an IoT device and a method of operating the same.

[0007] Embodiments of the present disclosure relate to an electronic device and an operating method thereof for transmitting new network connection information to a pre-registered IoT device.

[0008] The technical problems to be achieved in the present disclosure are not limited to the technical problems mentioned above, and other technical problems not mentioned can be clearly understood by a person having ordinary skill in the technical field to which the present invention belongs from the description below.

[0009] A second electronic device according to one embodiment may include a memory storing instructions, a communication circuit, and at least one processor operatively connected to the memory and the communication circuit. The instructions, when executed by the at least one processor, may cause the second electronic device to receive, through the communication circuit, an ownership transfer request message requesting to transfer ownership of an IoT (Internet over Things) device registered in a server from a first user to a second user. The instructions, when executed by the at least one processor, may cause the second electronic device to receive a user input consenting to the ownership transfer of the IoT device. The instructions, when executed by the at least one processor, may cause the second electronic device to transmit, to the server through the communication circuit, a request message requesting the ownership transfer of the IoT device based on the user input. The instructions, when executed by the at least one processor, may cause the second electronic device to receive, from the server through the communication circuit, ownership transfer information necessary to process the ownership transfer of the IoT device after transmitting the request message. The above commands, when executed by the at least one processor, may cause the second electronic device to establish a device-to-device (D2D) connection with the IoT device through the communication circuit based on the ownership transfer information. The above commands, when executed by the at least one processor, may cause the second electronic device to transmit network connection information to the IoT device through the D2D connection, the network connection information being used by the IoT device to connect to the server.

[0010] A first electronic device according to one embodiment of the present disclosure may include a memory storing instructions, a communication circuit, and at least one processor operatively connected to the memory and the communication circuit. The instructions, when executed by the at least one processor, may cause the first electronic device to receive a user input requesting to transfer ownership of a first IoT device among one or more IoT devices registered to a server for a first user to a second user. The instructions, when executed by the at least one processor, may cause the first electronic device to transmit an ownership transfer notification message including user information of the second user to the server through the communication circuit. The instructions, when executed by the at least one processor, may cause the first electronic device to transmit an ownership transfer request message including ownership information indicating a right to transfer ownership of the first IoT device from the first user to a second electronic device associated with the second user through the communication circuit.

[0011] A method by a second electronic device according to one embodiment of the present disclosure may include receiving an ownership transfer request message requesting to transfer ownership of an Internet over Things (IoT) device registered in a server from a first user to a second user. The method may include receiving a user input consenting to the ownership transfer of the IoT device. The method may include transmitting a request message to the server for requesting the ownership transfer of the IoT device based on the user input. The method may include receiving ownership transfer information necessary to process the ownership transfer of the IoT device from the server after transmitting the request message. The method may include establishing a device-to-device (D2D) connection with the IoT device based on the ownership transfer information. The method may include transmitting network connection information to the IoT device through the D2D connection, the network connection information to be used by the IoT device to connect to the server.

[0012] A method by a first electronic device according to one embodiment of the present disclosure may include receiving a user input requesting to transfer ownership of a first IoT device among one or more IoT devices registered to a server for a first user to a second user. The method may include transmitting an ownership transfer notification message including user information of the second user to the server. The method may include transmitting an ownership transfer request message including ownership information indicating a right to transfer ownership of the first IoT device from the first user to a second electronic device associated with the second user.

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

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

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

[0016] FIG. 3 is a diagram for explaining an IoT network according to one embodiment of the present disclosure.

[0017] FIG. 4 is a diagram illustrating an IoT client application according to one embodiment of the present disclosure.

[0018] FIG. 5 is a diagram illustrating transfer of ownership of an IoT device according to one embodiment of the present disclosure.

[0019] FIG. 6 is a flowchart illustrating a procedure for requesting transfer of ownership according to one embodiment of the present disclosure.

[0020] FIG. 7 is a sequence diagram illustrating an ownership transfer procedure using an ownership transfer request message according to one embodiment of the present disclosure.

[0021] FIG. 8 is a flowchart illustrating a procedure for processing an ownership transfer request message according to one embodiment of the present disclosure.

[0022] FIG. 9 is a sequence diagram illustrating a procedure for transferring ownership using a QR code according to one embodiment of the present disclosure.

[0023] FIG. 10 is a flowchart illustrating a procedure for processing ownership transfer based on a QR code according to one embodiment of the present disclosure.

[0024] FIG. 11 is a sequence diagram illustrating a procedure for processing transfer of ownership according to one embodiment of the present disclosure.

[0025] FIG. 12 is a sequence diagram illustrating a procedure for establishing a Wi-Fi connection according to one embodiment of the present disclosure.

[0026] FIG. 13 is a sequence diagram illustrating a procedure for establishing a BLE (Bluetooth low energy) connection according to one embodiment of the present disclosure.

[0027] FIG. 14 is a flowchart illustrating a procedure for processing transfer of ownership according to one embodiment of the present disclosure.

[0028] FIGS. 15A and 15B illustrate a user interface (UI) including a QR code for a transfer of ownership request according to one embodiment of the present disclosure.

[0029] FIGS. 16A, 16B, and 16C illustrate a UI for transmitting an ownership transfer request according to one embodiment of the present disclosure.

[0030] FIG. 17a and FIG. 17b illustrate a UI including a process for transferring ownership according to one embodiment of the present disclosure.

[0031] The terms used in this disclosure are used only to describe specific embodiments and may not be intended to limit the scope of other embodiments. The singular expression may include plural expressions unless the context clearly indicates otherwise. Terms used herein, including technical or scientific terms, may have the same meaning as commonly understood by those of ordinary skill in the art described in this disclosure. Terms defined in general dictionaries among the terms used in this disclosure may be interpreted as having the same or similar meaning in the context of the relevant technology, and shall not be interpreted in an idealized or overly formal sense unless explicitly defined in this disclosure. In some cases, even if a term is defined in this disclosure, it cannot be interpreted to exclude embodiments of the present disclosure.

[0032] The embodiments of the present disclosure described below illustrate a hardware-based approach. However, the embodiments of the present disclosure encompass techniques utilizing both hardware and software, and the description of the embodiments of the present disclosure does not exclude software-based approaches.

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

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

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

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

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

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

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

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

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

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

[0043] According to one embodiment, the voice assistant server (130) can transmit and receive data with the first IoT server (110) via a data network (116). The voice assistant server (130) according to one embodiment can include at least one of a communication interface (131), a processor (132), or a storage unit (133). The communication interface (131) can communicate with a smart phone (136) or an AI speaker (137) via a data network (not shown) and / or a cellular network (not shown). The smart phone (136) or the AI ​​speaker (137) can include a microphone, acquire a user voice, convert it into a voice signal, and transmit the voice signal to the voice assistant server (130).

[0044] The processor (132) can receive a voice signal from a smart phone (136) or an AI speaker (137) via a communication interface (131). The processor (132) can process the received voice signal based on a stored model (134). The processor (132) can generate (or confirm) a control command using the processing result based on information stored in a database (135). According to one embodiment, the storage unit (113, 133, 143) may include a non-transitory storage medium of at least one type among a flash memory type, a hard disk type, a multimedia card micro type, a card type memory (e.g., SD or XD memory, etc.), a RAM (Random Access Memory), a SRAM (Static Random Access Memory), a ROM (Read-Only Memory), an EEPROM (Electrically Erasable Programmable Read-Only Memory), a PROM (Programmable Read-Only Memory), a magnetic memory, a magnetic disk, and an optical disk, and the type thereof is not limited.

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

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

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

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

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

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

[0051] The input module (250) can receive commands or data to be used in a component of the electronic device (201) (e.g., a processor (220)) from an external source (e.g., a user) of the electronic device (201). The input module (250) can include, for example, a microphone, a mouse, a keyboard, a key (e.g., a button), or a digital pen (e.g., a stylus pen).

[0052] The audio output module (255) can output audio signals to the outside of the electronic device (201). The audio output module (255) can include, for example, a speaker or a receiver. The speaker can be used for general purposes, such as multimedia playback or recording playback. The receiver can be used to receive incoming calls. In one embodiment, the receiver can be implemented separately from the speaker or as part of the speaker.

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

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

[0055] The sensor module (276) can detect the operating status (e.g., power or temperature) of the electronic device (201) or the external environmental status (e.g., user status) and generate an electrical signal or data value corresponding to the detected status. According to one embodiment, the sensor module (276) can include, for example, a gesture sensor, a gyro sensor, a barometric pressure sensor, a magnetic sensor, an acceleration sensor, a grip sensor, a proximity sensor, a color sensor, an IR (infrared) sensor, a biometric sensor, a temperature sensor, a humidity sensor, or an illuminance sensor.

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

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

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

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

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

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

[0062] The communication module (290) may support the establishment of a direct (e.g., wired) communication channel or a wireless communication channel between the electronic device (201) and an external electronic device (e.g., electronic device (202), electronic device (204), or server (208)), and the performance of communication through the established communication channel. The communication module (290) may operate independently from the processor (220) (e.g., application processor) and may include one or more communication processors that support direct (e.g., wired) communication or wireless communication. According to one embodiment, the communication module (290) may include a wireless communication module (292) (e.g., a cellular communication module, a short-range wireless communication module, or a global navigation satellite system (GNSS) communication module) or a wired communication module (294) (e.g., a local area network (LAN) communication module, or a power line communication module). Any of these communication modules may communicate with an external electronic device (204) via a first network (298) (e.g., a short-range communication network such as Bluetooth, wireless fidelity (WiFi) direct, or infrared data association (IrDA)) or a second network (299) (e.g., a long-range communication network such as a legacy cellular network, a 5G network, a next-generation communication network, the Internet, or a computer network (e.g., a LAN or WAN)). These various types of communication modules may be integrated into a single component (e.g., a single chip) or implemented as multiple separate components (e.g., multiple chips). The wireless communication module (292) may use subscriber information (e.g., an international mobile subscriber identity (IMSI)) stored in the subscriber identification module (296) to verify or authenticate the electronic device (201) within a communication network such as the first network (298) or the second network (299).

[0063] The wireless communication module (292) can support 5G networks and next-generation communication technologies following the 4G network, such as NR access technology (new radio access technology). The NR access technology can support high-speed transmission of high-capacity data (eMBB (enhanced mobile broadband)), minimization of terminal power and connection of multiple terminals (mMTC (massive machine type communications)), or high reliability and low latency (URLLC (ultra-reliable and low-latency communications)). The wireless communication module (292) can support, for example, a high-frequency band (e.g., mmWave band) to achieve a high data transmission rate. The wireless communication module (292) can support various technologies for securing performance in a high-frequency band, such as beamforming, massive multiple-input and multiple-output (MIMO), full dimensional MIMO (FD-MIMO), array antenna, analog beam-forming, or large scale antenna. The wireless communication module (292) can support various requirements specified in the electronic device (201), an external electronic device (e.g., the electronic device (204)), or a network system (e.g., the second network (299)). According to one embodiment, the wireless communication module (292) can support a peak data rate (e.g., 20 Gbps or more) for realizing eMBB, a loss coverage (e.g., 164 dB or less) for realizing mMTC, or a U-plane latency (e.g., 0.5 ms or less for downlink (DL) and uplink (UL), or 1 ms or less for round trip) for realizing URLLC.

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

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

[0066] At least some of the above components can be interconnected and exchange signals (e.g., commands or data) with each other via a communication method between peripheral devices (e.g., a bus, GPIO (general purpose input and output), SPI (serial peripheral interface), or MIPI (mobile industry processor interface)).

[0067] According to one embodiment, commands or data may be transmitted or received between the electronic device (201) and an external electronic device (204) via a server (208) connected to a second network (299). Each of the external electronic devices (202 or 204) may be the same or a different type of device as the electronic device (201). According to one embodiment, all or part of the operations executed in the electronic device (201) may be executed in one or more of the external electronic devices (202, 204, or 208). For example, when the electronic device (201) is to perform a certain function or service automatically or in response to a request from a user or another device, the electronic device (201) may, instead of or in addition to executing the function or service itself, request one or more external electronic devices to perform the function or at least a part of the service. One or more external electronic devices that receive the request may execute at least a portion of the requested function or service, or an additional function or service related to the request, and transmit the result of the execution to the electronic device (201). The electronic device (201) may process the result as is or additionally and provide it as at least a portion of a response to the request. For this purpose, cloud computing, distributed computing, mobile edge computing (MEC), or client-server computing technology may be used, for example. The electronic device (201) may provide an ultra-low latency service by using distributed computing or mobile edge computing, for example. In another embodiment, the external electronic device (204) may include an Internet of Things (IoT) device. The server (208) may be an intelligent server utilizing machine learning and / or a neural network. According to one embodiment, the external electronic device (204) or the server (208) may be included in the second network (299).The electronic device (201) can be applied to intelligent services (e.g., smart home, smart city, smart car, or healthcare) based on 5G communication technology and IoT-related technology.

[0068] FIG. 3 is a diagram for explaining an IoT network according to one embodiment of the present disclosure.

[0069] Referring to FIG. 3, a network (300) may include a server (310) operating as an IoT cloud, an electronic device (e.g., an electronic device (201)) capable of communicating with the server (310) via the Internet, and at least one IoT device (320) (e.g., controlled devices (320a, 320b, 320c, 320d, 320e) and a hub device (330)) that supports IoT technology and can communicate with the server (310) (e.g., a cloud server) via the Internet (e.g., a Wi-Fi access point (AP) (340)). In one embodiment, the hub device (330) may support connections between controlled devices (320a, 320b, 320c, 320d, 320e) and an electronic device (201) and / or connections between controlled devices (320a, 320b, 320c, 320d) and a server (310) and / or manage controlled devices (320a, 320b, 320c, 320d, 320e). In one embodiment, the electronic device (201) may communicate with the controlled devices (320a, 320b, 320c, 320d, 320e) via a hub device (330), via a server (310), via the Internet using long-range wireless communication (e.g., a second network (299)), or directly using short-range wireless communication (e.g., a first network (298)).

[0070] In one embodiment, the controlled devices (320a, 320b, 320c, 320d, 320e) can be controlled (e.g., to report status and / or execute specific functions) by remote commands (e.g., control commands of the electronic device (201)) and may include, for example, at least one of a television, an air conditioner, a refrigerator, a washing machine, a lighting device, a security camera, a sensor, or a window treatment.

[0071] In one embodiment, at least one of the controlled devices (320a, 320b, 320c, 320d, 320e) may communicate with the electronic device (201) via the hub device (330), communicate with the electronic device (201) via the server (310), and / or communicate directly with the electronic device (201) (e.g., without going through the server (310) or the hub device (330)). In one embodiment, at least one of the controlled devices (320a, 320b, 320c, 320d, 320e) may be configured to communicate with the electronic device (201) via the Internet using long-range wireless communication (e.g., the second network (299)), or using short-range wireless communication (e.g., the first network (298)). In one embodiment, at least one of the controlled devices (320a, 320b, 320c, 320d, 320e) may be configured to communicate with the server (310) via the Internet using long-range wireless communication (e.g., the second network (299)) or using short-range wireless communication (e.g., the first network (298)). In one embodiment, at least one of the controlled devices (320a, 320b, 320c, 320d, 320e) may access the Internet via a Wi-Fi AP (340).

[0072] In one embodiment, the electronic device (201) may be a personal electronic device, such as a smart phone, tablet, or wearable device, or an electronic device having a display and user interface, such as a television or control console. The electronic device (201) may discover an IoT device (320) and perform an onboarding procedure (e.g., a registration procedure) to register the discovered IoT device (320) with the server (310). The IoT device (320) may be registered with the server (310) to be associated with a user account. The electronic device (201) may use the user account to manage and control the IoT device (320) registered with the server (310).

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

[0074] In one embodiment, the hub device (330) is an electronic device that operates an IoT control service, and may be a server or gateway located within a building (home or hotel), or a remote server located outside the building. In one embodiment, the hub device (330) may be a home appliance such as a smartphone, tablet, personal computer (PC), or TV with a hub function. The hub device (330) may be registered with the server (310) via the electronic device (201), similar to the controlled devices (320a, 320b, 320c, 320d, 320e).

[0075] In one embodiment, the electronic device (201) may include a client application for an IoT control service that processes a procedure for registering an IoT device (320) with a cloud server (e.g., server (310)) and enables remote control of the registered IoT device (320). The electronic device may include various devices and platforms such as a mobile phone, a television, a family hub, or a smart watch. The IoT device (320) may have a connection type of hub-connected, direct-connected, or cloud-to-cloud connected. The hub-connected type may mean that the IoT device (320) is connected to a hub device (330) through short-range wireless communication such as Zigbee, Z-Wave, or Wi-Fi, and is connected to the server (310) through the hub device (330). The direct-connected type may mean that the IoT device (320) is directly connected to a Wi-Fi AP (340) and connected to a Wi-Fi This may mean being connected to a server (310) via an AP (320). Cloud-connected may mean that an IoT device (320) registered in a third-party cloud is connected to a server (310) via an application programmable interface (API).

[0076] In one embodiment, the electronic device (201) may perform an operation (e.g., an onboarding procedure) to register the IoT device (320) with the server (310) via a client application. After onboarding, if the IoT device (320) is disconnected from the server (310), the IoT device (320) may perform a designated operation (e.g., a Wi-Fi scan or BLE (Bluetooth low energy) advertising) to find an Internet connection while offline.

[0077] FIG. 4 is a diagram illustrating an IoT client application according to one embodiment.

[0078] Referring to FIG. 4, the electronic device (201) may execute a client application for an IoT control service and display an execution screen (400) provided by the client application through a display module (e.g., the display module (260)). The execution screen (400) may include states (e.g., at least one of an image, a location, a name, or a connection status) of at least one external electronic device (e.g., the IoT device (320)) registered for a user account. The connection status may include online or offline. If the IoT device (320) is normally connected to the server (310), the connection status may indicate an online status. If the IoT device (320) is not normally connected to the server (310), the connection status may indicate an offline status. In one embodiment, the IoT device (320) may be in an offline status based on a disconnection with a Wi-Fi AP (340), a hub device (330), and / or the electronic device (201).

[0079] In one embodiment, when the Internet connection of the IoT device (320) is disconnected, the execution screen (400) may include status information indicating that the IoT device (320) is offline. In one embodiment, the status information (e.g., status object (410)) of an IoT device (e.g., IoT device (320d)) that is offline may be displayed in black and white. Although not shown, the status object of an online controlled device may be displayed in color. Although not shown, when a user input (e.g., touch) is received for a status item (410), the electronic device (201) may display an offline guide pop-up notifying that the IoT device (e.g., IoT device (320d)) is offline.

[0080] In one embodiment, if a user (e.g., a consumer) purchases one or more appliances with IoT functionality and has them delivered to his or her new home, but the new home does not yet have internet access (e.g., a Wi-Fi access point (340) does not exist or is not available), the appliances cannot be onboarded. In one embodiment, appliances in a newly built apartment cannot connect to the internet and therefore cannot be onboarded until the user activates the Wi-Fi access point. In one embodiment, an installer can use his or her electronic device (e.g., a smartphone or a personal digital assistant (PDA)) as a mobile hotspot to onboard multiple appliances and then transfer ownership of the multiple appliances in bulk to the consumer's user account. In one embodiment, an electronic device (e.g., a first electronic device) carried by an installer may request a server to collectively transfer ownership of multiple IoT devices (e.g., home appliances) to the consumer's user account, and may cause an electronic device (e.g., a second electronic device) carried by the user to transmit new network connection information (e.g., Wi-Fi AP information) to the IoT devices.

[0081] FIG. 5 is a diagram illustrating transfer of ownership of an IoT device according to one embodiment.

[0082] Referring to FIG. 5, a second user (e.g., a consumer) may purchase at least one IoT device (510) (e.g., IoT device (320)) (e.g., IoT devices (510a, 510b, 510c, 510d)) and request delivery to a first user (e.g., an installer). Before or after installing the IoT devices (510a, 510b, 510c, 510d) at the second user's home, the first user may perform an operation (e.g., an onboarding procedure) to register the IoT devices (510a, 510b, 510c, 510d) with a server (550) (e.g., server (310)) using a first electronic device (520) (e.g., electronic device (201)). In one embodiment, the first electronic device (520) may act as a mobile hotspot to connect to IoT devices (510a, 510b, 510c, 510d) and allow the IoT devices (510a, 510b, 510c, 510d) to connect to the server (550) through the first electronic device (520). Through the onboarding procedure, the server (550) may identify that the ownership of the IoT devices (510a, 510b, 510c, 510d) belongs to the first user who carries the first electronic device (520).

[0083] In one embodiment, the server (550) may store identification information (e.g., mobile node identifier (mnid)) of the first electronic device (520) and identification information (e.g., serial number (SN)) of the IoT devices (510a, 510b, 510c, 510d) together with user information (e.g., user account, email address, and / or phone number). The user information may indicate that the IoT devices (510a, 510b, 510c, 510d) belong to the first user. In one embodiment, one or more IoT devices (e.g., IoT devices (510a, 510b, 510c, 510d)) registered to the first user may be associated with the same user information.

[0084] In one embodiment, a first electronic device (520) may receive a user input from a first user requesting to transfer ownership of IoT devices (510a, 510b, 510c, 510d) to a second user. Based on the user input, the first electronic device (520) may request an ownership transfer to a second electronic device (530) (e.g., electronic device (201)) possessing the second user. In one embodiment, the first electronic device (520) may transmit an ownership transfer request message to the second electronic device (530) (e.g., the procedure of FIG. 7) or display a machine-readable code (e.g., a quick response (QR) code) for the ownership transfer request so that the second electronic device (530) scans the code (e.g., the procedure of FIG. 9).

[0085] In one embodiment, the first electronic device (520) may transmit an ownership transfer notice to the server (550) indicating that ownership of the IoT devices (510a, 510b, 510c, 510d) is to be transferred to a second user. The second electronic device (530) may inquire of the server (550) (e.g., the procedure of FIG. 11) to receive ownership transfer information of the IoT devices (510a, 510b, 510c, 510d) from the server (550).

[0086] The above ownership transfer information may represent information required to register IoT devices (510a, 510b, 510c, 510d) to the server (550) via the second electronic device (530). In one embodiment, the ownership transfer information may include at least one of identification information of the second electronic device (530) (e.g., mnid), identification information of the IoT devices (510a, 510b, 510c, 510d) (e.g., model code and / or serial number), service set identifier (SSID) of a Wi-Fi AP to which the IoT devices (510a, 510b, 510c, 510d) were last connected, ownership information of the IoT devices (510a, 510b, 510c, 510d) (e.g., owner ID), or media access address (MAC) address information of the IoT devices (510a, 510b, 510c, 510d).

[0087] Figure 6 is a flowchart illustrating a procedure for requesting a transfer of ownership according to one embodiment of the present disclosure. Depending on the embodiments, at least one of the operations described below may be modified, omitted, or executed in a different order. Depending on the embodiments, at least one of the operations described below may be executed by a processor (e.g., processor 220) of the first electronic device (520).

[0088] Referring to FIG. 6, in operation 602, a first electronic device (520) (e.g., processor (220)) may display a user interface (UI) including a device list of at least one IoT device (e.g., IoT device (510)) registered for a first user through a display module (e.g., display module (260)). In one embodiment, the device list may include at least one of a device name, an image, a model name, a location, or a connection status of the IoT device (510). In one embodiment, the device list may include at least one of a device name, an image, a model name, a location, or a connection status of one or more IoT devices (510a, 510b, 510c, 510d) located in a specified location (e.g., home, office, living room, or bedroom).

[0089] At step 604, the first electronic device (520) (e.g., the processor (220)) may receive a user input requesting to transfer ownership of the IoT device (510) through the UI (in one embodiment, a user input selecting the IoT device (510). At step 606, the first electronic device (520) (e.g., the processor (220)) may receive user information (e.g., a user account, an email address, and / or a phone number) of a second user to whom ownership of the IoT device (510) will be transferred. In one embodiment, step 606 may be omitted.

[0090] In operation 608, the first electronic device (520) (e.g., the processor (220)) may transmit an ownership transfer notification message indicating that the ownership of the IoT device (510) is transferred from the first user to the second user to the server (550). In one embodiment, the ownership transfer notification message may include at least one of user 1 information indicating the first user, user 2 information indicating the second user, or device information indicating the IoT device (510). In one embodiment, the user 1 information may include a user account and / or an email address of the first user. In one embodiment, the user 2 information may include a user account and / or an email address of the second user. In one embodiment, the device information may include a device identifier (ID) of the IoT device (510).

[0091] In one embodiment, the first electronic device (520) (e.g., the processor (220)) may transmit the ownership transfer notification to the server (550), thereby causing the server (550) to transmit an ownership transfer request message to the second electronic device (530) to request that the ownership of the IoT device (510) be transferred from the first user to the second user. In one embodiment, the ownership transfer request message may be transmitted to the second electronic device (530) based on the email address transmitted in operation 608. In one embodiment, the ownership transfer request message may be transmitted to the second electronic device (530) via a short messaging service (SMS) or an instant messaging service based on the phone number transmitted in operation 608. In one embodiment, the ownership transfer request message may be transmitted to the second electronic device (530) via an application push notification based on the user account transmitted in operation 608.

[0092] In operation 610, the first electronic device (520) (e.g., the processor (220)) may receive ownership information (e.g., an ownership token and / or an owner ID) of the IoT device (510) from the server (550). The ownership information (e.g., an ownership token and / or an owner ID) may indicate a right to transfer ownership from the first user. In one embodiment, operation 610 may be omitted.

[0093] In operation 612, the first electronic device (520) (e.g., the processor (220)) may display a machine-readable code (e.g., a QR code) via the display module (260) to request transfer of ownership of the IoT device (510) from the first user to the second user. In one embodiment, the operation of displaying the QR code may correspond to operation 912 of FIG. 9. In one embodiment, the first electronic device (520) (e.g., the processor (220)) may generate a QR code including the ownership information (e.g., an owner ID) based on a user input and display the QR code. The QR code may cause the second electronic device (530) to install a client application for an IoT control service and / or process the transfer of ownership of the IoT device (510) via the client application.

[0094] In one embodiment, instead of displaying a QR code, the first electronic device (520) (e.g., the processor (220)) may transmit an ownership transfer request message to the second electronic device (530) to request that ownership of the IoT device (510) be transferred from the first user to the second user. In one embodiment, the operation of transmitting the ownership transfer request message may correspond to operation 710 of FIG. 7.

[0095] In one embodiment, the ownership transfer request message may be transmitted to the second electronic device (530) based on the email address received in operation 606. In one embodiment, the ownership transfer request message may be transmitted to the second electronic device (530) via SMS or an instant messaging service based on the phone number received in operation 606. In one embodiment, the ownership transfer request message may be transmitted to the second electronic device (530) via an application push notification based on the user account received in operation 606.

[0096] Figure 7 is a sequence diagram illustrating an ownership transfer procedure using an ownership transfer request message according to one embodiment of the present disclosure. Depending on the embodiments, at least one of the operations described below may be modified, omitted, or executed in a different order.

[0097] Referring to FIG. 7, in operation 702, the first electronic device (520) may display a device list of at least one IoT device (e.g., IoT device (510)) registered for the first user. In one embodiment, the device list may include at least one of a device name, an image, a model name, a location, or a connection status of each IoT device. In operation 704, the first electronic device (520) may receive a user input (e.g., a touch) for selecting at least one IoT device (e.g., IoT device (510) or a designated device group) to be transferred based on the device list. In operation 706, the first electronic device (520) may receive information (e.g., a user account, an email address, and / or a phone number) of a second user to whom ownership of the IoT device (510) will be transferred.

[0098] In operation 708, the first electronic device (520) may transmit an ownership transfer notification message including user1 information representing a first user, user2 information representing a second user, and / or device information representing an IoT device (510) to the server (550). Although not shown, after transmitting the ownership transfer notification message, the first electronic device (520) may receive ownership information including an owner ID associated with the IoT device (510) from the server (550).

[0099] In operation 710, the first electronic device (520) may transmit an ownership transfer request message to the second electronic device (530). In one embodiment, operation 710 may be omitted, and instead, in operation 710a, the server (550) may transmit the ownership transfer request message to the second electronic device (530) based on the ownership transfer notification message received in operation 708. In one embodiment, the ownership transfer request message may be transmitted based on a phone number, an email address, and / or a user account.

[0100] In one embodiment, the ownership transfer request message may include device information to be transferred (e.g., a list of devices to be transferred) and / or ownership information (e.g., an ownership token and / or an owner ID) representing the IoT device (510). In one embodiment, the device information to be transferred may include at least one of a device ID, a device name, an image, or a model name. The ownership information may indicate a right to receive ownership from the first user. In one embodiment, the ownership transfer request message may include information indicating that there is a device to be transferred to the second electronic device (530), without specific device information. In one embodiment, after receiving the ownership transfer request message, the second electronic device (530) may obtain the device information to be transferred from the server (550).

[0101] In operation 712, the second electronic device (530) may display an ownership transfer guidance UI including the device information to be transferred. In one embodiment, the device information to be transferred may include at least one of a device name, an image, or a model name for at least one IoT device (e.g., IoT device (510)). In one embodiment, if the ownership transfer request message does not include specific device information to be transferred, the second electronic device (530) may simply display information indicating that at least one IoT device to be transferred exists. In operation 714, the second electronic device (530) may receive a user input agreeing to the ownership transfer. In one embodiment, the second electronic device (530) may receive a user input for selecting at least one IoT device to be transferred (e.g., IoT device (510)) based on the displayed device information to be transferred. In one embodiment, the second electronic device (530) may receive a user input agreeing to the ownership transfer of at least one IoT device that it does not know.

[0102] In one embodiment, operations 712 and 714 may be omitted, and the second electronic device (530) may perform the ownership transfer processing as a background operation without user intervention.

[0103] In step 716, the second electronic device (530) may transmit an ownership transfer request message to the server (550). In one embodiment, the ownership transfer request message may include device information to be transferred (e.g., device ID) and / or ownership information (e.g., ownership token and / or owner ID) indicating at least one IoT device to be transferred (e.g., IoT device (510)). In one embodiment, the ownership transfer request message may include information requesting the transfer of ownership of at least one unknown IoT device.

[0104] In operation 718, the server (550) may perform an ownership transfer process of the IoT device (510) in response to the ownership transfer request message. In one embodiment, the server (550) may delete previous user information of the IoT device (510) (e.g., information related to the first user and / or the first electronic device (520). In one embodiment, the server (550) may update user information for the IoT device (510) to a second user. In one embodiment, the server (550) may change ownership information (e.g., owner ID) of the IoT device (510). In one embodiment, the server (550) may store identification information (e.g., mnid) of the second electronic device (530) and identification information (e.g., serial number) of the IoT device (510) in association with the changed ownership information (e.g., owner ID). The changed ownership information may indicate that the ownership of the IoT device (510) belongs to the second user. In one embodiment, the server (550) may register a new location (e.g., a room) for the IoT device (510).

[0105] In operation 720, the server (550) may transmit an ownership transfer approval message to the second electronic device (530) indicating that ownership of the IoT device (510) has been transferred to the second user. In one embodiment, the ownership transfer approval message may include ownership transfer information indicating information necessary to register the IoT device (510) with the server (550) via the second electronic device (530). In one embodiment, the ownership transfer information may include at least one of identification information of the second electronic device (530) (e.g., mnid), identification information of the IoT device (510) (e.g., model code and / or serial number), SSID, ownership information of the IoT device (510) (e.g., owner ID), or at least one MAC address of the IoT device (510) (e.g., hashed MAC address).

[0106] In operation 722, the second electronic device (530) may establish a D2D (device-to-device) connection based on short-range wireless communication with the IoT device (510) based on the ownership transfer information. In one embodiment, the D2D connection may include at least one of a Zigbee connection, a Z-Wave connection, a Wi-Fi connection, a Bluetooth legacy connection, and / or a BLE connection. In one embodiment, the ownership transfer information may include a Wi-Fi MAC address of the IoT device (510) and / or a BLE MAC address of the IoT device (510), and the second electronic device (530) may establish a Wi-Fi connection or a BLE connection with the IoT device (510) using the Wi-Fi MAC address or the BLE MAC address. In one embodiment, operation 722 may include the procedure of FIG. 12 or the procedure of FIG. 13.

[0107] In operation 724, the second electronic device (530) may transmit network connection information necessary for the IoT device (510) to connect to the server (550) to the IoT device (510) through the D2D connection. In one embodiment, the network connection information may include an SSID (service set ID), a password, and / or authentication type information of a Wi-Fi AP (e.g., a Wi-Fi AP (540)). In one embodiment, the second electronic device (530) may include an SSID and a password of a Wi-Fi AP (e.g., a Wi-Fi AP (540)) to which the second electronic device (530) is currently connected or has connected in the network connection information. In one embodiment, the second electronic device (530) may transmit the network connection information to the IoT device (510) through the D2D connection, thereby notifying the IoT device (510) that the ownership of the IoT device (510) has been transferred from a first user to a second user. In one embodiment, the IoT device (510) may store information indicating that the owner of the IoT device (510) has changed from a first electronic device (520) to a second electronic device (530).

[0108] In operation 726, the IoT device (510) may connect to the server (550) using the network connection information. In one embodiment, the IoT device (510) may connect to the Wi-Fi AP (540) using the SSID and password included in the network connection information, and may connect to the server (550) through the Wi-Fi AP (540). After connecting to the server (550), the IoT device (510) may transmit a connection completion report to the server (550). The server (550) may update the connection status of the IoT device (510) to an online state based on the connection completion report.

[0109] At step 728, the server (550) may transmit an ownership transfer completion notification message to the second electronic device (530) based on the successful connection of the IoT device (510). The ownership transfer completion notification message may include information indicating that the IoT device (510) is online and that ownership of the IoT device (510) has been transferred to the second user. In one embodiment, after step 720 or step 728, the second electronic device (530) may display a result UI indicating the result of the ownership transfer of the IoT device (510) (e.g., “IoT device (510) has been onboarded”).

[0110] Figure 8 is a flowchart illustrating a procedure for processing an ownership transfer request message according to one embodiment of the present disclosure. Depending on the embodiments, at least one of the operations described below may be modified, omitted, or executed in a different order. Depending on the embodiments, at least one of the operations described below may be executed by a processor (e.g., processor 220) of the second electronic device (530).

[0111] Referring to FIG. 8, in operation 802, the second electronic device (530) (e.g., the processor (220)) may receive an ownership transfer request message (e.g., the ownership transfer request message of operation 710) related to at least one IoT device to be transferred (e.g., the IoT device (510)) from the first electronic device (520) or the server (550). In one embodiment, the second electronic device (530) (e.g., the processor (220)) may receive the ownership transfer request message via SMS, an instant messaging service, or email, and execute a client application for an IoT control service based on receiving the ownership transfer request message. If the client application is not installed, the second electronic device (530) (e.g., the processor (220)) may install the client application based on receiving the ownership transfer request message. In one embodiment, the second electronic device (530) may execute the client application based on receiving the ownership transfer request message via a push notification of the client application.

[0112] In one embodiment, the ownership transfer request message may include device-to-be-transferred information (e.g., a list of devices to be transferred) associated with at least one IoT device to be transferred (e.g., an IoT device (510)). In one embodiment, the second electronic device (530) (e.g., a processor (220)) may obtain the device-to-be-transferred information from the server (550) after receiving the ownership transfer request message. In one embodiment, the ownership transfer request message may include device-to-be-transferred information (e.g., a list of devices to be transferred) and / or ownership information (e.g., an ownership token and / or an owner ID) representing the IoT device (510).

[0113] In operation 804, the second electronic device (530) (e.g., processor (220)) may display information about the device to be transferred (e.g., the information about the device to be transferred of operation 712) based on the ownership transfer request message. In one embodiment, the information about the device to be transferred may include at least one of a device name, an image, or a model name for at least one IoT device (e.g., IoT device (510)). In one embodiment, the information about the device to be transferred may include information simply indicating that at least one IoT device to be transferred to the second user exists.

[0114] At step 806, the second electronic device (530) (e.g., processor (220)) may receive user input consenting to the transfer of ownership (e.g., user input of step 714). The user input may include user input selecting at least one IoT device to which ownership is to be transferred, or may include user input consenting to the transfer of ownership of any IoT device.

[0115] At step 808, the second electronic device (530) (e.g., the processor (220)) may transmit an ownership transfer request message (e.g., the ownership transfer request message of step 716) to the server (550). In one embodiment, the ownership transfer request message may include information (e.g., a device ID) and / or ownership information (e.g., an ownership token and / or an owner ID) indicating at least one IoT device (e.g., the IoT device (510)) to receive the ownership transfer request message. In one embodiment, the ownership transfer request message may include information requesting a transfer of ownership of at least one unknown IoT device.

[0116] In operation 810, the second electronic device (530) (e.g., processor (220)) may receive ownership transfer information (e.g., ownership transfer information of operation 720) from the server (550). In one embodiment, the ownership transfer information may include at least one of identification information of the second electronic device (530) (e.g., mnid), identification information of at least one IoT device to be transferred (e.g., IoT device (510)) (e.g., model code and / or serial number), SSID, ownership information of the IoT device (510) (e.g., owner ID), or at least one MAC address of the IoT device (510).

[0117] In operation 812, the second electronic device (530) (e.g., the processor (220)) may establish a D2D connection (e.g., the D2D connection of operation 722) with the IoT device (510) based on the ownership transfer information. In operation 814, the second electronic device (530) (e.g., the processor (220)) may transmit network connection information (e.g., the network connection information of operation 724) to the IoT device (510) through the D2D connection, thereby allowing the IoT device (510) to connect to the server (550) through the network connection information. The network connection information may include an SSID and password of a Wi-Fi AP (e.g., a Wi-Fi AP (540)) to which the second electronic device (530) is connected or has connected. In one embodiment, the second electronic device (530) may notify the IoT device (510) that ownership of the IoT device (510) has been transferred from the first user to the second user by transmitting the network connection information to the IoT device (510).

[0118] Figure 9 is a sequence diagram illustrating a procedure for transferring ownership using a QR code according to one embodiment of the present disclosure. Depending on the embodiments, at least one of the operations described below may be modified, omitted, or executed in a different order.

[0119] Referring to FIG. 9, in operation 902, the first electronic device (520) may display a device list of at least one IoT device (e.g., IoT device (510)) registered for the first user. In one embodiment, the device list may include at least one of a device name, an image, a model name, a location, or a connection status of each IoT device. In operation 904, the first electronic device (520) may receive a user input (e.g., a touch) for selecting at least one IoT device (e.g., IoT device (510) or a specified device group) to be transferred based on the device list.

[0120] At operation 906, the first electronic device (520) may transmit an ownership information request message to the server (550) to request ownership information (e.g., an ownership token and / or an owner ID) associated with the first user. In one embodiment, the ownership information request message may include device information representing at least one IoT device selected at operation 904. At operation 908, the first electronic device (520) may transmit an ownership information response message to the second electronic device (530) that includes ownership information (e.g., an ownership token and / or an owner ID) associated with the first user. The ownership information (e.g., an ownership token and / or an owner ID) may indicate a right to transfer ownership from the first user.

[0121] In operation 910, the second electronic device (530) may display a QR code (e.g., QR code 1512 of FIG. 15B) for a request for transfer of ownership. In one embodiment, the QR code may include the ownership information. The QR code may include information for causing the second electronic device (530) to install a client application for an IoT control service and / or perform an operation (e.g., operation 914) for transferring ownership of the IoT device (510) through the client application. In operation 912, the second electronic device (530) may scan the QR code to obtain the ownership information. Although not illustrated, in one embodiment, the second electronic device (530) may receive a user input agreeing to the transfer of ownership based on scanning the QR code. In one embodiment, the second electronic device (530) may display an ownership transfer guidance UI (e.g., ownership transfer guidance UI (1702)) based on scanning the QR code, and receive a user input agreeing to the ownership transfer through the ownership transfer guidance UI.

[0122] In operation 914, the second electronic device (530) may transmit an ownership transfer request message to the server (550) based on scanning the QR code. In one embodiment, the ownership transfer request message may include information indicating at least one IoT device to be transferred, information indicating a group (e.g., location or space) of at least one IoT device to be transferred, and / or ownership information (e.g., ownership token and / or owner ID) obtained from the QR code. In one embodiment, the ownership transfer request message may include information requesting a transfer of ownership of at least one IoT device registered for the ownership information.

[0123] In operation 916, the server (550) may perform an ownership transfer process for at least one registered IoT device (e.g., IoT device (510)) corresponding to the ownership information in response to the ownership transfer request message. In one embodiment, the server (550) may perform an ownership transfer process for at least one IoT device (e.g., IoT device (510)) identified by the ownership information request message of operation 906 among one or more IoT devices registered for the owner ID.

[0124] In one embodiment, the server (550) may delete previous user information of the IoT device (510) (e.g., information associated with the first user and / or the first electronic device (520). In one embodiment, the server (550) may update user information for the IoT device (510) to a second user. In one embodiment, the server (550) may change ownership information (e.g., owner ID) of the IoT device (510). In one embodiment, the server (550) may store identification information (e.g., mnid) of the second electronic device (530) and identification information (e.g., model code and / or serial number) of the IoT device (510) in association with the changed ownership information (e.g., owner ID). The changed ownership information may indicate that the ownership of the IoT device (510) belongs to the second user. In one embodiment, the server (550) may register a new location (e.g., room) for the IoT device (510).

[0125] In operation 918, the server (550) may transmit an ownership transfer approval message to the second electronic device (530), indicating that ownership of the IoT device (510) has been transferred to the second user. In one embodiment, the ownership transfer approval message may include ownership transfer information indicating information necessary to register the IoT device (510) with the server (550) via the second electronic device (530). In one embodiment, the ownership transfer information may include at least one of identification information of the second electronic device (530) (e.g., mnid), identification information of at least one IoT device to be transferred (e.g., IoT device (510)) (e.g., model code and / or serial number), SSID, ownership information of the IoT device (510) (e.g., owner ID), or at least one MAC address of the IoT device (510). In one embodiment, the ownership transfer information may include at least one hashed MAC address.

[0126] In operation 920, the second electronic device (530) may establish a D2D connection based on short-range wireless communication with the IoT device (510) based on the ownership transfer information. In one embodiment, the D2D connection may include at least one of a Zigbee connection, a Z-Wave connection, a Wi-Fi connection, a Bluetooth legacy connection, and / or a BLE connection. In one embodiment, the ownership transfer information may include a Wi-Fi MAC address of the IoT device (510) and / or a BLE MAC address of the IoT device (510), and the second electronic device (530) may establish a Wi-Fi connection or a BLE connection with the IoT device (510) using the Wi-Fi MAC address or the BLE MAC address. In one embodiment, operation 920 may include the procedure of FIG. 12 or the procedure of FIG. 13.

[0127] In operation 922, the second electronic device (530) may transmit network connection information necessary for the IoT device (510) to connect to the server (550) to the IoT device (510) through the D2D connection. In one embodiment, the network connection information may include an SSID, a password, and / or authentication type information of a Wi-Fi AP (e.g., a Wi-Fi AP (540)). In one embodiment, the second electronic device (530) may include an SSID and a password of a Wi-Fi AP (e.g., a Wi-Fi AP (540)) to which the second electronic device (530) is currently connected or has connected in the network connection information. In one embodiment, the second electronic device (530) may transmit the network connection information to the IoT device (510) through the D2D connection, thereby notifying the IoT device (510) that the ownership of the IoT device (510) has been transferred from a first user to a second user. In one embodiment, the IoT device (510) may store information indicating that the owner of the IoT device (510) has changed from a first electronic device (520) to a second electronic device (530).

[0128] In operation 924, the IoT device (510) may connect to the server (550) using the network connection information. In one embodiment, the IoT device (510) may connect to the Wi-Fi AP (540) using the SSID and password included in the network connection information, and may connect to the server (550) through the Wi-Fi AP (540). After connecting to the server (550), the IoT device (510) may transmit a connection completion report to the server (550). The server (550) may update the connection status of the IoT device (510) to an online state based on the connection completion report.

[0129] At operation 926, the server (550) may transmit an ownership transfer completion notification message to the second electronic device (530) based on the successful connection of the IoT device (510). The ownership transfer completion notification message may include information indicating that the IoT device (510) is online and that ownership of the IoT device (510) has been transferred to the second user. In one embodiment, after operation 918 or operation 926, the second electronic device (530) may display a result UI indicating the result of the ownership transfer of the IoT device (510) (e.g., “IoT device (510) has been onboarded”).

[0130] Figure 10 is a flowchart illustrating a procedure for processing a transfer of ownership based on a QR code according to one embodiment of the present disclosure. Depending on the embodiments, at least one of the operations described below may be modified, omitted, or executed in a different order. Depending on the embodiments, at least one of the operations described below may be executed by a processor (e.g., processor 220) of the second electronic device (530).

[0131] Referring to FIG. 10, in operation 1002, the second electronic device (530) (e.g., the processor (220)) may scan a QR code (e.g., the QR code (1512) of FIG. 15B) to obtain ownership information (e.g., an ownership token and / or an owner ID) included in the QR code. In one embodiment, the second electronic device (530) (e.g., the processor (220)) may execute a client application for an IoT control service based on scanning the QR code. If the client application is not installed, the second electronic device (530) (e.g., the processor (220)) may install the client application based on scanning the QR code. In one embodiment, the second electronic device (530) (e.g., the processor (220)) may proceed to operation 1004 to process ownership transfer of the IoT device (510) through the client application based on scanning the QR code. Although not shown, in one embodiment, the second electronic device (530) may receive user input consenting to the transfer of ownership based on scanning the QR code.

[0132] In operation 1004, the second electronic device (530) (e.g., processor (220)) may transmit an ownership transfer request message (e.g., ownership transfer request message of operation 914) including the ownership information to the server (550). In one embodiment, the ownership transfer request message may include information requesting a transfer of ownership of at least one IoT device registered for the ownership information.

[0133] In operation 1006, the second electronic device (530) (e.g., processor (220)) may receive ownership transfer information (e.g., ownership transfer information of operation 918) from the server (550). In one embodiment, the ownership transfer information may include at least one of identification information of the second electronic device (530) (e.g., mnid), identification information of at least one IoT device to be transferred (e.g., IoT device (510)) (e.g., model code and / or serial number), SSID, ownership information of the IoT device (510) (e.g., owner ID), or at least one MAC address of the IoT device (510).

[0134] In operation 1008, the second electronic device (530) (e.g., the processor (220)) may establish a D2D connection (e.g., the D2D connection of operation 920) with the IoT device (510) based on the ownership transfer information. In operation 1010, the second electronic device (530) (e.g., the processor (220)) may transmit network connection information (e.g., the network connection information of operation 922) required for the IoT device (510) to connect to the server (550) to the IoT device (510) through the D2D connection, thereby allowing the IoT device (510) to connect to the server (550) through the network connection information. In one embodiment, the second electronic device (530) may notify the IoT device (510) that the ownership of the IoT device (510) has been transferred from the first user to the second user by transmitting the network connection information to the IoT device (510).

[0135] Figure 11 is a sequence diagram illustrating a procedure for processing a transfer of ownership according to one embodiment of the present disclosure. Depending on the embodiments, at least one of the operations described below may be modified, omitted, or executed in a different order.

[0136] Referring to FIG. 11, in operation 1102, the second electronic device (530) may transmit a query message to the server (550) to query the existence of an IoT device to be transferred. In one embodiment, the second electronic device (530) may execute a client application for an IoT control service and transmit the query message based on receiving a user input requesting a transfer of ownership through the client application. In one embodiment, the query message may include user information of the second user (e.g., a user account, an email address, and / or a phone number).

[0137] Although not illustrated, in one embodiment, the server (550) may receive an ownership transfer notification from the first electronic device (520) indicating that ownership of at least one IoT device (e.g., IoT device (510)) is transferred from a first user to a second user, and may store information of the ownership transfer notification. In one embodiment, the server (550) may retrieve information of the ownership transfer notification based on receiving the inquiry message, and determine to process the ownership transfer of the IoT device (510) associated with the second user.

[0138] In operation 1104, the server (550) may transmit a response message to the second electronic device (530) indicating that there is at least one IoT device to which ownership is to be transferred.

[0139] In operation 1106, the second electronic device (530) may display an ownership transfer guidance UI (e.g., ownership transfer guidance UI (1702) of FIG. 17A) indicating that there is at least one IoT device to which ownership will be transferred, through a display module (e.g., display module (260)). In operation 1108, the second electronic device (530) may receive a user input (e.g., user input (1704)) requesting to process ownership transfer through the ownership transfer guidance UI.

[0140] In operation 1110, the second electronic device (530) may transmit a request message to the server (550) for requesting a list of devices to be transferred. In operation 1112, the server (550) may transmit a response message to the second electronic device (530) including a list of devices for which a transfer of ownership has been requested, for example, at least one IoT device (e.g., IoT device (510)) associated with an ownership transfer notification.

[0141] In operation 1114, the second electronic device (530) may transmit a request message to the server (550) for requesting ownership transfer information necessary to process the ownership transfer of the IoT device (510). In operation 1116, the server (550) may transmit a response message including the ownership transfer information to the second electronic device (530). In one embodiment, the ownership transfer information may include at least one of identification information of the second electronic device (530) (e.g., mnid), identification information of at least one IoT device to be transferred (e.g., IoT device (510)) (e.g., model code and / or serial number), SSID, ownership information of the IoT device (510) (e.g., owner ID), or at least one MAC address of the IoT device (510). In one embodiment, the ownership transfer information may include at least one hashed MAC address.

[0142] In operation 1118, the second electronic device (530) may establish a D2D connection based on short-range wireless communication with the IoT device (510) based on the ownership transfer information. In one embodiment, the D2D connection may include at least one of a Zigbee connection, a Z-Wave connection, a Wi-Fi connection, a Bluetooth legacy connection, and / or a BLE connection. In one embodiment, the ownership transfer information may include a Wi-Fi MAC address of the IoT device (510) and / or a BLE MAC address of the IoT device (510), and the second electronic device (530) may establish a Wi-Fi connection or a BLE connection with the IoT device (510) using the Wi-Fi MAC address or the BLE MAC address. In one embodiment, operation 1118 may include the procedure of FIG. 12 or the procedure of FIG. 13.

[0143] In operation 1120, the second electronic device (530) may transmit network connection information necessary for the IoT device (510) to connect to the server (550) to the IoT device (510) through the D2D connection. In one embodiment, the network connection information may include an SSID, a password, and / or authentication type information of a Wi-Fi AP (e.g., a Wi-Fi AP (540)). In one embodiment, the second electronic device (530) may include an SSID and a password of a Wi-Fi AP (e.g., a Wi-Fi AP (540)) to which the second electronic device (530) is currently connected or has connected in the network connection information. In one embodiment, the second electronic device (530) may transmit the network connection information to the IoT device (510) through the D2D connection, thereby notifying the IoT device (510) that the ownership of the IoT device (510) has been transferred from a first user to a second user. In one embodiment, the IoT device (510) may store information indicating that the owner of the IoT device (510) has changed from a first electronic device (520) to a second electronic device (530).

[0144] In operation 1122, the IoT device (510) may connect to the server (550) using the network connection information. In one embodiment, the IoT device (510) may connect to the Wi-Fi AP (540) using the SSID and password included in the network connection information, and may connect to the server (550) through the Wi-Fi AP (540). After connecting to the server (550), the IoT device (510) may transmit a connection completion report to the server (550). The server (550) may update the connection status of the IoT device (510) to an online state based on the connection completion report. The server (550) may update the user information of the IoT device (510) to a second user based on the connection completion report.

[0145] In operation 1124, the server (550) may transmit an ownership transfer completion notification message to the second electronic device (530) based on the successful connection of the IoT device (510). The ownership transfer completion notification message may include information indicating that the IoT device (510) is online and that ownership of the IoT device (510) has been transferred to the second user. In one embodiment, after operation 1116 or operation 1124, the second electronic device (530) may display a result UI indicating the result of the ownership transfer of the IoT device (510) (e.g., “IoT device (510) has been onboarded”).

[0146] FIG. 12 is a sequence diagram illustrating a procedure for establishing a Wi-Fi connection according to one embodiment of the present disclosure. Depending on the embodiments, at least one of the operations described below may be modified, omitted, or executed in a different order.

[0147] Referring to FIG. 12, in operation 1202, the IoT device (510) may identify that it is disconnected from the server (550) (e.g., offline). In one embodiment, the IoT device (510) may be registered with the server (550) through the first electronic device (520) using the first electronic device (520) as a mobile hotspot, and then may go offline based on the disconnection with the mobile hotspot (i.e., the first electronic device (520)).

[0148] In operation 1204, the IoT device (510) may perform a designated operation (e.g., a Wi-Fi scan) based on identifying an offline state. In one embodiment, the IoT device (510) may perform a Wi-Fi scan to search for a previously connected Wi-Fi AP (e.g., the first electronic device (520)) and a designated AP (e.g., a local hotspot AP). In one embodiment, the local hotspot AP may mean an AP having a designated SSID (e.g., an SSID including an owner ID).

[0149] At operation 1206, the second electronic device (530) may begin operating in a local hotspot mode to process the ownership transfer. In one embodiment, the second electronic device (530) may initiate the local hotspot mode based on receiving an ownership transfer request message from the first electronic device (520) (e.g., the ownership transfer request message of operation 710), scanning a QR code including an owner ID (e.g., the QR code of operation 910), or receiving ownership transfer information including an owner ID from a server (550) (e.g., the ownership transfer information of operation 1116). In one embodiment, the second electronic device (530) may initiate the local hotspot mode based on identifying that the IoT device (510) supports soft AP mode. In one embodiment, the second electronic device (530) may initiate the local hotspot mode based on identifying that the IoT device (510) includes a Wi-Fi MAC address (e.g., a hashed Wi-Fi MAC address) in the ownership transfer information.

[0150] In operation 1208, the second electronic device (530) may broadcast a beacon message including a designated SSID according to the local hotspot mode. In one embodiment, at least some bits of the designated SSID may be set to the owner ID. In one embodiment, at least some bits of the designated SSID may be set to a hashed value of the owner ID.

[0151] In operation 1210, the IoT device (510) can discover a second electronic device (530) operating in local hotspot mode by receiving the beacon message through a Wi-Fi scan. The IoT device (510) can obtain the owner ID from the SSID included in the beacon message using a designated hash function.

[0152] In operation 1212, the second electronic device (530) may establish a Wi-Fi connection with the IoT device (510). In one embodiment, the second electronic device (530) may establish the Wi-Fi connection based on the Wi-Fi MAC address (e.g., a hashed Wi-Fi MAC address) of the IoT device (510) included in the ownership transfer information.

[0153] In operation 1214, the IoT device (510) may begin operating in a hypertext transfer protocol secure (HTTPS) server mode after the Wi-Fi connection is established. In one embodiment, the IoT device (510) may initiate the HTTPS server mode based on establishing a Wi-Fi connection with a new AP (e.g., the second electronic device (530)) or a designated local hotspot (e.g., the second electronic device (530)) in an offline state. In operation 1216, the second electronic device (530) may establish an HTTPS connection with the IoT device (510) via the Wi-Fi connection. In one embodiment, the second electronic device (530) may establish the HTTPS connection based on discovering an IP (internet protocol) address of the IoT device (510) from a designated ARP (address resolution protocol) table. The HTTPS connection may be used to transfer network connection information from the second electronic device (530) to the IoT device (510).

[0154] FIG. 13 is a sequence diagram illustrating a procedure for establishing a BLE connection according to one embodiment of the present disclosure. Depending on the embodiments, at least one of the operations described below may be modified, omitted, or executed in a different order.

[0155] Referring to FIG. 13, in operation 1302, the IoT device (510) may identify that it is disconnected from the server (550) (e.g., offline). In one embodiment, the IoT device (510) may become offline based on the disconnection with the mobile hotspot (i.e., the first electronic device (520)) after registering with the server (550) through the first electronic device (520) using the first electronic device (520) as a mobile hotspot.

[0156] In operation 1304, the IoT device (510) may perform a designated operation (e.g., BLE advertising) based on identifying an offline status. In one embodiment, the IoT device (510) may broadcast a BLE advertising message including the BLE MAC address of the IoT device (510).

[0157] In operation 1306, the second electronic device (530) may perform a BLE scan to process an ownership transfer. In one embodiment, the second electronic device (530) may initiate the BLE scan based on receiving an ownership transfer request message from the first electronic device (520) (e.g., the ownership transfer request message of operation 710), scanning a QR code including an owner ID (e.g., the QR code of operation 910), or receiving ownership transfer information including an owner ID from a server (550) (e.g., the ownership transfer information of operation 1116). In one embodiment, the second electronic device (530) may initiate the BLE scan based on identifying that the IoT device (510) supports BLE. In one embodiment, the second electronic device (530) may initiate the BLE scan based on identifying that the IoT device (510) includes a BLE MAC address (e.g., a hashed BLE MAC address) in the ownership transfer information.

[0158] In operation 1308, the second electronic device (530) can receive the BLE advertising message broadcast from the IoT device (510) through the BLE scan. In operation 1310, the second electronic device (530) can discover the IoT device (510) to which the ownership will be transferred based on whether the BLE MAC address included in the BLE advertising message matches the BLE MAC address included in the ownership transfer information.

[0159] In operation 1312, the second electronic device (530) may transmit a hashed value of the SN (e.g., hashed SN) included in the ownership transfer information to the IoT device (510). In operation 1314, the IoT device (510) may verify the hashed SN. In one embodiment, the IoT device (510) may obtain the SN by decrypting the hashed SN using a designated hash function, and may determine whether the obtained SN matches the SN of the IoT device (510). If the obtained SN matches the SN of the IoT device (510), the IoT device (510) may determine that the verification of the hashed SN is successful.

[0160] In operation 1316, the IoT device (510) may transmit a verification response message indicating that the verification of the hashed SN has been successful to the second electronic device (530). In operation 1318, the second electronic device (530) may transmit a connection request message for a BLE connection to the IoT device (510). In operation 1320, the IoT device (510) may transmit a connection response message corresponding to the connection request message to the second electronic device (530). In operation 1322, the second electronic device (530) may establish a BLE connection with the IoT device (510). The BLE connection may be used to transfer network connection information from the second electronic device (530) to the IoT device (510).

[0161] Figure 14 is a flowchart illustrating a procedure for processing a transfer of ownership according to one embodiment of the present disclosure. Depending on the embodiments, at least one of the operations described below may be modified, omitted, or executed in a different order. Depending on the embodiments, at least one of the operations described below may be executed by a processor (e.g., processor (220)) of the second electronic device (530).

[0162] Referring to FIG. 14, in operation 1402, the second electronic device (530) (e.g., the processor (220)) may confirm that there is at least one IoT device to which ownership will be transferred. In one embodiment, the second electronic device (530) (e.g., the processor (220)) may transmit an inquiry message (e.g., the inquiry message of operation 1102) to the server (550) to inquire about the existence of the IoT device to be transferred, and may receive a response message (e.g., operation 1104)) from the server (550) indicating that there is at least one IoT device to which ownership will be transferred.

[0163] In operation 1404, the second electronic device (530) (e.g., processor (220)) may receive a user input requesting an ownership transfer. In one embodiment, the second electronic device (530) (e.g., processor (220)) may display an ownership transfer guidance UI (e.g., ownership transfer guidance UI of operation 1106) for receiving an input on whether to execute an ownership transfer, and may receive the user input through the ownership transfer guidance UI.

[0164] In operation 1406, the second electronic device (530) (e.g., processor (220)) may obtain a list of devices to be transferred, including at least one IoT device (e.g., IoT device (510)) to which ownership is to be transferred. In one embodiment, the second electronic device (530) (e.g., processor (220)) may transmit a request message (e.g., request message of operation 1110) to a server (550) for requesting the list of devices to be transferred, and may receive a response message (e.g., response message of operation 1112) including the list of devices to be transferred from the server (550).

[0165] In operation 1408, the second electronic device (530) (e.g., the processor (220)) may obtain ownership transfer information related to at least one IoT device (e.g., the IoT device (510)) to which ownership is to be transferred. In one embodiment, the second electronic device (530) (e.g., the processor (220)) may transmit a request message (e.g., the request message of operation 1114) to the server (550) for requesting ownership transfer information necessary to process the ownership transfer of the IoT device (510), and may receive a response message (e.g., the response message of operation 1116) including the ownership transfer information from the server (550).

[0166] In operation 1410, the second electronic device (530) (e.g., the processor (220)) may establish a D2D connection (e.g., the D2D connection of operation 1118) based on short-range wireless communication with the IoT device (510) based on the ownership transfer information. In operation 1412, the second electronic device (530) (e.g., the processor (220)) may transmit network connection information (e.g., the network connection information of operation 1120) required for the IoT device (510) to connect to the server (550) to the IoT device (510) through the D2D connection, thereby allowing the IoT device (510) to connect to the server (550) through the network connection information. In one embodiment, the second electronic device (530) may notify the IoT device (510) that the ownership of the IoT device (510) has been transferred from the first user to the second user by transmitting the network connection information to the IoT device (510).

[0167] FIG. 15a and FIG. 15b illustrate a UI including a QR code for a transfer of ownership request according to one embodiment of the present disclosure.

[0168] Referring to FIG. 15A, the first electronic device (520) may display an execution screen (1502) of a client application for IoT setup (e.g., an application for an installer). The execution screen (1502) may include a device information object (1504) of at least one IoT device (e.g., an IoT device (510)). In one embodiment, the device information object (1504) may include a guidance phrase for registering the IoT device (510) (e.g., “The washing machine delivery is complete. Please move near the device to register it”). The first electronic device (520) may perform an onboarding procedure for registering the IoT device (510) with a server based on a user input through the device information object (1504).

[0169] Referring to FIG. 15B, the first electronic device (520) may display a QR code (1512) for transferring ownership of the IoT device (510) and a list of devices to which ownership will be transferred (1514). In one embodiment, the first electronic device (520) may display the QR code (1512) based on a user input requesting ownership transfer. The QR code (1512) may include ownership information (e.g., an ownership token and / or an owner ID) of the IoT device (510) received by the second electronic device (520) from the server (550). The QR code may include information for causing an external electronic device (e.g., the second electronic device (530)) that scans the QR code to install a client application for an IoT control service and / or perform an operation (e.g., operation 914) for transferring ownership of the IoT device (510) through the client application.

[0170] FIGS. 16A, 16B, and 16C illustrate a UI for transmitting an ownership transfer request according to one embodiment of the present disclosure.

[0171] Referring to FIG. 16A, the first electronic device (520) may display an execution screen (1602) of a client application for IoT setup (e.g., an application for an installer). The execution screen (1602) may include an input object (1604) for requesting execution of ownership transfer of at least one IoT device (e.g., an IoT device (510)). Based on a user input (e.g., a touch) to the input object (1604), the first electronic device (520) may display an ownership transfer screen (1612) of FIG. 16B.

[0172] Referring to FIG. 16b, the ownership transfer screen (1612) displayed by the first electronic device (520) may include a first input object (1614) for selecting display of a QR code, a second input object (1614) for selecting transmission of an ownership transfer request to an external electronic device (e.g., a second electronic device (530)), and / or a third input object (1618) for selecting link sharing to enable the external electronic device (e.g., the second electronic device (530)) to perform the ownership transfer.

[0173] In one embodiment, the first electronic device (520) may display the QR code (1512) of FIG. 15B based on a user input (e.g., a touch) to the first input object (1614). In one embodiment, the first electronic device (520) may directly transmit an ownership transfer request message to an external electronic device (e.g., a second electronic device (530)) associated with a user (e.g., a second user) to whom ownership is to be transferred, or may transmit the message via a server (550), based on a user input (e.g., a touch) to the second input object (1616). In one embodiment, the ownership transfer request message may be transmitted to the second electronic device (530) via an application push notification based on the user account of the second user. In one embodiment, the ownership transfer request message may be transmitted to the second electronic device (530) via an email based on the email address of the second user.

[0174] In one embodiment, the first electronic device (520) may generate a link to cause an external electronic device (e.g., a second electronic device (530)) to perform a transfer of ownership based on a user input (e.g., a touch) to the third input object (1616).

[0175] Referring to FIG. 16C, the first electronic device (520) may display an input object (1622) for a request for transfer of ownership based on a user input (e.g., a touch) to the second input object (1616). The input object (1622) may receive a user account or email address of a second user to whom ownership will be transferred. In one embodiment, the first electronic device (520) may directly transmit an ownership transfer request message to the second electronic device (530) using the user account or email address input through the input object (1622). In one embodiment, the first electronic device (520) may transmit the user account or email address input through the input object (1622) to the server (550), thereby causing the server (550) to transmit an ownership transfer request message to the second electronic device (530).

[0176] FIG. 17a and FIG. 17b illustrate a UI including a process for transferring ownership according to one embodiment of the present disclosure.

[0177] Referring to FIG. 17A, the second electronic device (530) may display an ownership transfer guidance UI (1702) notifying that a transfer of ownership has been requested through a client application for an IoT control service. In one embodiment, the ownership transfer guidance UI (1702) may include a phrase guiding the ownership transfer, for example, "Abc has transferred ownership. You must accept to receive the transfer of ownership." In one embodiment, the ownership transfer guidance UI (1702) may include a list of devices to be transferred. The second electronic device (530) may receive a user input (1704) accepting the ownership transfer through the ownership transfer guidance UI (1702).

[0178] Referring to FIG. 17B, the second electronic device (530) may display an ownership transfer processing UI (1712) showing the process of the ownership transfer based on receiving a user input (1704) accepting the ownership transfer. In one embodiment, the ownership transfer processing UI (1712) may include processing status objects representing the process of the ownership transfer of one or more IoT devices previously registered by the first electronic device (520). In one embodiment, each of the processing status objects may include a device name (e.g., “_devicename0”, “_devicename1”, “_devicename2”, or “_devicename3”), an image, and / or a phrase indicating the processing status (e.g., “updated”, “update failed”, “updating”, or “waiting”). Here, the updated processing status may indicate that the ownership of the IoT device (e.g., “_devicename1”) has been transferred from the first user to the second user.

[0179] A second electronic device (530) according to one embodiment may include a memory (230) for storing instructions, a communication circuit (292), and at least one processor (220) operatively connected to the memory and the communication circuit. The instructions, when executed by the at least one processor, may cause the second electronic device to receive, through the communication circuit, an ownership transfer request message requesting to transfer ownership of an IoT (internet over things) device registered in a server (550) from a first user to a second user. The instructions, when executed by the at least one processor, may cause the second electronic device to receive a user input consenting to the ownership transfer of the IoT device. The instructions, when executed by the at least one processor, may cause the second electronic device to transmit, to the server through the communication circuit, a request message requesting the ownership transfer of the IoT device based on the user input. The above instructions, when executed by the at least one processor, may cause the second electronic device to receive, from the server via the communication circuit, ownership transfer information necessary to process ownership transfer of the IoT device after transmitting the request message. The instructions, when executed by the at least one processor, may cause the second electronic device to establish a device-to-device (D2D) connection with the IoT device via the communication circuit based on the ownership transfer information. The instructions, when executed by the at least one processor, may cause the second electronic device to transmit, to the IoT device via the D2D connection, network connection information for use in connecting the IoT device to the server.

[0180] In one embodiment, the ownership transfer request message may be received from a first electronic device associated with the first user or from the server.

[0181] In one embodiment, the ownership transfer request message may include at least one of a list of devices to be transferred, including the IoT device, or ownership information indicating a right to transfer ownership of the IoT device from the first user.

[0182] In one embodiment, the request message may include at least one of the list of devices to be transferred, or the ownership information.

[0183] In one embodiment, the ownership information may include an ownership token indicating a right to transfer ownership of the IoT device from the first user and / or an owner identifier (ID) indicating the first user.

[0184] In one embodiment, the ownership transfer information may include at least one of identification information of the first electronic device associated with the first user, identification information of the IoT device, SSID of an access point (AP) associated with the IoT device, owner ID of the IoT device, or MAC (media access control) address information of the IoT device.

[0185] In one embodiment, the commands may cause the second electronic device to scan a QR (quick response) code including information requesting transfer of ownership of a first IoT device registered in the server from the first user to the second user through a camera (280) of the second electronic device, transmit a first request message to the server for requesting transfer of ownership of the first IoT device based on scanning the QR code, receive first ownership transfer information necessary to process the transfer of ownership of the IoT device from the server after transmitting the first request message, establish a first D2D connection with the first IoT device based on the first ownership transfer information, and transmit first network connection information to the first IoT device through the first D2D connection, the first IoT device being used to connect to the server.

[0186] In one embodiment, the instructions may cause the second electronic device to transmit an inquiry message to the server for inquiring about the existence of an IoT device to which ownership is to be transferred, receive a response message from the server indicating that at least one IoT device to which ownership is to be transferred exists, receive a second user input requesting to process ownership transfer based on receiving the response message, transmit a first request message to the server for requesting a list of devices to be transferred based on the second user input, receive a list of devices to be transferred including a second IoT device from the server based on the first request message, transmit a second request message to the server for requesting second ownership transfer information related to the second IoT device, receive the second ownership transfer information from the server based on the second request message, establish a second D2D connection with the second IoT device based on the second ownership transfer information, and transmit second network connection information to the second IoT device via the second D2D connection for use in connecting the second IoT device to the server.

[0187] A first electronic device (520) according to one embodiment of the present disclosure may include a memory (230) for storing instructions, a communication circuit (292), and at least one processor (220) operatively connected to the memory and the communication circuit. The instructions, when executed by the at least one processor, may cause the first electronic device to receive a user input requesting transfer of ownership of a first IoT device among one or more IoT devices registered with a server (550) for a first user to a second user. The instructions, when executed by the at least one processor, may cause the first electronic device to transmit an ownership transfer notification message including user information of the second user to the server via the communication circuit. The instructions, when executed by the at least one processor, may cause the first electronic device to transmit an ownership transfer request message including ownership information indicating a right to transfer ownership of the first IoT device from the first user to a second electronic device (530) associated with the second user via the communication circuit.

[0188] In one embodiment, the commands may cause the first electronic device to receive a user input requesting to transfer ownership of a second IoT device among one or more IoT devices registered with the server (550) for the first user to the second user, receive ownership information indicating a right to transfer ownership of the second IoT device from the first user from the server through the communication circuit, and display a QR (quick response) code including information requesting to transfer ownership of the second IoT device from the first user to the second user based on the ownership information through the display module (260).

[0189] A method by a second electronic device (530) according to one embodiment of the present disclosure may include receiving an ownership transfer request message requesting to transfer ownership of an IoT (Internet over Things) device registered in a server (550) from a first user to a second user. The method may include receiving a user input consenting to the ownership transfer of the IoT device. The method may include transmitting a request message to the server for requesting the ownership transfer of the IoT device based on the user input. The method may include receiving ownership transfer information necessary to process the ownership transfer of the IoT device from the server after transmitting the request message. The method may include establishing a device-to-device (D2D) connection with the IoT device based on the ownership transfer information. The method may include transmitting network connection information to be used by the IoT device to connect to the server through the D2D connection.

[0190] In one embodiment, the ownership transfer request message may be received from a first electronic device associated with the first user or from the server.

[0191] In one embodiment, the ownership transfer request message may include at least one of a list of devices to be transferred, including the IoT device, or ownership information indicating a right to transfer ownership of the IoT device from the first user.

[0192] In one embodiment, the request message may include at least one of the list of devices to be transferred, or the ownership information.

[0193] In one embodiment, the ownership information may include an ownership token indicating a right to transfer ownership of the IoT device from the first user and / or an owner identifier (ID) indicating the first user.

[0194] In one embodiment, the ownership transfer information may include at least one of identification information of the first electronic device associated with the first user, identification information of the IoT device, SSID of an access point (AP) associated with the IoT device, owner ID of the IoT device, or MAC (media access control) address information of the IoT device.

[0195] In one embodiment, the method may include an operation of scanning a QR (quick response) code including information requesting to transfer ownership of a first IoT device registered in the server from the first user to the second user through a camera (280) of the second electronic device, an operation of transmitting a first request message to the server for requesting transfer of ownership of the first IoT device based on the scanning of the QR code, an operation of receiving first ownership transfer information necessary to process the transfer of ownership of the IoT device from the server after transmitting the first request message, an operation of establishing a first D2D connection with the first IoT device based on the first ownership transfer information, and an operation of transmitting first network connection information to the first IoT device through the first D2D connection, the first IoT device being used to connect to the server.

[0196] In one embodiment, the method may include transmitting an inquiry message to the server for inquiring about the existence of an IoT device to which ownership is to be transferred, receiving a response message from the server indicating that at least one IoT device to which ownership is to be transferred exists, receiving a second user input requesting to process ownership transfer based on receiving the response message, transmitting a first request message to the server for requesting a list of devices to be transferred based on the second user input, receiving a list of devices to be transferred including a second IoT device from the server based on the first request message, transmitting a second request message to the server for requesting second ownership transfer information related to the second IoT device, receiving the second ownership transfer information from the server based on the second request message, establishing a second D2D connection with the second IoT device based on the second ownership transfer information, and transmitting second network connection information to the second IoT device via the second D2D connection, the second IoT device being used to connect to the server.

[0197] A method by a first electronic device (520) according to one embodiment of the present disclosure may include receiving a user input requesting that ownership of a first IoT device among one or more IoT devices registered with a server (550) for a first user be transferred to a second user. The method may include transmitting an ownership transfer notification message including user information of the second user to the server. The method may include transmitting an ownership transfer request message including ownership information indicating a right to transfer ownership of the first IoT device from the first user to a second electronic device (530) associated with the second user.

[0198] In one embodiment, the method may include receiving a user input requesting that ownership of a second IoT device among one or more IoT devices registered with the server (550) for the first user be transferred to the second user, receiving ownership information from the server indicating a right to transfer ownership of the second IoT device from the first user, and displaying a QR (quick response) code including information requesting that ownership of the second IoT device be transferred from the first user to the second user based on the ownership information, through the display module (260).

[0199] A non-transitory computer-readable storage medium storing one or more programs according to one embodiment of the present disclosure may include instructions configured to cause the second electronic device to: receive an ownership transfer request message requesting to transfer ownership of an IoT (internet over things) device registered in a server from a first user to a second user, receive a user input agreeing to the ownership transfer of the IoT device, transmit a request message to the server for requesting the ownership transfer of the IoT device based on the user input, receive ownership transfer information necessary to process the ownership transfer of the IoT device after transmitting the request message, establish a device-to-device (D2D) connection with the IoT device based on the ownership transfer information, and transmit network connection information to the IoT device to be used for connecting the IoT device to the server through the D2D connection.

[0200] A non-transitory computer-readable storage medium storing one or more programs according to one embodiment of the present disclosure may include instructions configured to cause the first electronic device, when executed by at least one processor of the first electronic device, to: receive a user input requesting to transfer ownership of a first IoT device among one or more IoT devices registered to a server for a first user to a second user, transmit an ownership transfer notification message including user information of the second user to the server, and transmit an ownership transfer request message including ownership information indicating a right to transfer ownership of the first IoT device from the first user to a second electronic device associated with the second user.

[0201] While the present disclosure has been described and illustrated with reference to various exemplary embodiments, it should be understood that the various exemplary embodiments are illustrative and not limiting. Those skilled in the art will further appreciate that various changes in form and detail may be made without departing from the true spirit and scope of the present disclosure, including the appended claims and their equivalents. Furthermore, it should be understood that any of the embodiment(s) described herein can be used in conjunction with any other embodiment(s) described herein.

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

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

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

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

[0206] According to one embodiment, the method according to various embodiments disclosed in this document may be provided as a computer program product. The computer program product may be traded between sellers and buyers as a product. The computer program product may be distributed in the form of a device-readable storage medium (e.g., compact disc read-only memory (CD-ROM)) or may be provided through an application store (e.g., Play Store). TM ) or directly between two user devices (e.g., smart phones), online distribution (e.g., downloading or uploading). In the case of online distribution, at least a portion of the computer program product may be at least temporarily stored or temporarily created in a machine-readable storage medium, such as the memory of a manufacturer's server, an application store's server, or an intermediary server.

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

Claims

1. In the second electronic device (530), Memory (230) for storing commands; Communication circuit (292); and At least one processor (220) operatively connected to the memory and the communication circuit, wherein the instructions, when individually or collectively executed by the at least one processor, cause the second electronic device to: A first request message requesting to transfer ownership of an IoT (internet over things) device registered in a server (550) from a first user to a second user is received through the communication circuit, Receiving user input consenting to the transfer of ownership of the IoT device; Based on the user input, a second request message for requesting transfer of ownership of the IoT device is transmitted to the server through the communication circuit, After transmitting the second request message, ownership transfer information required to process the transfer of ownership of the IoT device is received from the server through the communication circuit, Establishing a D2D (device-to-device) connection with the IoT device through the communication circuit based on the above ownership transfer information, A second electronic device that transmits network connection information to be used for connecting the IoT device to the server through the D2D connection.

2. In the first paragraph, the first request message, A second electronic device, which is received from the first electronic device or the server associated with the first user.

3. In the first or second paragraph, the first request message, A second electronic device comprising at least one of a list of devices to be transferred, including the IoT device, or ownership information indicating a right to transfer ownership of the IoT device from the first user.

4. In the third paragraph, the second request message A second electronic device comprising at least one of the list of devices to be transferred, or the ownership information.

5. In paragraph 4, the ownership information is: A second electronic device comprising an ownership token representing a right to transfer ownership of the IoT device from the first user and / or an owner ID (identifier) ​​representing the first user.

6. In any one of paragraphs 1 to 5, the ownership transfer information is: A second electronic device comprising at least one of identification information of a first electronic device related to the first user, identification information of the IoT device, SSID of an access point (AP) related to the IoT device, owner ID of the IoT device, or MAC (media access control) address information of the IoT device.

7. In any one of paragraphs 1 to 6, the instructions, when individually or collectively executed by the at least one processor, cause the second electronic device to: Scanning a QR (quick response) code containing information requesting to transfer ownership of the first IoT device registered on the server from the first user to the second user through the camera (280) of the second electronic device, Based on scanning the QR code, a first request message for requesting transfer of ownership of the first IoT device is transmitted to the server, After transmitting the first request message, the first ownership transfer information required to process the transfer of ownership of the IoT device is received from the server, Establishing a first D2D connection with the first IoT device based on the first ownership transfer information; A second electronic device that transmits first network connection information to the first IoT device through the first D2D connection, the first IoT device being used to connect to the server.

8. In any one of paragraphs 1 to 7, the instructions, when individually or collectively executed by the at least one processor, cause the second electronic device to: Sending an inquiry message to the server to inquire about the existence of the IoT device to which ownership is to be transferred; Receive a response message from the server indicating that there is at least one IoT device to which ownership is to be transferred; Receive a second user input requesting to process the transfer of ownership based on receiving the above response message; Based on the second user input, a first request message is transmitted to the server to request a list of devices to be transferred, Receive a list of devices to be transferred, including a second IoT device, from the server based on the first request message; Transmitting a second request message to the server to request second ownership transfer information related to the second IoT device; Receive the second ownership transfer information from the server based on the second request message; Establishing a second D2D connection with the second IoT device based on the second ownership transfer information; A second electronic device that transmits second network connection information to the second IoT device via the second D2D connection, the second IoT device being used to connect to the server.

9. In the first electronic device (520), Memory (230) for storing commands; Communication circuit (292); and At least one processor (220) operatively connected to the memory and the communication circuit, wherein the instructions, when individually or collectively executed by the at least one processor, cause the first electronic device to: Receiving a user input requesting to transfer ownership of a first IoT device among one or more IoT devices registered with the server (550) for a first user to a second user; Transmitting a transfer of ownership notification message including the user information of the second user to the server through the communication circuit; A first electronic device that transmits an ownership transfer request message including ownership information indicating a right to transfer ownership of the first IoT device from the first user to a second electronic device (530) associated with the second user through the communication circuit.

10. In the 9th paragraph, the instructions, when individually or collectively executed by the at least one processor, cause the first electronic device to: Receiving a user input requesting to transfer ownership of a second IoT device among one or more IoT devices registered with the server (550) for the first user to the second user; Receive ownership information indicating a right to transfer ownership of the second IoT device from the first user from the server through the communication circuit; A first electronic device that displays a QR code including information requesting transfer of ownership of the second IoT device from the first user to the second user through a display module (260) based on the ownership information.

11. In the method by the second electronic device (530), An operation (802) of receiving a first request message requesting to transfer ownership of an IoT (internet over things) device registered in a server (550) from a first user to a second user; An action (806) of receiving user input consenting to transfer of ownership of the IoT device; An operation (808) of transmitting a second request message to the server to request transfer of ownership of the IoT device based on the user input; An operation (810) of receiving ownership transfer information required to process ownership transfer of the IoT device from the server after transmitting the second request message; An operation (812) of establishing a D2D (device-to-device) connection with the IoT device based on the above ownership transfer information; and A method comprising an operation (814) of transmitting network connection information to be used for connecting the IoT device to the server through the D2D connection.

12. In paragraph 11, the first request message, A method, wherein the method is received from a first electronic device or the server associated with the first user.

13. In paragraph 11 or 12, the first request message, At least one of a list of devices to be transferred including the IoT device, or ownership information indicating a right to transfer ownership of the IoT device from the first user, The second request message includes at least one of the list of devices to be transferred or the ownership information, A method wherein the ownership information includes an ownership token indicating a right to transfer ownership of the IoT device from the first user and / or an owner ID (identifier) ​​indicating the first user.

14. In any one of paragraphs 11 to 13, the ownership transfer information is: A method comprising at least one of identification information of a first electronic device associated with the first user, identification information of the IoT device, SSID of an access point (AP) associated with the IoT device, owner ID of the IoT device, or MAC (media access control) address information of the IoT device.

15. In the method by the first electronic device (520), An action of receiving a user input requesting to transfer ownership of a first IoT device among one or more IoT devices registered with the server (550) for a first user to a second user; An action of transmitting an ownership transfer notification message including the user information of the second user to the server; and A method comprising the action of transmitting an ownership transfer request message including ownership information indicating a right to transfer ownership of the first IoT device from the first user to a second electronic device (530) associated with the second user.

Images