The present invention relates to countermeasures that can be used to mitigate the effects of Stimulated Raman Scattering (SRS) that causes data transmission propagated at a first optical wavelength to interfere with broadcast video transmission propagated at a second optical wavelength in optical waveguides used in optical networks. More particularly described, the present invention relates to modifying idle transmission patterns or transmitting random data to a non-existent MAC address to decrease the SRS optical interference and improve the quality of video transmissions.
The Institute of Electrical and Electronics Engineers (IEEE) has defined the 802.3ah Ethernet in the First Mile (EFM) Point-to-Multipoint standard for Ethernet-based Passive Optical Networks (EPONs). These networks can act as optical access networks for residential and business subscribers, providing a full range of communications services to those users. Consistent with such deployments, the IEEE 802.3ah standard specifies optical wavelengths that leave room or capacity for communication services other than Ethernet, particularly broadcast video.
Unfortunately, key characteristics of Ethernet data transmission can cause significant optical interference to video signals through a phenomenon known as Stimulated Raman Scattering (SRS). The IEEE 802.3ah standard specifies that Ethernet data is transmitted to the subscriber using the 1490 mn optical wavelength. Wavelength division multiplexing (WDM) permits an optical network using the 1490 nm optical wavelength to propagate data to also deliver broadcast video on the same optical fiber using the 1550 nm optical wavelength. When the network transmits on two optical wavelengths simultaneously, such as the 1490 nm and 1550 nm wavelengths, it can be vulnerable to SRS. In IEEE 802.3ah EPON networks, the Ethernet signal transmitted at 1490 nm amplifies any video signal transmitted at 1550 nm, and therefore interference can result in a noticeable degradation of video quality. A particularly egregious case occurs when an Ethernet idle pattern is transmitted because no data is available to transmit. This causes extreme interference with broadcast video on certain channels.
SRS between optical signals can develop in the trunk fiber 160, and is a function of the signal levels and optical wavelengths used. The amount of SRS optical interference introduced is a complex function of the distance 170 to the split. Very short lengths of optical fiber are not susceptible to SRS, but trunk fibers 160 of practical length tend to be quite susceptible to SRS. The IEEE 802.3ah EFM standard specifies distances of 10 and 20 km, which can be all in the Trunk Fiber 160, or some portion can be after the split, in the drop fiber 150. The worst case situation is where all the fiber is in the trunk portion 160. The IEEE 802.3ah standard also specifies the signal levels to be used.
The curve plots the effect of SRS on an optical system carrying random data and also analog video. Better performance is reflected at higher points on the graph. The effect of random data is to worsen the carrier-to-noise ratio (C/N) of the received optical signal, to well below acceptable levels. The curve plots the C/N on each lower-frequency channel where the problem is the worst for a family of PONs of different practical lengths.
The figure also illustrates C/N limits for cable TV good engineering practice 220 and typical Fiber-to-the-Home (FTTH) typical performance absent SRS 210. If SRS causes the C/N to get significantly worse than the C/N without it 210, then the performance of the optical system will be degraded and users will not perceive the benefits that FTTH is supposed to offer. PONs with distances to the split 170 of 2 km 230, 5 km 240, 10 km 250 and 20 km 260 are shown. From this curve, one can see that a 2 km distance will not drop the C/N below cable TV good engineering practices 220, but it will be close at the lowest channel, and the performance will be worse than what a FTTH system should deliver. Longer PONs will cause unacceptable C/N performance on several channels.
One of ordinary skill in the art knows that a different selection of optical wavelengths could reduce or effectively eliminate the problem introduced by SRS. For example, other FTTH systems are known which use 1310 nm for bidirectional transmission of data. These systems are usually not troubled by SRS. However, the IEEE 802.3ah standard requires that downstream data be transmitted at 1490 nm, where the problem exists. It is possible to move the wavelength of the video transmission as high as possible in the 1550 nm window, but this will only result in slight improvement.
One of ordinary skill in the art is familiar with the specification for Gigabit Ethernet, which requires a prescribed bit pattern to be transmitted as an idle pattern when there is no data available to be transmitted. This method used in gigabit Ethernet and in certain other applications, is called 8B/10B encoding. The purpose of the 8B/10B encoding is to remove the low frequency dc component that digital optical systems are not able to transmit and to ensure clock synchronization to prevent the clock from wandering out of phase, which can damage data recovery. In 8B/10B encoding, for every 8 bits (one byte), a 10 bit code is substituted. The substituted 10 bit code is chosen to have very close to an equal number of 1s and 0s and three to eight transitions per symbol. The codes satisfy the requirement of no dc component in the signal, and the large number of transitions ensure clock synchronization. Furthermore, since a limited number of the available codes are used, the encoding provides another way to detect transmission errors.
The downside of 8B/10B encoding is that because 10 bits must be transmitted to represent 8 bits, the bandwidth required is increased by 25%. For instance, in a gigabit Ethernet system, the desired data is transmitted at 1 Gb/s, but because of 8B/10B encoding, the data rate on the fiber (the so-called wire rate) is 1.25 Gb/s. Furthermore, it has been found that when the idle pattern is transmitted and encoded with 8B/10B encoding, the resulting signal has strong power concentration at certain frequencies. These frequencies for Gigabit Ethernet happen to be at 62.5 MHz and all harmonics thereof, with the odd harmonics having virtually all of the power.
The IEEE 802.3ah standard defines two different idle codes. The first idle code, referred to as /I1/, has two versions. One version changes the running disparity on the link from positive (a preponderance of 1s—designated as /I1+/) to negative (a preponderance of 0s—designated as /I1−/), while the second version changes the running disparity from negative to positive. As known to one or ordinary skill in the art, the running disparity rules change the transmitted value from one column to the other based on certain rules related to the number of 1s or 0s that have been transmitted in the previous code group. These rules ensure that there is no dc content in the optical signal and that there is not a long string of like binary digits, thus ensuring reliable clock recovery.
The second idle code, referred to as /I2/, maintains the existing running disparity on the link. In a normal procedure for using these two idle codes the systems performs one of the following: (a) If, after the last transmitted frame, the link has a positive running disparity, the system transmits one /I1+/ to reverse the running disparity, and then transmits /I2/ continuously or (b) if, after the last transmitted frame, the link has a negative running disparity, the system transmits /I2/ continuously.
In view of the foregoing, there is a need in the art to mitigate the effects of SRS optical interference on video transmissions in optical networks that use the IEEE 802.3ah data standard. Particularly, a need exists in the art for reducing or substantially eliminating the optical interference between data transmitted on a first optical wavelength and video information transmitted on a second optical wavelength when the data and video information are propagated along the same optical waveguide.
The present invention can mitigate the effects of SRS optical interference in optical networks between data transmitted at a first optical wavelength, such as 1490 nm, and video information transmitted at a second optical wavelength, such as 1550 nm. Specifically, the present invention can substantially reduce or eliminate SRS optical interference produced by idle transmission patterns generated in accordance with the IEEE 802.3ah data standard that are propagated at 1490 nm and that can interfere with video information propagated at 1550 nm. The invention can reduce or substantially eliminate SRS optical interference in optical networks by modifying the idle transmission pattern or transmitting random data to a non-existent MAC address.
One exemplary aspect of an optical network system embodying the invention can be described as follows: Data signals can be received by a tap routing device from different data sources including telephone switches or internet routers. These data signals can then eventually be transmitted at a first optical wavelength to a plurality of subscriber optical interfaces which are located on the premises of subscribers. Video information such as broadcast video can be transmitted at a second optical wavelength along the same optical waveguide of the data signals to the plurality of subscriber optical interfaces.
For data sent to subscribers downstream along the optical waveguide according to a standard that requires idle patterns, such as the IEEE 802.3ah data standard, and when no data signals are being transmitted, the tap routing device can transmit ten-bit idle patterns downstream. An idle pattern replacement device can monitor the downstream data of the tap routing device in the electrical domain and can detect when the idle patterns are being transmitted. In response to the transmission of an idle pattern in the electrical domain or the absence of data, the idle pattern replacement device can generate substitute data in the electrical domain to replace the idle pattern that is produced according to the data standard, such as the IEEE 802.3ah standard. The substitute data in the electrical domain may then be converted into the optical domain and then transmitted at the first optical wavelength along with the video information at a second optical wavelength to the plurality of subscriber optical interfaces.
According to one exemplary aspect of the present invention, the idle pattern replacement device can generate substitute data in the electrical domain by generating non-repetitive random data and transmitting it to a non-existent MAC address. First, the idle pattern replacement device can create a predetermined Ethernet header based on a group of non-existent MAC addresses. Next, the idle pattern replacement device can generate forty bytes of random data. Finally, the cyclical redundancy check (CRC) can be calculated from the previously created Ethernet header and random data and the entire Ethernet frame can be transmitted to the optical transmitter. The optical transmitter can then convert data generated in the electrical domain into the optical domain for optical transmission over a waveguide. The generation of substitute data in the electrical domain can reduce any electrical interference between data and video signals in the electrical domain. And when the substitute data is converted to the optical domain, the substitute data can reduce any optical interference between data and video signals in the optical domain.
For another exemplary aspect of the invention, an idle pattern replacement device can reduce the effect of SRS between optical signals by modifying the normal idle transmission pattern. As previously discussed, SRS optical interference is caused by the repetition of the normal idle transmission pattern. In accordance with an exemplary aspect of the present invention, an alternative idle transmission pattern may be transmitted in the electrical domain to break up the normal idle transmission pattern of sending a repetitive pattern. The increased randomness of this pattern after it is converted to the optical domain can reduce the effect of SRS while still conforming to the specifications of the IEEE standard.
For another exemplary aspect of the invention, non-repetitive random data can be generated and then transmitted to a non-existent MAC address using an idle pattern replacement device comprising a CPU, a Layer 2 (L2) switch fabric, and an EPON chip. As is understood by one of ordinary skill in the art, L2 refers to the second layer of the ISO seven layer data transmission model, and specifically is where Ethernet is implemented. Ethernet implementations are usually done using a combination of hardware and software. The term “switch fabric” refers to the combination of hardware and software that allows data packets to be switched from one of a plurality of inputs to one of a plurality of outputs. In this aspect of the invention, the Ethernet frame data can be assigned an associated priority value. A CPU, or other special circuitry, can continuously transfer random data frames in the electrical domain to the L2 switch fabric with the lowest priority value. When the L2 switch fabric receives real data from the logic interface, data in the electrical domain can be immediately transferred to the tap routing device while the random data frames can be dropped. However, when the L2 switch fabric stops receiving real data and no data is being transmitted, the random data frames can be made available and can be transmitted to the tap routing device in place of the normal idle patterns. The optical transmitter that follows the tap routing device and tap multiplexer can convert any data in the electrical domain into the optical domain for optical transmission.
These and other aspects, objects, and features of the present invention will become apparent from the following detailed description of the exemplary embodiments, read in conjunction with, and reference to, the accompanying drawings.
The present invention relates to mitigating SRS optical interference between data propagated at a first optical wavelength and video information propagated at a second optical wavelength on the same waveguide. More specifically, the invention relates to improving the quality of video transmissions on a optical network by modifying idle transmission patterns or transmitting random data to a non-existent MAC address when data is transmitted according to a data standard at a first optical wavelength and when the video information is transmitted on a second optical wavelength.
In an exemplary embodiment of the present invention, an idle pattern replacement device can monitor the downstream data stream of a tap routing device in the electrical domain in order to detect the idle patterns that the routing device generates and that cause SRS optical interference between the optical data signals and optical video signals propagated at two different optical wavelengths. To mitigate the SRS optical interference, the idle pattern replacement device generates non-repetitive substitute data in the electrical domain to take the place of the previously generated repeating or constant idle patterns. The idle pattern replacement device accomplishes this goal by modifying the idle transmission patterns or transmitting random data to a non-existent MAC address. The substitute data of the idle pattern replacement device can be converted from the electrical domain to the optical domain and then optically transmitted to subscriber optical interfaces at a first optical wavelength that is different than a second optical wavelength used to carry video information.
Referring now to the drawings, in which like numerals represent like elements, aspects of the exemplary embodiments will be described in connection with the drawing set.
The logic interface 415 is also connected to a tap routing device 433. The tap routing device 433 can comprise a commercial chip that implements the IEEE 802.3ah standard by using 8B/10B encoding on the incoming data. Therefore, the tap routing device 433 can transmit idle code patterns when no data is received from the logic interface 415. Alternatively the 8B/10B encoding may be added at the tap multiplexer 430, as discussed below. The 8B/10B encoding process includes steps in which each 8-bit word of data is replaced with a specified 10-bit symbol. According to one exemplary embodiment, the tap routing device 433 sends the downstream data to a plurality of tap multiplexers 430. The tap multiplexer 430, that can comprise a Serializer/Deserializer (SERDES), divides the signal among a plurality of subscriber optical interfaces, and it handles serialization of data. In some exemplary embodiments, the tap multiplexer 430 can produce idle pattern codes. Usually when the tap multiplexer 430 has the capability to produce idle pattern codes, the tap routing device 433 does not.
In order to minimize the speed at which electrical circuits must operate, the data signals through the tap routing device are often handled in parallel. That is, a signal path that is, usually, 8, 16, 32, or 64 bits wide handles the signals, with many bits being handled on different wires at the same time. For example, if a data processing element is 32 bits wide, it handles 32 bits simultaneously on 32 wires, but the data rate on any one wire is only 1/32 of the overall data rate. However, before the signal can be supplied to the fiber optic optical transmitter 435, it must be converted to a faster serial data on a single wire, since there is only one optical transmitter 435 and one fiber optic cable to handle data to each group of subscriber optical terminals. This is the purpose of the serialization portion of the SERDES, to convert the parallel paths to a single serial path. At the same time, the 8B/10B encoding may be added. The deserialization portion of the SERDES operates on the received signal coming in from Optical Receiver 440, converting from serial to parallel format. This process is understood by one of ordinary skill in the art.
The tap multiplexer 430 can also add idle code patterns when no input data is available. The plurality of tap multiplexers 430 are connected to a plurality of optical transmitters 435 and optical receivers 440. The optical transmitters 435 can comprise can comprise one of Fabry-Perot (F-P) Laser Transmitters, distributed feedback lasers (DFBs), or Vertical Cavity Surface Emitting Lasers (VCSELs). However, other types of optical transmitters are possible and are not beyond the scope of the invention. The optical receivers 440 can comprise one or more photoreceptors or photodiodes that convert optical signals into electrical signals. According to one exemplary embodiment, when downstream data to subscribers is transmitted according to a standard, such as the IEEE 802.3ah standard, the optical transmitters 435 transmit downstream data at a wavelength of approximately 1490 nm. Meanwhile, the optical receivers 440 receive upstream data on a wavelength of 1310 nm.
Further describing
Each optical multiplexer 445 combines the downstream data of a first optical wavelength, such as 1490 nm, with the downstream video broadcast signals of a second optical wavelength, such as 1550 nm. Each optical multiplexer 445 also separates the upstream data signals sent on a third optical wavelength, such as 1310 nm, from the downstream optical signals. Each optical multiplexer 445 sends the upstream data signals sent using the third wavelength to respective optical receivers 440.
Even though the tap multiplexer 430 and the 3k optical multiplexer 445 share similar nomenclature, and even though their functions are somewhat analogous, the two devices work much differently. As is understood by one of ordinary skill in the art, a multiplexer is any device that combines two or more signals. The tap multiplexer 430 works in the electrical domain to combine signals to and from the optical transmitter 435 and the optical receiver 440. On the other hand, 3λ optical multiplexer 445 operates in the optical domain, and combines downstream signals from optical transmitter 435 and splitter 480, with upstream signals transmitted to optical receiver 440. In essence, the 3λ optical multiplexer 445 is the device that directs the three optical signals in the appropriate directions.
Optical signals entering and leaving the data service hub 400 are interfaced by way of the combined signal Input/Output ports 450 that are coupled to respective optical waveguides 160. The optical waveguides 160 are connected to optical taps or splitters as illustrated in
In an exemplary embodiment of the present invention, as illustrated in
In an exemplary embodiment of the present invention, the idle pattern replacement device 425A monitors this electrical data and when it detects either an idle pattern or no data, it inserts substitute data that is later converted from the electrical domain into the optical domain at a first optical wavelength in order to avoid SRS optical interference between downstream optical data signals at the first optical wavelength and downstream video signals at a second optical wavelength. The downstream optical data signals and downstream optical video signals are sent through the combined signal input/output port 450 over an optical waveguide 160 to optical splitters 130.
In an exemplary embodiment of the present invention, the tap routing device 433, idle pattern replacement device 425A, and tap multiplexer 430 may all be incorporated on a single commercial chip.
The Subscriber Optical Interface 140 comprises a three wavelength (3λ) Optical Multiplexer 445, which separates the three optical wavelengths, 1310 mn, 1490 nm, and 1550 nm, as did the corresponding device in the Data Service Hub 400. The 1550 nm broadcast signal is routed to an Analog Optical Receiver 525, and from there to a Modulated RF Unidirectional Signal Output 535 which connects to the subscriber's TVs and other suitable appliances known to one of ordinary skill in the art.
The 1490 nm downstream data is routed to a Digital Optical Receiver 540 then to a processor 550, which manages data signals and interfaces to Telephone Input/Outputs 555 and Data interfaces 560.
Referring now to
The idle pattern replacement device 425A comprises a downstream data shift register 640 operating in the electrical domain, which accepts data 620 from the tap routing device 433. As is understood by one of ordinary skill in the art, data at this point is often handled in parallel format, whereby a number of bits (typically 8, 16, 32, or 64) are transferred simultaneously, or in parallel. Thus, downstream data shift register 640 is comprised of several sets of connected storage devices 625 that may comprise flip-flops, which are well known to one of ordinary skill in the art. For each bit in the parallel data transfer, data is shifted horizontally across the downstream data shift register 640. The purpose of the downstream data shift register 640 is to delay the start of each packet long enough to determine whether real data, or non-idle code data, is present, and if not, to allow random data to be inserted. If true data is present, then it is passed through to switches 645 and sent to the tap multiplexer 430.
If no data is being sent from the tap routing device 433, this no-data condition is detected by the no-data detector 630. The no-data detector 630 is coupled to each of the first stage storage devices in downstream data shift register 640, to allow it to detect when no data is present. Depending on the exemplary embodiment, a no-data condition can be represented by all 0s or 1s in the first stage of the shift register, or it can be represented by a unique data pattern, such as idle code. It could also be represented by the lack of a clock signal to shift data into the downstream data shift register 640 when the tap routing device 433 does not produce any idle code. In such an exemplary embodiment when the tap routing device 433 does not produce any idle code, the no-data detector 630 determines if an absence of data condition exists in which there is a lack of a clock signal or through pattern matching. When the no-data detector 630 is looking for the absence of data, it uses pattern matching to detect the absence of data. The absence of data typically comprises all 0s or 1s, which is well to known to one of ordinary skill in the art.
If the embodiment of the system is such that when no data is present, a fixed pattern of data 620 appears from the tap routing device, such as an idle code pattern, then the no-data detector 630 comprises a pattern recognition circuit known to one of ordinary skill in the art. The no-data detector 630 determines when the data pattern representing no real data or idle code pattern is present. Such a pattern recognition device can comprise a series of exclusive OR gates, for example, with an input from each exclusive OR gate connected to a 1 or a 0, depending on the pattern to be recognized. Furthermore, there are also software techniques for recognizing a pattern, like idle code patterns, which utilize the same process implemented in software that are well known in the art.
So long as data is present, then the no-data detector 630 controls the data selection switch control 635 to keep the data selection switches 645 in the positions shown so that the data is transmitted to the tap multiplexer 430. In this position, input data is supplied to the tap multiplexer 430 after a delay represented by the number of storage devices 610 connected horizontally in the downstream data shift register 640.
If a no-data condition is detected, then the data selection switches 645 are thrown to the opposite position, which connects the output to the replacement data shift register 615. This replacement data shift register 615 is similar to the downstream data shift register 640 except that it is loaded from a data initializer 605. The replacement shift register 615 contains data, such as inventive idle code, that is put in when no data is being transmitted, in order to prevent the tap multiplexer 430 from generating any conventional idle code patterns in exemplary embodiments in which the tap routing device 433 does not produce idle code patterns. As noted above, conventional idle code will cause the SRS problems as described above between downstream optical data signals of a first optical wavelength and downstream optical video signals at a second optical wavelength.
The data initializer 605 can be as simple as fixed pre-programming of the state of the storage devices 625 in the replacement data shift register 615. It can also be a microprocessor that can load data that is either pre-determined or downloaded or generated randomly by the microprocessor. A number of implementations are known to one of ordinary skill in the art and not beyond the scope of the invention.
The actual data loaded into the replacement data shift register 615 can be of a number of types. One type of data can be random numbers preceded by a code that tells the subscriber optical interface to ignore the data that follows in an Ethernet frame. Another type of data can be random data sent to a non-existent Ethernet MAC address, as is understood by one of ordinary skill in the art.
According to another exemplary embodiment of the present invention, random data is sent to a pre-determined set of non-existent MAC addresses such that there is minimal concentration of signal power at any one frequency. The set of non-existent MAC addresses can be selected from the range of MAC addresses that are assigned to each idle pattern replacement device 425A. Alternatively, the same set of non-existent MAC addresses can be assigned to all idle pattern replacement devices 425A. According to another exemplary aspect, an alternate idle code pattern, that complies with IEEE's 802.3ah standard, can be transmitted. All of these types of data can lessen the SRS optical interference and improve the quality of video transmissions.
The length of both the downstream data shift register 640 and the replacement data shift register 615 can be identical. The downstream data shift register 640 usually must delay any real data arriving after a period of no data, until the replacement data shift register 615 has shifted out its entire data. A normal Ethernet idle pattern is 20 bytes long, but the minimum length for a complete Ethernet frame is 64 bytes.
Thus, when an idle condition is detected and if the embodiment is such that random data is being sent to a non-existent MAC address, the output to the tap multiplexer 430 must comprise the 64 bytes of the packet being sent to the non-existent MAC address. If a real data packet comes along before the end of this 64 byte word, then the real data must be delayed in the downstream data shift register 640 until the end of the data being sent to the non-existent MAC address. The switches 645 are then thrown to the position shown, and the real data is shifted out.
If the random data being sent to the non-existent MAC address has all been shifted out and still there is no real data to be sent, then the Data Initializer 605 loads the Replacement Data Shift Register 615 with a new set of random data and a non-existent MAC address, and the process begins again. Because of this possibility (multiple packets of random data sent to non-existent MAC addresses sequentially), according to one exemplary embodiment, it is preferred to use a plurality of random non-existent MAC addresses, to prevent a common address from forcing a spectral peak. As soon as new real data is presented to Downstream Data Shift Register 640, then at the completion of the current random data packet being sent to the non-existent MAC address, the real data is transmitted. A Communications Path 655 between the No-data Detector 630 and the Data Initializer 605 facilitates coordination between the data initializer 605 and the no-data detector 630 of the Idle Pattern Replacement Device 425A.
Referring now to
If the idle pattern replacement device 425A determines that an idle pattern is not being transmitted in Step 720, the data is transmitted to the tap multiplexer 430 in Step 750. This data is transferred through Downstream Data Shift Register 640. However, if the idle pattern replacement device 425A determines that an idle pattern (or no data, depending on the embodiment) is being transmitted in Step 720, the idle pattern replacement device will need to transmit substitute non-repetitive data to the tap multiplexer 430. First, the idle pattern replacement device 425A will determine if real data from a previous packet is being held within the Downstream Data Shift Register 640 in Step 730. If the Downstream Data Shift Register 640 contains real data from a previous packet, that data will be transmitted to the tap multiplexer 430 in Step 750. If the buffer does not contain real data from a previous packet, the Data Initializer 605 will generate substitute data in Routine 740, which will be transmitted to the tap multiplexer 430 in Step 750, by way of Replacement Data Shift Register 615.
In an alternative exemplary embodiment, in Step 710, the idle pattern replacement device 425B of
In Step 730, the idle pattern replacement device 425B will determine if any real data from a previous packet is stored in a buffer. If the idle pattern replacement device 425B determines that any real data from a previous packet is stored in a buffer in Step 730, the data is transmitted to the tap multiplexer 430 in Step 750; otherwise, the method proceeds to Step 740 to generate an alternative idle code pattern.
In Step 740, the idle code replacement device 425B generates an alternative idle code pattern and transmits the alternative idle code pattern to the tap multiplexer 430 in Step 750. More specific details related to the generation of an alternative idle code pattern are shown in
The header is based on a group of non-existent or reserved MAC addresses stored in the Data Initializer 605. The creation of Ethernet headers are well known in the art. Next, in Step 830, the idle pattern replacement device 425A generates forty (40) bytes of random substitute data. In Step 840, the idle pattern replacement device 425A performs a cyclical redundancy check (CRC) based on the previously created header and random data. Performing a CRC is an optional step because it does not matter whether this packet of substitute data is actually delivered to an actual MAC address, as it is just random data, but the CRC is part of the Ethernet standard. Finally, in step 850 the data is passed to the tap multiplexer 430 for transmission.
Combining the Ethernet header, random substitute data, and CRC from Routine 740A can add up to sixty-four (64) bytes of data that is to be transmitted to the tap multiplexer 430. Only two (2) bytes of data must be read to determine whether an idle pattern is being transmitted. Therefore, in method 700, two (2) bytes of idle pattern data could be sent that could trigger Routine 740 to begin creating sixty-four (64) bytes of data to be transmitted to the tap multiplexer 430. In the meantime, bytes of real data could be transmitted from the optical routing device 433 to the idle pattern replacement device 425A.
However, instead of immediately transferring the real data to the tap multiplexer 430, the real data is held in a buffer until the entire sixty-four (64) bytes of random substitute data is transmitted to the tap multiplexer 430. It should be noted that in the exemplary method 700, the No-data Detector 630 is continuously monitoring the incoming data to determine whether idle pattern data or real data is being transferred. The continuous monitoring of Data 620 allows any real data that immediately follows any idle pattern data to be stored, or buffered, in Downstream Data Shift Register 640 until all random substitute data is transmitted to the tap multiplexer 430. Furthermore, the buffer allows the continuous storage of random substitute data that can immediately be transferred to the tap multiplexer 430 when an idle pattern is detected.
In Step 910, the idle code replacement device 425B has determined in Step 720 that it must generate substitute data because an idle pattern code is being transmitted and there is no waiting data available in a buffer in Step 730. If there is waiting data in a buffer, it is sent to the tap multiplexer 430 before the routine of
In Step 920, the last frame transmitted is checked to see if it had a positive running disparity. If so, Step 920 is exited through the YES path and a single /I1+/ is transmitted to reverse the running disparity as required by the IEEE 802.3ah standard. After Step 920, the method proceeds to Step 940. Furthermore, Step 940 is also entered if the result of Step 920 is NO. In Step 940, a random bit, either a 1 or a 0, is generated, with equal probability of the random bit being 1 or 0. In Step 950, that random bit is examined to see if it is a 1 or a 0. If the random bit is a 0, then Step 950 is exited at the YES outlet, and a normal idle pattern, /I2/ is transmitted in Step 960. If the random bit is a 1, then Step 950 is exited at the NO outlet, and a pair of idle patters, /I1+/ followed by /I1−/, are transmitted in Step 970.
After transmitting either /I2/ in Step 960 or the pair /I1+/ and /I1−/ in Step 970, the routine returns to Step 750. In Step 750, the idle pattern is passed to Tap Multiplexer 430, then control passes back to Step 710, where the incoming data is again examined to see if there is real data to be transmitted, or whether another idle code must be generated.
Referring now to
In Step 1140, the L2 switch fabric 1030 selects between normal incoming data from 415 or random information data 1020 from the CPU 1010. The L2 switch fabric 1030 always processes the data such that higher-priority data is transmitted before lower priority data is transmitted. The random information data 1020 from the CPU 1010 is sent as the lowest-priority data, and thus, the only time it will be transmitted is when there is no data available from the logic interface 415. In Step 1150, the L2 switch fabric 1030 transmits the data with the higher priority value to the tap routing device 433. The data with higher priority will always be the data from the logic interface 415 if there is any real data to transmit, so that the only time the random information data 1020 from the CPU 1010 will be transmitted is if there is no data from the logic interface 415 ready to be transmitted.
Therefore, when no real data is being received from the logic interface 415, the L2 switch fabric 1030 will forward the previously created random information data 1020 to the tap routing device 433. Similar to
Referring now to
While, it is not easy to show the effect of the embodiment of
It should be understood that the foregoing relates only to illustrative exemplary embodiments of the present invention, and that numerous changes may be made therein without departing from the scope and spirit of the invention as defined by the following claims.
This application is a continuation of and claims priority to application Ser. No. 11/200,873 filed Aug. 10, 2005, now U.S. Pat. No. 7,340,180 entitled “Countermeasures for Idle Pattern SRS Interference in Ethernet Optical Network Systems,” the entire contents of which are incorporated by reference.
Number | Name | Date | Kind |
---|---|---|---|
4253035 | Amitay | Feb 1981 | A |
4295005 | Daugherty | Oct 1981 | A |
4495545 | Dufresne et al. | Jan 1985 | A |
4500990 | Akashi | Feb 1985 | A |
4654891 | Smith | Mar 1987 | A |
4665517 | Widmer | May 1987 | A |
4733398 | Shibagaki et al. | Mar 1988 | A |
4763317 | Lehman et al. | Aug 1988 | A |
4805979 | Bossard | Feb 1989 | A |
4852023 | Lee et al. | Jul 1989 | A |
4945541 | Nakayama | Jul 1990 | A |
4956863 | Goss | Sep 1990 | A |
4975899 | Faulkner | Dec 1990 | A |
5105336 | Jacoby et al. | Apr 1992 | A |
5132992 | Yurt et al. | Jul 1992 | A |
5144267 | West, Jr. | Sep 1992 | A |
5179591 | Hardy | Jan 1993 | A |
5189725 | Bensell, III et al. | Feb 1993 | A |
5247347 | Litteral et al. | Sep 1993 | A |
5249194 | Sakanushi | Sep 1993 | A |
5253250 | Schlafer et al. | Oct 1993 | A |
5253275 | Yurt et al. | Oct 1993 | A |
5303295 | West et al. | Apr 1994 | A |
5313546 | Toffetti | May 1994 | A |
5325223 | Bears | Jun 1994 | A |
5345504 | West, Jr. | Sep 1994 | A |
5349457 | Bears | Sep 1994 | A |
5365585 | Puhl et al. | Nov 1994 | A |
5365588 | Bianco et al. | Nov 1994 | A |
5378174 | Brownlie | Jan 1995 | A |
5402315 | Reichle | Mar 1995 | A |
5412498 | Arstein et al. | May 1995 | A |
5432875 | Korkowski et al. | Jul 1995 | A |
5469507 | Canetti et al. | Nov 1995 | A |
5495549 | Schneider | Feb 1996 | A |
5509099 | Hermsen | Apr 1996 | A |
5510921 | Takai et al. | Apr 1996 | A |
5528455 | Miles | Jun 1996 | A |
5528582 | Bodeep | Jun 1996 | A |
5534912 | Kostreski | Jul 1996 | A |
5541917 | Farris | Jul 1996 | A |
5550863 | Yurt et al. | Aug 1996 | A |
5557317 | Nishio et al. | Sep 1996 | A |
5559858 | Beveridge | Sep 1996 | A |
5566099 | Shimada | Oct 1996 | A |
5572347 | Burton et al. | Nov 1996 | A |
5572348 | Carlson et al. | Nov 1996 | A |
5572349 | Hale | Nov 1996 | A |
5666487 | Goodman et al. | Sep 1997 | A |
5694232 | Parsay et al. | Dec 1997 | A |
5701186 | Huber | Dec 1997 | A |
5706303 | Lawrence | Jan 1998 | A |
5715020 | Kuroiwa et al. | Feb 1998 | A |
5731546 | Miles et al. | Mar 1998 | A |
RE35774 | Moura et al. | Apr 1998 | E |
5769159 | Yun | Jun 1998 | A |
5778017 | Sato et al. | Jul 1998 | A |
5790523 | Ritchie, Jr. | Aug 1998 | A |
5793413 | Hylton | Aug 1998 | A |
5793506 | Schmid | Aug 1998 | A |
5799088 | Raike | Aug 1998 | A |
5802089 | Link | Sep 1998 | A |
5822102 | Bodeep et al. | Oct 1998 | A |
5861966 | Ortel | Jan 1999 | A |
5867485 | Chambers et al. | Feb 1999 | A |
5875430 | Koether | Feb 1999 | A |
5880864 | Williams | Mar 1999 | A |
5892865 | Williams | Apr 1999 | A |
5953690 | Lemon et al. | Sep 1999 | A |
5969836 | Foltzer | Oct 1999 | A |
5974063 | Yoshida | Oct 1999 | A |
6002692 | Wills | Dec 1999 | A |
6002720 | Yurt et al. | Dec 1999 | A |
6041056 | Bigham et al. | Mar 2000 | A |
6097159 | Mogi | Aug 2000 | A |
6097515 | Pomp et al. | Aug 2000 | A |
6144702 | Yurt et al. | Nov 2000 | A |
6151343 | Jurgensen | Nov 2000 | A |
6167553 | Dent | Dec 2000 | A |
RE37125 | Carlson | Apr 2001 | E |
6215939 | Cloud | Apr 2001 | B1 |
6229701 | Kung et al. | May 2001 | B1 |
6295148 | Atlas | Sep 2001 | B1 |
6300562 | Daoud | Oct 2001 | B1 |
6330155 | Remsburg | Dec 2001 | B1 |
6336201 | Geile et al. | Jan 2002 | B1 |
6342004 | Lattimore et al. | Jan 2002 | B1 |
6356369 | Farhan | Mar 2002 | B1 |
6360320 | Ishiguro et al. | Mar 2002 | B1 |
6385366 | Lin | May 2002 | B1 |
6421150 | Graves et al. | Jul 2002 | B2 |
6424656 | Hoebeke | Jul 2002 | B1 |
6427035 | Mahony | Jul 2002 | B1 |
6452714 | Rollins | Sep 2002 | B1 |
6460182 | Buabbud | Oct 2002 | B1 |
6463068 | Lin et al. | Oct 2002 | B1 |
6483635 | Wach | Nov 2002 | B1 |
6486907 | Farber et al. | Nov 2002 | B1 |
6490727 | Nazarathy et al. | Dec 2002 | B1 |
6493335 | Darcie et al. | Dec 2002 | B1 |
6496641 | Mahony | Dec 2002 | B1 |
6507494 | Hutchison | Jan 2003 | B1 |
6519280 | Cole | Feb 2003 | B1 |
6529301 | Wang | Mar 2003 | B1 |
6546014 | Kramer et al. | Apr 2003 | B1 |
6577414 | Feldman | Jun 2003 | B1 |
6611522 | Zheng et al. | Aug 2003 | B1 |
6621975 | Laporte et al. | Sep 2003 | B2 |
6654565 | Kenny | Nov 2003 | B2 |
6674967 | Skrobko et al. | Jan 2004 | B2 |
6680948 | Majd et al. | Jan 2004 | B1 |
6682010 | Pohl | Jan 2004 | B2 |
6687376 | Yamaguchi | Feb 2004 | B1 |
6687432 | Schemmann et al. | Feb 2004 | B2 |
6707024 | Miyamoto et al. | Mar 2004 | B2 |
6738983 | Rao et al. | May 2004 | B1 |
6740861 | Matsuda | May 2004 | B2 |
6771614 | Jones, IV et al. | Aug 2004 | B1 |
6775137 | Chu et al. | Aug 2004 | B2 |
6778785 | Imajo | Aug 2004 | B2 |
6804256 | Chang | Oct 2004 | B2 |
6804354 | Driscoll | Oct 2004 | B1 |
6807188 | Blahut | Oct 2004 | B1 |
6814328 | Li et al. | Nov 2004 | B1 |
6823385 | McKinnon, III et al. | Nov 2004 | B2 |
6889007 | Wang et al. | May 2005 | B1 |
6912075 | Ionov et al. | Jun 2005 | B1 |
6961956 | Bontempi | Nov 2005 | B2 |
6973271 | Farmer et al. | Dec 2005 | B2 |
7007297 | Woodward | Feb 2006 | B1 |
7023871 | Lind et al. | Apr 2006 | B2 |
7190901 | Farmer et al. | Mar 2007 | B2 |
7218855 | Whittlesey et al. | May 2007 | B2 |
7222358 | Levinson et al. | May 2007 | B2 |
7227871 | Dworkin et al. | Jun 2007 | B2 |
7242694 | Beser | Jul 2007 | B2 |
7340180 | Farmer et al. | Mar 2008 | B2 |
20010002195 | Fellman et al. | May 2001 | A1 |
20010002196 | Fellman et al. | May 2001 | A1 |
20010002486 | Kocher et al. | May 2001 | A1 |
20010004362 | Kamiya | Jun 2001 | A1 |
20010030785 | Pangrac et al. | Oct 2001 | A1 |
20020006197 | Carroll et al. | Jan 2002 | A1 |
20020012138 | Graves | Jan 2002 | A1 |
20020021465 | Moore, Jr. et al. | Feb 2002 | A1 |
20020027928 | Fang | Mar 2002 | A1 |
20020039218 | Farmer et al. | Apr 2002 | A1 |
20020063924 | Kimbrough | May 2002 | A1 |
20020063932 | Unitt et al. | May 2002 | A1 |
20020080444 | Phillips et al. | Jun 2002 | A1 |
20020089725 | Farmer | Jul 2002 | A1 |
20020105965 | Dravida et al. | Aug 2002 | A1 |
20020106178 | Bumgarner et al. | Aug 2002 | A1 |
20020116719 | Dapper | Aug 2002 | A1 |
20020135843 | Gruia | Sep 2002 | A1 |
20020141159 | Bloemen | Oct 2002 | A1 |
20020164026 | Huima | Nov 2002 | A1 |
20020181925 | Hodge et al. | Dec 2002 | A1 |
20030007210 | Kenny | Jan 2003 | A1 |
20030007220 | Whittlesey et al. | Jan 2003 | A1 |
20030011849 | Farmer et al. | Jan 2003 | A1 |
20030016692 | Thomas et al. | Jan 2003 | A1 |
20030048512 | Ota | Mar 2003 | A1 |
20030072059 | Thomas et al. | Apr 2003 | A1 |
20030086140 | Thomas et al. | May 2003 | A1 |
20030090320 | Skrobko et al. | May 2003 | A1 |
20030128983 | BuAbbud | Jul 2003 | A1 |
20030154282 | Horvitz | Aug 2003 | A1 |
20030189587 | White et al. | Oct 2003 | A1 |
20030194241 | Farmer | Oct 2003 | A1 |
20030206564 | Mills et al. | Nov 2003 | A1 |
20030206634 | Rose | Nov 2003 | A1 |
20030223750 | Farmer et al. | Dec 2003 | A1 |
20040028405 | Unitt et al. | Feb 2004 | A1 |
20040086277 | Kenny | May 2004 | A1 |
20040131357 | Farmer et al. | Jul 2004 | A1 |
20040141747 | Kenny et al. | Jul 2004 | A1 |
20040161217 | Hodge et al. | Aug 2004 | A1 |
20040199502 | Wong et al. | Oct 2004 | A1 |
20040208565 | Roberts et al. | Oct 2004 | A1 |
20040221088 | Lisitsa et al. | Nov 2004 | A1 |
20040240885 | Naoe et al. | Dec 2004 | A1 |
20040253003 | Farmer et al. | Dec 2004 | A1 |
20040264492 | Blahut | Dec 2004 | A1 |
20040267730 | Dumais et al. | Dec 2004 | A1 |
20050053350 | Hodge et al. | Mar 2005 | A1 |
20050074241 | Farmer et al. | Apr 2005 | A1 |
20050081244 | Barrett et al. | Apr 2005 | A1 |
20050123001 | Craven et al. | Jun 2005 | A1 |
20050125837 | Farmer et al. | Jun 2005 | A1 |
20050175035 | Neely et al. | Aug 2005 | A1 |
20060020975 | Kenny et al. | Jan 2006 | A1 |
20060039699 | Farmer et al. | Feb 2006 | A1 |
20060075428 | Farmer et al. | Apr 2006 | A1 |
20070076717 | Limb et al. | Apr 2007 | A1 |
Number | Date | Country |
---|---|---|
2107922 | Apr 1995 | CA |
0566662 | Jul 1992 | EP |
0713347 | May 1996 | EP |
0720322 | Jul 1996 | EP |
0955739 | Nov 1999 | EP |
0933892 | Oct 2003 | EP |
07-020327 | Jan 1995 | JP |
10-020123 | Jan 1998 | JP |
11-305052 | Nov 1999 | JP |
4-504433 | Mar 2002 | JP |
180038 | Nov 1995 | MX |
72821 | Aug 2005 | TW |
WO 0127940 | Apr 2001 | WO |
WO 0230019 | Apr 2002 | WO |
WO 0230020 | Apr 2002 | WO |
WO 02060123 | Aug 2002 | WO |
WO 03001737 | Jan 2003 | WO |
WO 03005611 | Jan 2003 | WO |
WO 03005612 | Jan 2003 | WO |
WO 03019243 | Mar 2003 | WO |
WO 03021820 | Mar 2003 | WO |
WO 03023980 | Mar 2003 | WO |
WO 03079567 | Sep 2003 | WO |
WO 03090396 | Oct 2003 | WO |
WO 2006014433 | Feb 2006 | WO |
WO 2006020538 | Feb 2006 | WO |
WO 2006041784 | Apr 2006 | WO |
Number | Date | Country | |
---|---|---|---|
20080187313 A1 | Aug 2008 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 11200873 | Aug 2005 | US |
Child | 12002321 | US |