CRC counter normalization

• US 7,979,778 B2
• Filed: 05/20/2010
• Issued: 07/12/2011
• Est. Priority Date: 09/25/2004
• Status: Expired due to Fees

• Current Assignee: TQ Delta LLC (Techquity Capital Management, LLC)
• Original Assignee: Aware Incorporated (Crowley Holdings Preferred LLC)
• Inventors: Tzannes, Marcos C.
• Primary Examiner(s): Chase, Shelly A
• Application Number:
  US12/783,771
• Publication Number:
  US 20100293444A1
• Time in Patent Office: 418 Days
• Field of Search: 714/746, 714/752, 714/758, 714/799, 714/704
• US Class Current: 714/758
• CPC Class Codes: G06F 11/1004 to protect a block of data words, e.g. CRC or checksum G06F11/1076 takes precedence; security arrangements for protecting computers or computer systems against unauthorized activity G06F21/00
• CPC Class Codes: H03M 13/09 Error detection only, e.g. using cyclic redundancy check [CRC] codes or single parity bit
• CPC Class Codes: H03M 13/096 Checksums
• CPC Class Codes: H04L 1/0045 Arrangements at the receiver end
• CPC Class Codes: H04L 1/0061 Error detection codes
• CPC Class Codes: H04L 1/22 using redundant apparatus to increase reliability

Abstract

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.

Claims

1. A method of reporting severely errored seconds (SES) in a consistent manner across a plurality of connections in a service provider network comprising:

computing a local CRC octet based on a received bit stream;

comparing, by a processor, the local CRC octet to a received CRC octet;

identifying a CRC anomaly when the local CRC octet is not identical to the received CRC octet; and

normalizing a CRC anomaly counter based on a value for a CRC computation period (PERp), wherein a Severely Errored Second is declared if there are more than N CRC anomalies in a second.

2. The method of claim 1, wherein the normalizing of the CRC anomaly counter comprises incrementing the CRC anomaly counter by a value of M, wherein the value M is equal to PERp/K, and K is a positive integer.

3. The method of claim 2, wherein K is equal to 20 or 15.

4. The method of claim 1, wherein N is equal to 18.

5. The method of claim 1, further comprising receiving an alarm.

6. The method of claim 1, further comprising dispatching a network technician to fix a connection.

7. The method of claim 1, further comprising communicating SES information to a service provider management system.

8. The method of claim 1, wherein the service provider network uses ADSL2.

9. The method of claim 1, wherein the service provider network uses VDSL2.