CSMA/CD
`
`IEEE
`Std 802.3u-1995
`
`1 TX_D1+
`_[: 2 TX_D1—
`3 RX_D2+
`6 RX_D2—
`it
`%4 Bl D3+
`:%7 B|_D4+
`
`5 B|_D3—
`
`8 B|_D4—
`PHY
`
`TX_D1+
`1
`TX_D1— 2:]_
`RX_D2+ 3
`I:
`RX_D2— 5
`B|_D3+ 4g
`B|_D4+ 7g
`
`Bl_D3— 5
`
`B|_D4— 3
`PHY
`
`a) Two PHYs with external crossover function
`
`MD|-X Label
`MD|
`1
`TX_D1+ — TX_D1+ 1
`_l;2 TX_D1— Z TX_D1— 2
`3 RX_D2+: RX_D2+ 3
`_<]:5 Rx_D2—j RX_D2— 6
`4 BI_D3+ — Bl_D3+
`4
`
`5
`
`Bl_D3— j Bl_D3— 5
`
`%7 Bl_D4+ : Bl_D4+
`
`5
`
`Bl_D4— — Bl_D4— 8
`
`7
`
`Internal Signal
`
`
`
`b) PHY with internal crossover function
`
`23.9.2 Network safety
`
`This clause sets forth a number of recommendations and guidelines related to safety concerns; the list is nei-
`ther complete nor does it address all possible safety issues. The designer is urged to consult the relevant
`local, national, and international safety regulations to ensure compliance with the appropriate requirements.
`
`LAN cable systems described in this clause are subject to at least four direct electrical safety hazards during
`their installation and use. These hazards are as follows:
`
`Direct contact between LAN components and power, lighting, or communications circuits
`a)
`Static charge buildup on LAN cables and components
`b)
`c) High-energy transients coupled onto the LAN cable system
`d)
`Voltage potential differences between safety grounds to which various LAN components are
`connected
`
`This is an Archive IEEE Standard.
`
`It has been superseded by a later version of this standard.
`
`025
`149
`
`Aerohive - Exhibit 1025
`
`0149
`
`

`
`IEEE
`Std 802.3u-1995
`
`SUPPLEMENT TO 802.3:
`
`Such electrical safety hazards must be avoided or appropriately protected against for proper network instal-
`lation and performance. In addition to provisions for proper handling of these conditions in an operational
`system, special measures must be taken to ensure that the intended safety features are not negated during
`installation of a new network or during modification or maintenance of an existing network.
`
`23.9.2.1 Installation
`
`It is a mandatory fimctional requirement that sound installation practice, as defined by applicable local codes
`and regulations, be followed in every instance in which such practice is applicable.
`
`23.9.2.2 Grounding
`
`Any safety grounding path for an externally connected PHY shall be provided through the circuit ground of
`the MH connection.
`
`WARNING—It is assumed that the equipment to which the PHY is attached is properly grounded, and not left floating
`nor serviced by a “doubly insulated, ac power distribution system.” The use of floating or insulated equipment, and the
`consequent implications for safety, are beyond the scope of this standard.
`
`23.9.2.3 Installation and maintenance guidelines
`
`It is a mandatory functional requirement that, during installation and maintenance of the cable plant, care be
`taken to ensure that noninsulated network cable conductors do not make electrical contact with unintended
`
`conductors or ground.
`
`23.9.2.4 Telephony voltages
`
`The use of building wiring brings with it the possibility of wiring errors that may connect telephony voltages
`to 100BASE-T4 equipment. Other than voice signals (which are low voltage), the primary voltages that may
`be encountered are the “battery” and ringing voltages. Although there is no universal standard, the following
`maximums generally apply.
`
`Battery voltage to a telephone line is generally 56 Vdc applied to the line through a balanced 400 9 source
`impedance.
`
`Ringing voltage is a composite signal consisting of an ac component and a dc component. The ac component is
`up to 175 V peak at 20 Hz to 60 Hz With a 100 9 source resistance. The dc component is 56 Vdc with a 300 Q
`to 600 9. source resistance. Large reactive transients can occur at the start and end of each ring interval.
`
`Although 100BASE-T4 equipment is not required to survive such wiring hazards without damage, applica-
`tion of any of the above voltages shall not result in any safety hazard.
`
`NOlI‘E—Wh1'ng errors may impose telephony voltages differentially across 100BASE-T4 transmitters or receivers.
`Because the termination resistance likely to be present across a receiver’s input is of substantially lower impedance than an
`off-hook telephone instrument, receivers will generally appear to the telephone system as off-hook telephones. Therefore,
`full-ring voltages will be applied for only short periods. Transmitters that are coupled using transformers will similarly
`appear like ofi‘-hook telephones (though perhaps a bit more slowly) due to the low resistance of the transformer coil.
`
`23.9.3 Environment
`
`23.9.3.1 Electromagnetic emission
`
`The twisted-pair link shall comply with applicable local and national codes for the limitation of electromag-
`netic interference.
`
`This is anlggrchive IEEE Standard.
`
`It has been superseded by a later version of this standard.
`
`1025
`0150
`
`Aerohive - Exhibit 1025
`
`0150
`
`

`
`CSMA/CD
`
`23.9.3.2 Temperature and humidity
`
`IEEE
`Std 802.3u-1995
`
`The twisted—pair link is expected to operate over a reasonable range of environmental conditions related to
`temperature, humidity, and physical handling (such as shock and vibration). Specific requirements and val-
`ues for these parameters are considered to be beyond the scope of this standard.
`
`It is recommended that manufacturers indicate in the literature associated with the PHY the operating envi-
`ronmental conditions to facilitate selection, installation, and maintenance.
`
`23.10 PHY labeling
`
`It is recommended that each PHY (and supporting documentation) be labeled in a manner visible to the user
`with at least these parameters:
`
`a) Data rate capability in Mb/s
`b)
`Power level in terms of maximum current drain (for external PHYs)
`c) Any applicable safety warnings
`
`See also 23.7.2.
`
`23.11 Timing summary
`
`23.11.1 Timing references
`
`All MII signals are defined (or corrected to) the DTE end of a zero length MII cable.
`
`NOTE—With a finite length M11 cable, TX_CLK appears in the PHY one cable propagation delay earlier than at the
`MII. This advances the transmit timing. Receive timing is retarded by the same amount.
`
`The phrase adjustedfor pair skew, when applied to a timing reference on a particular pair, means that the
`designated timing reference has been adjusted by adding to it the difference between the time of arrival of
`preamble on the latest of the three receive pairs and the time of arrival of preamble on that particular pair.
`
`PMA_UNITDATA request
`
`Figures 23-29, 30, 31, and 32. The implementation of this abstract message is not specified.
`Conceptually, this is the time at which the PMA has been given full knowledge and use of the
`ternary symbols to be transmitted.
`
`PMA_UNITDATA.indicate
`
`Figure 23-33. The implementation of this abstract message is not specified. Conceptually, this is
`the time at which the PCS has been given full knowledge and use of the ternary symbols received.
`WAVEFORM
`
`Figure 23-29. Point in time at which output waveform has moved 1/2 way from previous nominal
`output level to present nominal output level.
`
`TX EN
`
`Figure 23-30. First rising edge of TX_CLK following the rising edge of TX_EN.
`
`NOT_TX_EN
`
`Figures 23-31 and 32. First rising edge of TX_CLK following the falling edge of TX_EN.
`
`CRS
`
`Figure 23-33. Rising edge of CRS.
`
`CARRIER_STATUS
`
`This is an Archive IEEE Standard.
`
`It has been superseded by a later version of this standard.
`
`tlO25
`0151
`
`Aerohive - Exhibit 1025
`
`0151
`
`

`
`IEEE
`Std 802.3u-1995
`
`SUPPLEMENT TO 802.3:
`
`Figure 23-33. Rising edge of cam'er_status.
`
`NOT_CARRIER_STATUS
`
`Figure 23-34. Falling edge of carn'er_status.
`
`RX_DV
`
`COL
`
`No figure. First rising edge of RX_CLK following rising edge of RX_DV.
`
`No figure. Rising edge of COL signal at MII.
`
`NOT_COL
`
`No figure. Falling edge of COL signal at MII.
`
`PMA_ERROR
`
`No figure. Time at which rxerror_status changes to ERROR.
`
`This is anlgirrchive IEEE Standard.
`
`It has been superseded by a later version of this standard.
`
`
`
`Aerohive - Exhibit 1025
`
`0152
`
`

`
`CSMA/CD
`
`IEEE
`Std 802.3u-1995
`
`23.11.2 Definitions of controlled parameters
`
`PMA_OUT
`
`Figure 23-29. Time between PMA_UNITDATA request (tx_code_vector) and the WAVEFORM
`timing reference for each of the three transmit channels TX_Dl, BI_D3, or BI_D4.
`
`TEN_PMA
`
`Figures 23-30, 31, and 32. Time between TX_EN timing reference and MA_UNITDATA request
`(tx_code_vector).
`
`TEN_CRS
`
`Figure 23-30. Time between TX_EN timing reference and the loopback of TX_EN to CRS as
`measured at the CRS timing reference point.
`
`NOT_TEN_CRS
`
`Figures 23-31 and 32. Time between NOT_TX_EN timing reference and the loopback of TX_EN
`to CRS as measured at the NOT_CRS timing reference point. 111 the event of a collision (COL is
`raised at any point during a packet) the minimum time for NOT_TEN_CRS may optionally be as
`short as 0.
`
`RX_PMA_CARR]ER
`
`Figure 23-33. Time between the WAVEFORM timing reference, adjusted for pair skew, of first
`pulse of a normal preamble (or first pulse of a preamble preceded by a link test pulse or a partial
`link test pulse) and the CARRIER_STATUS timing reference.
`
`RX_CRS
`
`Figure 23-33. Time between the WAVEFORM timing reference, adjusted for pair skew, of first
`pulse of a normal preamble (or first pulse of a preamble preceded by a link test pulse or a partial
`link test pulse) and the CRS timing reference.
`NOTE—The input waveform used for this test is an ordinary T4 preamble, generated by a compliant T4
`transmitter. As such, the delay between the first and third pulses of the preamble (which are used by the car-
`rier sense logic) is very nearly 80 ns.
`
`RX_NOT_CRS
`
`For a data packet, the time between the WAVEFORM timing reference, adjusted for pair skew, of
`the first pulse of eopl, and the de-assertion of CRS. For a collision fragment, the time between the
`WAVEFORM timing reference, adjusted for pair skew, of the ternary symbol on pair TX_D2,
`which follows the last ternary data symbol received on pair RX_D2, and the de-assertion of CRS.
`
`Both are limited to the same value. For a data packet, detection of the six ternary symbols of eopol
`is accomplished in the PCS layer. For a collision fragment, detection of the concluding seven
`ternary zeroes is accomplished in the PMA layer, and passed to the PCS in the form of the
`carrier_status indication.
`FAIRNESS
`
`The difference between RX_NOT_CRS at the conclusion of one packet and RX_CRS on a
`subsequent packet. The packets used in this test may arrive with an IPG anywhere in the range of
`80 to 160.
`
`RX_PMA_DATA
`
`Figure 23-33. Time between the WAVEFORM timing reference, adjusted for pair skew, of first
`pulse of a normal preamble (or first pulse of a preamble preceded by a link test pulse or a partial
`link test pulse) and the particular PMA_UNITDATA.indicate that transfers to the PCS the first
`ternary symbol of the first 6T code group from receive pair BI_D3.
`
`This is an Archive IEEE Standard.
`
`It has been superseded by a later version of this stanqigrd.
`
`
`
`Aerohive - Exhibit 1025
`
`0153
`
`

`
`IEEE
`Std 802.3u-1995
`
`EOP_CARRIER_STATUS
`
`SUPPLEMENT TO 802.3:
`
`Figure 23-34. For a data packet, the time between the WAVEFORM timing reference, adjusted for
`pair skew, of first pulse of eopl and the NOT_CARRIER_STATUS timing reference.
`
`EOC_CARRIER_STATUS
`
`Figure 23-35. In the case of a colliding packet, the time between the WAVEFORM timing
`reference, adjusted for pair skew, of the ternary symbol on pair RX_D2, which follows the last
`ternary data symbol received on pair RX_D2 and the NOT_CARRIER_STATUS timing
`reference.
`
`RX_RXDV
`
`No figure. Time between WAVEFORM timing reference, adjusted for pair skew, of first pulse of
`a normal preamble (or first pulse of a preamble preceded by a link test pulse or a partial link test
`pulse) and the RX_DV timing reference.
`
`RX_PMA_ERROR
`
`No figure. In the event of a preamble in error, the time between the WAVEFORM timing reference
`adjusted for pair skew, of first pulse of that preamble (or first pulse of the preamble preceded by a
`link test pulse or a partial link test pulse), and the PMA_ERROR timing reference.
`
`RX_COL
`
`No figure. In the event of a collision, the time between the WAVEFORM timing reference
`adjusted for pair skew, of first pulse of a normal preamble (or first pulse of a preamble preceded
`by a link test pulse or a partial link test pulse), and the COL timing reference.
`
`RX_NOT_COL
`
`No figure. In the event of a collision in which the receive signal stops before the locally transmitted
`signal, the time between the WAVEFORM timing reference adjusted for pair skew, of the ternary
`symbol on pair RX_D2, which follows the last ternary data symbol received on pair RX_D2 and
`the NOT_COL timing reference point.
`
`TX_NOT_COL
`
`No figure. In the event of a collision in which the locally transmitted signal stops before the
`received signal, the time between the NOT_TX_EN timing reference and the loopback of TX_EN
`to COL as measured at the NOT_COL timing reference point.
`
`TX_SKEW
`
`Greatest absolute difference between a) the waveform timing reference of the first pulse of a
`preamble as measured on output pair TX_D1; b) the waveform timing reference of the first pulse
`of a preamble as measured on output pair BI_D3; and c) the waveform timing reference of the first
`pulse of a preamble as measured on output pair BI_D4. Link test pulses, if present during the
`measurement, must be separated from the preamble by at least 100 ternary symbols.
`
`CRS_PMA_DATA
`
`Time between the timing reference for CARRIER STATUS and the transferral, via
`PMA_UNITDATA.indicate, of the first ternary symbol of the 6T code group marked DATA1 in
`figure 23-6.
`
`COL_to_BI_D3/D4_OFF
`
`No figure. In the case of a colliding packet, the time between the WAVE FORM timing reference,
`adjusted for pair skew, of the first pulse of preamble (or the first pulse of the preamble preceded
`by a link test pulse or a partial link test pulse) on RX_D2, and the first ternary zero transmitted on
`BI_D3 and on BI_D4.
`
`NOTE—Subclause 23.4.1.2 mandates that transmission on pairs BI_D3 and BI_D4 be halted in the event of a collision.
`
`This is anlggchive IEEE Standard.
`
`It has been superseded by a later version of this standard.
`
`0154
`
`1025
`
`Aerohive - Exhibit 1025
`
`0154
`
`

`
`CSMA/CD
`
`23.11.3 Table of required timing values
`
`IEEE
`Std 802.3u-1995
`
`While in the LINK_PASS state, each PHY timing parameter shall fall within the Low and High limits listed
`in table 23-7. All units are in bit times. A bit time equals 10 ns.
`
`Table 23-7—Required timing values
`
`Controlled parameter
`
`Low limit (bits)
`
`High limit (bits)
`
`PMA_OUT
`
`TEN_PMA + PMA_OUT
`
`TEN_CRS
`
`NOT_TEN_CRS
`
`RX_PMA_CARRIER
`
`RX_CRS
`
`RX_NOT_CRS
`
`FAIRNESS
`
`RX_PMA_DATA
`
`EOP_CARRIER_STATUS
`
`EOC_CARRIER_STATUS
`
`RX_RXDV
`
`67
`
`5 1
`
`3
`
`81
`
`28
`
`90.5
`
`74.5
`
`50.5
`
`114.5
`
`RX_PMA_ERROR
`
`RX_PMA_DATA
`
`RX_PMA_DATA + 20
`
`Allowed limits equal the actual
`RX_PMA_DATA time for the
`device under test plus from 0 to
`20 BT
`
`RX_COL
`
`RX_NOT_COL
`
`TX_NOT_COL
`
`TX_SKEW
`
`CRS_PMA_DATA
`
`COL_to_BI_D3/D4_OFF
`
`.
`
`SAME AS RX_CRS
`
`SAME AS
`RX_NOT_CRS
`
`This is an Archive IEEE Standard.
`
`It has been superseded by a later version of this stanqigrd.
`
`Aerohive - Exhibit 1025
`
`0 l 5 5
`
`Aerohive - Exhibit 1025
`
`0155
`
`

`
`IEEE
`Std 802.3u-1995
`
`SUPPLEMENT TO 802.3:
`
`PMA_UN|TDATA.request (tx_code_vector)
`\
`
`Succession of
`ternarysymbols
`available to PMA
`
`X
`
`t1
`
`X
`
`‘Z
`
`X
`
`t3
`
`X
`
`*4
`
`nominal height
`
`Typical 2x oversampled
`raw transmitter output
`
`t1
`
`t1
`
`II 4
`
`Filtered output signal
`at MDI
`
`1/2 ”°”‘i"a' height
`
`« PMA_OUT
`
`\ WAVEFORM
`timing reference point
`
`TXCLK
`at Mll
`(zero length cable)
`
`TX_EN
`
`TxD[o;3]
`octet formed
`from two nibbles
`(13,)
`
`nib1
`
`Succession
`of ternary symbols
`on pair TX_D1
`
`Timing reference
`‘/ for TX_EN
`
`nib2
`\A\‘
`X
`_
`X °°tet1
`Tlmelspent L/_\‘ _
`First symbol
`coding data
`
`of preamble
`and preparing for
`PMA_UN|TDATA.request
`
`<—TEN_PMA
`
`
`
`PMA_UN|TDATA.request (tx_code_vector)
`Loopback of TX_EN
`*
`a (earlytis ) enega Ive
`.
`(late Is
`—’
`positive) ‘’
`
`TEN_CRS
`
`This is anlggchive IEEE Standard.
`
`It has been superseded by a later version of this standard.
`
`
`
`Aerohive - Exhibit 1025
`
`0156
`
`

`
`CSMA/CD
`
`IEEE
`Std 802.3u-1995
`
`Timing reference
`‘/ for NOT TX_EN
`
`TXCLK
`llTILTIUIHJLHJUIIUIHJLHIUIIUI
`mMn
`(zero length cable)
`
`TX_EN
`
`TXD[0:3]
`last two
`nibbles
`octets
`(tsr)
`
`_
`Succession
`
`ofternary
`symbols
`
`‘
`
`|
`
`X:X:X
`84%
`X last Xeop1Xeop2)(eop3Xeop4)(eop5X zerox zero
`
`$5“ 320 ns ..
`
`last 6T
`code group
`
`eop3
`
`x |x |x |x |x|x + |+|- |— |o|o[o|o|o |o|o|o lo|o|o |o[
`eop1
`eop4
`
`l+l+I+l+l+I+ -1- l—l—I-|-I0I0I0l0I0l0l0l0l
`eop2
`eop5
`
`‘
`
`‘
`
`, ‘
`
`Loopback of TX_EN
`to CRS
`
`+I+l+l+l?l- |- l0I0I0l0l0I0l0l0l0l0l
`v\ The end of packet as sent to the PMA
`
`is defined here at the particular
`PMA_UN|TDATA.request (tx_code_vector)
`where b(_code_vector includes
`the 1st ternary symbol of eop4.
`
`_,
`TEN_PMA + 240 ns
`|
`
`|
`
`% NOT_TEN_CRS |% W
`(min)
`(max)
`
`This is an Archive IEEE Standard.
`
`It has been superseded by a later version of this stanqigrd.
`
`t1025
`0157
`
`Aerohive - Exhibit 1025
`
`0157
`
`

`
`IEEE
`Std 802.3u-1995
`
`SUPPLEMENT TO 802.3:
`
`Timing reference
`fo NOT TX EN
`"
`_
`
`A/
`
`L
`
`TXCLK J
`at MII
`(zero length cable)
`
`TX_EN
`
`TXD[0:3]
`last two X:X:X
`n bbles
`\§
`X last
`
`octets
`
`(tsr)
`
`%
`
`)(eop1 Xeop2 X eop3Xeop4)(eop5Xzero Xzero
`
`4-
`TEN_PMA
`
`Las..ema,, /,1x oloiouououoloiouoioionol
`symbolto_
`betransmltted
`o o|o|o|o|o]o|o|o|o|o|o[
`Duringa £0 o|o|o|o|olo|o|o|o|o|o]
`collision, these
`ternary symbols
`‘\
`are all zeros.
`PMA_UNlTDATA.request (tx_code_vector = all zeros)
`
`TX_D1
`B|_D3
`|3|_D4
`
`l
`Loopback of TX_EN
`to CRS
`
`
`—>
`
`NOT_TEN_CRS
`
`I%
`(max)
`
`
`
`This is anpegchive IEEE Standard.
`
`It has been superseded by a later version of this standard.
`
`158
`
`025
`
`Aerohive - Exhibit 1025
`
`0158
`
`

`
`CSMA/CD
`
`IEEE
`Std 802.3u-1995
`
`Succession of ternary symbols as received
`(measured at receiving MDI, with short cable, with no skew)
`sosa
`sosa
`sosb
`
`{J
`
`Output wave
`form timing
`reference point ?’
`fiergfsfgged at
`.
`.
`the transmitting
`device. use
`timing reference
`from pain-X_D1_
`K‘
`
` sosa
`
`sosa
`
`sosb
`
`sosa
`
`sosb
`
`first 6T code group
`
`KThe threshold crossing of the
`third pulse in the carrier
`_
`detect sequence. (+ — +)
`occurs 80 ns after
`
`_
`_
`the output WAVEFORM tlmlng
`reference point.
`
`X X X X X X
`
`F- H
`"5 be|"‘a">t’
`53"" ° 59"
`across PMA
`as DATA
`
`
`
`
`carrier_status
`
`RX_PMA_CARR|ER
`‘_
`
`CRS
`
`_>
`
`RX CRS
`_
`
`RX_CRS may be delayed in the PCS to
`meet the FAIRNESS criterion.
`‘_
`
`4e RX_PMA_DATAT»
`
`
`
`/'
`PMA_UN|TDATA.indicate (rx_code_vector= DATA)
`
`This is an Archive IEEE Standard.
`
`It has been superseded by a later version of this stanmrd.
`
`
`
`159
`
`025
`
`Aerohive - Exhibit 1025
`
`0159
`
`

`
`IEEE
`Std 8D2.3u—1995
`
`SUPPLEMENT TO 802.3:
`
`Succession
`of ternary symbols
`as received
`
`GT code group‘ resulting
`from last octet of CRC
`
`last
`
`complete
`First
`pair to
`complete
`
`complete
`
`End4)l—packet
`reference is
`defined here
`
`carrier_status
`
`Earliest opportunity
`for carrier_statJ.Is to drop
`i5 after 9094-
`
`EOF’_CAR RI ER_STATUS my
`
`NOT_CARRlEFl_STATUS
`
`/1
`
`_
`Latest opportunity
`_
`‘to/I end of carrier
`
`‘T RXiNOTiCRS T,
`
`{Wait for eop4 to cross PMA
`service interface before de—asserting.)
`
`hlOT_CRS
`(De—assserts when eop1 is
`recognized bythe PCS.)
`
`"RX_DV de—asserls after sending the last nibble of this decoded octet across the MIL
`CR5 may de—assert prior to that time.
`
`Figure 23-34—PMA RECEIVE timing end of normal packet
`
`This is an1&g'chive IEEE Standard.
`
`It has been superseded by a later version of this standard.
`
`Aerohive - Exhibit 1
`
`Aerohive - Exhibit 1025
`
`0160
`
`

`
`CSMA/CD
`
`IEEE
`Std 802.3u-1995
`
`Succession
`of ternary symbols
`as recewed
`
`Last non-zero ternary data
`symb°' transmmed
`/
`I
`1
`
`
`carrier status algorithm
`/ looks for7zerosinarow
`2 3 4 5 6 7
`
`Pairs B|_D4 nd B|_D3 are already shut
`off when in collision
`pairB|_D3 ooooooooooooooooooo
`
`CARRIER STATUS «V EOC_CARRlER_STATUS er
`NOT_CARRlER_STATUS /7‘
`
`CR5
`
`4e RX_NOT_CRS A;
`
`NOT_CRS /V‘
`
`NOTE—CRS and RX_DV both de-assert at this point.
`
`This is an Archive IEEE Standard.
`
`It has been superseded by a later version of this standgrd.
`
`
`
`Aerohive - Exhibit 1025
`
`0161
`
`

`
`CSMA/CD
`
`IEEE
`Std 802.3, 1998 Edition
`
`23.12 Protocol Implementation Confonnance Statement (PICS) proforma for clause 23,
`Physical Coding Sublayer (PCS), Physical Medium Attachment (PMA) sublayer and
`baseband medium, type 100BASE-T423
`
`23.12.1 Introduction
`
`The supplier of a protocol implementation that is claimed to conform to clause 23, Physical Coding Sublayer
`(PCS), Physical Medium Attachment (PMA) sublayer and baseband medium, type 100BASE—T4, shall com-
`plete the following Protocol Implementation Conformance Statement (PICS) proforma.
`
`A detailed description of the symbols used in the PICS proforma, along with instructions for completing the
`PICS proforma, can be found in clause 21.
`
`23.12.2 Identification
`
`23.12.2.1 Implementation identification
`
`Supplier
`
`Contact point for enquiries about the PICS
`
`Implementation Name(s) and Version(s)
`
`Other information necessary for full identification—e.g.,
`name(s) and version(s) for machines and/or operating
`systems; System Names(s)
`
`NOTES
`
`(e.g., Type, Series, Model).
`
`l—Only the first three items are required for all implementations; other information may be completed as appropri-
`ate in meeting the requirements for the identification.
`2—The terms Name and Version should be interpreted appropriately to correspond with a supplier’s terminology
`
`23.12.2.2 Protocol summary
`
`Identification of protocol standard
`
`IEEE Std 802.3, 1998 Edition, clause 23, Physical Coding
`Sublayer (PCS), Physical Medium Attachment (PMA)
`sublayer and baseband medium, type 100BASE-T4
`
`Date of Statement
`
`Identification ofamendments and corrigenda to this PICS
`proforma that have been completed as part of this PICS
`
`Yes [ ]
`No [ ]
`Have any Exception items been required?
`(See clause 21; the answer Yes means that the implementation does not conform to IEEE Std 802.3, 1998 Edition.)
`
`28Capyright releasefor PICSpmformas Users of this standard may freely reproduce the PICS proforma in this annex so that it can be
`used for its intended purpose and may further publish the completed PICS.
`
`This is arbeigfigig/@1bEfiEE§tanggrg,e,lt,‘has been superseded by a later version of this standard.
`
`Aerohive - Exhibit 1025
`
`O1 62
`
`Aerohive - Exhibit 1025
`
`0162
`
`

`
`IEEE
`Std 802.3, 1998 Edition
`
`23.12.3 Major capabilitiesloptions
`
`LOCAL AND METROPOLITAN AREA NETWORKS:
`
`Subclause
`
`Value/Comment
`
`Exposed MII interface
`
`PCS fimctions
`
`Exposed PMA service inter-
`face
`
`Internal wiring crossover
`
`Support for optional Auto-
`Negotiation (clause 28)
`
`Installation / cable
`
`a PHY manufacturer
`
`Devices supporting this option
`must also support the PCS
`option
`
`Required for integration with
`DTE or MII
`
`Required for integration into
`symbol level repeater core
`
`Usually implemented in
`repeater, usually not in DTE
`
`Required ifAuto-Negotiation
`is implemented
`
`Items marked with INS include
`installation practices and cable
`specifications not applicable to
`
`23.12.4 PICS proforma tables for the Physical Coding sublayer (PCS), Physical Medium
`Attachment (PMA) sublayer and baseband medium, type 100BASE-T4
`
`23.12.4.1 Compatibility considerations
`
`
`
`23.12.4.2 PCS Transmit functions
`
`Subclause
`
`Value/Comment
`
`code group first
`
`PCS Transmit function
`
`Data encoding
`
`Order of ternary symbol trans-
`mission
`
`Complies with state diagram
`figure 23-8
`
`8B6T with DC balance encod-
`ing rules
`
`Leftmost symbol of each 6T
`
`This is anpfirchive IEEE Standard.
`
`It has been superseded byogpigggrg/g§§iggEg(..l;i;i§$s;agagard.
`
`Aerohive - Exhibit 1025
`
`0163
`
`Aerohive - Exhibit 1025
`
`0163
`
`

`
`CSMA/CD
`
`23.12.4.3 PCS Receive functions
`
`IEEE
`Std 802.3, 1998 Edition
`
`Subclause
`
`Value/Comment
`
`PCS Receive function
`
`Value of RXD<3:0> while
`RXDV is dc-asserted
`
`Data decoding
`
`Value of dc_ba1ance_error,
`eop_error and codeword_error
`at times other than those speci-
`fied in the error detecting rules.
`
`Codeword_error indication
`sets RX_ER when
`
`Dc_ba1ance_error sets RX_ER
`when
`
`Eop_error sets RX_ER when
`
`Action taken if carrier_status is
`truncated dur to early de-asser-
`tion of carrier_status
`
`23.12.4.4 Other PCS functions
`
`PCS Reset function executed
`when
`
`PCS Error Sense function
`
`Signaling of RX_ER to MII
`
`Timing of rxerror_status
`
`PCS Carrier Sense function
`
`MII signal COL is asserted
`when
`
`At other times COL remains
`
`Loopback implemented in
`accordance with 22.4.1.2
`
`Complies with state diagram
`figure 23-9
`
`All zeroes
`
`8B6T with error detecting rules
`
`OFF
`
`During transfer of both
`affected data nibbles across the
`M11
`
`During transfer of both
`affected nibbles across the MII
`
`During transfer of last decoded
`data nibble across the M11
`
`Assert RX_ER, and then de-
`assert RX_DV
`
`Subclause
`
`Value/Comment
`
`Power-on, or the receipt of a
`reset request from the manage-
`ment entity
`
`Complies with state diagram
`figure 23-10
`
`Before last nibble of clause 4
`MAC frame has passed across
`MII
`
`Causes RX_ER to appear on
`the MII no later than last nib-
`ble of first data octet
`
`Controls MII signal CRS
`according to rules in 23.2.1.5
`
`Upon detection of a PCS colli-
`sion
`
`De-asserted
`
`Redundantly specified in
`22.2.4. 1.2
`
`This is arbe,5fi5|ii/@1bE¢fiEE§tanggrg,e,li.,‘has been superseded by a later version of this standard.
`
`Aerohive - Exhibit 1025
`
`0164
`
`Aerohive - Exhibit 1025
`
`0164
`
`

`
`IEEE
`Std 802.3, 1998 Edition
`
`LOCAL AND METROPOLITAN AREA NETWORKS:
`
`Subclause
`
`Value/Comment
`
`directions
`
`No spurious signals emitted on
`the MDI during or afier power
`down
`
`PMA frame structure
`
`PMA_UNITDATA messages
`
`Conformance to figure 23-6
`
`Must have a clock for both
`
`23.12.4.5 PCS state diagram variables
`
`Feature
`
`Timing of eop adjusted such
`that the last nibble sent across
`the M11 with RX_DV asserted
`is
`
`Transmission of octets on the
`three transmit pairs
`
`Value of tsr during first 16
`TX_CLK cycles after TX_EN
`is asserted
`
`Value of tsr during first 10
`TX_CLK cycles afler TX_EN
`is de-asserted
`
`TX_ER causes transmission of
`
`TX_ER received during the
`first 16 TX_CLK cycles causes
`
`Action taken in event TX_EN
`falls on an odd nibble
`boundary
`
`Transmission when TX_EN is
`not asserted
`
`TX_CLK generated synchro-
`nous to
`
`Subclause
`
`23.2.4.1 .5
`
`23.2.4.1 .8
`
`23.2.4.1.1l
`
`23.2.4.l.ll
`
`23.2.4.l.l1
`
`23.2.4.l.ll
`
`23.2.4.1.l1
`
`23.2.4.l.ll
`
`23.2.4.l.l2
`
`Value/Comment
`
`Last nibble of last decoded
`data octet in a packet
`
`Transmission order is: TX_Dl,
`then BI_D3, and then BI_D4
`
`sosa, sosa, sosa, sosa,
`sosa, sosa, sosa, sosa,
`sosa, sosa, sosb, sosb,
`sosb, sosb, sosb, sosb
`
`eopl, eopl, eop2, eop2,
`eop3, eop3, eop4, eop4,
`eop5, eop5
`
`bad_code
`
`Transmission of bad_code
`during 17th and 18th clock
`cycles
`
`Extension of TX_EN by one
`TX_CLK cycle, and transmis-
`sion of bad_code
`
`zero_code
`
`twl_timer
`
`This is anlegchive IEEE Standard.
`
`It has been superseded byogpigggrg/g§§iggEg(..ti;is$s;agag@rd.
`
`Aerohive - Exhibit 1025
`
`0165
`
`Aerohive - Exhibit 1025
`
`0165
`
`

`
`CSMA/CD
`
`23.12.4.6 PMA service interface
`
`IEEE
`Std 802.3, 1998 Edition
`
`Subclause
`
`Value/Comment
`
`Continuous generation of
`PMA_TYPE
`
`Generation of
`PMA_UNITDATA.indicate
`(DATA) messages
`
`Generation of
`PMA_CARRIER.indicate
`message
`
`Generation of
`PMA_LINK.indicate message
`
`Link_c0ntrol defaults on
`power-on or reset to
`
`Action taken in
`SCAN_FOR_CARRIER mode
`
`Reporting of link_status while
`in SCAN_FOR_CARRRIER
`mode
`
`Reporting of link_status while
`in DISABLE mode
`
`Action taken in ENABLE
`mode
`
`Generation of
`PMA_RXERROR
`
`synchronous with data
`received at the MDI
`
`ON/OFF
`
`FAIL/READY/OK
`
`ENABLE
`
`Enables link integrity state dia-
`gram, but blocks passage into
`LINK_PASS
`
`FAIL / READY
`
`FAIL
`
`enables data processing func-
`tions
`
`ERROR / N0_ERROR
`
`23.12.4.7 PMA Transmit functions
`
`Subclause
`
`Value/Comment
`
`TX_D1
`
`Transmission while
`(tx_code_vector=DATA)
`* (pma_carrier=OFF)
`
`Transmission from time
`(tx_code_vector=DATA)
`* (pma_carrier=ON),
`until (tx_code_Vector=IDLE
`Transmission while
`
`tx_code_vector=IDLE
`
`Duration of silence between
`link test pulses
`
`Link test pulse composed of
`
`tx_code_vector[TX_D 1]
`tx_code_vector[BI_D3]
`tx_code_vector[BI_D4]
`
`tx_code_vector[TX_D 1]
`CS0
`CS0
`
`Idle signal TP_DIL_l00
`
`1.2 ms :: 0.6 ms
`
`CS-l, CS1 transmitted on
`
`This is arbeigfigii/@1bEfiEE§tanggrg,e,li.,‘has been superseded by a later version of this standard.
`
`Aerohive - Exhibit 1025
`
`0166
`
`Aerohive - Exhibit 1025
`
`0166
`
`

`
`IEEE
`Std 802.3, 1998 Edition
`
`LOCAL AND METROPOLITAN AREA NETWORKS:
`
`
`
`This is an14>g'chive IEEE Standard.
`
`It has been superseded byogpggggrg/g§§iggEg(..tI{g§$$;agag@rd.
`
`t1025
`
`0167
`
`Aerohive - Exhibit 1025
`
`0167
`
`

`
`CSMA/CD
`
`23.12.4.8 PMA Receive functions
`
`IEEE
`Std 802.3, 1998 Edition
`
`Subclause
`
`Value/Comment
`
`Reception and translation of
`data with ternary symbol error
`rate less than
`
`Assertion of pma_carrie1=ON
`upon reception of test signal
`
`condition required to turn off
`pma_carrier
`
`Value of carrier_status while
`rcv=ENABLE
`
`Value of carrier_status while
`rcv=DISABLE
`
`23.12.4.9 Link Integrity functions
`
`One part in 108
`
`Test signal is a succession of
`three data values, produced
`synchronously with a 25 MHz
`clock, both preceded and fol-
`lowed by 100 symbols of
`silence. The three Values are:
`467 mV, -225 mV, and then
`467 mV again
`
`Either of
`a) Seven consecutive zeroes
`b) Reception of eopl per
`23.4.1.4
`
`pma_carrier
`
`OFF
`
`
`
`23.4.1.5
`
`M
`
`State diagram figure 23-12
`
`LIFl
`
`Link Integrity function com-
`plies with
`
`23.12.4.10 PMA Align functions
`
`Feature
`
`Subclause
`
`Value/Comment
`
`Generation of
`PMA_UNITDATA.indicate
`(PREAMBLE) messages
`
`Ternary symbols transferred by
`first PMA_UNITDATA.indi-
`cate (DATA) message
`
`of third data code group
`
`rx_code_vector[BI_D3] zfirst
`ternary symbol of first data
`code group
`rx_code_vector[RX_D2] ztwo
`ternary symbols prior to start
`of second data code group
`rx_code_vector[BI_D4] zfour
`ternary symbols prior to start
`
`This is arbeigfigii/@1bEfiEE§tanggrg,e,li.,.has been superseded by a later version of this standard.
`
`Aerohive - Exhibit 1025
`
`0168
`
`Aerohive - Exhibit 1025
`
`0168
`
`

`
`IEEE
`Std 802.3, 1998 Edition
`
`LOCAL AND METROPOLITAN AREA NETWORKS:
`
`Subclause
`
`Value/Comment
`
`PMA UNITDATA.indicate
`
`(DATA) messages continue
`until carrier_status=OFF
`
`While carrier_status=OFF,
`PMA emits message
`
`Failure to recognize SSD gen-
`erates rxerror_status=ERROR
`
`Action taken when
`carrier_status=OFF
`
`Action taken if first packet is
`used for alignment
`
`Tolerance of line skew
`
`Detection of misplaced sosb
`6T code group caused by 3 or
`fewer ternary symbols in error
`Action taken if rcv=disable
`
`23.12.4.11 Other PMA functions
`
`PMA_UNITDATA.indicate
`(IDLE)
`
`Clear rxerror_status
`
`PMA emits
`PMA_UNITDATA.indicate
`(PREAMBLE)
`60 ns
`
`PMA emits
`PMA_UNITDATA.indicate
`(IDLE)
`
`
`
`PMA Reset function
`
`M
`
`Suitable clock recovery
`
`23.12.4.12 Isolation requirements
`
`Subclause
`
`Value/Comment
`
`Values of all components used
`in test circuits
`
`Electrical isolation meets
`
`At least 2 M Q
`
`Accurate to within ::1% unless
`required otherwise
`1500 V at 50-60 Hz for 60 s
`per IEC 950: 1991
`or
`
`2250 Vdc for 60 s per IEC 950:
`1991
`or
`
`Ten 2400 V pulses per IEC 60
`
`None per IEC 950: 1991
`
`Insulation breakdown during
`isolation test
`
`Resistance after isolation test
`
`This is anlgqchive IEEE Standard.
`
`It has been superseded by(gpifi§e.r@/g§§iggEg(..ti§i§s$;§g.1gard.
`
`Aerohive - Exhibit 1025
`
`0169
`
`Aerohive - Exhibit 1025
`
`0169
`
`

`
`CSMAICD
`
`23.12.4.13 PMA electrical requirements
`
`Subclause
`
`23.5.1.2
`
`23.5.1.2
`
`23.5.1.2.1
`
`23.5.l.2.2
`
`23.5.l.2.2
`
`23.5.l.2.2
`
`23.5.l.2.2
`
`23.5.l.2.2
`
`23.5.l.2.2
`
`23.5.l.2.2
`
`23.5.l.2.2
`
`23.5.l.2.3
`
`23.5.l.2.3
`
`23.5.l.2.3
`
`23.5.l.2.3
`
`Conformance to all transmitter
`specifications in 23.5.1.2
`
`Transmitter load unless other-
`wise specified
`
`Peak differential output
`voltage
`
`Differential transmit template
`at MDI
`
`Differential MDI output tem-
`plate Voltage scaling
`
`Interpolation between points
`on transmit template
`
`Differential link pulse template
`at MDI
`
`Differential link pulse template
`scaling
`
`Interpolation between point on
`link pulse template
`
`State when transmitting seven
`or more consecutive CSO dur-
`ing TP_IDL-100 signal
`
`Limit on magnitude of har-
`monies measured at MDI
`
`Differential output ISI
`
`Measurement of ISI and peak-
`to-peak signal voltage
`
`Transfer function of
`IOOBASE-T4 transmit test
`filter
`
`Reflection loss of 100BASE-
`T4 transmit test filter and
`100 W load across the fre-
`quency range 2—l2.5 MHz
`
`Differential output impedance
`
`23.5.l.2.4
`
`Maintenance of return loss
`
`23.5.l.2.4
`
`Droop as defined in figure 23-
`18 during transmission of eopl
`and eop4
`
`Output timing jitter
`
`23.5.l.2.4
`
`23.5.l.2.5
`
`IEEE
`Std 802.3, 1998 Edition
`
`Value/Comment
`
`100 9
`
`3.15-3.85 V
`
`Table 23-2
`
`3.15—3.85V
`
`Linear
`
`Table 23-2
`
`Same value as used for differ-
`ential transmit template scaling
`Linear
`
`-50 mV to 50 mV
`
`27 dB below fundamental
`
`Less than 9%
`
`Halfway between nominal zero
`crossing of the observed eye
`pattern
`
`Third-order Butterworth filter
`with -3 dB point at 25.0 MHz
`
`Exceeds 17 dB
`
`Provide return loss into 100 Q
`of 17 dB from 2.0 to 12.5 MHz
`
`At all times PHY is fully pow-
`ered
`
`Less than 6%
`
`No more than 4 ns peak-to-
`peak
`
`This is arbepgggm