Method and apparatus for controlling device onboarding
The introduction of a commissioning assistance device (CAD) addresses the challenge of device onboarding in IoT environments without a commissioner, enabling efficient and autonomous device registration and integration into the network.
Patent Information
- Application Number
- PCT/KR2023/014994
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-09-27
- Publication Date
- 2025-04-03
AI Technical Summary
In the IoT environment, device onboarding processes are often hindered when a commissioner is absent, as existing technologies lack a robust mechanism for device onboarding without direct human intervention.
The proposed solution involves a commissioning assistance device (CAD) that can perform device onboarding on behalf of a commissioner, even in their absence. This CAD acts as a transmission bridge and controller, receiving requests from commissioners, activating device onboarding functions, and registering devices into the network.
The CAD enables seamless device onboarding in scenarios where a commissioner is not present, ensuring that devices can be registered and integrated into the network efficiently, thereby enhancing the scalability and reliability of IoT systems.
Smart Images

Figure KR2023014994_03042025_PF_FP_ABST
Abstract
Description
Method and device for controlling device onboarding
[0001] The present disclosure relates to a method and apparatus for controlling device onboarding.
[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] As wireless communication systems evolve, the ability to offer a variety of services increases. Therefore, methods for effectively delivering these services are becoming increasingly necessary. For example, a device onboarding procedure can be performed to register an out-of-box (OOTB) device (commissionee) with the network through a commissioner.
[0005] The present disclosure proposes a device onboarding method for registering a device to a network.
[0006] According to one embodiment of the present disclosure, a method for operating a commissioning assist device in a wireless communication system may include: receiving a request message from a commissioner requesting that the commissioning assist device activate a device onboarding function for a device (commissionee) on behalf of the commissioner; transmitting, in response to the request message, a response message to the commissioner including a result code indicating that the commissioning assist device activates the device onboarding function; and performing the device onboarding function for the device.
[0007] According to one embodiment of the present disclosure, a method for operating a commissioner in a wireless communication system may include: transmitting a request message to a commissioning assist device, the request message requesting that the commissioning assist device activate a device onboarding function for a device (commissionee) on behalf of the commissioner; and receiving a response message from the commissioning assist device, the response message including a result code indicating that the commissioning assist device has activated the device onboarding function. At this time, the device onboarding function for the device may be performed by the commissioning assist device.
[0008] According to one embodiment of the present disclosure, a commissioning assist device in a wireless communication system includes a transceiver; and a control unit connected to the transceiver. The control unit can receive a request message from a commissioner requesting that the commissioning assist device activate a device onboarding function for a device (commissionee) on behalf of the commissioner. The control unit can control, in response to the request message, to transmit a response message to the commissioner including a result code indicating that the commissioning assist device has activated the device onboarding function. The control unit can perform the device onboarding function for the device.
[0009] According to one embodiment of the present disclosure, in a wireless communication system, a commissioner includes a transceiver; and a control unit connected to the transceiver. The control unit can control a commissioning assist device to transmit a request message requesting that the commissioning assist device activate a device onboarding function for a device (commissionee) on behalf of the commissioner to the commissioning assist device. The control unit can receive a response message from the commissioning assist device including a result code indicating that the commissioning assist device has activated the device onboarding function. At this time, the device onboarding function for the device can be performed by the commissioning assist device.
[0010] The method and device according to the embodiment of the present disclosure can perform device onboarding for a device even in the absence of an in-home commissioner device.
[0011] FIG. 1A and FIG. 1B are diagrams illustrating a device onboarding procedure according to one embodiment of the present disclosure.
[0012] FIG. 2 is a diagram illustrating a process by which a commissioner obtains a certificate from a server according to one embodiment of the present disclosure.
[0013] FIG. 3A is a diagram illustrating a process in which a commissioner performs a device onboarding procedure according to one embodiment of the present disclosure.
[0014] FIG. 3b is a diagram illustrating a process in which a commissioning assist device performs a device onboarding procedure on behalf of a commissioner according to one embodiment of the present disclosure.
[0015] FIG. 4 is a diagram illustrating a process for searching for a commissioning assist device according to one embodiment of the present disclosure.
[0016] FIG. 5 is a diagram illustrating a process for registering a commissioning assist device according to one embodiment of the present disclosure.
[0017] FIG. 6 is a diagram illustrating a process for setting up function delegation with a commissioning assist device according to one embodiment of the present disclosure.
[0018] FIG. 7 is a diagram illustrating a process of performing a delegated function as a commissioning assist device according to one embodiment of the present disclosure.
[0019] FIG. 8 is a diagram illustrating a process for disabling a delegation function of a commissioning assist device according to one embodiment of the present disclosure.
[0020] FIG. 9A and FIG. 9B are diagrams illustrating a process of activating or deactivating a commissioning assist device through a certificate-based authentication method according to one embodiment of the present disclosure.
[0021] FIG. 10A and FIG. 10B are diagrams illustrating a process of activating or deactivating a commissioning assist device through a certificate-based authentication method according to one embodiment of the present disclosure.
[0022] FIG. 11 illustrates the structure of a commissioning assist device according to one embodiment of the present disclosure.
[0023] FIG. 12 illustrates the structure of a commissioner according to one embodiment of the present disclosure.
[0024] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the attached drawings.
[0025] In describing the embodiments, descriptions of technical details that are well known in the technical field to which the present disclosure pertains and are not directly related to the present disclosure will be omitted. This is to convey the gist of the present disclosure more clearly without obscuring it by omitting unnecessary explanations.
[0026] For the same reason, some components in the attached drawings are exaggerated, 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.
[0027] 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 together 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 embodiments of the present disclosure are provided only to make the present disclosure complete and to fully inform those skilled in the art of the scope of the disclosure, and the present disclosure is defined only by the scope of the claims. Like reference numerals refer to like elements throughout the specification.
[0028] At this time, it will be understood that each block of the processing flowchart drawings and combinations of the flowchart drawings 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 flowchart 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 flowchart 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, so that 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 be able to provide steps for performing the functions described in the flowchart block(s).
[0029] 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.
[0030] Here, the term '~ unit' used in the present embodiment means software or hardware components such as FPGA (Field Programmable Gate Array) or ASIC (Application Specific Integrated Circuit), and the '~ unit' performs certain roles. However, the '~ unit' is not limited to software or hardware. The '~ unit' may be configured to be on an addressable storage medium and may be configured to play one or more processors. Accordingly, according to some embodiments, the '~ unit' includes components such as software components, object-oriented software components, class components, and task components, processes, functions, properties, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functions 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'. Additionally, the components and '~parts' may be implemented to activate one or more CPUs within the device or secure multimedia card. Furthermore, according to some embodiments, the '~parts' may include one or more processors.
[0031] The term 'terminal' or 'device' used herein may refer to a mobile station (MS), user equipment (UE), user terminal (UT), wireless terminal, access terminal (AT), terminal, subscriber unit (SS), subscriber station (SS), wireless device, wireless communication device, wireless transmit / receive unit (WTRU), mobile node, mobile, or other terms. Various embodiments of the terminal may include a cellular telephone, a smart phone having a wireless communication function, a personal digital assistant (PDA) having a wireless communication function, a wireless modem, a portable computer having a wireless communication function, a photographing device such as a digital camera having a wireless communication function, a gaming device having a wireless communication function, a music storage and playback home appliance having a wireless communication function, an internet home appliance capable of wireless internet access and browsing, as well as portable units or terminals integrating combinations of such functions. In addition, the terminal may include, but is not limited to, an M2M (Machine to Machine) terminal, an MTC (Machine Type Communication) terminal / device. In this specification, the terminal may also be referred to as an electronic device or simply a device.
[0032] 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] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. While the embodiments of the present disclosure will be described below using a communication system for device onboarding as an example, the embodiments of the present disclosure can also be applied to other communication systems with similar technical backgrounds or characteristics. Accordingly, the embodiments of the present disclosure can be applied to other communication systems with some modifications, as determined by a person skilled in the art, without significantly departing from the scope of the present disclosure.
[0034] Additionally, when describing the present disclosure, detailed descriptions of related 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 contents of this specification.
[0035] In addition, when explaining the present disclosure, if it is determined that a specific description of a related public notice function or configuration may unnecessarily obscure the gist of the present disclosure, the detailed description is omitted.
[0036] Various embodiments of the present disclosure are described below with reference to the attached drawings.
[0037] In the present disclosure, device onboarding may be a process of registering a device (commissionee) through a commissioner to enter (or register) an out-of-box (OOTB) state device (commissionee) into a network (or operational network).
[0038] Each of the commissioner and the commissionee may be implemented as an electronic device. The electronic device according to one embodiment of the present disclosure may take various forms. The electronic device may include, for example, a portable communication device (e.g., a smartphone), a computer device, a portable multimedia device, a portable medical device, a camera, a wearable device, a home appliance, or wireless earphones. The electronic device according to one embodiment of the present disclosure is not limited to the aforementioned devices.
[0039] During device onboarding, the commissioner may perform at least one of the following actions: 1) to 3).
[0040] 1) Device attestation
[0041] 2) Issuing and / or obtaining and delivering an operational certificate (OC) to establish a certificate-based secure session with the device (commissionee); The commissioner issues the OC directly or requests a trusted root certificate authority (CA) to obtain the OC and then delivers it to the device (commissionee).
[0042] 3) Sharing multiple pieces of information (e.g., network configuration information and ACL (access control list)) for device registration of the device (commissionee)
[0043] FIG. 1A and FIG. 1B are diagrams illustrating a device onboarding procedure according to one embodiment of the present disclosure.
[0044] In FIGS. 1A and 1B , a commissioner may perform a device onboarding procedure for a commissionee by exchanging messages with an administrator. In one embodiment, the administrator may be implemented as an electronic device or a server.
[0045] In Action 101, the commissioner may verify (or modify) at least one of the date, time, timezone, regulatory information, and fabric information available.
[0046] In operation 102, a commissioner may discover a device (commissionee) through device discovery and establish a commissioning channel with the device (commissionee). In one embodiment, all messages may be exchanged through the commissioning channel.
[0047] In operation 103, the commissioner may establish a security setup with the commissionee (e.g., using Password Authenticated Session Establishment (PASE)). In one embodiment, all messages may be encrypted with a PACE-derived encryption key. At this time, implicit administer privileges may be initiated.
[0048] In operation 104, a fail-safe timer can be set between the commissioner and the commissionee.
[0049] In operation 105, configuration information (e.g., UTC (universal time coordinated) time, regulatory information) can be established between the commissioner and the commissionee.
[0050] In operation 106, the commissioner can verify the authenticity of the device (commissionee attestation).
[0051] In operation 107, the commissioner and the commissionee can exchange an operational certificate signing request (CSR).
[0052] In operation 108, the commissioner can either directly generate (or issue) an operational certificate (OC) (or certificate) or obtain an operational certificate from another device. In one embodiment, the commissioner can request a Trusted Root CA to obtain an operational certificate and then transmit the operational certificate to the device (commissionee).
[0053] In operation 109, configuration information for operating certificates between the commissioner and the commissionee can be set.
[0054] In operation 110, configuration information for ACL between the commissioner and the commissionee can be set.
[0055] In operation 111, configuration information for the operational network between the commissioner and the commissionee can be set.
[0056] In operation 112, at least one of the commissioner and the commissionee may trigger the commissionee to join the operating network.
[0057] In one embodiment, an administrator may act as a commissioner. All messages between the administrator and the commissionee may then be exchanged via the operational network.
[0058] In operation 113, the administrator and the commissionee can perform operational discovery through the operational network.
[0059] In operation 114, the administrator can establish a security setup with the commissionee (e.g., a security setup using Certificate Authenticated Session Establishment (CASE)). In one embodiment, all messages can be encrypted with a CACE-derived encryption key. At this time, implicit administer privileges can be initiated.
[0060] In operation 115, the administrator and the commissionee may exchange a commissioning completion message. At this point, commissioning may be completed successfully. The commissioning channel may be terminated, and the implicit administer privilege may be terminated.
[0061] FIG. 2 is a diagram illustrating a process by which a commissioner obtains a certificate from a server according to one embodiment of the present disclosure.
[0062] Referring to FIG. 2, in operation 201, a commissioner may obtain an operating certificate (OC) from a cloud server (or Root CA). In one embodiment, an application for device onboarding may be executed within the commissioner.
[0063] In one embodiment, the commissioner must know information about the cloud server (or Root CA) in advance (e.g., cloud server URL) before requesting an OC from the cloud server (or Root CA), and must also have access to the cloud server (or Root CA).
[0064] In operation 203, a commissioner can discover a device (commissionee) through device discovery and form a commissioning channel with the device (commissionee).
[0065] In operation 205, the commissioner can verify the authenticity of the device (commissionee attestation).
[0066] When the commissioner completes verification of the device (commissionee), the commissioner may provide security and network configuration information to the device (commissionee) in operation 207. In one embodiment, the commissioner may transmit an OC obtained through a cloud server (or Root CA) to the device (commissionee). In one embodiment, the commissioner may transmit at least one piece of information for device registration (e.g., network configuration information, ACL information) to the device (commissionee). Thereafter, the device (commissionee) may perform device registration on the network based on the obtained information.
[0067] In one embodiment, a commissioner may be connected to a Wi-Fi access point (AP). In operation 209, the Wi-Fi AP and the device (commissionee) may establish a network connection and complete commissioning.
[0068] On the other hand, some devices support only limited features due to limited resources (e.g., limited memory, limited battery, or limited display). Furthermore, some devices may not support all features depending on their version (e.g., devices that do not support certain network protocols due to hardware or software specifications). Furthermore, some devices may not support all features based on the manufacturer's intentions (e.g., devices that support only the bare minimum features to reduce development resources / costs, or existing devices that have already been released with older specifications).
[0069] If your device only supports limited features, there is a possibility that certain features may be temporarily limited in your home due to device mobility, compatibility issues may exist with other devices depending on the pairing technology supported by the device, and resource limitations may result in limited performance for certain features.
[0070] The present disclosure proposes a commissioning assist device (CAD) that delegates the functions of a commissioner and processes them on his behalf. The CAD can support protocols that delegate specific functions of the commissioner and then process them on his behalf.
[0071] In one embodiment, the commissioning assistant device (CAD) may be implemented as a standalone device or as an additional component of an existing device that implements the commissioning assistant function. The existing device may be implemented as at least one of a Wi-Fi AP, a speaker, a TV, and an ST Hub (SmartThings station).
[0072] In one embodiment, the commissioning assistant device (CAD) may pre-implement multiple functions, but additional steps may be required to activate and use the actual delegated functions. In one embodiment, the default state for multiple functions that can be implemented in the commissioning assistant device (CAD) may be disabled.
[0073] In one embodiment, the commissioning assistant device (CAD) may enable a specific function only when a commissioner requests the use of that function. In one embodiment, when receiving a request for function delegation, the CAD may receive the information necessary to delegate the function from the commissioner and perform the function on his behalf.
[0074] FIG. 3A is a diagram illustrating a process in which a commissioner performs a device onboarding procedure according to one embodiment of the present disclosure.
[0075] Referring to Figure 3a, a Wi-Fi AP not connected to a Commissioning Assistant Device (CAD) may be connected to a commissioner and a non-commissioner via Wi-Fi. The home commissioner can directly perform device onboarding for the commissionee.
[0076] However, if the home commissioner is absent, device onboarding for the commissionee may not be possible.
[0077] FIG. 3b is a diagram illustrating a process in which a commissioning assist device performs a device onboarding procedure on behalf of a commissioner according to one embodiment of the present disclosure.
[0078] Referring to FIG. 3b, a non-commissioner associated with a Wi-Fi AP may be a commissioning assistant device (CAD) delegated with device onboarding functionality by a commissioner.
[0079] In the absence of the home commissioner, a non-commissioner may act as a CAD to perform device onboarding for the commissionee.
[0080] The commissioning assist protocol proposed in the present disclosure may be composed of at least one of steps 1 to 5 below.
[0081] Step 1: Retrieving the Commissioning Aid (CAD) (Figure 4)
[0082] Step 2: Pre-configuration process to register the retrieved CAD with the Trusted Root-CA (Figure 5)
[0083] Step 3: Setting up CAD for delegation of functions (Figure 6)
[0084] Step 4: Performing actions for functions delegated as CAD (Figure 7)
[0085] Step 5: Disable the Delegation Feature in CAD (Figure 8)
[0086] Specific descriptions of each of the above steps 1 to 5 are provided below in FIGS. 4 to 8, respectively.
[0087] FIG. 4 is a diagram illustrating a process for searching for a commissioning assist device according to one embodiment of the present disclosure.
[0088] A search procedure for new CADs may be required to utilize the commissioning assistance feature. Upon discovering a new CAD, the commissioner can send a request message to the CAD to obtain feature information it supports.
[0089] Referring to FIG. 4, in operation 401, a commissioner may perform a scan operation for CAD. In one embodiment, the commissioner may search for devices with CAD capabilities (e.g., CAD device type, indicators in messages) through device discovery (e.g., vendor specific IEs in Beacon or (Probe) Response messages, etc.).
[0090] When a CAD is found, in action 403, the commissioner may send a request message to the CAD requesting CAD Supported Feature information. In one embodiment, a first parameter (“From”) in the request message may include an identifier of a transmitting device of the request message (Commissioner ID), and a second parameter (“To”) in the request message may include an identifier of a receiving device of the request message (Commissioning Assist Device ID).
[0091] In operation 405, the CAD may transmit a response message to the request message to the commissioner. In one embodiment, a first parameter (“From”) in the response message may include an identifier of a transmitting device of the response message (Commissioning Assist Device ID), and a second parameter (“To”) in the response message may include an identifier of a receiving device of the request message (Commissioner ID). In one embodiment, the response message may include a Supporting Features List supported by the CAD. In one embodiment, the Supporting Features List supported by the CAD may include device onboarding, always-on discovery, and various other functions.
[0092] FIG. 5 is a diagram illustrating a process for registering a commissioning assist device according to one embodiment of the present disclosure.
[0093] A pre-configuration process may be required to register the discovered CAD with the Trusted Root CA (or cloud server). In one embodiment, the commissioner may request access to the CAD in advance to allow the CAD access to the Trusted Root CA. That is, the CAD may request and / or register access to the Trusted Root CA for the CAD to perform device onboarding on behalf of the commissioner. After the CAD is authenticated by the Trusted Root CA through the commissioner, the CAD may directly access the Root CA.
[0094] Referring to FIG. 5, in operation 501, a commissioner may register a CAD to access the Trusted Root-CA on behalf of the commissioner during the device onboarding process.
[0095] In step 503, the commissioner may transmit a first message to the CAD regarding the device registration result of the CAD. In step 505, the CAD may transmit a response message (OK message) to the first message to the commissioner.
[0096] If the CAD is successfully registered with the Trusted Root CA, the CAD can directly access the Trusted Root CA in step 507. The Trusted Root CA can then perform a validation check on the CAD. In one embodiment, a certificate and / or token may be utilized for validation checks between the Trusted Root CA and the CAD. In step 509, the Trusted Root CA may send a response message (OK message) to the CAD.
[0097] FIG. 6 is a diagram illustrating a process for setting up function delegation with a commissioning assist device according to one embodiment of the present disclosure.
[0098] A commissioner can delegate commissioning functions to a CAD. After the CAD approves the request for delegation of commissioning functions, the CAD can perform device onboarding on behalf of the commissioner.
[0099] Referring to Figure 6, a CAD may have (or acquire) access to a Trusted Root CA. In operation 601, a commissioner may send a request message to the CAD to activate the commissioner role on behalf of the commissioner.
[0100] In one embodiment, the first parameter (“From”) in the request message may include an identifier of the device transmitting the request message (Commissioner ID), and the second parameter (“To”) in the request message may include an identifier of the device receiving the request message (Commissioning Assist Device ID). In one embodiment, the request message may include information about a delegated feature (e.g., device onboarding).
[0101] In one embodiment, the request message may include a binary value (e.g., “Enable”: True) that determines whether to activate an assistant functionality (e.g., device onboarding). In one embodiment, the request message may include additional information for operating the activated assistant functionality. The additional information may include at least one of address information (e.g., IP address, URL) for the Trusted Root CA, a certificate, and a token for the CAD.
[0102] In action 603, the CAD may send a response message containing a result code to the commissioner.
[0103] In one embodiment, the first parameter (“From”) in the response message may include an identifier of a device transmitting the response message (Commissioning Assist Device ID), and the second parameter (“To”) in the response message may include an identifier of a device receiving the response message (Commissioner ID). In one embodiment, the response message may include information about a delegated feature (e.g., device onboarding).
[0104] In one embodiment, the response message may include a binary value (e.g., “Enable”: True) that determines whether to enable an assistant functionality (e.g., device onboarding). In one embodiment, the response message may include information about a result code (e.g., text or numbers indicating the reason for the activation result).
[0105] Afterwards, CAD can perform device onboarding on behalf of the commissioner.
[0106] FIG. 7 is a diagram illustrating a process of performing a delegated function as a commissioning assist device according to one embodiment of the present disclosure.
[0107] Referring to FIG. 7, CAD can perform device onboarding on behalf of a commissioner.
[0108] In operation 701, the CAD may send an announcement message to the commissioner to notify the event information. In operation 703, the commissioner may send an ACK message to the CAD in response to the announcement message.
[0109] In one embodiment, the first parameter (“From”) in the notification message may include an identifier of the device sending the notification message (Commissioning Assist Device ID), and the second parameter (“To”) in the notification message may include an identifier of the device receiving the notification message (Commissioner ID). In one embodiment, the notification message may include information about a delegated feature (e.g., device onboarding).
[0110] In one embodiment, the notification message may include a binary value (e.g., “Enable”: True) that determines whether to enable the assistant functionality request. In one embodiment, the notification message may include additional information (e.g., an event code) related to the enabled delegate functionality.
[0111] In one embodiment, when an event occurs for a delegated function (e.g., device onboarding is completed), the CAD may transmit information about the event to the commissioner, including additional information about the delegated function being performed. In one embodiment, the event code may be expressed as a numeric code or text such as "Complete device onboarding."
[0112] FIG. 8 is a diagram illustrating a process for disabling a delegation function of a commissioning assist device according to one embodiment of the present disclosure.
[0113] Referring to FIG. 8, in operation 801, a commissioner may send a request message to the CAD instructing it to deactivate its commissioner role.
[0114] In one embodiment, a first parameter (“From”) in the request message may include an identifier of a device transmitting the request message (Commissioner ID), and a second parameter (“To”) in the request message may include an identifier of a device receiving the request message (Commissioning Assist Device ID).
[0115] In one embodiment, the request message may include information regarding a delegated feature (e.g., device onboarding). In one embodiment, the request message may include a binary value (e.g., “Enable”:False) indicating that the assistant functionality request should be disabled.
[0116] In action 803, the CAD may send a response message to the commissioner with the result of the disablement.
[0117] In one embodiment, a first parameter (“From”) in the response notification message may include an identifier of a device sending the response message (Commissioning Assist Device ID), and a second parameter (“To”) in the response message may include an identifier of a device receiving the response message (Commissioner ID). In one embodiment, the response message may include information about a delegated feature (e.g., device onboarding).
[0118] In one embodiment, the response message may include a binary value (e.g., “Enable”: False) indicating that the assistant functionality request is to be disabled. In one embodiment, the response message may include additional information related to the enabled delegate functionality (e.g., an event code).
[0119] Afterwards, delegated functions (e.g., device onboarding) can be disabled in CAD.
[0120] FIG. 9A and FIG. 9B are diagrams illustrating a process of activating or deactivating a commissioning assist device through a certificate-based authentication method according to one embodiment of the present disclosure.
[0121] Referring to FIG. 9A, in operation 901, the commissioner may scan the CAD through device discovery. If a new CAD is discovered, in operation 902, the commissioner may request information about the new CAD from the CAD.
[0122] In operation 903, the CAD may transmit information about the CAD to the commissioner. In one embodiment, the information about the CAD may include at least one of a CAD Device ID and a CAD Certificate. In one embodiment, for the Matter standard, a Node Operational Certificate (NOC) may be used as the CAD Certificate.
[0123] In operation 904, the commissioner may transmit a request message to the cloud server to register the CAD as a commissioner. In one embodiment, the request message may include at least one of a CAD device ID and a CAD certificate. In one embodiment, the cloud server may verify the authenticity of the CAD certificate and then register the CAD certificate with the cloud server.
[0124] In action 905, the cloud server may send a response message to the commissioner that includes a result code for registration and a CAD Device ID.
[0125] In operation 906, the commissioner may send a request message to the CAD to activate the CAD's "device onboarding" function on behalf of the commissioner. In one embodiment, the request message may include at least one of a CAD Device ID, a result code, and address information of a cloud server.
[0126] In operation 907, the CAD may send a message to the commissioner indicating that it is activating the CAD functionality in response to the above request message.
[0127] A CAD can be delegated the role of commissioner and discover a commissionee to perform device onboarding on behalf of the commissioner in action 908.
[0128] Referring to FIG. 9B, if a device (commissionee) to perform device onboarding is discovered, in operation 909, the CAD may perform device onboarding on behalf of the commissioner. In one embodiment, the CAD may perform onboarding on the device (commissionee) using the acquired operating certificate (OC). Thereafter, the CAD may complete onboarding on the device (commissionee).
[0129] In operation 909-0, the cloud server authenticates the CAD certificate and establishes a secure channel between the cloud server and the CAD. In operation 909-1, the CAD can request an operating certificate (OC) for the device (commissionee) from the cloud server. In operation 909-2, the cloud server can transmit the operating certificate (OC) for the device (commissionee) to the CAD.
[0130] In action 910, the CAD may send at least one notification message to the commissioner for an event indicating that onboarding for the device (commissionee) has been completed.
[0131] In a 911 operation, the commissioner may send a request message to the CAD requesting that the CAD's “device onboarding” feature be disabled.
[0132] In Action 912, the CAD may send a response message to the Commissioner containing a result code indicating that the CAD's auxiliary functions have been disabled. The CAD's Commissioner role may then be disabled.
[0133] FIG. 10A and FIG. 10B are diagrams illustrating a process of activating or deactivating a commissioning assist device through a certificate-based authentication method according to one embodiment of the present disclosure.
[0134] Referring to Figure 10a, in operation 1001, the commissioner may scan the CAD through device discovery. If a new CAD is discovered, in operation 1002, the commissioner may request information about the new CAD from the CAD.
[0135] In operation 1003, the CAD may transmit information about the CAD to a commissioner. In one embodiment, the information about the CAD may include at least one of a CAD Device ID and additional CAD information.
[0136] In operation 1004, the commissioner may send a request message to the cloud server to register the CAD as a commissioner. In one embodiment, the request message may include at least one of a CAD device ID and additional CAD information. The cloud server may then issue a token for the CAD.
[0137] In action 1005, the cloud server may send a response message to the commissioner that includes a result code for registration, a CAD Device ID, and a token issued for the CAD.
[0138] In operation 1006, the commissioner may send a request message to the CAD to activate the CAD's "device onboarding" function on behalf of the commissioner. In one embodiment, the request message may include at least one of a CAD Device ID, a token issued to the CAD, a result code, and address information of a cloud server.
[0139] In action 1007, the CAD may send a message to the commissioner indicating that it is activating the CAD functionality in response to the above request message.
[0140] A CAD can be delegated the role of commissioner and discover devices (commissionees) to perform device onboarding on behalf of the commissioner in action 1008.
[0141] Referring to FIG. 10b, if a device (commissionee) to perform device onboarding is discovered, in operation 1009, the CAD may perform device onboarding on behalf of the commissioner. In one embodiment, the CAD may perform onboarding on the device (commissionee) using the acquired operating certificate (OC). Thereafter, the CAD may complete onboarding on the device (commissionee).
[0142] In operation 1009-0, the cloud server authenticates the token for the CAD and establishes a secure channel between the cloud server and the CAD. In operation 1009-1, the CAD can request an Operation Certificate (OC) for the device (commissionee) from the cloud server. In operation 1009-2, the cloud server can send the Operation Certificate (OC) for the device (commissionee) to the CAD.
[0143] In action 1010, the CAD may send at least one notification message to the commissioner for an event indicating that onboarding for the device (commissionee) has been completed.
[0144] In Action 1011, the commissioner may send a request message to the CAD requesting that the CAD's “device onboarding” feature be disabled.
[0145] In Action 1012, the CAD may send a response message to the Commissioner containing a result code indicating that the CAD's auxiliary functions have been disabled. The CAD's Commissioner role may then be disabled.
[0146] FIG. 11 illustrates the structure of a commissioning assist device according to one embodiment of the present disclosure.
[0147] Referring to FIG. 11, a commissioning assist device (CAD) may include a transceiver (1110), a control unit (1120), and a storage unit (1130). In the present disclosure, the control unit (1120) may be defined as a circuit or an application-specific integrated circuit, or at least one processor. In the present disclosure, the transceiver (1110) may also be referred to as a transceiver or a transceiver.
[0148] The transceiver (1110) can transmit and receive signals with other devices. The transceiver (1110) can transmit and receive messages and / or information with, for example, a commissioner or a server.
[0149] The control unit (1120) can control the overall operation of the commissioning assist device according to the embodiment proposed in the present disclosure. For example, the control unit (1120) can control the signal flow between each block to perform operations according to the flowchart described above. Specifically, the control unit (1120) can control the operation of the commissioning assist device described with reference to FIGS. 1 to 10b, for example.
[0150] In one embodiment, the control unit (1120) may receive a request message from a commissioner requesting that the commissioning assistant activate a device onboarding function for a device (commissionee) on behalf of the commissioner. In one embodiment, the request message may include an identifier of a device transmitting the request message, an identifier of a device receiving the request message, information about the device onboarding function, and an indicator of whether to activate the device onboarding function. In one embodiment, the request message may further include at least one of information about a cloud server for registering the commissioning assistant to perform the device onboarding function on behalf of the commissioner, a certificate for the commissioning assistant, or a token for the commissioning assistant.
[0151] In one embodiment, the control unit (1120) may control the commissioning assistant device to transmit a response message to the commissioner in response to the request message, the response message including a result code indicating that the device onboarding function is activated. In one embodiment, the response message may further include at least one of an identifier of a device transmitting the response message, an identifier of a device receiving the response message, information regarding the device onboarding function, an indicator of whether to activate the device onboarding function, and a result code related to activation of the device onboarding.
[0152] In one embodiment, the control unit (1120) may perform the device onboarding function for the device.
[0153] In one embodiment, the control unit (1120) may receive a request message from the commissioner instructing the commissioning assistant to deactivate the device onboarding function. In one embodiment, the control unit (1120) may control, in response to the request message, to transmit a response message containing event information regarding the device onboarding to the commissioner.
[0154] In one embodiment, the authenticity of the commissioning assistant device can be verified at the server based on a certificate for the commissioning assistant device.
[0155] In one embodiment, a token may be issued to the commissioning assistant device by a server that registers the commissioning assistant device to act as a commissioner.
[0156] The storage unit (1130) can store at least one of the information transmitted and received through the transmission and reception unit (1110) and the information generated through the control unit (1120). For example, the storage unit (1130) can store the information and data transmitted and received with reference to FIGS. 1 to 10b, for example.
[0157] FIG. 12 illustrates the structure of a commissioner according to one embodiment of the present disclosure.
[0158] Referring to FIG. 12, the commissioner may include a transceiver (1210), a control unit (1220), and a storage unit (1230). In the present disclosure, the control unit may be defined as a circuit or an application-specific integrated circuit, or at least one processor. In the present disclosure, the transceiver (1210) may also be referred to as a transceiver or a transceiver.
[0159] The transceiver (1210) can transmit and receive signals with other devices. The transceiver (1210) can transmit and receive messages and / or information with, for example, a commissioning assist device or a server.
[0160] The control unit (1220) can control the overall operation of the commissioner according to the embodiment proposed in the present disclosure. For example, the control unit (1220) can control the signal flow between each block to perform operations according to the flowchart described above. Specifically, the control unit (1220) can control the operation of the commissioner described with reference to FIGS. 1 to 10b, for example.
[0161] In one embodiment, the control unit (1220) may control a commissioning assist device to transmit a request message to the commissioning assist device, requesting the commissioning assist device to activate a device onboarding function for a device (commissionee) on behalf of the commissioner. In one embodiment, the request message may include an identifier of a device transmitting the request message, an identifier of a device receiving the request message, information about the device onboarding function, and an indicator of whether to activate the device onboarding function. In one embodiment, the request message may further include at least one of information about a cloud server for registering that the commissioning assist device performs the device onboarding function on behalf of the commissioner, a certificate for the commissioning assist device, or a token for the commissioning assist device.
[0162] In one embodiment, the control unit (1220) may receive a response message from the commissioning assistant device that includes a result code indicating that the commissioning assistant device has activated the device onboarding function. In one embodiment, the response message may further include at least one of an identifier of a device transmitting the response message, an identifier of a device receiving the response message, information regarding the device onboarding function, an indicator of whether to activate the device onboarding function, and a result code related to activation of the device onboarding.
[0163] In one embodiment, the control unit (1220) may control the server to transmit a registration message requesting that the commissioning auxiliary device perform the commissioner role, including a certificate for the commissioning auxiliary device. At this time, the authenticity of the commissioning auxiliary device may be verified by the server based on the certificate.
[0164] In one embodiment, the control unit (1220) may control the commissioning assistant device to transmit a registration message to the server requesting that the commissioning assistant device perform the commissioner role. In one embodiment, the control unit (1220) may receive a response message from the server that includes a token for the commissioning assistant device issued by the server.
[0165] The storage unit (1230) can store at least one of the information transmitted and received through the transceiver unit (1210) and the information generated through the control unit (1220). For example, the storage unit (1230) can store information and data related to device onboarding, for example, referring to FIGS. 1 to 10b.
[0166] In the specific embodiments of the present invention described above, components included in the invention 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 invention is not limited to singular or plural components. Even components expressed in the plural form may be composed of singular elements, or even components expressed in the singular form may be composed of plural elements.
[0167] While the detailed description of the present invention has described specific embodiments, it is clear that various modifications are possible without departing from the scope of the present invention. Therefore, the scope of the present invention should not be limited to the described embodiments, but should be defined not only by the scope of the following claims but also by equivalents thereof.
Claims
1. In a method of operating a commissioning assist device in a wireless communication system, An action of receiving a request message from the commissioner requesting the commissioning assistant to activate a device onboarding function for a device (commissionee) on behalf of the commissioner; In response to said request message, the commissioning assistant transmits to the commissioner a response message including a result code indicating that the device onboarding function has been activated; and A method characterized by comprising an action for performing said device onboarding function for said device.
2. In paragraph 1, the request message is: A method characterized by comprising an identifier of a device transmitting the request message, an identifier of a device receiving the request message, information regarding the device onboarding function, and an indicator of whether to activate the device onboarding function.
3. In the second paragraph, the request message is: A method characterized in that the commissioning assistant further comprises at least one of information for a cloud server for registering that the commissioning assistant performs the device onboarding function on behalf of the commissioner, a certificate for the commissioning assistant, or a token for the commissioning assistant.
4. In paragraph 1, the response message is: A method characterized in that it further comprises at least one of an identifier of a device transmitting the response message, an identifier of a device receiving the response message, information regarding the device onboarding function, an indicator of whether to activate the device onboarding function, and a result code related to activation of the device onboarding.
5. In paragraph 1, An action of receiving a request message from said commissioner instructing said commissioning assistant to disable said device onboarding function; and A method further comprising the action of transmitting, in response to said request message, a response message including event information for said device onboarding to said commissioner.
6. In paragraph 5, A method characterized in that the authenticity of the commissioning auxiliary device is verified on a server based on a certificate for the commissioning auxiliary device.
7. In paragraph 1, A method characterized in that a token is issued to the commissioning assistant device by a server that registers the commissioning assistant device to perform the role of a commissioner.
8. In the operation method of a commissioner in a wireless communication system, An action of transmitting a request message to a commissioning assist device requesting that the commissioning assist device activate a device onboarding function for a device (commissionee) on behalf of the commissioner; and comprising the action of receiving a response message from the commissioning assistant device including a result code indicating that the commissioning assistant device has activated the device onboarding function; A method characterized in that the device onboarding function for the device is performed by the commissioning auxiliary device.
9. In paragraph 8, the request message is: A method characterized by comprising an identifier of a device transmitting the request message, an identifier of a device receiving the request message, information regarding the device onboarding function, and an indicator of whether to activate the device onboarding function.
10. In paragraph 9, the request message is: A method characterized in that the commissioning assistant further comprises at least one of information for a cloud server for registering that the commissioning assistant performs the device onboarding function on behalf of the commissioner, a certificate for the commissioning assistant, or a token for the commissioning assistant.
11. In paragraph 8, the response message is: A method characterized in that it further comprises at least one of an identifier of a device transmitting the response message, an identifier of a device receiving the response message, information regarding the device onboarding function, an indicator of whether to activate the device onboarding function, and a result code related to activation of the device onboarding.
12. In paragraph 8, further comprising an action of transmitting a registration message to a server, the registration message including a certificate for said commissioning assistant device, requesting that said commissioning assistant device perform the role of a commissioner; A method characterized in that the authenticity of the commissioning auxiliary device is verified by the server based on the certificate.
13. In paragraph 8, An action of transmitting a registration message to the server requesting that the above commissioning assistant device perform the role of a commissioner; and A method further comprising the action of receiving a response message from the server, the response message including a token for the commissioning assistant device issued by the server.
14. In a commissioning assist device in a wireless communication system, Transmitter and receiver; and It includes a control unit connected to the above transmitter and receiver, and the control unit, The above commissioning assistant device receives a request message from the commissioner requesting that the commissioning assistant device activate the device onboarding function for the device (commissionee) on behalf of the commissioner, In response to the request message, control the commissioning assistant to transmit a response message to the commissioner, the response message including a result code indicating that the device onboarding function has been activated; A commissioning assistant device characterized by performing the device onboarding function for the device.
15. In the wireless communication system, for the commissioner, Transmitter and receiver; and It includes a control unit connected to the above transmitter and receiver, and the control unit, Controlling the commissioning assist device to transmit a request message to the commissioning assist device requesting the commissioner to activate a device onboarding function for the device (commissionee), Receive a response message from the commissioning assistant device including a result code indicating that the commissioning assistant device has activated the device onboarding function; A commissioner characterized in that the device onboarding function for the device is performed by the commissioning auxiliary device.
Citation Information
Patent Citations
User terminal device, Internet of Things control method, computer program and storage medium therefor
KR1020160149751A
A faucet with a direct connection structure
KR1020250042476A
Distribution hub for internet-of-things data
US20220150309A1
Cloud-to-device mediator service from services definition
US20220377069A1
Method and system for self-onboarding of IoT devices
WO2023054935A1