TRE__._.._E5HEB
`
`Page 1
`
`Dell Inc.
`
`Exhibit 10 19
`
`Page 1
`
` Dell Inc.
` Exhibit 1019
`
`
`
`Page 1
`
`Dell Inc.
`
`Exhibit 10 19
`
`Page 1
`
` Dell Inc.
` Exhibit 1019
`
`
`
`- --
`
`1
`
`...
`.......
`
`ADDISON
`WESLEY
`
`Page 2
`
`
`
`Gigabit Ethernet
`
`Technology and Applications
`for High-Speed LANs
`
`Rich Seifert
`
`... TT
`
`Addison-Wesley
`An imprint of Addison Wesley Longman, Inc.
`Reading, Massachusetts • Harlow, England • Menlo Park, California
`Berkeley, California • Don Mills, Ontario • Sydney • Bonn
`Amsterdam • Tokyo • Mexico City
`
`Page 3
`
`
`
`Many of the designations used by manufacturers and sellers to
`distinguish their productS are claimed as trademarks. Where those
`designations appear in this book and Addison-Wesley was aware of a
`trademark claim, the designations have been printed in initial caps or
`all caps.
`
`The author and publisher have taken care in the preparation of this
`book, but make no expressed or implied warranty of any kind and
`assume no responsibility for errors or omissions. No liability is
`assumed for incidental or consequential damages in connection with
`or arising out of the use of the information or programs contained
`herein.
`
`The publisher offers discounts on this book when ordered in quantity
`for special sales. For more information, please contact:
`
`Corporate, Government, and Special Sales
`Addison Wesley Longman, Inc.
`One Jacob Way
`Reading, Massachusetts 01867
`
`Library of Congress Cataloging-in-Publication Data
`
`Seifert, Rich, 1952-
`Gigabit Ethernet: technology and applications for high-speed
`LANs I Rich Seifert.
`p. em.
`Includes bibliographical references and index.
`ISBN 0-201-18553-9
`1. Ethernet (Local area network system)
`TK5105.8.E83S45
`1998
`62l.39'81-dc21
`
`I. Title.
`
`98- 9357
`CIP
`
`Copyright@ 1998 by Addison Wesley Longman, Inc.
`
`All rights reserved. No part of this publication may be reproduced,
`stored in a retrieval system, or transmitted, in any form, or by any
`means, electronic, mechanical, photocopying, recording, or otherwise,
`without the prior consent of the publisher. Printed in the United States
`of America. Published simultaneously in Canada.
`
`ISBN 0-201-18553-9
`Text printed on recycled and acid-free paper.
`1 2 3 4 56 7 8 9 10-MA-0201009998
`First printing, April 1998
`
`Page 4
`
`
`
`8.2
`
`Auto-Negotiation on UTP Systems
`
`137
`
`--+f I-- 100 na Nominal
`
`I-- 82.5111 Nominal
`
`Figure 8-3 Auto-Negotiation signaling.
`
`The entire message is repeated, nominally at 16-ms intervals, until the nego(cid:173)
`tiation is complete.
`
`8.2.4.3 Automatic Configuration without Auto-Negotiation
`A device can easily detect whether the signals it is receiving were generated
`using 10BASE-T, 100BASE-TX, or 100BASE-T4. In the case of 10BASE-T,
`every device emits characteristic "link pulses" every 16 ms when the link is
`idle; this constitutes an unmistakable signature. 11 In the case of 100BASE-TX
`and 100BASE-T4, the signal levels, timing, and encoding used are sufficiently
`different that determination of the link's nature can be made without the use
`of Auto-Negotiation. This is often called "parallel detection."
`Thus it is possible to automatically configure to any of these three signal(cid:173)
`ing methods without implementing the negotiation protocol. Doing this is
`fairly common, and it slightly lowers the cost of a product.
`However, a great deal of flexibility is lost by not using Auto-Negotiation:
`
`• It is not possible to implement automatic dual-speed capability (for ex(cid:173)
`ample, 10Mb/sand 100 Mb/s).
`• It is not possible to determine duplex mode.
`• It is not possible to determine flow control capability.
`
`The defa ult assumption if Auto-Negotiation is not employed is that the
`link is operating in half-duplex mode, without explicit flow control. Thus
`devices not implementing Auto-Negotiation are generally those with only a
`single mode of operation, for example, a 100BASE-TX (only) repeater hub or
`a 10BASE-T (half-duplex-only) controller, where there is nothing to be
`gained by implementing Auto-Negotiation.
`
`11. Also called "link beat," these pulses are used to ensure that the link is physically con(cid:173)
`ne{:ted.lt is the detection of this pulse that usually enables a "Link LED" on a lOBASE-T con·
`rroller or hub port.
`
`Page 5
`
`
`
`116
`
`Gigabit Etbemet Physical Layer
`
`requires that there be some minimum number of logic transitions in the
`code stream in order to provide clocking information. In the case of Giga(cid:173)
`bit Ethernet, the block code used guarantees this transition densiry.
`NRZJ-Non-Recurn-to-Zero, Invert on Ones-is a variation of NRZ
`th:n leaves the signal unchanged for a logic zero and inverts the signal from
`irs previous state for a logic one. NRZI is used in FDDI and 1 OOBASE(cid:173)
`FX; the 48/58 block code guarantees a sufficient "ones density."
`• Manchester code. This code, used in all10 Mb/s Ethernet systems, elimi(cid:173)
`nates the need for :tny transitions or one's density in the data srream-at
`the expense of increasing the maximum transmission frequency by a fac-
`tor of 2.
`• Multilevel Thrcshold-3 (MLT-3). This code uses three signal levels. The
`maximum transmission frequency is reduced by half (relative to NRZ),
`at the expense of reduced noise margin. The code leaves the signal un(cid:173)
`changed for a logic zero and moves the signal to the "next state" for a logic
`one, where the states are zero voltage, high voltage, zero voltage, low volt(cid:173)
`age, zero voltage, and so on.
`
`Data Panem
`
`0
`
`0
`
`0
`
`0
`
`0
`
`0
`
`0
`
`t
`
`•
`
`rtJ~'"--'uir--i-· _,___,.
`
`•
`
`•
`
`'
`
`NRZ
`
`NRZI
`
`Mandlester
`
`l
`
`0
`
`1
`
`0
`
`0
`
`+
`
`'
`
`MLT-3 0
`
`Figure 12- 3 Line coding.
`
`Page 6
Accessing this document will incur an additional charge of $.
After purchase, you can access this document again without charge.
Accept $ Charge
Still Working On It
This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.
Give it another minute or two to complete, and then try the refresh button.
A few More Minutes ... Still Working
It can take up to 5 minutes for us to download a document if the court servers are running slowly.
Thank you for your continued patience.
This document could not be displayed.
We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.
Your account does not support viewing this document.
You need a Paid Account to view this document. Click here to change your account type.
Your account does not support viewing this document.
Set your membership
status to view this document.
With a Docket Alarm membership, you'll
get a whole lot more, including:
- Up-to-date information for this case.
- Email alerts whenever there is an update.
- Full text search for other cases.
- Get email alerts whenever a new case matches your search.
One Moment Please
The filing “” is large (MB) and is being downloaded.
Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.
Your document is on its way!
If you do not receive the document in five minutes, contact support at support@docketalarm.com.
Sealed Document
We are unable to display this document, it may be under a court ordered seal.
If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.
Access Government Site
