Device for managing plurality of iot devices, and operation method thereof

Patent metadata

Field	Value
Publication number	US-2025211562-A1
Application number	US-202519078064-A
Country	US
Kind code	A1
Filing date	Mar 12, 2025
Priority date	Sep 20, 2022
Publication date	Jun 26, 2025
Grant date	—

Abstract

An operation method of a server device includes receiving an Internet protocol (IP) address of an Internet-of-Things (IoT) device from the IoT device, identifying another IoT device having a same IP address as the IP address of the IoT device, based on there being no link generated between the IoT device and the another IoT device, generating a link between the IoT device and the another IoT device, based on there being a link generated between the IoT device and the another IoT device, increasing a weight for the link generated between the IoT device and the another IoT device, and generating data on the IoT device and the another IoT device based on the weight for the generated link.

First claim

What is claimed is:

1 . An operation method of a server device, the operation method comprising:
receiving an Internet protocol (IP) address of an Internet-of-Things (IoT) device from the IoT device; identifying another IoT device having an IP address that is the same as the IP address of the IoT device; based on there being no link generated between the IoT device and the another IoT device, generating a link between the IoT device and the another IoT device; based on there being a link generated between the IoT device and the another IoT device, increasing a weight for the link generated between the IoT device and the another IoT device; and generating data on the IoT device and the another IoT device based on the weight for the generated link.

2 . The operation method of claim 1 , further comprising identifying one or more links having a weight equal to or greater than a threshold among a plurality of links generated between a plurality of IoT devices including the IoT device and the another IoT device.

3 . The operation method of claim 2 , further comprising:
identifying at least one link that is connected among the one or more links; and identifying two or more IoT devices connected through the at least one link.

4 . The operation method of claim 3 , further comprising:
generating a group including the two or more IoT devices; and generating an identifier for the group.

5 . The operation method of claim 4 , further comprising generating the two or more IoT devices as the group, based on a preset time having elapsed in the server device.

6 . The operation method of claim 5 , further comprising:
identifying an anchor IoT device having a same IP address while the preset time elapses; and generating the group including the anchor IoT device.

7 . The operation method of claim 4 , further comprising receiving device information of the IoT device from the IoT device,
wherein the device information of the IoT device includes information on an access point (AP) to which the IoT device is connected, identification information of the IoT device, and information on an external device connected to the IoT device.

8 . The operation method of claim 7 , further comprising adding an external device connected to the two or more IoT devices to the group, based on the information on the external device.

9 . The operation method of claim 7 , wherein the device information includes the IP address.

10 . The operation method of claim 9 , further comprising identifying that the IP address of the IoT device changes based on the device information.

11 . A server device comprising:
a communication interface; memory storing at least one instruction; and at least one processor operatively connected to the communication interface and the memory, and configured to execute the at least one instruction, wherein the at least one instruction, when executed by the at least one processor, causes the server device to:
receive an Internet protocol (IP) address of an Internet-of-Things (IoT) device from the IoT device;
identify another IoT device having an IP address that is the same as the IP address of the IoT device;
based on there being no link generated between the IoT device and the other IoT device, generate a link between the IoT device and the another IoT device;
based on there being a link generated between the IoT device and the another IoT device, increase a weight for the link generated between the IoT device and the another IoT device; and
generate data on the IoT device and the another IoT device, based on the weight for the generated link.

12 . The server device of claim 11 , wherein the at least one instruction, when executed by the at least one processor, causes the server device to identify one or more links having a weight equal to or greater than a threshold among a plurality of links generated between a plurality of IoT devices including the IoT device and the another IoT device.

13 . The server device of claim 12 , wherein the at least one instruction, when executed by the at least one processor, causes the server device to identify at least one link that is connected among the one or more links, and identifies two or more IoT devices that are connected via the at least one link.

14 . The server device of claim 13 , wherein the at least one instruction, when executed by the at least one processor, causes the server device to generate a group including the two or more IoT devices, and generate an identifier for the group.

15 . The server device of claim 14 , wherein the at least one instruction, when executed by the at least one processor, causes the server device to, based on a preset time having elapsed in the server device, generate the two or more IoT devices as the group.

16 . The server device of claim 15 , wherein the at least one instruction, when executed by the at least one processor, causes the server device to:
identify an anchor IoT device having a same IP address while the preset time elapses; and generate the group including the anchor IoT device.

17 . The server device of claim 14 , wherein the at least one instruction, when executed by the at least one processor, causes the server device to receive device information of the IoT device from the IoT device,
wherein the device information of the IoT device includes information on an access point (AP) to which the IoT device is connected, identification information of the IoT device, and information on an external device connected to the IoT device.

18 . The server device of claim 17 , wherein the at least one instruction, when executed by the at least one processor, causes the server device to add an external device connected to the two or more IoT devices to the group, based on the information on the external device.

19 . The server device of claim 17 , wherein the device information includes the IP address.

20 . The server device of claim 17 , wherein the at least one instruction, when executed by the at least one processor, causes the server device to identify that the IP address of the IoT device changes based on the device information.

Assignees

• Samsung Electronics Co Ltd

Inventors

• Kim Donghyuk
• Lee Hodong
• Baskar Rajasimhan

Classifications

• H04L61/5007

  Internet protocol [IP] addresses · CPC title

• G16Y40/35

  Management of things, i.e. controlling in accordance with a policy or in order to achieve specified objectives · CPC title

• H04L61/35 Primary

  involving non-standard use of addresses for implementing network functionalities, e.g. coding subscription information within the address or functional addressing, i.e. assigning an address to a function · CPC title

• H04L2101/365

  Application layer names, e.g. buddy names, unstructured names chosen by a user or home appliance name · CPC title

• G16Y10/80

  Homes; Buildings · CPC title