The present invention relates to a communication apparatus adaptable in an optical network of GE-PON (Gigabit Ethernet (registered trademark) Passive Optical Network) system. The present invention relates more particularly to a communication apparatus that can prevent frame mis-synchronization that occurs at a certain frequency when an FEC (forward error correction) function according to the IEEE802.3ah standard is realized.
The FEC system defined in the conventional GE-PON system (IEEE802.3ah (see Non-Patent Document 1)), as shown in
These code patterns for frame boundary identification (S_FEC and T_FEC) are added in front of and behind a frame and a parity during frame transmission and outputted to a communication partner apparatus. The receiving unit of the communication partner apparatus establishes frame synchronization (detection of a boundary between the frame and the parity) by detecting these code patterns for frame boundary identification. In IEEE802.3ah, a certain degree of error (in IEEE802.3ah, smaller than 5 bits) is allowed for these code patterns for the frame boundary identification during frame reception to protect code patterns for frame boundary identification not protected by the FEC function and prevent frame synchronization from being overlooked even when a frame propagates on a transmission channel with a high error rate.
Non-Patent Document 1: IEEE802.3ah, section 65.2.3
However, in the conventional FEC system of IEEE802.3ah, as explained above, because a certain degree of error is allowed for the code patterns for frame boundary identification in the receiving unit, even when a transmission channel is error free, as shown in
In
The present invention has been devised in view of the above. It is an object of the present invention to provide a communication apparatus that can reduce the probability of occurrence of misdetection of a T_FEC, which is located between a frame and a parity, without changing the allowable number of errors of a code pattern for frame boundary identification.
To solve the above-explaining problems, and to achieve the object, a communication apparatus realizes an FEC function and includes a T_FEC-pattern comparing unit that executes, for each of a plurality of detection windows provided at staggered times, processing for comparing an FEC frame defined in IEEE802.3ah as a reception frame and a T_FEC pattern as a pattern for boundary identification added during transmission and calculates code distances between patterns in the detection windows and the T_FEC pattern one after another; a code-distance comparing unit that compares the code distances calculated for each of the detection windows and detects, based on a result of the comparison, a code for boundary identification T_FEC between an IEEE802.3 frame and an FEC parity; and a boundary-signal generating unit that generates, based on a result of the detection, a T_FEC boundary signal as a signal indicating a detection position (a boundary) of the T_FEC in the FEC frame.
According to the present invention, there is an effect that it is possible to obtain a communication apparatus that can reduce the probability of occurrence of misdetection of the T_FEC compared with the same in the past.
Exemplary embodiments of a communication apparatus according to the present invention are explained in detail below based on the drawings. The present invention is not limited by the embodiments.
First Embodiment.
The T_FEC-pattern detecting units 11 and 12 shown in
The T_FEC-pattern detecting units 11 and 12 output respective code distances, which is obtained as a result of comparison of the input FEC frame and the T_FEC pattern, to the T_FEC-code-distance comparing unit 14 one after another. The T_FEC-code-distance comparing unit 14 compares the code distances received respectively from the T_FEC-pattern detecting units 11 and 12. For example, when the code distance received from the T_FEC-pattern detecting unit 12 is small and equal to or smaller than an allowable number of errors (in IEEE802.3ah, equal to or smaller than 4 bits) of a T_FEC, the T_FEC-code-distance comparing unit 14 notifies the T_FEC-boundary-signal generating unit 15 that a pattern detected by the T_FEC-pattern detecting unit 12 is a T_FEC.
The T_FEC-boundary-signal generating unit 15 generates and outputs a T_FEC boundary signal based on the information notified from the T_FEC-code-distance comparing unit 14. Specifically, the T_FEC boundary signal indicates a position (a boundary) of a T_FEC corresponding to the FEC frame that has passed the delay element 17.
Operations of the communication apparatus are explained below.
A state in which 4 bytes at a frame end and 2 bytes at a T_FEC front are in the detection window 11a of the T_FEC-pattern detecting unit 11 is shown in
A state in which the pattern that was in the T_FEC detection window 11a in
A state in which the T_FEC that was in the T_FEC detection window 11a in
As explained above, in this embodiment, two different but overlapping detection windows are employed and, a position of the T_FEC is judged after checking a T_FEC in an FEC frame and the patterns in front and behind the T_FEC. As a result, misdetection of the T_FEC will not occur if no error is included in the original T_FEC. Even if an error is included in the T_FEC of the FEC frame, misdetection of the T_FEC can occur only in a rare situation. That is, for example, when the code distance of a pattern obtained by combining 4 bytes at the frame end and 2 bytes at the T_FEC front and a code distance of the T_FEC pattern are equal and an error of the code distance of 4 bits occurs in the 4 bytes at the T_FEC end. In other words, misdetection of the T_FEC can occur only when the pattern obtained by combining the 4 bytes at the frame end and the 2 bytes at the T_FEC front and the T_FEC pattern coincide with each other at a code distance of 4 bits.
The above embodiment is explained by taking a T_FEC of 6 bytes (/T/R/K28.5/D29.5/T/R/) as an example; however, the same effect can be obtained even if the T_FEC is 6 bytes (/T/R/K28.5/D10.1/T/R/) or 7 bytes (/T/R/R/K28.5/D16.2(or /D5.6/)/T/R/).
Second Embodiment.
In the above embodiment, two T_FEC detection windows have been used. It is possible, however, to further reduce the probability of misdetection of a T_FEC by increasing the number of T_FEC detection windows to three. Processing different from that in the first embodiment described above is explained below.
Operations of the communication apparatus are explained below.
(I) For example, when the code distance is equal to or smaller than the allowable number (in IEEE802.3ah, equal to or smaller than 4 bits) in only the T_FEC detection window 11a, the T_FEC-code-distance comparing unit 19 does not notify detection of a T_FEC to the T_FEC-boundary-signal generating unit 15.
(II) When the code distance is equal to or smaller than the allowable number (in IEEE802.3ah, equal to or smaller than 4 bits) in only the T_FEC detection window 12a, the T_FEC-code-distance comparing unit 19 does not notify detection of a T_FEC to the T_FEC-boundary-signal generating unit 15.
(III) When the code distance is equal to or smaller than the allowable number (in IEEE802.3ah, equal to or smaller than 4 bits) in only the T_FEC detection window 13a, the T_FEC-code-distance comparing unit 19 judges that a pattern detected in the T_FEC detection window 13a is a T_FEC and notifies detection of the T_FEC to the T_FEC-boundary-signal generating unit 15.
(IV) When the code distances are equal to or smaller than the allowable number (in IEEE802.3ah, equal to or smaller than 4 bits) in both the T_FEC detection windows 11a and 12a, the T_FEC-code-distance comparing unit 19 does not notifies detection of a T_FEC to the T_FEC-boundary-signal generating unit 15.
(V) When the code distances are equal to or smaller than the allowable number (in IEEE802.3ah, equal to or smaller than 4 bits) in both the T_FEC detection windows 13a and 12a, the T_FEC-code-distance comparing unit 19 compares the code distance inputted from the T_FEC-pattern detecting unit 12 and the code distance inputted from the T_FEC-pattern detecting unit 13. When the code distance inputted from the T_FEC-pattern detecting unit 13 is smaller, the T_FEC-code-distance comparing unit 19 judges that a pattern detected in the T_FEC detection window 13a is a T_FEC and notifies detection of the T_FEC to the T_FEC-boundary-signal generating unit 15.
(VI) When the code distances are equal to or smaller than the allowable number (in IEEE802.3ah, equal to or smaller than 4 bits) in both the T_FEC detection windows 11a and 13a, the T_FEC-code-distance comparing unit 19 judges that a pattern detected in the T_FEC detection window 12a is a T_FEC and notifies detection of the T_FEC to the T_FEC-boundary-signal generating unit 15.
(VII) When the code distances are equal to or smaller than the allowable number (in IEEE802.3ah, equal to or smaller than 4 bits) in all the three T_FEC detection windows 11a, 12a, and 13a, the T_FEC-code-distance comparing unit 19 judges that a pattern detected in the T_FEC detection window 12a is a T_FEC and notifies detection of the T_FEC to the T_FEC-boundary-signal generating unit 15.
As explained above, in this embodiment, three different but overlapping detection windows are employed and, a position of the T_FEC is judged after checking a T_FEC in an FEC frame and the patterns in front and behind the T_FEC. Thus, it is possible to prevent misdetection in the cases of, for example, (VI) and (VII) above in which it is impossible to prevent misdetection of a T_FEC in the first embodiment.
Third Embodiment.
In the above embodiments, the probability of misdetection of a T_FEC is reduced by using a plurality of T_FEC detection windows. However, in this embodiment, misdetection of a T_FEC is prevented by using the relation between the frame length and the parity length.
The frame-boundary detecting unit 2 shown in
The S_FEC-pattern detecting unit 21 performs detection of coincidence of the FEC frame with an S_FEC pattern and, when a pattern having a code distance to the FEC frame equal to or smaller than the allowable number of errors (in IEEE8023ah, equal to or smaller than 4 bits) is detected, notifies detection of S_FEC to the frame-boundary-signal generating unit 24.
The T_FEC-pattern detecting unit 22 performs detection of coincidence of the FEC frame with a T_FEC pattern and, when a pattern having a code distance to the FEC frame equal to or smaller than the allowable number of errors (in IEEE802.3ah, equal to or smaller than 4 bits) is detected, notifies detection of T_FEC to the frame-boundary-signal generating unit 24.
The frame-boundary-signal generating unit 24 counts a frame length of an IEEE802.3 frame (a frame) from a S_FEC detection signal output from the S_FEC-pattern detecting unit 21 and a T_FEC detection signal output from the T_FEC-pattern detecting unit 22, and outputs the result of the counting, i.e., the frame length, to each of the parity-length checking units 23-1 to 23-n. Because it is possible that n (n is a natural number) T_FECs are detected in one FEC frame, the frame-boundary-signal generating unit 24 counts frame lengths of each of the n T_FECs and outputs result of the counting to a corresponding one of the n parity-length checking units 23-1 to 23-n in order.
Each of the parity-length checking units 23-1 to 23-n calculates a parity length by using Equation (1) below based on the frame length inputted from the frame-boundary-signal generating unit 24. Each of the parity-length checking units 23-1 to 23-n checks whether a pattern having a code distance equal to or smaller than the allowable number of errors (in IEEE802.3ah, equal to or smaller than 4 bits) is present behind the parity. For example, when a unit from among the parity-length checking units 23-1 to 23-n detects such a pattern, that unit notifies the frame-boundary-signal generating unit 24 “yes” and, when such a pattern is not detected, notify the frame-boundary-signal generating unit 24 “no”.
(Parity length)=[(frame length)]/239]×16(unit:byte) (1)
The fractions in the square brackets in Equation 1 are rounded up.
The frame-boundary-signal generating unit 24 judges that the frame lengths that are outputted by the parity-length checking units from which “yes” is received, i.e., positions of the S_FEC and the T_FEC between the frame and the parity, are correct and outputs an FEC frame boundary signal to a circuit at a post stage.
Operations of the communication apparatus are explained below.
For example, in
On the other hand, in
Actually, when misdetection occurs of a T_FEC, which is located between a frame and a parity, it means that a plurality of T_FECs are detected in one FEC frame. Therefore, when misdetection of a T_FEC occurs, the processing in
As described above, in this embodiment, the relation between a frame length and a parity length is checked to judge a position of a T_FEC. Thus, even when a T_FEC that should be correct has a specified code distance to a T_FEC pattern larger than that of a false T_FEC, which cannot be prevented in the first and the second embodiments, it is possible to prevent misdetection of the T_FEC. This makes it possible to reduce the probability of misdetection of a T_FEC more than the first and the second embodiments.
Fourth Embodiment.
In the above embodiments, the processing for deciding a position of a T_FEC is explained. However, in this embodiment, FEC decoding processing is applied to all possible candidates of a T_FEC and a candidate having a smallest number of error corrections during the FEC decoding is outputted to a circuit at a post stage. This configuration makes it possible to further reduce the probability of misdetection of a T_FEC.
The FEC-frame-boundary detecting unit 3 shown in
Misdetection of a T_FEC between a frame and a parity is often performed in 4 bytes (or 5 bytes) at the end of the frame and 2 bytes at the front of the T_FEC or performed in 2 bytes at the end of the T_FEC and 4 bytes (or 5 bytes) of the parity. A probability of detection of the T_FEC in the middle of the frame is not zero. However, in that case, because the frame has a pattern closer to the T_FEC from the beginning and an error needs to be added in a direction in which a code distance to the T_FEC is smaller on a transmission channel, the probability of occurrence is extremely small.
Consequently, in this embodiment, maximum three kinds of FEC frame boundary signals are outputted from the FEC-frame-boundary detecting unit 3 to the FEC decoding units 5-1 to 5-3, respectively. However, the number of FEC decoding units can be increased to cope with four or more FEC frame boundary signals.
The FEC-frame-boundary detecting unit 3 delays the inputted FEC frame by a certain time so that the inputted frame is synchronized with FEC frame boundary signals #1 to #3 and outputs the FEC frame.
The 10B/8B converting unit 4 converts the FEC frame inputted with a 10B code into a 8B code and outputs the result of the conversion to the FEC decoding units 5-1 to 5-3.
The FEC decoding units 5-1 to 5-3 separate the frame and the parity based on the FEC frame boundary signals, respectively, and outputs the numbers of error corrections obtained by this processing to the FEC-error-correction-number comparing unit 6.
The FEC-error-correction-number comparing unit 6 compares the numbers of error corrections outputted from the respective FEC decoding units and switches the selector 7 to output an output of the FEC decoding unit having the smallest number of error corrections to a circuit at a post stage.
As explained above, in this embodiment, the EC decoding processing is executed based on all the possible FEC frame boundary signals, and the result of the FEC decoding processing with the smallest number of error corrections is outputted to the circuit at the post stage. As a result, the possibility of misdetection of the T_FEC is eliminated by the use of the combination of the 4 bytes (or 5 bytes) at the end of the frame and the 2 bytes at the front of the T_FEC and the combination of the 2 bytes at the end of the T_FEC and the 4 bytes (or 5 bytes) at the front of the parity. In other words, it is possible to reduce the probability of misdetection of the T_FEC to a practically acceptable degree.
As explained above, the communication apparatus according to the present invention is useful for an optical network of the GE-PON system and, in particular, suitable as a communication apparatus in realizing an FEC function according to the standard of IEEE802.3ah.
Filing Document | Filing Date | Country | Kind | 371c Date |
---|---|---|---|---|
PCT/JP2006/312742 | 6/26/2006 | WO | 00 | 9/6/2007 |
Publishing Document | Publishing Date | Country | Kind |
---|---|---|---|
WO2008/001419 | 1/3/2008 | WO | A |
Number | Name | Date | Kind |
---|---|---|---|
6452991 | Zak | Sep 2002 | B1 |
7050373 | Tonami et al. | May 2006 | B2 |
7152199 | Nuyen et al. | Dec 2006 | B2 |
7343540 | Khermosh et al. | Mar 2008 | B2 |
7581155 | Lee et al. | Aug 2009 | B2 |
7586820 | Oki | Sep 2009 | B2 |
7600171 | Lee et al. | Oct 2009 | B2 |
7890840 | Khermosh et al. | Feb 2011 | B2 |
7917833 | Mizuochi et al. | Mar 2011 | B2 |
20050135803 | Lee et al. | Jun 2005 | A1 |
20070104225 | Mizuochi et al. | May 2007 | A1 |
20080260378 | Khermosh | Oct 2008 | A1 |
Number | Date | Country |
---|---|---|
0 626 771 | Nov 1994 | EP |
10-117190 | May 1998 | JP |
11-112489 | Apr 1999 | JP |
11-298467 | Oct 1999 | JP |
2001-197053 | Jul 2001 | JP |
2004 523955 | Aug 2004 | JP |
2005 524281 | Aug 2005 | JP |
10-2005-0061140 | Jun 2005 | KR |
102005-0092696 | Sep 2005 | KR |
Entry |
---|
IEEE Standard 802.3ah, 2004. |
Ariel Maislos, et al., “FEC in EPON Technical Proposal”, IEEE 802.3ah, XP002616684, URL:http://www.ieee802.org/3/efm/baseline/khermosh—general—1—0702.pdf, Jan. 18, 2003, 21 pages. |
Lior Khermosh, et al., “Frame FEC in EPON Technical Proposal”, XP002616683, URL:http://www.ieee802.org/3/efm/baseline/khermosh—fec—1—0902.pdf, Jan. 18, 2003, 11 pages. |
Supplementary Search Report issued Jan. 28, 2011, in European Patent Application No. 06767359.0-1237 / 2034657. |
Part 3: Carrier Sense Multiple Access with Collision Detection (CSMA/CD) Access Method and Physical Layer Specifications, IEEE Std 802.3R Evam/2.0-Section 5 Clause 65.2.3, pp. 1 and 311-324, 2004. |
Number | Date | Country | |
---|---|---|---|
20090254793 A1 | Oct 2009 | US |