
Preliminary Data Sheet, Rev. 1
October 2000
TMXF28155 Super Mapper
155/51 Mbits/s SONET/SDH x28/x21 DS1/E1
107
Lucent Technologies Inc.
TMUX Functional Description
(continued)
Receive Direction (Receive Path from Sonet/SDH)
(continued)
B3 BIP-8 Check.
A B3 BIP-8 even parity is computed over all the incoming synchronous payload envelope bits of
the STS-3/STM-1/STS-1 signal after descrambling, and compared to the B3 byte received in the next frame. The
total number of B3 BIP-8 bit errors (raw count), or block errors (as determined by TMUX_BITBLKB3 (Table 56)) is
counted. Upon the configured performance monitor (PM) interval, the value of the internal running counter is
placed into holding registers TMUX_B3ECNT[1—3][15:0] (Table 88) and then cleared. Depending on the value of
SMPR_SAT_ROLLOVER (Table 15) in the microprocessor interface block, the internal counter will either roll over
or stay at its maximum value until cleared.
Signal Label C2 Byte Monitor.
The C2 byte per STS-1/STM-1 is stored in TMUX_C2MON[1—3][7:0] (Table 66).
Each register will be updated after a number, determined by the value in TMUX_CNTDC2[3:0] (Table 61), of con-
secutive frames of identical C2 bytes for a given STS-1/STM-1, i.e., the 8-bit pattern must be identical for a pro-
grammed number frames prior to updating the C2 register. Any change to C2 byte monitor is reported via the
corresponding delta and mask register bits, TMUX_RC2MOND[1—3] (Table 45) and TMUX_RC2MONM[1—3]
(Table 49).
In addition, there are programmable expected value(s) for the C2 bytes of each STS-1/STM-1 in
TMUX_C2EXP[1—3][7:0] (Table 62). If the current value of a C2 byte in TMUX_C2MON[1—3][7:0], does not equal
the expected C2 value in TMUX_C2EXP[1—3][7:0]), then a payload label mismatch defect may be declared for
that STS-1/STM-1 in TMUX_RPLMP[1—3] (Table 54). Also, if the current value of a C2 byte is all 0s, then the cor-
responding unequipped defect is declared in TMUX_RUNEQP[1—3] (Table 54). Note that the payload label mis-
match and unequipped defects are mutually exclusive and that unequipped takes priority. The following table
describes the conditions for generating payload label mismatch (TMUX_RPLMP[1—3]) and unequipped defects
(TMUX_RUNEQP).
Table 27. STS Signal Label Defect Conditions
TMUX_FORCEC2DEF[2:0] will force path payload label mismatch defects on those conditions that are shown on
in Table 27 above.
The continuous N times detection counter(s) will be reset to 0 upon the transition of the framer into the out of frame
state.
Provisioned STS PTE
Functionality, Expected C2
Any Equipped Functionality
Any Equipped Functionality
Equipped—Nonspecific
Any Payload Specific Code
Received Payload Label
(C2 in hex)
Unequipped (00)
Equipped—Nonspecific (01)
Any value (02 to E0, FD to FE)
The same Payload Specific Code
(02 to E0, FD to FE)
A different Payload Specific Code
(02 to E0, FD to FE)
PDI, 1 to 27 VTx defects (E1 to FB)
Defect
TMUX_FORCEC2DEF = 1
(Table 59)
No change
No change
No change
No change
TMUX_RUNEQP
none
none
none
Any Payload Specific Code
TMUX_RPLMP
No change
Equipped—Nonspecific (01)
or VT-Structured
STS-1 (02)
Any Payload Specific Code
except VT-Structured
STS-1 (02)
Any Equipped Functionality
none
TMUX_RPLMP
PDI, 1 to 27 VTx defects (E1 to FB)
TMUX_RPLMP
No change
PDI, 28 VT1.5 defects or 1 non-VT
payload defect (FC)
Reserved (FF)
none
TMUX_RPLMP
Any Equipped Functionality
none
TMUX_RPLMP