
PRELIMINARY
XRT86SH221
76
REV. P1.0.5
SDH-TO-PDH FRAMER/MAPPER WITH INTEGRATED 21-CHANNEL E1 SH LIU
DESIGN DESCRIPTION
The function of this reusable block is limited to the construction and extraction of the VT structured content of
the SDH STM-0 Payload Capacity / SDH VC-3 as described by Telcordia's GR-253-CORE Generic
Requirements and ITU-T's G.707 recommendations. The rest of the work for the higher levels of hierarchy
including Transport and Path Overhead is handled by the STM-0 SDH blocks.
VT STRUCTURED STM-0 PAYLOAD CAPACITY
This section briefly describes the structure of the SDH data stream used to carry lower bit-rate channels. The
STM-0 Payload Capacity is made up of 84 columns of 9 rows each. The Payload Capacity is divided equally
amongst seven Groups. Each Group can contain three VT2/TU-12 tributaries. VT2/TU-12 tributaries are used
to carry an E1 signal.
VT Superframe
Four consecutive STM-0 frames of Payload Capacity are used to make up a VT Superframe. The first byte of
each Tributary in each frame has a special function. These special bytes are called V1 to V4.
V1 & V2 : VT Payload Pointer
The V1 and V2 bytes form the VT Payload Pointer. In asynchronous mappings or on transmission, the VT
Payload Pointer is assigned a fixed value by this block such that the V5, J2, Z6/N2 and Z7/K4 bytes
immediately follow the V1 to V4 bytes. In synchronous mappings or on reception, the VT Payload Pointer is
processed as prescribed in Telcordia and ITU. Each time a received VT Payload Pointer is incremented or
decremented, internal counters are available to be read by the processor in registers BIP2CNT1 to
BIP2CNT21 and REICNT1 to REICNT21 are incremented.
V3 : VT Pointer Action Byte
This byte is used as a negative stuff byte when required by a pointer decrement. Otherwise, it is Undefined. It
is never used by this block on transmission of asynchronously mapped signals. In synchronous mappings or
on reception, this byte is processed along with the VT Payload Pointer bytes as prescribed in the Telcordia and
ITU documents.
V4 : Undefined
This byte is reserved for future growth and is treated as Undefined. It is ignored on reception and is transmitted
as all zeros.
VT Path Overhead
Each Virtual Tributary has it's own set of Path Overhead bytes which are processed as described in the
following paragraphs.
V5 : VT Path Error Checking, Signal Label and Path Status
The bit assignments for the V5 byte are shown in
Table 7
.
Bits [7:6] of V5 are used for error performance monitoring. A BIP-2 scheme is defined as follows. When
generating a tributary, bit 7 is set to the exclusive-or of all the odd numbered bits (bits 7,5,3 and 1) of the
previous VT SPE (including the V5, J2, Z6/N2 or Z7/K4 byte but not the V1 to V4 bytes, except V3 when it is
used as a negative stuff byte), bit 6 is set to the exclusive-or of all the even numbered bits (bits 6, 4, 2 and 0) of
the previous VT SPE. When terminating a tributary, bit 7 is compared to the exclusive-or of all the odd
numbered bits of the previous VT SPE, bit 6 is compared to the exclusive-or of all the even numbered bits of
the previous VT SPE. If there is any difference, bit 5 of V5 (REI-V) of the peer tributary generator is set to "1",
T
ABLE
7: V5 - VT P
ATH
E
RROR
C
HECKING
, S
IGNAL
L
ABEL
AND
P
ATH
S
TATUS
7 (MSB)
6
5
4
3
2
1
0 (LSB)
BIP-2
REI-V
RFI-V
Signal Label
RDI-V