M28529G-12 Mindspeed Technologies, M28529G-12 Datasheet - Page 292

• Manufacturer Part Number: M28529G-12
• Description: ATM IMA 8.192Mbps 1.8V/3.3V 484-Pin BGA
• Manufacturer: Mindspeed Technologies

Specifications of M28529G-12

• Package: 484BGA
• Utopia Type: Level 2
• Typical Operating Supply Voltage: 1.8|3.3 V
• Minimum Operating Supply Voltage: 1.71|3.135 V
• Maximum Operating Supply Voltage: 1.89|3.465 V
• Maximum Output Rate: 8.192 Mbps

Table 4-1.
28529-DSH-001-K
BIP.10
BIP.11
BIP.12
BIP.13
BIP.14
BIP.15
BIP.16
BIP.17
BIP.18
BIP.19
BIP.20
BIP.22
BIP.23
BIP.24
BIP.25
BIP.26
BIP.27
BIP.28
BIP.21
Item
BIP.9
Does the implementation support the ICP cell format defined in Table 2 on
page 31 to convey IMA configuration, synchronization, status, and defect
information to the far-end?
Does the implementation perform cell rate decoupling by inserting IMA Filler
cells in place of ATM cells when there is no cell available at the ATM layer?
Does the implementation accept, on receive, ATM cells from the N links
according to ascending order based on the LID received in the ICP cells on
the incoming link?
Does the implementation, on receive, compensate for link differential delays
and rebuild the original ATM cell stream?
Does the implementation discard received Filler cells and cells with bad
HEC?
Does the implementation process and discard incoming ICP cells?
Does the implementation aggregate, on receive, the ATM cell stream to the
ATM layer?
Does the implementation preserve the order of incoming cells?
Does the implementation use the ICP cell to maintain IMA protocol
synchronization?
Does the implementation use the ICP cell to maintain link delay
synchronization?
Does the implementation transmit first the most significant bit of each octet
of the IMA OAM cell?
Does the implementation support the same cell header for both the Filler and
ICP cell formats as defined in Table 1 on page 28 and Table 2 on page 31?
Does the implementation use bit 7 of octet 7 (CID field) of the Filler and ICP
cells to identify the IMA OAM cell as an ICP or Filler cell?
Does the implementation use octets 52-53 as specified in ITU-T
Recommendation I.610 [A-5] for octets 52-53 of the OAM cells of the F1/F3
flows?
Does the implementation support the Filler cell format defined in Table 1 on
page 28?
Does the implementation support the ICP cell format defined in Table 2 on
page 31?
Does the implementation transmit the content of the link specific fields
appearing in class A over the link for which these fields apply?
Does the implementation transmit the same content of fields appearing in
classes B and C of the ICP cell over all links within an IMA group?
Does the implementation use the LID bits (bits 4-0 of octet 7) in the ICP cell
to identify the Link ID (range being 0 to 31)?
Does the implementation use the “Tx State” field, located in the Link “x”
Information field in an ICP cell, to report the transmit state of the IMA link on
which the NE IMA is transmitting ICP cells carrying LID = “x” (“x” being a
value between 0 and 31)?
Basic IMA Protocol (BIP) Definition Functions (2 of 5)
Protocol feature
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
M
M
(R-9)
(R-10)
(R-11)
(R-11)
(R-11)
(R-11)
(R-11)
(R-11)
(R-12)
(R-12)
(R-13)
(R-14)
(R-15)
(R-16)
(R-17)
(R-18)
(R-19)
(R-20)
(R-21)
(R-22)
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__
Yes X No__
Appendices
Support
277