Electronic device and control method therefor

Abstract

This electronic device included in an Internet of Things (IoT) network comprises a communication interface and at least one processor, wherein the at least one processor: determines a target IoT apparatus to share a control right among one or more IoT apparatuses included in the IoT network when receiving a user input for sharing the control right for the IoT network; broadcasts a communication packet for sharing the control right via the communication interface; receives contact information from a terminal device in response to the communication packet via the communication interface; and shares the control right with the terminal device corresponding to the contact information when the received contact information is included in a pre-stored contact list.

Description

Electronic device and method of controlling the same

[0001] The present disclosure relates to an electronic device and a control method thereof, and more particularly, to an electronic device and a control method thereof that share control rights for an IoT (Internet of Things) device using identification information.

[0002] A variety of IoT devices are being used, including TVs, air conditioners, air purifiers, lighting, and AI speakers. Users can check the status of these devices and control them using smartphone applications.

[0003] A TV is typically located in the center of a home's living room and may include a display. When turned off, the TV operates in a low-power mode and can perform specific functions.

[0004] If you want to control IoT devices within an IoT network, you can use the terminal devices of a pre-registered user. IoT networks can control IoT devices using devices such as Access Points (APs). Pre-registered users' terminal devices can control IoT devices using APs.

[0005] Unregistered users (visitors) must access the AP or perform a new connection operation to control IoT devices. Registered users may experience the inconvenience of having to provide instructions to unregistered users (visitors) on how to control IoT devices.

[0006] If you want to share (or grant) control rights (control rights) for a specific IoT device to a visitor, the preparatory process of connecting to the IoT network may be inconvenient for both users (registered users and visitors).

[0007] For example, if you're hosting a meeting or party at a specific location, you can share a wireless Wi-Fi environment with visitors' devices and give them control over IoT devices connected to that Wi-Fi. Visitors who are granted temporary control over IoT devices will then be able to control them for a set period of time.

[0008] Once granted control, the visitor's device can easily share images and videos to the TV and adjust the air conditioner temperature. The visitor's device can also change the color of the lighting and play specific music on the AI ​​speaker.

[0009] However, to grant visitors control over their IoT devices, they must be provided with information such as the AP name, password, and QR code. Furthermore, visitors must go through a complex process to directly connect to the IoT network.

[0010] The present disclosure is designed to improve the above-described problems, and the purpose of the present disclosure is to provide an electronic device and a control method thereof that share control over an IoT device using contact information of a visitor terminal device.

[0011] According to one embodiment, an electronic device includes a communication interface, at least one processor, and the at least one processor identifies a target device among at least one external device connected to the electronic device based on occurrence of an event in which control information for controlling a target device is provided, broadcasts a packet related to provision of the control information through the communication interface, receives identification information through the communication interface from a device responding to the packet, and provides the control information for controlling the target device to the device when the identification information received from the device is included in pre-stored identification information.

[0012] The above event is a user input requesting the control information, and the at least one processor can broadcast the packet using BLE (Bluetooth Low Energy) communication through the communication interface.

[0013] The at least one processor may transmit AP (Access Point) information to which the electronic device is connected through the communication interface to a device that responded to the packet, if the contact information obtained through the received identification information is included in the pre-stored identification information.

[0014] The at least one processor may control a UI (User Interface) provided to confirm the connection authority of the device responding to the packet if the contact information obtained through the received identification information is not included in the pre-stored identification information.

[0015] The at least one processor may receive account information from a device that responded to the packet through the communication interface, and, if the received account information is included in a pre-stored account list, provide the control information to the device that responded to the packet based on the account information.

[0016] The at least one processor may generate temporary account information if the received account information is not included in a list of previously stored accounts, and provide the control information to a device that responded to the packet based on the temporary account information.

[0017] The at least one processor may generate the temporary account information based on contact information obtained through the identification information received from the device responding to the packet.

[0018] The at least one processor may update the account information received from the device to add the control information for the target device to the account information.

[0019] An electronic device in which at least one processor is controlled to maintain a state for providing the control information to a device that responded to the packet for a preset period of time based on the event in which a user input for providing the control information is received, and in which the control information is not provided to the device that responded to the packet when the preset period of time has elapsed.

[0020] The at least one processor can obtain a signal strength corresponding to each of the at least one external devices connected to the electronic device, and identify an external device among the at least one external device whose signal strength is greater than or equal to a threshold value as the target device.

[0021] According to one embodiment, a method for controlling an electronic device includes the steps of: identifying a target device among at least one external device connected to the electronic device based on an occurrence of an event in which control information for controlling a target device is provided; broadcasting a packet related to provision of the control information; receiving identification information from a device responding to the packet; and providing the control information for controlling the target device to the device when the identification information received from the device is included in pre-stored identification information.

[0022] The above event is a user input requesting the above control information, and the step of broadcasting the packet can broadcast the packet using BLE (Bluetooth Low Energy) communication.

[0023] The above control method may further include a step of transmitting AP (Access Point) information to which the electronic device is connected to a device that responded to the packet, if the contact information obtained through the received identification information is included in the pre-stored identification information.

[0024] The above control method may further include a step of controlling a UI (User Interface) provided to confirm the connection authority of the device responding to the packet, if the contact information obtained through the received identification information is not included in the pre-stored identification information.

[0025] The control method may further include a step of receiving account information from a device responding to the packet, and a step of providing the control information to the device responding to the packet based on the account information if the received account information is included in a pre-stored account list.

[0026] FIG. 1 is a block diagram illustrating an electronic device according to an embodiment of the present disclosure.

[0027] Figure 2 is a block diagram for explaining the specific configuration of the electronic device of Figure 1.

[0028] FIG. 3 is a diagram for explaining an IoT system according to one embodiment.

[0029] FIG. 4 is a diagram for explaining an IoT system according to one embodiment.

[0030] FIG. 5 is a diagram for explaining an IoT system according to one embodiment.

[0031] Figure 6 is a diagram for explaining an IoT system according to one embodiment.

[0032] FIG. 7 is a flowchart illustrating an operation for starting IoT control sharing according to one embodiment.

[0033] FIG. 8 is a flowchart illustrating an operation for terminating IoT control sharing according to one embodiment.

[0034] Figure 9 is a flowchart for explaining IoT control sharing according to various embodiments.

[0035] FIG. 10 is a diagram illustrating a UI for starting IoT control sharing according to one embodiment.

[0036] FIG. 11 is a diagram for explaining a notification related to IoT control sharing according to one embodiment.

[0037] FIG. 12 is a drawing for explaining an operation of detecting a visitor according to one embodiment.

[0038] FIG. 13 is a diagram for explaining an operation of selecting a target IoT device according to one embodiment.

[0039] FIG. 14 is a diagram for explaining an operation of selecting target IoT devices by group according to one embodiment.

[0040] FIG. 15 is a drawing for explaining an operation of selecting a visitor according to one embodiment.

[0041] FIG. 16 is a diagram for explaining an operation of selecting a sharing mode according to one embodiment.

[0042] FIG. 17 is a diagram for explaining an operation of providing an invitation notification through a text message service according to one embodiment.

[0043] FIG. 18 is a diagram for explaining an operation of providing an invitation notification according to one embodiment.

[0044] FIG. 19 is a diagram for explaining an operation of accepting an invitation notification through an NFC function according to one embodiment.

[0045] FIG. 20 is a diagram illustrating an operation of accepting an invitation notification via a QR code according to one embodiment.

[0046] FIG. 21 is a diagram illustrating an operation of accepting an invitation notification through a watermark according to one embodiment.

[0047] FIG. 22 is a drawing for explaining a contact confirmation operation according to one embodiment.

[0048] FIG. 23 is a drawing for explaining a screen displayed when contact verification fails according to one embodiment.

[0049] FIG. 24 is a drawing for explaining a screen displayed when contact verification fails according to one embodiment.

[0050] FIG. 25 is a drawing for explaining a screen displayed when contact verification fails according to one embodiment.

[0051] FIG. 26 is a diagram illustrating an operation of adding a target IoT device to visitor account information according to one embodiment.

[0052] FIG. 27 is a drawing for explaining a screen displayed when account verification fails according to one embodiment.

[0053] FIG. 28 is a diagram for explaining an operation of sharing image content according to one embodiment.

[0054] FIG. 29 is a diagram for explaining an operation of sharing audio content according to one embodiment.

[0055] FIG. 30 is a drawing for explaining an operation of sharing game content according to one embodiment.

[0056] FIG. 31 is a drawing for explaining an operation of deleting control according to one embodiment.

[0057] FIG. 32 is a drawing for explaining a screen related to termination of IoT control sharing according to one embodiment.

[0058] FIG. 33 is a flowchart illustrating an operation in which AP information is included in a BLE packet according to one embodiment.

[0059] FIG. 34 is a flowchart illustrating an operation of performing contact verification and account verification in an electronic device according to one embodiment.

[0060] FIG. 35 is a flowchart illustrating an operation in which contact verification is performed on a user terminal device and account verification is performed on an electronic device according to one embodiment.

[0061] FIG. 36 is a flowchart illustrating operations performed by a server for contact verification and account verification according to one embodiment.

[0062] FIG. 37 is a flowchart illustrating an operation of performing IoT control sharing using only contacts according to one embodiment.

[0063] Figure 38 is a flowchart for explaining a control method of an electronic device according to one embodiment.

[0064] FIG. 39 is a drawing for explaining a screen related to IoT control sharing according to one embodiment.

[0065] Hereinafter, the present disclosure will be described in detail with reference to the attached drawings.

[0066] The terms used in the embodiments of this disclosure have been selected from widely used, current terms, taking into account the functions of this disclosure. However, these terms may vary depending on the intentions of those skilled in the art, precedents, the emergence of new technologies, etc. Furthermore, in certain cases, terms may be arbitrarily selected by the applicant, and in such cases, their meanings will be described in detail in the description of the relevant disclosure. Therefore, the terms used in this disclosure should not be defined simply as names of terms, but rather based on the meanings of the terms and the overall content of this disclosure.

[0067] In this specification, expressions such as “has,” “can have,” “includes,” or “may include” indicate the presence of a feature (e.g., a number, function, operation, or component such as a part), and do not exclude the presence of additional features.

[0068] The expression "at least one of A and / or B" should be understood to mean either "A" or "B" or "A and B".

[0069] As used herein, the expressions “first,” “second,” “first,” or “second,” etc., may describe various components, regardless of order and / or importance, and are only used to distinguish one component from another, but do not limit the components.

[0070] When it is said that a component (e.g., a first component) is “(operatively or communicatively) coupled with / to” or “connected to” another component (e.g., a second component), it should be understood that the component may be directly coupled to the other component, or may be connected through another component (e.g., a third component).

[0071] Singular expressions include plural expressions unless the context clearly dictates otherwise. In this application, terms such as "comprise" or "consist of" are intended to indicate the presence of a feature, number, step, operation, component, part, or combination thereof described in the specification, but should be understood not to preclude the presence or addition of one or more other features, numbers, steps, operations, components, parts, or combinations thereof.

[0072] In the present disclosure, a "module" or "part" performs at least one function or operation and may be implemented as hardware or software, or as a combination of hardware and software. Furthermore, multiple "modules" or multiple "parts" may be integrated into at least one module and implemented as at least one processor (not shown), excluding any "modules" or "parts" that need to be implemented as specific hardware.

[0073] In this specification, the term user may refer to a person using an electronic device or a device using an electronic device (e.g., an artificial intelligence electronic device).

[0074] The present disclosure is designed to improve the aforementioned problems, and the purpose of the disclosure is to provide an electronic device and a control method thereof that share control over an IoT device using a contact information of a visitor terminal device.

[0075] An electronic device included in an IoT (Internet of Things) network includes a communication interface and at least one processor, wherein the at least one processor, when receiving a user input for sharing control over the IoT network, determines a target IoT device to share control among at least one IoT device included in the IoT network, broadcasts a communication packet for sharing control through the communication interface, receives a contact from a terminal device in response to the communication packet through the communication interface, and shares control with the terminal device corresponding to the contact when the received contact is included in a pre-stored contact list.

[0076] An embodiment of the present disclosure will be described in more detail with reference to the attached drawings below.

[0077] FIG. 1 is a block diagram illustrating an electronic device (100) according to one embodiment of the present disclosure.

[0078] Referring to FIG. 1, the electronic device (100) may include at least one of a memory (110), at least one processor (120), a communication interface (130), and a display (140).

[0079] The memory (110) can store various information used in the electronic device (100). The memory (110) can store information related to the IoT network (1000). The memory (110) can store information on IoT devices included in the IoT network (1000). The memory (110) can store AP (Access Point) information corresponding to the IoT network (1000). The memory (110) can store information received from a visitor terminal device (200), a server (300), a user terminal device (400), an AP device (500), etc.

[0080] The communication interface (130) can be connected to a visitor terminal device (200), a server (300), a user terminal device (400), an AP device (500), etc. The communication interface (130) can include at least one communication module depending on the communication method.

[0081] The display (140) can display various UIs (User Interfaces) or screens, etc.

[0082] An IoT (Internet of Things) network (1000) may include at least one IoT device. At least one IoT device may include an electronic device (100).

[0083] When a user input for providing control information of an external device connected to an electronic device (100) is received, at least one processor (120) identifies a control target device among at least one external device connected to the electronic device (100), broadcasts a packet corresponding to the provision of control information through a communication interface (130), receives identification information from a device that responds to the packet through the communication interface (130), and, when the received identification information is included in the pre-stored identification information, provides control information to the device corresponding to the identification information.

[0084] An external device connected to an electronic device (100) may represent a device included in an IoT network (1000). The IoT network (1000) may include at least one device, such as an electronic device (100) and an external device.

[0085] Control information of an external device connected to an electronic device (100) may include information for controlling a device included in an IoT network (1000). The control information may include at least one of a control target, a control command, a control signal, a control code, a control type, and a control authority for controlling a specific device.

[0086] User input for providing control information may be described as user input for sharing control.

[0087] The device to be controlled may be described as a target IoT device.

[0088] A packet corresponding to the provision of control information may be described as a communication packet for sharing control rights.

[0089] The device that responded to the packet may be described as a terminal device.

[0090] Identification information may represent information used to identify a specific entity (e.g., a user, a device, etc.). Identification information may include contact information.

[0091] An action providing control information may include an action providing control authority.

[0092] When a user input for sharing control over an IoT network (1000) is received, at least one processor (120) determines a target IoT device to share control with among at least one IoT device included in the IoT network (1000), broadcasts a communication packet for sharing control through a communication interface (130), receives contact information from a terminal device (200) in response to the communication packet through the communication interface (130), and when the received contact information is included in a pre-stored contact list, shares control with a terminal device (200) corresponding to the contact information.

[0093] At least one processor (120) can receive (or acquire) user input for sharing control over IoT devices included in the IoT network (1000).

[0094] The act of sharing control may refer to an act of temporarily granting control to an unregistered user (visitor). When a preset event is identified, at least one processor (120) may control the electronic device (100) and the IoT network (1000) in a control sharing mode. The control sharing mode may be described as an IoT sharing mode (IoT control sharing), a party mode, a conference mode, a control sharing mode, a smart sharing mode, etc.

[0095] User input may be input to initiate IoT control sharing. According to various embodiments, even if no user input is received, at least one processor (120) may initiate IoT control sharing when a preset event is identified.

[0096] When the electronic device (100) operates in IoT control sharing, at least one processor (120) can determine a target IoT device. The target IoT device may refer to a device with which control is to be shared. The target IoT device may refer to a device with which control is to be shared among at least one IoT device included in the IoT network (1000).

[0097] The operation of determining a target IoT device is described in FIGS. 14 and 15.

[0098] Control sharing can be done on a per-function basis. For example, control over some of the multiple functions provided by a single IoT device may be shared. A related explanation is provided in Figure 16.

[0099] At least one processor (120) may generate a communication packet for sharing control rights. The communication packet may include a notification message for sharing control rights for an IoT device. The communication packet may be described as an invitation notification. The communication packet may be a Bluetooth Low Energy (BLE) packet. The communication packet may be described as a request packet.

[0100] At least one processor (120) can broadcast a packet (or communication packet) using BLE (Bluetooth Low Energy) communication through a communication interface (130).

[0101] A communication packet may include a control command requesting that a device receiving the communication packet transmit identification information. The device receiving the communication packet may generate a response packet containing its own identification information.

[0102] A visitor terminal (200) may receive a broadcasted communication packet. The visitor terminal (200) may include a communication interface. The visitor terminal (200) may analyze the received communication packet to recognize that the electronic device (100) is attempting to share control. The visitor terminal (200) may generate a response packet containing identification information in response to the communication packet.

[0103] Identification information may include various information to distinguish the visitor terminal device (200) from other devices.

[0104] For example, identification information may include at least one of the device's contact information, device account information, and device model number. Contact information may be described as "contact" or "contact data," and account information may be described as "account" or "account data." The model number may be described as a unique terminal number or a unique terminal serial number.

[0105] Upon receiving a response packet from a visitor terminal device (200), at least one processor (120) may obtain contact information included in the response packet. At least one processor (120) may determine whether it has the authority (or qualification) to share control based on the contact information.

[0106] Based on the comparison result between the previously stored contact list and the contact information of the visitor terminal device (200), at least one processor (120) can determine whether the visitor terminal device (200) has the authority (or qualification) to share control.

[0107] According to one embodiment, a contact verification operation may be performed in an electronic device (100). The electronic device (100) may store a contact list in a memory (110). The electronic device (100) may receive the contact list from a server (300) or a user terminal device (400). The server (300) or the user terminal device (400) may transmit the contact list to the electronic device (100) in response to a request from the electronic device (100).

[0108] According to one embodiment, a contact verification operation may be performed on a user terminal device (400). At least one processor (120) may transmit contact information to the user terminal device (400). The user terminal device (400) may compare the received contact information with a contact list previously stored in the user terminal device (400). The user terminal device (400) may transmit the comparison result to the electronic device (100).

[0109] According to one embodiment, the contact verification operation may be performed on a server (300). The server (300) may be a server connected to an IoT network (1000). The server (300) may be a server that manages accounts related to a service that controls IoT devices.

[0110] For example, the electronic device (100) may transmit contact information to the server (300). The server (300) may compare the received contact information with a contact list corresponding to the electronic device (100). The server (300) may transmit the comparison result to the electronic device (100).

[0111] For example, the electronic device (100) may transmit contact information and account information to the server (300). The server (300) may identify a contact list corresponding to the received account information. The server (300) may compare the identified contact list with the received contact information. The server (300) may transmit the comparison result to the electronic device (100).

[0112] The electronic device (100) can determine whether the visitor terminal device (200) has the authority (or qualification) to connect to the IoT network (1000) based on the comparison result.

[0113] If the contact information of the visitor terminal device (200) is identified as being included in the contact list based on the comparison result, at least one processor (120) may determine that the visitor terminal device (200) has the authority (or qualification) to connect to the IoT network (1000).

[0114] At least one processor (120) can transmit AP (Access Point) information to which the electronic device (100) is connected to the packet to the device that responded to the packet through the communication interface (130), if the contact information obtained through the received identification information is included in the contact information included in the pre-stored identification information.

[0115] At least one processor (120) can obtain AP (Access Point) information corresponding to an IoT network (1000) when the received contact information is included in a pre-stored contact list, and transmit the AP information to a terminal device (200) through a communication interface (130).

[0116] If the received contact information is included in the pre-stored contact list, at least one processor (120) may transmit AP information to the visitor terminal device (200) so that the visitor terminal device (200) is connected to an AP corresponding to the IoT network (1000). The AP may refer to a device used to control an IoT device of the IoT network (1000). The AP may refer to a router, etc. The AP may be described as an AP device (500). A description related thereto is described in FIG. 4.

[0117] According to various embodiments, the AP may be implemented as an IoT device rather than a separate device, such as the AP device (500). For example, an electronic device (100) may perform AP functions. A description related to this is provided in FIG. 5.

[0118] According to various embodiments, IoT devices can communicate with each other without an AP. A related description is provided in Figure 6. While the above description describes obtaining AP information, control can be shared without AP information.

[0119] At least one processor (120) can control to provide a UI (User Interface) corresponding to confirmation of connection authority of a device that responded to the packet, if the contact information obtained through the received identification information is not included in the contact information included in the pre-stored identification information.

[0120] At least one processor (120) may provide a guide UI (User Interface) for confirming connection authority of the terminal device (200) if the received contact information is not included in the pre-stored contact list. A description related to this is provided in FIGS. 23 and 24.

[0121] For example, the electronic device (100) may include a display (140). The electronic device (100) may display a guide UI on the display (140).

[0122] For example, the electronic device (100) can generate a guide screen including a guide UI. The electronic device (100) can transmit the guide screen to an external device (such as a visitor terminal device (200) or a user terminal device (400)). The external device can output (or display) the received guide screen.

[0123] At least one processor (120) may receive account information from a device that responded to the packet through a communication interface (130), and if the received account information is included in a list of previously stored accounts, may provide control information to the device that responded to the packet based on the account information.

[0124] At least one processor (120) receives account information from a terminal device (200) in response to a communication packet through a communication interface (130), and if the received account information is included in a list of previously stored accounts, it can share control with the terminal device (200) corresponding to the contact information.

[0125] In addition to the contact verification operation, an account verification operation may be performed. It is necessary to identify a user to control IoT devices included in the IoT network (1000). This is because a single user may own multiple terminal devices. An account may exist to identify a user when controlling the IoT network (1000). The account may be an account managed by a server (300) or other service related to various services used to control IoT devices.

[0126] Upon receiving a response packet from a visitor terminal device (200), at least one processor (120) may obtain account information included in the response packet. At least one processor (120) may determine whether it has the authority (or qualification) to share control based on the account information.

[0127] Based on the comparison result of the list of previously stored accounts and the account information of the visitor terminal device (200), at least one processor (120) can determine whether the visitor terminal device (200) has the authority (or qualification) to share control.

[0128] According to one embodiment, an account verification operation may be performed in an electronic device (100). The electronic device (100) may store an account list in a memory (110). The electronic device (100) may receive the account list from a server (300) or a user terminal device (400). The server (300) or the user terminal device (400) may transmit the account list to the electronic device (100) in response to a request from the electronic device (100).

[0129] According to one embodiment, an account verification operation may be performed on a user terminal device (400). At least one processor (120) may transmit account information to the user terminal device (400). The user terminal device (400) may compare the received account information with a list of accounts previously stored in the user terminal device (400). The user terminal device (400) may transmit the comparison result to the electronic device (100).

[0130] According to one embodiment, the account verification operation may be performed on a server (300). The server (300) may be a server connected to an IoT network (1000). The server (300) may be a server that manages accounts related to a service that controls IoT devices.

[0131] For example, the electronic device (100) may transmit account information to the server (300). The server (300) may compare the received account information with a list of accounts corresponding to the electronic device (100). The server (300) may transmit the comparison result to the electronic device (100).

[0132] For example, the electronic device (100) may transmit account information to the server (300). The server (300) may identify a list of accounts corresponding to the received account information. The server (300) may compare the identified list of accounts with the received account information. The server (300) may transmit the comparison results to the electronic device (100).

[0133] The electronic device (100) can determine whether the visitor terminal device (200) has the authority (or qualification) to connect to the IoT network (1000) based on the comparison result.

[0134] If the account information of the visitor terminal device (200) is identified as being included in the account list based on the comparison result, at least one processor (120) may determine that the visitor terminal device (200) has the authority (or qualification) to connect to the IoT network (1000).

[0135] According to various embodiments, based on the contact verification result, at least one processor (120) may determine that the visitor terminal device (200) has the authority (or qualification) to connect to the IoT network (1000).

[0136] According to various embodiments, based on the account verification result, at least one processor (120) may determine that the visitor terminal device (200) has the authority (or qualification) to connect to the IoT network (1000).

[0137] According to various embodiments, based on the contact verification result and the account verification result, at least one processor (120) may determine that the visitor terminal device (200) has the authority (or qualification) to connect to the IoT network (1000).

[0138] At least one processor (120) may generate temporary account information if the received account information is not included in the list of previously stored accounts, and provide control information to the device that responded to the packet based on the temporary account information.

[0139] At least one processor (120) may generate temporary account information if the received account information is not included in the list of previously stored accounts, and share control with the terminal device (200) based on the temporary account information.

[0140] At least one processor (120) can generate temporary account information based on contact information obtained through identification information received from a device responding to the packet.

[0141] At least one processor (120) can generate temporary account information based on contact information received from the terminal device (200).

[0142] The operation of creating a temporary account is described in FIG. 7 and FIG. 27.

[0143] At least one processor (120) may update the account information to add control information about the controlled device to the account information.

[0144] At least one processor (120) may update account information to add control over the target IoT device to the account information. The operation of updating account information is described in FIG. 26.

[0145] At least one processor (120) can control, when a user input for providing control information of an external device connected to an electronic device (100) is received, to maintain a state for providing control information to a device that responded to the packet for a preset period of time, and when the preset period of time has elapsed, to not provide control information to the device that responded to the packet.

[0146] At least one processor (120) may, when a user input for sharing control over an IoT network (1000) is received, maintain IoT control sharing for sharing control over a terminal device (200) for a preset period of time, and, when the preset period of time has elapsed, delete the control shared over the terminal device (200). Operations related thereto are described in FIGS. 31 and 32.

[0147] At least one processor (120) can obtain a signal intensity corresponding to each of at least one external device connected to the electronic device (100), and identify an external device among at least one external device whose signal intensity is greater than a threshold value as a control target device.

[0148] At least one processor (120) may acquire a signal intensity corresponding to each of at least one IoT device included in the IoT network (1000), and determine an IoT device among at least one IoT device whose signal intensity is greater than a threshold value as a target IoT device. This is described in FIG. 26.

[0149] The electronic device (100) can automatically grant visitors direct control of IoT devices through contact information, accounts, etc. Visitors can easily control IoT devices automatically without performing separate connection actions. Users can share control with visitors without having to disclose information about the IoT device (network name, password, etc.).

[0150] The electronic device (100) can allow users to access wireless Wi-Fi to visitors gathered at a specific location and provide control over Internet of Things devices connected to the Wi-Fi for a certain period of time.

[0151] The electronic device (100) can provide a function in which temporary visitors are automatically invited and accepted without granting control to each visitor when there are multiple visitors.

[0152] Instead of giving permission to all visitors, you can share control only with visitors in your mobile contacts.

[0153] For example, assume a user is hosting a party and many friends are attending. The electronic device (100) can search for the visitor terminal device (200) to obtain contact information of nearby devices. The electronic device (100) can determine whether the contacts are friends by determining whether they correspond to previously stored contact information.

[0154] A visitor terminal device (200) corresponding to a previously stored contact can automatically connect to an IoT network (1000). The electronic device (100) can send a notification to the visitor terminal device (200) so that it can take control of IoT devices.

[0155] When a response accepting the invitation is received from the visitor terminal device (200) that has received the notification, the electronic device (100) can authorize the visitor terminal device (200) to automatically connect to the IoT network (1000). The electronic device (100) can transmit a message to the visitor terminal device (200) to install an application for controlling the IoT device. The visitor terminal device (200) can access the application installation link through the message. After installing the application, the visitor terminal device (200) can control the IoT device.

[0156] An electronic device (100) can send an invitation notification in advance to a specific visitor. The electronic device (100) can send an invitation notification in advance to some of the multiple users included in its contact list. A visitor terminal (200) that receives an invitation notification in advance can immediately connect (or access) to the IoT network (1000).

[0157] The visitor terminal device (200) can perform sharing functions such as operating an air conditioner, controlling lighting, sharing images / photos via TV, and playing music. The IoT network (1000) can also transmit notifications generated from IoT devices such as air purifiers and food completion to the visitor terminal device (200).

[0158] The visitor terminal device (200) can share photos / videos in IoT control sharing. The electronic device (100) can output the avatar of the visitor terminal device (200). If there are multiple visitor terminal devices (200), multiple avatars can be displayed.

[0159] The electronic device (100) can display a QR code that can directly participate in IoT control sharing.

[0160] IoT devices can provide a music content sharing function. Music content selected through a visitor terminal device (200) can be output from the IoT device.

[0161] FIG. 2 is a block diagram for explaining the specific configuration of the electronic device (100) of FIG. 1.

[0162] Referring to FIG. 2, the electronic device (100) may include at least one of a memory (110), at least one processor (120), a communication interface (130), a display (140), an operation interface (150), an input / output interface (160), a speaker (170), a microphone (180), and a camera (190).

[0163] The memory (110) may be implemented as an internal memory such as a ROM (e.g., an electrically erasable programmable read-only memory (EEPROM)) or RAM included in at least one processor (120), or may be implemented as a separate memory from at least one processor (120). The memory (110) may be implemented as a memory embedded in the electronic device (100) or as a memory detachable from the electronic device (100) depending on the purpose of data storage. For example, data for driving the electronic device (100) may be stored in a memory embedded in the electronic device (100), and data for expanding functions of the electronic device (100) may be stored in a memory detachable from the electronic device (100).

[0164] In the case of memory embedded in the electronic device (100), it may be implemented as at least one of volatile memory (e.g., dynamic RAM (DRAM), static RAM (SRAM), or synchronous dynamic RAM (SDRAM)), non-volatile memory (e.g., one time programmable ROM (OTPROM), programmable ROM (PROM), erasable and programmable ROM (EPROM), electrically erasable and programmable ROM (EEPROM), mask ROM, flash ROM, flash memory (e.g., NAND flash or NOR flash), etc.), hard drive, or solid state drive (SSD), and in the case of memory that can be attached or detached to the electronic device (100), it may be implemented in the form of a memory card (e.g., compact flash (CF), secure digital (SD), micro secure digital (Micro-SD), mini secure digital (Mini-SD), extreme digital (xD), multi-media card (MMC), etc.), external memory that can be connected to a USB port (e.g., USB memory), etc.

[0165] The memory (110) can store at least one instruction. Based on the instruction stored in the memory (110), at least one processor (120) can perform various operations.

[0166] At least one processor (120) may be implemented as a digital signal processor (DSP), a microprocessor, or a time controller (TCON) that processes digital signals. However, the present invention is not limited thereto, and may include one or more of a central processing unit (CPU), a micro controller unit (MCU), a micro processing unit (MPU), a controller, an application processor (AP), a graphics-processing unit (GPU), a communication processor (CP), or an advanced reduced instruction set computer (RISC) machines (ARM) processor, or may be defined by the relevant terminology. At least one processor (120) may be implemented as a system on chip (SoC) having a built-in processing algorithm, a large scale integration (LSI), or may be implemented in the form of a field programmable gate array (FPGA). At least one processor (120) may perform various functions by executing computer executable instructions stored in a memory.

[0167] The communication interface (130) is a configuration that performs communication with various types of external devices according to various types of communication methods. The communication interface (130) may include a wireless communication module or a wired communication module. Each communication module may be implemented in the form of at least one hardware chip.

[0168] A wireless communication module may be a module that communicates wirelessly with an external device. For example, the wireless communication module may include at least one of a Wi-Fi module, a Bluetooth module, an infrared communication module, or other communication modules.

[0169] Wi-Fi and Bluetooth modules can communicate via Wi-Fi and Bluetooth, respectively. When using a Wi-Fi or Bluetooth module, various connection information, such as the service set identifier (SSID) and session key, is first transmitted and received. This information is then used to establish a communication connection before various other information can be transmitted and received.

[0170] Infrared communication modules perform communication based on infrared communication (IrDA, infrared Data Association) technology, which transmits data wirelessly over short distances using infrared light, which is between visible light and millimeter waves.

[0171] In addition to the above-described communication method, other communication modules may include at least one communication chip that performs communication according to various wireless communication standards such as zigbee, 3G (3rd Generation), 3GPP (3rd Generation Partnership Project), LTE (Long Term Evolution), LTE-A (LTE Advanced), 4G (4th Generation), 5G (5th Generation), etc.

[0172] A wired communication module may be a module that communicates with an external device via a wire. For example, the wired communication module may include at least one of a Local Area Network (LAN) module, an Ethernet module, a paired cable, a coaxial cable, a fiber optic cable, or an Ultra Wide-Band (UWB) module.

[0173] According to various embodiments, the communication interface (130) may utilize the same communication module (e.g., a Wi-Fi module) to communicate with an external device such as a remote control device and an external server.

[0174] According to various embodiments, the communication interface (130) may utilize different communication modules to communicate with external devices, such as remote control devices, and external servers. For example, the communication interface (130) may utilize at least one of an Ethernet module or a Wi-Fi module to communicate with an external server, and may also utilize a Bluetooth module to communicate with an external device, such as a remote control device. However, this is merely an embodiment, and the communication interface (130) may utilize at least one of various communication modules when communicating with multiple external devices or external servers.

[0175] The display (140) may be implemented as a variety of displays such as a liquid crystal display (LCD), an organic light emitting diode (OLED) display, a plasma display panel (PDP), etc. The display (140) may also include a driving circuit, a backlight unit, etc., which may be implemented as a form such as an a-si TFT (amorphous silicon thin film transistor), an LTPS (low temperature poly silicon) TFT, an OTFT (organic TFT), etc. The display (140) may be implemented as a touch screen combined with a touch sensor, a flexible display, a three-dimensional display (3D display, three-dimensional dispaly), etc. According to an embodiment of the present disclosure, the display (140) may include not only a display panel that outputs images, but also a bezel that houses the display panel. In particular, according to an embodiment of the present disclosure, the bezel may include a touch sensor (not shown) for detecting user interaction.

[0176] The operating interface (150) may be implemented as a device such as a button, a touch pad, a mouse, and a keyboard, or as a touch screen capable of performing the above-described display function and operating input function. The button may be a mechanical button, a touch pad, a wheel, or any other type of button formed in any area of ​​the front, side, or back of the main body of the electronic device (100).

[0177] The input / output interface (160) may be any one of HDMI (High Definition Multimedia Interface), MHL (Mobile High-Definition Link), USB (Universal Serial Bus), DP (Display Port), Thunderbolt, VGA (Video Graphics Array) port, RGB port, D-SUB (D-subminiature), and DVI (Digital Visual Interface). The input / output interface (160) may input / output at least one of audio and video signals. Depending on the implementation example, the input / output interface (160) may include a port that inputs / outputs only audio signals and a port that inputs / outputs only video signals as separate ports, or may be implemented as a single port that inputs / outputs both audio signals and video signals. The electronic device (100) may transmit at least one of the audio and video signals to an external device (e.g., an external display device or an external speaker) through the input / output interface (160). An output port included in the input / output interface (160) can be connected to an external device, and the electronic device (100) can transmit at least one of an audio and video signal to the external device through the output port.

[0178] The input / output interface (160) can be connected to a communication interface. The input / output interface (160) can transmit information received from an external device to the communication interface or transmit information received through the communication interface to the external device.

[0179] The speaker (170) may be a component that outputs various audio data as well as various notification sounds or voice messages.

[0180] The microphone (180) is a component that receives a user's voice or other sounds and converts them into audio data. The microphone (180) can receive the user's voice in an activated state. For example, the microphone (180) can be formed integrally on the upper side, the front side, the side side, etc. of the electronic device (100). The microphone (180) can include various components such as a microphone that collects the user's voice in analog form, an amplifier circuit that amplifies the collected user's voice, an A / D conversion circuit that samples the amplified user's voice and converts it into a digital signal, and a filter circuit that removes noise components from the converted digital signal.

[0181] The camera (190) is a device configured to capture a subject and generate a captured image, and the captured image includes both moving images and still images. The camera (190) can acquire images for at least one external device and can be implemented with a camera, lens, infrared sensor, or the like.

[0182] The camera (190) may include a lens and an image sensor. The type of lens may include a general-purpose lens, a wide-angle lens, a zoom lens, etc., and may be determined according to the type, characteristics, usage environment, etc. of the electronic device (100). The image sensor may include a complementary metal oxide semiconductor (CMOS) and a charge-coupled device (CCD).

[0183] According to various embodiments, the electronic device (100) may include a display (140). The electronic device (100) may directly display an acquired image or content on the display (140).

[0184] According to various embodiments, the electronic device (100) may not include a display (140). The electronic device (100) may be connected to an external display device and may transmit images or content stored in the electronic device (100) to the external display device.

[0185] The electronic device (100) can transmit an image or content to an external display device along with a control signal for controlling the display of the image or content on the external display device. The external display device can be connected to the electronic device (100) via a communication interface (130) or an input / output interface (160). For example, the electronic device (100) may not include a display, such as a set-top box (STB).

[0186] The electronic device (100) may include only a small display capable of displaying simple information such as text information. The electronic device (100) may transmit images or content to an external display device via a communication interface (130) wired or wirelessly, or transmit the images or content to the external display device via an input / output interface (160).

[0187] There may be various embodiments in which the electronic device (100) performs an action corresponding to a user voice signal received through a microphone (180).

[0188] According to various embodiments, the electronic device (100) may control the display (140) based on a user voice signal received through the microphone (180). For example, when a user voice signal for displaying content A is received, the electronic device (100) may control the display (140) to display content A.

[0189] According to various embodiments, the electronic device (100) may control an external display device connected to the electronic device (100) based on a user voice signal received through the microphone (180). The electronic device (100) may generate a control signal for controlling the external display device so that an operation corresponding to the user voice signal is performed on the external display device, and transmit the generated control signal to the external display device. The electronic device (100) may store a remote control application for controlling the external display device. In addition, the electronic device (100) may transmit the generated control signal to the external display device using at least one communication method among Bluetooth, Wi-Fi, and infrared. For example, when a user voice signal for displaying content A is received, the electronic device (100) may transmit a control signal to the external display device so that the content A is displayed on the external display device. The electronic device (100) may refer to various terminal devices that can install a remote control application, such as a smartphone or an AI speaker.

[0190] According to various embodiments, the electronic device (100) may use a remote control device to control an external display device connected to the electronic device (100) based on a user voice signal received through a microphone (180). The electronic device (100) may transmit a control signal to the remote control device for controlling the external display device so that an operation corresponding to the user voice signal is performed on the external display device. In addition, the remote control device may transmit the control signal received from the electronic device (100) to the external display device. For example, when a user voice signal for displaying content A is received, the electronic device (100) may transmit a control signal to the remote control device for controlling the display of content A on the external display device, and the remote control device may transmit the received control signal to the external display device.

[0191] The electronic device (100) can receive a user voice signal in various ways.

[0192] According to various embodiments, the electronic device (100) can receive a user voice signal through a microphone (180) included in the electronic device (100).

[0193] According to various embodiments, the electronic device (100) may receive a user voice signal from an external device including a microphone. The external device may refer to a remote control device or a smartphone, etc. The received user voice signal may be a digital voice signal, but may also be an analog voice signal depending on the implementation example. The electronic device (100) may receive the user voice signal via a wireless communication method such as Bluetooth or Wi-Fi.

[0194] The electronic device (100) can convert the user voice signal in various ways.

[0195] According to various embodiments, the electronic device (100) may obtain text information corresponding to a user voice signal from an external server. The electronic device (100) may transmit the user voice signal (audio signal or digital signal) to the external server. The external server may refer to a voice recognition server. The voice recognition server may convert the user voice signal into text information using STT (Speech To Text). Then, the external server may transmit text information corresponding to the converted user voice signal to the electronic device (100).

[0196] According to various embodiments, the electronic device (100) can independently acquire text information corresponding to a user voice signal. The electronic device (100) can also directly apply a STT (Speech To Text) function to a digital voice signal to convert it into text information and transmit the converted text information to an external server.

[0197] An external server can transmit information to the electronic device (100) in a variety of ways.

[0198] According to various embodiments, an external server may transmit text information corresponding to a user voice signal to an electronic device (100). The external server may be a server that performs a voice recognition function that converts a user voice signal into text information.

[0199] According to various embodiments, the external server may transmit at least one of text information corresponding to the user voice signal or search result information corresponding to the text information to the electronic device (100). The external server may be a server that performs a search result providing function that provides search result information corresponding to the text information in addition to a voice recognition function that converts the user voice signal into text information. For example, the external server may be a server that performs both a voice recognition function and a search result providing function. In another example, the external server may perform only a voice recognition function and the search result providing function may be performed by a separate server. The external server may transmit text information to a separate server to obtain a search result and obtain a search result corresponding to the text information from the separate server.

[0200] The electronic device (100) can communicate with external devices and external servers in various ways.

[0201] According to various embodiments, communication modules for communication with external devices and external servers may be implemented identically. For example, the electronic device (100) may communicate with an external device using a Bluetooth module, and the external server may also communicate using a Bluetooth module.

[0202] According to various embodiments, communication modules for communication with external devices and external servers may be implemented separately. For example, the electronic device (100) may communicate with external devices using a Bluetooth module and with external servers using an Ethernet modem or Wi-Fi module.

[0203] FIG. 3 is a drawing for explaining an IoT system (3000) according to one embodiment.

[0204] The IoT system (3000) may include at least one of an IoT network (1000), a visitor terminal device (200), and a server (300).

[0205] An IoT network (1000) may include at least one IoT device (100, 100-2, 100-3). The IoT network (1000) may be connected to a server (300). The IoT devices (100, 100-2, 100-3) may be connected to the server (300). The server (300) may be connected to the IoT network (1000).

[0206] The visitor terminal device (200) can control the IoT devices (100, 100-2, 100-3) through the server (300). The visitor terminal device (200) can connect to (or be connected to) the server (300). The visitor terminal device (200) can transmit control commands to the IoT devices (100, 100-2, 100-3) through the server (300).

[0207] The server (300) can store account information related to the visitor terminal device (200).

[0208] FIG. 4 is a diagram for explaining an IoT system (4000) according to one embodiment.

[0209] The IoT system (4000) may include at least one of an IoT network (1000), a visitor terminal device (200), a server (300), and an AP device (500).

[0210] An IoT network (1000) may include IoT devices (100, 100-2, 100-3). The IoT network (1000) may be connected to a server (300) via an AP device (500).

[0211] The visitor terminal device (200) can perform direct communication with the electronic device (100) to connect to the AP device (500). The direct communication may include short-range communication. The short-range communication may include BLE communication, Wi-Fi Direct, NFC, etc. Using the direct communication, the visitor terminal device (200) can obtain information about the AP device (500). After the AP device (500) and the visitor terminal device (200) are connected, the visitor terminal device (200) can control the IoT devices (100, 100-2, 100-3) using the AP device (500).

[0212] The visitor terminal device (200) can be connected to the IoT network (1000) via the AP device (500). The visitor terminal device (200) can transmit control commands to the IoT devices (100, 100-2, 100-3) using the AP device (500).

[0213] The AP device (500) can be connected to the server (300). The AP device (500) can exchange information with the server (300).

[0214] FIG. 5 is a diagram for explaining an IoT system (5000) according to one embodiment.

[0215] The IoT system (5000) may include at least one of an IoT network (1000) and a visitor terminal device (200). The IoT network (1000) may include IoT devices (100, 100-2, 100-3).

[0216] The IoT system (5000) may not include an AP device (500). One electronic device (100) among the IoT devices (100, 100-2, 100-3) may operate as an AP. The electronic device (100) may create a temporary AP. The electronic device (100) may create a temporary AP and connect to the IoT devices (100-2, 100-3) through the temporary AP. The visitor terminal device (200) may perform direct communication with the electronic device (100), and the visitor terminal device (200) may be connected to the IoT network (1000) through the temporary AP. The visitor terminal device (200) may transmit a control command to the IoT devices (100-2, 100-3) through the electronic device (100) performing the temporary AP function.

[0217] FIG. 6 is a drawing for explaining an IoT system (6000) according to one embodiment.

[0218] An IoT system (6000) may include at least one of an IoT network (1000) and a visitor terminal device (200). The IoT network (1000) may include IoT devices (100, 100-2, 100-3). The visitor terminal device (200) and the IoT devices (100, 100-2, 100-3) may be connected using direct communication. The IoT devices (100, 100-2, 100-3) may be directly connected to the visitor terminal device (200) without using an AP.

[0219] Figure 7 is a flowchart to explain the operation of starting IoT control sharing.

[0220] Referring to FIG. 7, the electronic device (100) may obtain a control sharing command (S705). The control sharing command may be a command to share control over an IoT device included in an IoT network with a visitor. The electronic device (100) may be one of the IoT devices included in the IoT network.

[0221] The electronic device (100) can determine an IoT device with which to share control (S710). The IoT device with which to share control can be designated as a target IoT device. An IoT network can include multiple IoT devices. The electronic device (100) can determine at least one of the multiple IoT devices as the target IoT device. The target IoT device can be designated as either a target device or a shared device.

[0222] The electronic device (100) can obtain AP information (S715). The electronic device (100) can use an AP to connect to an IoT device included in an IoT network. The AP may be a regular AP or a temporary AP. A regular AP may refer to an AP used when a separate AP device (500) exists. A temporary AP may refer to an IoT device that performs AP functions independently, other than the AP device (500). The electronic device (100) can obtain AP information used in the IoT network to which it belongs.

[0223] The electronic device (100) can generate a BLE packet for sharing notification (S720). The electronic device (100) can transmit a sharing notification to external devices to notify the start of IoT control sharing. The electronic device (100) can generate a communication packet including the sharing notification. The communication packet may be a BLE packet. The communication packet may be described as an advertising packet. The sharing notification may be described as an invitation notification, as it is intended to invite a visitor.

[0224] The electronic device (100) can broadcast the generated BLE packet (S725). The electronic device (100) can broadcast the generated communication packet. The broadcasting operation may include an operation of randomly transmitting the communication packet to peripheral devices based on the electronic device (100).

[0225] The visitor terminal device (200) can receive a BLE communication packet broadcast from the electronic device (100). The visitor terminal device (200) can accept sharing in response to a sharing notification (or invitation notification) included in the BLE communication packet (S726). For example, a response to the sharing notification can be automatically generated by the visitor terminal device (200). For example, a response to the sharing notification can be manually generated by the visitor terminal device (200). A response can be generated when a user directly inputs a response.

[0226] The visitor terminal device (200) may generate a response packet in response to a BLE communication packet. The response packet may include at least one of the contact information of the visitor terminal device (200) or an account of the visitor terminal device (200). The contact information may be described as contact information, and the account information may be described as account information.

[0227] The visitor terminal device (200) can transmit a response packet containing at least one of a contact or an account to the electronic device (100) (S727).

[0228] The electronic device (100) can receive a response packet from the visitor terminal device (200). The electronic device (100) can obtain at least one of the contact information of the visitor terminal device (200) or the account of the visitor terminal device (200) included in the response packet.

[0229] The electronic device (100) can perform a contact verification operation.

[0230] The electronic device (100) may transmit a signal requesting contact verification to the user terminal device (400) (S730). The signal requesting contact verification may include a contact and a control command for verifying the contact.

[0231] The user terminal device (400) can receive a signal requesting contact verification from the electronic device (100). The user terminal device (400) can obtain a contact from the received signal. The user terminal device (400) can verify the contact (the contact of the visitor terminal device (200)) (S731). The user terminal device (400) can verify whether the contact is included in the contact list of the user terminal device (400). The contact requesting verification may be the contact of the visitor terminal device (200). The contact requesting verification may be listed as a target contact.

[0232] For example, assume that a user terminal device (400) stores 100 contacts, including friends, family, and coworkers. The user terminal device (400) can check whether the 100 stored contacts include a target contact for which the electronic device (100) has requested confirmation.

[0233] The user terminal device (400) can obtain a verification result. The verification result may include result information regarding whether the target contact is included in the contact list of the user terminal device (400). The user terminal device (400) can transmit the contact verification result to the electronic device (100) (S732).

[0234] The electronic device (100) can receive a contact verification result from the user terminal device (400). Based on the verification result, the electronic device (100) can determine whether the target contact is already stored in the contact list of the user terminal device (400) (S735).

[0235] If the target contact (contact of the visitor terminal device (200)) is not pre-stored in the contact list (contact list of the user terminal device (400)) (S735-N), the electronic device (100) may provide a guide UI (S736). The guide UI may include a guide action requiring access permission from the visitor terminal device (200). A description of the guide UI (or screen) is provided in FIGS. 23 and 24.

[0236] After providing the guide UI, the electronic device (100) can check connection authority for the visitor terminal device (200) (S737). The electronic device (100) can check whether the visitor terminal device (200) has acquired connection authority through the guide UI. The connection authority may be described as AP connection authority.

[0237] If the connection authority of the visitor terminal device (200) is not confirmed (S737-N), the electronic device (100) can provide the guide UI again.

[0238] When the connection authority of the visitor terminal device (200) is confirmed (S737-Y), the electronic device (100) can transmit AP information to the visitor terminal device (200) (S740).

[0239] If the target contact (contact of the visitor terminal device (200)) is pre-stored in the contact list (contact list of the user terminal device (400)) (S735-Y), the electronic device (100) can transmit AP information to the visitor terminal device (200).

[0240] The visitor terminal device (200) can receive AP information from the electronic device (100). The visitor terminal device (200) can perform AP connection based on the received AP information (S741). AP connection may refer to a communication connection using an AP. The visitor terminal device (200) can access the AP (or a device functioning as an AP) based on the received AP information.

[0241] The electronic device (100) may transmit a signal requesting account verification to the server (300) (S750). The signal requesting account verification may include an account and a control command for verifying the account.

[0242] The server (300) can receive a signal requesting account verification from the electronic device (100). The server (300) can obtain an account from the received signal. The server (300) can verify the account (account of the visitor terminal device (200)) (S751). The server (300) can verify whether the account is included in the account list of the server (300). The account requesting verification may be the account of the visitor terminal device (200). The account requesting verification may be described as a target account.

[0243] For example, assume that the server (300) stores 1,000 accounts of multiple users, etc. The server (300) can check whether the target account for which the electronic device (100) has requested verification is included among the 1,000 stored accounts.

[0244] The server (300) can obtain a verification result. The verification result may include result information regarding whether the target account is included in the account list of the server (300). The server (300) can transmit the account verification result to the electronic device (100) (S752).

[0245] The electronic device (100) can receive an account verification result from the server (300). Based on the verification result, the electronic device (100) can determine whether the target account (account of the visitor terminal device (200)) is already stored in the account list of the server (300) (S755).

[0246] If the target account is not already registered (S755-N), the electronic device (100) may create a temporary account (S756). The temporary account may be an account created temporarily rather than a previously registered regular account. The temporary account may be an account that is deleted when IoT control sharing is terminated. The temporary account may be an account that is deleted after a preset period of time has elapsed since the termination of IoT control sharing.

[0247] After creating a temporary account, the electronic device (100) can share control of the IoT device with the visitor account (S757).

[0248] If the target account is already registered (S755-Y), the electronic device (100) can share control of the IoT device with the visitor account (S757).

[0249] A visitor account can be either a pre-registered regular account or a temporary account created on a temporary basis.

[0250] The action of sharing control may include an action of sharing (or granting) control of an IoT device to a visitor terminal device (200). To share control, the electronic device (100) may transmit a signal indicating that control is granted to the visitor terminal device (200) to one of the visitor terminal device (200), the server (300), the user terminal device (400), and the AP device (500).

[0251] Figure 8 is a flowchart for explaining an operation for terminating IoT control sharing.

[0252] Referring to FIG. 8, steps S805 to S857 may overlap with steps S705 to S757 of FIG. 7. The overlapping description is omitted.

[0253] After sharing control of an IoT device with a visitor account, the electronic device (100) can identify a termination event for IoT control sharing (S860). The termination event for IoT control sharing may include an event for deleting control. The event for deleting control may include at least one of an event in which a preset time has elapsed or an event in which a user's termination command has been received.

[0254] After the termination event is identified, the electronic device (100) can delete control of the IoT device that was added to the visitor account (S870).

[0255] The electronic device (100) may transmit a notification related to the deletion of control rights to the visitor terminal device (200) (S871). The electronic device (100) may transmit a notification related to the deletion of control rights to the user terminal device (400) (S872). The electronic device (100) may transmit a notification related to the deletion of control rights to the server (300) (S873). The electronic device (100) may transmit a notification related to the deletion of control rights to the AP device (500).

[0256] A notification regarding the deletion of control rights may include at least one of the following: information indicating that control rights have been deleted, or a control command to delete previously shared control rights. Upon receiving a notification regarding the deletion of control rights, information related to control sharing may be deleted from each receiving device.

[0257] The electronic device (100) can delete AP information after a termination event for IoT control sharing is identified (S880). If the AP information is a temporary AP, the electronic device (100) can delete all information related to the temporary AP. If the AP information is a regular AP, the electronic device (100) can maintain the AP information.

[0258] Figure 9 is a flowchart for explaining IoT control sharing according to various embodiments.

[0259] Referring to FIG. 9, the electronic device (100) can start IoT control sharing (S910).

[0260] The electronic device (100) can obtain user input from a user of the electronic device (100) to initiate IoT control sharing. IoT control sharing can be described as an IoT sharing mode, a party mode, a conference mode, a control sharing mode, a smart sharing mode, etc.

[0261] The electronic device (100) can display a UI related to IoT control sharing through the display (140) of the electronic device (100). Specific operations related thereto are described in FIGS. 10 and 11.

[0262] The electronic device (100) can receive user input through a displayed UI. The electronic device (100) can receive user voice. The electronic device (100) can receive user input through a remote control device corresponding to the electronic device (100) or an integrated remote control device corresponding to an IoT network. Specific operations related thereto are described in FIG. 10.

[0263] The electronic device (100) can identify an event that initiates IoT control sharing when a user (visitor) other than the preset user is identified. Specific operations related to this are described in FIG. 12.

[0264] According to various embodiments, the electronic device (100) may initiate IoT control sharing when a preset event occurs. The preset event may be an event that causes a preset application to be executed. The preset application may be an application preset by the user to automatically initiate IoT control sharing. For example, the preset application may include a music playback application, a movie playback application, a chat application, an education-related application, etc. When the preset application is executed through the electronic device (100), the electronic device (100) may automatically initiate IoT control sharing.

[0265] The pre-configured application may include an application related to IoT control. The application related to IoT control may include an application for control of a specific user (e.g., a user of the electronic device (100)).

[0266] Applications related to IoT control may include a separate application for sharing control authority to users other than the user of the electronic device (100).

[0267] The preset event may include an event that receives a signal indicating that a preset application has been executed from the visitor terminal device (200). It is assumed that the application has been installed on the visitor terminal device (200). When the application installed on the visitor terminal device (200) is executed, the visitor terminal device (200) may transmit a signal to the electronic device (100) to notify that the application has been executed. When the electronic device (100) receives a notification signal from the visitor terminal device (200), the electronic device (100) may automatically initiate IoT control sharing.

[0268] According to various embodiments, the electronic device (100) may be connected to an external device for controlling the electronic device (100). The external device may refer to a user control device. For example, the electronic device (100) may be controlled by a user terminal device (400). The user terminal device (400) does not necessarily need to be located near the electronic device (100). The user may remotely transmit a control command to the electronic device (100) via the user terminal device (400) to initiate IoT control sharing in the electronic device (100). The electronic device (100) may receive the control command (user input) via the user terminal device (400). The electronic device (100) may initiate IoT control sharing according to the control command. The user terminal device (400) may be described as a host device, a remote host device, an IoT control device, etc.

[0269] User input does not necessarily mean input through a user terminal device (400), but may be input through a visitor terminal device (200). If user input is input through a visitor terminal device (200), it may be described as visitor input.

[0270] According to various embodiments, the electronic device (100) may provide a chat service. The chat service may be provided through a chat application. The chat service may be a service that allows multiple users to converse regarding a single piece of content. The chat service may be provided through an IoT device including a display. The server (300) may generate and provide the chat service. The server (300) may obtain and manage identification information for at least one user to provide the chat service.

[0271] An electronic device (100) can obtain a user list representing multiple users participating in a chat service. The electronic device (100) can select at least some of the multiple users included in the user list. The electronic device (100) can share control rights with some of the selected users. The electronic device (100) can provide (or display) a guide screen including the user list. The electronic device (100) can receive a user input for selecting a user with whom to share control rights through the guide screen. The electronic device (100) can obtain identification information of a terminal device corresponding to the selected user. Using the identification information, the electronic device (100) can transmit a signal related to sharing control rights to the terminal device corresponding to the user input.

[0272] A chat service may provide a menu related to control sharing. When the control sharing function is selected through the menu provided by the chat service, the electronic device (100) may provide a screen or UI for selecting a partner with whom to share control. The electronic device (100) may receive user input for selecting at least one partner through the screen or UI. Once at least one partner is selected, the electronic device (100) may provide a notification related to control sharing to the at least one partner. After providing the notification, the electronic device (100) may receive a signal indicating approval (or acceptance) related to control sharing from the at least one partner. The electronic device (100) may share control only with the terminal device that transmitted the signal indicating approval.

[0273] An electronic device (100) may include a display (140). The electronic device (100) may provide a screen related to a chat service. The electronic device (100) may obtain identification information related to at least one user using the chat service. The electronic device (100) may initiate IoT control sharing for the users of the obtained chat service. The electronic device (100) may obtain identification information about the users of the chat service through the server (300). The electronic device (100) may grant control over an IoT device based on the identification information received from the server (300). The electronic device (100) may grant control to an account (or device) corresponding to the identification information.

[0274] The electronic device (100) can determine a specific IoT device with which it shares control. The specific IoT device may be designated as a target IoT device.

[0275] An electronic device (100) can determine an IoT device to which control is granted through IoT control sharing. The IoT device to which control is granted through IoT control sharing can be designated as a target IoT device. The target IoT device can be determined automatically.

[0276] The target IoT device may include all devices connected to the IoT network. The target IoT device may be a device connected to an electronic device (100), a server (300), an AP device (500), etc.

[0277] According to various embodiments, the electronic device (100) may determine an IoT device connected to the server (300) as a target IoT device. An IoT network may be connected to the server (300). The server (300) may register an IoT device included in the IoT network using the user's account information. The server (300) may map specific account information (the user's account information) to the IoT device. The server (300) may determine an IoT device mapped to specific account information (the user's account information) as a target IoT device.

[0278] According to various embodiments, the electronic device (100) may determine an IoT device connected to the AP device (500) as a target IoT device. The AP device (500) may store information (e.g., identification information) related to IoT devices included in an IoT network. The AP device (500) may store information about connectable IoT devices. The electronic device (100) may request information about IoT devices stored in the AP device (500). In response to the request, the AP device (500) may transmit information about connectable IoT devices to the electronic device (100). The electronic device (100) may determine a target IoT device based on information received from the AP device (500).

[0279] According to various embodiments, the electronic device (100) may determine an IoT device connected to the electronic device (100) as a target IoT device. The electronic device (100) may store information (e.g., identification information) related to the IoT device included in the IoT network. The electronic device (100) may store information about connectable IoT devices. The electronic device (100) may determine the target IoT device based on the information about the connectable IoT devices that has been previously stored.

[0280] According to various embodiments, the electronic device (100) can allow the user to directly determine the target IoT device. A description related to this is provided in FIG. 13.

[0281] According to various embodiments, the electronic device (100) can group and manage visitors or target IoT devices to which invitation notifications are sent. A description of this is provided in FIGS. 14 and 15 .

[0282] According to various embodiments, the electronic device (100) may share control over functions related to IoT devices. A description thereof is provided in FIG. 16.

[0283] According to various embodiments, the electronic device (100) can use an AP corresponding to an IoT network.

[0284] Assume that an AP device (500) is connected to an IoT network. IoT devices included in the IoT network can receive control commands through the AP device (500). In addition, the IoT devices can transmit status information (or control information or response information) related to the IoT devices to other devices through the AP device (500).

[0285] The AP device (500) may be a device previously connected to an IoT network. For example, the AP device (500) may be a router using Wi-Fi. The electronic device (100) may obtain AP information related to the AP device (500). The electronic device (100) may grant control using the AP information. The electronic device (100) may transmit the AP information to the visitor terminal device (200) to which the control is to be granted.

[0286] According to various embodiments, even if an AP device (500) is connected to an IoT network, the electronic device (100) may operate as a temporary AP. Operating as a temporary AP may mean that the electronic device (100) directly performs AP functions. The electronic device (100) may operate as a temporary AP to perform functions identical to / similar to those of the AP device (500).

[0287] According to various embodiments, the AP device (500) may not be connected to the IoT network. If the AP device (500) is not connected or does not exist, the electronic device (100) may operate as a temporary AP. The electronic device (100) may generate AP information related to the temporary AP. Operations related to the temporary AP are described in FIG. 5.

[0288] When an AP device (500) exists, the AP information used may be described as regular AP information or first AP information.

[0289] When the AP device (500) does not exist, the AP information used may be described as temporary AP information or second AP information.

[0290] AP information may include at least one of regular AP information or temporary AP information.

[0291] According to various embodiments, an IoT network can control (or manage) IoT devices using individual communication methods between devices. IoT devices can utilize individual direct communication methods without using an AP device (500) or a temporary AP. For example, IoT devices can establish a two-way communication session via BLE, direct Wi-Fi, etc. IoT devices can communicate with a visitor terminal device (200) using BLE, direct Wi-Fi, etc. Operations for individual communication methods are described in FIG. 6.

[0292] The electronic device (100) can transmit a notification to the visitor for IoT control sharing. The electronic device (100) can transmit a notification to automatically grant the visitor control over the IoT device. The notification can be described as an invitation notification or an invitation message. The notification can be included in a communication packet and transmitted to the visitor terminal device (200). The electronic device (100) can transmit a communication packet related to the notification to the visitor terminal device (200).

[0293] For example, the electronic device (100) may transmit a communication packet (e.g., a BLE communication packet) containing notification information for an invitation to the visitor terminal device (200). In response to the communication packet, the electronic device (100) may obtain identification information (e.g., contact information, account, etc.) from the visitor terminal device (200). The electronic device (100) may determine whether to grant control to the visitor based on the identification information. If it is determined to grant control, the electronic device (100) may transmit AP information to the visitor terminal device (200). Operations related thereto are described in FIG. 7.

[0294] For example, the electronic device (100) may transmit a communication packet (e.g., a BLE communication packet) containing notification information and AP information for an invitation to the visitor terminal device (200). In response to the communication packet, the electronic device (100) may obtain identification information (e.g., contact information, account, etc.) from the visitor terminal device (200). The electronic device (100) may determine whether to grant control to the visitor based on the identification information. If it is determined to grant control, the electronic device (100) may transmit an approval notification for AP connection (or connection through AP) to the visitor terminal device (200). Operations related thereto are described in FIG. 33.

[0295] According to various embodiments, the electronic device (100) may transmit an invitation notification to the visitor terminal device (200). The electronic device (100) may transmit a communication packet (e.g., a BLE communication packet) containing the invitation notification to the visitor terminal device (200). A description related thereto is provided in FIGS. 17 and 18.

[0296] According to various embodiments, the electronic device (100) may provide a guide UI for NFC tagging. A description thereof is provided in FIG. 19. When NFC tagging is performed, the electronic device (100) may receive contact information and / or account information from the visitor terminal (200). According to various embodiments, when NFC tagging is performed, the electronic device (100) may transmit an invitation notification to the visitor terminal (200).

[0297] According to various embodiments, the electronic device (100) may provide a guide UI for recognizing a QR code. A description thereof is provided in FIG. 20.

[0298] According to various embodiments, the electronic device (100) may output a guide UI for recognizing a watermark. A description thereof is provided in FIG. 21.

[0299] According to various embodiments, the electronic device (100) may transmit an invitation notification using an inaudible frequency. The electronic device (100) may include an audio signal corresponding to a preset frequency. The preset frequency may be included in a frequency range related to an inaudible frequency. The electronic device (100) may be connected to a visitor terminal (200). The electronic device (100) may request audio data from the visitor terminal (200). The visitor terminal (200) may transmit audio data recorded through a microphone included in the visitor terminal (200) to the electronic device (100).

[0300] The electronic device (100) can analyze audio data received from the visitor terminal device (200). The electronic device (100) can determine whether a preset frequency is identified in the audio data. If the preset frequency is identified in the audio data, the electronic device (100) can transmit an invitation notification to the visitor terminal device (200). If the preset frequency is not identified in the audio data, the electronic device (100) may not transmit an invitation notification to the visitor terminal device (200).

[0301] When transmitting an invitation notification, the electronic device (100) may also transmit password information for connecting to an IoT network. According to an implementation example, the electronic device (100) may generate and transmit an invitation notification including the password information. The visitor terminal device (200) may receive the password information and use it for AP connection operations.

[0302] The electronic device (100) can check the visitor terminal device (200) (S920).

[0303] The electronic device (100) can obtain identification information (contact information, account information, etc.) from the visitor terminal device (200) and perform a verification operation. A description related to this is provided in FIG. 22.

[0304] According to various embodiments, the electronic device (100) may provide a chat service. The electronic device (100) may provide a chat service corresponding to specific content. The electronic device (100) assumes that the chat service is provided to multiple devices via a server (300). The electronic device (100) may obtain identification information about a user participating in the chat service via the server (300). The identification information may include at least one of a contact number or an account.

[0305] The electronic device (100) can obtain a pre-stored contact list using user identification information obtained through the server (300). The pre-stored contact list may be a contact list for users participating in the chat service. The electronic device (100) can compare the contact list related to the chat service with the contact list of the visitor terminal (200).

[0306] If the contact of the visitor terminal device (200) is included in the contact list related to the chat service, the electronic device (100) can approve an AP connection for the visitor terminal device (200).

[0307] The electronic device (100) can obtain account information for multiple participants using the chat service. If it determines that a pre-stored (or pre-registered) account is using the chat service, the electronic device (100) can identify the terminal device for that account.

[0308] According to various embodiments, before the electronic device (100) completes a contact verification (or identification) operation for the visitor terminal device (200), the electronic device (100) may check whether the visitor terminal device (200) is connected to an AP. If the visitor terminal device (200) successfully connects directly to the AP, the contact verification operation may be unnecessary. If the visitor terminal device (200) is already connected to the AP, the electronic device (100) may determine (or consider) that the contact verification has been performed.

[0309] AP devices can be implemented as devices that require a password (password) to connect.

[0310] AP devices can be implemented as devices that can be accessed without entering a password (password).

[0311] According to various embodiments, the electronic device (100) may perform various actions when the visitor terminal device (200) transmits a response packet but fails to share control rights. A description related to this is provided in FIG. 23.

[0312] According to various embodiments, the electronic device (100) may perform various actions when the visitor terminal device (200) does not transmit a response packet. A description related to this is provided in FIGS. 24 and 25.

[0313] According to various embodiments, the visitor terminal device (200) may not respond to the invitation notification. The electronic device (100) may wait for a response for a preset period of time from the time the invitation notification is transmitted.

[0314] If no response to the invitation notification is received within a preset time, the electronic device (100) may terminate IoT control sharing.

[0315] The electronic device (100) can be controlled to connect the visitor terminal device (200) and the IoT device (S930).

[0316] The visitor terminal device (200) can connect to an IoT device included in an IoT network using AP information. The electronic device (100) can transmit AP information to the visitor terminal device (200). The electronic device (100) can share control over the IoT device using the account of the visitor terminal device (200). A description related to this is provided in FIG. 26. FIG. 26 assumes that a visitor account or an account of the visitor terminal device (200) exists.

[0317] If the visitor's account is not identified, various actions can be performed on the electronic device (100). A description of this is provided in FIG. 27.

[0318] The electronic device (100) can share control over the IoT device with the visitor terminal device (200) (S940).

[0319] After sharing control, the electronic device (100) can perform a screen sharing operation. A description related to this is provided in FIG. 28.

[0320] According to various embodiments, after sharing control, the electronic device (100) may perform a music sharing operation. A description thereof is provided in FIG. 29.

[0321] According to various embodiments, after sharing control, the electronic device (100) may perform a game sharing operation. A description thereof is provided in FIG. 30.

[0322] According to various embodiments, at least one terminal device that has shared control can share content with each other. For example, assume that a first device (210) and a second device (220) are connected to an AP in an IoT network. The multiple devices (210, 220) can share specific content. Specific content can also be shared between the multiple devices (210, 220) and IoT devices. Operations related to this are described in FIG. 28.

[0323] According to various embodiments, the electronic device (100) and the plurality of devices (210, 220) can share common content. The electronic device (100) can store at least one piece of content that has been shared. When the sharing function is terminated, the electronic device (100) can transmit the stored at least one piece of content to some of the plurality of devices (210, 220). The electronic device (100) can transmit the content provided by the device (210) to the device (220). The electronic device (100) can transmit the content provided by the device (220) to the device (210).

[0324] In various embodiments, it is assumed that there are multiple terminal devices that share control. If multiple terminal devices simultaneously transmit control commands, conflicts may arise. Therefore, it is necessary to determine which of the multiple terminal devices is the host device. When multiple terminal devices are connected to an IoT network, one of the multiple terminal devices may be designated as the host device. The remaining devices may be designated as guest devices.

[0325] For example, the device determined to be the host device may be the terminal device that was first connected.

[0326] For example, the device determined as the host device may be a terminal device directly selected by the user.

[0327] A terminal device determined as a host device can share host privileges. Host privileges may imply preferential or exclusive control over an IoT device. A terminal device determined as a host device can delegate host privileges to another terminal device. For example, a first device determined as a host device can delegate host privileges to a second device based on user input.

[0328] According to various embodiments, the electronic device (100) may store user inputs and corresponding actions obtained during IoT control sharing as a separate history. The history may include at least one of content usage history (or content viewing history) and webpage visit history (or webpage access history).

[0329] The electronic device (100) can store and manage the history collected while IoT control sharing is performed and the history collected while IoT control sharing is not performed separately.

[0330] The electronic device (100) can store the first history collected in a state where IoT control sharing is not performed in the first group. The electronic device (100) can store the second history collected in a state where IoT control sharing is performed in the second group. The electronic device (100) can individually manage the first group and the second group. The electronic device (100) can individually delete or update the history included in each group.

[0331] According to various embodiments, when IoT control sharing is performed, the electronic device (100) may display a QR code related to IoT control sharing on the display (140). The electronic device (100) may display the QR code in a preset area of ​​the display (140). The electronic device (100) may obtain a screen for displaying the QR code in the preset area. A description related to the QR code is described in FIG. 20.

[0332] QR codes may not be specific to a specific user. Users who are not currently granted control via a QR code may still be able to gain control later.

[0333] *299According to various embodiments, when IoT control sharing is performed, the electronic device (100) may repeatedly broadcast BLE packets for inviting visitors. Even if a visitor terminal device (200) is connected to the IoT network, the electronic device (100) may continue to broadcast BLE packets for inviting additional visitors.

[0334] The electronic device (100) can terminate IoT control sharing (S950).

[0335] The electronic device (100) may provide a screen related to the termination of IoT control sharing. A description thereof is provided in FIG. 31. FIG. 31 describes an event in which a user input for terminating IoT control sharing is received.

[0336] The electronic device (100) can automatically terminate IoT control sharing. A description related to this is provided in FIG. 32.

[0337] According to various embodiments, if control over all visitors (visitors' terminal devices) is deleted (or terminated), the electronic device (100) may terminate IoT control sharing. If control over one visitor is maintained, the electronic device (100) may maintain IoT control sharing.

[0338] According to various embodiments, the electronic device (100) can check the AP connection status of the visitor terminal device (200). IoT control sharing can be terminated based on whether the AP connection of the visitor terminal device (200) has been released. If the AP connection of all visitor terminal devices is released, the electronic device (100) can terminate IoT control sharing. The event of AP connection termination can occur in a situation where no terminal device is present near the device performing the AP operation.

[0339] For example, it is assumed that an AP device (500) is placed in a first space. If a visitor terminal device (200) is located at a distance greater than a threshold distance from the AP device (500), the AP connection of the visitor terminal device (200) may be disconnected.

[0340] According to various embodiments, the electronic device (100) may use a BLE signal to determine the presence of a visitor terminal device (200). The electronic device (100) may broadcast a communication packet requesting a response signal using the BLE signal. If no response signal is received, the electronic device (100) may determine that the visitor terminal device (200) is not present in the vicinity. If no response signal is received from any of the visitor terminal devices, the electronic device (100) may terminate IoT control sharing.

[0341] According to various embodiments, if a preset event is identified as occurring, the electronic device (100) may terminate IoT control sharing. The preset event may include at least one of an emergency situation event and a security situation event.

[0342] An emergency situation event may include at least one of an event in which the power supplied to the electronic device (100) is below a threshold power, an event in which the power supplied to the AP device (500) is below a threshold power, an event in which the strength of the connection signal with the IoT device is all below a threshold strength, an event in which a command to forcibly terminate IoT control sharing is received from a user terminal device (400), and an event in which a command to forcibly terminate IoT control sharing is received from a server (300).

[0343] A security situation event may include at least one of an event in which a security threat related to an IoT network is detected in real time, and an event in which personal information is identified as being included in a screen provided by an electronic device (100).

[0344] If personal information is identified as being output through the electronic device (100), the electronic device (100) may perform a function of filtering the personal information from the output screen. The electronic device (100) may identify an area where the personal information is displayed on the screen to be provided and may add a blur process or a preset block object to the identified area. The electronic device (100) may transmit the original screen without filtering the personal information to only the host device among the plurality of terminal devices. The electronic device (100) may transmit the modified screen (filtering screen) with the personal information filtered to only the guest device (a device other than the host device) among the plurality of terminal devices.

[0345] According to various embodiments, when IoT control sharing is terminated, the electronic device (100) may delete account information related to the visitor stored in the electronic device (100). The visitor account information may not be permanently deleted, as the visitor account information may be stored in the server (300). The electronic device (100) may delete visitor account information only for the electronic device (100). It may not be efficient to store information on all visitors accessible to the IoT network in the electronic device (100).

[0346] According to various embodiments, when IoT control sharing is terminated, the electronic device (100) may retain and store account information associated with the visitor without deleting it. When the visitor reconnects after IoT control sharing is terminated, the electronic device (100) may perform an AP connection using the visitor account information. Control approval authority may be granted immediately to visitors for whom visitor account information has already been stored, or approval authority may be granted first, prioritizing the granting of approval authority.

[0347] According to various embodiments, when IoT control sharing is terminated, the electronic device (100) may delete the target IoT device that was added to the visitor account information. The operation of adding the target IoT device to the visitor account information is described in FIG. 26. The opposite operation to the operation described in FIG. 26 may be performed. When IoT control sharing is terminated, the electronic device (100) may delete the target IoT device or the control rights to the target IoT device that was added to the visitor account information. The electronic device (100) may update the visitor account information by performing the operation of deleting the target IoT device. The visitor account information prior to being updated may include the target IoT device. The visitor account information after being updated may not include the target IoT device. The visitor account information may be described as first visitor account information, second visitor account information, third visitor account information, etc., depending on the update operation.

[0348] According to various embodiments, when IoT control sharing is terminated, the electronic device (100) may maintain and store the target IoT device added to the visitor account information without deleting it. When the visitor reconnects after IoT control sharing is terminated, the electronic device (100) may perform a control sharing operation using the visitor account information. The electronic device (100) may extract the target IoT device included in the visitor account information. The electronic device (100) may grant control approval authority to the extracted target IoT device immediately or grant approval authority in a priority order.

[0349] Figure 10 is a drawing for explaining the UI for starting IoT control sharing.

[0350] Referring to FIG. 10, the electronic device (100) may provide a UI related to the setting of IoT control sharing. When initiating IoT control sharing, the electronic device (100) may provide a preset UI. For example, the electronic device (100) may provide a UI (1010) related to IoT control sharing. While the electronic device (100) is providing specific content, the electronic device (100) may provide a UI (1010) related to IoT control sharing according to a preset event.

[0351] The UI (1010) may be a UI for settings related to the electronic device (100). The UI (1010) may include image data (1020) and / or text data (1030) representing IoT control sharing. The image data (1020) may include an icon for IoT control sharing. The text data (1030) may include data representing 'IoT control sharing' in a language set on the TV.

[0352] According to various embodiments, the UI (1010) may be displayed on a user terminal device (400).

[0353] To perform (or initiate) IoT control sharing, the electronic device (100) may receive user input. The electronic device (100) may receive user input in various ways.

[0354] According to various embodiments, the electronic device (100) may receive user input including a user voice. The electronic device (100) may receive a user voice for performing IoT control sharing.

[0355] For example, the electronic device (100) may include a microphone (180). The electronic device (100) may directly acquire a user's voice through the microphone (180). The electronic device (100) may perform (or initiate) IoT control sharing based on the user's voice received through the microphone (180).

[0356] For example, the electronic device (100) may receive signal information (or signal data) containing a user voice from an external device. The external device may include its own microphone. The external device may receive the user voice through its own microphone. The external device may transmit signal information containing the received user voice to the electronic device (100). The electronic device (100) may obtain signal information containing the user voice from the external device. The electronic device (100) may extract (or obtain) the user voice based on the signal information. The electronic device (100) may initiate IoT control sharing based on the extracted user voice.

[0357] For example, the electronic device (100) may receive signal information (or signal data) including a user voice from a visitor terminal device (200) or a user terminal device (400). Each terminal device may include a microphone. An application for connection with the electronic device (100) may be installed on each terminal device. The application may be an application having control authority. While the application is running on each terminal device, each terminal device may receive the user voice through a voice recognition function provided by the application. Each terminal device may transmit signal information including the user voice to the electronic device (100). The electronic device (100) may receive signal information including the user voice from each terminal device.

[0358] According to various embodiments, the electronic device (100) may communicate with a remote control (10). The remote control (10) may be a device for controlling the electronic device (100). The remote control (10) may be described as a device corresponding to the electronic device (100). The remote control (10) may be a device for operating the electronic device (100). The electronic device (100) may receive a user input for initiating IoT control sharing through the remote control (10).

[0359] For example, the remote control (10) may include a manipulation interface for user manipulation. When a user input including a user manipulation is received, the remote control (10) may transmit the user input including the user manipulation to the electronic device (100). The electronic device (100) may extract the user manipulation based on the user input received from the remote control (10). The electronic device (100) may perform an action corresponding to the user manipulation (e.g., clicking a specific UI). The performed action may be an action for initiating IoT control sharing.

[0360] For example, the remote control (10) may include a microphone for acquiring a user's voice. When a user's voice including a command to initiate IoT control sharing is acquired through the microphone, the remote control (10) may acquire (or generate) signal information (or signal data) including the user's voice. The remote control (10) may transmit the signal information to the electronic device (100). The electronic device (100) may acquire the user's voice based on the signal information received from the remote control (10). The electronic device (100) may initiate IoT control sharing based on the user's voice.

[0361] In the embodiment of FIG. 10, text data (1030) is described as indicating IoT control sharing. As an example, text data (1030) may include information indicating an invitation to a member capable of controlling an IoT device.

[0362] Figure 11 is a diagram for explaining notifications related to IoT control sharing.

[0363] Referring to FIG. 11, the electronic device (100) may provide a screen related to IoT control sharing. When a user input for initiating IoT control sharing is received, the electronic device (100) may display a screen (1100) related to IoT control sharing. The screen (1100) may include information related to IoT control sharing. The screen (1100) may be described as a guide screen, a sharing mode screen, etc. The screen (1100) may include at least one of a UI (1110) including text information describing IoT control sharing and a UI (1120) for receiving a user command. The electronic device (100) may receive a user input for initiating IoT control sharing through (1120).

[0364] According to various embodiments, the screen (1100) may be displayed on the user terminal device (400).

[0365] Figure 12 is a drawing for explaining the operation of detecting a visitor.

[0366] Referring to FIG. 12, the electronic device (100) may provide a screen related to IoT control sharing. If a preset event is identified as occurring, the electronic device (100) may provide a UI (1210) related to IoT control sharing. The preset event may be an event in which a device not registered in the IoT network is recognized. The IoT network may be connected to at least one pre-registered IoT device. It is assumed that the electronic device (100) is included in the IoT network.

[0367] An IoT network including an electronic device (100) can register at least one user who can control the IoT device. Identification information may be used to identify the user. The identification information may refer to information that can identify the user and / or the device. The identification information may include at least one of account information and terminal model information.

[0368] For example, an IoT network might represent a network connected to the same AP in your home.

[0369] For example, an IoT network can be implemented as a device-to-device connection without access points (APs). An IoT network can be implemented as a mesh network.

[0370] For example, an IoT network may represent a network in which at least one device within a home is connected to an external communications network. An IoT network may be implemented as a network in which a device within the home connects to an external server via a communication chip (e.g., a USIM (Unified Sim Card) for 3G or 4G).

[0371] An IoT network can register at least one piece of identification information. Using the registered identification information, the IoT network can grant (or share) control rights to a specific account (or device). The IoT network can search for identification information that can connect to its network in real time.

[0372] The IoT network can verify whether the retrieved identifier is already registered. If the retrieved identifier is already registered, the IoT network can grant control to the account (or device) corresponding to the retrieved identifier.

[0373] If the retrieved identification information has not been previously registered, the IoT network may not grant control to the account (or device) corresponding to the retrieved identification information.

[0374] According to various embodiments, if the searched identification information has not been previously registered, the IoT network may provide a UI (1210) to notify that non-registered identification information (or visitor) has been searched. The UI (1210) may include at least one of image data or text data indicating that non-registered identification information has been searched. The image data may include a preset icon. The text data may include the content, 'A visitor other than a previously registered user has been detected.' The UI (1210) may include content querying whether to start IoT control sharing. The UI (1210) may include text querying whether to grant control to non-registered identification information (or visitor).

[0375] According to various embodiments, the UI (1210) may be displayed on a user terminal device (400).

[0376] Figure 13 is a diagram for explaining the operation of selecting a target IoT device.

[0377] Referring to FIG. 13, the electronic device (100) may provide a screen (1300) related to a target IoT device. When a user input for starting IoT control sharing or a user input for determining a target IoT device is received, the electronic device (100) may provide the screen (1300). The screen (1300) may include at least one of a UI (1310) for guiding selection of a device with which control rights are shared through IoT control sharing, etc., a UI (1320) for explaining a list of connected IoT devices, and a UI (1330) for displaying a list of connected IoT devices.

[0378] Through a UI (1330) displaying a list of connected IoT devices, the electronic device (100) can receive user input for determining target IoT devices. The user can determine whether to grant control to each device through the UI (1330). The UI (1330) can include a UI for selecting all or deselecting all.

[0379] According to various embodiments, the screen (1300) may be displayed on the user terminal device (400).

[0380] Figure 14 is a diagram for explaining the operation of selecting target IoT devices by group.

[0381] Referring to FIG. 14, the electronic device (100) may provide a screen (1400) for determining a target IoT device. The screen (1400) may include at least one of a UI (1410) indicating that it is a screen for determining a target IoT device, a UI (1420) for describing a list of connected IoT devices, a UI (1430) for searching for IoT devices, and a UI (1440) for indicating a list of IoT devices classified by group.

[0382] The UI (1440) that displays a list of IoT devices classified by group may include multiple IoT devices classified by group according to specific criteria. For example, a first group may include a TV, an AI speaker, an air conditioner, lighting, etc. A second group may include a computer, CCTV, etc. The classification criteria for each group may be user-defined. A user may directly classify the groups, and the IoT network may store the classification results. The storage location may be an electronic device (100), a server (300), a user terminal device (400), an AP device (500), etc.

[0383] In various embodiments, the classification criterion may be a security level. Each IoT device may have a pre-set security level. There may be IoT devices with a security level that grants control only to pre-registered users. Additionally, there may be IoT devices with a security level that grants control to temporary users (visitors). The electronic device (100) may pre-classify IoT devices into groups based on their security levels. The first group may include IoT devices with relatively low security levels, and the second group may include IoT devices with relatively high security levels.

[0384] According to various embodiments, the screen (1400) may be displayed on the user terminal device (400).

[0385] According to various embodiments, each group (group 1, group 2) may be distinguished by a space within a home. For example, group 1 may include devices located in a first space (e.g., a living room), and group 2 may include devices located in a second space (e.g., a kitchen). The location of each group may be determined automatically. The electronic device (100) may distinguish the groups of devices using location information of the devices included in the IoT network. The electronic device (100) may provide a screen (1400) using the groups representing the distinguished devices.

[0386] According to various embodiments, each group can be manually determined by the user's settings. The user can pre-determine the groups of devices included in the IoT network. The electronic device (100) can store group information for the devices determined by the user. The electronic device (100) can generate and provide a screen (1400) based on the pre-stored group information.

[0387] Figure 15 is a drawing for explaining the operation of selecting a visitor.

[0388] Referring to FIG. 15, the electronic device (100) may provide a screen (1500) for determining a visitor with whom control will be shared. The screen (1500) may include at least one of a UI (1510) indicating that it is a screen for determining a visitor for control sharing, a UI (1520) indicating contacts, a UI (1530) for searching contacts, and a UI (1540) indicating a list of contacts categorized by group. The contacts may include names, phone numbers, affiliations, addresses, email addresses, etc.

[0389] The UI (1540) representing a list of contacts categorized by group may include multiple contacts categorized by group according to specific criteria. The contact list may be categorized according to specific criteria. The specific criteria may be selected by the user.

[0390] Certain criteria can be categorized by affiliation. For example, affiliation information can be categorized as family, friends, work, or other. If the affiliation information is family or friends, it would be grouped first, while if the affiliation information is work or other, it would be grouped second. The contact list can group multiple contacts based on affiliation information. Based on the grouped contact list, the visitors to whom control is granted can be ultimately determined. Only contacts in group first can be determined as visitors to whom control is granted.

[0391] The electronic device (100) can obtain individual user selections for each contact through a UI (1540) that displays a list of contacts categorized by group. For example, the electronic device (100) can determine whether to grant control over a single contact included in each group. The electronic device (100) may not grant control over some contacts even within the first group.

[0392] According to various embodiments, the screen (1500) may be displayed on the user terminal device (400).

[0393] Figure 16 is a drawing for explaining the operation of selecting a sharing mode.

[0394] Referring to FIG. 16, the electronic device (100) may provide a screen (1600) related to a target function. The electronic device (100) may determine a target function to which control is granted among multiple functions provided by the IoT device. The electronic device (100) may grant control over all of the multiple functions. The electronic device (100) may grant control over only some of the multiple functions. The function to which control is ultimately granted may be described as a target function. The target function may be described as a shared function.

[0395] The electronic device (100) can determine a target function through a screen (1600). It is not necessary to display all functions for an IoT device. The electronic device (100) can provide a screen (1600) that includes only preset functions that need to be selected as target functions. The screen (1600) can include at least one of a UI (1610) for guiding selection of a target function, a UI (1620) for selecting all functions at once, a UI (1630) for selecting a function corresponding to a kids mode, a UI (1640) for selecting a function corresponding to a security mode, a UI (1650) for selecting a function corresponding to an air conditioning mode, and a UI (1650) for selecting / deselecting each function.

[0396] The UI (1610) guiding selection of a target function may include the text 'Please select a function to share'.

[0397] When a user input is received to select a UI (1620) for selecting all functions at once, the electronic device (100) can determine (or select) all functions provided on the screen (1600) as target functions.

[0398] When a user input for selecting a UI (1630) corresponding to a function corresponding to the kids mode is received, the electronic device (100) may determine (or select) the function corresponding to the kids mode as a target function. For example, in the kids mode, the first and third functions of the TV may be selected, and the second function of the TV may not be selected. The UI (1630) may include explanatory information corresponding to the kids board, such as 'Functions that are not accessible to children under the age of 18 are restricted.'

[0399] When a user input for selecting a UI (1640) that selects a function corresponding to a security mode is received, the electronic device (100) can determine (or select) the function corresponding to the security mode as a target function. For example, in the security mode, only functions with a security level lower than a critical level among multiple functions provided by the IoT device can be determined as target functions. The UI (1640) can include descriptive information corresponding to the security mode, such as "Some functions requiring security permissions are restricted."

[0400] When a user input for selecting a function corresponding to an air conditioning mode (1650) is received, the electronic device (100) can determine (or select) only functions related to the air conditioning function as target functions. The UI (1650) can include descriptive information corresponding to the air conditioning mode, such as "Only functions related to air conditioning operation are shared."

[0401] Through the UI (1650) for selecting / deselecting each function, the electronic device (100) can receive user input for selecting / deselecting each individual function.

[0402] According to various embodiments, when a preset event is identified, the electronic device (100) may output an icon related to IoT control sharing. When the output icon is selected by user input, the electronic device (100) may provide a QR code screen related to IoT control sharing. A detailed description of the QR code screen is provided in FIG. 20.

[0403] According to various embodiments, the screen (1600) may be displayed on the user terminal device (400).

[0404] Although Figure 16 describes certain functions as being restricted, control rights for specific devices may be restricted depending on the implementation. Control rights for specific devices corresponding to specific modes may be restricted. For example, control rights for an induction cooktop in the kitchen may be restricted in Kids Mode.

[0405] Depending on the various embodiments, control of only specific devices corresponding to a specific mode may be shared. For example, in air conditioning mode, control of only air conditioning devices within the home may be shared. For example, in visitor music mode, control of only devices capable of sound output within the home may be shared.

[0406] Figure 17 is a drawing for explaining an operation of providing an invitation notification through a text message service.

[0407] Referring to FIG. 17, the electronic device (100) can transmit an invitation notification to the visitor terminal device (200).

[0408] The electronic device (100) may transmit a screen (1700) related to the invitation notification to the visitor terminal device (200). The visitor terminal device (200) may display the screen (1700) related to the invitation notification. The screen (1700) may include at least one of a UI (1710) notifying that a request for sharing control rights for an IoT device has been received, a UI (1720) querying whether to accept the control rights sharing, and a UI (1730) guiding acceptance of the control rights request. The screen related to the invitation notification may be described as a screen for sharing control rights.

[0409] The UI (1710) may include text indicating 'A request to share control of an IoT device has been received.'

[0410] The UI (1720) may include text indicating 'Do you want to start sharing control?'

[0411] The UI (1730) may include URL information for accessing a specific site, such as "Please connect to the link below. https: / www.share-IoT.com." When a user input for selecting a specific URL is received through the UI (1730), the visitor terminal device (200) may transmit the user input to a device (or server) corresponding to the URL. When the user input is obtained through the UI (1730), the electronic device (100) may grant control to the visitor terminal device (200).

[0412] *For example, the electronic device (100) may request the server (300) to transmit an invitation notification to the visitor terminal device (200) via the server (300). The server (300) may transmit the invitation notification to the visitor terminal device (200) in response to the request.

[0413] For example, the electronic device (100) may request the user terminal device (400) to transmit an invitation notification to the visitor terminal device (200) via the user terminal device (400). The user terminal device (400) may transmit the invitation notification to the visitor terminal device (200) in response to the request.

[0414] For example, the electronic device (100) can directly transmit an invitation notification to the visitor terminal device (200).

[0415] Invitation notifications can be provided to the visitor terminal device (200) via a text message function.

[0416] According to various embodiments, the URL information may include a URL for accessing a site that provides services related to control sharing. By accessing a specific URL via the UI (1730), the visitor terminal device (200) may access the site related to control sharing. After accessing the site, the visitor terminal device (200) may additionally obtain information related to control sharing or perform actions related to control sharing.

[0417] According to various embodiments, the URL information may include a URL generated in a state in which the sharing target, target device, target function, and permissions related to the target function are determined. When accessing a specific URL through the UI (1730), the visitor terminal device (200) can immediately access a webpage for accepting control sharing. The URL may indicate that the sharing target, target device, target function, and permissions related to the target function are determined, such as https: / www.share-IoT.com / user2 / galaxyS23 / TV.

[0418] Figure 18 is a drawing for explaining an operation of providing an invitation notification.

[0419] Referring to FIG. 18, the visitor terminal device (200) may display a screen (1800) related to an invitation notification. The screen (1800) related to an invitation notification may include at least one of a UI (1810) notifying that a request for sharing control rights for an IoT device has been received, a UI (1820) querying whether to accept sharing control rights, and a UI (1830) guiding a response to the control rights request. The UI (1810) and the UI (1820) may correspond to the UI (1710) and the UI (1720) of FIG. 17. Duplicate descriptions will be omitted.

[0420] The UI (1830) may include at least one of the user information that sent the invitation notification related to control sharing and a UI for responding. The user information may include at least one of the user's name, the user's contact information (phone number), and the user's account. The user information allows visitors to easily recognize who sent the invitation notification.

[0421] Figure 19 is a drawing for explaining an operation of accepting an invitation notification through the NFC function.

[0422] Referring to FIG. 19, the visitor terminal device (200) may display a screen (1900) related to an invitation notification. The screen (1900) related to an invitation notification may include at least one of a UI (1910) notifying that a request for sharing control rights for an IoT device has been received, a UI (1920) inquiring whether to accept sharing control rights, a UI (1930) guiding a response to a request for control rights, and a UI (1940) indicating a response method. The UI (1910) and the UI (1920) may correspond to the UI (1710) and the UI (1720) of FIG. 17. Duplicate descriptions will be omitted.

[0423] The electronic device (100) and the visitor terminal (200) may be connected via a short-range communication method. The short-range communication method may be NFC communication. The electronic device (100) and the visitor terminal (200) may exchange information via the NFC method. The visitor terminal (200) may transmit a response to an invitation notification via the NFC function. The transmitted response may include identification information of the visitor terminal (200). The identification information may be transmitted to the electronic device (100) via NFC. The electronic device (100) may use the received identification information to determine whether to grant control to the visitor terminal (200). The electronic device (100) may provide a guide screen for NFC tagging to the visitor terminal (200).

[0424] The UI (1930) may be a UI that includes a guide action for accepting a control request. The UI (1930) may include text indicating, "Please turn on the NFC function of the terminal device and tag the terminal device to the TV."

[0425] The UI (1940) may be a UI that guides a visitor to perform a specific action for an NFC tag. A communication module performing NFC functions in an electronic device (100) may be placed in a specific area of ​​the electronic device (100). The UI (1940) may include information that guides the placement location of the communication module for the NFC function.

[0426] For example, when a visitor terminal device (200) is tagged to an electronic device (100), identification information of the visitor terminal device (200) may be transmitted to the electronic device (100). The electronic device (100) may provide the identification information of the visitor terminal device (200) as a guide screen. A user of the electronic device (100) may use the identification information of the visitor terminal device (200) to determine whether to grant control authority.

[0427] For example, when a user input is received to grant control authority to a visitor terminal device (200), the electronic device (100) can share control authority with the visitor terminal device (200).

[0428] The electronic device (100) can transmit temporary AP information or MAC address (Media Access Control Address) information to the visitor terminal device (200) using the NFC function.

[0429] The visitor terminal device (200) can transmit temporary AP information or MAC address (Media Access Control Address) information to the electronic device (100) using the NFC function.

[0430] Information transmitted and received between the electronic device (100) and the visitor terminal device (200) may change depending on the situation.

[0431] The electronic device (100) and the visitor terminal (200) can compare previously shared information with information received via the NFC function to determine reliability. If the information received via the NFC function is identical to previously stored reference information (shared information), the electronic device (100) can share control with the visitor terminal (200).

[0432] According to various embodiments, at least one of UI (1930) and UI (1940) may be displayed on the electronic device (100).

[0433] Figure 20 is a drawing for explaining the operation of accepting an invitation notification via a QR code.

[0434] Referring to FIG. 20, the electronic device (100) may provide a screen (2000) for invitation notification. The screen (2000) may include at least one of a UI (2010) for notifying IoT control sharing, a UI (2020) for indicating a guide operation related to IoT control sharing, and a UI (2030) for indicating a QR code related to the invitation notification.

[0435] The electronic device (100) can send an invitation notification to a visitor by providing a screen (2000). The visitor can access the IoT network using the information contained in the screen (2000).

[0436] The UI (2020) may include text guiding the user to scan the QR code.

[0437] The UI (2030) may include a QR code. A visitor may capture a QR code displayed on the screen (2000) using a camera included in the visitor terminal (200). The visitor terminal (200) may receive an invitation notification from the electronic device (100) using the QR code included in the captured image.

[0438] The QR code may include at least one of the following: invitation notification information or AP information. The AP information may include information for connection to the AP device (500) or information related to a temporary AP. The QR code may include a URL for a specific website for connecting to the IoT network. When the QR code is recognized, the visitor terminal device (200) can access the specific website. Upon accessing the specific website, the electronic device (100) may receive an invitation notification.

[0439] The UI (2030) may include a remaining time for the QR code to be displayed. When the remaining time displayed in the UI (2030) has elapsed, the electronic device (100) may no longer display the already displayed QR code.

[0440] The electronic device (100) can regenerate and display the QR code when the visitor terminal device (200) reconnects.

[0441] The UI (2030) may include a UI indicating regeneration of a QR code. When a user input for regenerating a QR code is received through the UI (2030), the electronic device (100) may regenerate the QR code.

[0442] According to various embodiments, the UI (2010) and UI (2020) may be displayed on a visitor terminal device (200).

[0443] Figure 21 is a drawing for explaining the operation of accepting an invitation notification through a watermark.

[0444] Referring to FIG. 21, the electronic device (100) may provide a screen including a watermark (2101) for an invitation notification. The electronic device (100) may request an image captured by a connected visitor terminal device (200). The electronic device (100) may analyze the captured image received from the visitor terminal device (200) and determine whether to transmit an invitation notification to the visitor terminal device (200).

[0445] The visitor terminal device (200) can capture a screen provided through the electronic device (100) in real time. The visitor terminal device (200) can transmit the captured image in real time to the electronic device (100). The electronic device (100) can determine whether the image received from the visitor terminal device (200) includes a watermark (2101).

[0446] If a preset watermark (2101) is included in an image received from a visitor terminal device (200), the electronic device (100) can transmit an invitation notification to the visitor terminal device (200).

[0447] If the preset watermark (2101) is not included in the image received from the visitor terminal device (200), the electronic device (100) may not transmit an invitation notification to the visitor terminal device (200).

[0448] According to various embodiments, the watermark (2101) may not be present on all screens provided by the electronic device (100). The electronic device (100) may sequentially include multiple screens (2110, 2120, 2130, 2140). The electronic device (100) may provide screens in which the watermark (2101) is inserted at regular time intervals in the sequential screens. For example, the screens at times t=1 and t=3 may include the watermark (2101), but the screens at times t=2 and t=4 may not include the watermark (2101).

[0449] Although t=1, 2, 3, 4 is written as an example, it can be implemented in various time units. Time units can be s, ms, us, etc.

[0450] The time interval may be a unit of time that is difficult to visually perceive for a typical user. However, it may be a unit of time that can be recognized by an image sensor (e.g., a camera).

[0451] The electronic device (100) can analyze multiple images acquired from the visitor terminal device (200) to determine whether the watermark (2101) is displayed at preset time intervals. If the multiple images acquired from the visitor terminal device (200) are analyzed and it is determined that the watermark (2101) is displayed at preset time intervals, the electronic device (100) can transmit an invitation notification to the visitor terminal device (200).

[0452] The watermark (2101) may be included in a preset area among multiple screens provided by the electronic device (100). The electronic device (100) may create (or edit) screens (2110, 2120, 2130, 2140) so that the watermark (2101) is included in the preset area. The screens (2110, 2120, 2130, 2140) may include images related to content provided by the electronic device (100) and watermarks (2101) added to the images. The electronic device (100) may add watermarks (2101) to existing content.

[0453] The electronic device (100) can determine whether a preset watermark is included in a preset area in a photographed image received from a visitor terminal device (200).

[0454] Figure 22 is a drawing for explaining the contact confirmation operation.

[0455] Referring to FIG. 22, upon receiving an invitation notification, the visitor terminal (200) may transmit identification information to the electronic device (100). The identification information may include at least one of a contact number and an account. The visitor terminal (200) may encrypt the identification information using a preset method (or preset key). The visitor terminal (200) may transmit the encrypted identification information to the electronic device (100).

[0456] The electronic device (100) can obtain the contact information (2220) of the visitor terminal device (200). The electronic device (100) can determine whether the contact information (2220) of the visitor terminal device (200) is a pre-stored contact information based on the pre-stored contact list (2210).

[0457] A pre-stored contact list (2210) can be stored in the electronic device (100). The electronic device (100) can identify whether the pre-stored contact list (2210) includes a contact (2220) of the visitor terminal device (200).

[0458] The pre-stored contact list (2210) may be stored in the server (300). The electronic device (100) may transmit the contact information (2220) of the visitor terminal device (200) to the server (300). The server (300) may identify whether the contact information (2220) of the visitor terminal device (200) is included in the pre-stored contact list (2210). The server (300) may transmit the identification result to the electronic device (100).

[0459] The pre-stored contact list (2210) may be stored in the user terminal device (400). The electronic device (100) may transmit the contact information (2220) of the visitor terminal device (200) to the user terminal device (400). The user terminal device (400) may identify whether the contact information (2220) of the visitor terminal device (200) is included in the pre-stored contact list (2210). The user terminal device (400) may transmit the identification result to the electronic device (100).

[0460] If the contact information (2220) of the visitor terminal device (200) is included in the previously saved contact list (2210), the electronic device (100) can approve an AP connection for the visitor terminal device (200).

[0461] If the contact (2220) of the visitor terminal device (200) is not included in the previously stored contact list (2210), the electronic device (100) may not approve the AP connection to the visitor terminal device (200).

[0462] According to various embodiments, the visitor terminal device (200) may transmit only some of its contact numbers to the electronic device (100). The electronic device (100) may request only information according to a preset method (location, number of digits, etc.) from the visitor terminal device (200) among the contact numbers.

[0463] For example, the electronic device (100) may request the visitor terminal (200) to transmit only the last four digits of a plurality of numbers included in a contact. The visitor terminal (200) may, in response to the request of the electronic device (100), transmit only the last four digits of its contact to the electronic device (100).

[0464] The electronic device (100) and visitor terminal device (200) can increase data transmission and processing efficiency by checking some numbers rather than all numbers of a contact.

[0465] Figure 23 is a drawing for explaining the screen displayed when contact verification fails.

[0466] Referring to FIG. 23, if the contact information of the visitor terminal device (200) is not included in the pre-stored contact list, the visitor terminal device (200) may display a screen (2300). The screen (2300) may be displayed on the visitor terminal device (200) that has failed to verify the contact information. The screen (2300) may be transmitted from the electronic device (100).

[0467] The screen (2300) may include at least one of a UI (2310) for notifying that an IoT network cannot be accessed, a UI (2320) for indicating a guide operation for accessing an IoT network, and a UI (2330) for guiding user input.

[0468] The UI (2320) may include text indicating that permission must be obtained to access the IoT network. The UI (2320) may include text requesting an inquiry from the user.

[0469] The UI (2330) may be a UI for entering a password for accessing an IoT network. When a user input including a password is received through the UI (2330), the visitor terminal device (200) may transmit the user input including the password to the electronic device (100). The electronic device (100) may verify the password and determine whether to connect to the AP for the visitor terminal device (200). If the password matches a preset password, the electronic device (100) may approve the AP connection for the visitor terminal device (200).

[0470] According to various embodiments, the screen (2300) may be displayed on an electronic device (100) rather than a visitor terminal device (200).

[0471] According to various embodiments, if the contact of the visitor terminal device (200) is not included in the pre-stored contact list, the electronic device (100) may terminate IoT control sharing.

[0472] According to various embodiments, if the contact information of the visitor terminal device (200) is not included in the pre-stored contact list, the electronic device (100) may reject the AP connection to the visitor terminal device (200) and maintain a standby state. The standby state may be a state in which it is checked whether another device is accessing the IoT network.

[0473] Figure 24 is a drawing to explain the screen displayed when contact verification fails.

[0474] Referring to FIG. 24, when an event related to a failure in control sharing is identified, the electronic device (100) may provide a screen (2400).

[0475] Events related to failure to share control rights may be one of the following: a contact unconfirmed event, a sharing rejection event, or a sharing non-response event. A contact unconfirmed event may be an event in which the contact of the visitor terminal device (200) is not included in the previously stored contact list. A sharing rejection event may be an event in which a signal indicating an invitation rejection is received from the visitor terminal device (200). A sharing non-response event may be an event in which no response is received within a preset period of time from the time an invitation notification is sent.

[0476] The screen (2400) may include at least one of a UI (2410) for notifying that control over an IoT device has not been shared, a UI (2420) for indicating information about a visitor terminal device (200), a UI (2430) for indicating a reason for a sharing failure, and a UI (2440) for indicating a guide operation related to a sharing failure.

[0477] The UI (2410) may include text indicating to the visitor terminal device (200) that control over the IoT device has not been ultimately shared.

[0478] The UI (2420) may include identification information indicating the visitor terminal device (200) that failed to share control. The UI (2420) may include at least one of a name, contact information, and an account corresponding to the visitor terminal device (200).

[0479] The UI (2430) may include a reason for the sharing failure. The reason for the sharing failure may include at least one of unregistered contact, refusal to share, and unresponsive sharing. In FIG. 24, it is assumed that the reason for the sharing failure corresponds to unregistered contact. The electronic device (100) may provide a UI (2440) that includes a guide action corresponding to unregistered contact.

[0480] The UI (2440) may include text indicating a guide action corresponding to the reason for the sharing failure. The UI (2440) may include at least one of the following actions: adding a contact of the visitor terminal device (200), temporarily granting (or sharing) control over the visitor terminal device (200), directly entering an account (or email), and generating a QR code. When a user input corresponding to each action is received, the electronic device (100) may perform a guide action corresponding to the user input.

[0481] According to various embodiments, the screen (2400) may be displayed on the user terminal device (400).

[0482] Figure 25 is a drawing for explaining the screen displayed when contact verification fails.

[0483] Referring to FIG. 25, when an event related to a failure in control sharing is identified, the electronic device (100) may provide a screen (2500).

[0484] The screen (2500) may include at least one of a UI (2510) for notifying that control over an IoT device has not been shared, a UI (2520) for indicating information about a visitor terminal device (200), a UI (2530) for indicating a reason for a sharing failure, and a UI (2540) for indicating a guide operation related to a sharing failure.

[0485] UI (2510), UI (2520), and UI (2530) may correspond to UI (2410), UI (2420), and UI (2430) of FIG. 24. Duplicate descriptions are omitted. Unlike FIG. 24, it is assumed in FIG. 25 that the reason for sharing failure is non-response to sharing. The electronic device (100) may provide UI (2540) including a guide action corresponding to non-response to sharing.

[0486] The UI (2540) may include text indicating a guide operation corresponding to the reason for the sharing failure. The UI (2540) may include at least one of an operation of transmitting a sharing request to the visitor terminal device (200) as a BLE packet, an operation of transmitting a sharing request as an SMS text message, and an operation of transmitting an NFC tag request. When a user input corresponding to each operation is received, the electronic device (100) may perform a guide operation corresponding to the user input. The operation related to the NFC tag request is described in FIG. 19.

[0487] According to various embodiments, the electronic device (100) may perform a first operation of transmitting an invitation notification as a BLE packet. If a sharing failure event is identified after performing the first operation, the electronic device (100) may perform a second operation of retransmitting a sharing request as an SMS text message. If a sharing failure event is identified after performing the second operation, the electronic device (100) may perform a third operation of transmitting an NFC tag request.

[0488] The order of the first, second, and third actions may be changed depending on the implementation example.

[0489] According to various embodiments, the screen (2500) may be displayed on the user terminal device (400).

[0490] Figure 26 is a diagram for explaining the operation of adding a target IoT device to visitor account information.

[0491] Referring to FIG. 26, when contact verification for the visitor terminal device (200) is completed, the electronic device (100) can approve the AP connection for the visitor terminal device (200). The electronic device (100) can share control over connectable IoT devices with the visitor terminal device (200).

[0492] The electronic device (100) can obtain a list of connectable IoT devices (2610). The electronic device (100) can share control over IoT devices included in the list of connectable IoT devices (2610) with the visitor terminal device (200).

[0493] The electronic device (100) can add (or update) control rights for IoT devices included in the list of connectable IoT devices (2610) to visitor account information (2620). The visitor account information (2620) may be an account corresponding to the visitor terminal device (200). When control rights are added to the visitor account information (2620), IoT devices can be controlled through the visitor account information (2620). When the visitor terminal device (200) is connected to the AP through the visitor account information (2620), the visitor terminal device (200) can directly control the IoT devices added to the visitor account information (2620).

[0494] A list of connectable IoT devices (2610) may be stored in at least one of an electronic device (100), a server (300), and a user terminal device (400).

[0495] The list of connectable IoT devices (2610) may include at least one of identification information and signal strength for each IoT device. The identification information may be information representing each IoT device. The signal strength may indicate the communication connection strength of each IoT device in the IoT network. The higher the signal strength level, the higher the connection strength. For example, the signal strength of a TV (#01) may be level 5, the signal strength of a refrigerator (#02) may be level 5, the signal strength of an air conditioner (#03) may be level 3, the signal strength of an AI speaker (#04) may be level 4, and the signal strength of a light (#05) may be level 1.

[0496] The electronic device (100) can determine a target IoT device based on signal strength. Among at least one IoT device included in the list of connectable IoT devices (2610), only IoT devices with a signal strength greater than or equal to a threshold level can be determined as target IoT devices. It is assumed that the threshold level is the second level. Only when the signal strength is greater than or equal to the second level can the device be determined as a target IoT device. For example, if the signal strength of the light (#05) is the first level, the light (#05) may not be included as a target IoT device.

[0497] The electronic device (100) can obtain visitor account information (2620). The visitor account can be described as information related to the visitor's account or information corresponding to the visitor account. Information related to the visitor account can be stored in the server (300). The electronic device (100) can receive information related to the visitor account through the server (300). The electronic device (100) can obtain and store visitor account information (2620) to which a target IoT device is added.

[0498] When visitor account information (2620) is stored in the electronic device (100), the electronic device (100) can transmit the visitor account information (2620) to at least one of the visitor terminal device (200), the server (300), the user terminal device (400), and the AP device (500). When the visitor terminal device (200) is connected to the IoT network, the visitor terminal device (200) can control the target IoT device based on the visitor account information (2620).

[0499] Figure 27 is a drawing to explain the screen displayed when account verification fails.

[0500] Referring to FIG. 27, the electronic device (100) may request the visitor terminal device (200) to transmit an account related to the IoT network.

[0501] If account information exists, the visitor terminal device (200) can transmit the visitor's account (or visitor account information) to the electronic device (100). The electronic device (100) can perform a verification operation on the visitor's account received from the visitor terminal device (200).

[0502] If account information does not exist, the visitor terminal device (200) may not transmit the visitor's account (or visitor account information) to the electronic device (100) or may transmit only null data.

[0503] If a visitor account is not already registered, the electronic device (100) may provide a screen (2700). If a visitor account is not already registered, the electronic device (100) may create a temporary account.

[0504] The electronic device (100) can check whether the visitor account received from the visitor terminal device (200) is already registered. If the visitor account is not already registered, the electronic device (100) can create a temporary account (or temporary account information). The electronic device (100) can create a temporary account based on the contact information of the visitor terminal device (200).

[0505] The screen (2700) may include at least one of a UI (2710) indicating that a visitor account is not already registered, a UI (2720) indicating that a temporary account is to be created, a UI (2730) indicating a temporary account, a UI (2740) indicating a description related to the temporary account, a UI (2750) guiding the creation of a formal account, and a UI (2760) guiding the search for a formal account.

[0506] The screen (2700) may be a screen displayed when an account related to the visitor terminal device (200) has not been previously registered.

[0507] The UI (2710) may include text indicating 'Visitor's account not found'.

[0508] The UI (2720) may include text indicating 'A temporary account has been created'.

[0509] The UI (2730) may include a created temporary account.

[0510] The UI (2740) may include text indicating, "Temporary accounts will be automatically deleted when IoT control sharing ends" or "Regular account registration is required." The electronic device (100) may delete the created temporary account when IoT control sharing ends.

[0511] The UI (2750) may be a guide UI for creating a formal account. When user input is received through the UI (2750), the electronic device (100) may provide a screen for creating a formal account.

[0512] The UI (2760) may be a guide UI for searching for a formal account. When a user input is received through the UI (2760), the electronic device (100) may provide a screen for searching for a formal account.

[0513] According to various embodiments, the screen (2700) may be displayed on the user terminal device (400).

[0514] According to various embodiments, the electronic device (100) may create a temporary account based on a device name corresponding to the visitor terminal device (200). The device name may include a model number, nickname, temporary device number, etc. that represent the visitor terminal device (200).

[0515] Figure 28 is a drawing for explaining an operation of sharing image content.

[0516] Referring to FIG. 28, the electronic device (100) may include a display (140).

[0517] According to an embodiment (2810), the electronic device (100) can display an image provided by at least one terminal device (210, 220) on the display (140). The at least one terminal device (210, 220) may be a device connected to an IoT network. The at least one terminal device (210, 220) may be a device connected to an AP. The at least one terminal device (210, 220) may be a device granted control over the electronic device (100).

[0518] At least one of the terminal devices (210, 220) can transmit a shared image (2800) to the electronic device (100).

[0519] The electronic device (100) can receive a shared image (2800) from one of the terminal devices (210, 220). The electronic device (100) can display the received shared image (2800) on the display (140). One device (210) can display the shared image (2800) on the display of one device (210). One device (210) and the electronic device (100) can display the same shared image (2800). The above-described operation can be described as an image sharing function or a content sharing function. The electronic device (100) and one device (210) can display the shared image simultaneously.

[0520] According to various embodiments, the shared image (2800) displayed identically may also be displayed on the remaining devices (220). An IoT network including an electronic device (100) may transmit the shared image (2800) to the remaining devices (220) via an AP connection.

[0521] Depending on the various embodiments, the remaining devices (220) may not display the same shared image (2800).

[0522] One device (210) may be described as a first device or a first connecting device, and the other device (220) may be described as a second device or a second connecting device.

[0523] According to various embodiments, the electronic device (100) may display icons (2810, 2820) representing AP-connected devices on the shared image (2800). The icons may be image data representing a specific device. For example, the icons may include avatars representing the specific device. The electronic device (100) may provide a screen that adds icons (2810, 2820) representing AP-connected devices to the shared image (2800).

[0524] According to various embodiments, the icons (2810, 2820) may be displayed only on the screen provided by the electronic device (100) and may not be displayed on the devices (210, 220).

[0525] According to various embodiments, the icons (2810, 2820) may be displayed on all devices (100, 210, 220). To this end, the electronic device (100) may transmit information including the icons (2810, 2820) and the display positions of the icons to the devices (210, 220).

[0526] According to an embodiment (2820), an image (2800) displayed on one device (210) may be different from an image (2801) displayed on the remaining devices (220). If the screens displayed on each device are different, the electronic device (100) may select one device. The electronic device (100) may display the image displayed on the selected device. In the embodiment (2820), it is indicated that the electronic device (100) has selected one device (210).

[0527] The icons described in Figure 28 can be replaced with a GUI (Graphical User Interface). The GUI may include at least one of a moving icon, an avatar, or an emoticon. The GUI may be implemented in a form that moves on the screen. For example, the GUI may include a moving emoticon.

[0528] Figure 29 is a drawing for explaining an operation of sharing audio content.

[0529] Referring to FIG. 29, an IoT network (1000) may include IoT devices (100, 100-2, 100-3, 100-4). It is assumed that a first device (210) and a second device (220) are connected to the IoT network (1000) via an AP. The first device (210) or the second device (220) may be a device that has shared control over the IoT devices (100, 100-2, 100-3, 100-4). When a user input is obtained by at least one of the first device (210) or the second device (220), the IoT devices (100, 100-2, 100-3, 100-4) may perform a function corresponding to the user input.

[0530] At least one of the IoT devices (100, 100-2, 100-3, 100-4) may include a speaker and output content corresponding to user input through the speaker. The content may include audio data. For example, the content may include music data.

[0531] When a first user input is acquired through the first device (210), the IoT device (100, 100-2, 100-3, 100-4) can perform an action corresponding to the first user input.

[0532] When a second user input is acquired through a second device (220), the IoT device (100, 100-2, 100-3, 100-4) can perform an action corresponding to the second user input.

[0533] The first user input and / or the second user input may include commands for controlling one IoT device.

[0534] The first user input may include a command for outputting first content from the electronic device (100). Based on the first user input, the electronic device (100) may output the first content. The first device (210) may transmit the first content to the electronic device (100).

[0535] The second user input may include a command to output second content from the IoT device (100-2). Based on the second user input, the IoT device (100-2) may output the second content. The second device (220) may transmit the second content to the IoT device (100-2).

[0536] The action of transmitting content may include either transmitting to each IoT device via an AP or transmitting via a direct connection between devices. The IoT devices (100, 100-2, 100-3, 100-4) may be devices including speakers for outputting audio data.

[0537] Figure 30 is a drawing for explaining the operation of sharing game content.

[0538] Referring to FIG. 30, the electronic device (100) may include a display (140). The visitor terminal (200) may also include its own display. The electronic device (100) may provide shared content with the visitor terminal (200) connected to the AP.

[0539] Referring to Example 3001, an electronic device (100) and a visitor terminal device (200) can perform operations related to a single content. The single content may be a game. The electronic device (100) and a visitor terminal device (200) connected to an AP can perform operations related to the content. The electronic device (100) can provide a screen (3010) related to the game. The visitor terminal device (200) can provide a screen (3020) related to game operation.

[0540] A screen (3020) related to game operation may include an interface for user operation. The screen (3020) may include a UI representing a game pad. The screen (3020) may include at least one UI representing an operation button. Through the screen (3020), the visitor terminal device (200) may receive user input. Based on the location where the user input is received, the visitor terminal device (200) may determine whether a specific button has been selected. The electronic device (100) may provide a screen (3010) to which the received user input is applied.

[0541] For example, when a user input is received in an area indicating a first button, the visitor terminal device (200) can transmit operation information indicating that the first button has been selected to the electronic device (100). The electronic device (100) can provide a screen (3010) reflecting an operation corresponding to the received first button.

[0542] For example, the entity that updates the game screen based on user input may be an electronic device (100). The electronic device (100) may generate the game screen on its own.

[0543] For example, an entity that updates a game screen based on user input may be an external device. The external device may refer to a game console, etc. The electronic device (100) may transmit user input (or operation command) obtained from the visitor terminal device (200) to the external device. The external device may provide the electronic device (100) with an updated game screen based on the user input. The electronic device (100) may receive the updated game screen through the external device. The electronic device (100) may display the updated game screen. The external device may be implemented as a server (300) or a game server, etc.

[0544] Referring to Example (3002), the game screens displayed on the electronic device (100), the terminal device (210), and the terminal device (220) may be different. The electronic device (100) may be connected to multiple terminal devices. The multiple terminal devices may play a single common game. For example, assume a poker game.

[0545] Terminal devices (210, 220) can play a common game using the electronic device (100). The electronic device (100) can display a common screen (3030). The terminal device (210) can display a screen (3040) corresponding to the terminal device (210), and the terminal device (220) can display a screen (3050) corresponding to the terminal device (220). The common screen (3030) may not reveal all of the opponent's cards. On the screens displayed on each terminal device, all of the player's cards may be revealed.

[0546] Figure 31 is a drawing for explaining the operation of deleting control.

[0547] Referring to FIG. 31, the electronic device (100) may provide a screen (3100) related to the termination of IoT control sharing. The screen (3100) may include at least one of a UI (3110) indicating the termination of IoT control sharing, a UI (3120) for explaining a guide operation related to the deletion of control rights, and a UI (3130) for deleting control rights for each visitor.

[0548] The UI (3110) may include text indicating 'End IoT control sharing'.

[0549] The UI (3120) may include text indicating 'Please select the terminal device from which you wish to delete control.'

[0550] UI (3130) may be a UI for deleting control rights for a visitor's terminal device with which control rights are shared. If the visitor has multiple terminal devices, UI (3130) may include a UI for deleting control rights for each of the multiple terminal devices. Through UI (3130), the user can decide whether to delete control rights for each of the visitor's terminal devices. When IoT control sharing ends, the electronic device (100) may simultaneously delete control rights for all multiple visitors.

[0551] According to various embodiments, the screen (3100) may be displayed on the user terminal device (400).

[0552] According to various embodiments, when a command to delete control rights for a target IoT device is obtained through the UI (3130), the electronic device (100) may transmit information to the visitor's terminal device to notify the deletion of control rights. The visitor's terminal device may output the received information. The visitor (or user) may be informed of the deletion of control rights through the output information. The target IoT device may include multiple IoT devices.

[0553] According to various embodiments, when a command to delete control rights for an IoT device is obtained through the UI (3130), the electronic device (100) may delete control rights for the IoT device. Information notifying the deletion of control rights may also be transmitted to only one IoT device.

[0554] While the control sharing feature remains active, control sharing for a specific device can be terminated. For example, control sharing may be stopped (or suspended) for only one of multiple devices. The electronic device (100) may terminate control sharing for only one device based on user input. Control sharing may still be maintained for the remaining devices.

[0555] Figure 32 is a drawing for explaining a screen related to the termination of IoT control sharing.

[0556] Referring to FIG. 32, the electronic device (100) may provide a screen (3200) related to the termination of IoT control sharing. The screen (3200) may include at least one of a UI (3210) indicating the termination time of IoT control sharing, a UI (3220) for notifying that control rights are automatically deleted, a UI (3230) indicating a set time for which IoT control sharing is maintained, a UI (3240) indicating the current time and / or remaining time, a UI (3250) for requesting an extension of the set time, a UI (3260) indicating a target IoT device, and a UI (3270) indicating an uncontrollable IoT device.

[0557] The UI (3210) may include text indicating 'IoT control sharing will only be maintained during the following times'.

[0558] The UI (3220) may include text indicating 'Control will be automatically deleted after the set time has elapsed'.

[0559] The UI (3230) may include the setup time of IoT control sharing currently set in the electronic device (100).

[0560] The UI (3240) may include at least one of the current time or the remaining time until IoT control sharing ends.

[0561] The UI (3250) may be a UI that receives user input to request an extension of the set time.

[0562] The UI (3260) may include target IoT devices with shared control rights. Through the UI (3260), the electronic device (100) may receive user input for extending or deleting (terminating) control rights for each target IoT device.

[0563] The UI (3270) may include non-target IoT devices with which control is not shared.

[0564] According to various embodiments, the screen (3200) may be displayed on the user terminal device (400).

[0565] Figure 33 is a flowchart explaining the operation in which AP information is included in a BLE packet.

[0566] Steps S3305, S3310, S3315, S3320, S3326, S3327, S3330, S3331, S3332, S3335, S3336, S3337, S3340, S3341, S3350, S3351, S3352, S3355, S3356, S3357 of FIG. 33 may correspond to steps S705, S710, S715, S720, S726, S727, S730, S731, S732, S735, S736, S737, S740, S741, S750, S751, S752, S755, S756, S757 of FIG. 23 will be omitted.

[0567] In step S725 of FIG. 7, it is described that the electronic device (100) transmits a BLE communication packet to the visitor terminal device (200). In addition, in step S740 of FIG. 7, it is described that the electronic device (100) transmits AP information to the visitor terminal device (200).

[0568] In the embodiment of FIG. 33, the electronic device (100) can generate a BLE communication packet including AP information. The electronic device (100) can transmit the BLE communication packet including AP information to the visitor terminal device (200) (S3325).

[0569] The electronic device (100) can broadcast AP information in advance along with an invitation notification. Transmitting AP information in advance can shorten the time required for future AP connection.

[0570] If it is determined that the contact information of the visitor terminal device (200) is already stored (S3335-Y), the electronic device (100) can transmit a signal approving AP connection to the visitor terminal device (200) (S3340).

[0571] When connection authority for the visitor terminal device (200) is confirmed (S3337-Y), the electronic device (100) can transmit a signal approving AP connection to the visitor terminal device (200) (S3340).

[0572] The visitor terminal device (200) can perform AP connection using pre-received AP information.

[0573] Figure 34 is a flowchart for explaining the operation of performing contact verification and account verification in an electronic device (100).

[0574] Steps S3405, S3410, S3415, S3420, S3425, S3426, S3427, S3435, S3436, S3437, S3440, S3441, S3455, S3456, S3457 of FIG. 34 may correspond to steps S705, S710, S715, S720, S725, S726, S727, S735, S736, S737, S740, S741, S755, S756, S757 of FIG. 24. Duplicate explanations are omitted.

[0575] In the embodiment of FIG. 7, it is described that the contact verification operation is performed in the user terminal device (400) and the account verification operation is performed in the server (300).

[0576] In the embodiment of FIG. 34, a contact verification operation and an account verification operation can be performed on the electronic device (100). The electronic device (100) may store a contact list and an account list in advance.

[0577] After receiving a contact from a visitor terminal device (200), the electronic device (100) can determine whether the contact of the visitor terminal device (200) is included in a previously stored contact list (S3431).

[0578] After receiving an account from a visitor terminal device (200), the electronic device (100) can determine whether the account of the visitor terminal device (200) is included in a list of previously stored accounts (S3451).

[0579] Figure 35 is a flowchart for explaining an operation in which contact verification is performed on a user terminal device (400) and account verification is performed on an electronic device (100).

[0580] Steps S3505, S3510, S3515, S3520, S3525, S3526, S3527, S3530, S3531, S3532, S3535, S3536, S3537, S3540, S3541, S3555, S3556, S3557 of FIG. 35 may correspond to steps S705, S710, S715, S720, S725, S726, S727, S730, S731, S732, S735, S736, S737, S740, S741, S755, S756, S757 of FIG. 7. Duplicate explanations are omitted.

[0581] In the embodiment of FIG. 7, the account verification operation is performed on the server (300). In the embodiment of FIG. 35, the account verification operation can be performed directly on the electronic device (100).

[0582] The electronic device (100) may pre-store an account list. The electronic device (100) may request the account list from the server (300) in advance and receive the account list from the server (300). The electronic device (100) may pre-store the account list.

[0583] After the visitor terminal device (200) is connected to the AP, the electronic device (100) can check whether the account of the visitor terminal device (200) is included in the list of previously stored accounts (S3355).

[0584] According to various embodiments, the account verification operation may be performed on the server (300) and the contact verification operation may be performed on the electronic device (100).

[0585] Figure 36 is a flowchart for explaining the operation of performing contact verification and account verification on the server (300).

[0586] *Steps S3605, S3610, S3615, S3620, S3625, S3626, S3627, S3635, S3636, S3637, S3640, S3641, S3650, S3651, S3652, S3655, S3656, S3657 of FIG. 36 may correspond to steps S705, S710, S715, S720, S725, S726, S727, S735, S736, S737, S740, S741, S750, S751, S752, S755, S756, S757 of FIG. 7. Duplicate explanations are omitted.

[0587] In Fig. 7, the contact confirmation operation is described as being performed on a user terminal device (400). In Fig. 36, the contact confirmation operation can be performed on a server (300).

[0588] The electronic device (100) may request the server (300) to confirm contact information (S3630). The electronic device (100) may transmit the contact information of the visitor terminal (200) and a control command for contact information confirmation to the server (300).

[0589] The server (300) can verify the received contact information (S3631). The server (300) can verify the contact information based on a previously stored contact list. The server (300) can identify the user account of the electronic device (100). The server (300) can obtain a contact list mapped to the user account of the electronic device (100). The electronic device (100) can obtain a contact list corresponding to the user account. The electronic device (100) can determine whether the contact information of the received visitor terminal device (200) is included in the contact list of the user account.

[0590] The server (300) can obtain the contact verification result. The server (300) can transmit the contact verification result to the electronic device (100) (S3632).

[0591] Figure 37 is a flowchart for explaining the operation of performing IoT control sharing using only contacts.

[0592] Steps S3705, S3710, S3715, S3720, S3725, S3726, S3730, S3731, S3732, S3735, S3736, S3737, S3740, S3741 of FIG. 37 may correspond to steps S705, S710, S715, S720, S725, S726, S730, S731, S732, S735, S736, S737, S740, S741 of FIG. 7. Duplicate explanations are omitted.

[0593] Figure 7 describes an operation for verifying account information. In the embodiment of Figure 37, control can be shared immediately without verifying account information.

[0594] The visitor terminal device (200) may transmit contact information to the electronic device (100) in response to the BLE packet (S3727). Unlike the embodiment of FIG. 7, account information may not be present in the response packet.

[0595] After the visitor terminal device (200) is connected to the AP, the electronic device (100) can share control over the IoT device with the visitor terminal device (200) (S3757).

[0596] Figure 38 is a flowchart for explaining a control method of an electronic device (100) according to one embodiment.

[0597] Referring to FIG. 38, a method for controlling an electronic device included in an IoT (Internet of Things) network includes, when a user input for sharing control over an IoT network is received, a step of determining a target IoT device to share control with among at least one IoT device included in the IoT network (S3805), a step of broadcasting a communication packet for sharing control with a terminal device (S3810), a step of receiving contact information from a terminal device in response to the communication packet (S3815), and a step of sharing control with a terminal device corresponding to the contact information when the received contact information is included in a pre-stored contact list (S3820).

[0598] The step of broadcasting a communication packet can broadcast the communication packet using BLE (Bluetooth Low Energy) communication.

[0599] The control method may further include a step of acquiring AP (Access Point) information corresponding to an IoT network and a step of transmitting the AP information to a terminal device when the received contact information is included in a pre-stored contact list.

[0600] The control method may further include a step of providing a guide UI (User Interface) for confirming connection authority of the terminal device if the received contact information is not included in the previously stored contact list.

[0601] The control method may further include a step of receiving account information from a terminal device in response to a communication packet, and a step of sharing control with a terminal device corresponding to the contact information if the received account information is included in a list of previously stored accounts.

[0602] The control method may further include a step of generating temporary account information if the received account information is not included in the list of previously stored accounts, and a step of sharing control over the terminal device based on the temporary account information.

[0603] The step of generating temporary account information may generate temporary account information based on contact information received from the terminal device.

[0604] The control method may further include a step of updating the account information to add control over the target IoT device to the account information.

[0605] The control method may further include a step of maintaining IoT control sharing for a terminal device for a preset period of time when a user input for sharing control over an IoT network is received, and a step of deleting the shared control over the terminal device when the preset period of time has elapsed.

[0606] The step of determining a target IoT device may include obtaining a signal strength corresponding to each of at least one IoT device included in an IoT network, and determining an IoT device among at least one IoT device whose signal strength is greater than a threshold as a target IoT device.

[0607] Meanwhile, the methods according to the various embodiments of the present disclosure described above can be implemented in the form of applications that can be installed on existing electronic devices.

[0608] Additionally, the methods according to the various embodiments of the present disclosure described above can be implemented only with a software upgrade or a hardware upgrade for an existing electronic device.

[0609] Additionally, the various embodiments of the present disclosure described above may also be performed through an embedded server provided in an electronic device, or an external server of at least one of the electronic device and the display device.

[0610] FIG. 39 is a drawing for explaining a screen related to IoT control sharing according to one embodiment.

[0611] The screen (3900) of FIG. 39 may include at least one of an on / off UI (3910), a description UI (3920), an invitation UI (3930), and a code UI (3940) of IoT control sharing.

[0612] The on / off UI (3910) may include a UI that can turn IoT control sharing on or off.

[0613] The description UI (3920) may include information (e.g., text) describing features related to IoT control sharing.

[0614] The invitation UI (3930) may be a UI for performing an action to transmit an invitation message for sharing control authority to a device designated by the user. Upon receiving a user input selecting the invitation UI (3930), the electronic device (100) may provide a new screen for performing an action to transfer control authority to the invitee (e.g., a friend). The invitation method may be at least one of email, text message, or URL provision.

[0615] The code UI (3940) may be a UI that provides a code for granting control authority. When a user input selecting the code UI (3940) is received, the electronic device (100) may provide a new screen displaying a code containing the control authority. For example, the screen displaying the code may include at least one of an authentication number or a QR code.

[0616] Meanwhile, according to a temporary example of the present disclosure, the various embodiments described above can be implemented as software including instructions stored in a machine-readable storage medium that can be read by a machine (e.g., a computer). The device is a device that can call instructions stored in the storage medium and operate according to the called instructions, and may include an electronic device according to the disclosed embodiments. When an instruction is executed by a processor, the processor can perform a function corresponding to the instruction directly or under the control of the processor by using other components. The instruction may include code generated or executed by a compiler or interpreter. The machine-readable storage medium may be provided in the form of a non-transitory storage medium. Here, 'non-transitory' means that the storage medium does not contain a signal and is tangible, but does not distinguish between whether data is stored semi-permanently or temporarily in the storage medium.

[0617] Furthermore, according to one embodiment of the present disclosure, the method according to the various embodiments described above may be provided as included in a computer program product. The computer program product may be traded as a product between a seller and a buyer. The computer program product may be distributed in the form of a machine-readable storage medium (e.g., compact disc read-only memory (CD-ROM)) or online through an application store (e.g., Play Store™). In the case of online distribution, at least a portion of the computer program product may be temporarily stored or temporarily generated in a storage medium, such as the memory of a manufacturer's server, an application store's server, or a relay server.

[0618] In addition, each of the components (e.g., modules or programs) according to the various embodiments described above may be composed of a single or multiple entities, and some of the corresponding sub-components described above may be omitted, or other sub-components may be further included in various embodiments. Alternatively or additionally, some components (e.g., modules or programs) may be integrated into a single entity, which may perform the same or similar functions as those performed by each of the corresponding components prior to integration. Operations performed by modules, programs or other components according to various embodiments may be executed sequentially, in parallel, iteratively or heuristically, or at least some operations may be executed in a different order, omitted, or other operations may be added.

[0619] Although the preferred embodiments of the present disclosure have been illustrated and described above, the present disclosure is not limited to the specific embodiments described above, and various modifications may be made by a person having ordinary skill in the art to which the present disclosure pertains without departing from the gist of the present disclosure as claimed in the claims, and such modifications should not be understood individually from the technical idea or prospect of the present disclosure.

Claims

1. In electronic devices, communication interface; comprising at least one processor; At least one processor of the above, Based on the occurrence of an event in which control information for controlling a target device is provided, identifying the target device among at least one external device connected to the electronic device, Broadcasting packets related to the provision of the above control information through the above communication interface, Receive identification information through the communication interface from the device responding to the above packet, An electronic device that provides control information for controlling the target device to the device when the identification information received from the device is included in the pre-stored identification information.

2. In paragraph 1, The above event is a user input requesting the above control information, At least one processor of the above, An electronic device that broadcasts the packet using BLE (Bluetooth Low Energy) communication through the above communication interface.

3. In paragraph 1, At least one processor of the above, An electronic device that transmits AP (Access Point) information to which the electronic device is connected through the communication interface to a device that responded to the packet when contact information obtained through the above-described received identification information is included in the pre-stored identification information.

4. In paragraph 1, At least one processor of the above, An electronic device that controls a UI (User Interface) provided to confirm the connection authority of a device that responded to the packet if the contact information obtained through the above-mentioned received identification information is not included in the pre-stored identification information.

5. In paragraph 1, At least one processor of the above, Through the above communication interface, account information is received from the device responding to the packet, An electronic device that provides the control information to a device that responded to the packet based on the account information, if the received account information is included in a list of previously stored accounts.

6. In paragraph 5, At least one processor of the above, If the above received account information is not included in the list of previously saved accounts, temporary account information is created, An electronic device that provides the control information to a device responding to the packet based on the temporary account information.

7. In paragraph 6, At least one processor of the above, An electronic device that generates temporary account information based on contact information obtained through the identification information received from a device responding to the packet.

8. In paragraph 5, At least one processor of the above, An electronic device that updates the account information received from the device to add the control information for the target device to the account information.

9. In paragraph 1, At least one processor of the above, Based on the event in which a user input for providing the above control information is received, a state for providing the above control information to a device responding to the packet is controlled to be maintained for a preset period of time, An electronic device in which the control information is not provided to the device that responded to the packet after the above-mentioned preset time has elapsed.

10. In paragraph 1, At least one processor of the above, An electronic device that acquires a signal strength corresponding to each of the at least one external device connected to the electronic device, and identifies an external device among the at least one external device whose signal strength is greater than a threshold value as the target device.

11. In a method for controlling an electronic device, A step of identifying the target device among at least one external device connected to the electronic device based on the occurrence of an event in which control information for controlling the target device is provided; A step of broadcasting a packet related to providing the above control information; A step of receiving identification information from a device responding to the above packet; and A control method, comprising: a step of providing control information for controlling the target device to the device when the identification information received from the device is included in the pre-stored identification information; 12. In paragraph 11, The above event is a user input requesting the above control information, The step of broadcasting the above packet is: A control method for broadcasting the packet using BLE (Bluetooth Low Energy) communication.

13. In paragraph 11, The above control method is, A control method further comprising: a step of transmitting AP (Access Point) information to which the electronic device is connected to a device that responded to the packet, if the contact information obtained through the received identification information is included in the pre-stored identification information; 14. In paragraph 11, The above control method is, A control method further comprising: a step of controlling a UI (User Interface) provided to confirm the connection authority of a device responding to the packet if the contact information obtained through the above-described received identification information is not included in the pre-stored identification information; 15. In paragraph 11, The above control method is, A step of receiving account information from a device responding to the above packet; and A control method further comprising: a step of providing the control information to a device that responded to the packet based on the account information, if the received account information is included in a list of previously stored accounts.

Images