Network Device Voice Data Filtering and Priority Verification

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Incorrect marking of non-voice data as voice data in networks can lead to congestion and dropping of valid voice data, highlighting the need for effective protection of Class of Service (CoS) to ensure accurate prioritization and handling of data units.

Innovation Solution

Implementing a system that filters data units marked as voice data to verify their actual content, discarding or modifying them if they are not voice data, and communicating an out-of-spec indication to downstream devices to adjust their treatment accordingly.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If data units are marked with priority information to enable differentiated handling, then voice data can be identified and treated uniquely, but non-voice data may be incorrectly marked as voice data causing network congestion and dropping of valid voice data

Engineering Contradiction:
Improveaccuracy of voice data identificationVSAvoidnetwork congestion and data loss
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The patent applies preliminary action by performing filtering and verification of data units marked as voice data before they are fully processed and transmitted through the network. The network element intercepts marked data units, verifies their actual content, and corrects or discards mismarked units before they can cause congestion or disrupt valid voice traffic. This preventive approach stops harmful incorrectly marked data from entering the voice handling pipeline.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces an intermediary filtering mechanism between the data source and the voice data handling system. This intermediary network element acts as a mediator that receives marked data units, verifies their authenticity, and either passes genuine voice data through or corrects/discards false markings. This intermediary layer protects the voice data system from harmful inputs without requiring changes to the core voice handling infrastructure.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Speed

If senders or network elements mark priority fields to indicate voice data, then voice data can be prioritized over other data, but this creates vulnerability to mislabeling that undermines the priority system

Engineering Contradiction:
Improveprioritization of voice data transmissionVSAvoidintegrity of priority marking
Core Design Contradiction:
SpeedVSReliability

Solution Approach 1:

The patent implements feedback by having the network element verify the actual content of data units against their priority markings. When a discrepancy is detected (non-voice data marked as voice), the system provides feedback by correcting the marking or discarding the unit. This feedback loop ensures that the priority marking system remains accurate and reliable, preventing mismarked data from undermining the prioritization mechanism.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The verification and correction of priority markings occurs preliminarily, before the data units are fully processed according to their marked priority. By checking the authenticity of voice data markings early in the transmission path, the system prevents mismarked data from receiving inappropriate priority treatment, thus maintaining the integrity of the prioritization system.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS8351341B1Filtering to protect class of service
Publication Date: 2013.01.08 JUNIPER NETWORKS INC
  • US8351341B1 patent drawing
  • US8351341B1 patent drawing
  • US8351341B1 patent drawing

AI summary

A first field of a data unit is analyzed to determine whether the data unit is marked as a particular type of data unit. If the data unit is marked as a particular type of data unit, a second field of the data unit is analyzed to determine whether characteristics of the second data field correspond to the particular type of the data unit. Determining whether the characteristics of the second field correspond to the type of data unit ensures that the data unit is properly marked with respect to type. The first field may indicate a particular priority or that the data unit is carrying voice data. The second field may carry voice data. The analysis of the fields may be done on a data unit by data unit basis, or on a stream basis.