An error correction apparatus comprises an input for receiving data. The received data includes error-check data. The apparatus also includes a processing resource arranged to calculate parity check data. A data store is coupled to the processing resource for storing look-up data for identifying, when in use, a location of an error in the received data. The look-up data is a compressed form of indexed error location data.

Description

6 parts

›FIELD OF THE INVENTION

This invention relates to an error correction apparatus of the type that, for example, employs look-up data to determine a location of an error in a bit pattern. This invention also relates to a method of correcting an error of the type that, for example, comprises looking-up data to determine a location of an error in a bit pattern. This invention further relates to a method of generating error location data of the type that, for example, is accessed to determine a location of an error in a bit pattern.

›BACKGROUND OF THE INVENTION

In the field of data communications, it is known to generate error check data based upon a bit pattern to be communicated from a source point to a destination point in a communications network. As an example, a header of an Asynchronous Transfer Mode (ATM) cell to be transmitted from the source point to the destination point comprises 40 bits of data. Bits 0 to 7 of the header comprise so-called Header Error Check (HEC) data based upon bits 8 to 39 of the header, bits 8 to 39 comprising actual header data to be communicated. The HEC data is a Cyclic Redundancy Check 8 (CRC8) value calculated from the actual data (bits 8 to 39 ).

Upon receipt of the header, the CRC8 value of the data portion of the header (bits 8 to 39 ) is re-calculated and used. In the case of ATM, the calculated CRC8 value is XORed with the HEC data received to calculate parity check data, sometimes known as a syndrome value. For each bit position of the received data (bits 0 to 39 ), a unique syndrome value exists and is typically stored in a look-up table indexed by bit position. Hence, the unique syndrome value indicates the location of a one-bit error.

Consequently, after calculation of the syndrome value, the syndrome value is used to search the look-up table for a corresponding location (bit position) of a bit that is in error. The location of the error is then used to correct the 1-bit error that the received data contains.

However, the table is unsorted and so access of error location data is inefficient, as a linear search method is usually involved. Therefore, for reasons of access speed, the table is sorted by syndrome value and “padded” with unspecified error locations for non-existent syndrome values, for example −1. The padded look-up table is indexed by syndrome value, the error location data constituting table entries. Further, the padded look-up table is known as a “reverse table”.

In order to provide the above error correction, a so-called micro-engine module is provided, supported by a microprocessor. However, the micro-engine has limited storage capacity and the padded reverse look-up table is an inefficient use of storage space. For example, a typical reverse look-up table for providing CRC8 error correction only has 40 out of 256 “specified” entries, i.e. only 15.6% of the entries are specified, the remaining entries using valuable storage capacity of the micro-engine. Consequently, use of the micro-engine module may not be possible where constraints on memory space exist.

›STATEMENT OF INVENTION

According to the present invention, there is provided an error correction apparatus, a method of correcting an error and a method of generating error location data as set forth in the appended claims.

›BRIEF DESCRIPTION OF THE DRAWINGS

At least one embodiment of the invention will now be described, by way of example only, with reference to the accompanying drawings, in which:

FIG. 1 is a schematic diagram of an error correction apparatus constituting an embodiment of the invention;

FIG. 2 is a schematic diagram of a data compression technique;

FIG. 3 is a schematic diagram of a data structure associated with data processed by the apparatus of FIG. 1 ; and

FIG. 4 is a flow diagram of a method of correcting an error for the apparatus of FIG. 1 .

›DESCRIPTION OF PREFERRED EMBODIMENTS · 1 of 2

Throughout the following description identical reference numerals will be used to identify like parts.

Referring to FIG. 1 , a communications processor 100 of a Power Quad Universal Integrated Communications Controller (PowerQUICC™) available from Freescale, Inc. comprises an input 102 coupled to an interface 104 , for example an analogue-to-digital converter circuit and, optionally an optical transducer circuit to convert received optical signals to the electrical domain in the event that the communications processor is coupled to an optical communications network (not shown). The interface 104 is coupled to a micro-engine circuit 106 comprising microcode 108 to be executed and a storage space 110 containing compressed look-up data. The micro-engine 106 is coupled to a Central Processing Unit (CPU) 112 of the communications processor 100 , the CPU 112 being coupled to an output 114 of the communications processor 100 for coupling the communications processor 100 to, for example an Internet Protocol (IP) interface (not shown).

The compressed look-up data is formed by compressing an original padded reverse look-up table of a known type, for example the padded reverse look-up table of Table I below.

Turning to FIG. 2 , the original padded reverse look-up table 200 is transformed to a matrix 202 , for example a square matrix, such as a 16×16 matrix. The matrix 202 is then compressed into a first array of data 204 and a second array of data 206 , the first array of data 204 being a displacement array, r, and the second array of data 206 comprising a plurality of vectors, each vector being two-dimensional. The matrix 202 is compressed according to any suitable algorithm, for example, as described in “Storing a Sparse Table” (Robert Endre Tarjan, Andrew Chi-Chih Yoo, Communications of the ACM, November 1979, Volume 22, Number 11).

The compression technique is such that a mapping exists between the first array of data 204 and the second array of data 206 . Examples of the first array of data 204 and the second array of data 206 are shown in Tables II and III below (use of the term “Table” is not intended to be limiting and purely for identification purposes), respectively.

Operation of the above apparatus will now be described in the context of a numerical example. In operation, the communications processor 100 receives a bit pattern 300 ( FIG. 3 ) comprising a data portion 302 and a HEC portion 304 , the bit pattern 300 being a header of an ATM cell. As transmitted, the data portion 302 was 0x30313233 and the HEC portion 304 was 0x69. Upon receipt, the data portion 302 was 0x31313233 and the HEC portion was 0x69. Hence, the data portion 302 , as received, comprises a 1-bit error as compared with the data portion 302 as transmitted.

Referring to FIG. 4 , in order to calculate a syndrome value (Step 400 ), the micro-engine 106 firstly calculates a verifying HEC value for the data portion 302 of the bit pattern 300 as received:

verHEC=CRC8(0 x 31313233)=0 x 7 F

As can be seen from the above calculation, the verifying HEC is calculated using CRC8, though the skilled person will appreciate that other techniques can be employed for other applications, for example CRC16 or CRC32.

Using module 2 addition of the HEC as received and the calculated verifying HEC, the syndrome value is calculated (Step 400 ):

S =verHEC⊕ rx HEC=0 x 7 F⊕ 0 x 69=0 x 16=22

The micro-engine 106 then determines (Step 402 ) whether the calculated syndrome value is equal to zero. If the syndrome value is zero, the micro-engine determines (Step 404 ) that the data portion 302 of the received bit pattern 300 is correct and so the bit pattern is transferred to the CPU 112 .

However, if the syndrome value is non-zero, access to the compressed look-up data is required as the non-zero nature of the calculated syndrome value is indicative of the bit pattern 300 as received containing one or more error. In accordance with the mappings convention between the first array of data 204 and the second array of data 206 , an entry, i, of the first array of data 204 is identified (Step 406 ) by performing a division operation by n, in this example 16, of the syndrome value in order to obtain the quotient of the division for use as the entry, i, of the first array of data 204 . The micro-engine 106 then calculates (Step 406 ) the remainder, j, of the division of the syndrome value by n, in this example 16.

The i th entry in the first array of data 204 is then accessed (Step 408 ) by the micro-engine 106 to obtain a corresponding stored displacement value, namely 17, and added to the remainder, j, calculated, namely 6:

r[i]= 17

j= 6

r[i]+j= 17+6=23

In accordance with the mapping scheme between the first and second data arrays 204 , 206 , the result of the above addition identifies an entry in the second array of data 206 (Step 410 ), namely entry number 23 that is deemed to contain location data identifying the location in the bit pattern 300 of the error, provided the following test is satisfied.

In this regard, the 23 rd entry of the second array of data 204 is a vector containing a look-up syndrome value and corresponding location data. The look-up syndrome value is compared (Step 412 ) with the calculated syndrome value. If the look-up syndrome value stored is the same as the syndrome value calculated, then the syndrome value calculated is deemed (Step 414 ) specified in the original look-up table 200 upon which the first and second arrays of data 204 , 206 are based and so the location data, in this example 32, is used. If, however, the look-up syndrome value and the calculated syndrome values are not the same, then the syndrome value calculated is deemed (Step 416 ) unspecified in the original look-up table 200 and the error in the bit pattern 300 cannot be corrected (Step 418 ) by the micro-engine 106 , for example due to the bit pattern 300 containing more than one error

When the calculated syndrome value is deemed (Step 414 ) specified, the error location in bit pattern 300 is found. If the one bit error occurs in the HEC portion 304 , the data portion 302 is error free and so no error correction to the data portion 302 is needed. If the one bit-error occurs in the data portion 302 , a correcting bit pattern needs be generated to correct (Step 420 ) the error. Consequently, a least significant bit of the following initial bit pattern is then shifted to the right by (32 (the location of the error)−8) bit positions (due to the first 8 bits of the header relating to the HEC) in order to yield a correcting bit pattern:

›DESCRIPTION OF PREFERRED EMBODIMENTS · 2 of 2

errorPattern=0 x 00000001<<(32−8)=0 x 01000000

The micro-engine 106 then performs module 2 addition of the data portion 302 as received with the correcting bit pattern:

rx Data=0 x 31313233⊕0 x 01000000=0 x 30313133

The 1-bit error in the received bit pattern is thus corrected and then forwarded to the CPU 112 . The above process is then repeated for subsequently received ATM headers.

Although the above example has been described in the context of an ATM header, the skilled person will appreciate that the above technique can be applied to other bit patterns, for example an IP packet.

It is thus possible to provide a method and apparatus that can facilitate access of error location data with sufficient speed whilst employing look-up data that is economic with storage space of the micro-engine. In this respect, the compressed look-up data only requires 120 bytes of storage space, representing a 53% saving in storage space over the original padded look-up table. Of course, the above advantages are exemplary, and these or other advantages may be achieved by the invention.

The invention may also be implemented in a computer program for running on a computer system, at least including code portions for performing steps of a method according to the invention when run on a programmable apparatus, such as a computer system or enabling a programmable apparatus to perform functions of a device or system according to the invention. Such a computer program may be provided on a data carrier, such as a CD-rom or diskette, stored with data loadable in a memory of a computer system, the data representing the computer program. The data carrier may further be a data connection, such as a telephone cable or a wireless connection.

In the foregoing specification, the invention has been described with reference to specific examples of embodiments of the invention. It will, however, be evident that various modifications and changes may be made therein without departing from the broader spirit and scope of the invention as set forth in the appended claims. For example, the invention is not limited to physical devices or units implemented in non-programmable hardware but can also be applied in programmable devices or units able to perform the desired device functions by operating in accordance with suitable program code. Furthermore, the devices may be physically distributed over a number of apparatuses, while functionally operating as a single device. Also, devices functionally forming separate devices may be integrated in a single physical device. Further, the skilled person will appreciate that not all advantages stated above are necessarily achieved by embodiments described herein.

In the claims, any reference signs placed between parentheses shall not be construed as limiting the claim. The word ‘comprising’ does not exclude the presence of other elements or steps then those listed in a claim. Furthermore, the words ‘a’ and ‘an’ shall not be construed as limited to ‘only one’, but instead are used to mean ‘at least one’, and do not exclude a plurality. The mere fact that certain measures are recited in mutually different claims does not indicate that a combination of these measures cannot be used to advantage.

›Tables in the description — 2

TABLE I

Syndrome	errorLoc
0	−1
1	0
2	1
3	−1
4	2
5	−1
6	−1
7	8
8	3
9	−1
10	−1
11	31
12	−1
13	−1
14	9
15	−1
16	4
17	−1
18	−1
19	−1
20	−1
21	16
22	32
23	−1
24	−1
25	−1
26	−1
27	−1
28	10
29	−1
30	−1
31	−1
32	5
33	−1
34	−1
35	−1
36	−1
37	−1
38	−1
39	−1
40	−1
41	−1
42	17
43	−1
44	33
45	−1
46	−1
47	−1
48	−1
49	39
50	−1
51	−1
52	−1
53	−1
54	−1
55	−1
56	11
57	−1
58	−1
59	−1
60	−1
61	−1
62	−1
63	−1
64	6
65	−1
66	−1
67	29
68	−1
69	−1
70	−1
71	−1
72	−1
73	−1
74	−1
75	−1
76	−1
77	−1
78	−1
79	−1
80	−1
81	27
82	−1
83	−1
84	18
85	−1
86	−1
87	20
88	34
89	−1
90	−1
91	22
92	−1
93	−1
94	−1
95	−1
96	−1
97	−1
98	−1
99	−1
100	−1
101	−1
102	−1
103	36
104	−1
105	−1
106	−1
107	24
108	−1
109	−1
110	−1
111	−1
112	12
113	−1
114	−1
115	−1
116	−1
117	−1
118	−1
119	−1
120	−1
121	−1
122	−1
123	−1
124	−1
125	−1
126	−1
127	−1
128	7
129	−1
130	−1
131	−1
132	−1
133	−1
134	30
135	−1
136	−1
137	15
138	−1
139	−1
140	−1
141	−1
142	−1
143	−1
144	−1
145	−1
146	−1
147	−1
148	−1
149	−1
150	−1
151	−1
152	−1
153	−1
154	−1
155	38
156	−1
157	−1
158	−1
159	−1
160	−1
161	−1
162	28
163	−1
164	−1
165	−1
166	−1
167	−1
168	19
169	−1
170	−1
171	26
172	−1
173	−1
174	21
175	−1
176	35
177	−1
178	−1
179	−1
180	−1
181	−1
182	23
183	−1
184	−1
185	−1
186	−1
187	−1
188	−1
189	−1
190	−1
191	−1
192	−1
193	−1
194	−1
195	−1
196	−1
197	−1
198	−1
199	14
200	−1
201	−1
202	−1
203	−1
204	−1
205	−1
206	37
207	−1
208	−1
209	−1
210	−1
211	−1
212	−1
213	−1
214	25
215	−1
216	−1
217	−1
218	−1
219	−1
220	−1
221	−1
222	−1
223	−1
224	13
225	−1
226	−1
227	−1
228	−1
229	−1
230	−1
231	−1
232	−1
233	−1
234	−1
235	−1
236	−1
237	−1
238	−1
239	−1
240	−1
241	−1
242	−1
243	−1
244	−1
245	−1
246	−1
247	−1
248	−1
249	−1
250	−1
251	−1
252	−1
253	−1
254	−1
255	−1

TABLE II

0	0
1	17
2	20
3	34
4	36
5	2
6	27
7	5
8	19
9	5
10	10
11	31
12	19
13	9
14	0
15	0

Claims as granted

20 claims

Classifications

5 codes

IPC · International Patent Classification

Section H — Electricity

H03M13/00

USPC · US Patent Classification

714/759714/49714/786714/701

Claim changes

Soon

Coming soonHow the claims changed between publication and grant

See which claims were amended, added or cancelled during examination, with every added and removed word marked.

AmendedAddedCancelledUnchanged

The published claims of this application are not paired with the granted ones in what we hold.

File wrapper

⤢ drag to zoom

USPTOApplicanthover for detail · click to open

Pendency

7.0 y

2,567 days filing → grant

Office actions

non-final + final

Responses

no RCE

Interviews

examiner interview summaries

Examiner

Joseph Schell

art unit 2114 · TC 2100

Law firm

Law firm · Log in to unlock

Citations: 16 back · 0 forward

See the full prosecution history — every USPTO and applicant action on this file, in order.

Documents

Log in to open the documents of this file: the application as filed, every office action and response, the notice of allowance.

Chain of title

⤢ drag to zoom

TitleLienReleasehover for detail · click to open

See the full assignment history — every owner this patent has passed through, with recordation dates and reel/frame numbers.