CRC Anomaly Counter Normalization Across Variable Computation Periods

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing communication systems face challenges in consistently detecting and reporting CRC anomalies across varying data rates and CRC computation periods, leading to inaccurate error detection and diagnostic issues, especially with new designs like Seamless Rate Adaptation and Dynamic Rate Repartition that alter data rates without changing framing parameters.

Innovation Solution

A method for normalizing CRC anomaly counters based on the actual CRC computation period (PERp value), ensuring consistent reporting of CRC anomalies across all connections in a network, regardless of data rate or CRC computation period, by adjusting the CRC anomaly counter values proportionally to the PERp value.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If CRC computations are performed at varying rates (e.g., every 2ms vs every 17ms), then the system can adapt to different data rates and communication conditions, but the CRC anomaly reporting becomes inconsistent and inaccurate

Engineering Contradiction:

Improvedata rate adaptationVSAvoidCRC anomaly detection accuracy

Core Design Contradiction:

Adaptability or versatilityVSMeasurement precision

Solution Approach 1:

The patent applies parameter changes by normalizing the CRC anomaly counter based on the actual CRC computation period (PERp). The normalization formula adjusts the anomaly count proportionally to the ratio of standard PERp (17ms) to actual PERp, ensuring that the diagnostic accuracy remains consistent regardless of variations in CRC computation rate caused by different data rates or SRA/DRR operations.

Inventive Principle:

Principle #35Parameter changes

2Adaptability or versatility

If Seamless Rate Adaptation and Dynamic Rate Repartition are implemented to allow online data rate changes, then system flexibility improves, but the CRC computation period varies causing inconsistent anomaly reporting

Engineering Contradiction:

Improveonline rate adaptationVSAvoidCRC reporting consistency

Core Design Contradiction:

Adaptability or versatilityVSStability of the object's composition

Solution Approach 1:

The patent implements dynamics by making the CRC anomaly counter normalization adaptive to changing communication conditions. The system dynamically adjusts the normalization factor based on the actual PERp value, which varies with data rate changes from SRA/DRR operations. This allows the system to maintain stable and consistent anomaly reporting despite the dynamic nature of rate adaptation.

Inventive Principle:

Principle #15Dynamics

3Ease of manufacture

If CRC anomaly threshold is set based on fixed computation period assumptions, then simple diagnostic rules can be established, but false alarms occur when computation period varies

Engineering Contradiction:

Improvediagnostic rule simplicityVSAvoiddiagnostic accuracy

Core Design Contradiction:

Ease of manufactureVSReliability

Solution Approach 1:

The patent resolves this contradiction by introducing a normalization parameter that adjusts the CRC anomaly counter based on actual computation period. This maintains the simplicity of threshold-based diagnostic rules while improving reliability, as the normalized counter values remain consistent across varying PERp conditions, preventing false alarms.

Inventive Principle:

Principle #35Parameter changes

Data Source

PatentUS7925958B2CRC counter normalization

Publication Date: 2011.04.12 DONGBU HITEK CO LTD

AI summary

The ability to accurately and efficiently calculate and report communication errors is becoming more important than ever in today's communications environment. More specifically calculating and reporting CRC anomalies in a consistent manner across a plurality of communications connections in a network is crucial to accurate error reporting. Through a normalization technique applied to a CRC computation period (e.g., the PERp value), accurate error identification and reporting for each individual connection can be achieved.