Method and device for providing service in system supporting multiple administrators

Abstract

The present disclosure relates to a method and a device for providing an IoT service in an IoT system supporting a multi-administrator service. According to an embodiment of the present disclosure, a method of a first device in an Internet of Things (IoT) system supporting a multi-administrator service may comprise: when an additional device is commissioned by a second device, an operation of checking whether first network information set in the first device is identical to second network information set in the second device; if the first network information and the second network information are different from each other, an operation of transmitting, to the second device, a confirmation request for whether to allow a change in network settings of the first device; and an operation of receiving, from the second device, a response message including the first network information and an indicator indicating whether to allow a change in network settings.

Description

Method and device for providing services in a system supporting multiple administrators

[0001] The present disclosure relates to a method and apparatus for providing a communication service for use of an IoT device in an IoT (Internet of Things) system.

[0002] The Internet is evolving from a human-centric network where humans create and consume information to an Internet of Things (IoT) network where information is exchanged and processed between distributed components such as objects. The Internet of Everything (IoE) technology, which combines IoT technology with big data processing technology through connections to cloud servers, is also emerging. To implement the IoT, technological elements such as sensing technology, wired and wireless communication and network infrastructure, service interface technology, and security technology are required. Recently, technologies such as sensor networks for connecting objects, Machine-to-Machine (M2M) communication, and Machine-Type Communication (MTC) are being researched.

[0003] In an IoT environment, intelligent IT (Internet Technology) services can be provided that collect and analyze data generated from connected objects, creating new value in human life. IoT, through the convergence and integration of existing IT (information technology) technologies with various industries, can be applied to fields such as smart homes, smart buildings, smart cities, smart or connected cars, smart grids, healthcare, smart appliances, and advanced medical services.

[0004] Additionally, with the recent advancement of information and communication technology, various wireless communication technologies are being developed. Among these wireless communication technologies, Wireless Local Area Network (WLAN) is a technology that allows wireless Internet access in homes, businesses, or specific service areas using electronic devices such as smartphones and laptops based on radio frequency technology. The WLAN includes various wireless access technologies proposed by the Institute of Electrical and Electronics Engineers (IEEE) 802.11x standard, and the WLAN technology is also referred to by the term, for example, Wi-Fi.

[0005] Matter is also being studied as an example of a smart home standard for managing and connecting various smart home devices in an IoT environment. Matter is an integrated open-source connectivity standard for IoT devices, enabling smart devices and platforms to work together seamlessly in an IoT environment.

[0006] The present disclosure provides a method and apparatus for performing device registration of an IoT device in a system supporting multi-admin functionality.

[0007] According to one embodiment of the present disclosure, in an Internet of Things (IoT) system supporting a multi-manager service, a method of a first device may include, when commissioning an additional device by a second device, an operation of checking whether first network information set in the first device is the same as second network information set in the second device; an operation of transmitting a confirmation request for whether to allow a change in network settings of the first device to the second device if the first network information and the second network information are different from each other; an operation of receiving a response message from the second device including the first network information and an indicator indicating whether to allow a change in the network settings; and an operation of performing a process of registering the additional device with the second device based on the response message.

[0008] According to one embodiment of the present disclosure, in an Internet of Things (IoT) system supporting a multi-manager service, a method of a second device may include: initiating an additional device commissioning process that enables the second device to manage a first device; receiving, from the first device, a confirmation request for whether to allow a change in network settings of the first device if first network information set in the first device and second network information set in the second device are different from each other; transmitting, to the first device, a response message including the first network information and an indicator indicating whether to allow a change in the network settings; and performing the additional device registration process with the first device based on the response message.

[0009] According to one embodiment of the present disclosure, in an IoT (Internet of Things) system supporting a multi-manager service, a first device may include a transceiver; and a processor. The processor may, when commissioning an additional device by a second device, check whether first network information set in the first device is identical to second network information set in the second device, and, if the first network information and the second network information are different from each other, control to transmit a confirmation request for whether to allow a change in network settings of the first device to the second device, receive a response message including the first network information and an indicator indicating whether to allow a change in network settings from the second device, and perform a process of registering the additional device with the second device based on the response message.

[0010] According to one embodiment of the present disclosure, in an Internet of Things (IoT) system supporting a multi-manager service, a second device may include a transceiver; and a processor. The processor may initiate an additional device commissioning process that allows the second device to manage a first device, and, if first network information set in the first device and second network information set in the second device are different from each other, receive a confirmation request from the first device regarding whether to allow a change in network settings of the first device, control to transmit a response message including the first network information and an indicator indicating whether to allow a change in network settings to the first device, and perform a process of registering the first device and the additional device based on the response message.

[0011] The method and device according to the embodiment of the present disclosure can perform network settings by considering user intention when registering an IoT device in a system supporting a multi-admin function.

[0012] FIG. 1 is a diagram for explaining a Multi-Admin registration process in an IoT environment according to one embodiment of the present disclosure.

[0013] FIG. 2 is a diagram for explaining a device registration process (commissioning) according to one embodiment of the present disclosure.

[0014] FIG. 3A and FIG. 3B are diagrams for explaining the operation of devices performing a device registration process (commissioning) according to one embodiment of the present disclosure.

[0015] FIG. 4 is a diagram for explaining a multi-admin registration process in a single AP configuration environment according to one embodiment of the present disclosure.

[0016] FIG. 5 is a diagram for explaining a multi-admin registration process in a multiple AP configuration environment according to one embodiment of the present disclosure.

[0017] FIG. 6A and FIG. 6B are diagrams illustrating an example of a case where a setting change notification is sent to a new admin when registering a multi-admin according to one embodiment of the present disclosure.

[0018] FIG. 7A and FIG. 7B are diagrams illustrating another example of a case where a setting change notification is sent to a new admin when registering a multi-admin according to one embodiment of the present disclosure.

[0019] FIG. 8A and FIG. 8B are diagrams illustrating an example of a case where a setting change notification is sent to the current admin when registering a multi-admin according to one embodiment of the present disclosure.

[0020] FIG. 9A and FIG. 9B are diagrams illustrating another example of a case where a setting change notification is sent to the current admin when registering a multi-admin according to one embodiment of the present disclosure.

[0021] FIG. 10 is a diagram illustrating an example of a case in which connection information is transmitted in advance before starting to register an additional device according to one embodiment of the present disclosure.

[0022] FIG. 11 is a drawing for explaining the configuration of a first electronic device according to one embodiment of the present disclosure.

[0023] FIG. 12 is a drawing for explaining the configuration of a second electronic device according to one embodiment of the present disclosure.

[0024] The operating principles of the present disclosure are described in detail below with reference to the attached drawings. In the following description of the present disclosure, detailed descriptions of related known functions or configurations will be omitted if they are deemed to unnecessarily obscure the gist of the present disclosure. Furthermore, the terms described below are defined based on the functions of the present disclosure and may vary depending on the intent or custom of the user or operator. Therefore, their definitions should be based on the overall content of this specification.

[0025] For the same reason, some components in the attached drawings are omitted or schematically depicted. Furthermore, the dimensions of each component do not entirely reflect its actual size. Identical or corresponding components in each drawing are assigned the same reference numbers.

[0026] The advantages and features of the present disclosure, and methods for achieving them, will become clearer with reference to the embodiments described below in detail with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below and may be implemented in various different forms. The various embodiments are provided to ensure that the present disclosure is complete and to fully convey the scope of the present disclosure to those skilled in the art, and the present disclosure is defined solely by the scope of the claims. Like reference numerals designate like elements throughout the specification.

[0027] At this time, it will be understood that each block of the processing flow diagrams and combinations of the flow diagrams can be performed by computer program instructions. These computer program instructions can be installed in a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing equipment, so that the instructions executed by the processor of the computer or other programmable data processing equipment create a means for performing the functions described in the flow diagram block(s). These computer program instructions can also be stored in a computer-available or computer-readable memory that can direct a computer or other programmable data processing equipment to implement the functions in a specific manner, so that the instructions stored in the computer-available or computer-readable memory can also produce a manufactured item that includes an instruction means for performing the functions described in the flow diagram block(s). Since the computer program instructions may be installed on a computer or other programmable data processing device, a series of operational steps may be performed on the computer or other programmable data processing device to create a computer-executable process, and the instructions that cause the computer or other programmable data processing device to perform the steps for performing the functions described in the flowchart block(s) may also provide steps for performing the functions described in the flowchart block(s).

[0028] Additionally, each block may represent a module, segment, or portion of code that contains one or more executable instructions for performing a specific logical function(s). It should also be noted that in some alternative implementation examples, the functions described in the blocks may occur out of order. For example, two blocks depicted in succession may actually be executed substantially concurrently, or the blocks may sometimes be executed in reverse order, depending on their respective functions.

[0029] The term "~unit" used in various embodiments of the present disclosure refers to a software or hardware component, and the "~unit" performs certain roles. However, the "~unit" is not limited to software or hardware. The "~unit" may be configured to reside on an addressable storage medium and may be configured to regenerate one or more processors. Thus, as an example, the "~unit" includes components such as software components, object-oriented software components, class components, and task components, processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functionality provided within the components and "~units" may be combined into a smaller number of components and "~units" or further separated into additional components and "~units." In addition, the components and "~units" may be implemented to regenerate one or more CPUs within a device or a secure multimedia card. Additionally, in various embodiments of the present disclosure, '~bu' may include one or more processors.

[0030] In this disclosure, phrases such as "A and / or B", "A or B", "at least one of A and B", "at least one of A or B", "A, B, or C", "at least one of A, B, and C", and "at least one of A, B, or C" can each include any one of the items listed together in that phrase, or all possible combinations thereof. Terms such as "first", "second", or "first" or "second" may be used merely to distinguish the corresponding component from other corresponding components and do not limit the corresponding components in any other respect (e.g., importance or order).

[0031] The terms 'manager device', 'IoT device', 'electronic device' or 'device' as used herein may refer to a terminal, a mobile station (MS), a user equipment (UE), a user terminal (UT), a wireless terminal, an access terminal (AT), a terminal, a subscriber unit (SS), a subscriber station (SS), a wireless device, a wireless communication device, a wireless transmit / receive unit (WTRU), a mobile node, a mobile or other terms. Various embodiments of the terminal may include a cellular telephone, a smart phone having a wireless communication function, a personal digital assistant (PDA) having a wireless communication function, a wireless modem, a portable computer having a wireless communication function, a photographing device such as a digital camera having a wireless communication function, a gaming device having a wireless communication function, a music storage and playback home appliance having a wireless communication function, an internet home appliance capable of wireless internet access and browsing, as well as portable units or terminals incorporating combinations of such functions. Additionally, the terminal may include, but is not limited to, an M2M (Machine to Machine) terminal or an MTC (Machine Type Communication) terminal / device. In this specification, the terminal may also be referred to as an electronic device or simply a device.

[0032] In the present disclosure, Multi-Admin (or Multi-Administration) refers to a function by which an electronic device (or IoT device) pre-registered on a first IoT platform can be registered and / or controlled on a second IoT platform that is different from the first IoT platform. On the first IoT platform, a first administrator device (or first Admin) can register and / or control the electronic device (or IoT device), and on the second IoT platform, a second administrator device (or second Admin) can register and / or control the electronic device (or IoT device).

[0033] In one embodiment, a first administrator device (or first Admin) has administrator privileges (Manage privileges) on the first IoT platform and can monitor and / or modify an access control cluster. In one embodiment, a second administrator device (or second Admin) has administrator privileges (Manage privileges) on the second IoT platform and can monitor and / or modify an access control cluster.

[0034] FIG. 1 is a diagram for explaining a Multi-Admin registration process in an IoT environment according to one embodiment of the present disclosure.

[0035] Referring to FIG. 1, even if an IoT device (120) is pre-registered on a first platform (115) where a first administrator device (or first Admin) (110) has administrator authority, the IoT device (120) can be registered and controlled on a second platform (135) where a second administrator device (or second Admin) (130) has administrator authority. According to one embodiment, each of the first administrator device (110), the IoT device (120), and the second administrator device (130) may be connected to the same AP (access point) (140).

[0036] In one embodiment, for connection between the IoT device (120) and the second manager device (130), the first manager device (110) may change and / or set the operation mode of the IoT device (120) to a commissionable mode. In one embodiment, for connection between the IoT device (120) and the second manager device (130), the IoT device (120) may change its operation mode to a commissionable mode.

[0037] The first administrator device (110) can issue (or newly issue) an onboarding payload used during commissioning with an IoT device (120) to the second administrator device (130). The second administrator device (130) can perform a commissioning process with the IoT device (120) based on the issued onboarding payload. Thereafter, the second administrator device (130) can complete the registration of the IoT device (120) with the second platform (135).

[0038] In this disclosure, commissioning may refer to the process of initially registering and / or connecting an IoT device (120) to a platform for controlling the IoT device (120). In this disclosure, commissioning may also be referred to as device registration, device onboarding, or device pairing.

[0039] FIG. 2 is a diagram for explaining a device registration process (commissioning) according to one embodiment of the present disclosure.

[0040] Referring to FIG. 2, a Commissioner (210) in an IoT platform (200) is connected to an AP (or Wi-Fi router) (220) and can control a new device, a Commissionee (230), to be commissioned to the IoT platform (200). Here, each of the Commissioner (210) and the Commissionee (230) may be implemented as an electronic device. The electronic device according to an embodiment of the present disclosure may be a device of various forms. The electronic device may include, for example, a portable communication device (e.g., a smartphone), a computer device, a portable multimedia device, a portable medical device, a camera, a wearable device, a home appliance device, or a wireless earphone. The electronic device according to an embodiment of the present disclosure is not limited to the above-described devices.

[0041] According to one embodiment, during the commissioning process, the commissioner (210) may provide configuration information including at least one of Operational Certification, Access Control List, and Operational network.

[0042] During device onboarding, the commissioner may perform at least one of the following actions: 1) to 3).

[0043] 1) Device attestation

[0044] 2) Issuing an operational certificate (OC) to establish a certificate-based secure session with the device (commissionee) and / or obtaining and delivering an OC; the commissioner issues the OC directly or requests a trusted root certificate authority (CA) to obtain the OC and then delivers it to the device (commissionee).

[0045] 3) Sharing multiple pieces of information (e.g., network configuration information and ACL (access control list)) for device registration of the device (commissionee)

[0046] Once commissioning of the commissioner (230) to the IoT platform (200) is completed, the commissioner (230) can operate as a single node within the IoT platform (200).

[0047] FIG. 3A and FIG. 3B are diagrams for explaining the operation of devices performing a device registration process (commissioning) according to one embodiment of the present disclosure.

[0048] Figures 3a and 3b specifically illustrate the operations between a Commissioner, an Administrator, and a Commissionee during a device commissioning process. In Figures 3a and 3b, the Commissioner, the Administrator, and the Commissionee are intended to indicate the roles of devices during the device commissioning process, and each of the Commissioner, the Administrator, and the Commissionee may be implemented as an electronic device.

[0049] Referring to FIG. 3A, in operation 301, the Commissioner may verify and / or modify at least one of available data, time, timezone, regulatory information, and fabric information.

[0050] In operation 302, the Commissioner and Commissionee may perform device discovery and establish a commissioning channel. In one embodiment, all messages between the Commissioner and Commissionee may be exchanged through the commissioning channel.

[0051] In operation 303, the Commissioner and Commissionee can perform security setup using Password Authenticated Session Establishment (PASE). In one embodiment, all messages between the Commissioner and Commissionee are encrypted with an encryption key derived from PASE, and operations involving implicit administrative privileges can be initiated.

[0052] In operation 304, the Commissioner and Commissionee may set up a fail-safe timer. In operation 305, the Commissioner and Commissionee may transmit and / or receive configuration information including Coordinated Universal Time (UTC) time and regulatory information. In operation 306, the Commissioner and Commissionee may perform operations related to commissionee attension.

[0053] In operation 307, the Commissioner and the Commissionee may exchange an operational Certificate Signing Request (CSR). In operation 308, the Commissioner may generate or obtain an operational certificate. In operation 309, the Commissioner and the Commissionee may transmit and / or receive configuration information including the operational certificate. In operation 310, the Commissioner and the Commissionee may transmit and / or receive configuration information including an access control list. In operation 311, the Commissioner and the Commissionee may transmit and / or receive configuration information including information about an operational network. In action 312, the Commissioner and / or the Commissionee may trigger the Commissionee to join the operating network.

[0054] Referring to Figure 3b, an Administrator can act as a Commissioner. All messages between the Administrator and the Commissionee can be exchanged via the operational network. In operation 313, the Administrator and the Commissionee can perform operational discovery via the operational network. In operation 314, the Administrator and the Commissionee can perform security setup using Certificate Authenticated Session Establishment (CASE). In one embodiment, all messages between the Administrator and the Commissionee can be encrypted using an encryption key derived using CASE.

[0055] In operation 315, the Administrator and Commissionee may exchange a commissioning completion message. Thereafter, the commissioning may be successfully completed. In one embodiment, the commissioning channel may be terminated, and implicit administrative privileges may be terminated.

[0056] FIG. 4 is a diagram for explaining a multi-admin registration process in a single AP configuration environment according to one embodiment of the present disclosure.

[0057] Referring to FIG. 4, a first administrator device (1st admin) (410) providing IoT services on a first platform can manage and / or control target IoT devices (A, B, C). A second administrator device (2nd admin) (420) providing IoT services on a second platform can manage and / or control target IoT devices (D, E).

[0058] The first administrator device (1st admin) (410) and the second administrator device (2nd admin) (420) can be connected to a Wi-Fi AP (430) and communicate via the same Wi-Fi network. For example, the SSID (Service Set Identifier) ​​for Wi-Fi communication provided by the Wi-Fi AP (430) can be set to AP1, and the password (PW) can be set to Credential 1.

[0059] In the multi-admin process, when the second administrator device (2nd admin) (420) performs device registration for a target IoT device (e.g., IoT device (C)), the second administrator device (2nd admin) (420) can perform network provisioning for the target IoT device (e.g., IoT device (C)) based on information about the operational network to which it is currently connected.

[0060] For a target IoT device (e.g., IoT device (C)) pre-connected by a first administrator device (1st admin) (410), a second administrator device (2nd admin) (420) can transmit and / or set the operating network information (e.g., SSID: AP 1, PW: Credential 1) to which it is currently connected to the target IoT device (e.g., IoT device (C)). Thereafter, the target IoT device (e.g., IoT device (C)) can additionally attempt to connect to the provided network and perform the connection.

[0061] In a single AP configuration environment in a home (i.e., when the first administrator device (1st admin) (410), the target IoT device, and the second administrator device (2nd admin) (420) are connected to the same Wi-Fi network), network setting information updates may not occur.

[0062] FIG. 5 is a diagram for explaining a multi-admin registration process in a multiple AP configuration environment according to one embodiment of the present disclosure.

[0063] Referring to FIG. 5, a first administrator device (1st admin) (510) providing IoT services on a first platform can manage and / or control target IoT devices (A, B, C). A second administrator device (2nd admin) (520) providing IoT services on a second platform can manage and / or control target IoT devices (D, E).

[0064] The first administrator device (1st admin) (510) is connected to the first Wi-Fi AP (530), the second administrator device (2nd admin) (520) is connected to the second Wi-Fi AP (540), and the first administrator device (1st admin) (510) and the second administrator device (2nd admin) (520) can communicate through different Wi-Fi networks. For example, the SSID for Wi-Fi communication provided by the first Wi-Fi AP (530) may be set to AP1, and the password (PW) may be set to Credential 1. For example, the SSID for Wi-Fi communication provided by the second Wi-Fi AP (540) may be set to AP2, and the password (PW) may be set to Credential 2.

[0065] In a multi-admin process in a home multiple AP configuration environment (for example, when one Wi-Fi AP physical device supports 2.4 GHz / 5 GHz bands simultaneously), when the second administrator device (2nd admin) (420) performs device registration for a target IoT device (for example, IoT device (C)), the second administrator device (2nd admin) (520) can transmit and / or set information about the operational network to which it is currently connected to the target IoT device (for example, IoT device (C)).

[0066] A target IoT device (e.g., IoT device (C)) may disconnect from an existing Wi-Fi AP connection (e.g., connection to the first Wi-Fi AP (530)) and connect to a new Wi-Fi AP (e.g., second Wi-Fi AP (540)) to which a second administrator device (2nd admin) (420) is connected, which may result in disconnection or performance degradation of the existing network configured with the first administrator device (1st admin) (510).

[0067] That is, since an IoT device can only set one network information when registering a device, a target IoT device (e.g., IoT device (C)) may be connected to a second Wi-Fi AP (540), which may result in a weakened or disconnected connection that the user does not want.

[0068] Meanwhile, during the registration process of the target IoT device during multi-admin registration, the configuration information of the target IoT device may be changed by the second administrator device (2nd admin). For example, if the second administrator device (2nd admin) is a malicious device (for example, if it attempts to search for and connect to a device from next door), there is a serious security issue, but the security issue can be resolved through a security policy. For example, a user may intentionally change the configuration information (for example, installing a new AP or changing the location of the target IoT device). For example, if a user unintentionally changes the configuration information (for example, the second administrator device (2nd admin) performs additional admin registration without knowing that the target IoT device is connected to a different Wi-Fi AP than itself), a measure may be needed to prevent a deterioration of the user UX.

[0069] This disclosure proposes a method for a second administrator device (2nd admin) to determine whether a change in the settings of a target IoT device is intentional or not. Furthermore, this disclosure proposes a method for preventing changes in the settings of a target IoT device that are not intentional.

[0070] This disclosure proposes a network security enhancement protocol that takes multi-administration into account. Specifically, this disclosure proposes a protocol that prevents network configuration information from being set differently for a target IoT device without user consent when setting up multi-admin (i.e., when a target IoT device is registered for the first time or more).

[0071] According to one embodiment, when a second administrator device (2nd admin) performs additional device registration for a target IoT device for multi-admin registration, if the setting information (e.g., Wi-Fi SSID and / or PW) received by the target IoT device from the second administrator device (2nd admin) is different from the existing network configuration information, at least one of the following processes 1) to 4) may be performed.

[0072] 1) A process for directly verifying whether the setting information received by the target IoT device from the second administrator device (2nd admin) is identical to the target IoT device's existing network settings;

[0073] 2) The process in which the target IoT device requests the user to allow changes to the network settings information;

[0074] 3) The process by which the target IoT device directly verifies whether the user is aware of the second administrator device (2nd admin);

[0075] 4) A process in which the target IoT device directly sets network setting information based on a response from the user regarding whether to allow changes to network setting information;

[0076] In one embodiment, the first administrator device (1st admin) and / or the second administrator device (2nd admin) may determine whether to allow changes to the configuration information of the target IoT device.

[0077] FIG. 6A and FIG. 6B are diagrams illustrating an example of a case where a setting change notification is sent to a new admin when registering a multi-admin according to one embodiment of the present disclosure.

[0078] In FIGS. 6A and 6B , a target IoT device (e.g., a security camera) and a first administrator device (1st admin) may be connected to a first Wi-Fi AP, and a second administrator device (2nd admin) may be connected to a second Wi-Fi AP. For example, the SSID for the first Wi-Fi AP may be set to AP1, and the password may be set to Credential1. For example, the SSID for the second Wi-Fi AP may be set to AP2, and the password may be set to Credential2.

[0079] Commissionable mode is activated for the target IoT device, and a second administrator device (2nd admin) can initiate additional commissioning for the target IoT device. In one embodiment, the target IoT device can receive a command to activate commissionable mode from the first administrator device (1st admin).

[0080] In operation 601, the second administrator device (2nd admin) can transmit configuration information including at least one of an operational certificate, an access control list (ACL), and an operational network to the target IoT device.

[0081] In operation 601-1, the second administrator device (2nd admin) may transmit a network configuration request to the target IoT device. In one embodiment, the network configuration request may include information about the Wi-Fi AP to which the second administrator device (2nd admin) is connected (e.g., SSID: AP 2 SSID, Password: Credential 2).

[0082] In operation 602, the target IoT device can check whether the network configuration information has changed.

[0083] If a credential update is requested in FIG. 6b, in operation 603, the target IoT device may transmit a confirmation request to the second administrator device (2nd admin) regarding whether to allow changes to the configuration information. In one embodiment, the confirmation request may include information about the Wi-Fi AP to which the target IoT device is connected (e.g., SSID: AP 1 SSID, Password: Credential 1).

[0084] In operation 604, the second administrator device (2nd admin) can check the Wi-Fi AP information (e.g., SSID: AP 1 SSID, Password: Credential 1) in response to user input.

[0085] In operation 605, the second administrator device (2nd admin) can transmit a verification response message to the target IoT device that includes Wi-Fi AP information based on user input (e.g., SSID: AP 1 SSID, Password: Credential 1) and information indicating that a network change is permitted (e.g., Change action: Allow).

[0086] In operation 606, the target IoT device can verify information indicating that it allows a password and network change for the Wi-Fi AP (e.g., Change action: Allow). In operation 607, the target IoT device can update the network with the Wi-Fi credentials of the second administrator device (2nd admin). In operation 608, the target IoT device can transmit the result of the change in network configuration information (e.g., Success or Fail) to the second administrator device (2nd admin). At this time, the target IoT device can connect to Wi-Fi AP 2, and the connection with the existing Wi-Fi AP 1 can be released.

[0087] In operation 609, the target IoT device and the second administrator device (2nd admin) can resume the commissioning process. The target IoT device and the second administrator device (2nd admin) can complete the registration of an additional 2nd admin for the target IoT device.

[0088] Meanwhile, if a credential update is not requested in FIG. 6b, the target IoT device can maintain its connection to Wi-Fi AP 1. Following operation 602, in operation 603-1, the target IoT device and the second administrator device (2nd admin) can proceed with the commissioning process without changing network configuration information. Thereafter, the target IoT device and the second administrator device (2nd admin) can complete the registration of an additional 2nd admin for the target IoT device.

[0089] FIG. 7A and FIG. 7B are diagrams illustrating another example of a case where a setting change notification is sent to a new admin when registering a multi-admin according to one embodiment of the present disclosure.

[0090] In FIGS. 7A and 7B , a target IoT device (e.g., a security camera) and a first administrator device (1st admin) may be connected to a first Wi-Fi AP, and a second administrator device (2nd admin) may be connected to a second Wi-Fi AP. For example, the SSID for the first Wi-Fi AP may be set to AP1, and the password may be set to Credential1. For example, the SSID for the second Wi-Fi AP may be set to AP2, and the password may be set to Credential2.

[0091] Commissionable mode is activated for the target IoT device, and a second administrator device (2nd admin) can initiate additional commissioning for the target IoT device. In one embodiment, the target IoT device can receive a command to activate commissionable mode from the first administrator device (1st admin).

[0092] In operation 701, the second administrator device (2nd admin) can transmit configuration information including at least one of an operational certificate, an access control list (ACL), and an operational network to the target IoT device.

[0093] In operation 701-1, the second administrator device (2nd admin) may transmit a network configuration request to the target IoT device. In one embodiment, the network configuration request may include information about the Wi-Fi AP to which the second administrator device (2nd admin) is connected (e.g., SSID: AP 2 SSID, Password: Credential 2).

[0094] In operation 702, the target IoT device can check whether the network configuration information has changed.

[0095] If a credential update is requested, in step 703, the target IoT device may transmit a confirmation request to the second administrator device (2nd admin) regarding whether to allow changes to the configuration information. In one embodiment, the confirmation request may include information about the Wi-Fi AP to which the target IoT device is connected (e.g., SSID: AP 1 SSID, Password: Credential 1).

[0096] FIG. 7a illustrates a case where the first admin device (1st admin) does not allow multi-admin process by the second admin device (2nd admin) and a case where the second admin device (2nd admin) decides to update network credentials (If 2nd admin decides to update Network Credentials).

[0097] In operation 704, the second administrator device (2nd admin) can check Wi-Fi AP information (e.g., SSID: AP 1 SSID, Password: Credential 1) in response to user input.

[0098] In operation 705, the second administrator device (2nd admin) may transmit a verification response message to the target IoT device, which includes Wi-Fi AP information based on user input (e.g., SSID: AP 1 SSID, Password: Credential 1) and information indicating that network changes are not allowed (e.g., Change action: Deny). In one embodiment, the second administrator device (2nd admin) may reject changes to network configuration information, but may respond by entering a correct Password value if administrator registration for the second administrator device (2nd admin) is desired.

[0099] In action 706, the target IoT device can verify the password for the Wi-Fi AP and information indicating that network changes are not allowed (e.g., Change action: Deny).

[0100] In operation 707, the target IoT device may transmit the result of the change in network configuration information (e.g., Success or Fail) and the AP SSID information to which the target IoT device is connected to the second administrator device (2nd admin). At this time, the target IoT device may request that the second administrator device (2nd admin) connect to the same network as the target IoT device in order to resume administrator registration for the second administrator device (2nd admin) even though the change in network configuration information failed.

[0101] Referring to FIG. 7B, in operation 708, the second administrator device (2nd admin) can perform a connection to the first Wi-Fi AP based on the AP SSID information to which the target IoT device is connected. In operation 709, the second administrator device (2nd admin) and the target IoT device can resume the commissioning process without changing the network configuration information. The second administrator device (2nd admin) and the target IoT device can complete the registration of the second administrator device (2nd admin) as an additional administrator for the target IoT device.

[0102] In one embodiment, instead of step 705 after step 704, in step 705-1, the second administrator device (2nd admin) may transmit a verification response message including information indicating that the network change is not allowed (e.g., Change action: Deny) to the target IoT device. In one embodiment, if the second administrator device (2nd admin) rejects the change in network configuration information and also gives up administrator registration for the second administrator device (2nd admin), the second administrator device (2nd admin) may respond without entering a PW value.

[0103] In action 706-1, the target IoT device can verify information indicating that it does not allow network changes (e.g., Change action: Deny).

[0104] In operation 707-1, the target IoT device may transmit the result of the network configuration information change (e.g., Success or Fail) to the second administrator device (2nd admin). In operation 708-1, the target IoT device and / or the second administrator device (2nd admin) may forcibly terminate the additional commissioning process. At this time, the target IoT device may maintain the connection with Wi-Fi AP 1.

[0105] In one embodiment, after step 703, in step 704-1, the target IoT device and the second administrator device (2nd admin) may perform the existing commissioning process. Thereafter, additional administrator registration of the second administrator device (2nd admin) for the target IoT device may be completed.

[0106] FIG. 8A and FIG. 8B are diagrams illustrating an example of a case where a setting change notification is sent to the current admin when registering a multi-admin according to one embodiment of the present disclosure.

[0107] In FIGS. 8A and 8B , a target IoT device (e.g., a security camera) and a first administrator device (1st admin) may be connected to a first Wi-Fi AP, and a second administrator device (2nd admin) may be connected to a second Wi-Fi AP. For example, the SSID for the first Wi-Fi AP may be set to AP1, and the password may be set to Credential1. For example, the SSID for the second Wi-Fi AP may be set to AP2, and the password may be set to Credential2.

[0108] Commissionable mode is activated for the target IoT device, and a second administrator device (2nd admin) can initiate additional commissioning for the target IoT device. In one embodiment, the target IoT device can receive a command to activate commissionable mode from the first administrator device (1st admin).

[0109] In operation 801, the second administrator device (2nd admin) can transmit configuration information including at least one of an operational certificate, an access control list (ACL), and an operational network to the target IoT device.

[0110] In operation 801-1, the second administrator device (2nd admin) may transmit a network configuration request to the target IoT device. In one embodiment, the network configuration request may include information about the Wi-Fi AP to which the second administrator device (2nd admin) is connected (e.g., SSID: AP 2 SSID, Password: Credential 2).

[0111] In operation 802, the target IoT device can check whether the network configuration information has changed.

[0112] If a credential update is requested in FIG. 8b, in operation 803, the target IoT device may transmit a confirmation request to the first administrator device (1st admin) regarding whether to allow changes to configuration information. In one embodiment, the confirmation request may include information about the Wi-Fi AP to which the second administrator device (2nd admin) is connected (e.g., SSID: AP 2 SSID).

[0113] In operation 804, the first administrator device (1st admin) can check the Wi-Fi AP information (e.g., SSID: AP 2 SSID, Password: Credential 2) to which the second administrator device (2nd admin) is connected in response to user input.

[0114] In operation 805, the first administrator device (1st admin) can transmit a verification response message to the target IoT device, which includes Wi-Fi AP information based on user input (e.g., SSID: AP 2 SSID, Password: Credential 2) and information indicating that a network change is permitted (e.g., Change action: Allow).

[0115] In operation 806, the target IoT device can verify the information indicating that the password and network change for the Wi-Fi AP are permitted (e.g., Change action: Allow). In operation 807, the target IoT device can update the network with the Wi-Fi credentials of the second administrator device (2nd admin). In operation 808, the target IoT device can transmit the result of the change in network configuration information (e.g., Success or Fail) to the first administrator device (1st admin). At this time, the target IoT device can connect to Wi-Fi AP 2, and the connection with the existing Wi-Fi AP 1 can be released.

[0116] In operation 809, the target IoT device and the second administrator device (2nd admin) can resume the commissioning process. The target IoT device and the second administrator device (2nd admin) can complete the registration of an additional 2nd admin for the target IoT device.

[0117] Meanwhile, if a credential update is not requested in FIG. 8b, the target IoT device can maintain its connection to Wi-Fi AP 1. Following operation 802, in operation 803-1, the target IoT device and the second administrator device (2nd admin) can proceed with the commissioning process without changing network configuration information. Thereafter, the target IoT device and the second administrator device (2nd admin) can complete the registration of an additional 2nd admin for the target IoT device.

[0118] FIG. 9A and FIG. 9B are diagrams illustrating another example of a case where a setting change notification is sent to the current admin when registering a multi-admin according to one embodiment of the present disclosure.

[0119] In FIG. 9A and FIG. 9B, a target IoT device (e.g., a security camera) and a first administrator device (1st admin) may be connected to a first Wi-Fi AP, and a second administrator device (2nd admin) may be connected to a second Wi-Fi AP. For example, the SSID for the first Wi-Fi AP may be set to AP1, and the password may be set to Credential1. For example, the SSID for the second Wi-Fi AP may be set to AP2, and the password may be set to Credential2.

[0120] Commissionable mode is activated for the target IoT device, and a second administrator device (2nd admin) can initiate additional commissioning for the target IoT device. In one embodiment, the target IoT device can receive a command to activate commissionable mode from the first administrator device (1st admin).

[0121] In operation 901, the second administrator device (2nd admin) can transmit configuration information including at least one of an operational certificate, an access control list (ACL), and an operational network to the target IoT device.

[0122] In operation 901-1, the second administrator device (2nd admin) may transmit a network configuration request to the target IoT device. In one embodiment, the network configuration request may include information about the Wi-Fi AP to which the second administrator device (2nd admin) is connected (e.g., SSID: AP 2 SSID, Password: Credential 2).

[0123] In operation 902, the target IoT device can check whether the network configuration information has changed.

[0124] If a credential update is requested, in step 903, the target IoT device may transmit a confirmation request to the first administrator device (1st admin) regarding whether to allow changes to the configuration information. In one embodiment, the confirmation request may include information about the Wi-Fi AP to which the second administrator device (2nd admin) is connected (e.g., SSID: AP 2 SSID).

[0125] Figure 9a illustrates a case where the first administrator device (1st admin) allows multi-admin process by the second administrator device (2nd admin).

[0126] In operation 904, the first administrator device (1st admin) can check the Wi-Fi AP information (e.g., SSID: AP 2 SSID, Password: Credential 2) to which the second administrator device (2nd admin) is connected in response to user input.

[0127] In operation 905, the first administrator device (1st admin) may transmit a verification response message to the target IoT device, which includes Wi-Fi AP information based on user input (e.g., SSID: AP 2 SSID, Password: Credential 2) and information indicating that network changes are not allowed (e.g., Change action: Deny). In one embodiment, the first administrator device (1st admin) may reject changes to network configuration information, but may respond by entering a correct Password value to register the administrator for the second administrator device (2nd admin), if desired.

[0128] In action 906, the target IoT device can verify the password for the Wi-Fi AP and information indicating that network changes are not allowed (e.g., Change action: Deny).

[0129] In operation 907, the target IoT device can transmit the result of changing the network configuration information (e.g., Success or Fail) and the AP SSID information to which the target IoT device is connected to the first administrator device (1st admin). In operation 908, the first administrator device (1st admin) can transmit the AP SSID information to which the target IoT device is connected to the second administrator device (2nd admin). At this time, the target IoT device can request that the second administrator device (2nd admin) connect to the same network as the target IoT device in order to resume administrator registration for the second administrator device (2nd admin) even though the network configuration information change failed.

[0130] Referring to FIG. 9b, in operation 909, the second administrator device (2nd admin) can perform a connection to the first Wi-Fi AP based on the AP SSID information to which the target IoT device is connected. Once the second administrator device (2nd admin) connects to the first Wi-Fi AP, the commissioning process can be resumed without a separate network provisioning process. The second administrator device (2nd admin) and the target IoT device can complete the registration of the second administrator device (2nd admin) as an additional administrator for the target IoT device.

[0131] FIG. 9B illustrates a case where the first administrator device (1st admin) does not allow a multi-admin process by the second administrator device (2nd admin). In one embodiment, instead of operation 905 after operation 904, in operation 905-1, the first administrator device (1st admin) may transmit a verification response message including information indicating that a network change is not allowed (e.g., Change action: Deny) to the target IoT device. In one embodiment, if the first administrator device (1st admin) rejects a change in network configuration information and at the same time gives up administrator registration for the second administrator device (2nd admin), the first administrator device (1st admin) may respond without entering a PW value.

[0132] In action 906-1, the target IoT device can verify information indicating that it does not allow network changes (e.g., Change action: Deny).

[0133] In operation 807-1, the target IoT device may transmit the result of the network configuration information change (e.g., Success or Fail) to the first administrator device (1st admin). In operation 908-1, the target IoT device and / or the second administrator device (2nd admin) may forcibly terminate the additional commissioning process. At this time, the target IoT device may maintain the connection with Wi-Fi AP 1.

[0134] In one embodiment, after operation 903, in operation 904-1, the target IoT device and the second administrator device (2nd admin) may perform the existing commissioning process. Thereafter, additional administrator registration of the second administrator device (2nd admin) for the target IoT device may be completed.

[0135] FIG. 10 is a diagram illustrating an example of a case in which connection information is transmitted in advance before starting to register an additional device according to one embodiment of the present disclosure.

[0136] In FIGS. 10A and 10B , a target IoT device (e.g., a security camera) and a first administrator device (1st admin) may be connected to a first Wi-Fi AP, and a second administrator device (2nd admin) may be connected to a second Wi-Fi AP. For example, the SSID for the first Wi-Fi AP may be set to AP1, and the password may be set to Credential1. For example, the SSID for the second Wi-Fi AP may be set to AP2, and the password may be set to Credential2.

[0137] In operation 1001, the second administrator device (2nd admin) may transmit an additional administrator registration request for the second administrator device (2nd admin) to the first administrator device (1st admin). In operation 1002, the first administrator device (1st admin) may obtain user consent for the additional administrator registration request based on user input.

[0138] In operation 1003, the first administrator device (1st admin) can transmit a command (OpenCommissionningWindow) to the target IoT device to activate the Commissioning mode. In operation 1004, the target IoT device can activate the Commissionable mode. In operation 1005, the first administrator device (1st admin) can transmit the result information (e.g., Pass or Fail) on whether the device is allowed to be commissioned to the second administrator device (2nd admin) and the Wi-Fi AP 1 SSID to the second administrator device (2nd admin).

[0139] If the 2nd admin decides to remain the existing associated Wi-Fi AP of the Target IoT device, the 2nd admin can perform a connection to Wi-Fi AP 1 in operation 1006. Thereafter, the 2nd admin can be connected to Wi-Fi AP 1.

[0140] In operation 1007, the second administrator device (2nd admin) and the target IoT device can perform a commissioning process on the same network. At this time, additional administrator registration of the second administrator device (2nd admin) for the target IoT device can be completed.

[0141] In one embodiment, instead of step 1006 after step 1005, in step 1006-1, the second administrator device (2nd admin) and the target IoT device may perform a commissioning process on different networks. Thereafter, the target IoT device may connect to Wi-Fi AP 2 (disconnecting from the existing Wi-Fi AP 1). Additional administrator registration of the second administrator device (2nd admin) for the target IoT device may be completed.

[0142] FIG. 11 is a drawing for explaining the configuration of a first electronic device according to one embodiment of the present disclosure.

[0143] The first electronic device of FIG. 11 may be one of the target IoT devices, electronic devices, IoT devices, and commissioning devices described in the embodiments of FIGS. 1 to 10 described above. The first electronic device of FIG. 11 may include a processor (1101), a transceiver (1103), and a memory (1105). The processor (1101), the transceiver (1103), and the memory (1105) of the first electronic device may operate according to the methods described in the embodiments of FIGS. 1 to 10. However, the components of the first electronic device are not limited to the examples described above. For example, the first electronic device may include more or fewer components than the components described above. In addition, the processor (1101), the transceiver (1103), and the memory (1105) may be implemented in the form of a single chip.

[0144] The transceiver (1103) is a general term for the receiver of the first electronic device and the transmitter of the device, and can transmit and receive signals with the counterpart device. At this time, the transmitted and received signals may include at least one of control information and data. In addition, the transceiver (1103) may receive a signal, output it to the processor (1101), and transmit the signal output from the processor (1101). In addition, the transceiver (1103) of FIG. 11 may include a transmitter capable of transmitting a signal according to at least one of the communication methods exemplified in the embodiments of FIGS. 1 to 10 or a known proximity communication method, and a receiver capable of receiving the signal. In addition, the transceiver (1103) may receive a signal, output it to the processor (1101), and transmit the signal output from the processor (1101) to the counterpart device via a network. The memory (1105) may store programs and data necessary for the operation of the device according to at least one of the embodiments of FIGS. 1 to 10. Additionally, the memory (1105) can store control information or data included in a signal acquired from the device. The memory (1105) can be configured as a storage medium or a combination of storage media, such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD.

[0145] Additionally, the processor (1101) may control a series of processes so that the device can operate according to at least one of the embodiments of FIGS. 1 to 10. The processor (1101) may include at least one processor.

[0146] FIG. 12 is a drawing for explaining the configuration of a second electronic device according to one embodiment of the present disclosure.

[0147] The second electronic device of FIG. 12 is the administrator device, the first administrator device (1st admin), and the second administrator device (2nd admin) described in the embodiments of FIGS. 1 to 10 described above. admin), and may be one commissioner. The first electronic device of FIG. 12 may include a processor (1201), a transceiver (1203), and a memory (1205). The processor (1201), the transceiver (1203), and the memory (1205) of the first electronic device may operate according to the method described in the embodiments of FIGS. 1 to 10. However, the components of the first electronic device are not limited to the examples described above. For example, the first electronic device may include more or fewer components than the components described above. In addition, the processor (1201), the transceiver (1203), and the memory (1205) may be implemented in the form of a single chip.

[0148] The transceiver (1203) is a general term for the receiver of the first electronic device and the transmitter of the device, and can transmit and receive signals with the counterpart device. At this time, the transmitted and received signals may include at least one of control information and data. In addition, the transceiver (1203) may receive a signal, output it to the processor (1201), and transmit the signal output from the processor (1201). In addition, the transceiver (1203) of FIG. 12 may include a transmitter capable of transmitting a signal according to at least one of the communication methods exemplified in the embodiments of FIGS. 1 to 10 or a known proximity communication method, and a receiver capable of receiving the signal. In addition, the transceiver (1203) may receive a signal, output it to the processor (1201), and transmit the signal output from the processor (1201) to the counterpart device via a network. The memory (1205) may store programs and data necessary for the operation of the device according to at least one of the embodiments of FIGS. 1 to 10. Additionally, the memory (1205) can store control information or data included in a signal acquired from the device. The memory (1205) can be configured as a storage medium or a combination of storage media, such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD.

[0149] Additionally, the processor (1201) may control a series of processes so that the device can operate according to at least one of the embodiments of FIGS. 1 to 10. The processor (1201) may include at least one processor.

[0150] The methods according to the embodiments described in the claims or specification of the present disclosure may be implemented in the form of hardware, software, or a combination of hardware and software. If implemented in software, a computer-readable storage medium storing one or more programs (software modules) may be provided. The one or more programs stored in the computer-readable storage medium are configured for execution by one or more processors within an electronic device. The one or more programs include instructions that cause the electronic device to execute the methods according to the embodiments described in the claims or specification of the present disclosure.

[0151] These programs (software modules, software) may be stored in random access memory, non-volatile memory including flash memory, read only memory (ROM), electrically erasable programmable read only memory (EEPROM), magnetic disc storage devices, compact disc-ROMs (CD-ROMs), digital versatile discs (DVDs) or other forms of optical storage devices, magnetic cassettes, or may be stored in memories formed by a combination of some or all of these. In addition, each configuration memory may include multiple copies. The above program may be stored on an attachable storage device that is accessible via a communication network such as the Internet, an intranet, a local area network (LAN), a wide area network (WAN), a storage area network (SAN), or a combination thereof. This storage device may be connected to a device performing an embodiment of the present disclosure via an external port. Additionally, a separate storage device on the communication network may be connected to a device performing an embodiment of the present disclosure.

[0152] In the specific embodiments of the present disclosure described above, components included in the disclosure are expressed in the singular or plural form, depending on the specific embodiment presented. However, the singular or plural expressions are selected to suit the presented situation for convenience of explanation, and the present disclosure is not limited to singular or plural components. Components expressed in the plural form may be composed of singular elements, or components expressed in the singular form may be composed of plural elements.

[0153] While the detailed description of this disclosure has described specific embodiments, it should be understood that various modifications are possible without departing from the scope of this disclosure. Therefore, the scope of this disclosure should not be limited to the described embodiments, but should be defined not only by the scope of the claims described below, but also by equivalents thereof.

Claims

1. In a method of a first device in an IoT (Internet of Things) system supporting a multi-manager service, When registering an additional device (commissioning) by a second device, an operation of checking whether the first network information set in the first device is the same as the second network information set in the second device; If the first network information and the second network information are different from each other, an operation of transmitting a confirmation request for whether to allow a change in the network settings of the first device to the second device; An operation of receiving a response message from the second device, the response message including the first network information and an indicator indicating whether to allow a change in the network settings; and A method characterized by comprising an action of performing a registration process between the second device and the additional device based on the response message.

2. In the first paragraph, the first network information includes a first SSID (Service Set Identifier) ​​and a first password for the first Wi-Fi AP (access point), A method characterized in that the second network information includes a second SSID and a second password for a second Wi-Fi AP.

3. In paragraph 1, A method characterized in that it further includes an action of receiving a command from a third device to activate a commissionable mode of the first device for registering the additional device by the second device.

4. In paragraph 1, A method characterized in that the method further includes an operation of changing the network settings for the first device based on the second network information, and performing the additional device registration process with the second device using the changed network, when the above instruction indicates that the network settings are allowed to be changed.

5. In paragraph 1, A method characterized in that the method further includes an action of performing a registration process for the second device and the additional device based on the first network information set in the first device, if the above instruction indicates that the network setting change is not allowed.

6. In a method of a second device in an IoT (Internet of Things) system supporting multi-manager services, An action to initiate an additional device commissioning process that enables the second device to manage the first device; If the first network information set in the first device and the second network information set in the second device are different from each other, an operation of receiving a confirmation request from the first device regarding whether to allow a change in the network settings of the first device; An operation of transmitting a response message to the first device, the response message including the first network information and an indicator indicating whether to allow a change in the network settings; and A method characterized by comprising an action of performing a registration process between the first device and the additional device based on the response message.

7. In the 6th paragraph, the first network information includes a first SSID (Service Set Identifier) ​​and a first password for the first Wi-Fi AP (access point), A method characterized in that the second network information includes a second SSID and a second password for a second Wi-Fi AP.

8. In paragraph 6, A method characterized in that when the above instruction indicates that the network setting change is permitted, the network setting for the first device is changed based on the second network information, and the first device and the second device perform the additional device registration process based on the changed network.

9. In paragraph 6, A method characterized in that, if the above instruction indicates that the network settings are not allowed to be changed, the first device uses the first network information and the second device uses the second network information, and the additional device registration process is performed.

10. In the first device of an IoT (Internet of Things) system that supports multi-manager services, Transmitter and receiver; and comprising a processor, said processor comprising: When registering an additional device (commissioning) by a second device, it is checked whether the first network information set in the first device is the same as the second network information set in the second device, If the first network information and the second network information are different from each other, control is provided to transmit a confirmation request for whether to allow a change in the network settings of the first device to the second device; Receive a response message from the second device that includes the first network information and an indicator indicating whether to allow a change in the network settings; A device characterized in that it performs a registration process of the second device and the additional device based on the response message.

11. In the 10th paragraph, the first network information includes a first SSID (Service Set Identifier) ​​and a first password for the first Wi-Fi AP (access point), A device characterized in that the second network information includes a second SSID and a second password for a second Wi-Fi AP.

12. In the 10th paragraph, the processor, A device characterized in that it receives a command from a third device to activate a commissionable mode of the first device for registering the additional device by the second device.

13. In the 10th paragraph, the processor, If the above instruction indicates that the network setting change is permitted, the network setting for the first device is changed based on the second network information, and the additional device registration process is performed with the second device using the changed network. A device characterized in that, if the above instruction indicates that the network settings are not allowed to be changed, the device performs a registration process with the second device based on the first network information set in the first device.

14. In a second device in an IoT (Internet of Things) system that supports multi-manager services, Transmitter and receiver; and comprising a processor, said processor comprising: Initiates an additional device commissioning process that enables the second device to manage the first device, If the first network information set in the first device and the second network information set in the second device are different from each other, a request for confirmation regarding whether to allow a change in the network settings of the first device is received from the first device, Control to transmit a response message including the first network information and an indicator indicating whether to allow a change in the network settings to the first device, A device characterized in that it performs a registration process between the first device and the additional device based on the response message.

15. In the 14th paragraph, the first network information includes a first SSID (Service Set Identifier) ​​and a first password for the first Wi-Fi AP (access point), A device characterized in that the second network information includes a second SSID and a second password for a second Wi-Fi AP.

Images