US7324539B1 - Method and apparatus for processing channelized and unchannelized data within a signal - Google Patents
Method and apparatus for processing channelized and unchannelized data within a signal Download PDFInfo
- Publication number
- US7324539B1 US7324539B1 US10/109,521 US10952102A US7324539B1 US 7324539 B1 US7324539 B1 US 7324539B1 US 10952102 A US10952102 A US 10952102A US 7324539 B1 US7324539 B1 US 7324539B1
- Authority
- US
- United States
- Prior art keywords
- channels
- data
- channelized
- unchannelized
- channel
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active, expires
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04J—MULTIPLEX COMMUNICATION
- H04J3/00—Time-division multiplex systems
- H04J3/16—Time-division multiplex systems in which the time allocation to individual channels within a transmission cycle is variable, e.g. to accommodate varying complexity of signals, to vary number of channels transmitted
- H04J3/1605—Fixed allocated frame structures
- H04J3/1611—Synchronous digital hierarchy [SDH] or SONET
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04J—MULTIPLEX COMMUNICATION
- H04J3/00—Time-division multiplex systems
- H04J3/02—Details
- H04J3/08—Intermediate station arrangements, e.g. for branching, for tapping-off
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04J—MULTIPLEX COMMUNICATION
- H04J3/00—Time-division multiplex systems
- H04J3/02—Details
- H04J3/08—Intermediate station arrangements, e.g. for branching, for tapping-off
- H04J3/085—Intermediate station arrangements, e.g. for branching, for tapping-off for ring networks, e.g. SDH/SONET rings, self-healing rings, meashed SDH/SONET networks
Definitions
- the invention relates to the field of communications. More specifically, the invention relates to processing channelized and unchannelized data within a signal.
- TDM Time Division Multiplexing
- IP Internet Protocol
- PPP Point-to-Point Protocol
- MPLS Multi-Protocol Label Switching
- Network elements are used to route or switch data of these different protocols across such high-speed networks.
- Examples of the types of data signals that can be transmitted and received by these network elements include Digital Signal (DS)-1 and DS-3 signals, which include a number of channels.
- Examples of other types of data signals that can be transmitted and received by these network elements include signals based on the Synchronous Optical Network (SONET) standard or Synchronous Digital Hierarchy (SDH) standard.
- SONET Synchronous Optical Network
- SDH Synchronous Digital Hierarchy
- these network elements typically include a number of line cards that include a number of ports to receive and transmit these data.
- conventional network elements are designed and provisioned such that a given port on a given line card processes data of a particular protocol. In other words, a particular port is tied to a particular type of protocol. Disadvantageously, this limitation precludes the handling of data of different types of protocols for a given port of a network element.
- Channels are communication pathways through which data are transmitted between network elements.
- DS-1 and DS-3 signals comprise numerous channels for transmitting data between network elements.
- a network element idly waits until either data arrives or a channel timeout occurs.
- network elements also perform system maintenance to keep the network element running smoothly.
- a given channel may be re-provisioned to process data of a different format. Accordingly, the channel is reset and re-provisioned based on the new format.
- IP Internet Protocol
- the method includes receiving in a network element, data packets within a number of channels, wherein each of the number of channels are channelized or unchannelized.
- the method also includes processing, in a protocol engine within the network element, the data packets within the number of channels that are channelized; and processing, in the protocol engine within the network element, the data packets within the number of channels that are unchannelized.
- the method comprises receiving in a network element data packets within a number of channels, wherein each of the number of channels are channelized or unchannelized, and wherein the data packets are stored in a buffer within the network element; and sending the data packets to a protocol engine for processing.
- the processing comprises determining a channel of the number of channels to process, determining whether the channel is channelized or unchannelized, determining a protocol of a number of protocols for the channel, upon determining the channel is unchannelized, and determining protocol settings for the channel, upon determining the channel is unchannelized.
- the processing further comprises determining a protocol of the number of protocols for the channel, upon determining the channel is channelized, determining protocol settings for the channel, upon determining the channel is channelized, determining where in the buffer data packet processing is to begin, and processing the data packets, and forwarding the data packets.
- the method includes retrieving in a network element, data packets from a data buffer, processing, in a protocol engine within the network element, the data packets, placing the data packets within a channelized channel of a number of channels, and placing the data packets within an unchannelized channel of the number of channels.
- the method includes retrieving a data packet from a memory buffer, preparing, within a protocol engine, the data packet for insertion into a first channel of a first number of channels, wherein the first channel comprises one of a number of protocols, wherein each protocol comprises a number of enabled protocol options.
- the preparing comprises determining one of the first number of channels into which the data packet is to be inserted, determining whether the first channel is channelized or unchannelized, wherein a channelized first channel includes a second number of channels.
- the preparing further includes determining a second channel within the second number of channels into which the data packet is to be placed, upon determining that the first channel is channelized, determining one of the number of protocols of the channel, determining at least one of the number of enabled protocol options, and processing the data packet according to the at least one enabled protocol options.
- the preparing further includes placing the data packet into the first channel, upon determining the first channel is unchannelized and placing the data packet into the channel within the second channel, upon determining the first channel is channelized.
- the apparatus includes a buffer, the buffer for storing data, wherein the data is channelized and unchannelized, and wherein the data is based on a number of protocols, and a protocol engine coupled to the buffer, the protocol engine to process the data.
- FIG. 1 is block diagram illustrating a system that incorporates embodiments of the present invention.
- FIG. 2 illustrates portions of in-ring network elements 102 - 108 , according to embodiments of the present invention.
- FIG. 3 is a block diagram of physical connection circuitry 210 A-D, according to embodiments of the present invention.
- FIG. 4 is a more detailed block diagram of another embodiment of physical connection circuitry 210 A-D, according to embodiments of the present invention.
- FIG. 5 illustrates a flowchart for the processing of data being received into a network element, according to embodiments of the present invention.
- FIG. 6 is a block diagram of a portion of physical connection circuitry 210 A-D, according to embodiments of the present invention.
- FIG. 7 illustrates a number of channelized DS-3 signals that are processed, according to embodiments of the present invention.
- FIG. 8 illustrates a number of unchannelized DS-3 signals that are processed, according to embodiments of the present invention.
- FIG. 9 illustrates a method for processing channels according to embodiments of the present invention.
- FIG. 10 is a block diagram of a portion of physical connection circuitry 210 A-D, according to embodiments of the present invention.
- FIG. 11 is a flow diagram illustrating the receipt of data, according to embodiments of the invention.
- FIG. 12 illustrates a flow diagram for the processing of data being transmitted out from a network element, according to embodiments of the present invention.
- FIG. 13 is a block diagram of a SONET signal carrying data, according to embodiments of the present invention.
- FIG. 1 is block diagram illustrating a system that incorporates embodiments of the present invention.
- system 100 that includes network ring 114 , which is comprised of in-ring network element 102 , in-ring network element 104 , in-ring network element 106 and in-ring network element 108 .
- System 100 also include non-ring network element 110 , non-ring element 111 and non-ring network element 112 , which are coupled to network ring 114 through in-ring network element 102 , in-ring network element 104 and in-ring network element 106 , respectively.
- non-ring elements 110 - 112 can be routers, switches, bridges or other types of network element that switch data across a network.
- connection among in-ring network element 102 , in-ring network element 104 , in-ring network element 106 and in-ring network element 108 allow for bi-directional traffic. Accordingly, this bi-directional capability allows for redundancy in the communication between the different network elements, such that if a given line of communication is lost, the data traffic to be transmitted thereon can be rerouted in the opposite direction to reach its intended destination within the ring architecture.
- system 100 transmits data traffic among the different network elements, both in-ring and non-ring, employing the Synchronous Optical Network (SONET) standard or Synchronous Digital Hierarchy (SDH).
- SONET Synchronous Optical Network
- SDH Synchronous Digital Hierarchy
- embodiments of the present invention are not so limited, as data traffic among the different network elements can be transferred using other types of transmission standards. Examples of other types of transmission standards can include, but are not limited to, T1, T3, Data Signal (DS)3 and DS1 signals.
- data traffic among in-ring network element 102 , in-ring network element 104 , in-ring network element 106 and in-ring network element 108 includes TDM traffic and packet traffic within a same Time Division Multiplexing (TDM) signal.
- TDM Time Division Multiplexing
- network elements are used that can transmit and receive TDM ring traffic.
- the network elements provide two different switching techniques—TDM and packet.
- the packet switching provided can support any number of protocols including layer 2 and layer 3 type protocols such as ATM, Ethernet, Frame Relay, etc.
- the network elements are implemented to be able to: 1) programmably select on an STS basis certain of the incoming TDM traffic to be extracted and packet switched rather than TDM switched; and/or 2) receive packet traffic in another form and to be packet switched. Regardless of which switching technique is used, the switched traffic going back onto the ring is put in TDM format and transmitted out. However, each time traffic is packet switched, that traffic can be statistically multiplexed (e.g., the packets can be selectively dropped based on various criteria).
- a further description of the operation of system 100 and the network elements therein is described in more detail below.
- system 100 is by way of example and not by way of limitation, as embodiments of the present invention can be incorporated in other types of systems.
- other such systems could incorporate less or more network elements into the network ring and/or network elements attached thereto.
- embodiments of the present invention are not limited to the network ring architecture as illustrated in FIG. 1 .
- Examples of other types of network architectures that can incorporate embodiments of the present invention include, but are not limited to, a point-to-point configuration, point-to-multipoint configuration and/or a hub configuration.
- embodiments of the present invention are not limited to TDM networks, but also applies to Wave Division Multiplexing (WDM) networks.
- WDM Wave Division Multiplexing
- FIG. 2 illustrates portions of in-ring network elements 102 - 108 (for purposes of FIG. 2 , hereinafter “network element 102 ”), according to embodiments of the present invention.
- network element 102 includes line cards 202 A-D and control card(s) 220 , such that control card(s) 220 are coupled to each of line cards 202 A-D.
- the number of line cards illustrated are for the sake of simplicity and not by way of limitation, as a lesser or greater number of line cards can be included within network element 102 .
- network element 102 includes a first switch fabric, packet mesh 226 , which includes a full mesh such that each of line cards 202 A-D are coupled to one another.
- line card 202 a is coupled to line cards 202 b - d through packet mesh 226 .
- embodiments of the present invention are not limited to a full mesh for the transmission of packets among line cards 202 A-D, as any type of switching method that switches based on the addressing scheme described herein can be incorporated into embodiments of the present invention.
- line cards 202 A-D could be coupled together using a switch fabric, such that the line cards are coupled to a control card, which provides for the switching therein.
- Line cards 202 A-D include physical connection circuitry 210 A-D, ingress packet processing circuitry 212 A-D and egress packet processing 214 A-D, respectively.
- Physical connection circuitry 210 A-D can be coupled to lines external to network element 102 , as shown, which can carry optical and/or electrical signals, which is described in more detail below in conjunction with FIG. 7 .
- line cards 202 A-D of network element 102 may be connected to an optical line transmitting SONET STS-N signals.
- line cards 202 A-D of network element 102 may be connected to an electrical line such as a T1, T3, E1, E3, Ethernet, Gigabit Ethernet, etc.
- control cards(s) 220 include TDM switching circuitry 216 .
- each line card 202 A-D can be coupled to four optical and/or electrical lines. In another embodiment, each line card 202 A-D can be coupled to eight optical and/or electrical lines. However, embodiments of the present invention are not so limited, as a lesser or greater number of optical and/or electrical lines can be coupled to network element 102 through line cards 202 A-D. Additionally, physical connection circuitry 210 A-D are coupled to ingress packet processing circuitry 212 A-D, respectively, such that packet data being received from the optical and/or electrical lines is passed from physical connection circuitry 210 A-D to ingress packet processing circuitry 212 A-D, respectively. In one embodiment, the packet data is extracted from a TDM signal, which is described in more detail below.
- Ingress packet processing circuitry 212 A-D is coupled to packet mesh 226 . Accordingly, each ingress packet processing circuitry 212 A-D is coupled to each egress packet processing circuitry 214 A-D, respectively, on other line cards 202 A-D through packet mesh 226 . Moreover, egress packet processing circuitry 214 A-D is respectively coupled to physical connection circuitry 210 A-D, such that packet data traffic coming in from packet mesh 226 from ingress packet processing circuitry 212 A-D is transmitted from egress packet processing circuitry 214 A-D to physical connection circuitry 210 A-D, respectively.
- Line cards incorporated into embodiments of the present invention are not limited to those illustrated by line cards 202 A-D.
- the network elements can have different line card configurations from that shown by line cards 202 A-D.
- a given in-ring network element could be limited to a single line card that can receive and transmit TDM traffic (which may include packet traffic) within network ring 114 , employing multiple interfaces for the receipt and transmittal of TDM traffic.
- a given in-ring network element can include a first line card to receive TDM traffic (which may include packet traffic) from another in-ring element, while a second line card can transmit TDM traffic to another or same in-ring network element.
- a third line card can be incorporated into this given in-ring network element to add, drop and transmit different types of traffic including different types of packet traffic, such as ATM, Frame Relay, IP, etc, received and transmitted to a non-ring network element.
- a given network element may include a single line card with multiple interfaces such that a first interface receives TDM traffic from another in-ring network element, a second interface transmits TDM traffic to another in-ring network element and a third interface adds, drops and transmits traffic, such as packet traffic to a non-ring network element.
- a line card is used either to connect to an in-ring network element to form part of the ring, or to provide communication with out-of ring network elements.
- layer 2/3 traffic from out-of-ring network element can come in, go through the packet mesh to a line card connected to an in-ring network element, and then out onto the ring being carried by a SONET frame; 2) layer 2/3 traffic coming from an out-of-ring network element can be de-mapped into SONET, go through the TDM switch fabric to a line card connected to an in-ring network element, and then out onto the ring being carried by a SONET frame; 3) TDM traffic coming from an out-of-ring network element can come in, go through the TDM switch fabric to a line card connected to an in-ring network element, and then out onto the ring being carried by a SONET frame; 4) TDM traffic carrying layer 2/3 traffic can be processed to extract the layer 2/3 traffic, with the layer
- a second switch fabric (in addition to packet mesh 226 ) is formed among line cards 202 A-D and TDM switching circuitry 216 of control cards 220 , as illustrated by the dashed lines in FIG. 2 .
- physical connection circuitry 210 A-D is coupled to TDM switching circuitry 216 for the receiving and transmitting of TDM traffic into and out of network element 102 .
- TDM switching circuitry 216 receive TDM traffic from physical connection circuitry 210 A-D and switches this traffic to any of physical connection circuitry 210 A-D, based on configuration data for the timeslots of the TDM traffic.
- TDM switching circuitry 216 could be configured such that data within the first ten timeslots of a TDM signal, such as a SONET/SDH signal, received on a first interface of physical connection circuitry 210 a are forwarded out the first five timeslots of a TDM signal being transmitted out from a first interface of physical connection circuitry 210 d.
- a TDM signal such as a SONET/SDH signal
- FIG. 3 is a more detailed block diagram of physical connection circuitry 210 A-D, according to embodiments of the present invention.
- physical connection circuitry 210 A-D (hereinafter physical connection circuitry 210 ) includes framing unit 302 , deframing unit 304 , receiving protocol processing unit 306 , transmitting protocol processing unit 308 , register arrays 314 a - i , register arrays 316 a - i , memory control circuit 318 and memory control circuit 320 .
- memory control circuit 342 is coupled to memory unit 312
- memory control circuit 340 is coupled to memory unit 310 .
- Memory control circuit 342 is also coupled to egress packet processing circuitry 214 A-D (hereinafter egress packet processing circuitry 214 ), and memory control circuit 340 is coupled to ingress packet processing circuitry 212 A-D (hereinafter ingress packet processing circuitry 212 ).
- Memory units 310 and 312 can be any type of read/write memory.
- memory units 310 and 312 are random access memories (RAMs).
- memory units 310 and 312 can be static RAMS.
- Register arrays 314 a - i and register arrays 316 a - i are also any type of read/write memory.
- register arrays 314 a - i and register arrays 316 a - i are registers.
- Deframing unit 304 is coupled to receive signal 318 . Additionally, deframing unit 304 is coupled to receiving protocol processing unit 306 , which is coupled to memory control unit 340 and register arrays 316 a - i . Framing unit 302 is coupled to transmitting protocol processing unit 308 , which is coupled to memory control unit 342 and register arrays 314 a - i . Moreover, framing unit 302 transmits signal 320 out from physical connection circuitry 210 .
- FIG. 4 is a more detailed block diagram of another embodiment of physical connection circuitry 210 A-D, according to embodiments of the present invention. Similar to the embodiment illustrated in FIG. 3 , the embodiment of physical connection circuitry 210 illustrated in FIG. 4 includes framing unit 302 , deframing unit 304 , receiving protocol processing unit 306 , transmitting protocol processing unit 308 , register arrays 314 a - i , register arrays 316 a - i , memory control circuit 318 and memory control circuit 320 . Additionally, physical connection circuitry 210 includes receiving channelizing unit 402 and transmitting channelizing unit 404 .
- Receiving channelizing unit 402 includes buffers 406 a - i
- transmitting channelizing unit 404 includes buffers 408 a - i
- memory units 310 - 312 are internal to physical connection circuitry 210 .
- Memory control circuit 342 is coupled to memory unit 312 , while memory control circuit 340 is coupled to memory unit 310 . Memory control circuit 342 is also coupled to egress packet processing circuitry 214 A-D (hereinafter egress packet processing circuitry 214 ), and memory control circuit 340 is coupled to ingress packet processing circuitry 212 A-D (hereinafter ingress packet processing circuitry 212 ).
- Memory units 310 and 312 can be any type of read/write memory.
- memory units 310 and 312 are random access memories (RAMs).
- memory units 310 and 312 can be static RAMS.
- Register arrays 314 a - i and register arrays 316 a - i are also any type of read/write memory.
- register arrays 314 a - i and register arrays 316 a - i are registers.
- Deframing unit 304 is coupled to receive signal 318 . Additionally, deframing unit 304 is coupled to receiving channelizing unit 402 . Receiving channelizing unit 402 is coupled to receiving protocol processing unit 306 , which is coupled to memory control unit 340 and register arrays 316 a - i . Framing unit 302 is coupled to transmitting channelizing unit 404 . Transmitting channelizing unit 404 is coupled to transmitting protocol processing unit 308 , which is coupled to memory control unit 342 and register arrays 314 a - i . Moreover, framing unit 302 transmits signal 320 out from physical connection circuitry 210 . The operation of physical connection circuitry 210 will now be described in conjunction with FIGS. 5-12 below.
- FIG. 5 is a block diagram of a portion of physical connection circuitry 210 A-D, according to embodiments of the present invention. The operations of the portions of protocol processing unit 306 illustrated in FIG. 5 will be described in more detail in conjunction with the flow diagram illustrated in FIG. 6 .
- receiving protocol processing unit 306 includes protocol engine 502 .
- protocol engine 502 includes hardware circuitry including digital logic. Alternatively, in addition to hardware circuitry, protocol engine 502 includes software for controlling the hardware circuitry.
- Protocol engine 502 is coupled to receiving channelizing unit 402 and memory control unit 340 .
- Memory control unit 340 is coupled to memory unit 310 .
- Receiving channelizing unit 402 is coupled to deframing unit 304 , and deframing unit 304 receives signal 318 .
- FIG. 6 illustrates a flow diagram for the processing of data being received into a network element, according to embodiments of the present invention.
- FIG. 6 includes flow diagram 600 that illustrates the processing of data received by receiving protocol processing unit 306 .
- Flow diagram 600 commences with the receipt of data in signal 318 by deframing unit 304 , at process block 602 .
- the signal 318 includes portions of data packets.
- deframing unit 304 receives signal 318 from an external network element (not shown).
- physical connection circuitry 210 of FIG. 2 could be located within in-ring network element 102 to receive signal 318 from non-ring network element 110 .
- physical connection circuitry 210 of FIG. 6 could be located within in-ring network element 102 to receive signal 318 from in-ring network element 108 .
- receiving channelizing unit 402 receives signal 318 for placement into buffers.
- receiving channelizing unit 402 includes buffers 406 a - i associated with different channels, wherein the channels include data packets.
- the number of buffers is four.
- buffers 406 a - i can associate a channel with a number of SONET frames, which is described in more detail below in conjunction with FIG. 8 .
- signal 318 is based on the DS-3 standard. In another embodiment, signal 318 is based on the DS-1 standard. In one embodiment, signal 318 comprises a number of DS-3 signals. In one such embodiment, the number of DS-3 signals is included in a SONET/SDH signal. Additionally, in an embodiment, signal 318 is channelized DS-3 signals. FIG. 7 illustrates one embodiment of a number of channelized DS-3 signals.
- FIG. 7 illustrates a number of channelized DS-3 signals that are processed, according to embodiments of the present invention.
- FIG. 7 illustrates 12 channelized DS-3 signals.
- FIG. 7 illustrates channelized DS-3 signals 701 that includes channel 7001 , channel 7002 , channel 7003 through channel 7682 , channel 7683 and channel 7684 .
- channelized DS-3 signals 701 can include 784 channels.
- each of these 784 channels can include a different protocol.
- channel 7001 is configured to process data traffic having a High-level Data Link Control (HDLC) protocol
- channel 7002 is configured to process data traffic (i.e., data packets) having an Asynchronous Transfer Mode (ATM) protocol
- ATM Asynchronous Transfer Mode
- Embodiments of the present invention can incorporate different types of the ATM protocol including but not limited to direct map, Physical Layer Convergence Protocol (PLCP) and ATM Adaptation Layer (AAL5).
- channel 7003 is configured to process data traffic having a Voice over Internet Protocol (VoIP) protocol
- channel 7683 is configured to process data traffic having an HDLC protocol.
- the above-described protocols are by way of example and not by way of limitation, as other types of protocols can be incorporated into embodiments of the present invention.
- channel 7684 illustrates another example of a mode, termed transparent mode, that data can be in for processing by receiving protocol processing unit 306 .
- a channel may not be associated with a protocol. Accordingly, receiving protocol processing unit 306 forwards the data as a number of bits, independent of a protocol.
- Channel 7682 illustrates another type of data that can be transmitted within a channel of channelized DS-3 signals 701 .
- channel 7682 transmits control data.
- this control data for a given control channel is associated with the DS-3 signal or one of the 28 DS-1s within the DS-3 channel.
- one channelized DS-3 signal can include 29 channels carrying control data (i.e., control channels), which includes a control channel for the channelized DS-3 signal and a control channel for each of the 28 DS-1 signals.
- the control channel for the channelized DS-3 is a maintenance data link (MDL) channel
- the control channels for the 28 DS-1s are facility data link (FDL) channels, as is known in the art.
- MDL maintenance data link
- FDL facility data link
- these different control channels being processed within physical connection circuitry 210 employ the HDLC protocol. In another embodiment, these different control channels being processed within physical connection circuitry 210 employ the transparent mode. However, embodiments of the present invention are not limited to the employment of the HDLC protocol or the transparent mode for use in these different control channels, as other types of protocols can be incorporated for the usage in these control channels.
- channels in channelized DS-3 signals 701 can have a same protocol, such channels can have different configurations for such a protocol.
- channel 7001 and channel 7683 both carry High-level Data Link Control (HDLC) traffic.
- the configuration for HDLC for channel 7001 can be different than the configuration for HDLC for channel 7683 .
- HDLC can support different scrambling modes, such as Asynchronous Transfer Mode (ATM) type scrambling and Larscom scrambling.
- ATM Asynchronous Transfer Mode
- the configuration for channel 7001 could include an ATM type scrambling
- the configuration for channel 7683 could include Larscom scrambling.
- Embodiments of the present invention are described in terms of a DS-3 or DS-1 signal. However, this is by way of example and not by way of limitation, as other types of signals carrying multiple protocols can be incorporated into embodiments of the present invention.
- Channelized DS-3 signals 701 which are being processed by embodiments of the present invention, are by way of example and not by way of limitation, as other types of signals in other types of configurations can be incorporated into embodiments of the present invention.
- portions of these DS-3 signals may be channelized while the others may be unchannelized. Accordingly, the number of channels to be processed can vary depending on the type and number of incoming signals as well as the configuration of such signal(s).
- the channels are traversed in sequential order starting with channel 7001 up through channel 7684 .
- the channels are prioritized such that certain channels are processed more frequently in comparison to other channels within the signal being received by receiving protocol processing unit 306 .
- control channels typically are not required to be serviced as frequently in comparison to channels carrying data.
- channels 7001 - 7003 and 7683 - 7684 are serviced by receiving protocol processing unit 306 more frequently in comparison to channel 7682 .
- the above embodiments of the order of traversal are by way of example and not by way of limitation, as any other type of order of traversal may be incorporated into embodiments of the present invention.
- signal 318 includes a number of unchannelized DS-3 signals.
- Unchannelized signals are not subdivided into a number of channels. Therefore, unchannelized DS-3s do not include a number of channels or a number of DS-1s, as described above.
- an unchannelized signal may be thought of as one large pipe, while a channelized signal may be a large pipe containing a number of smaller pipes.
- FIG. 8 illustrates a number of unchannelized DS-3 signals that are processed, according to embodiments of the present invention.
- FIG. 8 illustrates unchannelized signals 1 through 24 .
- 12 of the 24 signals are data channels and 12 are control channels.
- the control channels are MDL control channels, as known in the art.
- embodiments of the present invention can incorporate different ATM protocols including but not limited to direct map, Physical Layer Convergence Protocol (PLCP) and ATM Adaptation Layer (AAL5). Additionally, embodiments may configure some unchannelized data channels to Voice over Internet Protocol (VoIP) protocol, while configuring others to the HDLC protocol.
- PLCP Physical Layer Convergence Protocol
- AAL5 ATM Adaptation Layer
- Physical connection circuitry 210 A-D performs channel processing using timeslots.
- a timeslot represents a duration for which a task is performed.
- FIG. 9 illustrates a method for processing channels according to embodiments of the present invention.
- signal 318 includes twelve channels, where six are channelized and six are unchannelized.
- timeslot 1 channel 1 's channelized data is processed; during timeslot 2 , channel 2 's unchannelized data is processed, and so on.
- protocol processing unit 306 proceeds with channel 1 , continually repeating this process.
- each “sub-channel” is processed sequentially.
- channel 1 includes 5 channels
- channel 1 's first channel is processed.
- channel 1 's next timeslot its second channel is processed, and so on.
- the channels within a channel can be processed according to any suitable scheduling algorithm.
- receiving protocol processing unit 306 inspects a channel configuration bit, associated with the channel to be processed, in register array 316 a - i . If the configuration bit is set, the channel to be processed is in channelized format, and if the configuration bit is not set, the channel to be processed is in unchannelized format. Alternatively, receiving protocol processing unit 306 may determine whether the channel to be processed is channelized or unchannelized by inspecting values larger than a bit. For example, receiving protocol processing unit 306 may inspect a memory word or half-word in register array 316 a - i.
- receiving protocol processing unit 306 determines whether the signal is channelized or unchannelized based on information received from receiving channelizing unit 402 . For example, receiving channelizing unit 402 sends (along with data to process) a channel and “sub-channel” number (where the channel number is associated with a channelized or unchannelized signal and the “sub-channel” number is associated with a channel within a channelized signal) to the receiving protocol processing unit 306 to indicate which channel and/or sub-channel the data is associated with. From the channel and sub-channel numbers, receiving protocol processing unit 306 can determine whether the signal is channelized or unchannelized.
- the state information for the current channel within the channelized signal is fetched. For example, according to one embodiment of the invention, receiving protocol processing unit 306 fetches the state information of the current channelized channel from register array 316 a - i . More specifically, according to one embodiment of the invention, receiving protocol processing unit 306 fetches the state information of the channel and sub-channel based on the channel and sub-channel indicators sent by the receiving channelizing unit 402 .
- the state information includes information about the data to be processed and the protocol to be used, including any protocol options that are enabled.
- protocol engine 502 may support any number of protocols including HDLC, ATM, IP, and other protocols known in the art. Protocol options define various protocol specific operations that are carried out by protocol engine 502 .
- protocol options could include whether to enable scrambling as well as the type of scrambling that is enabled (e.g., ATM type scrambling, Larscom scrambling, digital link, Kentrox, etc.).
- protocol options include storing previous data received from the channel to be processed.
- receiving protocol processing unit 306 receives and processes one byte for a given channel.
- protocol engine 502 stores a number of previously received bytes for this channel in register array 316 a - i . The number of bytes stored for a given channel is dependent on the protocol associated with the channel.
- receiving protocol processing unit 306 can perform bit “destuffing” upon receipt of a given bit combination, as is known in the art.
- a bit combination of ‘0111110’ indicates that bit “destuffing” for the HDLC protocol is required.
- this bit combination may be across two different bytes received by receiving protocol processing unit 306 .
- receiving protocol processing unit 306 stores a previous byte as part of the previous state for the channel. For example, a previous byte stored in the previous state could include the bit combination of ‘00101001’ while the current byte being received could include the bit combination of ‘11110101’. The last two bits of the previous byte in conjunction with the first six bits of the current byte include the bit combination ‘0111110’, thereby indicating that bit “destuffing” for the HDLC protocol is required.
- embodiments of the present invention are not limited to the storage of a single previous byte associated with a channel in register array 316 a - i , as different protocols may be more demanding in the number of bytes needed to determine relevant information for the given protocol.
- the previous four bytes are stored in the previous state in order to generate the Header Error Check (HEC) for the ATM cells, as is known in the art.
- HEC Header Error Check
- the size of register arrays 316 a - i are large enough to accommodate the most demanding protocol.
- the state information for the current unchannelized signal is fetched. For example, receiving protocol processing unit 306 fetches the state information from register array 316 a - i . According to one embodiment of the invention, receiving protocol processing unit 306 fetches the state information of the unchannelized channel based on the channel indicators sent by the receiving channelizing unit 402 .
- the state information for unchannelized signals is similar to the state information for channelized signals described above.
- the data is processed.
- receiving channelizing unit 402 sends the data stored in its buffer(s) to receiving protocol processing unit 306 for processing.
- protocol engine 502 processes the data according to the state information associated with the current channelized/unchannelized signal.
- Protocol engine 502 processes the data for signals that are channelized and unchannelized.
- the state information can include protocol settings that determine how protocol engine 502 processes the data.
- protocol engine 502 processes data as described above, with reference to state information.
- receiving protocol processing unit 306 forwards the data through the network element. For example, referring to FIG. 4 , receiving protocol processing unit 306 forwards the data as part of a packet, such as an ATM cell, to memory unit 310 through memory control unit 340 . Accordingly, ingress packet processing circuitry 216 retrieves these processed packets from memory unit 310 through memory control unit 340 .
- a packet such as an ATM cell
- ingress packet processing circuitry 216 retrieves these processed packets from memory unit 310 through memory control unit 340 .
- FIG. 10 is a block diagram of a portion of physical connection circuitry 210 A-D, according to embodiments of the present invention.
- transmitting protocol processing unit 308 includes protocol engine 1002 .
- protocol engine 1002 includes hardware circuitry including digital logic.
- protocol engine 1002 includes software for controlling the hardware circuitry.
- Protocol engine 1002 is coupled to register array 314 a - i , memory control unit 342 , and transmitting channelizing unit 404 .
- Memory control unit 342 is coupled to egress packet processing circuitry 214 A-D (not shown).
- Transmitting channelizing unit 404 is coupled to framing unit 302 , and framing unit 302 generates signal 320 .
- FIG. 11 is a flow diagram illustrating the receipt of data, according to embodiments of the invention.
- FIG. 11 will be described with reference to the exemplary embodiment of FIG. 10 .
- it is determined whether the data is in a channelized or unchannelized format. If the data is within a channelized signal, control continues at block 1104 . Otherwise, control continues at block 1110 .
- transmitting protocol processing unit 308 determines whether egress packet processing circuitry 214 A-D (not shown) is attempting to send data in a channelized or unchannelized signal.
- Each of the buffers for channelized data has a read and write pointer associated with it to indicate where in the buffer data was last read and written from.
- Egress packet processing circuitry 214 A-D tracks the position of the read and write pointers for each channel, so it can determine the available space for each buffer. For example, the available space can be calculated by subtracting the space between the read and write pointers from the entire buffer space. As a more specific example, if the buffer holds ten data bytes and the space between the read and write pointers is eight bytes, there are two bytes of storage space available.
- the data is sent. For example, upon determining there is available space, egress packet processing circuitry 214 A-D sends the data to transmitting protocol processing unit 308 . Control continues at block 1109 .
- the data is stored.
- transmitting protocol processing unit 308 stores the data in a buffer in memory unit 310 .
- the data is dropped. For example, if there is no space in the appropriate buffer, the data is dropped (i.e. the data is not sent to the transmitting protocol processing unit 308 ; it is discarded).
- a write request is sent.
- egress packet processing circuitry 214 A-D sends a write request to transmitting protocol processing unit 308 indicating that it has (unchannelized) data to send.
- Control continues at block 1112 .
- control continues at block 1106 . Otherwise, control continues at block 1114 . For example, if buffer space is available in the appropriate unchannelized data buffer (the concept of buffers is described above with reference to block 1104 ), transmitting protocol processing unit 308 sends an acknowledgement to egress packet processing circuitry 214 A-D. If buffer space is not available, transmitting protocol processing unit 308 does not send an acknowledgement to egress packet processing circuitry 214 A-D.
- egress packet processing circuitry 214 A-D does not send data to transmitting protocol processing unit 308 until an acknowledgement is received. Control continues at block 1112 .
- FIG. 12 illustrates a flow diagram for the processing of data being transmitted out from a network element, according to embodiments of the present invention.
- FIG. 12 includes flow diagram 1200 that illustrates the processing of data packets received by transmitting protocol processing unit 308 that are stored in memory unit 312 .
- such data packets that are stored in memory unit 312 are being received from egress packet processing circuitry 214 A-D.
- transmitting protocol processing unit 308 determines which channel to process based on a table stored in memory within physical connection circuitry 210 (not shown), a prioritization scheme, or other suitable method. Such a table sets the order of traversal of the different channels of signal 320 .
- framing unit 302 determines which channel to process based on a table stored in memory within physical connection circuitry 210 (not shown), a prioritization scheme, or other suitable method. Once framing unit 302 makes this determination, it sends a signal to transmitting protocol processing unit 308 indicating which channel to process.
- channels are traversed in sequential order starting with channel 7001 up through channel 7684 .
- the channels are prioritized such that certain channels are processed more frequently in comparison to other channels within signal 320 .
- control channels typically are not required to be serviced as frequently in comparison to channels carrying data.
- channels 7001 - 7003 and 7683 - 7684 are serviced by transmitting protocol processing unit 308 more frequently in comparison to channel 7682 .
- the above embodiments of the order of traversal are by way of example and not by way of limitation, as any other type of order of traversal may be incorporated into embodiments of the present invention.
- protocol engine 1002 determines whether the channel contains channelized data or unchannelized data. As similarly described above, in an embodiment of the present invention, protocol engine 1002 inspects a channel configuration bit, associated with the channel to be processed, in state memory 1004 . If the configuration bit is set, the channel to be processed is in channelized format, and if the configuration bit is not set, the signal to be processed is in unchannelized format. Alternative embodiments use other data structures to indicate whether the signal is channelized or unchannelized (e.g. they may use bytes or some other number of bits).
- protocol engine 1002 determines the protocol settings of the channel to be processed. Protocol engine 1002 retrieves the protocol settings associated with the channel to be processed from state memory 1004 .
- the protocol settings include information about the channel protocol to be used and any protocol options that are enabled.
- protocol engine 1002 may support any number of protocols including HDLC, ATM, IP, and other protocols known in the art. Protocol options define various protocol specific operations that are carried out by protocol engine 1002 .
- transmitting protocol processing unit 308 retrieves at least a portion of a data packet that is to be transmitted on the selected channel.
- protocol engine 1002 delays the retrieval of portions of a data packet until a threshold amount of the entire data packet has been stored in memory unit 312 .
- protocol engine 1002 delays the retrieval of a portion of data for a given ATM cell until a threshold portion of the payload has been stored in memory unit 312 by egress packet processing circuitry 214 A-D.
- protocol engine 1002 forwards an idle ATM cell to framing unit 302 .
- protocol engine 1002 checks this threshold amount for the entire data packet for the first portion of the data packet being processed by transmitting protocol processing unit 308 .
- embodiments of the present invention are not so limited, as certain data packets may contain multiple data cells, depending on the protocol and protocol configuration.
- a channel transmitting an ATM protocol may be transmitting a data packet that can contain more than a single ATM cell therein.
- transmitting protocol processing unit 308 checks if the threshold value for an ATM cell within a given data packet and not just the entire data packet for a given ATM cell has been reached prior to the transmission of the ATM cell to framing unit 302 .
- each of the different protocols as well as each of the different channels of a same protocol can configure this threshold value.
- Embodiments of the present invention are not limited to the transmission of an idle cell if the data is not complete, as described in conjunction with the ATM protocol above.
- transmitting protocol processing unit 308 can retransmit the previous packet for the given channel.
- transmitting protocol processing unit 308 proceeds with the processing of this packet to send to framing unit 302 . Accordingly, this checking of threshold values by transmitting protocol processing unit 308 precludes underrunning, which is condition wherein transmitting protocol processing unit 308 does not have enough of a data packet to complete the transmission of the entire data packet to framing unit 302 .
- transmitting protocol processing unit 308 processes the data in the selected channel. Transmitting protocol processing unit 308 processes data in the selected channel based on whether the channel is channelized or unchannelized, the channel's protocol, and the data retrieved from memory unit 312 . In one embodiment, the processing of the data for this given channel includes encapsulating the data into a particular protocol, such as ATM, HDLC, or Voice over IP. Moreover, in an embodiment, the channel protocol settings include whether the channel is enabled, the type of protocol as well as the enabled protocol options associated with the selected channel. For example, for the HDLC protocol, configurations could include whether to enable scrambling as well as the type of scrambling enabled (e.g., ATM type scrambling, Larscom scrambling, digital link, Kentrox, etc.).
- transmitting protocol processing unit 308 places the processed data in the selected channel. Transmitting protocol processing unit 308 sends the processed data to a location within transmitting channelizing unit 404 that is associated with the selected channel. Transmitting channelizing unit 404 forwards the data to framing unit 302 , which inserts the data into the selected channel of signal 320 .
- Embodiments of the present invention are not limited to the channelized DS-3 signals, as illustrated in FIG. 6 .
- embodiments of the present invention can be incorporated into channelized DS-1 signals, unchannelized DS-3 signals, unchannelized DS-1 signals as well as both channelized and unchannelized T1 and T3 signals.
- physical connection circuitry 210 is incorporated into a single Application Specific Integrated Circuit (ASIC).
- ASIC Application Specific Integrated Circuit
- signals based on the SONET/SDH standard can be incorporated into embodiments of the present invention.
- signals based on the SONET/SDH standard can concatenate Synchronous Transport Signal (STS)-1 frames such that different STS-1 frames and/or the different concatenation of STS-1 frames can be processed by physical connection circuitry 210 differently as described above.
- STS Synchronous Transport Signal
- FIG. 13 is a block diagram of a SONET signal carrying data, according to embodiments of the present invention.
- FIG. 13 illustrates a STS-48 SONET signal, which could be transmitted among in-ring network elements 102 - 108 of FIG. 1 .
- the 48 frames of this STS-48 signal are apportioned into different groups.
- data traffic within this STS-48 signal is located in STS1-9, STS10-11, STS12-21, STS22-23, STS24-35, STS36-37, STS38-44, STS45-46 and STS47-48 within SONET portions 1302 , 1304 , 1306 , 1308 , 1310 , 1312 , 1314 , 1316 and 1318 , respectively.
- each of the groups of STS frames are concatenated together.
- STS frames 24 - 35 are concatenated together.
- the concatenation of STS frames within the SONET/SDH signals can be of any size and across any location within the SONET/SDH signals, which is described in more detail in a patent application titled “Any Size and Location of Concatenated Packet Data across TDM frames in a TDM signal” to Anurag Nigam and David Stiles, filed on Dec. 30, 2000, Ser. No. 09/751,764, which is hereby incorporated by reference.
- each of the individual frames of the SONET/SDH signals and/or concatenation of frames of the SONET/SDH signal can be processed by physical connection circuitry 210 such that each frame and/or concatenation includes a different protocol and/or protocol configuration, as described above in conjunction with the DS-1/DS-3 signals.
- SONET portion 1302 could be configured to process an ATM protocol having a first set of configurations
- SONET portion 1304 could be configured to process a Frame Relay protocol having a first set of configurations.
- SONET portion 1306 could be configured to process a voice over IP protocol having a first set of configurations
- SONET portion 1308 could be configured to process a PPP protocol having a first set of configurations.
- SONET portion 1310 could be configured to process an IP protocol having a first set of configurations
- SONET portion 1312 could be configured to process a Frame Relay protocol having a second set of configurations
- SONET portion 1314 could be configured to process an IP protocol having a second set of configurations
- SONET 1316 could be configured to process an ATM protocol having a second set of configurations
- SONET portion 1318 could be configured to process a Frame Relay protocol having a third set of configurations.
- the delineation and configuration of the SONET signal illustrated in FIG. 13 is by way of example and not by way of limitation, as other SONET signals wherein the STS frames are delineated differently and/or the types of protocols and/or configurations incorporated into such delineations are different.
- embodiments of the present invention are not limited to a DS-1, DS-3, T1, T3 or SONET-based signals.
- any type of data transmission signal that can be broken down into different portions such that these portions can be processed differently depending on the different protocols and/or protocol configurations.
- the line cards and control cards included in the different network elements include memories, processors and/or Application Specific Integrated Circuits (ASICs), Such memory includes a computer-readable medium on which is stored a set of instructions (i.e., software) embodying any one, or all, of the methodologies described herein. Software can reside, completely or at least partially, within this memory and/or within the processor and/or ASICs.
- a computer-readable medium shall be taken to include any mechanism that stores information in a form readable by a computer).
- a computer-readable medium includes read only memory (ROM); random access memory (RAM); magnetic disk storage media; optical storage media; flash memory devices.
Abstract
Description
Claims (41)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/109,521 US7324539B1 (en) | 2001-11-28 | 2002-03-28 | Method and apparatus for processing channelized and unchannelized data within a signal |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US33384501P | 2001-11-28 | 2001-11-28 | |
US10/109,521 US7324539B1 (en) | 2001-11-28 | 2002-03-28 | Method and apparatus for processing channelized and unchannelized data within a signal |
Publications (1)
Publication Number | Publication Date |
---|---|
US7324539B1 true US7324539B1 (en) | 2008-01-29 |
Family
ID=38973969
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/109,521 Active 2024-10-27 US7324539B1 (en) | 2001-11-28 | 2002-03-28 | Method and apparatus for processing channelized and unchannelized data within a signal |
Country Status (1)
Country | Link |
---|---|
US (1) | US7324539B1 (en) |
Citations (28)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5268936A (en) | 1991-07-08 | 1993-12-07 | At&T Bell Laboratories | Synchronous digital signal to asynchronous digital signal desynchronizer |
US5400369A (en) | 1992-07-15 | 1995-03-21 | Oki Electric Industry Co., Ltd. | Fram aligner with reduced circuit scale |
US5490252A (en) * | 1992-09-30 | 1996-02-06 | Bay Networks Group, Inc. | System having central processor for transmitting generic packets to another processor to be altered and transmitting altered packets back to central processor for routing |
US5511077A (en) | 1993-06-30 | 1996-04-23 | Nec Corporation | Frame transmission system |
US5519700A (en) | 1994-12-07 | 1996-05-21 | At&T Corp. | Telecommunication system with synchronous-asynchronous interface |
US5533018A (en) | 1994-12-21 | 1996-07-02 | National Semiconductor Corporation | Multi-protocol packet framing over an isochronous network |
US5550820A (en) | 1992-09-29 | 1996-08-27 | Com 21, Inc. | Multiple protocol personal communications network system |
US5621773A (en) | 1996-03-08 | 1997-04-15 | Lsi Logic Corporation | Method and apparatus for fast synchronization of T1 extended superframes |
US5805571A (en) | 1996-03-19 | 1998-09-08 | Zwan; Bryan J. | Dynamic communication line analyzer apparatus and method |
US5825770A (en) | 1996-06-06 | 1998-10-20 | Northern Telecom Limited | Multiple algorithm processing on a plurality of digital signal streams via context switching |
US5963564A (en) | 1995-06-13 | 1999-10-05 | Telefonaktiebolaget Lm Ericsson | Synchronizing the transmission of data via a two-way link |
US6038226A (en) | 1997-03-31 | 2000-03-14 | Ericcson Inc. | Combined signalling and PCM cross-connect and packet engine |
US6075788A (en) | 1997-06-02 | 2000-06-13 | Lsi Logic Corporation | Sonet physical layer device having ATM and PPP interfaces |
US6185635B1 (en) | 1998-05-30 | 2001-02-06 | Alcatel Networks Corporation | Method and circuit for transporting data based on the content of ingress data words and egress data words |
US6198751B1 (en) | 1997-11-19 | 2001-03-06 | Cabletron Systems, Inc. | Multi-protocol packet translator |
US6237029B1 (en) | 1996-02-26 | 2001-05-22 | Argosystems, Inc. | Method and apparatus for adaptable digital protocol processing |
US6272144B1 (en) | 1997-09-29 | 2001-08-07 | Agere Systems Guardian Corp. | In-band device configuration protocol for ATM transmission convergence devices |
US6272151B1 (en) * | 1994-05-19 | 2001-08-07 | Cisco Technology, Inc. | Scalable multimedia network |
US6285673B1 (en) | 1998-03-31 | 2001-09-04 | Alcatel Usa Sourcing, L.P. | OC3 delivery unit; bus control module |
US6320877B1 (en) | 1997-10-02 | 2001-11-20 | Alcatel Usa Sourcing, L.P. | System and method for data bus interface |
US20020018468A1 (en) | 2000-08-10 | 2002-02-14 | Nec Corporation | Device, method and system for transferring frame |
US6385209B1 (en) | 2000-06-14 | 2002-05-07 | Pluris, Inc. | Method and apparatus for mapping data packets between lines of differing capacity at a router interface |
US6466591B1 (en) * | 2000-12-30 | 2002-10-15 | Redback Networks Inc. | Method and apparatus for processing of multiple protocols within data and control channels in data transmission signals |
US6765916B1 (en) * | 2000-12-30 | 2004-07-20 | Redback Networks Inc. | Method and apparatus for processing of multiple protocols within data transmission signals |
US6778561B1 (en) * | 2000-02-23 | 2004-08-17 | Cypress Semiconductor Corp. | Hybrid data transport scheme over optical networks |
US20040252688A1 (en) * | 2001-08-28 | 2004-12-16 | May George Anthony | Routing packets in frame-based data communication networks |
US20050180429A1 (en) * | 1999-02-23 | 2005-08-18 | Charlie Ghahremani | Multi-service network switch with independent protocol stack architecture |
US6990121B1 (en) * | 2000-12-30 | 2006-01-24 | Redback, Networks, Inc. | Method and apparatus for switching data of different protocols |
-
2002
- 2002-03-28 US US10/109,521 patent/US7324539B1/en active Active
Patent Citations (29)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5268936A (en) | 1991-07-08 | 1993-12-07 | At&T Bell Laboratories | Synchronous digital signal to asynchronous digital signal desynchronizer |
US5400369A (en) | 1992-07-15 | 1995-03-21 | Oki Electric Industry Co., Ltd. | Fram aligner with reduced circuit scale |
US5550820A (en) | 1992-09-29 | 1996-08-27 | Com 21, Inc. | Multiple protocol personal communications network system |
US5490252A (en) * | 1992-09-30 | 1996-02-06 | Bay Networks Group, Inc. | System having central processor for transmitting generic packets to another processor to be altered and transmitting altered packets back to central processor for routing |
US5511077A (en) | 1993-06-30 | 1996-04-23 | Nec Corporation | Frame transmission system |
US6272151B1 (en) * | 1994-05-19 | 2001-08-07 | Cisco Technology, Inc. | Scalable multimedia network |
US5519700A (en) | 1994-12-07 | 1996-05-21 | At&T Corp. | Telecommunication system with synchronous-asynchronous interface |
US5533018A (en) | 1994-12-21 | 1996-07-02 | National Semiconductor Corporation | Multi-protocol packet framing over an isochronous network |
US5963564A (en) | 1995-06-13 | 1999-10-05 | Telefonaktiebolaget Lm Ericsson | Synchronizing the transmission of data via a two-way link |
US6237029B1 (en) | 1996-02-26 | 2001-05-22 | Argosystems, Inc. | Method and apparatus for adaptable digital protocol processing |
US5621773A (en) | 1996-03-08 | 1997-04-15 | Lsi Logic Corporation | Method and apparatus for fast synchronization of T1 extended superframes |
US5805571A (en) | 1996-03-19 | 1998-09-08 | Zwan; Bryan J. | Dynamic communication line analyzer apparatus and method |
US5825770A (en) | 1996-06-06 | 1998-10-20 | Northern Telecom Limited | Multiple algorithm processing on a plurality of digital signal streams via context switching |
US6038226A (en) | 1997-03-31 | 2000-03-14 | Ericcson Inc. | Combined signalling and PCM cross-connect and packet engine |
US6075788A (en) | 1997-06-02 | 2000-06-13 | Lsi Logic Corporation | Sonet physical layer device having ATM and PPP interfaces |
US6272144B1 (en) | 1997-09-29 | 2001-08-07 | Agere Systems Guardian Corp. | In-band device configuration protocol for ATM transmission convergence devices |
US6320877B1 (en) | 1997-10-02 | 2001-11-20 | Alcatel Usa Sourcing, L.P. | System and method for data bus interface |
US6198751B1 (en) | 1997-11-19 | 2001-03-06 | Cabletron Systems, Inc. | Multi-protocol packet translator |
US20010033580A1 (en) | 1997-11-19 | 2001-10-25 | Dorsey Paul C. | Multi-protocol packet translator |
US6285673B1 (en) | 1998-03-31 | 2001-09-04 | Alcatel Usa Sourcing, L.P. | OC3 delivery unit; bus control module |
US6185635B1 (en) | 1998-05-30 | 2001-02-06 | Alcatel Networks Corporation | Method and circuit for transporting data based on the content of ingress data words and egress data words |
US20050180429A1 (en) * | 1999-02-23 | 2005-08-18 | Charlie Ghahremani | Multi-service network switch with independent protocol stack architecture |
US6778561B1 (en) * | 2000-02-23 | 2004-08-17 | Cypress Semiconductor Corp. | Hybrid data transport scheme over optical networks |
US6385209B1 (en) | 2000-06-14 | 2002-05-07 | Pluris, Inc. | Method and apparatus for mapping data packets between lines of differing capacity at a router interface |
US20020018468A1 (en) | 2000-08-10 | 2002-02-14 | Nec Corporation | Device, method and system for transferring frame |
US6466591B1 (en) * | 2000-12-30 | 2002-10-15 | Redback Networks Inc. | Method and apparatus for processing of multiple protocols within data and control channels in data transmission signals |
US6765916B1 (en) * | 2000-12-30 | 2004-07-20 | Redback Networks Inc. | Method and apparatus for processing of multiple protocols within data transmission signals |
US6990121B1 (en) * | 2000-12-30 | 2006-01-24 | Redback, Networks, Inc. | Method and apparatus for switching data of different protocols |
US20040252688A1 (en) * | 2001-08-28 | 2004-12-16 | May George Anthony | Routing packets in frame-based data communication networks |
Non-Patent Citations (1)
Title |
---|
Kusky, R.G., et al., "Analysis of Techniques for the Reduction of Jitter Caused by SONET Pointer Adjustments," IEEE Transactions on Communications, vol. 42, No. 2/3/4, pp. 2036-2050, Feb./Mar./Apr. 1994. |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US6466591B1 (en) | Method and apparatus for processing of multiple protocols within data and control channels in data transmission signals | |
US7460554B2 (en) | Any size and location of concatenated packet data across SONET frames in a SONET signal | |
US7298738B1 (en) | Backpressuring using a serial bus interface and a status switch cell | |
US6765916B1 (en) | Method and apparatus for processing of multiple protocols within data transmission signals | |
USRE40809E1 (en) | Conversion of contiguous concatenation of virtual concatenation in a synchronous digital communication network | |
US8416770B2 (en) | Universal service transport transitional encoding | |
US20050271059A1 (en) | Network protocol conversions and routing methods and apparatus | |
US20040252688A1 (en) | Routing packets in frame-based data communication networks | |
US7848323B2 (en) | Method for transporting data packets, data network system, and network nodes | |
US20040028051A1 (en) | System and method for implementing combined packetized TDM streams and TDM cross connect functions | |
US8107362B2 (en) | Multi-ring resilient packet ring add/drop device | |
US7050395B1 (en) | Method and apparatus for disabling an interface between network element data processing units | |
US7586925B2 (en) | Data adaptation protocol | |
US20030016699A1 (en) | Alignment of TDM-based signals for packet transmission using framed and unframed operations | |
US7272675B1 (en) | First-in-first-out (FIFO) memory for buffering packet fragments through use of read and write pointers incremented by a unit access and a fraction of the unit access | |
US6510166B2 (en) | Stuffing filter mechanism for data transmission signals | |
EP1701495A1 (en) | Hybrid digital cross-connect for switching circuit and packet based data traffic | |
US6898647B2 (en) | Parallel byte processing engines shared among multiple data channels | |
US7379467B1 (en) | Scheduling store-forwarding of back-to-back multi-channel packet fragments | |
US20050053053A1 (en) | Method and apparatus for synchronized transport of data through an asynchronous medium | |
EP1339198B1 (en) | Enhanced transport of ethernet traffic over a transport SDH/SONET network | |
US7206310B1 (en) | Method and apparatus for replicating packet data with a network element | |
US6928080B2 (en) | Transporting variable length ATM AAL CPS packets over a non-ATM-specific bus | |
US7324539B1 (en) | Method and apparatus for processing channelized and unchannelized data within a signal | |
EP2197131B1 (en) | Method and apparatus for synchronized transport of data through an asynchronous medium |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: REDBACK NETWORKS INC., CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:DUVVURU, RAMESH;CHOW, FELIX;SEE, RICKY;AND OTHERS;REEL/FRAME:013150/0732;SIGNING DATES FROM 20020504 TO 20020617 |
|
AS | Assignment |
Owner name: SILICON VALLEY BANK, CALIFORNIA Free format text: SECURITY AGREEMENT;ASSIGNOR:REDBACK NETWORKS INC.;REEL/FRAME:014499/0957 Effective date: 20040310 Owner name: SILICON VALLEY BANK,CALIFORNIA Free format text: SECURITY AGREEMENT;ASSIGNOR:REDBACK NETWORKS INC.;REEL/FRAME:014499/0957 Effective date: 20040310 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
AS | Assignment |
Owner name: ERICSSON AB,SWEDEN Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:REDBACK NETWORKS INC.;REEL/FRAME:024002/0363 Effective date: 20070125 Owner name: ERICSSON AB, SWEDEN Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:REDBACK NETWORKS INC.;REEL/FRAME:024002/0363 Effective date: 20070125 |
|
FPAY | Fee payment |
Year of fee payment: 4 |
|
FPAY | Fee payment |
Year of fee payment: 8 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 12TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1553); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 12 |