Method and apparatus for providing internet of things service in internet of things system supporting multi-manager service

Abstract

The present disclosure relates to a method and an apparatus for providing an Internet of Things (IoT) service in an IoT system supporting a multi-manager service. According to an embodiment of the present disclosure, a method performed by a first device in an IoT system supporting a multi-manager service comprises the steps of: receiving a first message, which includes first information on a target IoT device registered as a first manager, from a second device by the first device in relation to use of the target IoT device; in response to reception of the first message, transmitting a second message including second information on the first device to the second device; receiving, from the second device, a third message for requesting permission to use the target IoT device; and in response to reception of the third message, transmitting a fourth message including information indicating whether the use is permitted.

Description

Method and device for providing Internet of Things services in an Internet of Things system supporting multi-manager services

[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 device for providing an efficient IoT service for use / connection of IoT devices in an IoT system supporting a multi-administrator (multi-admin) function.

[0007] In addition, the present disclosure provides a method and apparatus for providing efficient IoT services through a device of a first manager operating as a home hub in an IoT system supporting multi-manager services.

[0008] In addition, the present disclosure provides a method and device for providing efficient IoT services in an IoT system supporting multi-manager services or through an access point (AP).

[0009] Additionally, the present disclosure provides a method and device for providing a stable IoT service in an IoT system supporting a multi-manager service.

[0010] According to an embodiment of the present disclosure, a method performed by a first device in an IoT (Internet of Things) system supporting a multi-manager service includes the steps of: receiving, from a second device, a first message including first information about a target IoT device registered as a first manager in relation to use of the target IoT device; transmitting, to the second device, a second message including second information about the first device in response to receiving the first message; receiving, from the second device, a third message requesting permission to use the target IoT device; and transmitting, in response to receiving the third message, a fourth message including information indicating whether or not the use is permitted.

[0011] In addition, according to an embodiment of the present disclosure, in an IoT system supporting a multi-manager service, a first device includes a transceiver and a processor configured to receive, from a second device, a first message including first information about a target IoT device in relation to use of the target IoT device for which the first device is registered as a first manager, through the transceiver, and transmit, in response to receiving the first message, a second message including second information about the first device to the second device, through the transceiver, and receive, from the second device, through the transceiver, a third message requesting permission to use the target IoT device, and transmit, in response to receiving the third message, through the transceiver, a fourth message including information indicating whether the use is permitted.

[0012] In addition, according to an embodiment of the present disclosure, a method performed by a second device in an IoT system supporting a multi-manager service includes the steps of: transmitting a first request message requesting at least one of first information on at least one first device, which is a first manager for at least one IoT device connectable in the IoT system, and second information on at least one IoT device connectable in the IoT system to an access point (AP) of the IoT system; receiving, in response to the first request message, a first response message including at least one of the first information and the second information from the AP; transmitting, through the AP, a second request message requesting permission to use a target IoT device selected from among the at least one connectable IoT device, to the first device, which is a first manager of the target IoT device; and receiving, in response to the transmission of the second request message, a second response message including information indicating whether or not the use is permitted from the first device through the AP.

[0013] In addition, according to an embodiment of the present disclosure, in an IoT system supporting a multi-manager service, a second device includes a transceiver, and a processor configured to transmit, through the transceiver, to an AP (access point) of the IoT system, a first request message requesting at least one of first information about at least one first device, which is a first manager for at least one IoT device connectable in the IoT system, and second information about at least one IoT device connectable, and to receive, through the transceiver, a first response message including at least one of the first information and the second information from the AP in response to the first request message, and to transmit, through the transceiver, a second request message requesting permission to use a target IoT device selected from among the at least one connectable IoT device, to the first device, which is a first manager of the target IoT device, via the AP, and to receive, through the transceiver, a second response message including information indicating whether or not the use is permitted, from the first device via the AP in response to transmission of the second request message.

[0014] Figure 1 is a diagram showing an example of an IoT system based on a cloud network.

[0015] Figure 2 is a diagram showing an example of a D2D-based IoT system.

[0016] Figure 3 is a drawing for explaining a multi-manager service in an IoT system.

[0017] FIG. 4 is a diagram illustrating an example of a method for providing a home hub-based IoT service in an IoT system supporting a multi-manager service according to an embodiment of the present disclosure;

[0018] FIG. 5 is a diagram showing an example of a method for providing an IoT service by using a first device, which is a first manager of IoT devices, as a home hub in an IoT system supporting a multi-manager service according to an embodiment of the present disclosure;

[0019] FIG. 6A and FIG. 6B are drawings showing an example of a method for providing an IoT service with an added authentication procedure by using a first device, which is a first manager of an IoT device, as a home hub in an IoT system supporting a multi-manager service according to an embodiment of the present disclosure.

[0020] FIG. 7 is a diagram illustrating an example of a method for providing an IoT service with an additional authentication procedure by using a first device, which is a first manager of IoT devices, as a home hub in an IoT system supporting a multi-manager service according to an embodiment of the present disclosure.

[0021] FIGS. 8A and 8B are diagrams showing an example of a method for providing IoT services using an encrypted on-boarding payload while using a first device, which is a first manager of IoT devices, as a home hub in an IoT system supporting a multi-manager service according to an embodiment of the present disclosure.

[0022] FIG. 9A and FIG. 9B are diagrams showing an example of a method for providing IoT services using an encrypted on-boarding payload while using a first device, which is a first manager of IoT devices, as a home hub in an IoT system supporting a multi-manager service according to an embodiment of the present disclosure.

[0023] FIG. 10 is a diagram illustrating an example of a method for providing an AP-based IoT service in an IoT system supporting a multi-manager service according to an embodiment of the present disclosure;

[0024] FIG. 11 is a diagram showing an example of a method for storing / registering mapping information between an IoT device and a first manager (device) in an AP in an IoT system supporting a multi-manager service according to an embodiment of the present disclosure;

[0025] FIG. 12a and FIG. 12b are diagrams showing an example of a method for providing an IoT service using an AP in an IoT system supporting a multi-manager service according to an embodiment of the present disclosure;

[0026] FIG. 13a and FIG. 13b are diagrams showing an example of a method for providing an IoT service using an AP in an IoT system supporting a multi-manager service according to an embodiment of the present disclosure.

[0027] FIG. 14a and FIG. 14b are diagrams showing an example of a method for providing an IoT service using an AP and an encrypted on-boarding payload in an IoT system supporting a multi-manager service according to an embodiment of the present disclosure;

[0028] FIG. 15a and FIG. 15b are diagrams illustrating an example of a method for providing an IoT service using an AP and an encrypted on-boarding payload in an IoT system supporting a multi-manager service according to an embodiment of the present disclosure;

[0029] FIG. 16a and FIG. 16b are diagrams showing an example of a method for providing an IoT service using an AP in an IoT system supporting a multi-manager service according to an embodiment of the present disclosure when a first device, which is a first manager, is not connected to the AP.

[0030] FIG. 17a and FIG. 17b are diagrams showing an example of a method for providing an IoT service by prioritizing a list of first devices that are first managers using an AP in an IoT system that supports a multi-manager service according to an embodiment of the present disclosure, and

[0031] FIG. 18 is a diagram showing an example configuration of a device in a wireless communication system according to an embodiment of the present disclosure.

[0032] 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.

[0033] 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.

[0034] 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.

[0035] 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).

[0036] 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.

[0037] 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.

[0038] 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).

[0039] Figure 1 is a diagram showing an example of an IoT system based on a cloud network.

[0040] Referring to FIG. 1, a first platform of Company A, which provides an IoT environment, and a second platform of Company B, which provides an IoT environment, may be connected via a cloud network. For example, it is assumed that a user has a first account (e.g., A@aaa.com) (110) for using IoT services on the first platform of Company A, to which at least one IoT device (130) is connected, and that the same or a different user has a second account (e.g., A@samsung.com) (120) for using IoT services on the second platform of Company B, to which at least one IoT device (140) is connected.

[0041] In the cloud-based IoT system of FIG. 1, the first account (A@aaa.com) (110) has registered ownership for use of an IoT device (130) on the first platform (i.e., registered as the first admin / device), and the second account (A@aaa.com) has registered ownership for use of an IoT device (140) on the second platform (i.e., registered as the first admin / device). In addition, in the cloud-based IoT system of FIG. 1, the first account (A@aaa.com) and the second account (A@aaa.com) (120) are linked through account linking (101), so that a user of the second account (120) can use the IoT device (130) whose ownership is registered to the first account (110) through the second device. At this time, the second device registered to the second account (120) can have the status of a second administrator who can use the IoT device (130) if the first administrator (admin) / device approves. In addition, sharing of the IoT device list for the IoT device (130) and the IoT device (140) can be performed between the first device registered to the first account (110) and the second device registered to the second account (120). In the example of Fig. 1, the second device having the status of a second administrator for the IoT device (130) can receive the IoT device list of the IoT device (130) from the first device through account connection (101) (102).

[0042] Assuming that the first platform and the second platform are constantly connected via a cloud network in the example of FIG. 1, the second device, which is the second manager of the IoT device (130), can control the operation of at least one IoT device belonging to the list of IoT devices (130) via the cloud network (103). However, a cloud-based IoT system such as the example of FIG. 1 has the burden of having to constantly operate a cloud network.

[0043] Figure 2 is a diagram showing an example of an IoT system based on D2D (device to device).

[0044] The example of FIG. 2 illustrates an example of a method in which a first device (210) of a first manager and a second device (220) of a second manager share IoT devices through D2D communication without using a cloud network as in the example of FIG. 1 for use / sharing IoT devices owned by other managers. The first device (210) and the second device (220) can use a known D2D communication method to search for IoT devices and control the operation of IoT devices for which ownership is registered. The first device (210) and the second device (220) can be various electronic devices such as a hub, a smart phone, a laptop, and a tablet that can control the operation of IoT devices. In FIG. 2, it is assumed that the first device (210) operates as a first manager for at least one IoT device (230), and the second device (220) operates as a first manager for at least one IoT device (240). In the present disclosure, when a device acts as a first administrator for a first IoT device, it means that the device has registered ownership for use of the first IoT device or has received approval for use of the first IoT device from another device that is registered as a first administrator for the first IoT device. Referring to FIG. 2, in step 201, the first device (210) can change the state of the IoT device (230) to a state in which ownership registration of the IoT device (230) is possible in the second device (220) so that the second device (220) can use the IoT device (230). In step 202, the IoT device (230) that has been changed to the registerable state can be discovered by the second device (220), and the state is changed to a state in which additional registration of the second device (220) as a first administrator is possible in addition to the first device (210).In step 203, the second device (220) can be added as the first manager of the IoT device (230) by discovering the IoT device (230) and performing ownership registration for use of the IoT device (230). However, the example of FIG. 2 requires that the first device (210) change the status of the IoT device (230) in advance so that the second device (220) can discover and register ownership of the IoT device (230).

[0045] For the purpose of defining terms used in the present disclosure, registering / connecting an IoT device to an IoT platform (which may be various platforms such as Samsung's SmartThings, for example) for the purpose of controlling / using the IoT device's operation will be referred to as commissioning, device onboarding, or pairing (hereinafter referred to as "commissioning"). In addition, a service that can register multiple devices as the first administrator for an IoT device will be referred to as a multi-admin service. As an optional example, an administrator who is granted the same usage rights as the first administrator for the IoT device may be referred to as a second administrator, distinguishing them from the first administrator who originally owns the IoT device. In the following embodiments of the present disclosure, for the sake of convenience of explanation, an administrator (device) who owns (has registered usage rights for) an IoT device will be referred to as the first administrator.

[0046] Figure 3 is a diagram for explaining a multi-manager service in an IoT system.

[0047] The example of FIG. 3 assumes a situation in which a first device (310) is registered and operates on a first platform (300-1) for IoT services, a second device (320) is registered and operates on a second platform (300-2) for IoT services, and the first device (310) is registered as a first manager for an IoT device (340). In the case where a multi-manager service is supported between the first platform (300-1) and the second platform (300-2), the first device (310) can set the operation mode of the IoT device (230) to a commissioning mode (i.e., registration mode) to enable registration of the IoT device (340) (i.e., additional registration of the first manager) on the second device (320) via an AP (access point) (330). And in FIG. 3, the first device (310), which is the first manager of the IoT device (340), can provide the second device (320) with an onboarding payload, which is information necessary to register the second device (320) as an additional first manager of the IoT device (340) in the registration mode. The onboarding payload can use information such as a QR (Quick Response) code, a PIN (Personal Information Number), etc. As in the example of FIG. 3, in an IoT system (eco system) where different platforms for IoT services coexist, a multi-manager service can improve user convenience of the IoT service.

[0048] To ensure efficient and stable use of the multi-manager service in an IoT system, a second device must be able to easily locate the first device, which is the primary manager for the IoT devices. Furthermore, the second device must be able to easily identify IoT devices available through the multi-manager service. Furthermore, a method is required to provide the onboarding payload to the second device, enabling secure use of the IoT devices through the multi-manager service.

[0049] To this end, the present disclosure proposes various embodiments in which a first device, which is a first manager of an IoT device, and a second device that wishes to use the IoT device can easily find the first device and the IoT device from the second device, and the second device can safely receive the on-boarding payload, without the aforementioned account connection between the first device and the second device.

[0050] The embodiments of the present disclosure to be described below will be explained by dividing them into embodiments in which a first device, which is a first manager of an IoT device, operates as a home hub in an IoT system (e.g., a smart home system), and a second device that wishes to use the IoT device receives permission to use the IoT device from the first device through a multi-manager service, and embodiments in which information about a target IoT device can be provided to the second device through an AP of the IoT system, and in which a second device that wishes to use the target IoT device in an IoT system that supports a multi-manager service receives permission to use the target IoT device from the first device through the AP.

[0051] FIG. 4 is a diagram illustrating an example of a method for providing a home hub-based IoT service in an IoT system supporting a multi-manager service according to an embodiment of the present disclosure.

[0052] The example of Fig. 4 illustrates a case where the first device, which is the first manager of the target IoT device, operates as a home hub in the IoT system. In the example of Fig. 4, the first device (410) and the target IoT device (430) are registered or subscribed to a network service (400) that provides, for example, a platform-based IoT service, and the second device (420) can use the target IoT device (430) through a multi-manager service.

[0053] Referring to FIG. 4, in step 401, the second device (420) can obtain information about the target IoT device (430) (hereinafter, IoT device information) using, for example, a method known in the Matter standard or a QR code attached to the target IoT device (430). The IoT device information may include an IoT device ID (identifier), descriptor information of the IoT device, etc. In step 402, the second device (420) can broadcast a first message on the network to find the first device (410), which is the first manager of the target IoT device (430) that the second device (420) wants to use, using, for example, BLE (Bluetooth Low Energy), which is a low-power Bluetooth communication method, Wi-Fi Aware USD (Unsynchronized Service Discovery), DNS-SD (Domain Name System Service Discovery), which is a communication method for service discovery based on DNS (Domain Name System), a Wi-Fi probing message, etc. The first message may include an IoT device ID.

[0054] In step 403, the first device (410) that received the first message can transmit a second message to the second device (420) in response to the first message. The second message can include the ID of the first device (410), administrator descriptor information, etc. Here, the ID of the first device (410) corresponds to the first administrator ID. In the embodiments of the present disclosure below, the ID of the first device that operates as the first administrator can be understood as the first administrator ID.

[0055] In step 404, the second device (420) that received the second message can transmit a third message to the first device (420) for a connection request to the target IoT device (430). The third message can include, for example, at least one of the ID of the target IoT device (430), the ID of the first device (410), the ID of the second device (420), and descriptor information.

[0056] In step 405, the first device (410) that receives the third message outputs an alarm message (e.g., text, sound, video message, etc.) to the user of the first device (410) informing that there is a connection request for the target IoT device (430) from the second device (420), and in response to the output, obtains an consent / rejection input from the user of the first device (410).

[0057] Although not illustrated as an optional embodiment, the first device (410) may transmit a fourth message to the second device (420) indicating consent / rejection of a connection request to the IoT device (430) in response to the third message. Although not illustrated as an optional embodiment, if the first device (410) consents to the connection request, the first device (410) may provide an onboarding payload, which is information necessary for the second device (420) to be registered as an additional first manager of the target IoT device (430) in commissioning mode (i.e., registration mode), in response to the third message.

[0058] In step 405, if the first device (410) obtains the user's consent input, in step 406, the first device (410) may set / change the operation mode of the target IoT device (430) to the registration mode so that the second device (420) can register the target IoT device (430) (additional registration by the first administrator). Thereafter, in step 407, the second device (420) may perform registration (commissioning) on ​​the target IoT device (430) whose status has been changed to the registration mode, thereby additionally registering the target IoT device (430) as the first administrator. In the present disclosure, the registration may include searching (discovering) and / or connecting to the target IoT device (430) by the second device (420). In an optional embodiment, the on-boarding payload may be used when additionally registering as the first administrator.

[0059] FIG. 5 is a diagram illustrating an example of a method for providing an IoT service by using a first device, which is a first manager of IoT devices, as a home hub in an IoT system supporting a multi-manager service according to an embodiment of the present disclosure.

[0060] In the example of FIG. 5, the IoT system illustrates an IoT service environment including a target IoT device (51), a second device (52) that wishes to use the target IoT device (51) through a multi-manager service, a plurality of first devices (53-1, 53-2) that have registered ownership of the target IoT device (51) (i.e., are registered as first managers), and a device (54) that is a first manager of another IoT device (not shown) that does not have ownership of the target IoT device (51) (i.e., is not a first manager). In the example of FIG. 5, the target IoT device (51) and the second device (52) are each illustrated as one device for convenience of explanation, but a plurality of target IoT devices and a plurality of second devices may exist. In addition, there may be one or more first devices registered as first managers for the target IoT device (51).

[0061] Referring to FIG. 5, in step 501, the second device (52) searches for a connectable target IoT device (51). At this time, the second device (52) may search for a connectable target IoT device (51) using a QR code physically attached to the target IoT device (51) or through an IP (internet protocol) network, for example, DNS-SD. At this time, the second device (52) may obtain information about the target IoT device (51). The information about the target IoT device (51) may include, for example, an ID of the target IoT device (51), descriptor information, etc.

[0062] In step 502, the second device (52) that finds the target IoT device (51) to be used can broadcast a first message including the ID of the target IoT device (51) on the network to find the first device that is the first manager of the target IoT device (51). A plurality of first devices (53-1, 53-2) and a device (54) that is the first manager of other IoT devices can receive the first message. As an optional embodiment, the first message can further include descriptor information of the target IoT device (51). The descriptor information can be, for example, information indicating the smart light when the target IoT device (51) is a smart light. As an optional embodiment, it may also be possible to transmit the first message in a group cast or unicast manner.

[0063] In steps 503 and 504, a plurality of first devices (53-1, 53-2) that have received a first message including the ID of the target IoT device (51) can each transmit a second message including its own device ID (or administrator ID) to the second device (52) in response. At this time, a device (54) that is not the first administrator of the target IoT device (51) does not transmit the second message to the second device (52). As an optional example, the second message may further include administrator descriptor information of the first device (53-1, 53-2). The administrator descriptor information may be, for example, information indicating that the first device (53-1, 53-2) is the first administrator of the target IoT device (51). For example, if the first device is a smart speaker that operates as a hub in an IoT system and the pre-registered descriptor information of the first manager is "Joe's speaker," a description such as "Joe's speaker" can be provided as the manager descriptor information.

[0064] In step 505, the second device (52) that has received the second message from each of the plurality of first devices (53-1, 53-2) can select the first device (53-1 or 53-2) from among the plurality of first devices (53-1, 53-2) to request / apply for the multi-manager service. At this time, the selection can be performed through inputting consent from the user of the second device (52), etc. In the present embodiment, it is assumed that the first device (53-2) is selected as the target of the request / application for the multi-manager service. In step 506, the second device (52) can transmit a third message including at least one of the ID of the target IoT device (51), the ID of the selected target first device (53-2), and the ID of the corresponding second device (52) to the first device (53-2). The third message is a message requesting the first device (53-2) to allow the second device (52) as a multi-manager for the target IoT device (51). As an optional embodiment, the third message may further include at least one of the administrator descriptor information of the first device (53-2) and the descriptor information of the second device (52).

[0065] At step 507, the first device (53-2) that has received the third message for requesting permission for multiple administrators from the second device (52) can agree / reject allowing the second device (52) as a multiple administrator (i.e., the first administrator) for the target IoT device (51). At this time, the agreement / rejection can be performed through an agreement / rejection input by the user of the first device (53-2), etc. At step 508, the first device (53-2) that has confirmed the agreement input can set / change the operation mode of the target IoT device (51) to the aforementioned registration mode (commissioning mode) so that the second device (52) can commission the target IoT device (51) (i.e., additional registration of the first administrator).

[0066] Thereafter, in step 508, the first device (53-2) may transmit a fourth message to the second device (52) in response to the third message, which includes information indicating whether to allow the second device (52) as a multi-manager (first manager) for the target IoT device (51). Then, in step 510, the second device (52) that has received the fourth message checks whether to allow it, and if allowed, performs registration (commissioning) for the use of the target IoT device (51). The registration may include searching (discovering) and / or connecting to the target IoT device (51) from the second device (52).

[0067] FIG. 6A and FIG. 6B are diagrams illustrating an example of a method for providing an IoT service with an additional authentication procedure by using a first device, which is a first manager of IoT devices, as a home hub in an IoT system supporting a multi-manager service according to an embodiment of the present disclosure.

[0068] In the examples of FIGS. 6A and 6B, the IoT system illustrates an IoT service environment including a target IoT device (61), a second device (62) that wants to use the target IoT device (61) through a multi-manager service, a plurality of first devices (63-1, 63-2) that have registered ownership of the target IoT device (61) (i.e., registered as a first manager), and a device (64) that is a first manager of another IoT device (not shown) that does not have ownership of the target IoT device (61) (i.e., is not a first manager).

[0069] In the examples of FIGS. 6A and 6B, the target IoT device (61) and the second device (62) are each illustrated as one device for convenience of explanation, but there may be multiple target IoT devices and multiple second devices. In addition, there may be one or more first devices registered as the first manager for the target IoT device (61).

[0070] Referring to FIG. 6a, in steps 601a and 601b, a plurality of first devices (63-1, 63-2) registered as first administrators for the target IoT device (61) can each store part or all of the aforementioned on-boarding payload required in the multi-administrator service. The on-boarding payload is information required for a device other than the first administrator of the target IoT device (61) to be registered as an additional first administrator of the target IoT device (61) in a commissioning mode with the target IoT device (61), and can use information that can be used for registration / authentication, such as a Discriminator, Passcode, QR code, PIN, etc.

[0071] In step 602, the second device (62) searches for a connectable target IoT device (61). At this time, the second device (62) may search for a connectable target IoT device (61) using a QR code physically attached to the target IoT device (61) or through an IP network, for example, DNS-SD. At this time, the second device (62) may obtain information about the target IoT device (61). The information about the target IoT device (61) may include, for example, an ID of the target IoT device (61), descriptor information, etc. In addition, in step 602, the second device (62) may obtain part or all of the on-boarding payload for the target IoT device (61) through a discriminator, passcode, QR code, PIN, etc. of the target IoT device (61).

[0072] In step 603, the second device (62) that finds the target IoT device (61) to be used can broadcast a first message including the ID of the target IoT device (61) on the network to find the first device that is the first manager of the target IoT device (61). A plurality of first devices (63-1, 63-2) and a device (64) that is the first manager of other IoT devices can receive the first message. As an optional embodiment, the first message can further include descriptor information of the target IoT device (61). The descriptor information can be, for example, information indicating the smart light when the target IoT device (61) is a smart light. As an optional embodiment, it may also be possible to transmit the first message in a group cast or unicast manner.

[0073] In steps 604 and 605, a plurality of first devices (63-1, 63-2) that have received a first message including the ID of the target IoT device (61) can each transmit a second message including its own device ID (or administrator ID) to the second device (62) in response. At this time, a device (64) that is not the first administrator of the target IoT device (61) does not transmit the second message to the second device (62). As an optional embodiment, the second message may further include administrator descriptor information of the first device (63-1, 63-2). The administrator descriptor information may be, for example, information indicating that the first device (63-1, 63-2) is the first administrator of the target IoT device (61).

[0074] In step 606, the second device (62) that has received the second message from each of the plurality of first devices (63-1, 63-2) can select the first device (63-1 or 63-2) from among the plurality of first devices (63-1, 63-2) to request / apply for the multi-manager service. At this time, the selection can be performed through inputting consent from the user of the second device (62), etc. In the present embodiment, it is assumed that the first device (63-2) is selected as the target of the request / application for the multi-manager service. In step 607, the second device (62) can transmit a third message including at least one of the ID of the target IoT device (61), the ID of the selected first device (63-2), and the ID of the corresponding second device (62) to the first device (63-2). The third message is a message requesting the first device (63-2) to allow the second device (62) as a multi-manager for the target IoT device (61). As an optional embodiment, the third message may further include at least one of the administrator descriptor information of the first device (63-2) and the descriptor information of the second device (62).

[0075] In step 608, the first device (63-2) that received the third message for requesting permission for multiple administrators from the second device (62) can generate a nonce for authentication of the multiple administrator service and transmit it to the second device (62). The nonce refers to a random variable, a temporary value, etc. used in the authentication procedure. The procedure for performing authentication between the two devices using the nonce can use a known authentication technique. In step 609, the second device (62) that received the nonce can generate first authentication information necessary for registering as an additional first administrator of the target IoT device (61) using the nonce and part or all of the on-boarding payload acquired in step 602.

[0076] Referring to FIG. 6b, in step 610, the second device (62) transmits the first authentication information to the first device (63-2), and in step 611, the first device (63-2) generates second authentication information using part or all of the on-boarding payload acquired in step 601b and the nonce generated in step 608, and performs authentication information verification by comparing whether the received first authentication information and the generated second authentication information are identical. The first device (63-2) determines that the first authentication information and the second authentication information are verified if the comparison results show that the first authentication information and the second authentication information are identical.

[0077] In step 612, the first device (63-2) that received the third message for requesting permission for multiple administrators from the second device (62) can agree / reject allowing the second device (62) as a multiple administrator (i.e., the first administrator) for the target IoT device (61) based on the verification result in step 611. At this time, the agreement / rejection can be performed through an agreement / rejection input by the user of the first device (63-2), etc. In step 613, the first device (63-2) that confirmed the agreement input can set / change the operation mode of the target IoT device (61) to the aforementioned registration mode (commissioning mode) so that the registration of the target IoT device (61) (additional registration of the first administrator) is possible in the second device (62).

[0078] Thereafter, in step 614, the first device (63-2) may transmit a fourth message to the second device (62) in response to the third message, which includes information indicating whether to allow the second device (62) as a multi-manager (first manager) for the target IoT device (61). Then, in step 615, the second device (62) that has received the fourth message checks whether to allow it, and if allowed, performs registration (commissioning) for the use of the target IoT device (61). The registration may include searching (discovering) and / or connecting to the target IoT device (61) from the second device (62).

[0079] FIG. 7 is a diagram illustrating an example of a method for providing an IoT service using a first device, which is a first manager of IoT devices, as a home hub in an IoT system supporting a multi-manager service according to an embodiment of the present disclosure, but with an additional authentication procedure.

[0080] In the example of FIG. 7, the IoT system illustrates an IoT service environment including a target IoT device (71), a second device (72) that wants to use the target IoT device (71) through a multi-manager service, and a first device (73) that has registered ownership of the target IoT device (71) (i.e., registered as a first manager).

[0081] In the example of Fig. 7, the target IoT device (71), the second device (72), and the first device (73) are each illustrated as one device for convenience, but there may be multiple target IoT devices and multiple first and second devices. In addition, there may be one or more first devices registered as the first manager for the target IoT device (71).

[0082] Referring to FIG. 7, in steps 700a and 700b, it is assumed that the second device (72) and the first device (73) registered as the first manager for the target IoT device (71) have previously stored credentials for the authentication procedure required in the multi-manager service. The credentials may utilize, for example, certificates, shared secret information, etc.

[0083] In step 701, the second device (72) searches for a connectable target IoT device (71). At this time, the second device (72) can search for a connectable target IoT device (71) using a QR code physically attached to the target IoT device (71) or through an IP network, for example, DNS-SD. At this time, the second device (72) can obtain information about the target IoT device (71). The information about the target IoT device (71) can include, for example, an ID of the target IoT device (71), descriptor information, etc.

[0084] In step 702, the second device (72) that finds the target IoT device (71) to be used can broadcast a first message including the ID of the target IoT device (71) on the network to find the first device, which is the first manager of the target IoT device (71). The first message can be transmitted using, for example, BLE, a low-power Bluetooth communication method, USD, DNS-SD, a communication method for DNS-based service discovery, a Wi-Fi probing message, etc. As an optional embodiment, it may also be possible to transmit the first message in a group cast or unicast manner.

[0085] In step 703, the first device (73) that has received the first message including the ID of the target IoT device (71) can transmit a second message including its own device ID (or administrator ID) to the second device (72) in response. As an optional embodiment, the second message may further include administrator descriptor information of the first device (73). The administrator descriptor information may be, for example, information indicating that the first device (73) is the first administrator of the target IoT device (71). In step 704, the second device (72) that has received the second message from the first device (73) can select the first device (73) from which to request / apply for the multi-administrator service. At this time, the selection may be performed through inputting consent from the user of the second device (72), etc.

[0086] In step 705, the second device (72) can transmit a third message to the first device (73) that includes at least one of the ID of the target IoT device (71), the ID of the first device (73), and the ID of the second device (72). The third message is a message requesting the first device (73) to allow the second device (72) to be a multi-manager for the target IoT device (71). In an optional embodiment, the third message can further include at least one of the manager descriptor information of the first device (73) and the descriptor information of the second device (72).

[0087] The first device (73) that received the third message for a request for multi-administrator permission from the second device (72) in step 706 can perform an authentication procedure for the second device (72) based on the credentials previously stored in steps 700a and 700b for authentication of the multi-administrator service.

[0088] In step 706, based on the authentication result, in step 707, the first device (73) can consent / reject allowing the second device (72) to be a multi-administrator (i.e., the first administrator) for the target IoT device (71). At this time, consent / rejection can be performed through consent / rejection input by the user of the first device (73), etc. In step 708, the first device (73) that has confirmed the consent input can set / change the operation mode of the target IoT device (71) to the aforementioned registration mode (commissioning mode) so that the second device (72) can register the target IoT device (71) (additional registration of the first administrator).

[0089] Thereafter, in step 709, the first device (73) may transmit a fourth message to the second device (72) in response to the third message, which includes information indicating whether to allow the second device (72) as a multi-manager (first manager) for the target IoT device (71). Then, in step 710, the second device (72) that has received the fourth message checks whether to allow it, and if allowed, performs registration (commissioning) for the use of the target IoT device (71). The registration may include searching (discovering) and / or connecting to the target IoT device (71) from the second device (72).

[0090] FIGS. 8A and 8B are diagrams illustrating an example of a method for providing IoT services using a first device, which is a first manager of IoT devices, as a home hub in an IoT system supporting a multi-manager service according to an embodiment of the present disclosure, using an encrypted on-boarding payload.

[0091] In the examples of FIGS. 8A and 8B, the IoT system illustrates an IoT service environment including a target IoT device (81), a second device (82) that wishes to use the target IoT device (81) through a multi-manager service, and a plurality of first devices (83-1, 83-2) that have registered ownership of the target IoT device (81) (i.e., registered as first managers).

[0092] In the examples of FIGS. 8A and 8B, the target IoT device (81) and the second device (82) are each illustrated as one device for convenience of explanation, but there may be multiple target IoT devices and multiple second devices. In addition, there may be one or more first devices registered as the first manager for the target IoT device (81).

[0093] Referring to FIG. 8a, in steps 800a and 800b, a plurality of first devices (83-1, 83-2) registered as first administrators for the target IoT device (81) can each store part or all of the aforementioned on-boarding payload required for the multi-administrator service. The on-boarding payload is information required for a device other than the first administrator of the target IoT device (81) to be registered as an additional first administrator of the target IoT device (81) in a commissioning mode with the target IoT device (81), and can use information that can be used for registration / authentication, such as a Discriminator, Passcode, QR code, PIN, etc.

[0094] In step 801, the second device (82) searches for a connectable target IoT device (81). At this time, the second device (82) can search for a connectable target IoT device (81) using a QR code physically attached to the target IoT device (81) or through an IP network, for example, DNS-SD. At this time, the second device (82) can obtain information about the target IoT device (81). The information about the target IoT device (81) can include, for example, an ID of the target IoT device (81), descriptor information, etc. In addition, in step 801, the second device (62) can obtain part or all of the on-boarding payload for the target IoT device (61) using a discriminator, passcode, QR code, PIN, etc. of the target IoT device (61).

[0095] In step 802, the second device (82) that finds the target IoT device (81) to be used can broadcast a first message including the ID of the target IoT device (81) on the network to find the first device, which is the first manager of the target IoT device (81). A plurality of first devices (83-1, 83-2) can receive the first message. As an optional embodiment, the first message can further include descriptor information of the target IoT device (81). The descriptor information can be, for example, information indicating the smart light when the target IoT device (81) is a smart light. The first message can be transmitted using, for example, BLE, USD, which is a low-power Bluetooth communication method, DNS-SD, which is a communication method for DNS-based service discovery, a Wi-Fi detection message, etc. As an optional embodiment, it may also be possible to transmit the first message in a group cast or unicast manner.

[0096] In steps 803 and 804, a plurality of first devices (83-1, 83-2) that have received a first message including the ID of the target IoT device (81) may each transmit a second message including its own device ID (or administrator ID) to the second device (82) in response. As an optional embodiment, the second message may further include administrator descriptor information of the first device (83-1, 83-2). The administrator descriptor information may be, for example, information indicating that the first device (83-1, 83-2) is a first administrator of the target IoT device (81).

[0097] In step 805, the second device (62) that has received the second message from each of the plurality of first devices (83-1, 83-2) can select the first device (83-1 or 83-2) from among the plurality of first devices (83-1, 83-2) to request / apply for the multi-manager service. At this time, the selection can be performed through inputting consent from the user of the second device (82), etc. In the present embodiment, it is assumed that the first device (83-2) is selected as the target of the request / application for the multi-manager service. In step 806, the second device (82) can transmit a third message to the first device (83-2) that includes at least one of the ID of the target IoT device (81), the ID of the selected first device (83-2), the ID of the corresponding second device (82), and a public key for encrypting the on-boarding payload. The third message is a message requesting the first device (83-2) to allow the second device (82) to act as a multi-manager for the target IoT device (81). As an optional embodiment, the third message may further include at least one of the manager descriptor information of the first device (83-2) and the descriptor information of the second device (82).

[0098] The first device (83-2), which has received the third message for requesting permission for multiple administrators from the second device (82) at step 807, can generate a nonce for authentication of the multi-administrator service and transmit it to the second device (82). The nonce refers to a random variable, temporary value, etc. used in the authentication procedure. The procedure for performing authentication between the two devices using the nonce can utilize a known authentication technique.

[0099] Referring to FIG. 8b, the second device (82) that received the nonce in step 808 can generate first authentication information necessary to be registered as an additional first manager of the target IoT device (81) using the nonce and part or all of the on-boarding payload acquired in step 801. In step 809, the second device (82) transmits the first authentication information to the first device (83-2), and in step 810, the first device (83-2) generates second authentication information using part or all of the on-boarding payload acquired in step 800b and the nonce generated in step 807, and performs authentication information verification by comparing whether the received first authentication information and the generated second authentication information are identical. The first device (83-2) determines that the first authentication information and the second authentication information are verified if the comparison results show that the first authentication information and the second authentication information are identical.

[0100] The first device (83-2) that received the third message for requesting permission for multiple administrators from the second device (82) in step 811 can agree / reject allowing the second device (82) as a multiple administrator (i.e., the first administrator) for the target IoT device (81) based on the verification result in step 810. At this time, the agreement / rejection can be performed through an agreement / rejection input by the user of the first device (83-2). In step 812, the first device (83-2) that confirmed the agreement input can set / change the operation mode of the target IoT device (81) to the aforementioned registration mode (commissioning mode) so that the second device (82) can register the target IoT device (81) (additional registration of the first administrator).

[0101] Thereafter, in step 813, the first device (83-2) may transmit, in response to the third message, a fourth message to the second device (82), which includes information indicating whether to allow the second device (82) as a multi-manager (first manager) for the target IoT device (81) and (if allowed) an on-boarding payload for the target IoT device (81). At this time, the on-boarding payload may be encrypted using the public key received in step 806. In step 814, the second device (82) that receives the fourth message verifies whether to allow it, and if allowed, performs registration (commissioning) for the use of the target IoT device (81). The registration may include searching (discovering) and / or connecting to the target IoT device (81) from the second device (82). The second device (82) can decrypt the encrypted on-boarding payload using the public key and use the decrypted on-boarding payload in the registration mode of the target IoT device (81).

[0102] FIGS. 9A and 9B are diagrams illustrating an example of a method for providing IoT services using a first device, which is a first manager of IoT devices, as a home hub in an IoT system supporting a multi-manager service according to an embodiment of the present disclosure, using an encrypted on-boarding payload.

[0103] In the examples of FIGS. 9A and 9B, the IoT system illustrates an IoT service environment including a target IoT device (91), a second device (92) that wishes to use the target IoT device (91) through a multi-manager service, and a first device (93) that has registered ownership of the target IoT device (91) (i.e., registered as a first manager).

[0104] In the examples of FIGS. 9A and 9B, the target IoT device (91), the second device (92), and the first device (93) are each illustrated as one device for convenience, but there may be multiple target IoT devices and multiple first and second devices. In addition, there may be one or more first devices registered as the first manager for the target IoT device (91).

[0105] Referring to FIG. 9a, it is assumed that in steps 901a and 901b, the second device (92) and the first device (93) registered as the first manager for the target IoT device (91) have previously stored credentials for the authentication procedure required in the multi-manager service. The credentials may utilize, for example, certificates, shared secret information, etc.

[0106] In step 902, the second device (92) searches for a connectable target IoT device (91). At this time, the second device (92) can search for a connectable target IoT device (91) using a QR code physically attached to the target IoT device (91) or through an IP network, for example, DNS-SD. At this time, the second device (92) can obtain information about the target IoT device (91). The information about the target IoT device (91) can include, for example, an ID of the target IoT device (91), descriptor information, etc.

[0107] In step 903, the second device (92) that finds the target IoT device (91) to be used can broadcast a first message including the ID of the target IoT device (91) on the network to find the first device, which is the first manager of the target IoT device (91). The first message can be transmitted using, for example, BLE, which is a low-power Bluetooth communication method, USD, DNS-SD, which is a communication method for DNS-based service discovery, a Wi-Fi detection message, etc. As an optional embodiment, it may also be possible to transmit the first message in a group cast or unicast manner.

[0108] In step 904, the first device (93) that has received the first message including the ID of the target IoT device (91) can transmit a second message including its own device ID (or administrator ID) to the second device (92) in response. As an optional embodiment, the second message may further include administrator descriptor information of the first device (93). The administrator descriptor information may be, for example, information indicating that the first device (93) is the first administrator of the target IoT device (91). In step 905, the second device (92) that has received the second message from the first device (93) can select the first device (93) to request / apply for the multi-administrator service. At this time, the selection may be performed through inputting consent from the user of the second device (92), etc.

[0109] At step 906, the second device (92) can transmit a third message to the first device (93) that includes at least one of the ID of the target IoT device (91), the ID of the first device (93), and the ID of the second device (92). The third message is a message requesting the first device (93) to allow the second device (92) to be a multi-manager for the target IoT device (91). In an optional embodiment, the third message can further include at least one of the manager descriptor information of the first device (93) and the descriptor information of the second device (92).

[0110] Referring to FIG. 9b, the first device (93) that received the third message for a multi-administrator permission request from the second device (92) in step 907 may perform an authentication procedure for the second device (92) based on the credentials previously stored in steps 900a and 900b for authentication of the multi-administrator service. In addition, the first device (93) may generate a session key for a secure connection in the IoT service and transmit it to the second device (92). The session key may be used for encryption of the on-boarding payload to be transmitted to the second device (92).

[0111] In step 907, based on the authentication result, in step 908, the first device (93) can consent / reject allowing the second device (92) to be a multi-administrator (i.e., the first administrator) for the target IoT device (91). At this time, consent / rejection can be performed through consent / rejection input by the user of the first device (93). In step 909, the first device (93) that has confirmed the consent input can set / change the operation mode of the target IoT device (91) to the aforementioned registration mode (commissioning mode) so that the second device (92) can register the target IoT device (91) (additional registration of the first administrator).

[0112] Thereafter, in step 910, the first device (93) may encrypt an on-boarding payload that can be used in the registration mode of the target IoT device (91) using the session key, and in step 911, in response to the third message, may transmit to the second device (92) a fourth message including information indicating whether to allow the second device (92) as a multi-manager (first manager) for the target IoT device (91) and (if allowed) the encrypted on-boarding payload for the target IoT device (81). In step 912, the second device (92) that receives the fourth message checks whether to allow it, and if allowed, performs commissioning for the use of the target IoT device (91). The registration may include searching (discovering) and / or connecting to the target IoT device (91) from the second device (92). The second device (92) can decrypt the encrypted on-boarding payload using the session key and use the decrypted on-boarding payload in the registration mode of the target IoT device (81).

[0113] FIG. 10 is a diagram illustrating an example of a method for providing an AP-based IoT service in an IoT system supporting a multi-manager service according to an embodiment of the present disclosure.

[0114] The example of Fig. 10 is an embodiment in which information about a target IoT device (1030) can be provided to a second device (1020) through an AP (1040) of an IoT system, and a second device (1020) that wishes to use the target IoT device (1030) in an IoT system that supports a multi-manager service receives permission to use the target IoT device (1030) from a first device (1010) through the AP (1040). In Fig. 10, the first device (1010) and the IoT device (1030) are subscribed to a network service (1000) that provides an IoT service, and the second device (1020) can use the IoT device (1030) through a multi-manager service.

[0115] Referring to FIG. 10, it is assumed that in step 1001, the AP (1040) is connected to the first device (1010), which is the first manager of the target IoT device (1030). It is also assumed that the AP (1040) has previously stored mapping information of the first manager ID mapped to the IoT device ID of the target IoT device (1030). The first manager ID may use the device ID of the first device operating as the first manager. Although not shown, the AP (1040) may store / register mapping information of at least one first manager ID mapped to each IoT device of at least one IoT device (i.e., mapping information between the IoT device and the first manager (device)). In the embodiments of the present disclosure below, the ID of the first device operating as the first manager may be understood as the first manager ID.

[0116] In step 1002, the second device (1020) can obtain information about the target IoT device (1030) (hereinafter referred to as IoT device information) using, for example, a method known in the Matter standard or a QR code attached to the IoT device (1030). The IoT device information may include an IoT device ID (identifier), IoT device descriptor information, etc. In step 1003, the second device (1020) can obtain information about the first device (1010) through signaling with an AP (1040) that has previously stored information about the first device (1010), which is the first manager of the target IoT device (1030). The information about the first device (1010) may include an ID of the first device (1010), manager descriptor information, etc.

[0117] In step 1004, the second device (1020), which has acquired information about the first device (1010), can transmit a message to the AP (1040) for requesting a connection to the IoT device (1030). The message for requesting a connection may include, for example, at least one of the ID of the target IoT device (1030), the ID of the first device (1010), the ID of the second device (1020), and descriptor information.

[0118] In step 1005, the AP (1040) that received the message for the connection request can transmit the message for the connection request or information notifying the connection request to the first device (1010). In step 1006, the first device (1010) that received the message for the connection request or information notifying the connection request can output an alarm message (e.g., text, sound, video message, etc.) notifying the user of the first device (1010) that there is a connection request for the target IoT device (1030) from the second device (1020), and in response to the output, can obtain an consent / rejection input from the user of the first device (1010).

[0119] Although not illustrated as an optional embodiment, the first device (1010) may transmit a message to the second device (1020) indicating consent / rejection of a connection request for the IoT device (1030) in response to the connection request. Although not illustrated as an optional embodiment, if the first device (1010) consents to the connection request, the first device (1010) may provide the second device (1020) with an onboarding payload, which is information necessary for the second device (1020) to be registered as an additional first manager of the IoT device (1030) in commissioning mode (i.e., registration mode), in response to the connection request.

[0120] In step 1006, if the first device (1010) obtains the user's consent input, in step 1007, the first device (1010) can set / change the operation mode of the IoT device (1030) to the registration mode so that the registration of the IoT device (1030) (additional registration by the first administrator) is possible in the second device (1020).

[0121] Thereafter, in step 1008, the second device (1020) may perform commissioning on the target IoT device (1030) whose status has changed to registration mode, thereby additionally registering it as a first manager of the target IoT device (1030). In the present disclosure, the registration may include searching (discovering) and / or connecting to the target IoT device (1030) from the second device (1020). In an optional embodiment, the on-boarding payload may be utilized when additionally registering it as the first manager.

[0122] Through each of the embodiments of FIGS. 11 to 17b to be described below or a combination of two or more embodiments, the second device may transmit a request message to the AP requesting at least one of information about the first device, which is a first manager for connectable IoT devices in an IoT system, and information about the connectable IoT devices, and in response to the request message, may receive from the AP a response message including at least one of information about the first device and information about the connectable IoT devices.

[0123] FIG. 11 is a diagram illustrating an example of a method for storing / registering mapping information between an IoT device and a first manager (device) in an AP in an IoT system supporting a multi-manager service according to an embodiment of the present disclosure.

[0124] In the example of Fig. 11, the IoT system illustrates an IoT service environment including a target IoT device (111) and an AP (113) that registers, stores, and manages information about a first device that has ownership of the target IoT device (111) (i.e., is a first manager). In the example of Fig. 10, the target IoT device (111) and the first device (112) are each illustrated as one device for convenience of explanation, but a plurality of target IoT devices and a plurality of first devices may exist.

[0125] Referring to FIG. 11, in step 1101, the first device (112) performs registration (commissioning) for use of the target IoT device (111). The registration may include searching (discovering) and / or connecting to the target IoT device (111) from the first device (112). Through the registration, the first device (112) may become the first manager of the target IoT device (111). In addition, the first device (112) may attach (or connect) the target IoT device (111) to the AP (113) and register it on the manager platform of the first device (112) during the registration.

[0126] In step 1102, the first device (112) can transmit mapping information between the target IoT device (111) and the first manager, the first device (112), to the AP (113). The mapping information includes, for example, mapping information between the ID of the target IoT device (111) and the ID (i.e., admin ID) of the first device (112). As an optional embodiment, the mapping information may further include at least one of the Thing descriptor information of the target IoT device (111) and the manager descriptor information of the first device (112). The descriptor information may be composed of, for example, user-friendly text. For example, if the first device (112) is a smart speaker in the IoT system and the registered alias of the first manager is Joe, a description such as "Joe's speaker" may be provided as the manager descriptor information. In addition, the device ID, such as the ID of the target IoT device (111) and the ID of the first device (112), may use various combinations, such as a discriminator, a Fabric ID for identifying an IoT service, and a node ID.

[0127] In step 1103, the AP (113) that received the mapping information from the first device (112) can register and store the mapping information between the target IoT device (111) and the first manager, the first device (112). In step 1104, the AP (113) can transmit information indicating the success or failure of the registration and storage of the mapping information to the first device (112) as a response. In an optional embodiment, when the first device (112) includes the function of the AP (113), the operations of steps 1102 to 1104 can be performed as internal operations of the first device (112).

[0128] Additionally, as an optional embodiment, the registration and storage of the mapping information in the AP (113) may be performed periodically or aperiodically. In addition, when at least one of the IoT device and the first device (or related information of the IoT device and the first device) is added, modified, or deleted in the IoT system, the mapping information stored in the AP (113) may be updated.

[0129] FIGS. 12A and 12B are diagrams illustrating an example of a method for providing IoT services using an AP in an IoT system supporting multi-manager services according to an embodiment of the present disclosure. In this embodiment, it is assumed that the AP (123) has previously stored mapping information between an IoT device and a first manager (device) according to the method of FIG. 11.

[0130] In the examples of FIGS. 12A and 12B, the IoT system illustrates an IoT service environment including a target IoT device (121), a second device (122) that wishes to use the target IoT device (121) through a multi-manager service, an AP (123) that stores / manages the mapping information, and a first device (124) that has registered ownership of the target IoT device (121) (i.e., registered as a first manager). In the examples of FIGS. 12A and 12B, the target IoT device (121), the second device (123), and the first device (124) are each illustrated as one device for convenience, but a plurality of target IoT devices and a plurality of first and second devices may exist. In addition, one or more first devices may be registered as first managers for the target IoT device (121).

[0131] Referring to FIG. 12A, in step 1201, the second device (121) searches for a connectable target IoT device (122). At this time, the second device (122) may search for a connectable target IoT device (121) using a QR code physically attached to the target IoT device (121) or through an IP network, for example, DNS-SD. At this time, the second device (122) may obtain information about the target IoT device (121). The information about the target IoT device (121) may include, for example, an ID of the target IoT device (121), descriptor information, etc.

[0132] In step 1202, the second device (122) that finds the target IoT device (121) to be used can transmit a first request message requesting information about the first device (124) to the AP (123) in order to find the first device (124), which is the first manager of the target IoT device (121). The first request message can include the ID of the target IoT device (121). As an optional embodiment, the first request message can include information requesting information about the first managers (first devices) for all target IoT devices registered in the mapping information of the AP (123) (or a group predetermined according to the type / function / frequency of use / usage time of the target IoT devices). As an optional embodiment, the first request message can further include descriptor information of the target IoT device (121).

[0133] In step 1203, the AP (123) that received the first request message can search for information of the first device (124) mapped to the ID of the target IoT device (121) from the stored mapping information, and in step 1204, can transmit a first response message including the searched information of the first device (124) to the second device (122). As an optional embodiment, the first response message can include at least one of the ID of the target IoT device (121), the ID of the first device (124), descriptor information of the target IoT device (121), and manager descriptor information of the first device (124). As an optional embodiment, if the first request message in step 1202 includes information requesting information of first managers (first devices) for all (or a predetermined group) of target IoT devices, the first response message may include information of first managers (first devices) for all (or a requested group) of target IoT devices.

[0134] At step 1205, the second device (122) that received the first response message from the AP (123) can select a first device (124) from among at least one first device identified in the first response message to request / apply for the multi-manager service. At this time, the selection can be performed through inputting consent from the user of the second device (122), etc. In this embodiment, it is assumed that the first device (124) is selected as the target of the request / application for the multi-manager service.

[0135] In step 1206, the second device (122) can transmit a second request message to the AP (123) that includes at least one of the ID of the target IoT device (121), the ID of the selected first device (124), and the ID of the corresponding second device (122). The second request message is a message requesting the first device (124) to allow the second device (122) to be a multi-manager for the target IoT device (121). As an optional embodiment, the second request message can further include at least one of the manager descriptor information of the first device (124) and the descriptor information of the second device (122).

[0136] In step 1207, the second request message (or information included in the second request message) is transmitted to the first device (124) via the AP (123). In step 1208, the first device (124) that has received the second request message (or information included in the second request message) can consent / reject allowing the second device (122) to be a multi-manager (i.e., the first manager) for the target IoT device (121). At this time, consent / rejection can be performed through consent / rejection input by the user of the first device (124).

[0137] Thereafter, in step 1209, the first device (124) can set / change the operation mode of the target IoT device (121) to a commissioning mode to enable the commissioning (i.e., additional registration of the first manager) of the target IoT device (121) from the second device (122) (if permitted in step 1208). In steps 1210 and 1211, the first device (124) can, in response to the second request message, transmit a second response message to the second device (122) via the AP (123), which includes information indicating whether to permit the second device (122) as a multi-manager (the first manager) for the target IoT device (121). Then, in step 1212, the second device (122) that receives the second response message verifies whether or not it is permitted, and if permitted, performs commissioning for the use of the target IoT device (121). The above registration may include searching (discovering) and / or connecting to the target IoT device (121) from the second device (122).

[0138] FIGS. 13A and 13B are diagrams illustrating an example of a method for providing an IoT service using an AP in an IoT system supporting a multi-manager service according to an embodiment of the present disclosure. In this embodiment, it is assumed that the AP has previously stored mapping information between an IoT device and a first manager (device) according to the method of FIG. 11. Compared to the embodiment of FIGS. 12A and 12B, the embodiment of FIGS. 13A and 13B does not require an operation of directly searching for a target IoT device to which a second device can connect, as in step 1201 of FIG. 12A, and the second device can obtain information about a target IoT device to which it can connect from the AP.

[0139] In the examples of FIGS. 13A and 13B, the IoT system illustrates an IoT service environment including a target IoT device (131), a second device (132) that wishes to use the target IoT device (131) through a multi-manager service, an AP (133) that stores / manages the above-described mapping information in advance, and a first device (134) that has registered ownership of the target IoT device (131) (i.e., registered as a first manager). In the examples of FIGS. 13A and 13B, the target IoT device (131), the second device (133), and the first device (134) are each illustrated as one device for convenience, but a plurality of target IoT devices and a plurality of first and second devices may exist. In addition, one or more first devices may be registered as first managers for the target IoT device (131).

[0140] Referring to FIG. 13A, in order to check a list of at least one IoT device (hereinafter, IoT device list information) connectable through a multi-manager service in step 1301, the second device (132) may transmit a first request message requesting the IoT device list information to the AP (133). The mapping information may represent a mapping relationship of at least one first manager ID mapped to each IoT device of at least one IoT device in the form of a list. The IoT device list information may be identical to the mapping information or may represent a mapping relationship between at least one IoT device available to the second device (132) among the IoT devices registered in the mapping information and at least one first manager (first device).

[0141] In step 1302, the AP (133) that receives the first request message can transmit a first response message including the IoT device list information to the second device (132). In the present embodiment, the IoT device list information can include information of the first device (134). As an optional embodiment, the first response message can include at least one of a list of ID(s) of IoT device(s), a list of ID(s) of the first device(s) of the IoT device(s), descriptor information of the IoT device(s), and manager descriptor information of the first device(s).

[0142] At step 1303, the second device (132) that received the first response message from the AP (133) can select the first device (134) from among the list of IoT device(s) and first device(s) identified in the first response message to request / apply for the multi-manager service for the target IoT device (131). At this time, the selection can be performed through inputting consent from the user of the second device (132), etc. In this embodiment, it is assumed that the first device (134) is selected as the target of the request / application for the multi-manager service.

[0143] In step 1304, the second device (132) may transmit a second request message to the AP (123) that includes at least one of the ID of the selected target IoT device (131), the ID of the selected first device (134), and the ID of the corresponding second device (132). In an optional embodiment, when there are multiple target IoT devices selected by the second device (132), the IDs of the target IoT devices and the IDs of the corresponding first devices may be included in the second request message in the form of a list. The second request message is a message that requests the first device (134) through the AP (133) to allow the second device (132) as a multiple manager for the target IoT device (131). In an optional embodiment, the second request message may further include at least one of the manager descriptor information of the first device (134) and the descriptor information of the second device (132).

[0144] In step 1305, the second request message (or information included in the second request message) is transmitted from the AP (133) to the first device (134). In step 1306, the first device (134) that has received the second request message (or information included in the second request message) can consent / reject allowing the second device (132) to be a multi-manager (i.e., the first manager) for the target IoT device (131). At this time, consent / rejection can be performed through consent / rejection input by the user of the first device (134).

[0145] Thereafter, in step 1307, the first device (134) can set / change the operation mode of the target IoT device (131) to a commissioning mode to enable the commissioning (i.e., additional registration of the first manager) of the target IoT device (131) in the second device (132) (if permitted in step 1206). In steps 1308 and 1309, the first device (134) can, in response to the second request message, transmit a second response message to the second device (132) via the AP (133), which includes information indicating whether to permit the second device (132) as a multi-manager (first manager) for the target IoT device (131). Then, in step 1310, the second device (132) that receives the second response message verifies whether or not it is permitted, and if permitted, performs commissioning for the use of the target IoT device (131). The above registration may include searching (discovering) and / or connecting to the target IoT device (131) from the second device (132).

[0146] FIGS. 14A and 14B are diagrams illustrating an example of a method for providing an IoT service using an AP and an encrypted onboarding payload in an IoT system supporting a multi-manager service according to an embodiment of the present disclosure. In this embodiment, it is assumed that the AP has previously stored mapping information between an IoT device and a first manager (device) according to the method of FIG. 11 described above, and that the first device has previously a root certificate for verifying the certificate used to encrypt the onboarding payload.

[0147] In the examples of FIGS. 14A and 14B, the IoT system illustrates an IoT service environment including a target IoT device (141), a second device (142) that wishes to use the target IoT device (141) through a multi-manager service, an AP (143) that stores / manages the mapping information, and a first device (144) that has registered ownership of the target IoT device (141) (i.e., registered as a first manager). In the examples of FIGS. 14A and 14B, the target IoT device (141), the second device (143), and the first device (144) are each illustrated as one device for convenience, but a plurality of target IoT devices and a plurality of first and second devices may exist. In addition, one or more first devices may be registered as first managers for the target IoT device (141).

[0148] Referring to FIG. 14A, in step 1401, the second device (141) searches for a connectable target IoT device (142). At this time, the second device (142) may search for a connectable target IoT device (141) using a QR code physically attached to the target IoT device (141) or through an IP network, for example, DNS-SD. At this time, the second device (142) may obtain information about the target IoT device (141). The information about the target IoT device (141) may include, for example, an ID of the target IoT device (141), descriptor information, etc.

[0149] In step 1402, the second device (142) that finds the target IoT device (141) to be used can transmit a first request message requesting information about the first device (144) to the AP (143) in order to find the first device (144), which is the first manager of the target IoT device (141). The first request message can include the ID of the target IoT device (141). As an optional embodiment, the first request message can include information requesting information about the first managers (first devices) for all target IoT devices registered in the mapping information of the AP (143) (or a group predetermined according to the type / function / frequency of use / use time of the target IoT devices). As an optional embodiment, the first request message can further include descriptor information of the target IoT device (141).

[0150] In step 1403, the AP (143) that received the first request message can search for information of the first device (144) mapped to the ID of the target IoT device (141) from the stored mapping information, and in step 1404, can transmit a first response message including the searched information of the first device (144) to the second device (142). As an optional embodiment, the first response message can include at least one of the ID of the target IoT device (141), the ID of the first device (144), descriptor information of the target IoT device (141), and manager descriptor information of the first device (144). As an optional embodiment, if the first request message in step 1402 includes information requesting information of first managers (first devices) for all (or a predetermined group) of target IoT devices, the first response message may include information of first managers (first devices) for all (or a requested group) of target IoT devices.

[0151] At step 1405, the second device (142) that received the first response message from the AP (143) can select a first device (144) from among at least one first device identified in the first response message to request / apply for the multi-manager service. At this time, the selection can be performed through inputting consent from the user of the second device (142), etc. In this embodiment, it is assumed that the first device (144) is selected as the target of the request / application for the multi-manager service.

[0152] At step 1406, the second device (142) can transmit a second request message to the AP (143) that includes at least one of the ID of the target IoT device (141), the ID of the selected first device (144), the ID of the corresponding second device (142), and a certificate of the second device (142). The certificate may include a public key for encrypting the on-boarding payload. The second request message is a message requesting the first device (144) to allow the second device (142) as a multi-manager for the target IoT device (141). In an optional embodiment, the second request message may further include at least one of the manager descriptor information of the first device (144) and the descriptor information of the second device (142).

[0153] In step 1407, the second request message (or information included in the second request message) is transmitted to the first device (124) via the AP (143). In step 1408, the first device (144) that has received the second request message (or information included in the second request message) can verify the certificate included in the second request message using the root certificate it previously had. In step 1409, the first device (144) can consent / reject allowing the second device (142) as a multi-manager (i.e., first manager) for the target IoT device (141). At this time, consent / rejection can be performed through consent / rejection input by the user of the first device (144).

[0154] At step 1410, the first device (144) may generate an on-boarding payload, which is information necessary to register the second device (142) as an additional first manager of the target IoT device (141) (if allowed at step 1409), and may encrypt the on-boarding payload using the public key included in the verified certificate.

[0155] Thereafter, in step 1411, the first device (144) can set / change the operation mode of the target IoT device (141) to the registration mode (commissioning mode) to enable registration (i.e., additional registration of the first manager) of the target IoT device (141) from the second device (142) (if permitted in step 1409).

[0156] In steps 1412 and 1413, the first device (124) may, in response to the second request message, transmit a second response message to the second device (142) via the AP (143), which includes information indicating whether to allow the second device (142) as a multi-manager (first manager) for the target IoT device (141) and (if allowed) the encrypted on-boarding payload. Then, in step 1414, the second device (142) that has received the second response message determines whether to allow it, and if allowed, performs registration (commissioning) for the use of the target IoT device (141). The registration may include searching (discovering) and / or connecting to the target IoT device (141) from the second device (142). The second device (142) can decrypt the encrypted on-boarding payload using the public key and use the decrypted on-boarding payload in the registration mode of the target IoT device (141).

[0157] FIGS. 15A and 15B are diagrams illustrating an example of a method for providing an IoT service using an AP and an encrypted onboarding payload in an IoT system supporting a multi-manager service according to an embodiment of the present disclosure. In this embodiment, it is assumed that the AP has previously stored mapping information between an IoT device and a first manager (device) according to the method of FIG. 11 described above, and that the first device has previously a root certificate for verifying the certificate used to encrypt the onboarding payload.

[0158] The operations of steps 1501 to 1505 in FIG. 15a are identical to the operations of steps 1401 to 1405 in FIG. 14a, so a detailed description thereof will be omitted.

[0159] In the above step 1501, the second device (152) can obtain part or all of the on-boarding payload for the target IoT device (151) through the discriminator, passcode, QR code, PIN, etc. of the target IoT device (151).

[0160] Referring to FIG. 15A, in step 1506, the second device (152) may transmit a second request message to the AP (143) that includes at least one of the ID of the target IoT device (151), the ID of the selected first device (154), and the ID of the second device (152). The second request message is a message requesting the first device (154) to allow the second device (152) to be a multi-manager for the target IoT device (151). As an optional embodiment, the second request message may further include at least one of the manager descriptor information of the first device (154) and the descriptor information of the second device (152).

[0161] In step 1507, the second request message (or information included in the second request message) is transmitted to the first device (154) via the AP (153). In steps 1508 and 1509, the first device (154), which has received the second request message (or information included in the second request message), generates a nonce for authentication of the multi-manager service (i.e., authentication of the second device (154)) and transmits an authentication request message including the nonce to the second device (82) via the AP (153). The nonce refers to a random variable, temporary value, etc. used in the authentication procedure. The procedure for performing authentication between two devices using the nonce can utilize a known authentication technique.

[0162] In step 1510, the second device (152) can generate a (digital) signature used in the authentication procedure using at least one of the private key of the second device (152), the received nonce, and part or all of the on-boarding payload acquired in step 1501. In steps 1511 and 1512, the second device (152) transmits an authentication response message including the (digital) signature and the certificate of the second device (152) to the first device (154) via the AP (153) in response to the citation request message.

[0163] At step 1513, the first device (151) can verify the certificate and digital signature included in the second request message using the root certificate and public key it previously possessed. Digital signature using an asymmetric key can be performed in, for example, two ways. The first way is to encrypt a digital signature using a public key and decrypt the encrypted digital signature using a private key. The second way is to encrypt a digital signature using a private key and decrypt the encrypted digital signature using a public key.

[0164] In this embodiment, when the second device (152) transmits a digital signature encrypted using a private key to the first device (154) via the AP (153), the first device (154) can decrypt the encrypted digital signature using the public key and verify (confirm) whether the digital signature was transmitted by the second device (152). In this embodiment, the use of the second type of digital signature is exemplified, but the use of the first type of digital signature may also be possible.

[0165] At step 1514, the first device (154) can consent / reject allowing the second device (152) to act as a multi-manager (i.e., the first manager) for the target IoT device (151). At this time, consent / rejection can be performed through consent / rejection input by the user of the first device (154).

[0166] Thereafter, the first device (154) generates an encrypted on-boarding payload, sets a registration mode for the target IoT device (151), transmits a second response message including information indicating whether to allow the second device (152) as a multi-administrator (the first administrator) and the encrypted on-boarding payload, and the operations of steps 1515 to 1519, in which the second device (142) performs registration (commissioning) for the target IoT device (151), are identical to the operations of steps 1410 to 1414 of FIG. 14b, and therefore, a detailed description thereof will be omitted.

[0167] FIGS. 16A and 16B are diagrams illustrating an example of a method for providing IoT services using an AP in an IoT system supporting a multi-manager service according to an embodiment of the present disclosure when a first device, which is a first manager, is not connected to the AP. In this embodiment, it is assumed that the AP has previously stored mapping information between the IoT device and the first manager (device) according to the method of FIG. 11 described above.

[0168] The operations of steps 1601 to 1605 in FIG. 16a are identical to the operations of steps 1201 to 1205 in FIG. 12a, so a detailed description thereof will be omitted.

[0169] Referring to FIG. 16A, in step 1606, the second device (162) may transmit a second request message to the AP (163) that includes at least one of the ID of the target IoT device (161), the ID of the selected first device (154), and the ID of the second device (152). The second request message is a message requesting the first device (164) to allow the second device (162) to be a multi-manager for the target IoT device (161). In an optional embodiment, the second request message may further include at least one of the manager descriptor information of the first device (164) and the descriptor information of the second device (152).

[0170] In step 1607, if the AP (163) determines that the first device (164) is not connected to the AP (163), the AP (163) triggers a connection procedure so that the first device (164), which is the first manager, is connected to the AP (163) via, for example, BLE or a cloud network. In step 1608, the first device (164) is connected to the AP (163) through the connection procedure.

[0171] Thereafter, the AP (163) transmits the second request message to the first device (164), the first device (164) receives the user's consent / rejection input, and (in case of consent) the first device (164) sets the registration mode for the target IoT device (161), transmits the second response message including information indicating whether to allow the second device (162) as a multi-manager (first manager), and the second device (162) performs registration (commissioning) for the target IoT device (161). The operations of steps 1609 to 1614 are identical to the operations of steps 1207 to 1212 of FIG. 12b, so a detailed description thereof will be omitted.

[0172] FIGS. 17A and 17B are diagrams illustrating an example of a method for providing IoT services by prioritizing a list of first devices, which are first managers, using an AP in an IoT system supporting a multi-manager service according to an embodiment of the present disclosure. In this embodiment, it is assumed that the AP (123) has previously stored mapping information between the IoT device and the first manager (device) according to the method of FIG. 11.

[0173] In the examples of FIGS. 17A and 17B, the IoT system illustrates an IoT service environment including a target IoT device (171), a second device (172) that wishes to use the target IoT device (171) through a multi-manager service, an AP (173) that stores the mapping information, and a first device (174) that has registered ownership of the target IoT device (171) (i.e., registered as a first manager). In the examples of FIGS. 17A and 17B, the target IoT device (171), the second device (173), and the first device (174) are each illustrated as one device for convenience, but a plurality of target IoT devices and a plurality of first and second devices may exist. In addition, one or more first devices may be registered as first managers for the target IoT device (171).

[0174] In steps 1701 to 1703 of FIG. 17A, the second device (171) searches for a connectable target IoT device (172), the second device (172) that finds the target IoT device (121) transmits a first request message requesting information about the first device (124) to the AP (173), and the AP (123) that receives the first request message searches for information about the first device (124) mapped to the ID of the target IoT device (171) from pre-stored mapping information, the operation can be performed in the same manner as the operation in steps 1201 to 1203 of FIG. 12A.

[0175] Thereafter, in step 1704 of FIG. 17a, the AP (173) can check whether at least one first device registered as a first manager of the target IoT device (121) is connected to the AP and / or the signal strength (e.g., Received Signal Strength Indicator (RSSI)) of the at least one first device based on the mapping information. In step 1705, the AP (173) sorts the list of at least one first device registered as a first manager of the target IoT device (121) in order of priority based on at least one of the confirmed AP connection and signal strength. For example, the list can be sorted in order of the largest signal strength among the first device(s) connected to the AP.

[0176] In step 1706, the AP (173) may transmit a first response message including information of the first device (124) selected according to the priority to the second device (122). As an optional embodiment, the first response message may include at least one of the ID of the target IoT device (121), the ID of the first device (124), descriptor information of the target IoT device (121), and manager descriptor information of the first device (124). As an optional embodiment, if the first request message in step 1202 includes information requesting information of first managers (first devices) for all (or a predetermined group) of target IoT devices, the first response message includes list information of first managers (first devices) for all (or a requested group) of target IoT devices. The list information is list information sorted according to the priority in step 1705.

[0177] Thereafter, the operations of steps 1707 to 1714 in FIGS. 17a and 17b can be performed in the same manner as the operations of steps 1205 to 1212 in FIGS. 12a and 12b described above.

[0178] According to the embodiments of the present disclosure described above, in an IoT system supporting a multi-manager service, information about a first device(s) that is a first manager of a target IoT device can be easily / securely provided to a second device that wishes to use the target IoT device. In addition, when performing commissioning of a target IoT device in the second device, the first device that is a first manager can easily / securely provide (via an AP) an on-boarding payload required for the second device. In addition, for the second device to use the target IoT device, information about the first device can be easily / securely provided to the second device upon request / application from the second device without prior operation of the first device.

[0179] FIG. 18 is a diagram showing an example configuration of a device in a wireless communication system according to an embodiment of the present disclosure.

[0180] The device of FIG. 18 may be one of the first device, the second device, and the AP described in the embodiments of FIGS. 4 to 17B described above. The device of FIG. 18 may include a processor (1801), a transceiver (1803), and a memory (1805). The processor (1801), the transceiver (1803), and the memory (1805) of the device may operate according to the method described in the embodiments of FIGS. 4 to 17B. However, the components of the device are not limited to the examples described above. For example, the device may include more or fewer components than the components described above. In addition, the processor (1801), the transceiver (1803), and the memory (1805) may be implemented in the form of a single chip.

[0181] The transceiver (1803) is a general term for the receiver of the 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 (1803) may receive a signal, output it to the processor (1801), and transmit the signal output from the processor (1801). In addition, the transceiver (1803) of FIG. 18 may include a transmitter capable of transmitting a signal according to at least one of the communication methods exemplified in the embodiments of FIGS. 4 to 17b or a known proximity communication method, and a receiver capable of receiving the signal. In addition, the transceiver (1803) may receive a signal, output it to the processor (1801), and transmit the signal output from the processor (1801) to the counterpart device via a network. The memory (1805) can store programs and data necessary for the operation of the device according to at least one of the embodiments of FIGS. 4 to 17B. In addition, the memory (1805) can store control information or data included in a signal acquired from the device. The memory (1805) 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.

[0182] In addition, the processor (1801) may control a series of processes so that the device can operate according to at least one of the embodiments of FIGS. 4 to 17B. The processor (1801) may include at least one processor. 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. In the case of software implementation, 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 in 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.

[0183] 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.

[0184] 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.

[0185] 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. A method performed by a first device in an IoT (Internet of Things) system supporting a multi-manager service, A process in which the first device receives a first message including first information about the target IoT device from a second device in relation to the use of the target IoT device registered as a first manager; In response to receiving the first message, a process of transmitting a second message including second information about the first device to the second device; A process of receiving a third message requesting permission to use the target IoT device from the second device; and A method comprising the step of transmitting, in response to receiving the third message, a fourth message including information indicating whether the use is permitted.

2. In paragraph 1, A method further comprising a step of setting the target IoT device to a commissioning mode in which the target IoT device can be used, if the request for use of the target IoT device is permitted.

3. In paragraph 1, It further includes a process of performing an authentication procedure related to allowing the use of the second device and the target IoT device. The above authentication procedure is, Nonce information generated by the first device and provided to the first device; Part or all of the onboarding payload required for use of the above target IoT device; Credential information pre-stored in the first device and the second device, A method performed using at least one of the certificates of the second device including a public key for encryption of the on-boarding payload.

4. In paragraph 1, A method in which, if the request for use of the target IoT device is permitted, the fourth message further including an on-boarding payload required for use of the target IoT device is transmitted from the second device.

5. In paragraph 4, A method in which the above on-boarding payload is encrypted and transmitted using one of a public key included in a certificate of the second device and a session key generated by the first device.

6. In the first device of an IoT (Internet of Things) system that supports multi-manager services, Transmitter and receiver; and The first device receives, from the second device, a first message including first information about the target IoT device, through the transceiver, in relation to the use of the target IoT device registered as the first manager, In response to receiving the first message, through the transceiver, transmit a second message including second information about the first device to the second device, Through the transceiver, a third message requesting permission to use the target IoT device is received from the second device, A first device including a processor configured to transmit, in response to receiving the third message through the transceiver, a fourth message including information indicating whether the use is permitted.

7. A first device according to claim 6, adapted to operate according to any one of the methods of claims 2 to 5.

8. A method performed by a second device in an IoT (Internet of Things) system supporting multi-manager services, A process of transmitting a first request message requesting at least one of first information about at least one first device that is a first manager for at least one IoT device connectable in the IoT system and second information about at least one IoT device connectable to an AP (access point) of the IoT system; In response to the first request message, a process of receiving a first response message including at least one of the first information and the second information from the AP; A process of transmitting a second request message requesting permission to use a target IoT device selected from among at least one connectable IoT device to a first device, which is a first manager of the target IoT device, through the AP; and A method comprising the step of receiving, through the AP, a second response message including information indicating whether the use is permitted from the first device in response to transmission of the second request message.

9. In paragraph 8, A method according to claim 1, wherein the first response message further includes mapping information between first identification information of each of a plurality of IoT devices in the IoT system and second identification information of a first manager for each of the plurality of IoT devices, wherein the mapping information is stored in advance in the AP.

10. In paragraph 8, A method wherein the second request message further includes a certificate of the second device used in an authentication procedure related to allowing use of the target IoT device between the second device and the first device.

11. In paragraph 8, A method in which, if the request for use of the target IoT device is accepted, a second response message further including an on-boarding payload required for use of the target IoT device is received from the second device.

12. In paragraph 8, A method in which the first information about the at least one first device is provided to the second device as list information sorted in order of signal strength among the first devices connected to the AP.

13. In an IoT (Internet of Things) system that supports multi-manager services, in the second device, Transmitter and receiver; and Through the transceiver, a first request message is transmitted to the AP (access point) of the IoT system requesting at least one of first information about at least one first device that is a first manager for at least one IoT device connectable in the IoT system and second information about at least one IoT device connectable, Through the transceiver, in response to the first request message, a first response message including at least one of the first information and the second information is received from the AP, Through the above transceiver, a second request message requesting permission to use a target IoT device selected from among at least one connectable IoT device is transmitted to a first device, which is a first manager of the target IoT device, via the AP, A second device including a processor configured to receive, through the transceiver, a second response message from the first device via the AP, in response to transmission of the second request message, a second response message including information indicating whether the use is permitted.

14. A second device of claim 13 adapted to operate according to any one of the methods of claims 9 to 12.

Images