1. Field of the Invention
The invention relates to telecommunications. More particularly, the invention relates to a communications interface bus which can carry synchronous and asynchronous data signals simultaneously.
2. State of the Art
The first commercial digital voice communications system was installed in 1962 in Chicago, Ill. The system was called “T1” and was based on the time division multiplexing (TDM) of twenty-four telephone calls on two twisted wire pairs. The T1 system is still widely used today and forms a basic building block for higher capacity communication systems including T3 which transports twenty-eight T1 signals. The designations T1 and T3 were originally coined to describe a particular type of carrier equipment. Today T1 and T3 are often used to refer to a carrier system, a data rate, and various multiplexing and framing conventions. It is more accurate to use the designations “DS1” and “DS3” when referring to the multiplexed digital signal carried by the T1 and T3 carriers, respectively.
Today, another higher bandwidth TDM system is in use. This system is referred to as the synchronous optical network (SONET) or, in Europe, the synchronous digital hierarchy (SDH). The SONET network is designed to provide enormous bandwidth. SONET signals are referred to as Synchronous Transport Signals (STS) or Optical Carriers (OC). The narrowest SONET signal is referred to as STS-1 or OC-1. It has a bandwidth of 51.84 Mb/s which is sufficient to carry twenty-eight DS1 signals or a single DS3 signal. The hierarchy includes STS-3 (OC-3) which is three times the bandwidth of an STS-1 (OC-1) signal, and higher bandwidth signals increasing in multiples of four, i.e. STS-12 (OC-12), STS-48 (OC-48), STS-192 (OC-192), and STS-768 (OC-768).
SONET signals are said to be synchronous because all nodes in the SONET network are synchronized to a common reference clock. The older T-1 and T-3 signals are said to be plesiochronous (nearly synchronous) because the clock rate of each signal is tightly controlled. As used herein, however, all signals other than SONET signals are referred to as asynchronous. When multiple T-1 or T-3 signals from different sources are demultiplexed from a SONET signal, each of these plesiochronous signals will have its own separate clock. The clock for each signal is derived from the SONET signal using a desynchronizer. For example, when demultiplexing an STS-1 signal which carries twenty-eight DS-1 data signals, twenty-eight desynchronizers will be used to create twenty-eight separate clock signals, one for each DS-1 signal. In fact, each DS-1 signal will have its own clock, data, and frame signals.
As telecommunication networks grow, it is desirable to miniaturize network equipment as much as possible, particularly in urban areas where space is expensive and networks are large. For example, a SONET demultiplexer may be made of a few integrated circuit chips. One of the difficulties in miniaturization is that as more devices are placed on a single chip, more leads or pins are required. The physical size of the chip limits the number of leads which can be used. For example, in a SONET demultiplexer, it would be necessary to provide three pins (clock, data, and frame) for each “possible” asynchronous signal. By “possible”, it is meant that in a higher order SONET signal, such as an STS-3, demultiplexing may involve separating out twenty-eight DS-1 signals and two STS-1 signals or it could involve separating out up to eighty-four DS-1 signals. Thus, a demultiplexing solution for an STS-3 would require eighty-four data lines, eight-four clock lines, and eight-four frame signal lines in order to terminate eighty-four DS-1 signals. This would require many separate pins on a chip.
It is therefore an object of the invention to provide methods and apparatus for simultaneously transferring synchronous and asynchronous signals among broadband access devices.
It is also an object of the invention to provide methods and apparatus for efficiently transferring synchronous and asynchronous signals among broadband access devices.
It is another object of the invention to provide methods and apparatus for transferring synchronous and asynchronous signals among broadband access devices using a minimum number of lines.
In accord with these objects which will be discussed in detail below, the apparatus of present invention provides a bus which includes a data bus, a clock bus, and a plurality of control lines which are used to indicate the type of data being carried on the data bus. According to the methods of the invention, data is transferred on the bus in a repeating frame having a plurality of slots, each slot being defined as one bus clock cycle. Each slot may contain a synchronous or asynchronous data signal and one or more of the control lines are asserted during the slot time of the data to indicate the type of data.
Two embodiments are provided. One utilizes a 25 MHz clock bus and a repeating frame of three hundred thirty-six slots. The other utilizes a 75 MHz clock bus and a repeating frame of one thousand eight slots. In the first embodiment, data is interleaved in groups of four and in the second embodiment data is interleaved in groups of twelve. The first embodiment supports up to four STS-1 payloads or combinations of other signals totalling the same bandwidth. The second embodiment supports up to twelve STS-1 signals or combinations of other signals totalling the same bandwidth.
The presently preferred embodiment of the data bus includes eight receive bits and eight transmit bits. The control lines include RxIFSlot, TxIFSlot, RxValid, TxValid, RxFrm_ind, TxFrm_ind, RxFrm_pos2-0, TxFrm_pos2-0, RxPrty, TxPrty2, and TxPrty1. RxIFSlot (for the receive bus) and TxIFSlot (for the transmit bus) are used to mark the first bus slot. They are asserted low once every three hundred thirty-six time slots (one thousand eight for the second embodiment). RxValid indicates the presence of a valid data byte on the receive bus when it is asserted low. TxValid indicates that the data byte on the transmit bus is requested when it is asserted low. RxFrm_ind and TxFrm_ind indicate the start of frame (not to be confused with the repeating frame of the invention) of an asynchronous signal such as a T-1, etc. RxFrm_pos2-0 and TxFrm_pos2-0 indicate the frame pulse position within a byte when RxFr_ind, respectively TxFr_ind, is asserted. A value of 111 indicates the MSB and 000 indicates the LSB. RxPrty, TxPrty2, and TxPrty1 are parity bits which provide even parity over all (or some, depending on mode of operation) the other control and data signals.
The invention is implemented in conjunction with an optical network interface which is designated the sender and an interface to another network, e.g. an interface to a router, which is designated a receiver. The bus system according to the invention is operable with multiple senders and receivers. It is therefore applicable to an add/drop node of the optical network as well as to an end point node.
Additional objects and advantages of the invention, including the details of multiplexing synchronous and asynchronous signals in both the first and second embodiment will become apparent to those skilled in the art upon reference to the detailed description taken in conjunction with the provided Appendix.
The attached sixty-six page Appendix is a document entitled Extendible Asynchronous and Synchronous Interface (EASI) Bus for Broadband Access-Functional Requirements which includes numerous figures, tables and timing diagrams illustrating operation of the invention.
Turning now to
According to the invention, the first device 16 is coupled via a standard SONET interface (not shown) to an optical network 22 and is considered to be a “Sender”. The second device 18 is coupled to a non-SONET network 24 via an ETHERNET or other non-SONET interface (not shown) and is considered to be a “Receiver”. Details concerning the Sender are set out in the attached Appendix at pages 28-38 and 55-62. Details concerning the Receiver are set out in the Appendix at pages 19-28 and 50-55.
As used herein, the terms Sender and Receiver are not the same as the terms Master and Slave which are often used to describe devices coupled to a bus. According to the invention, either the Sender or the Receiver can act as bus Master. Appendix pages 50-62 include timing diagrams illustrating the Sender and Receiver operating in both Master Mode and Slave Mode.
Before discussing the operation of the apparatus and in particular, the operation of the control lines, it is useful to first understand the repeating frame by which data is transferred over the bus.
Turning now to
A second embodiment of the invention is shown in the attached Appendix at pages 40-49. The second embodiment operates at a bus speed of 75 MHz and uses a repeating frame of one thousand eight slots. In the second embodiment data is interleaved in groups of twelve. The second embodiment supports the transfer of up to twelve STS-1 signals or combinations of other signals totalling the same bandwidth. Examples of the types of signals which can be mapped into the frame of the second embodiment are illustrated in the attached Appendix at pages 44-49.
Referring now to
RxValid indicates the presence of a valid data byte on the receive bus when it is asserted low.
TxValid indicates that the data byte on the transmit bus is requested (or that it is being sent depending on the mode of operation) when it is asserted low.
The RxValid and TxValid signals are used to indicate when no data is available in an asynchronous signal.
RxFrm_ind and TxFrm_ind indicate the start of frame (not to be confused with the repeating frame of the invention) of an asynchronous signal such as a T-1, E-1 etc.
RxFrm_pos2-0 and TxFrm_pos2-0 indicate the frame pulse position within a byte when RxFrm_ind, respectively TxFrm_ind is asserted. A value of 111 indicates the MSB and 000 indicates the LSB.
RxPrty, TxPrty2, and TxPrty1 are parity bits which provide even parity over all (or some, depending on mode of operation) the other control and data signals. Details regarding the parity bits can be found in the attached Appendix at pages 29 and 30.
Timing diagrams illustrating the operation of the Receiver in both master and slave mode are shown at pages 22 and 50 of the Appendix. Timing diagrams illustrating operation of the Receiver in slave mode are shown at pages 23 and 52 of the Appendix. Timing diagrams illustrating operation of the Receiver in master mode are shown at pages 25, 26 and 54 of the Appendix.
A timing diagram illustrating operation of the Sender in both master mode and slave mode is shown at page 56 of the Appendix. Timing diagrams illustrating operation of the Sender in master mode are shown at pages 32, 34, 35, 36, and 58 of the Appendix. Timing diagrams illustrating operations of the Sender in slave mode are shown at pages 37, 38, and 60 of the Appendix.
The bus of the invention is extensible.
There have been described and illustrated herein several embodiments of an extendible asynchronous and synchronous interface bus for broadband access. While particular embodiments of the invention have been described, it is not intended that the invention be limited thereto, as it is intended that the invention be as broad in scope as the art will allow and that the specification be read likewise. Thus, while particular combinations of synchronous and asynchronous signals have been shown in the Appendix, it will be appreciated that other combinations could be utilized. Also, while the bus has been illustrated with one sender with one receiver, one sender with two receivers, and two senders with two receivers, it will be recognized that other combinations of senders and receivers could be used. It will therefore be appreciated by those skilled in the art that yet other modifications could be made to the provided invention without deviating from its spirit and scope as so claimed.
Number | Name | Date | Kind |
---|---|---|---|
3982077 | Clark et al. | Sep 1976 | A |
3985962 | Jones et al. | Oct 1976 | A |
4149144 | Diefender | Apr 1979 | A |
4156798 | Doelz | May 1979 | A |
4375681 | Abbott et al. | Mar 1983 | A |
4460993 | Hampton et al. | Jul 1984 | A |
4488293 | Haussmann et al. | Dec 1984 | A |
4535448 | Baxter et al. | Aug 1985 | A |
4660169 | Norgren et al. | Apr 1987 | A |
4685101 | Segal et al. | Aug 1987 | A |
4727536 | Reeves et al. | Feb 1988 | A |
4750168 | Trevitt | Jun 1988 | A |
4763320 | Rudolph et al. | Aug 1988 | A |
4789926 | Clarke | Dec 1988 | A |
4815074 | Jacobsen | Mar 1989 | A |
4817037 | Hoffman et al. | Mar 1989 | A |
5048012 | Gulick et al. | Sep 1991 | A |
5084872 | Le Cucq et al. | Jan 1992 | A |
5150359 | Wilson et al. | Sep 1992 | A |
5163048 | Heutink | Nov 1992 | A |
5172373 | Suzuki | Dec 1992 | A |
5263023 | Sevenhans et al. | Nov 1993 | A |
5276678 | Hendrickson et al. | Jan 1994 | A |
5299193 | Szczepanek | Mar 1994 | A |
5339395 | Pickett et al. | Aug 1994 | A |
5452330 | Goldstein | Sep 1995 | A |
5546392 | Boal et al. | Aug 1996 | A |
5572686 | Nunziata et al. | Nov 1996 | A |
5901146 | Upp | May 1999 | A |
6104724 | Upp | Aug 2000 | A |
6119188 | Sheafor et al. | Sep 2000 | A |
6240087 | Cummings et al. | May 2001 | B1 |
6275499 | Wynn et al. | Aug 2001 | B1 |
6414966 | Kulkarni et al. | Jul 2002 | B1 |
6457090 | Young | Sep 2002 | B1 |
6535520 | Hann et al. | Mar 2003 | B1 |
6667973 | Gorshe et al. | Dec 2003 | B1 |
6724772 | Borland et al. | Apr 2004 | B1 |
6768745 | Gorshe et al. | Jul 2004 | B1 |
6996125 | Kfir et al. | Feb 2006 | B2 |
Number | Date | Country | |
---|---|---|---|
20030147416 A1 | Aug 2003 | US |