Method and apparatus for coded symbol stuffing in recording systems

A system and method of forming RLL coded data streams with separator blocks has an RLL encoder and a channel encoder. The input code word is divided into data portions and a separator portion. The data portions are inserted into an output codeword without encoding. Each data portion is separated from a next data portion by a space. The separator portion is encoded into non-zero separator sub-matrices, which are stuffed into the spaces between the data portions. The separator portions and the data portions may be separately permuted without exceeding a maximum number of consecutive zeros.

CROSS-REFERENCE TO RELATED APPLICATION(S)

BACKGROUND OF THE INVENTION

The present invention relates to data storage and retrieval systems. More particularly, the present invention relates to a method and apparatus for coded symbol stuffing in optical and magnetic recording systems where run length limiting coding schemes are used.

Generally, both data storage/retrieval systems and data transmission systems communicate information. Storage/retrieval systems communicate information through time, while data transmission systems communicate information through space. Typically, data storage and retrieval systems use a read/write head to communicate data to a corresponding one of substantially concentric tracks or channels in the media Using various modulation techniques, data transmission systems similarly communicate data over channels in the transmission media or receive data from channels in the media. Storage/retrieval systems and data transmission systems often utilize encoding/decoding schemes for error detection, for privacy, and for data compression.

One common type of coding scheme is referred to as Run Length Limiting. Run length limiting encoding schemes involve separating consecutive “1s” in a binary sequence by some predefined number of zeros. Coded data sequences having this property are referred to as Ran Length Limited (RLL) codes.

Conventional systems that utilize RLL coding schemes, such as optical and magnetic storage systems, as well as in some communication systems, typically include an outer error correcting code (ECC), and a run length limiting (RLL) encoder. Such systems may also include an optional inner channel encoder. Data is encoded first by the ECC, then passed through the RLL encoder. If the optional inner channel encoder is used, the RLL encoded data is then passed through the inner channel encoder. The output of either the RLL encoded data or the inner channel encoded data can then be precoded before being recorded onto channels on the media.

Typically, at the detection side, a Viterbi detector is used to reconstruct the coded bits from the channel; however, due to electronic and media noise in the channel, conventional detectors cannot recover the original data with an arbitrarily small error probability. To correct errors after the coded bits are reconstructed by the Viterbi detector, an ECC decoder is used at the output of the read/write channel. Generally, the ECC decoder decreases the output Bit-Error Rate (BER) and the Sector Failure Rate (SFR) of the channel to the levels typically provided in the technical specifications for the implementing apparatus.

It is known that the RLL code typically facilitates the operation of the timing circuits. At the same time, the RLL code shapes the spectrum of the signal and modifies the distance properties of the output code words of the channel. Since the RLL code effects both the shape of the signal spectrum and the distance properties of the output, the RLL code can be used to improve the BER and the SFR characteristics of the system.

Conventional RLL coding schemes employ a state transition diagram. In a finite state encoder, arbitrary user data (p) is encoded to constraint data (q) via a finite state machine, where p and q represent sequences of data objects, each containing two or more elements. The data rate of the encoder can be defined as p/q (“p divided by q”), provided that, at each stage of the encoding process, one P-object of user data (p) is encoded to one q-object of constraint data (q) in such a way that the concatenation of the encoded q-objects obeys the given constraint.

The finite-state machine has multiple states, and the encoder or decoder moves from one state to another after the generation of each output object. A single error in the received sequence can trigger the generation of wrong states in the decoder, resulting in long sequences of errors. This phenomenon is referred to as error propagation.

It is expected that the received sequence to be decoded will not be identical to the transmitted sequence due to a variety of factors, such as inter-symbol interference (ISI), damage to the storage medium, noise, and the like. These factors lead to errors in the decoded sequence, and the decoder must account for these errors. For the purpose of limiting error propagation, the decoder can be implemented via a sliding-block decoder, which is a decoder having a decoding window of a fixed size. The encoded data sequence is decoded a portion at a time, such that recovery of a specific original bit involves only a portion of the received sequence. Specifically, the portion of the received sequence being decoded is the portion of the sequence that falls within the decoding window of the specific bit. Thus, the decoding process can be considered as a sequence of decoding decisions where the decoding window “slides” over the sequence to be decoded. The sliding block decoder limits errors in the received sequence such that the error only influences the decoding decisions made within the window, thereby effecting only a limited number of recovered bits.

The size of the decoding window of a sliding block decoder is relatively significant. The size of the window provides an upper bound to the expected amount of error propogation and it provides an indication of the complexity of the decoder (and the corresponding size of the decoder's hardware implementation).

One technique for constructing finite state encoders is the state-splitting algorithm, which reduces design procedure a series of steps. As a design technique, the state-splitting algorithm works well for small and moderate values of p, but when p is relatively large, the state-splitting algorithm encounters simply too many possible assignments of data-to-codeword in the encoding graph, making design difficult. Moreover, a poor choice of assignments, given the complexity, could lead to a costly implementation. In practice, the implemented design should include the fewest possible number of states. However, the state-splitting algorithm does not directly solve the general problem of designing codes that achieve, for example, the minimum number of encoder states, the smallest sliding-block decoding window, or the minimum hardware complexity (a less precise valuation).

Recently, various types of iterative detection and decoding schemes were developed for use in data storage and data communication systems, based on turbo codes, Low Density Parity Check (LDPC) codes, and turbo product codes. These types of codes provide very low BERs, but they usually require the use of an interleaver after the RLL and optional inner channel encoder(s). An interleaver changes the order of the bits in a sequence. By processing the already encoded bits with an interleaver, the interleaver changes the order of the already encoded bits, which can effectively nullify the operation of the RLL encoder. Since encoders based on finite-state machines transform all (or almost all) data bits while generating the output code words, the use of such codes in channels with interleaving coded bits is virtually impossible, or at least severely restricted.

BRIEF SUMMARY OF THE INVENTION

A method of forming RLL coded data streams uses separator blocks to limit consecutive zeros to a predetermined maximum. An input code word is divided into data portions and a separator portion. Each data portion is inserted into an output codeword without encoding and separated from a next data portion by a space. The separator portion is encoded into non-zero separator sub-matrices, which are stuffed into the spaces between the data portions. The separator portion and the data portions may be separately permuted without violating a constraint on consecutive zeros in the output.

While the above-identified illustrations set forth preferred embodiments, other embodiments of the present invention are also contemplated, some of which are noted in the discussion. In all cases, this disclosure presents the illustrated embodiments of the present invention by way of representation and not limitation. Numerous other minor modifications and embodiments can be devised by those skilled in the art which fall within the scope and spirit of the principles of this invention.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

FIG. 1illustrates a read/write channel of magnetic and/or optical disc drives. As shown, the system10reads and writes data to an inner subchannel12of the magnetic and/or optical disc of the disc drive. The system has an Reed-Solomon (RS) Error Correction Code (ECC) encoder14, a Run Length Limited (RLL) encoder16, a channel encoder(s)18, an Interleaver precoder20, head media22, front end and timing element24, a channel detector26, an outer decoder28, an RLL decoder30and an RS ECC decoder32.

Generally, RS codes are linear block codes, meaning that they can be processed all at once as blocks of data. The RS algorithm takes data words, splits them up into code words, and adds redundant parity bytes in order to correct symbol errors. RS codes are written as RS(N, K) where there are k data symbols in each n symbol codeword. This means that there are N-K parity symbols in each codeword and the RS algorithm can correct up to (N-K)/2 symbol errors in each codeword.

The RLL codes are codes that are limited by the number of flux changes that can be written in a given amount of disc area. In other words, RLL techniques limit the distance (run length) between magnetic flux reversals on the discs surface. By limiting the run length, the RLL coding technique defines the size of the data block that can be written within a given amount of disc space.

When data is presented to the system10for transmission over the inner subchannel12, the RS ECC encoder14encodes the data and passes the RS encoded data to an RLL encoder16. The RLL encoder encodes the RS encoded data and passes the RLL encoded data to a channel encoder18. The channel encoder18encodes the RS encoded data for the channel12and passes the encoded data to an interleaver precoder20, which reorders the coded data. Finally, the head media22writes the data to the inner subchannel12.

Encoded data is read from the inner subchannel12of the disc by the heads media block22. The encoded data is then processed by some analog filters, such as a preamp (preliminary amplifier), a low pass filter (LPF) and other elements, a process that is sometimes referred to as “front-end processing”. The filtered signal is then sampled using timing circuitry. InFIG. 1, the filtering and sampling elements are indicated by the front end and timing element24.

The data is then passed to a channel detector26and to an outer decoder28. The outer decoder28decodes the encoded data into RLL encoded data The RLL encoded data is then decoded by the RLL decoder30and passed to an RS ECC decoder32for decoding into the originally transmitted data.

The read/write channels of magnetic and/or optical disc drives include a number of different encoding/decoding circuits, each encoding or decoding data in different manners for different purposes. The various circuits shown in the blocks ofFIG. 1can be implemented as integrated circuits, discrete components, or suitably programmed processing circuitry. Additionally, while the discussion has included references to head media, other devices may be utilized to write data to a channel and to read data from the channel, such as a transceiver.

In general, the system10utilizes a combinatorial object called a separator matrix S, for stuffing separator bits between coded bits of the input data word. The separator matrix S is a matrix of size L×m and consists of binary elements 0 and 1. Generally, the separator matrix S is defined by two sets of positive integer parameters:
n1, n2, . . . , nl, and
v0, v1, . . . , vl.
where n=n1+n2+ . . . +nl.

FIG. 2shows the generic structure of the separator matrix S. As shown, the matrix S is partitioned by l−1 boundaries34into l submatrices S1, S2, . . . , Slof size L×n1, L×n2, . . . , L×nl, respectively. The matrix S is called the (v0, v1, . . . , vl)-separator matrix if 1) each submatrix Si, of 1≦i<l consists of nonzero rows, or in other words each row of S consists of l nonzero separators s1, s2, . . . , sl; 2) each line of S has at most v0consecutive leading zeros, and at most v1consecutive trailing zeros; and 3) each line of S has at most viconsecutive leading zeros at the i-th boundary 1≦i<l−1. Specifically, in each row of the matrix S, the total number of consecutive zeros at the left and right sides of the i-th dotted vertical line is not greater than v;, and this inequality is satisfied at all l−1 boundaries and for all rows of the separator matrix.

FIG. 3illustrates an embodiment of the separator matrix S. In this embodiment, the separator matrix S has the following parameters:

where M is the number of rows, n is the number of columns, and l is the number of separators in each row. Each code word (n1, n2, and n3) has two bits, and v0=v1=v2=v3=1.

A generic RLL encoding scheme using the (v0, v1, . . . , vl)-separator is constructed as follows. First, the input data word consisting of N bits is split into l+2 parts D0, D1, . . . , Dl+1of lengths N0, N1, . . . , Nl+1, respectively. The first l+1 data parts D0, D1, . . . , Dl+1are placed directly into the output code word without encoding as shown in FIG.4.

The last data part Dl+1is sent to the m/n encoder36that converts m input bits into one of the rows of the separator matrix S. Thus, the output of the m/n encoder is a binary word of length n. It consists of l separators s1, s2, . . . , slof length n1, n2, . . . , nl, respectively, and created by the boundary lines34shown in FIG.2.

Finally, the output of the m/n encoder is split into parts, which are then stuffed between the first l+1 data parts in the output code word. The resulting n coded bits satisfy the k-constraint, which requires no more than k consecutive zeros in the bit sequence.

With this encoding technique, the maximum number of consecutive zeros between any two consecutive ones in a coded sequence is not greater than 1) N1+v0+vl+1+N0(at the left and right boundaries of the codeword); 2) vi+Ni(between separator components siand si+1, 1≦i<l); or 3) k0(the maximum number of consecutive zeros within the separators si). Here, k0is less than ni−2, where i is greater than 1 and less than l (e.g. 1≦i<l). When the lengths niare small numbers, the constraint k0is usually defined only by the first two conditions given above.

By separating the data bits with coded data (e.g. by “code stuffing”), bit errors are contained between separator blocks. More specifically, bit errors are prevented from propagating throughout the bit sequence, thereby minimizing transmission errors by limiting them to a particular block. In this instance, an error in encoded block si would effect only the subblock si, but not the data blocks Di.

FIG. 5illustrates an embodiment of the system10having an RLL encoder16, an Interleaver (permuter)20, and a channel38. As shown, input word {right arrow over (x)} is passed to the RLL encoder16. The RLL encoder16encodes the input word {right arrow over (x)} into an RLL encoded word {right arrow over (y)}. The RLL encoded word {right arrow over (y)} is then passed to the Interleaver (permuter)20, which produces an output word {right arrow over (z)}. The output word {right arrow over (z)} is then passed onto the channel38. The channel38may be the inner subchannel12(as shown in FIG.1), a communication link between a transmitter and a receiver, or any kind of communication or transmission channel, including magnetic recording channels.

Generally, the permuter20changes the positions of the components in {right arrow over (y)} in a random manner to facilitate the operation of iterative detection scheme shown in FIG.1. Additionally, the permuter20must preserve the operation of the RLL encoder16. Specifically, the permuter20operates in the subblocks rather than on the entire codeword all at once. In this way, the resulting output sequence {right arrow over (z)} satisfies the same or similar constraints as its input sequence {right arrow over (y)}.

The structure and properties of the output codeword {right arrow over (y)} allows the permuter20to preserve the k-constraint at its output while performing permuting operations, such as swapping any two data blocks (Diand Dj) within the output codeword {right arrow over (y)} without shifting the boundaries between the two data blocks if Diand Djhave the same length or swapping any two separators siand sjin D0=[x1, x2, . . . , xN0] without shifting boundaries between blocks if siand sjhave the same length.

As shown inFIG. 6, K data bits40are passed through permuter A42(for the first l data bits) and through permuter B44(for the l+1 data bit) to produce the output codeword46. When the RLL encoder16performs swapping operations, the permuter A42swaps data blocks Di, and permuter B44swaps the separators si. Thus, none of these swapping operations changes the k-constraint provided by the RLL encoder16. Thus, the k-constraint is preserved in the proposed scheme combining the RLL encoder16and permuter20.

A number of pseudo-random and structured permuters are capable of separately shifting the data blocks and the separator blocks in an encoded bit sequence, so as to encode the signal without unwanted shuffling of the coded bits. Thus, the technique can be used in the magnetic recording channels, and other storage and communication systems facilitating the operations of the iterative detection schemes with soft decisions, such as Turbo codes, Low Density Parity Check (LDPC) codes and Turbo-Product Codes (TPC).

FIG. 7illustrates a RLL encoder16with a code rate of 32/33 and a k-constraint of k=12. In other words,FIG. 7shows a (0,12) RLL code with rate 32/33. In this embodiment, the input word of the RLL encoder consists of four bytes and is encoded into a code word of length 33.

As shown, the 32 data bits are split into five parts Di(specifically D0, D1, D2, D3, and D4) of lengths Ni(N0=4, N1=8, N2=8, and N3=5), a (m=N4=7), respectively. The first four data parts are directly placed in the output code word without encoding. The last 7 data bits D4are sent to the 7/8 encoder36. The output of the 7/8 encoder36is three nonzero separators s1, s2, and s3of lengths n1=3, n2=3 and n3=2, respectively. In this case, the first twenty four data bits are placed in the output code word without encoding at positions0-3,7-14,18-25and29-33, respectively. The separators s1,s2,s3are inserted between the uncoded data parts D0, D1, D2, and D3at positions 4-6, 15-17, and 26-28, respectively.

None of the separators s1,s2,s3consists of all zeros. Specifically, separators s1and s2take nonzero values from the following range of values: (0,0,1); (0,1,0); (0,1,1); (1,0,0); (1,0,1); (1,1,0); and (1,1,1). Separator s3takes a nonzero value from the following range of values: (0,1); (1,0); and (1,1). Thus, there are 147 words (7×7×3=147) of length 8, which can be used as output codewords of the 7/8 encoder36.

In this example, the maximum number of consecutive zeros in the coded bit stream is not greater than 12. At the left boundary, data block D0has 4 bits (4 possible zeros) and separator bit s1has 3 bits (2 possible zeros). At the right boundary, data block D3has 5 bits (5 possible zeros) and separator block s3has 2 bits (1 possible zero). Thus, the maximum number of consecutive zeros at the boundaries is 12.

Between s1, and s2, the maximum number of consecutive zeros is also 12, corresponding to the 2 possible zeros from each of s1and s2, and the eight bits (8 possible zeros) associated with data block D1. Between s2and s3, the maximum number of consecutive zeros is 11, corresponding to the 2 possible zeros from s2, the two bits (1 possible zero) from s3, and the eight bits (8 possible zeros) associated with D2. Therefore, the constructed code has the parameter k=12.

This example demonstrates that an additional bit could be included without altering the zero constraint k. Specifically, by including an extra data bit in the part D2, it is possible to increase the length of the output code by one bit, resulting in a 33/34 RLL code with k=12 for all portions of the data stream.

The 7/8 encoder/decoder can be implemented based on simple integer arithmetic. For example, each input bit u=(u0, u1, . . . , u6) of the 7/8 encoder can be represented as an integer I=0, 1, 2, . . . , 127, using the following equality:I=i⁡(u)=∑i=06⁢⁢ui·26-i
As discussed above, there are 147 possible output words of length 8 with three nonzero separators s1, s2, and s3, and any 127 of them can be used to encode the final seven input data bits.

To form the encoder, let delta (Δ) be a predefined constant (0≦Δ≦20), and J=I+Δ. In this example, the integer J satisfies the following inequality:
Δ≦J≦127+Δ<147.
By altering the parameter delta (Δ) within the defined range, it is possible to produce 21 different versions of the encoder using the following encoding steps.

The decoding algorithm for the 7/8 decoder is constructed as follows.

Given codewords (c1, c2, and c3), the integer J is reconstructed using the following equality:
J=21*i(s1)+3*i(s2)+i(s3),
where i(s) is an integer represented by the binary word Si.

Subtracting Δ from J gives the integer I. The binary representation of I is then sent to the output of the decoder (7 bits).

The 7/8 encoder/decoder described below effectively suppresses error propagation. To encode data using the 7/8 encoder36, first the input data bits are split into three parts (a, b, and c) of lengths 3 bits, 3 bits and 1 bit, respectively. The input of the 7/8 encoder is a, b, and c. The output 8 bits are also represented by three parts (s1, s2, and s3) of length 3 bits, 3 bits, and 2 bits. The output 8 bits are calculated as follows.

To decode a received encoded signal, the 7/8 encoder/decoder36divides the input codeword into three parts (s1, s2, and s3) having 3 bits, 3 bits and 2 bits, respectively. The output codewords of the decoder36consist of three parts â, {circumflex over (b)} and ĉ of lengths 3 bits, 3 bits and 1 bit, respectively. The output codewords are calculated as follows.

Case 2 (7/8 Decoder). If s3=(1,1) and s2∈{(001),(010)}, thena) â=s1,b) {circumflex over (b)}=(000), andc) ĉ is equal to the last component of s2.

Case 5 (7/8 Decoder). If s3=(1,1), s2=(100), and s1∈{(100),(011)} thena) â=(000),b) {circumflex over (b)}=(000), andc) ĉ is equal to the last component of s1.
Thus, the system10divides the input codeword into several parts, each part being composed of data bits. The last part is passed to the 7/8 encoder/decoder36, which utilizes the last portion of the input codeword to generate separator codes for stuffing between the other parts, which are inserted into the output codeword without encoding. The resulting output codeword is constrained such that the maximum number of consecutive zeros is determined by the k-constraint. Here, no more than 12 consecutive zeros is possible.

InFIG. 8, a (0,13) RLL code with rate 48/49 is illustrated. In this instance, the input codeword of the encoder36consists of 48 bits, and is encoded into an output codeword of length 49.

The last 10 data bits illustrated as D5are passed to the 10/11 encoder, which uses D5to produce an output consisting of four separators, s1,s2,s3, and s4. The output separators s3,s2,s3, and s4have lengths n1=3, n2=3, n3=3 and n4=2, respectively.

None of the separators s1,s2,s3, and s4consists of all zeros. Each separator s1,s2, and s3takes one of the following seven nonzero values: (0,0,1); (0,1,0); (0,1,1); (1,0,0); (1,0,1); (1,1,0); and (1,1,1). The separator s4takes one of three nonzero values: (0,1); (1,0); and (1,1). Therefore, there are total 1,029 words (7*7*7*3=1,029) of length 11 that can be used as output codewords of the 10/11 encoder36. These codewords form the rows of the separator matrix of size 1029×11 with the following parameters:
M=1029, n=11, l=4,
n1=n2=n3=3, n4=2,
v0=2, v1=v2=4, v3=3, and v4=1,
and any one of the 1024 of them may be used to construct the 48/49 RLL code with k=13.

In this example, the maximum number of consecutive zeros in the coded bit stream is not greater than 13. At the left boundary, data block D0has 5 bits (5 possible zeros) and separator block s1has 3 bits (2 possible zeros). At the right boundary, data block D4has 5 bits (5 possible zeros) and separator block s4has 2 bits (1 possible zero). Thus, the maximum number of consecutive zeros at the boundaries is 13.

Between s1and s2, the maximum number of consecutive zeros is 13, corresponding to the 2 possible zeros from each of s1and s2, and the 9 bits (9 possible zeros) associated with data block D1. Between s2and s3, the maximum number of consecutive zeros is 13, corresponding to the 2 possible zeros from each of s2and s3, and the 9 bits (9 possible zeros) associated with D2. Between s3and s4, the maximum number of consecutive zeros is 13, corresponding to the 2 possible zeros from s3, to the 1 possible zero from s4, and to the 10 bits (10 possible zeros) associated with D3. Therefore, the constructed code has the parameter k=13.

The input blocks D5of the 10/11 encoder36consists of 10 bits, which are represented by an integer I=0, 1, 2, . . . , 1023. Here, there are 1,029 possible codewords of length 11 bits. Each codeword consists of four nonzero separators (s1, s2, s3, and s4), and 1024 of these words can be used to encode the 10 data bits as follows. Let Δ be some predefined constant (0≦Δ<5), and J=I+Δ. By changing parameter Δ, it is possible to construct 5 different versions of the encoder as follows.

Given separators s1, s2, s3, and s4, the integer J can be reconstructed using the following formula:
J=147*i(s1)+21*i(s2)+3*i(s3)+i(s4),
where i(s) is an integer represented by binary word s.

Subtracting Δ from J results in I, the binary representation of which is passed to the output of the decoder (10 bits).

As with the 7/8 encoder, the 10/11 encoder produces separator blocks for insertion into the output codeword. The separator blocks serve to limit error propagation during transmission. In this embodiment, the system10divides the input data bits into four parts (a, b, c, and d). The 11 output data bits are also partitioned into four corresponding parts (s1, s2, s3, and s4) of lengths n1=n2=n3=3 and n4=2 bits. Depending on the bits in the four input parts (a, b, c, and d), the output bits are calculated as follows.

Case 2. If a≠0, b=0, and c≠0, thena) s1=a;b) s3=c;c) s4=(1,1).
and s2is defined by a and d according to the following replacement Table 1.

Case3. If a=0, b≠0, and c≠0, thena) s2=b;b) s3=c;c) s4=(1,1), andd) s1is defined by b and d according to the following replacement

Case 4. If a=0, b=0, and c≠0, thena) s3=c;b) s4=(1,1); andc) s1and s2are defined by d according to the following replacement Table 3

Case 5. If a≠0, b≠0, and c=0, thena) s1=a;b) s3=b;c) s4=(1,1), andd) s2is defined by a and d by the following replacement Table 4.

Case 6. If a=0, b≠0, and c=0, thena) s4=(1,1), andb) s1, s2, and s3are defined by a and d according to the following replacement Table 5.

Case 7. If a≠0, b=0, and c=0, thena) s4=(1,1), andb) s1, s2, and s3are defined by a and d by the following replacement Table 6.

Decoding of a received encoded signal operates similar to the decoding of a 7/8 encoded signal as described with respect toFIG. 7above. To decode a received encoded signal, the 10/11 encoder/decoder36divides the input codeword into four parts (s1, s2, s3, and s4) having 3 bits, 3 bits, 3 bits, and 2 bits, respectively. The output codewords of the decoder36consist of four parts â, {circumflex over (b)}, ĉ and {circumflex over (d)} of lengths 3 bits, 3 bits, 3 bits, and 1 bit, respectively. The output words are calculated as follows.

Case 2. Let T1(i) be the last three bits of the i-th row of Table 1. If s3=(1,1) and s2=T1(a0), thena) â=s1;b) {circumflex over (b)}=(000);c) ĉ=s3; andd) {circumflex over (d)} is equal to the last bit of s2, if a0≠4; and is equal to the second bit of s2, if a0=4.

Case 3. Let T2(i) be the last three bits of the i-th row of Table 2. If s3=(1,1) and s1=T2(b0), thena) â=(000);b) {circumflex over (b)}=s2;c) ĉ=s3;d) {circumflex over (d)} is equal to the second bit of s1, if b0>1; and is equal to the last bit of s1, if b0=1.

Case 4. If (a0=7 and b0=5), or (a0=6 and b0=7), thena) â=(000);b) {circumflex over (b)}=(000);c) ĉ=s3;d) {circumflex over (d)} is equal to the second bit of s2.

Case 5. Let T4(i) be the last three bits of the i-th row of Table 4. If s4=(1,1) and s4=T2(a0), thena) â=s1;b) {circumflex over (b)}=s3;c) ĉ=(000);d) {circumflex over (d)} is equal to the second bit of s2, if a0=6; and is equal to the last bit of s2, if a0≠6.

Table 7 is used for decoding in cases 6 and 7 below. Let t7(i) and T7(i) represent the first and the last three bits of the i-th row of Table 7, respectively, and let

While decoding has been described mathematically above, it is important to understand that the system10preserves the main portion of the data bits “as is”, encoding only a part of the data bits for use as separator blocks. Thus, the main portion of the data bits can be permuted by the channel interleaver20, arbitrarily, and without violating the k-constraint. The channel interleaver20may also permute the separator blocks formed from the part of the data bits without violating the k-constraint. Specifically, the channel interleaver20may permute the data bits and the separator blocks without altering the maximum number of consecutive zeros defined by the k-constraint. Thus, the system10may be utilized with various types of iterative detection schemes based on turbo codes, LDPC codes, and other similar coding schemes. Moreover, the separator blocks limit error propagation.

FIG. 9-17illustrate the BER and SFR characteristics of the 48/49 RLL code with k=13 construct by stuffing of 4 separators in the data stream.FIG. 9shows a graph of the bit error rates (BERs) before and after the RLL decoder of the present invention and before Error Correction Coding. Using a code rate of 48/49 with a k-constraint of 13, and a GPR target of length 5 and an ND of 2.5 (and no jitter), the system10provided an output code before and after the RLL decoder with a very small error propagation. Specifically, the before and after RLL lines are almost on top of one another.

FIG. 10illustrates the BERs of the same RLL code before and after decoding with a conventional RLL decoder. As shown, bit errors are propagated by conventional RLL decoders. Specifically, the before RLL and after RLL graph lines do not overlap, and the after RLL decoder graph line shows a higher bit error rate than the line showing the signal before the RLL decoder is used.

FIG. 11illustrates the conventional RLL code as compared with the RLL code of the present invention. Both the conventional and the new RLL code have a code rate of 48/49 and a k-constraint of 13. As shown, with no jitter, the new RLL code of the present invention has a better sector failure rate than the conventional RLL code, particularly at higher signal to noise ratios.

For example, at a signal to noise ratio of 19, the new RLL code has a sector failure rate of 2×10−8as compared to 8.5×10−8of the conventional RLL code. In data storage and retrieval systems, such error rate improvements are significant.

FIGS. 12 and 13illustrate the BERs of the new RLL code as compared with the conventional RLL code, both before and after the RLL decoder. As shown, both the new and the conventional RLL codes tested had a code rate of 48/49, a k-constraint of 13, a GPR target of length 5, a ND of 2.5, and 50/50 jitter. InFIG. 12, the BERs before and after RLL decoding are almost identical, indicating that there is very little error propagation during the decoding process. InFIG. 13, by contrast, there is a visible difference between the graphs showing before and after RLL decoding. Specifically, at every data point, the line showing after RLL decoding is visibly worse than the graph of the before RLL decoding. At a signal to noise ratio of 12, for example, the bit error rate is 2.5×10−2before the RLL decoder versus 3×10−2after the RLL decoder.

FIG. 14illustrates the sector failure rates of the conventional RLL code versus the new RLL code of the present invention. Here, the code rate was 48/49 and the k-constraint was 13. The data was written in a longitudinal channel with a GPR target of length 5. Noise consisted of 50% jitter and 50% electronic noise. As shown, the sector failure rates are approximately the same between the conventional RLL code and the RLL code of the present invention, and at high signal to noise ratios (such as 20), then RLL code of the present invention slightly out-performs the conventional RLL code. It is significant that the RLL code of the present invention performs as well as the conventional code with respect to the sector failure rate, since noticeable degradation in the sector failure rate would be intolerable.

FIGS. 15 and 16illustrate the BERs of the new RLL code as compared with the conventional RLL code, before and after decoding using the RLL decoder in perpendicular magnetic recording. In both cases, the RLL code had a code rate of 48/49 and a k-constraint of 13.FIG. 15once again demonstrates a very small error propagation between the before and after graphs of the invented code. By contrast,FIG. 16shows a visible separation between the graphs of the BER before and after RLL decoding.

FIG. 17illustrates the sector failure rate of the conventional RLL codes and the RLL codes of the present invention, with a code rate of 48/49 and a k-constraint of 13. Here, the sector failure rates are approximately equal, with the RLL code of the present invention slightly outperforming the conventional RLL code at a signal to noise ratio between 18.5 and 19.5.

The code stuffing technique of the present invention, while described with respect to 7/8 and 48/49 encoders, may be implemented using other code rates and with different encoders. Regardless of the encoder and the code rate, the system10divides the input codeword into parts and encodes one of the parts to form separator bits for stuffing between the remaining, unencoded parts of the input code word to form an output code word. This allows for the use of Interleavers/permuters for randomly reordering the bits, without effecting the k-constraint and without allowing errors to propagate throughout the output codeword.