m28529-12 Mindspeed Technologies, m28529-12 Datasheet - Page 293

• Manufacturer Part Number: m28529-12
• Description: Inverse Multiplexing For Atm Ima Family
• Manufacturer: Mindspeed Technologies

Table 4-1.
28529-DSH-001-K
BIP.29
BIP.30
BIP.31
BIP.32
BIP.33
BIP.34
BIP.35
BIP.36
BIP.37
BIP.38
BIP.39
BIP.40
BIP.41
BIP.42
BIP.43
BIP.44
BIP.45
BIP.46
BIP.47
Item
Does the implementation use t
Information field in an ICP cell, to report the receive state of the incoming
IMA link on which the FE IMA is transmitting ICP cells carrying LID = “x”
(“x” being a value between 0 and 31)?
Does the implementation use t
in the Link “x” Information field in an ICP cell, to report the Rx defect
indicators corresponding to the incoming IMA link on which the FE IMA is
transmitting ICP cells carrying LID = “x” (“x” being a value between 0 and
31)?
Does the implementation always transmit ICP cells with Octet 50 unused and
set to “0x6A” as defined in ITU-T Recommendation I.432 [A-4]?
Does the implementation reserve the End-to-End Channel field (Octet 51) as
a proprietary channel?
Does the implementation set the End-to-End Channel field (Octet 51) to “0”
when not using this field?
Does the implementation not rely on the processing of the End-to-End
Channel field for any IMA functionality?
Does the implementation only consider the information within ICP cells
exhibiting neither a HEC nor a CRC-10 error?
Does the implementation always transmit "0x03" over the OAM Label in the
Filler and ICP cells?
If the implementation does not support the IMA version proposed by the
OAM Label received from the far-end IMA unit, does the implementation
report the “Config-Aborted - Unsupported IMA Version" state over the
“Group Status and Control” field?
Does the implementation transmit IMA frames, composed of M consecutive
cells, on each link within the IMA group?
Does the implementation send ICP cells on each link once per IMA frame,
hence every M cells?
Does the implementation use the IFSN field in the ICP cell to indicate the
sequence number of the IMA frame?
Does the implementation increment the IFSN field in the ICP cell from 0 to
255 and repeat the sequence?
Does the implementation increment the IFSN field in the ICP cell with each
IMA frame on a per-link basis?
Within an IMA frame, does the implementation place identical IFSN values in
the ICP cells sent on each link?
Does the implementation align the transmission of the IMA frame on all links
within an IMA group?
Does the implementation use the ICP Cell Offset field (octet 9) to indicate the
location of the ICP cell within the IMA frame of length M cells?
Does the implementation always set the value of the ICP cell offset between
0 and M-1 where M is the IMA frame length in cells?
Does the implementation distribute the ICP cells, from link to link within the
IMA group, in an uniform fashion across the IMA frame?
Basic IMA Protocol (BIP) Definition Functions (3 of 5)
Protocol feature
he “Rx State”, located in the Link “x”
he “Rx Defect Indicators” field, located
Mindspeed Proprietary and Confidential
Mindspeed Technologies
®
Cond. for
Status
Status
Pred.
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
O
(R-23)
(R-24)
(R-25)
(R-26)
(R-27)
(R-28)
(R-29)
(R-30)
(R-31)
(R-32)
(R-33)
(R-34)
(R-35)
(R-36)
(R-36)
(R-37)
(R-38)
(R-39)
(O-1)
Ref.
Yes X No__
Yes X No__
Yes X No__
Yes X No__
Yes X No__
Yes X No__
Yes X No__
Yes X No__
Yes X No__
Yes X No__
Yes X No__
Yes X No__
Yes X No__
Yes X No__
Yes X No__
Yes X No__
Yes X No__
Yes X No__
Yes X No__
Appendices
Support
278