PM5363 TUPP+622
TUPP+622
DATASHEET
PMC-1981421
ISSUE 4
SONET/SDH TRIBUTARY UNIT PAYLOAD PROCESSOR FOR 622 MBIT/S
INTERFACES
seven TUG2s, each of which can be independently configured to carry TU11s,
TU12s, or TU2s. (The equivalent of a VT3 is allowed but there is no SDH
nomenclature to describe this.) The associated IC1J1 input is expected to mark
the J1 byte of each VC3 and each VTPP detects the tributary multiframe
encoded in the unique H4 byte that it receives.
AU4 Mode: This mode is enabled when the ICONCAT and OCONCAT bits of an
STP are set high. In AU4 mode, individual VTPPs in an STP must be configured
in either TUG3 mode or TU3 mode. The associated IC1J1 input is expected to
mark the J1 byte of the VC4. This J1 marker is stretched to provide a "J1" marker
to each VTPP. VTPP #2 and VTPP#3 are slaved to the tributary multiframe
indication provided by VTPP #1 as it is the only one that receives a valid H4 byte.
TUG3 Mode: This mode is enabled when the TUG3 bit is set high in a VTPP. In
addition, the ICONCAT and OCONCAT bits of the STP must be set high. The
TUG3 processed by the VTPP is assumed to carry seven TUG2s, each of which
can be independently configured to carry TU11s, TU12s, or TU2s. (The
equivalent of a VT3 is allowed but there is no SDH nomenclature to describe
this.) When an STP in the TUPP+622 is in AU4 mode, each VTPP can be
independently configured in TUG3 or TU3 mode.
TU3 Mode: This mode is enabled when the TU3 bit is set high in a VTPP. In
addition the ICONCAT and OCONCAT bits of the STP must be set high. The
TUG3 processed by the VTPP is assumed to carry a TU3. When an STP in the
TUPP+622 is in AU4 mode, each VTPP can be independently configured in
TUG3 or TU3 mode.
For figures in the operation and functional timing sections, transport overhead
and path overhead bytes are shown for notational convenience only. In the
incoming direction, except for the H4 byte, ID[7:0] (ID[15:8], ID[23:16], ID[31:24])
does not need to contain valid transport and STS/AU path overhead byte values.
The H4 byte must be valid only if H4 framing is enabled (ITMFEN=0). Otherwise,
it too may be invalid. However, the incoming parity must match the data supplied
at all times. In the outgoing direction, TUPP+622 places valid framing, STS/AU
pointer bytes and all-zeros data on OD[7:0] (OD[15:8], OD[23:16], OD[31:24]) for
transport overhead bytes. It generates all zero bytes for the STS/AU path
overhead except for the H4 byte which contains leading ones and an
incrementing two bit pattern. The fixed stuff bytes in the tributary mapping to the
synchronous payload envelope (virtual container) are also generated as all zero
PROPRIETARY AND CONFIDENTIAL TO PMC-SIERRA, INC., AND FOR ITS CUSTOMERS’ INTERNAL USE
377
PMC [ PMC-SIERRA, INC ]
