Observable Configuration Delivery for Hybrid Multicast and Unicast Updates

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing methods for delivering configuration parameters to networked computing devices are inefficient and costly, particularly when dealing with unicast messaging to individual devices and multicasting to groups with varying configurations.

Innovation Solution

A system utilizing a hybrid network architecture that orchestrates configuration updates through a central cloud and on-premises head-end service, supporting hierarchical configurations, prioritized scheduling, and flexible delivery methods like broadcasting, multicasting, unicasting, and unicast batching to manage spikes and regular traffic efficiently.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If unicast messaging is used to deliver configuration parameters to each endpoint device individually, then each device can receive unique parameters, but network bandwidth consumption increases and delivery efficiency decreases

Engineering Contradiction:
Improveconfiguration customizationVSAvoiddelivery efficiency
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent segments the configuration delivery process into two distinct phases: a multicasting phase for delivering common configuration parameters to multiple devices simultaneously, and a unicast phase for delivering device-specific parameters. This segmentation allows the system to leverage the efficiency of multicasting while still providing the adaptability of unicast messaging when needed, thereby resolving the contradiction between delivery efficiency and configuration customization.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent merges multicasting and unicast messaging into a hybrid delivery mechanism. The system first multicasts common configuration parameters to all target devices, then supplements this with unicast messages for device-specific parameters. This merging allows the system to achieve both high delivery efficiency through multicasting and configuration adaptability through unicast, resolving the technical contradiction.

Inventive Principle:
Principle #5Merging (Combining)

2Productivity

If multicasting is used to deliver identical configuration parameters to multiple endpoint devices, then network bandwidth consumption is reduced, but devices requiring different configurations cannot be accommodated

Engineering Contradiction:
Improvedelivery efficiencyVSAvoidconfiguration flexibility
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

The patent segments configuration parameters into common parameters (applicable to multiple devices) and device-specific parameters. Common parameters are delivered via efficient multicasting, while device-specific parameters are delivered via unicast messaging. This segmentation allows the system to maintain high delivery efficiency for the majority of parameters while still providing the flexibility needed for device-specific configurations.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent applies local quality by delivering different types of configuration data through different channels: common configuration parameters are delivered to multiple devices simultaneously through multicasting, while device-specific parameters are delivered individually through unicast. This allows each device to receive the appropriate level of configuration detail locally, maintaining both efficiency and flexibility.

Inventive Principle:
Principle #3Local quality

3Speed

If configuration updates are sent to all endpoint devices simultaneously, then all devices receive updates quickly, but network spikes and traffic overloads occur

Engineering Contradiction:
Improveupdate delivery speedVSAvoidnetwork overload
Core Design Contradiction:
SpeedVSObject-affected harmful factors

Solution Approach 1:

The patent implements periodic action by scheduling configuration updates to be delivered in controlled intervals rather than all at once. The system uses a scheduling mechanism that staggers the delivery of configuration parameters across multiple time periods, preventing network spikes while ensuring all devices eventually receive the updates. This approach maintains reasonable update speed while avoiding network overload.

Inventive Principle:
Principle #19Periodic action

Solution Approach 2:

The patent applies dynamics by making the configuration delivery process adaptive and flexible. The system dynamically adjusts the delivery schedule based on network conditions, device readiness, and priority levels. High-priority devices can receive updates faster, while the overall delivery is paced to prevent network overload, resolving the contradiction between speed and network health.

Inventive Principle:
Principle #15Dynamics

4Manufacturing precision

If unicast messaging is used for each endpoint device, then device-specific configurations are delivered accurately, but the cost and complexity of the delivery system increases

Engineering Contradiction:
Improveconfiguration accuracyVSAvoidsystem complexity
Core Design Contradiction:
Manufacturing precisionVSDevice complexity

Solution Approach 1:

The patent segments the configuration delivery system into a multicasting component and a unicast component. The multicasting component handles the bulk of configuration delivery with simple, efficient group messaging, while the unicast component handles only the device-specific parameters. This segmentation reduces overall system complexity compared to pure unicast while maintaining configuration accuracy through the targeted use of unicast messaging.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS12526188B2Observable feature configuration delivery
Publication Date: 2026.01.13 ITRON INC
  • US12526188B2 patent drawing
  • US12526188B2 patent drawing
  • US12526188B2 patent drawing

AI summary

A system and a method for observable configuration delivery include receiving one or more configuration change requests (CCRs); storing the one or more CCRs in a database; signaling configuration send channels of target tenants of a plurality of tenants associated with the one or more CCRs to awaken; sending the one or more CCRs from the database to the target tenants through a headend service (HES); receiving asynchronous status messages from the HES as a result of sending the one or more CCRs; signaling the configuration send channels for a next set of CCRs based on the asynchronous status messages; and sending the next set of CCRs to one or more tenants of the target tenants.