# US 2026/0246697 A1 · Systems and Methods for Dynamic Reconfiguration of Networks of Internet of Things (IoT) Devices

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2026/0246697 A1
- Document ID: US20260246697A1
- Status: Published application
- Kind: A1
- Application number: 19/056,330
- Filed: 2025-02-18
- Published: 2026-08-20
- Earliest claimed: 2025-02-18
- Assignees: Walmart Apollo, LLC
- Applicants: Walmart Apollo, LLC
- Inventors: Greg Passmore; Paul Briskey; Justin Rigling
- Web page: https://patentgrep.com/patent/US20260246697A1

## CPC

- H04L 41/0823: characterised by the purposes of a change of settings, e.g. optimising configuration for enhancing reliability (for optimising operational conditions of wireless networks H04W24/02)
- H04L 67/10: in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46)
- H04L 67/565: Conversion or adaptation of application format or content (adding application control or application functional data H04L67/561)
- H04L 69/40: for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection (management of faults, events, alarms or notifications in data switching networks H04L41/06)
- H04W 4/70: Services for machine-to-machine communication [M2M] or machine type communication [MTC]
- H04W 4/80: Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication
- H04L 67/12: specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

The present disclosure, in various embodiments, provides a system, method, and device for dynamic reconfiguration of networks of Internet of Things (IoT) devices. The method can include collecting network health data and gateway health data from a source gateway and transmitting a handoff signal to a source gateway. The handoff signal can initiate a device assignment routine when at least one trigger criterion is met, such as of a load-balancing event, a failover event, a roaming event, or a user-initiated event. A target gateway can be determined based on selection parameters and can receive relevant device details from the source gateway to enable the IoT device to connect with the target gateway.

## Claims

### Claim 1

A sitewide controller device configured to:
collect network health data and gateway health data from a source gateway;
transmit a device assignment signal to a source gateway, the device assignment signal configured to initiate a device assignment routine when at least one device assignment trigger criteria is satisfied at the source gateway, wherein the device assignment trigger comprises at least one of a load-balancing event, a failover event, a roaming event, or a user-initiated event;
determine a target gateway based on a plurality of selection parameters within the device assignment routine;
receive IoT device details from the source gateway; and
transmit the IoT device details to the target gateway to enable the IoT device to connect with the target gateway, wherein the IoT device details include at least an identifier associated with at least one of an IoT device or plurality of IoT devices, the identifier having been utilized by the source gateway to connect to the IoT device.

### Claim 2 (depends on 1)

The sitewide controller device of claim 1, wherein the gateway health data comprises at least one of CPU load, memory usage, network throughput, radio utilization including transmit, receive, and idle timing, mix of reported and assigned device types, received signal strengths, transmit power, response times, timeout events, latency indicators, clock accuracy, connection stability, connection failures, response failures, packet retries, diagnostic error reports, data consumption, noise levels across communication channels, channel map, spectral capacity, or data packet loss.

### Claim 3 (depends on 1)

The sitewide controller device of claim 1, wherein the load-balancing event occurs in response to the gateway health data of the source gateway exceeding load thresholds based on at least one of CPU usage, memory consumption, or congestion metrics.

### Claim 4 (depends on 1)

The sitewide controller device of claim 1, wherein the failover event occurs in response to the source gateway experiencing a failure or a maintenance downtime.

### Claim 5 (depends on 1)

The sitewide controller device of claim 1, wherein the roaming event occurs in response to at least one of:
the sitewide controller determining a signal strength differential that is based at least in part on gateway data received from the target gateway indicating that the target gateway is receiving a signal having a first signal strength from the IoT device, the first signal strength being greater than a second strength of the signal received by the source gateway, or
the sitewide controller determining movement of the IoT device based at least in part on a predictive roaming model that includes historical model data correlated to signal strength data.

### Claim 6 (depends on 1)

The sitewide controller device of claim 1, wherein the identifier associated with at least one of an IoT device or plurality of IoT devices includes at least one of a MAC address or a vMAC address.

### Claim 7 (depends on 1)

The sitewide controller device of claim 1, wherein the plurality of selection parameters of the target gateway comprise at least one of load capacity, radio availability, proximity of the target gateway to an IoT device, signal strength, communication history of the target gateway and the IoT device, or spectral resources.

### Claim 8 (depends on 1)

The sitewide controller device of claim 1, wherein the IoT device details includes at least one of timing data, device-specific identifiers, encryption keys, communication states, device status indicators, or protocol versions.

### Claim 9

A method for network reconfiguration, the method comprising:
collecting a network health data and gateway health data from a source gateway;
transmitting a device assignment signal to a source gateway, the device assignment signal configured to initiate a device assignment routine when a device assignment trigger is met at the source gateway, wherein the device assignment trigger comprises at least one of a load-balancing event, a failover event, a roaming event, or a user-initiated event;
determining a target gateway based on a plurality of selection parameters within the device assignment routine;
receiving IoT device details from the source gateway; and
transmitting the IoT device details to the target gateway to enable the IoT device to connect with the target gateway, wherein the IoT device details includes at least an identifier associated with at least one of an IoT device or plurality of IoT devices, the identifier having been utilized by the source gateway to connect to the IoT device.

### Claim 10 (depends on 9)

The method of claim 9, wherein the gateway health data comprises at least one of CPU load, memory usage, network throughput, radio utilization including transmit, receive, and idle timing, mix of reported and assigned device types, received signal strengths, transmit power, response times, timeout events, latency indicators, clock accuracy, connection stability, connection failures, response failures, packet retries, diagnostic error reports, data consumption, noise levels across communication channels, channel map, spectral capacity, or data packet loss.

### Claim 11 (depends on 9)

The method of claim 9, wherein initiating the device assignment routine for the load balancing event comprises initiating the device assignment routine in response to the gateway health data of the source gateway exceeding load thresholds based on at least one of CPU usage, memory consumption, or congestion metrics.

### Claim 12 (depends on 9)

The method of claim 9, wherein initiating the device assignment routine for the failover event comprises initiating the device assignment routine in response to the source gateway experiencing a failure or a maintenance downtime.

### Claim 13 (depends on 9)

The method of claim 9, wherein initiating the device assignment routine for the roaming event comprises initiating the device assignment routine in response to at least one of:
determining a signal strength differential that is based at least in part on gateway data received from the target gateway indicating that the target gateway is receiving a signal having a first signal strength from the IoT device, the first signal strength being greater than a second strength of the signal received by the source gateway, or
determining movement of the IoT device based at least in part on a predictive roaming model that includes historical model data correlated to signal strength data.

### Claim 14 (depends on 9)

The method of claim 9, wherein the identifier associated with at least one of an IoT device or plurality of IoT devices includes at least one of a MAC address or a vMAC address.

### Claim 15 (depends on 9)

The method of claim 9, wherein the plurality of selection parameters of the target gateway comprises at least one of load capacity, radio availability, proximity of the target gateway to an IoT device, signal strength, communication history of the target gateway and the IoT device, or spectral resources.

### Claim 16 (depends on 9)

The method of claim 9, wherein the IoT device details includes at least one of timing data, device-specific identifiers, encryption keys, communication states, device status indicators, or protocol versions.

### Claim 17

A computer-readable storage medium, storing instructions thereon, that, when executed by a processor, configure the processor to:
collect network health data and gateway health data from a source gateway;
transmit a device assignment signal to a source gateway, the device assignment signal configured to initiate a device assignment routine when a device assignment trigger is met at the source gateway, wherein the handoff trigger comprises at least one of a load-balancing event, a failover event, a roaming event, or a user-initiated event;
determine a target gateway based on a plurality of selection parameters within the device assignment routine;
receive IoT device details from the source gateway; and
transmit the IoT device details to the target gateway to enable the target gateway to connect with the IoT device wherein the IoT device details include at least an identifier associated with at least one of an IoT device or plurality of IoT devices, the identifier having been utilized by the source gateway to connect to the IoT device.

### Claim 18 (depends on 17)

The storage medium of claim 17, wherein the gateway health data comprises at least one of CPU load, memory usage, network throughput, radio utilization including transmit, receive, and idle timing, mix of reported and assigned device types, received signal strengths, transmit power, response times, timeout events, latency indicators, clock accuracy, connection stability, connection failures, response failures, packet retries, diagnostic error reports, data consumption, noise levels across communication channels, channel map, spectral capacity, or data packet loss.

### Claim 19 (depends on 17)

The storage medium of claim 17, wherein the load-balancing event occurs in response to the gateway health data of the source gateway exceeding load thresholds based on at least one of CPU usage, memory consumption, or congestion metrics.

### Claim 20 (depends on 17)

The storage medium of claim 17, wherein the failover event occurs in response to the source gateway experiencing a failure or a maintenance downtime.
