Abstract:
High speed communication networks divide data traffic into multiple physical lanes. For example, the IEEE standard 40G/100G supports sending Ethernet frames at 40/100 gigabits per second over multiple 10/25 Gb/s lanes. Techniques are disclosed for aligning the data across the physical lanes.

Description:
1. PRIORITY CLAIM 
       [0001]    This application claims priority to U.S. application Ser. No. 13/655,748, filed 19 Oct. 2012 which claims priority to U.S. Provisional Application No. 61/617,365, filed 29 Mar. 2012, both of which are herein incorporated by reference in their entirety. 
     
    
     2. TECHNICAL FIELD 
       [0002]    This disclosure relates to high speed computer networks that send data over multiple different physical channels. 
       3. BACKGROUND 
       [0003]    High speed communication networks divide data traffic into multiple physical lanes. For example, the IEEE standard 100G supports sending Ethernet frames at 40 and 100 gigabits (Gb/s) over multiple 10 Gb/s or 25 Gb/s lanes. Aligning the data across the lanes at the receiver is significant challenge. 
     
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         [0004]    The innovation may be better understood with reference to the following drawings and description. In the figures, like reference numerals designate corresponding parts throughout the different views. 
           [0005]      FIG. 1  shows an example data pattern of an Align Marker (AM) block. 
           [0006]      FIG. 2  shows an example division of 24b segments of a marker pattern into six groups of bits, resulting in 12 total symbols. 
           [0007]      FIG. 3  shows a logic implementation for counting a total number of unmatched bits in a marker pattern. 
           [0008]      FIG. 4  shows a logic implementation for determining a total number of unmatched symbols in a marker pattern. 
           [0009]      FIG. 5  shows an example matching sequence for matching blocks in a scenario with four physical lanes and 20 virtual lanes of traffic. 
           [0010]      FIG. 6  shows logic in the form of a state transition diagram for matching alignment markers when the lock criteria is two consecutive matches. In this example, the first AM in each AM-FEC block is checked to determine block match, where an AM-FEC block is an FEC block that contains a group of Alignment Marker (AM) blocks. 
           [0011]      FIG. 7  shows a matching sequence for matching block, also in a scenario with four physical lanes and 20 virtual lanes of traffic. In this example, the destination checks the first and the third AM blocks in each group of five AM blocks for matches. 
           [0012]      FIG. 8  shows logic in the form of a state transition diagram for matching alignment markers when the lock criteria is three consecutive matches. 
           [0013]      FIG. 9  shows an example matching sequence. In this example, the destination has checked for and found a match against the first three AM blocks in the current AM-FEC block. 
           [0014]      FIG. 10  shows an example matching sequence. In this example, the destination found a first match at the fourth AM block in the current AM-FEC block. 
           [0015]      FIG. 11  shows logic in the form of a state transition diagram for matching marker patterns in alignment markers. 
           [0016]      FIG. 12  shows an example of dividing the marker pattern into two bit symbols. 
           [0017]      FIG. 13  shows an example of dividing the marker pattern into twelve bit symbols. 
           [0018]      FIG. 14  shows an example of a system that may implement alignment over one or more physical lanes. 
       
    
    
     DETAILED DESCRIPTION 
       [0019]    Described below are techniques for efficient alignment of data over multiple physical lanes. Such techniques may be applied to high speed communication networks, such as those adhering to the IEEE standard 1000 (4X25G) backplane and copper cable systems, and other types of networks. More generally, the techniques may be applied to aligning data sent by any source communication system in which multiple communication channels each carry a portion of the original data to a destination system. 
         [0020]    Some of the examples below assume an input bit-error-rate (BER) that is relatively high, e.g., BERin=2e−5. However, the analysis may be done for any other BER. The analysis results may then be a parameter that drives selection of an alignment technique that meets sufficiently low false alignment probabilities, mean time to lock, and worst case lock time. 
         [0021]      FIG. 1  shows an example data pattern of an Align Marker block (AM)  100 . The AM block  100  includes two start bits  102 , and an eight byte (8B), 64 bit (64b) payload  104 . The start bits  102  may be a preselected pattern, e.g., “10” to flag the following 64b as part of an AM block. The start bits  102  may be omitted. Interleaved parity (e.g., BIP3 and BIP7) may also be present in the AM block  100 . 
         [0022]    Inside the AM block  100  is a marker pattern. The marker pattern facilitates the alignment (sometimes also referred to as deskew) of the data sent over multiple lanes. The marker pattern may take many different forms and have many different lengths. In the example shown in  FIG. 1 , the marker pattern (MP)  106  is 6B or 48b, distributed over the bytes M0, M1, M2, M4, M5, and M6. Further, in the example shown in  FIG. 1 , the bytes M4, M5, M6 are the one&#39;s complement of the bytes M0, M1, M2. 
         [0023]    The MP  106  may have a fixed value per lane. The number of unique MPs may vary depending on the implementation. For example, for 100 Gb/s, there may be 4 physical lanes, each carrying  5  virtual channels, for 20 total channels of data. Each of the 20 channels may have a unique MP  106  that identifies that channel. In a 40 Gb/s system, there may be four lanes each carrying one channel of data, and 4 unique MPs. 
         [0024]    The source communication system inserts MPs periodically. For example, the communication system may insert MPs every 4,096, 16K, or other number of blocks (e.g., Forward Error Correcting (FEC) blocks) on each lane at the same time. This interrupts transmission of the source data, but adds the alignment information that the destination system will use to align the data sent over multiple different physical channels. Each physical channel has a latency that differs from other physical channels. Accordingly, a way to align the received data is needed. 
         [0025]    In some implementations, the alignment techniques may the M0, M1, M2, M4, M5, and M6 data of the MP  106 . Several different techniques for accomplishing this are described below. The techniques avoid finding an exact match for all 48b of the MP  106 , but still provide sufficiently robust false alignment probabilities, mean time to lock, and worst case lock time. Trying to find an exact match for all 48b of the MP  106  can, when input BER is relatively high, result in very long worst case lock times. 
         [0026]    As an overview, one technique for reducing lock time in the worst case at high BER is to tolerate some number of bit errors when matching a  48   b  MP within a  64   b  AM block  100 . For instance, the destination system may still recognize a “match” when the total number of unmatched bits between the incoming block and the template is less than a match threshold, such as 3 bits. On the other hand, once the bit error tolerance in the block match process is increased, the probability of false alignment may increase as well. To mitigate false alignment, the techniques described below may implement specific lock criterion. For instance, instead of claiming a lock after finding 2 consecutive matched blocks, the destination system may implement a lock criterion of claiming a match after finding 1 matched block, 2 consecutive matched blocks, 3 consecutive matched blocks, or any other number of consecutive or non-consecutive matched blocks. 
         [0027]    In one implementation, the techniques tolerate symbol errors instead of tolerating bit errors. Tolerating symbol errors may reduce the lock time when error propagation occurs. Symbol definitions at the destination system may vary. As examples, the destination system may consider a symbol to be a group of 2 consecutive bits, 3 consecutive bits, 4 consecutive bits, a group of 6 bits, a group of 8 bits, or some other predefined number of grouped bits. The bits in the symbol need not be consecutive bits from the MP  106 . 
         [0028]    Three examples of alignment techniques that the destination may implement are: 
         [0029]    Technique 1: Tolerating 4 bit errors in matching the 48b MP  106 ; 
         [0030]    Technique 2: Tolerating 3 half-byte errors in matching the 48b MP  106 ; and 
         [0031]    Technique 3: Tolerating 4 half-byte errors in matching the 48b MP  106 . 
         [0032]    With respect to  FIG. 2 , in technique 2, a 24b segment, such as segment  108  of M0, M1, and M2, and segment  110  of M4, M5, and M6 may be divided into 6 groups. Each group in this example is a four bit symbol. For example, the alignment technique treats M0, M1, and M2 as two symbols each formed from bits  0  to  3 , and  4  to  7 . In  FIG. 2 , the two symbols for M2 are labeled  202  and  204 . 
         [0033]    Technique 2 has less implementation complexity than technique 1.  FIG. 3  shows a logic implementation 300 for counting a total number of unmatched bits in the MP  106 . The logic implementation 300, for example, includes a logic section  302  that compares a template pattern (tm[i]) for the MP for which the destination is searching against the input bits (in[i]). The XOR logic  304  finds mismatches between the template and the input bits, and the summers  306  add up the total number of mismatches. A set of logic sections and cascaded summers  308  may be formed that span  48   b  across the input bits in a search for the MP template. The destination may search for any desired template patterns each time a new input bit is received that then shifts the current set of 48b by one bit. 
         [0034]    In comparison,  FIG. 4  shows a logic implementation 400 for determining a total number of unmatched symbols in the MP  106 . The logic implementation 400, for example, includes a set of logic sections  402  that compares a template pattern (tm[i]) for the MP for which the destination is searching against the input bits (in[i]). The logic section  402  determines, without using more complex adders, whether any four bit symbol is in error, because any bit in the set of four bits in the symbol does not match the template. 
         [0035]    False Alignment Probability 
         [0036]    Technique 1: 
         [0037]    Pfa=(nchoosek(48,4)*2̂−44)̂2=1.22e−16, indicating a mean time of 1.4e4 years for a false alignment for the 100 Gb/s case. 
         [0038]    Where Pfa refers to the false alignment probability, and nchoosek refers to n choose k, and  4  choose  48  is the number of ways to find four mismatched bits in a  48   b  MP pattern. The factor 2̂−44 (two to the power minus 44) represents the chance of matching  44  input bits against the remaining 44 bits in the MP template for which the destination is searching. Recall that the destination may search for two, three of any other number of consecutive matches before declaring a lock. In this example, the destination searches for two consecutive matched blocks, and thus the probability of finding two consecutive mismatched blocks is nchoosek(48,4)*2̂−44 squared. 
         [0039]    If the destination implements a lock criteria that is 3 consecutive matched blocks, then the probability of false alignment decreases to: 
         [0040]    Pfa=(nchoosek(48,4)*2̂−44)̂3=1.35e−24, indicating a mean time of 1.27e12 years for the 100 Gb/s case. 
         [0041]    Technique 2: 
         [0042]    Pfa=(nchoosek(12,3)*2̂−36)̂2=1.02e−17, indicating a mean time of 1.7e5 years for the 100 Gb/s case. 
         [0043]    If the destination implements of lock criteria that is 3 consecutive matched blocks, then the probability of false alignment decreases to: 
         [0044]    Pfa=(nchoosek(12,3)*2̂−36)̂3=3.28e−26, indicating a mean time of 5.2e15 years for the 100 Gb/s case. 
         [0045]    Technique 3: 
         [0046]    Pfa=(nchoosek(12,4)*2̂−32)̂2=1.32e−14, indicating a mean time of 130 years for the 100 Gb/s case. 
         [0047]    Mean Time of Lock 
         [0048]    The following discussion assumes a lock criteria of two successive matches, and an error propagation probability of 0.4. In other words, if there is a single bit error, there is a 40% of chance that there will be 2 consecutive bit errors. Below, the parameter ‘ei’ refers to input bit error rate (BER) at the input side of the block match process. Similar calculations may be done for any desired error propagation probability, and for other lock criteria. 
         [0049]    Technique 1: 
         [0050]    PI3=P(lock in 2 matches)=(1−nchoosek(44,1)*ei*0.4̂4))̂2=1−4.5e−5, where ‘ei’ denotes input bit error rate at the block match point. 
         [0051]    Mean time of lock=0.5+1*PI3+2*(1−PI3)*PI3+3*(1−PI3)̂3*PI3+ . . . , which is approximately 1.5+4.5e−5 group delays. 
         [0052]    If the destination implements a lock criteria that is 3 consecutive matched blocks, then: 
         [0053]    PI3=P(lock in 3 matches)=(1−nchoosek(44,1)*ei*0.4̂4))̂3=1−6.76e−5. 
         [0054]    Mean time of lock=1*PI3+2*(1−PI3)*PI3+3*(1−PI3)̂3*PI3+ . . . , which is approximately 1+6.76e−5 group delay, where one group delay is the time between two consecutive groups of AM blocks (see, for example,  FIG. 5 ). 
         [0055]    Technique 2: 
         [0056]    P(lock in 2 matches)=(1−2*3*ei*(0.4̂12+0.4̂11+0.4̂10+0.4̂9))̂2=1−1.0e−7. 
         [0057]    Mean time of lock is ˜=1.5+1.0e−7 group delay. 
         [0058]    If the destination implements a lock criteria that is 3 consecutive matched blocks, then: 
         [0059]    P(lock in 3 matches)=1−2.04e−7. 
         [0060]    Mean time of lock is ˜=1+2.04e−7 group delay. 
         [0061]    Technique 3: 
         [0062]    P(lock in 2 matches)=(1−2*2*ei*(0.4̂16+0.4̂15+0.4̂14+0.4̂13))̂2=1−1.7e−9. 
         [0063]    Mean time of lock ˜=1.5+1.7e−9 group delay. 
         [0064]    Lock Time in the Worst Case 
         [0065]    Below are some examples of calculating worst case lock time for realistic scenarios. Here, it is assumed that the system only checks for a block match of one AM block per group of AM blocks. 
         [0066]    Technique 1: 
         [0067]    The probability of not aligning in 5 groups is: 
         [0068]    (4.5̂−5)̂5=1.85e−22. 
         [0069]    One realistic worst case scenario is: 
         [0070]    ----v----x----v----x----v----x----v----x----v----v 
         [0071]    where ‘v’ indicates a block match, ‘x’ indicates no match, and the ‘----’ indicates data transmission between two consecutive groups of AM blocks. 
         [0072]    For this scenario, the longest lock time will be 10 group delays. 
         [0073]    Technique 2: 
         [0074]    The probability of not aligning in 3 groups is: 
         [0075]    (1.0̂−7)̂3=1.0e−21, which corresponds to a mean time of 1.7e9 years. 
         [0076]    One realistic worst case scenario is: 
         [0077]    ----v----x----v----x----v----v 
         [0078]    For this scenario, the longest lock time will be 6 group delays. 
         [0079]    Technique 3: 
         [0080]    The probability of not aligning in 2 groups is: 
         [0081]    (1.7̂−9)̂2=2.9e−18, which corresponds to a mean time of 5.9e5 years. 
         [0082]    One realistic worst case scenario is: 
         [0083]    ----v----x----v----v 
         [0084]    For this scenario, the longest lock time will be 4 group delays. 
         [0085]    The above analysis shows that with Technique 2, the worst case lock time is 6 group delays while for Technique 1, it is 10 group delays. 
         [0086]    Alignment Marker Match Sequence 
         [0087]      FIG. 5  shows an example matching sequence  500  for matching blocks in a scenario with four physical lanes  502 ,  504 ,  506 , and  508  and 20 virtual lanes of traffic. AM0, 4, 8, 12, 16 represents the five unique MPs that identify five virtual lanes of data traffic over the first physical lane  502 . AM1, 5, 9, 13, 17 represents the unique MPs that identify five more virtual lanes of data traffic over the second physical lane  504 . AM2, 6, 10, 14, 18 represents the unique MPs that identify five more virtual lanes of data traffic over the third physical lane  506 . AM3, 7, 11, 15, 19 represents the unique MPs that identify the last five virtual lanes of data traffic over the fourth physical lane  508 . 
         [0088]      FIG. 5  shows that the AMs are carried to the destination in lower layer protocol frames. In  FIG. 5 , the lower layer protocol frame is an FEC block, e.g., the FEC block  510 . The FEC block carries the AMs, but the much of the FEC block is source data  512 . Because the source data is spread across four physical lanes, and the lanes will have different latency characteristics, the destination searches for the marker patterns in the AMs to align the data across the lanes. Recall that FEC blocks may only include AMs on a periodic basis, such as once every 4,096 FEC blocks. Thus, only some FEC blocks include AM blocks. Those FEC blocks that include AM blocks are referred to as AM-FEC blocks. 
         [0089]    There are twenty different MPs that the destination may search for to find an initial match. In the example of  FIG. 5 , the destination has found an initial match  516  on the first AM position on the fourth physical lane  508 , which corresponds to AM3 and the fourth virtual lane. In the sequence  500 , once the destination finds an initial match, the match sequence may select a second check point  518  that is, for example, the also the first AM position in the next consecutive AM-FEC block  514  that carries AMs. 
         [0090]    If a match is found for the MP at the second check point  518  (thereby locating two consecutive MPs), then the destination may consider that a lock has been established for that lane. The destination may establish lock in the same way across all of the lanes, and once the relative alignment of the lanes is known, the destination may communicate data out of received data buffers for each lane at an offset for each lane that matches the alignment. 
         [0091]      FIG. 6  shows logic  600  in the form of a state transition diagram for matching AMs when the lock criteria is two consecutive matches. Starting from a reset or Out of Lock state, the logic  600  may determine whether there is a match on a MP in the next 64b block of data ( 602 ). If not, the destination is still Out of Lock. If there is a match, the logic  600  determines whether the first AM in the next AM-FEC is also a match ( 604 ). Note that in this example, only the first AM in each AM group is checked to determine block match. However, in other implementations, the second check may happen at whatever FEC block and MP and lane the match sequence has established. In other words, the second match need not always be a match against the first AM that was already matched in ( 602 ). If there is no second match, then the destination receiver is still Out of Lock. 
         [0092]    If there is a match at ( 604 ), then the destination may enter the Lock state, and continue to check for alignment. For example, the destination may continue to check for matches in the MP in AMs received in subsequent AM-FEC blocks ( 606 ). When there is no match, the logic  600  increments a mismatch count (UM_cnt) ( 608 ). 
         [0093]    When the mismatch count exceeds a pre-defined threshold ‘n’, e.g., 2, or 3, or 4, then the destination receiver may determine that Lock is lost, and transition to the Out of Lock state. Otherwise, if the destination is able to find a match, then it sets the mismatch count to zero, and continues checking. 
         [0094]      FIG. 7  shows a matching sequence  700 , also in a scenario with four physical lanes  502 ,  504 ,  506 , and  508  and 20 virtual lanes of traffic. In the example of  FIG. 7 , the destination checks the first and third AMs in the AM blocks for matches. In  FIG. 7 , the match sequence  700  has found a particular initial match  702  at the third AM block position (e.g., for AM11), and a consecutive match  704  at the first AM block position (e.g., for AM3) in the next group of AMs. In addition, the match sequence  700  has checked for and found a match at the non-sequential subsequent check point, namely the third check point  706 . The third check point  706  is the third AM position (recall that the destination, in this example, searches for matches at the first and third AM positions). As will be discussed in more detail below, more generally, the match sequence may search for any number of consecutive matches against any AM blocks that meets the chosen lock criteria. 
         [0095]      FIG. 8  shows logic  800  in the form of a state transition diagram for matching AMs when the lock criteria is three consecutive matches, and where the destination tries to match only against the first or the third AM in the AM-FECs. Starting from a reset or Out of Lock state, the logic  800  may determine whether there is a match on the MP for the first or the third AM in the next 64b block of data ( 802 ). If not, the destination is still Out of Lock. If there is a match on the first AM, the logic  800  determines whether the third AM in the same AM-FEC block is also a match ( 804 ). If there is no second match, then the destination receiver is still Out of Lock. If there is a match at ( 804 ), then the logic  800  may search for the third consecutive match ( 806 ). In particular, the logic  800  may determine whether the first AM in the next AM-FEC block that was analyzed at ( 804 ) is also a match. The destination must check the next AM-FEC block because the destination (in this example) only checks the first and third AMs in each AM-FEC. If there is no match, then the destination receiver is still Out of Lock. 
         [0096]    If there is a match at ( 806 ), then the destination may enter the Lock state, and continue to check for alignment. For example, the destination may continue to check for matches at any monitor point, such as against the MP for the first AM received in subsequent AM-FEC blocks ( 808 ). When there is no match, the logic  800  increments a mismatch count (UM_cnt) ( 810 ). When the mismatch count exceeds a pre-defined threshold ‘n’, e.g., 2, or 3, or 4, then the destination receiver may determine that Lock is lost, and transition to the Out of Lock state. Otherwise, if the destination is able to find a match, then it sets the mismatch count to zero, and continues checking. 
         [0097]    When it was the third AM that matched initially in ( 802 ), then the logic  800  may check for the next subsequent match against the first AM in the next AM-FEC block ( 812 ). The destination waits for the next AM-FEC because the destination only checks, in this example, for matches against the first and third AMs in any given AM-FEC block. If no match is found at the first AM in the next AM-FEC, then the destination is still out of lock. Otherwise, the destination attempts to match against the third AM in the same AM-FEC block ( 814 ) in which the second match was found at ( 812 ). If a match is found at ( 814 ), then the destination has established a lock. 
         [0098]    Alternative Alignment Marker Match Techniques 
         [0099]    The logic in the destination receiver may implement any of a wide variety of AM matching sequences, either more or less aggressive than the examples described above. More aggressive searches may lead to reduced mean time to lock or other performance benefits. One alternative is that once the logic has identified an initial match (e.g., the match  702 ), the logic may (more aggressively) check the next AM block in the received data sequence on the same physical lane and in the same AM-FEC block. As just three examples, the logic may handle: a) the current matched AM block is the number 3 or number 2 or number 1 AM block in the group; b) the current matched AM block is the number 4 AM block in the group; and c) the current matched block is the number 5 (i.e., the last AM block) AM group in the group. 
         [0100]    In case a, the logic may check for two consecutive AM block matches at any selected AM block positions which may be in the current AM-FEC block or subsequent AM-FEC blocks. In case b, the logic may check the next 64b block, and if it is a match to the next MP pattern, then check the first AM block in the next AM-FEC block for a match. In case c, after an initial match, the logic checks the first AM block in the next AM-FEC block, and may optionally check the second AM block in that next AM-FEC block if the 1st block is a match. 
         [0101]      FIG. 9  shows a matching sequence  900  for case a.  FIG. 9  shows that within the same AM-FEC block  510 , the more aggressive matching sequence finds a first match  902 , a second match  904 , and a third match  906 . In this example, the destination checked for and has found matches against the first three AMs in the current AM-FEC. Alternatively, the matching sequence could search for 2, 4, 5, or some other number of matches against any specified combination of AMs (not just the first three), or try to meet any other lock criteria. 
         [0102]      FIG. 10  shows a matching sequence  1000  for case b. As noted above for case b, the matching sequence  1000  finds an initial match  1002  at the fourth AM block position, and first subsequent match  1004  at the next (fifth) AM block position. The initial match  1002  and subsequent match  1004  are the fourth and fifth AMs in the AM-FEC block  510 . The matching sequence  1000  then searches for the third consecutive match in the next AM-FEC block  514 . That consecutive match is labeled as the third match  1006 , which is the first AM block in the next AM-FEC block  514 . 
         [0103]    These more aggressive examples illustrated in  FIGS. 9 and 10  help show that lock criteria may be flexibly established. A destination may implement any desired lock criteria at any particular point in time.  FIG. 11  provides a more general state diagram for determining when lock is met. 
         [0104]    In particular,  FIG. 11  shows logic  1100  in the form of a state transition diagram for determining when lock is achieved. The logic  1100  may search for consecutive matches within the same AM-FEC block where an initial match is found when there are more AM in that AM-FEC block. Further, these searches may bridge to a subsequent AM-FEC block when the current AM-FEC block has no further AMs to match against, or whenever the lock criteria specifies to search for a subsequent match in a different AM-FEC. 
         [0105]    The logic  1100  obtains a lock pattern ( 1102 ), e.g., established as a pre-programmed parameter or as a configuration parameter in a configuration file, as examples. The lock pattern may specify any or all of: which checkpoints (e.g., AMs) to match (which could be, e.g., any Boolean combination of AMs), where the checkpoints are located, the number and sequence of checkpoints to match, and the checkpoints to review for remaining in the lock state. For example, the lock pattern may be any of the examples given above. Some additional examples are: 
         [0106]    1) lock is achieved when this lock pattern is met: First match: AM3, current AM-FEC block; Second Match AM11, current AM-FEC block; Third match: AM15, current AM-FEC block; 
         [0107]    2) lock is achieved when this lock pattern is met: First match: AM3, current AM-FEC block; Second Match AM11, next AM-FEC block; 
         [0108]    3) lock is achieved when this lock pattern is met: First match: AM3, current AM-FEC block OR AM7 current AM-FEC block; Second Match AM11, next AM-FEC block OR AM15, next FEC block; 
         [0109]    4) lock is achieved when this lock pattern is met: First match: AM15, current FEC block; Second match: AM19, current FEC block; Third match: AM15, next FEC-block; Fourth match: AM19, next FEC-block. 
         [0110]    Thus, the logic  1100 , given the lock pattern, determines whether the next 64b of data match the first checkpoint in the lock pattern ( 1104 ). If so, the logic  1100  determines whether the lock pattern is complete ( 1106 ). If not, then the logic  1100  advances to the next checkpoint ( 1108 ) (e.g., to the next AM block and AM-FEC specified in the lock pattern). Then, the logic  1100  tries to find a match at that next checkpoint ( 1110 ). If there is not match, the destination remains out of lock. 
         [0111]    However, once all of the checkpoints in the lock pattern are matched, then the lock pattern is complete ( 1106 ). Once the lock pattern is complete, the destination enters the lock state. In the lock state, the destination checks the next monitor point for a match ( 1112 ). If a match is found, the destination remains in the lock state. However, if a match is not found ( 1114 ), then a counter is incremented, and further checks are made against any specified monitor points in the lock pattern. If the counter exceeds an out-of-lock threshold ‘n’, then the destination may determine that lock has been lost. 
         [0112]    Tolerating symbol errors leads to a better tradeoff between false alignment probability and worst lock time compared to tolerating bit errors in block matching. Tolerating 4 half byte errors per block can essentially guarantee lock in only 4 group delays. The false alignment probability is low, with about a mean time of 130 years. The techniques may use symbol sizes such as 2, 3, 4, 6, or 8 bits, or other sizes. 
         [0113]      FIG. 12  shows an example  1200  of dividing the MP into two bit symbols  1202 . Thus, for the six byte MP, there are 24 symbols that the destination receiver may try to match against, as opposed to the 12 half-byte symbols described above.  FIG. 13  shows an example  1300  of dividing the MP into 12 bit symbols  1302  that cross MP byte boundaries. Thus, for the six byte MP, there are 4 symbols that the destination receiver may try to match against, and tolerating some pre-determined number of symbols errors in the matching process. 
         [0114]      FIG. 14  shows an example of a system  1400  that may implement the techniques described above. The system  1400  may be a network switch, router, hub, or other part of the network fabric. The system  1400  may be implemented in any device that is a destination that receives data and performs data alignment, whether fixed or mobile. The system  1400  includes a communication interface  1402  (e.g., an Ethernet or other network interface), alignment logic  1403 , and a user interface  1408 . The user interface  1408  may display, for example, a graphical user interface  1410  and may accept data alignment parameters and display data alignment status. The alignment logic  1403  may be implemented in hardware, software, or both. In one implementation, the alignment logic  1403  is implemented in hardware state machines, to perform the processing noted above with regard to the state machine diagrams. Additionally or alternatively, the alignment logic  1403  may include a processor  1404  and a memory  1406 . The memory  1406  may store alignment instructions  1412  (e.g., program instructions) for execution by the processor  1404 . 
         [0115]    The alignment logic  1403  may implement the techniques described above with regard to any of  FIGS. 1-13 . Thus, in one implementation, the alignment instructions  1412  obtain data (e.g., the FEC blocks) from the communication interface  1402 , and store the data into data buffers for each lane of traffic.  FIG. 14  shows four lanes  1416 ,  1418 ,  1420 , and  1422  of data traffic received by the communication interface  1402  but there may be more or fewer lanes. 
         [0116]    The alignment instructions  1412  operate according to the alignment parameters  1424  to match AMs and decide when there is a lock. Examples of alignment parameters include the symbol definitions, e.g., the number of bits per symbol  1430 , lock criteria  1428  (e.g., 2 consecutive matches or 3 consecutive matches), match thresholds  1426  (e.g., whether the match process tolerates 3 symbol errors, 4 symbol errors, 4 bits errors, or some other threshold), the target lock delay (e.g., in terms of number of group delays), the desired false alignment probability, the number of consecutive matched blocks to find before declaring a lock, and other parameters that influence the operation of the alignment logic  1412 . All of these parameters may vary on a dynamic basis to suit the current configuration goals of the system  1400 . The alignment logic  1403  may communicate the lock condition to the user interface  1408  for display, may communicate the lock condition external to the system  1400 , or may provide the lock condition to other logic in the system  1400  to be used in subsequent processing stages. 
         [0117]    The techniques, methods, devices, and logic described above may be implemented in many different ways in many different combinations of hardware, software or both hardware and software. For example, all or parts of the techniques for matching or locking may include circuitry in a controller, a microprocessor, or an application specific integrated circuit (ASIC), or may be implemented with discrete logic or components, or a combination of other types of analog or digital circuitry, combined on a single integrated circuit or distributed among multiple integrated circuits. All or part of the techniques described above may be implemented as instructions for execution by a processor, controller, or other processing device and may be stored in a tangible or non-transitory machine-readable or computer-readable medium such as flash memory, random access memory (RAM) or read only memory (ROM), erasable programmable read only memory (EPROM) or other machine-readable medium such as a compact disc read only memory (CDROM), or magnetic or optical disk. Thus, a product, such as a computer program product, may include a storage medium and computer readable instructions stored on the medium, which when executed in an endpoint, computer system, or other device, cause the device to perform operations according to any of the description above. 
         [0118]    The processing capability of the system that implements the techniques may be distributed among multiple system components, such as among multiple processors and memories, optionally including multiple distributed processing systems. Parameters, databases, and other data structures may be separately stored and managed, may be incorporated into a single memory or database, may be logically and physically organized in many different ways, and may implemented in many ways, including data structures such as linked lists, hash tables, or implicit storage mechanisms. Programs may be parts (e.g., subroutines) of a single program, separate programs, distributed across several memories and processors, or implemented in many different ways, such as in a library, such as a shared library (e.g., a dynamic link library (DLL)). The DLL, for example, may store code that performs any of the system processing described above. 
         [0119]    While various embodiments have been described, it will be apparent to those of ordinary skill in the art that many more embodiments and implementations are possible. Accordingly, the techniques are not to be restricted except in light of the attached claims and their equivalents.