Network Orchestrator Reconfigures mDNS Query-Response Messages

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The existing DNS-SD and mDNS protocols lead to network flooding and high bandwidth utilization due to multicast query-response messages, especially in large-scale networks, which can cause service discovery failures and reduced user experience.

Innovation Solution

A network orchestrator determines the average packet counts for client types in networks configured for multicast and unicast query-response messages, reconfiguring the network to use unicast query-response messages when the difference exceeds a threshold, thereby reducing bandwidth consumption and preventing flooding.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multicast query-response messages are used in DNS-SD protocol, then service discovery is enabled in networks without local name servers, but network flooding and high bandwidth utilization occur

Engineering Contradiction:
Improveservice discovery capabilityVSAvoidbandwidth utilization
Core Design Contradiction:
Adaptability or versatilityVSLoss of energy

Solution Approach 1:

The patent changes the communication parameter from multicast to unicast for query-response messages. By detecting when a client device receives multiple duplicate query-response messages (indicating network flooding) and switching to unicast mode, the system maintains service discovery functionality while significantly reducing bandwidth consumption and preventing network flooding.

Inventive Principle:
Principle #35Parameter changes

2Adaptability or versatility

If multicast query-response messages are used, then service discovery is achieved, but network flooding causes service discovery failures

Engineering Contradiction:
Improveservice discovery functionalityVSAvoidservice discovery success rate
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent implements a feedback mechanism where the network orchestrator monitors duplicate query-response messages received by client devices. When flooding is detected (multiple duplicates from different servers), the system switches to unicast mode, providing feedback that restores reliable service discovery by eliminating the flooding problem that causes failures.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The patent makes the query-response message transmission mode dynamic by switching between multicast and unicast based on network conditions. The system dynamically detects flooding conditions and adapts its behavior accordingly, ensuring service discovery reliability is maintained while avoiding the flooding-induced failures.

Inventive Principle:
Principle #15Dynamics

3Loss of energy

If unicast query-response messages are used, then bandwidth consumption is reduced, but service discovery efficiency decreases

Engineering Contradiction:
Improvebandwidth consumptionVSAvoidservice discovery efficiency
Core Design Contradiction:
Loss of energyVSProductivity

Solution Approach 1:

The patent dynamically changes the transmission parameter based on network conditions. In normal conditions, multicast is used for efficient service discovery. When flooding is detected (indicated by multiple duplicate messages), the system switches to unicast, achieving a balance between bandwidth efficiency and service discovery effectiveness.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS11824640B2System and method for reconfiguring a network using network traffic comparisions
Publication Date: 2023.11.21 HEWLETT PACKARD ENTERPRISE DEV LP
  • US11824640B2 patent drawing
  • US11824640B2 patent drawing
  • US11824640B2 patent drawing

AI summary

Example implementations relate to a method for reconfiguring a network based on network traffic comparison. The first network supports multicast Domain Name Service (mDNS) query with multicast query-response messages. The method includes determining a client type for each client device and a first average packet count for each client type in a first network. The method includes receiving a second average packet count for each corresponding client type from a second network. The second network supports mDNS query with unicast query-response messages. A difference between the first average packet counts and the second average packet counts for corresponding client types is computed. The first network is reconfigured to respond to mDNS query with unicast query-response messages when the difference computed for at least one client type in the first network and each corresponding client type in the second network is above a predefined threshold.