Metadata Channel Allocation in Ring Network Topologies

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In ring and daisy-chain network topologies, such as BLU link V2, transmitting metadata alongside audio data can cause bottlenecks and network disruptions due to the need for separate packet transmission, which is not efficiently managed in existing systems.

Innovation Solution

Allocating a chunk of a packet as a metadata channel within the audio data stream, allowing metadata to be transmitted at regular intervals, synchronized across all devices in the network, thereby maintaining network efficiency and minimizing disruptions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If metadata is transmitted separately from audio data in ring/daisy-chain networks, then metadata can be delivered to all nodes, but network bottlenecks and disruptions occur due to the topology's inherent data propagation delays

Engineering Contradiction:
Improvemetadata deliveryVSAvoidnetwork throughput
Core Design Contradiction:
Loss of informationVSProductivity

Solution Approach 1:

The patent combines metadata transmission with audio data transmission by allocating specific channels within the audio data stream for metadata. This merging eliminates separate metadata transmission paths that cause bottlenecks in ring/daisy-chain topologies, allowing both audio and metadata to be delivered simultaneously without additional network load.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The audio data stream is designed to serve multiple functions: carrying both audio content and metadata. By making the audio channel universal, the system eliminates the need for dedicated metadata channels that would exacerbate propagation delays and bottlenecks in ring networks.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Reliability

If a dedicated metadata channel is created in ring networks, then metadata transmission is ensured, but network complexity and potential failure points increase

Engineering Contradiction:
Improvemetadata transmission reliabilityVSAvoidnetwork configuration
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

Instead of creating a separate dedicated metadata channel that would add complexity, the patent merges metadata transmission into the existing audio data channels. This approach ensures reliable metadata delivery without increasing network complexity or creating additional failure points.

Inventive Principle:
Principle #5Merging (Combining)

3Speed

If metadata is transmitted at high frequency intervals, then real-time updates are achieved, but bandwidth consumption increases causing buffer overflows

Engineering Contradiction:
Improvemetadata update rateVSAvoidbandwidth usage
Core Design Contradiction:
SpeedVSQuantity of substance

Solution Approach 1:

The patent implements periodic metadata transmission at optimized intervals within the audio data stream. By using periodic action rather than continuous high-frequency transmission, the system achieves real-time updates while controlling bandwidth consumption to prevent buffer overflows in ring network topologies.

Inventive Principle:
Principle #19Periodic action

Solution Approach 2:

The system transmits metadata at sufficient intervals to achieve real-time updates without excessive frequency that would overload the network. This partial action approach balances update speed with bandwidth constraints.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentEP3133795B1Network device and method for metadata distribution in a network
Publication Date: 2019.06.19 HARMAN INT IND INC
  • EP3133795B1 patent drawingFigure 1
  • EP3133795B1 patent drawingFigure 2
  • EP3133795B1 patent drawingFigure 3

AI summary

Embodiments are disclosed for network devices and metadata transmission/receipt in a network. An example network device in a daisy-chain or ring network includes a network interface device, a processor, and a storage device storing instructions executable by the processor to allocate a channel in the network as a metadata channel, and synchronize with each other device in the network. The instructions are further executable to insert mctadata into a metadata packet, and transmit the metadata packet on the allocated metadata channel alongside content transmitted on remaining channels of the network.