DS34S132GNA2+ Maxim Integrated, DS34S132GNA2+ Datasheet - Page 29

• Manufacturer Part Number: DS34S132GNA2+
• Description: Communication ICs - Various 32Port TDM-Over-Pack Transport Device
• Manufacturer: Maxim Integrated

Specifications of DS34S132GNA2+

• Rohs: yes
• Part # Aliases: 90-34S13+2N2

9.1 Connection Types
The following subsections describe the different connection types in more detail.
9.1.1 SAT/CES Payload Connections
The S132 can support up to 256 SAT/CES Payload Connections spread across 32 TDM Ports. Each SAT/CES
Payload Connection carries constant bit rate data and is programmed as part of a Bundle. In the RXP direction, the
Classifier identifies a packet for a SAT/CES Payload Connection when the received Header and PW-ID match that
of a Bundle and that Bundle is programmed to forward payload data to a SAT/CES Engine. The SAT/CES Payload
Connection is diagramed in
Figure 9-3. SAT/CES Payload Connection
Each Bundle can be configured to support any number of DS0s up to an entire TDM Port line rate. In the RXP
direction the PW Header is stripped off of the packets and the payload is stored in a Jitter Buffer to smooth the
bursty transmission of the PSN. In the TXP direction, when sufficient SAT/CES Payload has been received the
S132 appends a configured TXP Bundle Header to generate a PW packet. A Timeslot Assignment block provides a
DS0 cross-connect function to interconnect the payload of any SAT/CES Bundle to any set of DS0 positions on a
single TDM Port and to allow control and monitoring of Sub-channel CAS Signaling and Data Conditioning.
A Bundle that includes a SAT/CES Payload Connection can also include a PW-Timing Connection and an In-band
VCCV (CPU) Connection (the PW-Timing and CPU Connections are described in the sections that follow).
9.1.2 HDLC Connections
The S132 supports up to 256 HDLC Connections. This connection type can be used to support T1/E1 CCS
Signaling or other HDLC encoded packet streams. Each HDLC Connection is programmed as part of a Bundle. In
the RXP direction, the Classifier identifies a packet for an HDLC Connection when the header and PW-ID of a
received packet matches the Header protocol and BID of a Bundle and that Bundle is programmed to forward data
to an HDLC Engine. The HDLC Connection is diagramed in
Figure 9-4. Bundle HDLC Connection
At the TDM Port the HDLC data appears as constant bit rate data because the HDLC packet stream, at the TDM
Port, is supplemented with Idle HDLC Flags (Idle Flags are used during time periods when there are no HDLC
packets). On the Ethernet/PW side the HDLC encoding does not exist. The HDLC data no longer appears as
constant bit rate data since the HDLC Idle Flags are not carried by the HDLC PWs (only non-idle packet data is
carried by an HDLC PW).
19-4750; Rev1; 7/11
S132
S132
Figure
RXP
TXP
TSA
TSA
9-3.
RXP
TXP
TSA
TSA
Engine
SAT/
CES
Engine
HDLC
Figure
(Jitter) Buffer
RXP Bundle
RXP Bundle
TXP Bundle
TXP Bundle
Jitter Buffer
9-4.
Buffer
Buffer
Generator
Generator
Classifier
Classifier
RXP Pkt
RXP Pkt
TXP Pkt
TXP Pkt
DS34S132 DATA SHEET
29 of 194