User device and system for onboarding external electronic device to server from user device

Abstract

A system for onboarding an electronic device to a cloud network, according to one aspect, comprises: a cloud network; a user device including a first communication unit for establishing communication with an electronic device registered in the cloud network, a first user interface, and a first processor electrically connected to the first communication unit and the first user interface; and an electronic device including a second communication unit for establishing communication with the user device, a second user interface, and a second processor electrically connected to the second communication unit and the second user interface, wherein the first processor may control the first user interface to output a first guide requesting confirmation according to a preset default authentication method, on the basis of the communication connection between the first communication unit and the electronic device, and the second processor may control the second user interface to output a second guide indicating that the electronic device is in a state of being able to receive the confirmation according to the preset default authentication method.

Description

A system for onboarding user devices, external electronic devices from user devices to servers.

[0001] The present disclosure relates to a system for onboarding a user device and an external electronic device from the user device to a server.

[0002] Cloud computing technology provides computing resources located elsewhere to users via a network, offering computing services such as servers, storage, software, and analytics. Cloud computing is being utilized to process data generated by the Internet of Things (IoT). User data and content collected from IoT devices are stored on cloud servers, and data processing can provide cloud services to users.

[0003] Using IoT devices in an IoT environment requires an onboarding process to register them on a cloud server. Onboarding an IoT device may require authentication information for authenticating the IoT device, a uniform resource locator (URL) for accessing the cloud server, and / or device information such as the IoT device's device type, profile, or location.

[0004] Onboarding IoT devices to cloud servers involves manual steps performed by users. They must run the IoT device onboarding application and manually enter their identifier and password for network credentials, which requires device authentication. Specifically, users must wait several seconds before receiving the IoT device authentication guide. This process significantly increases the time required for IoT device onboarding, resulting in user inconvenience and potential for users to cancel the connection midway.

[0005] The present disclosure relates to a system for rapidly onboarding a user device and an external electronic device from the user device to a server.

[0006] A user device according to one aspect of the present disclosure includes a communication unit for connecting communication with an electronic device registered in a cloud server; a user interface; and a processor electrically connected to the communication unit and the user interface; wherein the processor comprises:

[0007] The user interface can be controlled to output a first guide requesting confirmation according to a preset default authentication method based on the communication connection between the communication unit and the electronic device, and a control signal can be transmitted to the electronic device to output a second guide indicating that the electronic device is in a state where it can receive the confirmation according to the preset default authentication method.

[0008] A system for onboarding an electronic device according to one aspect of the present disclosure

[0009] A cloud network; a user device including a first communication unit for connecting communication with an electronic device registered in the cloud network, a first user interface, and a first processor electrically connected to the first communication unit and the first user interface; and an electronic device including a second communication unit for connecting communication with the user device, a second user interface, and a second processor electrically connected to the second communication unit and the second user interface; wherein the first processor,

[0010] The first user interface may be controlled to output a first guide requesting confirmation according to a preset default authentication method based on the communication connection between the first communication unit and the electronic device, and the second processor may control the second user interface to output a second guide indicating that the electronic device is in a state where it can receive the confirmation according to the preset default authentication method.

[0011] A method for onboarding an electronic device according to one aspect of the present disclosure may include connecting communication between a user device including a first user interface and an electronic device including a second user interface and registered in a cloud network, outputting a first guide requesting confirmation according to a preset default authentication method on the first user interface based on the communication connection between the user device and the electronic device, and simultaneously or simultaneously with the first guide, outputting a second guide indicating that the electronic device is in a state where it can receive the confirmation according to the preset default authentication method on the second user interface.

[0012] A user device according to one embodiment of the present disclosure may further include a memory capable of storing state information regarding the default device authentication.

[0013] According to one aspect of the present disclosure, by performing device authentication according to a preset default authentication method, the user does not need to wait until data exchange for coordinating the device authentication method is completed, thereby reducing the connection time perceived by the user and improving convenience.

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

[0015] FIG. 1 illustrates multiple devices within an IoT environment according to one embodiment.

[0016] FIG. 2 illustrates an example of an IoT server of an IoT system according to one embodiment.

[0017] FIG. 3 illustrates an example of each device of an IoT system according to one embodiment.

[0018] FIG. 4 is a block diagram schematically illustrating an electronic device in an IoT environment according to one embodiment.

[0019] Figure 5 is a control block diagram of an electronic device according to one embodiment.

[0020] FIG. 6 is a diagram illustrating an example of an onboarding method for an IoT device according to one embodiment.

[0021] FIG. 7 is a diagram illustrating an example of a device authentication process of an electronic device for onboarding an electronic device according to one embodiment.

[0022] FIG. 8 is a diagram illustrating an example of a screen displayed through a user interface of a user device after an electronic device is identified according to one embodiment.

[0023] FIG. 9 is a diagram illustrating an example of a screen displayed through a user interface of a user device while data communication for coordinating a device authentication method is performed according to one embodiment.

[0024] FIG. 10 is a diagram illustrating an example of a screen displayed through a user interface of a user device to guide authentication to be performed according to an authentication method of an electronic device tuned according to one embodiment.

[0025] FIG. 11 is a diagram illustrating an example of a screen displayed through a user interface of an electronic device to receive confirmation for authentication of an electronic device according to one embodiment.

[0026] FIG. 12 is a flowchart illustrating a process by which a user device and an electronic device perform default device authentication according to one embodiment.

[0027] FIG. 13 is a flowchart illustrating a process in which a user device and an electronic device perform default device authentication according to another embodiment.

[0028] It should be understood that the various embodiments and terms used in this document are not intended to limit the technical features described in this document to specific embodiments, but rather to include various modifications, equivalents, or substitutes of the embodiments.

[0029] In connection with the description of the drawings, similar reference numerals may be used for similar or related components.

[0030] The singular form of a noun corresponding to an item may include one or more of said items, unless the relevant context clearly indicates otherwise.

[0031] In this document, each of the phrases "A or B", "at least one of A and B", "at least one of A or B", "A, B, or C", "at least one of A, B, and C", and "at least one of A, B, or C" may include any one of the items listed together in that phrase, or all possible combinations thereof.

[0032] The term “and / or” includes any combination of a plurality of related described elements or any one of a plurality of related described elements.

[0033] Terms such as "first," "second," or "first" or "second" may be used simply to distinguish one component from another and do not qualify the components in any other respect (e.g., importance or order).

[0034] When a component (e.g., a first component) is referred to as being "coupled" or "connected" to another component (e.g., a second component), with or without the terms "functionally" or "communicatively," it means that the component can be connected to the other component directly (e.g., wired), wirelessly, or through a third component.

[0035] The terms “include” or “have” are intended to specify the presence of a feature, number, step, operation, component, part or combination thereof described in this document, but do not preclude the presence or addition of one or more other features, numbers, steps, operations, components, parts or combinations thereof.

[0036] When a component is said to be “connected,” “coupled,” “supported,” or “in contact with” another component, this includes not only cases where the components are directly connected, coupled, supported, or in contact, but also cases where the components are indirectly connected, coupled, supported, or in contact through a third component.

[0037] When we say that a component is "on" another component, this includes not only cases where the component is in contact with the other component, but also cases where there is another component between the two components.

[0038] Meanwhile, the terms “front”, “back”, “left”, “right”, “up”, “down”, etc. used in the description below are expressions related to direction, and are defined based on the drawing, and the shape and position of each component are not limited by these terms.

[0039] FIG. 1 illustrates multiple devices within an IoT environment according to one embodiment.

[0040] An Internet of Things (IoT) system (100) according to one embodiment may include at least one leaf device (110), at least one hub device (120) (or edge device), a cloud network (130), and / or a user device (140).

[0041] For example, the leaf device (110), the hub device (120), and / or the user device (140) may be located in close proximity and connected to the same home network (i.e., the same AP (access point)), and the cloud network (130) may be located remotely but connected to the leaf device (110), the hub device (120), and the user device (140) via the Internet. In the present disclosure, the leaf device (110) and the hub device (120) of the IoT system (100) may also be referred to as IoT devices.

[0042] According to various embodiments, each device of the IoT system can be used to provide a cloud computing service. For example, if information regarding the temperature inside a house is acquired from a temperature sensor (115c), the information acquired by the temperature sensor (115c) is provided to a cloud network (130). The cloud network (130) can then verify the event of the sensor (115c) and the mapped operation, and transmit a command to the air conditioner (113) to turn it on.

[0043] According to various embodiments, edge computing services may be provided using each device of an IoT system. The edge computing service may include a technology for transmitting data acquired from a leaf device to a hub device located adjacent to the leaf device and on the same home network, and providing a series of data processing and other services on the hub device. In the present disclosure, a device that acquires data through a sensor (e.g., a camera (111), a refrigerator (112), a smart light bulb (115a), a motion sensor (115b), and / or a digital thermometer (115c)) is defined as a leaf device (110), but the leaf device (110) may also be referred to by other names, such as a client device, an end device, a sensor device, an IoT device, or a slave device of an edge computing service. In addition, although defined as a hub device in various embodiments of the present document, the hub device may also be defined by other names, such as an edge device, an edge server, a server device, a master device, or a service device of an edge computing service.

[0044] In the present disclosure, devices within an IoT system (100) are classified and described as leaf devices (110), hub devices (120), and user devices (140) according to their functions or operations. However, the same device (e.g., a smartphone or TV) may operate as any one of the leaf devices (110), hub devices (120), and user devices (140) depending on the case. That is, the names and / or definitions of the devices described in various embodiments of the present disclosure do not limit the functions and / or operations of the corresponding devices.

[0045] According to various embodiments, the leaf device (110) may collect various information using a sensor as an end point of the IoT system (100) and transmit the collected information to a hub device (120) or a cloud network (130). In addition, the leaf device (110) may perform various operations according to commands transmitted from the hub device (120), the cloud network (130), and / or the user device (140). Referring to FIG. 1, the leaf device (110) may include a camera (111), a refrigerator (112), an air conditioner (113), a washing machine (114), a smart light bulb (115a), a motion sensor (115b), and / or a smart thermometer (115c).

[0046] According to various embodiments, at least some of the leaf devices (110) (e.g., a camera (111), a refrigerator (112), an air conditioner (113), a washing machine (114)) can access a cloud network (130) via the Internet, and devices among the leaf devices (110) that do not support Internet Protocol (IP) (e.g., a light bulb (115a), a motion sensor (115b), or a smart thermometer (115c)) can transmit information acquired to a relay device (116) via non-IP-based communication (e.g., Bluetooth, Zigbee) that they support, and the relay device (116) can transmit information acquired by each leaf device (115a, 115b, 115c) to the cloud network (130) via the Internet.

[0047] According to various embodiments, information acquired from the leaf device (110) may be processed by a cloud computing service or an edge computing service. For example, image information acquired from a camera (111), which is a leaf device, may be transmitted to a cloud network, and an on / off control command may be transmitted from the cloud network to a light bulb (115a), and / or the image information may be provided to a user device (140) in real time. Alternatively, information acquired from the camera (111) may be transmitted to a hub device (120), and an on / off control command or image information may be transmitted from the hub device (120) to a light bulb (123a).

[0048] According to various embodiments, the cloud network (130) may be located on a network and include various server devices (e.g., an IoT management server, an IoT hub server) that support cloud computing services in the IoT system (100). The cloud network (130) may perform computing processing on acquired information received from a leaf device (110) and transmit commands for controlling the leaf device (110).

[0049] According to various embodiments, the cloud network (130) may perform a function of operating and managing a specific device within a home network so that it can operate as a hub device (120). For example, the cloud network (130) may include an IoT server (e.g., an IoT management server or an IoT hub server), and the IoT server may perform edge computing services such as registration, connection, or management of the hub device (120) and leaf devices (110), and provide modules (e.g., device modules and / or service modules) required for the edge computing services to the hub device (120).

[0050] According to various embodiments, the hub device (120) may directly process data received from the leaf device (110) or transmit it to a cloud network (130) (e.g., an IoT server). The hub device (120) may be a device including hardware and / or software resources required for edge computing services, such as a TV or a tablet PC. The hub device (120) may be connected to the cloud network (130) via the Internet, and may communicate with the leaf device (110) via direct communication, a mesh network, or an access point.

[0051] According to various embodiments, there may be multiple hub devices (120) within a home network, and a leaf device (110) may be connected to any one of the multiple hub devices (120) to transmit information. For example, when a specific leaf device (110) is connected, the hub device (120) may download and execute a module (e.g., a device module and / or a service module) required for an edge computing service from a cloud network (130).

[0052] According to various embodiments, the hub device (120) may perform a device-specific function (e.g., a video output function of a TV) and may perform edge computing services through hardware and / or software resources at least partially simultaneously with the performance of the device-specific function or during idle time when the device is not performing the device-specific function.

[0053] According to various embodiments, the hub device (120) may store rule information including information for event automation processing. For example, the rule information may be a rule that maps an action command that instructs another leaf device to perform an action in response to a trigger event occurring in a specific leaf device. The hub device (120) may receive rule information from the cloud network (130) and build a database in the memory of the hub device (120).

[0054] According to various embodiments, the user device (140) may provide various user interfaces related to edge computing services through applications. For example, the user device (140) may receive data acquired from the leaf device (110) (e.g., camera image streaming) or user input, such as connection of the hub device (120) and / or the leaf device (110), or server registration, and transmit the data to the cloud network (130). In addition, the result data (e.g., IoT device authentication completion) processed by the hub device (120) or the cloud network (130) may be displayed on the display.

[0055] FIG. 2 illustrates an example of an IoT server of an IoT system according to one embodiment.

[0056] According to various embodiments, the IoT hub server (131a) supports a cloud computing platform and can provide data necessary for a leaf device (110) and a hub device (120) within a cloud environment to be connected to each other. The IoT hub server (131a) can include an IoT hub (132) and a module registry (133).

[0057] According to one embodiment, an IoT hub (132) maintains a connection with a hub device (120), provides modules stored in a module registry (133) to the hub device (120), and can maintain information about modules installed in multiple hub devices (120).

[0058] According to one embodiment, the module registry (133) can store information about modules (e.g., device module (123), service module (124)) required to perform edge computing services.

[0059] According to various embodiments, the IoT managing server (131b) (e.g., SmartThingsTM server) is a server that provides various services for determining, connecting, and / or operating edge computing services, and may include a provision manager (134), a module manager (135), and an edge-leaf manager (136).

[0060] According to one embodiment, the provision manager (134) may perform a function of intermediating so that the hub device (120) can be connected to the IoT hub server (131a). For example, when the hub device (120) is initially registered with the IoT managing server (131b), the provision manager (134) may transmit a connection string to the hub device (120) so that the hub device (120) can be connected to the IoT hub server (131a).

[0061] According to one embodiment, the module manager (135) can manage information about various modules required for edge computing services and devices supporting each service.

[0062] A module required to perform an edge computing service may include a device module (123) that enables the hub device (120) to transmit data received from the leaf device (110) to an external server (e.g., IoT hub server (131a)).

[0063] Additionally, a module required to perform an edge computing service may include a service module (124) that includes programs that the hub device (120) executes to implement a service based on data received from the leaf device (110).

[0064] According to one embodiment, the edge-leaf manager (136) can manage the connection status of hub devices (120) and leaf devices (110) existing in multiple home networks. For example, when a hub device (120) and a leaf device (110) registered in the IoT managing server (131b) are connected or disconnected from each other, the edge-leaf manager (136) can transmit connection or disconnection information from the hub device (120) and / or the leaf device (110) to the IoT managing server (131b). At this time, the IoT managing server (131b) can store information in real time about which hub device (120) and leaf device (110) are connected and / or which service is being performed.

[0065] According to various embodiments, a leaf device (110) may be connected to a specific edge device (e.g., a hub device (121) of FIG. 1) to perform an edge computing service, and then, upon a handover event, the leaf device (110) may disconnect from the edge device and connect to another edge device (e.g., a TV (122) of FIG. 1) to perform an edge computing service. The handover event may include a connection being switched from one device or system to another. At this time, the IoT managing server (131b) may update connection information between the hub device (120) and the leaf device (110) to which the connection is switched in response to the handover event.

[0066] FIG. 3 illustrates an example of each device of an IoT system according to one embodiment.

[0067] Referring to FIG. 3, an IoT system (or cloud computing system, edge computing system) (100) may include a leaf device (110), a hub device (120), an IoT server (131), and / or a user device (140). The IoT server (131) may include an IoT hub server (131a) and an IoT managing server (131b).

[0068] As described above with reference to FIG. 1, various IoT devices may exist on a home network, and FIG. 3 will describe an example of one leaf device (110) (e.g., a refrigerator (112) of FIG. 1) and one hub device (120) (e.g., a user terminal (140) of FIG. 1).

[0069] According to one embodiment, the hub device (120) may be a device having device-specific functions, such as a TV, tablet PC, or laptop PC, and including hardware and / or software components (e.g., an edge runtime and / or a basic module) for edge computing services. Edge computing services may be performed through hardware and / or software resources at least partially concurrently with the performance of the device-specific functions or during idle time when the device is not performing the device-specific functions.

[0070] An edge runtime (122) and a basic module for edge computing may be installed in the hub device (120) through a process or software upgrade of the hub device (120). For example, the edge runtime (122) may include a daemon program for interfacing with an IoT server, and the basic module may be configured as a container as a program required for communication with the IoT server. For example, the basic module may be a container installed in the edge runtime (122) environment.

[0071] According to various embodiments, the hub device (120) may receive and install at least one module for performing edge computing services from the IoT hub server (131a) in response to being connected to a specific leaf device (110).

[0072] At least one module may be determined based on the type of connected leaf device (110) and / or the type of service to be performed. For example, the at least one module may include a device module (123) corresponding to the connected leaf device (110) and / or a service module (124) corresponding to the type of service to be performed.

[0073] When the hub device (120) is connected to a plurality of leaf devices (110), a device module (123) corresponding to each leaf device (110) (e.g., a first device module (123a), a second device module (123b), etc.) may be installed.

[0074] The hub device (120) executes an edge runtime (122) during the provisioning process to connect to the IoT hub server (131a), and at least one module may be additionally installed and executed depending on the type of leaf device (110). The hub device (120) may activate or deactivate the edge mode according to a command received from the IoT hub server (131a) or the IoT managing server (131b). When the edge mode is deactivated, the hub device (120) may only perform its own functions (e.g., the video output function of a TV), and the device module (123) and the service module (124) may not be executed.

[0075] According to various embodiments, the leaf device (110) may transmit information acquired using a sensor to a connected hub device (120) or cloud network (130) (e.g., an IoT managing server (131b) and / or an IoT hub server (131a)). For example, in the case of a refrigerator (112) operating as a leaf device (110), it may be connected to a hub device (120) and transmit information regarding the temperature inside the chamber of the refrigerator (112) to the hub device (120).

[0076] According to various embodiments, the user device (140) may be a device including a display capable of displaying a user interface (UI). The user device (140) may install and / or execute an application for edge computing services, and receive content and / or notifications generated in the leaf device (110) through the application. In other words, when the hub device (120) and the leaf device (110) are connected, content or notifications generated in the leaf device (110) may be transmitted to the user device (140) through the hub device (120).

[0077] According to various embodiments, the functions of the IoT hub server (131a) or the IoT managing server (131b) may be performed by a single server device (e.g., the IoT server (131) of FIG. 3). Alternatively, the functions may be performed by three or more server devices. For example, each component of the IoT hub server (131a) and the IoT managing server (131b) of FIG. 2 may be distributed and deployed by three or more server devices existing on a network, or some operations performed by each component may also be distributed and performed by multiple server devices.

[0078] FIG. 4 is a block diagram schematically illustrating an electronic device in an IoT environment according to one embodiment.

[0079] As described above, in the IoT system (100), the same device can operate as an IoT device (e.g., leaf device (110) and hub device (120) of FIG. 1) and can operate as a user device (e.g., user device (140) of FIG. 1). Hereinafter, the configuration and / or function of an electronic device (301) that can operate as an IoT device and / or a user device will be described in detail through FIG. 3.

[0080] Referring to FIG. 4, in a network environment (300), an electronic device (301) may communicate with an electronic device (302) via a first network (398) (e.g., a short-range wireless communication network), or may communicate with at least one of an electronic device (304) or a server (308) via a second network (399) (e.g., a long-range wireless communication network). According to one embodiment, the electronic device (301) may also communicate with the electronic device (304) via the server (308).

[0081] According to one embodiment, the electronic device (301) may include a processor (320), a memory (330), an input module (350), an audio output module (355), a display module (360), an audio module (370), a sensor module (376), an interface (377), a connection terminal (378), a haptic module (379), a camera module (380), a power management module (388), a battery (389), a communication unit (390), a subscriber identification module (396), and / or an antenna module (397).

[0082] In the electronic device (301), at least one of the aforementioned components (e.g., the connection terminal (378)) may be omitted, or one or more other components may be added. In addition, in the electronic device (301), some of these components (e.g., the sensor module (376), the camera module (380), or the antenna module (397)) may be integrated into one component (e.g., the display module (360)).

[0083] The processor (320) may execute software (e.g., a program (340)) to control at least one other component of an electronic device (301) connected to the processor (320) and perform various data processing or calculations. At this time, the components of the electronic device (301) connected to the processor (320) may include hardware or software components.

[0084] According to one embodiment, as at least part of data processing or calculation, the processor (320) may store commands or data received from another component (e.g., a sensor module (376) or a communication unit (390)) in a volatile memory (332), process the commands or data stored in the volatile memory (332), and store resulting data in a non-volatile memory (334). In this case, the data received from the other component may include information acquired by the sensor module (376).

[0085] According to one embodiment, the processor (320) may include a main processor (321) (e.g., a central processing unit or an application processor) or an auxiliary processor (323) (e.g., a graphics processing unit, a neural processing unit (NPU), an image signal processor, a sensor hub processor, or a communication processor) that can operate independently or together with the main processor (321). For example, when the electronic device (301) includes the main processor (321) and the auxiliary processor (323), the auxiliary processor (323) may be configured to use less power than the main processor (321) or to be specialized for a given function. The auxiliary processor (323) may be implemented separately from the main processor (321) or as a part thereof.

[0086] The auxiliary processor (323) may control at least a portion of functions or states associated with at least one component (e.g., a display module (360), a sensor module (376), or a communication unit (390)) of the electronic device (301), for example, on behalf of the main processor (321) while the main processor (321) is in an inactive (e.g., sleep) state, or together with the main processor (321) while the main processor (321) is in an active (e.g., application execution) state. The auxiliary processor (323) (e.g., an image signal processor or a communication processor) may be implemented as a part of another functionally related component (e.g., a camera module (380) or a communication unit (390)).

[0087] According to one embodiment, the auxiliary processor (323) (e.g., a neural network processing device) may include a hardware structure specialized for processing an artificial intelligence model. The artificial intelligence model may be generated through machine learning. Such learning may be performed, for example, in the electronic device (301) itself where the artificial intelligence model is executed, or may be performed through a separate server (e.g., server (308)). The learning algorithm may include, for example, supervised learning, unsupervised learning, semi-supervised learning, or reinforcement learning, but is not limited to the examples described above. The artificial intelligence model may include a plurality of artificial neural network layers. The artificial neural network may be one of a deep neural network (DNN), a convolutional neural network (CNN), a recurrent neural network (RNN), a restricted Boltzmann machine (RBM), a deep belief network (DBN), a bidirectional recurrent deep neural network (BRDNN), a deep Q-network, or a combination of two or more of the above, but is not limited to the examples described above. In addition to, or alternatively to, a hardware structure, an artificial intelligence model may include a software structure.

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

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

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

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

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

[0093] The audio module (370) can convert sound into an electrical signal, or vice versa, convert an electrical signal into sound. The audio module (370) can acquire sound through the input module (350), or output sound through an audio output module (355), or an external electronic device (e.g., electronic device (302)) (e.g., speaker or headphone) directly or wirelessly connected to the electronic device (301).

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

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

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

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

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

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

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

[0101] The communication unit (390) may support the establishment of a direct (e.g., wired) communication channel or a wireless communication channel between the electronic device (301) and an external electronic device (e.g., electronic device (302), electronic device (304), or server (308)), and the performance of communication through the established communication channel. The communication unit (390) may operate independently from the processor (320) (e.g., application processor) and may include one or more communication processors that support direct (e.g., wired) communication or wireless communication. According to one embodiment, the communication unit (390) may include a wireless communication unit (392) (e.g., a cellular communication unit, a short-range wireless communication unit, or a global navigation satellite system (GNSS) communication unit) or a wired communication unit (394) (e.g., a local area network (LAN) communication unit, or a power line communication unit). Among these communication units, the corresponding communication unit can communicate with an external electronic device (304) via a first network (398) (e.g., a short-range communication network such as Bluetooth, wireless fidelity (WiFi) direct, or infrared data association (IrDA)) or a second network (399) (e.g., a long-range communication network such as a legacy cellular network, a 5G network, a next-generation communication network, the Internet, or a computer network (e.g., a LAN or WAN)). These various types of communication units can be integrated into a single component (e.g., a single chip) or implemented as a plurality of separate components (e.g., multiple chips). The wireless communication unit (392) can verify or authenticate the electronic device (301) within a communication network such as the first network (398) or the second network (399) by using subscriber information (e.g., an international mobile subscriber identity (IMSI)) stored in the subscriber identification module (396).

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

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

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

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

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

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

[0108] Figure 5 is a control block diagram of an electronic device according to one embodiment.

[0109] Referring to FIG. 5, the electronic device (400) may include a communication unit (410), a user interface (420), a sensor (430), a processor (440), and a memory (450). The electronic device (400) may further include at least some of the configurations and / or functions of the electronic device (301) of FIG. 3, and may implement various embodiments of the present document even if some of the illustrated configurations are omitted or replaced. According to various embodiments, the electronic device (400) may be implemented as any one device in an IoT system (e.g., the IoT system (100) of FIG. 1). For example, the electronic device (400) may be any one of a hub device (120) or a leaf device (110) of the IoT system.

[0110] The electronic device (400) may be a device that includes a sensor (430) including various sensors (e.g., a camera, a light sensor, or a microphone), such as a smart phone or tablet PC, and has at least one processor and / or memory resource. In this case, the electronic device (400) may install and execute an application that supports IoT services, thereby providing IoT services.

[0111] The communication unit (410) supports wireless communication (e.g., Wi-Fi, cellular communication) and can transmit and receive data with other electronic devices or cloud networks within the IoT system. The communication unit (410) may include the communication unit (39) and / or the antenna module (397) of FIG. 4.

[0112] The communication unit (410) may communicate with other devices through an AP (access point), or may communicate directly with other devices using D2D (e.g., Bluetooth) or P2P (e.g., Wi-Fi Direct or Wi-Fi Aware) communication.

[0113] The user interface (420) can provide information necessary for providing IoT services to an external party (e.g., a user) of the electronic device (400) in the form of visual information or voice information.

[0114] The user interface (420) may include a display module (360), an input module (350), an audio output module (355), an audio module (370), and / or a sensor module (376) of FIG. 4.

[0115] According to one embodiment, the user interface (420) may include a touch screen including a touch sensing circuit (or touch sensor) (not shown), a pressure sensor capable of measuring the intensity of a touch, and / or a touch panel (e.g., a digitizer) capable of detecting a magnetic field-type stylus pen.

[0116] At this time, the touch screen may include, but is not limited to, a liquid crystal display (LCD), an organic light emitting diode (OLED), an active matrix organic light emitting diode (AMOLED), a flexible display, or an expandable display.

[0117] According to one embodiment, the user interface (420) may provide guidance regarding the authentication operation of the electronic device (400) through various visual information.

[0118] Specifically, the user interface (420) may include a microphone, a mouse, a keyboard, or a key (e.g., a button) for receiving commands or data to be used for an authentication operation of the electronic device (400) from an external source (e.g., a user) of the electronic device (400). In addition, the user interface (420) may include a speaker to provide various information and / or guidance for guiding the authentication operation through voice information.

[0119] According to one embodiment, the user interface (420) may include at least one input interface (420a) and at least one output interface (420b).

[0120] At least one input interface (70a) may include, for example, a tact switch, a push switch, a slide switch, a toggle switch, a micro switch, a touch switch, a touch pad, a touch screen, a jog dial, and / or a microphone.

[0121] In the present disclosure, 'button' may be replaced with a UI element (User Interface Element), a tact switch, a push switch, a slide switch, a toggle switch, a micro switch, a touch switch, a touch pad, a touch screen, a jog dial, and / or a microphone.

[0122] At least one output interface (70b) can transmit various information related to the authentication operation to the user by generating sensory information.

[0123] For example, at least one output interface (70b) may output a description of an operation for device authentication. Additionally, at least one output interface (70b) may include a visual indicator of an operation for device authentication.

[0124] At this time, the visual indicator may include at least one of an illustration, a graphic guide, or a visual reference.

[0125] The electronic device (400) may include at least one sensor (430). For example, the electronic device (400) may include a sensor (430) such as a camera, a light sensor, a motion sensor, or a microphone. The electronic device (400) may transmit sensor (430) information acquired through the sensor (430) to a cloud network or another electronic device, thereby providing an IoT system that controls other devices on a local network based on a cloud (or edge).

[0126] The memory (450) may include volatile memory and non-volatile memory, and may temporarily or permanently store various data used in at least one component (e.g., processor (440)) of the electronic device (400). The memory (450) may store various instructions that may be performed by the processor (440). Such instructions may include various control commands including arithmetic and logical operations, data movement, or input / output that may be recognized by the processor (440).

[0127] The processor (440) is a component that can perform calculations or data processing related to control and / or communication of each component of the electronic device (400), and can be operatively, functionally and / or electrically connected to each component of the electronic device (400), such as the communication unit (410), the user interface (420), the sensor (430) and / or the memory (450).

[0128] According to various embodiments, there will be no limitation to the computational and data processing functions that the processor (440) can implement within the electronic device (400). However, various embodiments for self-onboarding, which registers the electronic device (400) in real time to the cloud network without a separate registration process in advance, will be described below. The operations of the processor (440), which will be described later, can be performed by executing instructions stored in the memory (450).

[0129] FIG. 6 is a diagram illustrating an example of an onboarding method for an IoT device according to one embodiment.

[0130] A manufacturer of an electronic device (e.g., an electronic device (400) of FIG. 5) may register device information and authentication information of the electronic device (400) within an IoT system (100) in advance in a cloud network (130), and may cause the electronic device (400) to be connected to a user device (e.g., a user device (140) of FIG. 1) in Bluetooth or soft AP mode to request onboarding to the cloud network (130) through the user device (140).

[0131] Specifically, according to one embodiment, the manufacturer of the electronic device (400) may register authentication information and device information of the electronic device (400) in advance with the cloud network (130) (601). For example, during the manufacturing process of the electronic device (400), the cloud network may provide services related to authentication and registration of the electronic device (400). The manufacturer may register authentication information and device information of the electronic device (400) through the provided online environment.

[0132] Specifically, the manufacturer of the electronic device (400) can access the provided online environment and register device information of the electronic device (400), such as device type and profile information, and authentication information, such as ED25519 and X.509. In addition, the manufacturer of the electronic device (400) can update device information and onboarding configuration information in the SDK (software development kit) of the IoT device, and store software required for the cloud service.

[0133] After this, a user who has purchased an electronic device (400) can proceed with the process of onboarding the electronic device (400) to the cloud network.

[0134] Specifically, the electronic device (400) may obtain onboarding information from the user device (140) to perform onboarding (602). The onboarding information is information required to connect and authenticate the electronic device (400) to the cloud network (130), and may include credential information.

[0135] Credential information may include Wi-Fi provisioning information, cloud provisioning information, and device configuration provisioning information.

[0136] For example, Wi-Fi provisioning information may include the SSID and password of the access point to be connected stored on the user device, cloud provisioning information may include the broker URL to be connected and authentication information obtained by the user device from the cloud network, and device setup provisioning information may include additional information such as location, language, country code, time zone, model name, or device name entered through the user device.

[0137] The electronic device (400) can access the cloud network (130) and request onboarding based on the onboarding information received from the user device (140) (603).

[0138] In one embodiment, if the electronic device (400) does not provide a function for inputting device setting information, such as location or device name, the user may be required to input such information through the user device (140). To this end, the electronic device (400) may enter soft AP mode, and the user device (140) may connect to the soft AP to provide device setting provisioning information and cloud provisioning information.

[0139] According to various embodiments, the electronic device (400) may enter discoverable mode through Bluetooth (or low-power Bluetooth) advertising, and the user device (140) may select the electronic device (400) that has entered discoverable mode through BLE scan and proceed with the setup process described above.

[0140] In order for an electronic device (400) to be onboarded to a cloud server (130), it is essential to obtain onboarding information (e.g., credential information) from a user device through device authentication of the electronic device (400).

[0141] Hereinafter, with reference to FIG. 7, the device authentication process of the electronic device (400) for onboarding the electronic device (400) and the guide provided to the user during the device authentication process will be described.

[0142] FIG. 7 is a diagram illustrating an example of a device authentication process of an electronic device for onboarding an electronic device according to one embodiment.

[0143] In one embodiment, the electronic device (400) may activate a communication connection readiness state for device authentication (701). For example, the electronic device (400) may initiate BLE advertising.

[0144] At this time, the electronic device (400) can activate the communication connection readiness state based on a user's input or request. Additionally, the electronic device (400) can activate the communication connection readiness state based on power being applied even without a user's input or request.

[0145] The electronic device (400) can periodically send broadcast packets through BLE (Bluetooth Low Energy) Advertising when the communication connection readiness state is activated.

[0146] The broadcast packet may include a unique identifier (UUID) of the electronic device (400), service information, data, etc. In addition, the broadcast packet may include information regarding a service or profile of the electronic device (400), for example, whether an audio output service is provided or whether a heart rate measurement service is provided.

[0147] Additionally, the broadcast packet may include whether the user device (140) supports a service for default device authentication.

[0148] Additionally, the electronic device (400) may activate a communication connection readiness state, which may include activating a Soft Access Point (SoftAP). Activating a Soft Access Point (SoftAP) may include the electronic device (400) acting as a Wi-Fi access point on its own, without a separate device functioning as a router or access point. In other words, the electronic device (400) may create a Wi-Fi network on its own, and other electronic devices (e.g., user devices (140)) may be able to connect to the network.

[0149] The user device (140) can identify an electronic device (400) in which a communication standby state is activated through scanning (702).

[0150] When the user device (140) identifies the electronic device (400), it requests a communication connection based on the identification information or the preset password information of the electronic device (400) (703), and the electronic device (400) that receives the communication connection request receives the communication connection based on the received identification information or the preset password information (704).

[0151] At this time, the connected communication may be one of Wi-Fi communication, Bluetooth communication, low-power Bluetooth communication, and / or Zigbee communication.

[0152] When communication between the user device (140) and the electronic device (400) is connected, the user device (140) and the electronic device (400) may exchange information or resources for device authentication several times.

[0153] For example, a user device (140) may request a resource (705) regarding whether the electronic device (400) has specific information. For example, the specific information may include provisioning information (sec / provisioninginfo in FIG. 7) that includes information related to security aspects such as security settings, authentication, encryption, and key exchange.

[0154] In response, the electronic device (400) can check whether the user device (140) has the requested resource, and if it can provide the resource, it can provide a response indicating that the user device (140) has the resource (706).

[0155] Additionally, the user device (140) may request resources regarding specific information (707) to provide or update the electronic device (400). For example, the specific information may include security-related provisioning information (sec / provisioninginfo in FIG. 7).

[0156] In response to this, the electronic device (400) may provide the contents of a resource regarding specific information after receiving a request from the user device (140) (707).

[0157] In other words, the user device (140) and the electronic device (400) can go through several data exchange processes for device authentication and coordinate the device authentication method through the process.

[0158] After exchanging information or resources with the electronic device (400) several times (705 to 708), the user device (140) can determine a device authentication method and transmit a confirmation request for device authentication according to the determined authentication method to the electronic device (400) (709).

[0159] Confirmation can be performed by the user or without user intervention.

[0160] For example, if the electronic device (400) is a refrigerator (112), the user device (140) may request the user to turn the refrigerator (112) door on / off once or press a preset button for a preset time as confirmation for device authentication.

[0161] Additionally, the user device (140) may request confirmation of an authentication signal including infrared code set information for device authentication when the electronic device (400) is a refrigerator (112).

[0162] The electronic device (400) can receive confirmation in response to receiving a confirmation request (710).

[0163] Receiving confirmation input by the electronic device (400) may include receiving an action for device authentication from the user by the electronic device (400) (e.g., receiving user input through the user interface (1120)) or / and performing an action for confirmation without user intervention by the electronic device (400) (e.g., transmitting an authentication signal including infrared code set information).

[0164] When the electronic device (400) receives a confirmation, it can provide a response regarding the success of the confirmation to the user device (140) (711).

[0165] When the user device (140) receives a response regarding successful confirmation from the electronic device (400), it can determine that device authentication is complete.

[0166] Accordingly, the user device (140) can provide information for onboarding to the electronic device (400) (712).

[0167] The electronic device (400) can request onboarding to the cloud network (130) based on the received onboarding information (713).

[0168] In the process described above, the user device (140) or electronic device (400) can provide the user with a guide for device authentication, which will be described below with reference to FIGS. 8 to 11.

[0169] FIG. 8 is a diagram illustrating an example of a screen displayed through a user interface of a user device after an electronic device is identified according to one embodiment.

[0170] The user device (140) may include a user interface (e.g., the user interface (420) of FIG. 4) and / or a processor (e.g., the processor (440) of FIG. 4). The user device (140) may include an input interface (e.g., the input interface (420a) of FIG. 4) and / or an output interface (e.g., the output interface (420b) of FIG. 4).

[0171] For convenience of explanation, the user interface of the user device (140) will be described as a first interface (1420), and the processor of the user device (140) will be described as a first processor (1440). In addition, the input interface of the user device (140) will be described as a first input interface (1420a), and the output interface of the user device (140) will be described as a first output interface (1420b).

[0172] According to one embodiment, the first processor (1440) may control the first interface (1420) to display the screen illustrated in FIG. 8 when the electronic device (400) is identified in the scan step (702) of FIG. 7.

[0173] Referring to FIG. 8, the first processor (1440) can control the first user interface (1420) to display an electronic device (400) identified through a scan.

[0174] The first user interface (1420) displaying the identified electronic device (400) may include displaying a designation or indicator (e.g., an icon) of the identified electronic device (400).

[0175] For example, if the identified electronic device (400) is a refrigerator (112), the first processor (1440) may control the first user interface (1420) to display 'BESPOKE Refrigerator' or an icon depicting a refrigerator, which refers to the identified refrigerator (112), through the output interface (1420b) (801).

[0176] Additionally, the first processor (1440) can control the first user interface (1420) to display at least one button for receiving instructions from the user regarding whether to establish a connection with the identified electronic device (400).

[0177] As described above, in the present disclosure, the 'button' may be replaced with a UI element (User Interface Element), a tact switch, a push switch, a slide switch, a toggle switch, a micro switch, a touch switch, a touch pad, a touch screen, a jog dial, and / or a microphone.

[0178] For example, the first processor (1440) can control the first user interface (1420) to display a button for receiving instructions regarding whether to not perform a connection with the refrigerator (112) identified through the input interface (1420a), whether to perform the connection now, or whether to perform the connection later (802).

[0179] The first processor (1440) can control the first user interface (1420) to display some of the aforementioned components by omitting them, and can additionally display other components necessary to provide the user with information about the identified electronic device (400) in addition to the aforementioned configuration and to receive instructions from the user as to whether to perform a communication connection with the identified electronic device (400).

[0180] FIG. 9 is a diagram illustrating an example of a screen displayed through a user interface of a user device while data communication for coordinating a device authentication method is performed according to one embodiment.

[0181] According to one embodiment, the first processor (1440) may control the first interface (1420) to display the screen illustrated in FIG. 9 in steps (705 to 708) in which data communication for coordinating the device authentication method of FIG. 7 is performed after communication with the electronic device (400) is established.

[0182] According to various embodiments, the first processor (1440) may control the first interface (1420) to display the screen illustrated in FIG. 9 not only in the steps (705 to 708) of performing data communication for coordinating the device authentication method, but also prior to that, in the steps (703 to 704) of connecting communication.

[0183] Referring to FIG. 9, the first processor (1440) may control the first user interface (1420) to indicate that a communication connection is currently being established between the electronic device (400) and the user device (140) and that data exchange for coordinating the device authentication method is being performed. At this time, the user must wait until the data exchange for coordinating the device authentication method is completed.

[0184] For example, referring to FIG. 9, the first processor (1440) can control the first user interface (1420) to display the time required to tune the device authentication method and / or the time remaining until the data exchange for tuning the device authentication method is completed through a bar-type indicator (901).

[0185] Additionally, the first processor (1440) may control the first user interface (1420) to display at least one button for receiving instructions from the user as to whether to continue performing the device authentication operation.

[0186] At this time, the action for device authentication may include at least one of an action for communication connection or an action for coordinating a device authentication method.

[0187] For example, referring to FIG. 9, the first processor (1440) can control the first interface (1420) to display a button (e.g., a Cancel button) on the first output interface (1420b) for receiving an instruction from the user regarding whether to cancel an operation for device authentication currently being performed (902).

[0188] For example, if a user presses a button to receive instructions on whether to cancel an action for device authentication, the first processor (1440) may cancel an action for a communication connection or an action for coordinating a device authentication method that was being performed.

[0189] At this time, canceling the action being performed may mean terminating the connection between the user device (140) and the electronic device (400) or no longer performing data communication to coordinate the device authentication method.

[0190] The longer it takes for data communication to coordinate device authentication, the more likely it is that the user will press a button midway through the authentication process to receive instructions on whether to cancel the device authentication action.

[0191] Therefore, to improve customer experience by preventing users from waiting for long periods of time, it may be necessary to either avoid displaying screens like those in Figure 9 or to minimize the time it takes for them to be displayed. This will be described below with reference to Figures 10 to 12.

[0192] FIG. 10 is a diagram illustrating an example of a screen displayed through a user interface of a user device to guide authentication to be performed according to an authentication method of an electronic device tuned according to one embodiment.

[0193] According to one embodiment, the first processor (1440) may control the first interface (1420) to output a guide (hereinafter, “first guide”) requesting confirmation for device authentication to the user in the confirmation request step (709) of FIG. 7 after coordinating the electronic device (400) and the device authentication method.

[0194] A first guide according to one embodiment may include a verbal guide including a description of the action and / or a visual guide including an illustration, a graphic guide, a visual reference, etc. regarding the action.

[0195] For example, if confirmation for device authentication includes an action to be performed by the user, as illustrated in FIG. 10, the first processor (1440) may provide a first guide so that the user can open and close the door of the refrigerator (112) once.

[0196] At this time, the first guide may include a verbal guide such as 'Opening and Closing the door to verify yout refrigerator' and a visual guide such as a graphic guide of the refrigerator door opening and closing.

[0197] Although not shown in Figure 10, confirmation for device authentication may not include actions that must be performed by the user.

[0198] For example, when an ultrasonic signal or an IR (Infrared Light) signal is used as a device authentication method between a user device (140) and an electronic device (400), device authentication can be performed through signal exchange between the respective devices.

[0199] At this time, the first guide displayed on the first interface (1420) by the first processor (1440) may include a verbal and / or visual guide indicating that the device authentication process is currently being performed.

[0200] The types of guides included in the first guide are not limited to the examples described above, and may further include guides that convey information about confirmation through the five senses, or may omit some of the guides described above.

[0201] Above, the screen displayed on the interface of the user device (140) (i.e., the first interface (1420)) during the device authentication process has been described. As there are multiple electronic devices (400) of the same type in an environment where the user device (140) and the electronic device (400) are performing onboarding, there may be cases where the user is unable to know which of the multiple electronic devices (400) around him / her is currently performing the onboarding process. In response to this, the guide (hereinafter referred to as the “second guide”) displayed on the interface of the electronic device (400) that is the object of authentication during the device authentication process will be described below.

[0202] FIG. 11 is a diagram illustrating an example of a screen displayed through a user interface of an electronic device to receive confirmation for authentication of an electronic device according to one embodiment.

[0203] The electronic device (400) may include a user interface (e.g., the user interface (420) of FIG. 4) and / or a processor (e.g., the processor (440) of FIG. 4). The user interface of the electronic device (400) may include an input interface (e.g., the input interface (420a) of FIG. 4) and / or an output interface (e.g., the output interface (420b) of FIG. 4).

[0204] The user interface of the electronic device (400) is referred to as a second interface (4420), and the processor of the electronic device (400) is referred to as a second processor (4440). In addition, the input interface of the electronic device (400) is referred to as a second input interface (4420a), and the output interface of the user device (140) is referred to as a second output interface (4420b).

[0205] According to one embodiment, the second processor (4440) can control the second interface (4420) to output a second guide indicating that the electronic device (400) is in a state where it can receive a confirmation in the confirmation request step (709) of FIG. 7.

[0206] By displaying the second guide on the second interface (4420), the user can identify the current user device (140) and the electronic device (400) performing device authentication. In other words, the user can recognize which electronic device (400) is the target for performing the operation for confirmation included in the first guide displayed on the first interface (1420).

[0207] According to one embodiment, the second processor (4440) may display a preset indicator on the second user interface (4440) to indicate that the electronic device (400) is in a state where it can receive a confirmation input.

[0208] For example, if the electronic device (400) performing device authentication is a refrigerator, the second processor (4440) can control the second user interface (4420) to blink an “AP” sign on the second output interface (4420b), thereby transmitting to the user information that the electronic device (400) currently performing device authentication is the refrigerator (112) whose “AP” sign is blinking and that the refrigerator (112) has now transitioned to a state in which confirmation can be input. At this time, the indicator displayed on the second output interface (4420b) is not limited to the present disclosure, and if it is appropriate to transmit information to the user about what electronic device (400) currently performing device authentication is and / or information that the electronic device (400) has now transitioned to a state in which confirmation can be input, it can be employed as an indicator included in the second guide displayed on the second output interface (4420b).

[0209] In one embodiment, the user may recognize the second guide displayed on the second output interface (4420b) and input confirmation for device authentication into the electronic device (400) on which the second guide is displayed. For example, referring to FIG. 11, the user may input confirmation for device authentication by performing an action of pressing the OK button on the second input interface (4420a) for a preset period of time.

[0210] When performing a device authentication process for onboarding an electronic device (400) through the aforementioned series of processes, it takes a long time (e.g., approximately 8 to 10 seconds) from the time the user requests a communication connection between the user device (140) and the electronic device (400) until the user inputs confirmation for device authentication. Accordingly, the user may cancel the connection midway or abandon the onboarding process.

[0211] According to one aspect of the present invention, while data communication for coordinating a device authentication method is performed as shown in the drawing in FIG. 9, a screen displayed through a user device (140) can be eliminated or the display time can be shortened as much as possible to prevent connection cancellation in the middle and increase the connection rate.

[0212] This means that the customer experience can be improved by eliminating the need for users to wait while data communication is performed to coordinate device authentication methods.

[0213] In this way, according to one embodiment, the first processor (1420) of the user device (140) can guide, in response to each electronic device (400), device authentication to be performed through the most basic and most frequently used method (hereinafter referred to as the “default device authentication method”) among the multiple device authentication methods that each electronic device (400) can perform. Guiding the default device authentication method may be performed not only by the first processor (1420) of the user device (140) but also by the second processor (4420) of the electronic device (400).

[0214] Hereinafter, with reference to FIGS. 10 to 12, a process of performing a default device authentication method in a user device (140) or electronic device (400) will be described.

[0215] FIG. 12 is a flowchart illustrating a process by which a user device and an electronic device perform default device authentication according to one embodiment.

[0216] According to one embodiment, the user device (140) can identify an electronic device (400) in which a communication standby state is activated through scanning (1201).

[0217] At this time, the user device (140) can receive a broadcast packet periodically transmitted from the electronic device (400) in which the communication standby state is activated, and the broadcast packet can include whether the electronic device (400) supports a service for default device authentication.

[0218] The user device (140) may request a communication connection based on identification information included in a broadcast packet or preset password information of the electronic device (400) when the electronic device (400) is identified (1202). At this time, as described above with reference to FIG. 8, the first processor (1440) of the user device (140) may control the first user interface (1420) to display at least one button for receiving instructions from the identified electronic device (400) and / or the user regarding whether to establish a connection with the identified electronic device (400).

[0219] An electronic device (400) that has received a communication connection request (example of 1202) can connect communication based on the received identification information or preset password information (1203). At this time, the connected communication may be one of Wi-Fi communication, Bluetooth communication, low-power Bluetooth communication, and / or Zigbee communication.

[0220] When communication is connected between the user device (140) and the electronic device (400), the user device (140) or the electronic device (400) may display a guide for device authentication according to the default device authentication method (1204).

[0221] Specifically, the first processor (1440) of the user device (140) can control the first user interface (1420) to output a first guide requesting confirmation according to a preset default authentication method based on the connection of communication.

[0222] The second processor (4440) of the electronic device (400) can control the electronic device (400) to switch to a state in which a confirmation for preset default authentication can be input based on the connection of communication.

[0223] Additionally, the second processor (4440) of the electronic device (400) can control the second user interface (4420) to output a second guide indicating that the electronic device (400) is in a state where it can receive confirmation according to a preset confirmation method based on the connection of communication.

[0224] In one embodiment, the first guide and the second guide may be displayed simultaneously or in a different time. That is, the first guide and the second guide may be displayed with a time difference.

[0225] For example, the first processor (1440) of the user device (140) may control the first user interface (1420) to display the first guide in step 703 of FIG. 7 (i.e., a state in which communication between the user device (140) and the electronic device (400) is connected), and the second processor (4440) of the electronic device may control the second user interface (4420) to display the second guide in step 705 or step 707 of FIG. 7 (i.e., a state in which a resource for data exchange is requested from the user device (140).

[0226] The default device authentication method may vary depending on the electronic device (400) being authenticated, and may be preset as the most basic or most frequently used method among the multiple device authentication methods that each electronic device (400) can perform. For example, the default device authentication method may be preset as a simple method. The simple method may include authentication performed by the user confirming a simple action to the electronic device (400), such as pressing a preset button for a preset time or performing a preset action (e.g., opening and closing a refrigerator (112) door once).

[0227] When the second processor (4400) of the electronic device (400) receives a confirmation from the user according to a preset default device authentication method, it can transmit a confirmation success response to the user device (140).

[0228] Accordingly, the first processor (1440) of the user device (140) can determine whether authentication according to the preset default device authentication method is successful (1205).

[0229] If authentication according to the preset default device authentication method fails (No of 1205), the user device (140) or electronic device (400) may display a guide for device authentication according to the default device authentication method again.

[0230] If authentication according to the preset default device authentication method is successful (example of 1205), the user device (140) can set the status that device authentication according to the default device authentication method is completed to 1 bit and store it in the RAM (Random Access Memory) of the memory (450) (1206).

[0231] After the data exchange between the user device (140) and the electronic device (400) for determining the final device authentication method is completed, the first processor (1420) of the user device (140) can determine the final device authentication method (1207).

[0232] If authentication according to the preset default device authentication method fails (No of 1205), the first processor (1420) of the user device (140) may perform data exchange between the user device (140) and the electronic device (400) to determine the final device authentication method without separately storing the device authentication failure, and may determine the final device authentication method.

[0233] At this time, the final device authentication method may be the same or different from the default device authentication method.

[0234] For example, the final device authentication method may be performed through at least one of the following methods: a BUA (Broadband Ultrasound Attenuation) method that uses ultrasonic signals to further enhance security; a method of entering a preset serial number corresponding to each electronic device (400), a method of scanning a preset QR code; or a method of using various authentication means such as a user's PIN, pattern, fingerprint recognition, or facial recognition.

[0235] The first processor (1440) of the user device (140) can determine whether the final device authentication method determined through data exchange is the same as the default authentication method (1208).

[0236] If the final device authentication method is the same as the default authentication method (example of 1208), the first processor (1440) of the user device (140) can maintain the default device authentication based on the information about the default device authentication success status stored in 1206 (1209).

[0237] Accordingly, the first processor (1440) of the user device (140) may report that device authentication is complete and transmit onboarding information to the authenticated electronic device (400) so that the authenticated electronic device (400) can be onboarded to the cloud network (130).

[0238] If the final device authentication method is not the same as the default authentication method (No of 1208), the first processor (1440) of the user device (140) may cancel authentication according to the existing default device authentication method (1210) and perform an operation to perform device authentication according to the final device authentication method (1211). In addition, the first processor (1440) of the user device (140) may also transmit a control signal to the electronic device (400) so that device authentication according to the final device authentication method is performed.

[0239] When device authentication according to the final device authentication method is completed, the first processor (1440) of the user device (140) can transmit onboarding information to the authenticated electronic device (400) so that the authenticated electronic device (400) can be onboarded to the cloud network (130).

[0240] By performing device authentication according to a preset default authentication method, the user can receive a guide for device authentication immediately after requesting a communication connection with the identified electronic device (400) without having to wait until data exchange for coordinating the device authentication method is completed, as described with reference to FIG. 9, thereby reducing the connection time perceived by the user.

[0241] According to various embodiments, a series of processes performed by the first processor (1440) of the user device (140) described above may also be performed by the second processor (4440) of the electronic device (400).

[0242] FIG. 13 is a flowchart illustrating a process by which a user device and an electronic device perform default device authentication according to another embodiment.

[0243] According to one embodiment, the user device (140) may identify an electronic device (400) in which a communication standby state is activated through a scan (1401), and request a communication connection based on identification information included in a broadcast packet received from the electronic device (400) or preset password information of the electronic device (400) (1402). At this time, the first processor (1440) of the user device (140) may control the first user interface (1420) to display at least one button for receiving an instruction related to whether to perform a connection with the identified electronic device (400) and / or the user.

[0244] Afterwards, the electronic device (400) that has received the communication connection request (example of 1402) can connect the communication based on the received identification information or preset password information (1403). At this time, the connected communication may be one of Wi-Fi communication, Bluetooth communication, low-power Bluetooth communication, and / or Zigbee communication.

[0245] The broadcast packet transmitted by the electronic device (400) may include a request as to whether the user device (140) supports a service for default device authentication.

[0246] If the user device (140) does not support a service for default device authentication, the user device (140) may not display a guide (i.e., the first guide) for device authentication according to the default device authentication method. However, even in this case, the first processor (1440) of the user device (140) may transmit a control signal to the second processor (4440) of the electronic device (400) through communication so that the electronic device (400) can be switched to a state in which a confirmation for preset default authentication can be input.

[0247] Accordingly, when communication is connected between the user device (140) and the electronic device (400), only the electronic device (400) can display a guide (i.e., a second guide) for device authentication according to the default device authentication method (1404).

[0248] Specifically, the second processor (4440) of the electronic device (400) can control the second user interface (4420) to output a second guide indicating that the electronic device (400) is in a state where it can receive confirmation according to a preset confirmation method based on the connection of communication.

[0249] Additionally, the second processor (4440) of the electronic device (400) that received the control signal can switch the electronic device (400) to a state in which it can receive confirmation for default authentication.

[0250] The description regarding the default device authentication method preset according to the electronic device (400) that is the subject of the authentication described above in Fig. 12 can be applied equally.

[0251] When the second processor (4400) of the electronic device (400) receives a confirmation from the user according to a preset default device authentication method, it can transmit a confirmation success response to the user device (140).

[0252] Accordingly, the first processor (1440) of the user device (140) determines whether authentication according to the preset default device authentication method is successful (1405), and if the default device authentication fails (No of 1405), the second processor (4440) of the electronic device (400) can display a second guide again indicating that the electronic device (400) is currently in a state where confirmation can be input according to the preset confirmation method.

[0253] In this way, even if the user device (140) does not support a service for default device authentication, the user can be guided to perform default device authentication by displaying a second guide indicating that the electronic device (400) is in a state where confirmation can be input.

[0254] If authentication according to the preset default device authentication method is successful (example of 1405), the user device (140) can set the status that device authentication according to the default device authentication method is completed to 1 bit and store it in the RAM (Random Access Memory) of the memory (450) (1406).

[0255] After the data exchange between the user device (140) and the electronic device (400) for determining the final device authentication method is completed, the first processor (1420) of the user device (140) can determine the final device authentication method (1407).

[0256] As mentioned above, the final device authentication method may be the same as or different from the default device authentication method.

[0257] For example, the final device authentication method may be performed through at least one of the following methods: a BUA (Broadband Ultrasound Attenuation) method that uses ultrasonic signals to further enhance security; a method of entering a preset serial number corresponding to each electronic device (400), a method of scanning a preset QR code; or a method of using various authentication means such as a user's PIN, pattern, fingerprint recognition, or facial recognition.

[0258] The first processor (1440) of the user device (140) can determine whether the final device authentication method determined through data exchange is the same as the default authentication method (1408).

[0259] If the final device authentication method is the same as the default authentication method (example of 1408), the first processor (1440) of the user device (140) can maintain the default device authentication based on the information about the default device authentication success status stored in 1406 (1409).

[0260] Accordingly, the first processor (1440) of the user device (140) may report that device authentication is complete and transmit onboarding information to the authenticated electronic device (400) so that the authenticated electronic device (400) can be onboarded to the cloud network (130).

[0261] On the other hand, if the final device authentication method is not the same as the default authentication method (No of 1408), the first processor (1440) of the user device (140) can cancel authentication according to the existing default device authentication method (1410) and perform an operation to perform device authentication according to the final device authentication method (1411).

[0262] For example, even if the user device (140) does not support a service for default device authentication, a guide according to the final device authentication method determined through data exchange can be provided, so the user device (140) can display a guide requesting confirmation for device authentication according to the final device authentication method.

[0263] When device authentication according to the final device authentication method is completed, the first processor (1440) of the user device (140) can transmit onboarding information to the authenticated electronic device (400) so that the authenticated electronic device (400) can be onboarded to the cloud network (130).

[0264] That is, by performing device authentication according to a preset default authentication method, the user does not need to wait until the data exchange for coordinating the device authentication method is completed, thereby reducing the connection time perceived by the user and improving convenience.

[0265] According to various embodiments, a series of processes performed by the first processor (1440) of the user device (140) described above may also be performed by the second processor (4440) of the electronic device (400).

[0266] According to one embodiment, a user device includes a communication unit that communicates with an electronic device registered in a cloud server; a user interface; and a processor electrically connected to the communication unit and the user interface; wherein the processor controls the user interface to output a first guide requesting confirmation according to a preset default authentication method based on the communication connection between the communication unit and the electronic device, and transmits a control signal to the electronic device to output a second guide indicating that the electronic device is in a state where the confirmation according to the preset default authentication method can be input.

[0267] The first guide may include at least one of a verbal guide including a description of the operation for the confirmation or a visual guide including a visual indicator.

[0268] The above visual indicator may include at least one of an illustration, a graphic guide or a visual reference regarding the operation for the confirmation.

[0269] The second guide may include a preset indicator to indicate that the electronic device is capable of receiving the confirmation.

[0270] The above first guide and the above second guide can be outputted simultaneously or sequentially.

[0271] The above-mentioned connected communication may be one of Wi-Fi communication, Bluetooth communication, low-power Bluetooth communication, or Zigbee communication.

[0272] The user device further includes a memory capable of storing status information regarding the default device authentication; and the processor can set a status indicating that device authentication according to the default device authentication method has been completed to 1 bit and store the status in the memory based on whether authentication according to the preset default device authentication method has been successful.

[0273] The processor may determine a final device authentication method through data exchange with the electronic device after device authentication according to the default device authentication method is successful, and determine whether the final device authentication method and the default device authentication method are the same method.

[0274] The processor may maintain a state in which device authentication according to the default device authentication method is completed based on the determination that the final device authentication method and the default device authentication method are the same.

[0275] The processor may cancel completion of device authentication according to the default device authentication method based on the determination that the final device authentication method and the default device authentication method are different, and perform device authentication according to the final device authentication method.

[0276] A system for onboarding an electronic device according to one embodiment comprises: a cloud network; a user device including a first communication unit for communicating with an electronic device registered in the cloud network, a first user interface, and a first processor electrically connected to the first communication unit and the first user interface; and an electronic device including a second communication unit for communicating with the user device, a second user interface, and a second processor electrically connected to the second communication unit and the second user interface; wherein the first processor comprises:

[0277] The first user interface may be controlled to output a first guide requesting confirmation according to a preset default authentication method based on the communication connection between the first communication unit and the electronic device, and the second processor may control the second user interface to output a second guide indicating that the electronic device is in a state where it can receive the confirmation according to the preset default authentication method.

[0278] The first guide may include at least one of a verbal guide including a description of an action for the confirmation or a visual guide including a visual indicator of an action for the confirmation.

[0279] The above visual indicator may include at least one of an illustration, a graphic guide or a visual reference regarding the operation for the confirmation.

[0280] The second guide may include a preset indicator to indicate that the electronic device is in a state where it can receive the confirmation.

[0281] The above first guide and the above second guide can be outputted simultaneously or sequentially.

[0282] The second processor can switch the electronic device to a state in which it can receive confirmation according to the preset default authentication method based on the communication connection between the second communication unit and the user device.

[0283] The above-mentioned connected communication may be one of Wi-Fi communication, Bluetooth communication, low-power Bluetooth communication, or Zigbee communication.

[0284] The user device further includes a first memory capable of storing status information regarding the default device authentication; and the first processor can set a status indicating that device authentication according to the default device authentication method has been completed to 1 bit and store the status in the first memory based on whether authentication according to the preset default device authentication method has been successful.

[0285] The first processor, after device authentication according to the default device authentication method is successful, determines a final device authentication method through data exchange with the electronic device, and can determine whether the final device authentication method and the default device authentication method are the same method.

[0286] In one embodiment, a method for onboarding an electronic device comprises: connecting communication between a user device including a first user interface and an electronic device including a second user interface and registered in a cloud network; outputting a first guide requesting confirmation according to a preset default authentication method on the first user interface based on the communication connection between the user device and the electronic device; and simultaneously or concurrently with the first guide, outputting a second guide indicating that the electronic device is in a state where it can receive the confirmation according to the preset default authentication method on the second user interface.

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

[0288] The disclosed embodiments have been described with reference to the attached drawings as described above. Those skilled in the art will understand that the present invention can be implemented in forms other than the disclosed embodiments without altering the technical spirit or essential features of the present invention. The disclosed embodiments are illustrative and should not be construed as limiting.

[0289] Meanwhile, the disclosed embodiments may be implemented in the form of a recording medium storing computer-executable instructions. The instructions may be stored in the form of program code, and when executed by a processor, may generate program modules to perform the operations of the disclosed embodiments. The recording medium may be implemented as a computer-readable recording medium.

[0290] Computer-readable storage media include all types of storage media that store instructions that can be deciphered by a computer. Examples include read-only memory (ROM), random access memory (RAM), magnetic tape, magnetic disks, flash memory, and optical data storage devices.

[0291] Additionally, a computer-readable recording medium may be provided in the form of a non-transitory storage medium. Here, the term "non-transitory storage medium" simply means a tangible device that does not contain signals (e.g., electromagnetic waves). This term does not distinguish between cases where data is permanently stored in the storage medium and cases where data is temporarily stored. For example, a "non-transitory storage medium" may include a buffer in which data is temporarily stored.

[0292] According to one embodiment, the method according to various embodiments disclosed in the present document 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 recording medium (e.g., compact disc read only memory (CD-ROM)), or may be distributed online (e.g., downloaded or uploaded) via an application store (e.g., Play Store™) or directly between two user devices (e.g., smartphones). In the case of online distribution, at least a portion of the computer program product (e.g., a downloadable app) may be temporarily stored or temporarily generated on a machine-readable recording medium, such as the memory of a manufacturer's server, an application store's server, or an intermediary server.

Claims

1. A communication unit that connects electronic devices registered on a cloud server and communicates with them; User interface; and A processor electrically connected to the communication unit and the user interface; The above processor, Control the user interface so that a first guide requesting confirmation according to a preset default authentication method is output based on the communication connection between the communication unit and the electronic device, A user device that transmits a control signal to the electronic device so as to output a second guide indicating that the electronic device is in a state where it can receive the confirmation according to the preset default authentication method.

2. In paragraph 1, The above first guide is, A user device comprising at least one of a verbal guide including a description of the action for said confirmation or a visual guide including a visual indicator.

3. In paragraph 2, The above visual indicators are, A user device including at least one of an illustration, a graphic guide or a visual reference regarding the operation for said confirmation.

4. In paragraph 1, The second guide above is, A user device including a preset indicator to indicate that said electronic device is capable of receiving said confirmation.

5. In paragraph 1, The above first guide and the above second guide, User devices that output at the same time or simultaneously.

6. In paragraph 1, The above connected communication is, A user device that communicates using either Wi-Fi, Bluetooth, low-power Bluetooth, or Zigbee.

7. In paragraph 1, The above user device, Further comprising a memory capable of storing status information regarding the above default device authentication; The above processor, A user device that sets a status indicating that device authentication according to the default device authentication method has been completed to 1 bit and stores the same in the memory based on the success of authentication according to the preset default device authentication method.

8. In paragraph 7, The above processor, After device authentication is successful according to the above default device authentication method, the final device authentication method is determined through data exchange with the electronic device. A user device that determines whether the final device authentication method and the default device authentication method are the same method.

9. In paragraph 8, The above processor, A user device that maintains a state in which device authentication according to the default device authentication method is completed based on the determination that the final device authentication method and the default device authentication method are the same.

10. In paragraph 8, The above processor, A user device that cancels completion of device authentication according to the default device authentication method and performs device authentication according to the final device authentication method based on the determination that the final device authentication method and the default device authentication method are different methods.

11. Cloud Network; A user device including a first communication unit for connecting communication with an electronic device registered in the cloud network, a first user interface, and a first processor electrically connected to the first communication unit and the first user interface; and An electronic device comprising a second communication unit for communicating with the user device, a second user interface, and a second processor electrically connected to the second communication unit and the second user interface; The above first processor, Controlling the first user interface so that a first guide requesting confirmation according to a preset default authentication method is output based on the communication connection between the first communication unit and the electronic device; The second processor, A system for onboarding an electronic device that controls the second user interface to output a second guide indicating that the electronic device is in a state where it can receive the confirmation according to a preset default authentication method.

12. In paragraph 11, The above first guide is, A system for onboarding an electronic device comprising at least one of a verbal guide including a description of the actions for said confirmation or a visual guide including a visual indicator of the actions for said confirmation.

13. In paragraph 12, The above visual indicators are, A system for onboarding an electronic device, comprising at least one of an illustration, a graphic guide or a visual reference regarding the operations for said confirmation.

14. In paragraph 11, The second guide above is, A system for onboarding an electronic device including a preset indicator to indicate that the electronic device is capable of receiving the confirmation.

15. Connecting communication between a user device including a first user interface and an electronic device registered to a cloud network including a second user interface; Outputting a first guide requesting confirmation according to the preset default authentication method on the first user interface based on the communication connection between the user device and the electronic device, A method for onboarding an electronic device, wherein the electronic device outputs a second guide to the second user interface, simultaneously or concurrently with the first guide, indicating that the electronic device is in a state where it can receive the confirmation according to the preset default authentication method.

Images